Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Jolt   |   Topic List   |   Previous   |   Next   |   Contents   |   Index

   Using BEA Jolt

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:

• Service-level

• Parameter-level

Guidelines for Using Keywords

The jbld program reads the service definitions from a text file. To use the keywords, observe the guidelines in the following table.

Guidelines for Using Keywords

Guideline	Example
Each keyword must be followed by an equal sign (=) and the value.	Correct: type=string Incorrect: type
Only one keyword is allowed on each line.	Correct: type=string Incorrect: type=string access=out
Any lines not having an equal sign (=) are ignored.	Correct: type=string Incorrect: type string
Certain keywords only accept a well-defined set of values.	The keyword access accepts only these values: in, out, inout, noaccess
The input file can contain multiple service definitions.	service=INQUIRY <service keywords and values> service=DEPOSIT <service keywords and values> service=WITHDRAWAL <service keywords and values> service=TRANSFER <service keywords and values>
Each service definition consists of multiple keywords and values.	service=DEPOSIT export=true inbuf=VIEW32 outbuf=VIEW32 inview=INVIEW outview=OUTVIEW

Keyword Order in the Bulk Loader Data File

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 or STRING 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.

The following table contains the guidelines for use of the service-level keywords and acceptable values for each.

Service-Level Keywords and Values

Keyword	Value
service	Any BEA Tuxedo service name
export	true or false (default is false)
inbuf/outbuf	Select one of these buffer types: FML FML32 VIEW VIEW32 STRING CARRAY X_OCTET X_COMMON X_C_TYPE
inview	Any view name for input parameters (This keyword is optional only if one of the following buffer types is used: VIEW, VIEW32, X_COMMON, X_C_TYPE.)
outview	Any view name for output parameters (optional)

Using Parameter-Level Keywords and Values

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.

Parameter-Level Keywords and Values

Keyword	Values
param	Any parameter name
type	byte short integer float double string carray
access	in out inout noaccess
count	Maximum number of occurrences (default is 1). The value for unlimited occurrences is 0. Used only by the Repository Editor to format test screens.