Working with Jolt Configuration Options

This chapter provides overview information and discusses how to:

Click to jump to parent topicConfiguring Jolt Failover and Load Balancing

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicConfiguring Weighted Load Balancing

With weighted load balancing, you can set the “weight” of the load, or amount of requests, being directed to a particular server. Weight values are integers 1–10, with 1 being low and 10 being a heavy load. Servers that can handle extra work can take heavy loads, while servers that are either less powerful or are being used in other capacities can take lower loads. You specify weighted load balancing by modifying the server values in the psserver property in the PeopleSoft Internet Architecture file, using the following format.


For example,


In this case, appserver1 would receive 3x more requests than appserver2.

Click to jump to top of pageClick to jump to parent topicConfiguring Jolt Failover

You an also specify strict failover assignments with weighted load balancing, with the following options:

You add the failover string within curly brackets at the end of the server entry.

psserver=<host>:<port>#wt{failover servers}

With the failover string, you can set weighted backup by separating failover server with a comma (,).


In this case, Host 3 and Host 4 are failover servers when Host 1 is down. You can assign weighted load balancing to the backup servers just as you would a primary server.

You can also set a sequential backup with your failover string. To set sequential backup, you separate multiple backup servers using a semicolon (;).


In this case, the system assigns Host 4 the requests when both Hosts 1 and 3 are down.

Click to jump to parent topicConfiguring Jolt Session Pooling

Jolt session pooling is enabled by default. Jolt session pooling enables web server connections to be shared between user sessions, which reduces the usage of system resources, such as threads and file descriptors.

You control session pooling by modifying the joltPooling property in the file per site.


To enable Jolt session pooling, set the property value to true, and to disable Jolt session pooling set the property value to false.

Click to jump to parent topicConfiguring Domain Connection Password

The DomainConnectionPwd setting in the [Security] section of the application server domain, sets the domain connection password for all PeopleSoft Internet Architecture Jolt connections to that application server domain. For the Jolt session to connect successfully to the application server domain the DomainConnectionPwd property value in the file needs to match the DomainConnectionPwd parameter set for the application server domain.

The default value is PS and it is encrypted by the pscipher utility. For example:


Click to jump to parent topicUnderstanding Jolt Internet Relay

This section discusses:

Click to jump to top of pageClick to jump to parent topicJolt Internet Relay Architecture

Jolt Internet Relay provides an environment in which the PeopleSoft web server and application server can be further decoupled. This provides greater security at sites where security is of utmost importance. Jolt Internet Relay routes messages from a Jolt client to a Jolt Server Listener (JSL) or Jolt Server Handler (JSH), and eliminates the need for the JSL, JSH, and Tuxedo application to run on the same machine as the web server. Communication takes place between the JRLY and JRAD elements rather than between the Jolt client and JSL/JSH processes. Traditionally an application server domain opens between 2 and 6 ports for such communications. The use of Jolt relay restricts this to one port per domain on the application server machine. This enables an administrator to open just one port on the application server machine. The following diagram illustrates this feature:

Jolt Internet Relay Architecture showing the Jolt Relay sending messages through a firewall to the Jolt Relay Adapter

Jolt Internet Relay consists of two elements: Jolt Relay (JRLY) and Jolt Relay Adapter (JRAD). It's important to understand the difference between these two elements.

JRLY consists of a standalone program and configuration file; the program runs on the same machine as the web server. JRLY receives Jolt messages from a PeopleSoft web application and routes those messages to JRAD on the application server. It receives the Jolt message through one port, the LISTEN port, and connects to the JRAD by using another port, the CONNECT port. JRLY is sometimes referred to as a front-end relay.

JRAD runs on the same machine as the application server. It's configured on the application server domain as part of the PeopleSoft PSADMIN domain configuration procedure. JRAD listens for JRLY messages on its LISTEN port and transfers the message to the JSL or JSH. JRAD is sometimes referred to as a back-end relay.

Note. Implementing Jolt Relay can impede performance. Always perform testing with typical production system load to ensure it will meet your service level requirements.

Click to jump to top of pageClick to jump to parent topicImplementation Considerations

Keep the following points in mind as you configure the Jolt Internet Relay components:

Click to jump to parent topicConfiguring JRLY

Configuring JRLY is identical on UNIX and Windows.

To configure JRLY, navigate toTUXDIR\udataobj\jolt\relay and open jrly.config in a text editor.

Important! On UNIX, you can edit this configuration file by using VI or an equivalent editor. However, on Windows, you must edit the file using an editor that preserves the file's UNIX line feeds. WordPad is valid for this purpose, but Notepad is not.

Modify the parameters in the configuration file to reflect the site specifications, as follows:




LOGDIR specifies the directory where JRLY creates access and error log files. This directory must exist; the JRLY program does not start if it can't find this directory. The path that you specify for LOGDIR should be an absolute path (starting from / on UNIX systems, starting from a drive letter on Windows systems). The JRLY accepts relative path names, but LOGDIR is relative to the directory from which the JRLY program is started, unless you specify it as an absolute.


ACCESS_LOG specifies the name of the file where JRLY records access information. This log file is created in LOGDIR. If the log file already exists, the most recent information is appended to it.

This parameter can be any valid file name. Everything after the equals sign (=) to the end of the line is considered as part of the file name, but leading and trailing blanks are ignored.

Note. If the JRLY program can't create this file or open it for appending, the program exits.


ERROR_LOG specifies the name of the file where JRLY records error information. This file follows all the rules that apply to the ACCESS_LOG parameter. JRLY_error_log is created in /tmp.


