This section covers the following topics:
As a systems administrator, you may have an existing TUXEDO application with multiple TUXEDO services. Manually creating these definitions to the repository database may take hours to complete.
Using the program, See Chapter 5, "Using the Jolt Repository Editor," for information about using the Jolt Repository Editor.
Since For security reasons, The bulk loader utility gets its input from command-line arguments and from the input file.
To activate the bulk loader using UNIX:
Introduction to the Bulk Loader
jbld, the bulk loader utility reads the specified text file consisting of the TUXEDO service definitions and bulk loads them into the Jolt repository. The services are loaded to the repository database in one "bulk load." After the services have populated the Jolt Repository, you may edit services, create new services, and group services using the Jolt Repository Editor.
Getting Started Using the Bulk Loader
jbld is a Java application, before running the jbld command, set the CLASSPATH environment variable (or its equivalent) to point to the directory where the Jolt class directory (e.g., /opt/bea/jolt/classes) is located. If it is not set, the Java Virtual Machine cannot locate any Jolt classes.
jbld does not use command-line arguments to specify user authentication information (user password or application password). Depending on the server's security level, jbld will automatically prompt the user for passwords.
Using UNIX
setenv CLASSPATH <pathname>
java bea.joltadm.jbld [-n] [-u usrname] [-r usrrole] <//host:port inputfile>
C:\> set CLASSPATH=C:<pathname>
C:\> java bea.jolt.jbld [-n][-u usrname] [-r usrrole] <//host:port> <filename>
Table 4-1 describes the bulk loader command-line options.
The bulk load file is a text file that defines services and their associated parameters. The bulk loader loads the services defined in the bulk loader file into the repository using the package name, "BULKPKG." If a bulk load has been performed, the "BULKPKG" package exists in the repository. If another load is performed from a bulk loader file, all the services in the original "BULKPKG" are deleted. A new "BULKPKG" package is created with the services from the new bulk loader file.
If a service exists in a package other than "BULKPKG," the bulk loader reports the conflict and does not load a service from the bulk loader file into the repository. Use the Repository Editor to remove duplicate services and load the bulk loader file again. See Chapter 5, "Using the Jolt Repository Editor," for additional information.
Each service definition consists of services properties and parameters that have a set number of parameter properties. Each property is represented by a keyword and a value.
Keywords are divided into two levels:
The
Keyword order must be maintained within the data files to ensure an error-free transfer during the bulk load.
The first keyword definition in the bulk loader data text file must be the initial Next, specify all the parameters associated with the service. Following each of the Guidelines for Using Keywords
jbld reads the service definitions from a text file. While using the keywords, follow the guidelines in Table 4-2.
Keyword Order in the Bulk Loader Data File
service=<NAME> keyword definition (shown in Listing 4-1). Following the service=<NAME> keyword, all of the remaining service keywords that apply to the named service must be specified before the first param=<NAME> definition. These remaining service keywords can be in any order. Refer to Table 4-3 for a list of the service keywords and values.
param=<NAME> keywords are all the parameter keywords that apply to the named parameter until the next occurrence of a parameter definition. These remaining parameter keywords can be in any order. When all the parameters associated with the first service are defined, specify a new service=<NAME> keyword definition.
Listing 4-1
Correct Example of Hierarchical Order in a Data File
service=<NAME>
<service keyword>=<value>
<service keyword>=<value>
<service keyword>=<value>
param=<NAME>
<parameter keyword>=<value>
<parameter keyword>=<value>
param=<NAME>
<parameter keyword>=<value>
<parameter keyword>=<value>
A service definition must begin with the "service=" keyword. For more information about services, see Chapter 5, "Using the Jolt Repository Editor."
Note: Services using CARRAY or STRING buffer types should only have one parameter in the service. The recommended parameter name for a CARRAY service is "CARRAY" with "carray" as the data type. For a STRING service, the recommended parameter name is "STRING" with "string" as the data type. See Chapter 5, "Using the Jolt Repository Editor," for more information.
To review the service-level keywords and values, see Table 4-3.
A parameter begins with the "param=" keyword followed by a number of parameter keywords until another "param" or "service" keyword, or end-of-file is encountered. The parameters can be in any order after the "param" keyword.
See Chapter 5, "Using the Jolt Repository Editor," for more information about parameters.
To review the parameter-level keywords and values, see Table 4-4.
If you encounter any problems using the bulk loader utility, see Table 4-5. For a complete list of bulk loader utility error messages and solutions, see Appendix B, "System Messages."
Listing 4-2 shows a sample data file in the correct format using the following UNIX command, cat servicefile. This example loads TRANSFER and PAYROLL service definitions to the BULKPKG.
Listing 4-2 Sample Bulk Load Data
service=TRANSFER
export=true
inbuf=FML
outbuf=FML
param=ACCOUNT_ID
type=integer
access=in
count=2
param=SAMOUNT
type=string
access=in
param=SBALANCE
type=string
access=out
count=2
param=STATLIN
type=string
access=out
service=LOGIN
inbuf=VIEW
inview=LOGINS
outview=LOGINR
export=true
param=user
type=string
access=in
param=passwd
type=string
access=in
param=token
type=integer
access=out
service=PAYROLL
inbuf=FML
outbuf=FML
param=EMPLOYEE_NUM
type=integer
access=in
param=SALARY
type=float
access=inout
param=HIRE_DATE
type=string
access=inout