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

If you are already familiar with BEA Jolt and BEA Tuxedo, Quick Configuration provides efficient guidelines for the configuration procedure. If you have not used Jolt, refer to Jolt Background Information before you begin any configuration procedures.

Quick Configuration contains the information you need to configure the Jolt Server Listener (JSL) on BEA Tuxedo and covers the following procedures:

• Editing the UBBCONFIG File

• Configuring the Jolt Repository

• Initializing Services That Use BEA Tuxedo and the Repository Editor

• Logging on to the Repository Editor

• Exiting the Repository Editor

• Configuring the BEA Tuxedo TMUSREVT Server for Event Subscription

• Configuring Jolt Relay

1. In the MACHINES section, specify MAXWSCLIENTS=number (Required).

   Note: If MAXWSCLIENTS is not set, JSL does not boot.

2. In the GROUPS section, set GROUPNAME required parameters [optional parameters].

3. Set the SERVERS section (Required).

   Lines within this section have the form:

   JSL required parameters [optional parameters] 

   where JSL specifies the file (string_value) to be executed by tmboot(1).

4. Set the required parameters for JSL.

   Required parameters are:

   SVRGRP=string_value

   SRVID=number

   CLOPT="-A...-n...//host port"

5. Set other parameters for JSL.

   You can use the following parameters with the JSL, but you need to understand how doing so affects your application. Refer to Parameters Usable With JSL for additional information.

   MAX # of JSHs

   MIN # of JSHs

1. Specify the same identifiers given as the value of the LMID parameter in the MACHINES section.

2. Specify the value of the GRPNO, between 1 and 30,000.

The BEA Jolt Repository Server (JREPSVR) contains services for accessing and editing the Repository. Multiple JREPSVR instances share repository information through a shared file. Include JREPSVR in the SERVERS section of the UBBCONFIG file.

1. Indicate a new server identification with the SRVID parameter.

2. Specify the -W flag for one (and only one) JREPSVR to ensure that you can edit the repository. (Without this flag, the repository is read-only.)

3. Type the -P flag to specify the path of the repository file. (An error message is displayed in the BEA Tuxedo ULOG file if the argument for the -P flag is not entered.)

4. Add the file pathname of the Repository file (for example, /app/jrepository).

5. Boot the BEA Tuxedo system by using the tmloadcf and tmboot commands.

Define the BEA Tuxedo services that use BEA Tuxedo and BEA Jolt in order to make the Jolt services available to the client.

1. Build the BEA Tuxedo server that contains the service.

2. Access the BEA Jolt Repository Editor.

Before you start the Repository Editor, make certain that you have installed all of the necessary BEA Jolt software.

Note: You cannot use the Repository Editor until JREPSVR and JSL are running.

To use the Repository Editor, you must:

1. Start the Repository Editor.

   You can start the Repository Editor from either the JavaSoft appletviewer or from your Web browser. Both of these methods are detailed in the following sections.

2. Log on to the Repository Editor.

1. Set the CLASSPATH to include the Jolt class directory or the directory where the *.jar files reside.

2. If loading the applet from a local disk, type the following at the URL location:

   appletviewer full-pathname/RE.html

   If loading the applet from the Web server, type the following at the URL location:

   http://www.server/URL path/RE.html

3. Press Enter.

   The window is displayed as shown in the figure BEA Jolt Repository Editor Logon Window.

Use one of the following procedures to start the Repository Editor from your Web browser.

1. Set the CLASSPATH to include the Jolt class directory.

2. Type the following:

   file:full-pathname/RE.html

3. Press Enter.

   The window is displayed as shown in the figure BEA Jolt Repository Editor Logon Window.

1. Ensure that the CLASSPATH does not include the Jolt class directory.

2. Remove the Jolt clases from CLASSPATH.

3. Type the following:

   http://www.server/URL path/RE.html

   Note: If jolt.jar and admin.jar are in the same directory as RE.html, the Web server provides the classes. If they are not in the same directory as RE.html, modify the applet code base.

4. Press Enter.

   The Repository Editor Logon window is displayed as shown in the figure BEA Jolt Repository Editor Logon Window.

After starting the Jolt Repository Editor, follow these directions to log on:

Note: The BEA Jolt Repository Editor Logon Window must be displayed before you log on. Refer to this figure as you perform the following procedure.

1. In the logon window, type the name of the Server machine designated as the "access point" to the BEA Tuxedo application and press Tab.

2. Type the Port Number and press Enter.

   The system validates the server and port information.

   Note: Unless you are logging on through Jolt Relay, the same port number is used to configure the Jolt Listener. Refer to your UBBCONFIG file for additional information.

3. Type the BEA Tuxedo Application Password and press Enter.

   Depending upon the authentication level, complete Steps 5 and 6 as required.

4. Type the BEA Tuxedo User Name and press Tab.

5. Type the BEA Tuxedo User Password and press Enter.

   The Packages and Services command buttons are enabled.

   Note: The BEA Jolt 1.2.1 Repository Editor uses the hardcoded joltadmin for the User Role value.

   BEA Jolt Repository Editor Logon Window

   

The following table, Repository Editor Logon Window Description, contains details about each of the fields and buttons.

Repository Editor Logon Window Description

Option	Description
Server	The server name.
Port Number	The port number in decimal value. Note: After the Server Name and Port Number are entered, the User Name and Password fields are activated. Activation is based on the authentication level of the BEA Tuxedo application.
User Role	BEA Tuxedo user role. Required only if BEA Tuxedo authentication level is USER_AUTH or higher.
Application Password	BEA Tuxedo administrative password text entry.
User Name	BEA Tuxedo user identification text entry. The first character must be an alpha character.
User Password	BEA Tuxedo password text entry.
Packages	Accesses the Packages window. (Enabled after the logon.)
Services	Accesses the Services window. (Enabled after the logon.)
Log Off	Terminates the connection with the server.

Exiting the Repository Editor

Exit the Repository Editor when you finish adding, editing, testing, or deleting packages, services, and parameters. Prior to exit, the window is displayed as shown in the figure BEA Jolt Repository Editor Logon Window Prior to Exit.

.

Note that only the Packages, Services, and Log Off command buttons are enabled. All of the text entry fields are disabled.

Follow the steps below to exit the Repository Editor.

1. Click Back in a previous window to return to the Repository Editor Logon window.

2. Click Log Off to terminate the connection with the server.

   The Repository Editor Logon window shows disabled fields.

3. Click Close from your browser menu to close the window.

Jolt Event Subscription receives event notifications from either BEA Tuxedo services or other BEA Tuxedo clients. Configure the BEA Tuxedo TMUSREVT server and modify the application UBBCONFIG file. The following listing, TMUSREVT Parameters in the UBBCONFIG File, shows the relevant TMUSREVT parameters in the UBBCONFIG file:

TMUSREVT Parameters in the UBBCONFIG File

TMUSREVT        SRVGRP=EVBGRP1  SRVID=40        GRACE=3600
                ENVFILE="/usr/tuxedo/bankapp/TMUSREVT.ENV"
                CLOPT="-e tmusrevt.out -o tmusrevt.out -A --
                -f /usr/tuxedo/bankapp/tmusrevt.dat"
                SEQUENCE=11

In the SERVERS sections of the UBBCONFIG file, specify the SRVGRP and SRVID.

Start the JRLY process on UNIX by typing the following command at the system prompt:

jrly -f <config_file_path>

If the configuration file does not exist or cannot be opened, the JRLY writes a message to standard error, attempts to log the startup failure in the error log, then exits.

The format of the configuration file is a TAG=VALUE format. Blank lines or lines starting with a "#" are ignored. The following listing, Formal Configuration File Specifications, is an example of the formal specifications of the configuration file.

LOGDIR=<LOG_DIRECTORY_PATH>
ACCESS_LOG=<ACCESS_FILE_NAME in LOGDIR>
ERROR_LOG=<ERROR_FILE_NAME in LOGDIR>
LISTEN=<IP:Port combination where JRLY will accept comma-separated connections>
CONNECT=<IP:Port1, IP:Port2...IP:PortN:Port(List of IP:Port combinations associated with JRADs: can be 1...N)>

SOCKETTIMEOUT is the time in seconds for which JRLY NT service blocks for network activity (new connections, data to be read, closed connections). SOCKETTIMEOUT also affects the Service Control Manager (SCM). When the SCM requests the NT service to stop, the SCM must wait for at least SOCKETTIMEOUT seconds before quitting.

Note: The format for directory and file names is determined by the operating system. UNIX systems use the forward slash (/). NT systems use the backslash (\). If any files specified in LOGDIR, ACCESS_LOG, or ERROR_LOG cannot be opened for writing, JRLY prints an error message on stderr and exits.

The formats for the host names and the port numbers are shown in the following table

.

Host Name and Port Number Formats

Host Name/Port Number	Description
//Hostname:Port	Hostname is a string; Port is a decimal number.
IP:Port	IP is a dotted notation IP address; Port is a decimal number.

Start the Jolt Relay Adapter (JRAD)

1. Type tmloadcf -y <UBBFILE>.

2. Type tmboot.

A single JRAD process can only be connected to a single JRLY. A JRAD can be configured to communicate with only one JSL and its associated JSH. However, multiple JRADs can be configured to communicate with one JSL. The CLOPT parameter for BEA Tuxedo services must be included in the UBBCONFIG file.

1. Type -l hexadecimal format (The JSL port to which the JRLY connects on behalf of the client.)

2. Type -c hexadecimal format (The address of the corresponding JSL to which JRAD connects.)

   Note: The format is 0x0002PPPNNN, or, in dot notation, 100.100.10.100.

3. Configure networked components.

   Jolt is now configured.