|
|
As a systems administrator, you may have an existing BEA Tuxedo application with multiple BEA Tuxedo services. Manually creating these definitions in the repository database may take hours to complete. The Jolt Bulk Loader is a command utility that allows you to load multiple, previously defined BEA Tuxedo services to the Jolt Repository database in a single step. Using the jbld program, the Bulk Loader utility reads the BEA Tuxedo service definitions from the specified text file and bulk loads them into the Jolt Repository. The services are loaded to the repository database in one "bulk load." After the services populate the Jolt Repository, you can create, edit, and group services with the Jolt Repository Editor.
This topic includes the following sections:
The jbld program 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 (that is, jolt.jar and joltadmin.jar) is located. If the CLASSPATH variable is not set, the Java Virtual Machine (JVM) cannot locate any Jolt classes.
For security reasons, 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 automatically prompts the user for passwords.
The Bulk Loader utility gets its input from command-line arguments and from the input file.
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 Jolt Repository using the package name "BULKPKG" by default. The -p command overrides the default and you can give the package any name you choose. If another load is performed from a bulk loader file with the same -p option, all the services in the original package are deleted and a new package is created with the services from the new bulk loader file.
If a service exists in a package other than the package you name that uses the -p option, 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 Using the Jolt Repository Editor for additional information.
Each service definition consists of service 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 jbld program reads the service definitions from a text file. To use the keywords, observe the guidelines in the following table.
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 service=<NAME> keyword definition (shown in the listing "Keyword Hierarchical Order in a Data File"). Following the service=<NAME> keyword, all 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.
All parameters associated with the service must be specified. Following each 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.
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=<NAME> keyword. Services using CARRAY, STRING, or XML buffer types should only have one parameter in the service. The recommended parameter name for a service that uses a CARRAY buffer type is CARRAY with carray as the data type. For a service that uses a STRING buffer type, the recommended parameter name is STRING with string as the data type. For a service that uses a XML buffer type, the recommended parameter name is XML with xml as the data type.
The following table contains the guidelines for use of the service-level keywords and acceptable values for each.
A parameter begins with the param=<NAME> keyword followed by a number of parameter keywords. It ends when another param or service keyword, or end-of-file is encountered. The parameters can be in any order after the param=<NAME> keyword.
The following table contains the guidelines for use of the parameter-level keywords and acceptable values for each.
If you encounter problems using the Bulk Loader utility, refer to the following table. For a complete list of Bulk Loader utility error messages and solutions, see "System Messages."
The following listing contains a sample data file in the correct format using the UNIX command cat servicefile. This sample loads TRANSFER, LOGIN, and PAYROLL service definitions to the BULKPKG.
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
|
