Skip to content


April 11, 2008

If we need to configure an existing service to be available to Jolt client we need the following steps:

Jolt Server, Jolt Class Library, Jolt Repository, Jolt internet relay.

Jolt Servers

The following Jolt Server components act in concert to pass Jolt client transaction processing requests to the BEA Tuxedo application.

Jolt Server Listener (JSL)
Jolt client connection, and assigns client to JSH

Jolt Server Handler (JSH)
The JSH manages network connectivity, executes service requests on behalf of the client and translates BEA Tuxedo buffer data <—> Jolt buffer

Jolt Repository Server (JREPSVR)
The JREPSVR retrieves Jolt service definitions from the Jolt Repository and returns the service definitions to the JSH. The JREPSVR also updates or adds Jolt service definitions.



Define repository – either using applet – Jolt repository editor or using the bulk tool. jbld program is a Java application.

set the CLASSPATH environment variable (or its equivalent) to point to the directory where the Jolt class directory (that is, jolt.jar and joltadmin.jar) is located

java bea.jolt.admin.jbld [-n][-p package][-u usrname][-r usrrole] //host:port filename

-n to validate and not make change . Default package is BULKPKG. Use -p to override.

Example of a bulk upload file


JOLT Basics

.LDR file which is having all the input and the output fields mentioned
compile time integration with vb applications for services

Create a .TBL file and then compile it – you get a .tbl.h file.
.tbl.h file has the ID – of the variables input and output and this file is imported
in the vb application

Application server – set of services – and these services are then, called.
But to call them – how do fml Buffer and java datatypes interchange?
To interchange them – we need a file – that has the ID’s and fml buffers corresponding to it existing. and this file is existing in JRepository.

Now, keep a default JRepository.default – and in case you find that your jreposity is having
DELETE statements – after updation of service params – just replace the new jrep file with default and then do a fresh reload. Otherwise it will consider the appended,deleted,appended -as in sequential processing of the file would take place. would make it unclean.

And then You have a JREP server that is responsible for using the jrepository file and then communicating the right data type with the java program.Similary using that file and translating the java data type to the FML Buffer type.

So the name that you use in the .TBL file is important because each name is mapped to an ID in the Jrep file. In case two different services are using the same input name then, it would pick up the first ID mapping to the name and would use that for the service resulting in an error FML Field Not found.

So we need to create the .TBL file at the application server level and also have a .LDR file which is having all the parameter names,datatypes existing and pushed into JRepository.
what they do is – FMl32 – is used for getting the input data and FMLAppend is used for getting the result output writing….

Basically Mappings – FMLBuffer, ID , Names, DataTypes. etc…..
So in the environment variable FMLBFRDIR and FMLBFR32 – we have the directory and files – to be picked up sequentially for the mappings.
So for Java applications – resolving of the data types with buffer is a run time integration.
JRAD -is for adding a second layer – for routing from one listener to the other – just to mantain the inter layer communication of the architecture – this can be removed if needed.
JSL – is the listener for the service.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: