Previous Topic: Enabling Tuxedo Servers for Java Client AccessNext Topic: Client-Side Changes


Bulk Loading the Jolt Repository

When the server remotes (.RMT files) are split and built, it results in the generation of some Tuxedo specific files for each server load module. These files have the extensions .tvf, .jvf, and .sh.

The .jvf files make the Tuxedo servers accessible to Java-based clients. The .tvf and the corresponding .jvf files both describe the views that are used by the Tuxedo server, but differ in some of the field names and field types.

The .jblk files are the result of the compilation of the .jvf file, which takes place when the .sh files are executed by the user to enable access by Java-based clients to Tuxedo Servers. The .jvf can also be compiled into the .jblk as follows:

$IEFH/make/jvf2jblk.sh JvfFile.jvf

Before continuing, the Jolt servers (JSL and JREPSVR) must be started.

The data in the .jblk file is in a format that is understood by the Jolt Bulk Loader. The Tuxedo Administrator needs to load the information from the .jblk file into the Jolt Repository, using the Bulk Loader tool provided with the Jolt installation.

java oracle.jolt.admin.jbld -p package //jslHostName:jslPortNumber JblkFileName

Where package could be a Name under which the Services are grouped.