LISTEN specifies the host and port on the current machine (that is, the machine where you're installing Jolt Relay). JRLY listens for client connections. The following formats are acceptable:

LISTEN= LISTEN=// LISTEN=sp-ibm02:9000 LISTEN=//sp-ibm02:9000

Specify the port number in decimal; it must match the port number that is specified by the psserver parameter in the file for the PIA web application.

Note. If a machine has multiple network interfaces, you should use the IP address notation, because specifying the hostname could be ambiguous (the result is OS dependent). If the JRLY program can't establish a network listening end-point at the host and port specified, it prints an error and exits.

The hostname that's specified for this parameter must be the name of the host on which the program is running.

Note. You can create multiple configuration files to run multiple instances of JRLY. Each configuration file must specify a different port number for this parameter.


CONNECT specifies the location of the JRAD machine and process port on the application server machine to which the JRLY program connects. A JRLY program communicates only with a single JRAD. The address you specify for this parameter must match the JRAD listener address that's on the application server machine (check the PSAPPSRV.CFG file in PS_CFG_HOME/appserv/domain). The JRAD doesn't have to be running when you start the JRLY program. JRLY attempts to connect to the JRAD when it first starts, and if the JRAD is not available, JRLY tries again whenever a new client connects to it. You can use any of the following formats for this parameter:

CONNECT= CONNECT=// CONNECT=sp-hp06:9105 CONNECT=//sp-hp06:9105

Note. PeopleSoft has found that machine address formats are operating system and environment dependent. If one fails to connect to the application server, try another format.


SOCKETTIMEOUT specifies the duration (in seconds) for which the Jolt Internet Relay Windows service blocks the establishment of new socket connections to allow network activity (new connections, data to be read, closed connections) to complete. It's valid only on Windows machines.

SOCKETTIMEOUT also affects the Service Control Manager (SCM). When the SCM requests that the service stop, the SCM needs to wait at least the number of seconds specified by this parameter.

Click to jump to parent topicConfiguring JRAD

The JRLY connect port connects to the JRAD listener port that is specified on the application server machine. JRAD then routes the message to Jolt, either using the JSL for initial connection from a web client, or using the JSH for all subsequent connections from a web client. The return message follows the same path in reverse.

To configure JRAD:

  1. Launch the PSADMIN utility.

  2. Navigate to the PeopleSoft Domain Administration menu and select Configure this domain.

  3. In the Quick Configure menu, select the number for the Jolt Relay option, to enable Jolt Internet Relay.

  4. Select the JRAD Port option, and enter the appropriate port number for the JRAD Port.

    Note. The JRAD (listener) port number must match the JRLY connect port that you previously configured.

See Also

Using the Quick-Configure Menu

Click to jump to parent topicRunning Jolt Relay

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicUsing the JRLY Administration Program

You use the jrly command located in TUXDIR\udataobj\jolt\relay to administer Jolt Relay on all platforms. You can use the following jrly command options at any time:

Click to jump to top of pageClick to jump to parent topicRunning Jolt Relay on Windows

On Windows, you set up Jolt Relay to run as a service. On other platforms you must run Jolt Relay directly.

See Running Jolt Relay on UNIX.

If you want to install multiple Jolt Relay services, you must specify a string to be used as a display suffix that uniquely identifies each additional service you install. You subsequently use the suffix to identify each service it commands. An additional service with the suffix MyJoltRelay, for example, is called Oracle Jolt Relay_MyJoltRelay, but you refer to it using only the suffix. You can omit the suffix when installing only one of these services, which becomes the default Jolt Relay service, called Oracle Jolt Relay.

Note. All administrative commands in the following table except -start and -stop require that you have write access to the Windows registry. The -start and -stop commands require that you have Windows service control access. These requirements are based on Windows user restrictions.



jrly -install [display_suffix]

Install JRLY as a Windows service.

jrly -remove [display_suffix | -all]

Remove one instance, all instances, or the default JRLY Windows service.

jrly -set [-d display_suffix] -f config_file

Update the registry with the full path of a new configuration file for the specified JRLY service.

Note. You can run multiple Jolt Relay services by specifying a different display suffix along with the name of a different configuration file for each installed service. Each configuration file must contain a unique value for the LISTEN parameter that specifies a different port. This is essential to avoid port clashes when running the services concurrently. You must run this command before the service starts.

jrly -manual [display_suffix]

Set the start/stop to manual. This command sets the specified JRLY service to be manually controlled, using either the command-line options or the Service Control Manager (SCM).

jrly -auto [display_suffix]

Set the start/stop to automatic. This command sets all the operations for a specified JRLY service to be automatically started when the OS boots and stopped when the OS shuts down.

jrly -start [display_suffix]

Start the specified JRLY service.

jrly -stop [display_suffix]

Stop the specified JRLY service.

Click to jump to top of pageClick to jump to parent topicRunning Jolt Relay on UNIX

This section discusses how to start and stop Jolt Relay directly from a command line on UNIX.

To start Jolt Relay on UNIX:

  1. Change directories to the Jolt Relay directory within your Tuxedo installation:

    cd $TUXDIR/udataobj/jolt/relay

  2. Run the following command:

    jrly -f ​jrly_config &

    Where jrly_config is the name of a Jolt Relay configuration file.

    You can run multiple instances of Jolt Relay by using a different port for each instance. You run JRLY once for each instance, and specify a different configuration file each time. Each configuration file must contain a value for the LISTEN parameter that specifies a different port.

    The & causes JRLY to run in the background.

To shut down Jolt Relay on UNIX, use the UNIX kill -9 command.