Skip to Main Content
Return to Navigation

Configuring 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:

Parameter

Description

LOGDIR

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

ACCESS_LOG specifies the name of the file where JRLY records access information. This log file is created inLOGDIR. 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

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

LISTEN

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=192.9.100.100:9000
LISTEN=//192.9.100.100:9000
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 configuration.properties 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

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 inPS_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=192.9.100.100:9100
CONNECT=//207.135.44.91:9105
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

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.