Implementation Considerations

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

• The jrly binary and its corresponding jrly.config file must exist in the same directory. To start multiple Jolt Relays on a machine, copy the jrly binary and jrly.config into each subdirectory, modify the parameters in the jrly.config file, and start Jolt Relay. On Windows, you can define multiple Jolt Relay services on a machine.

• You can start the JRLY process before or after you start JRAD. The JRLY attempts to connect to JRAD on the client request. If the JRLY is unable to connect to the JRAD, the client is denied access and disconnected. The connection will be retried upon the first use of PeopleTools..

• If you're installing Jolt Internet Relay on UNIX and anticipate a large number of concurrent connected clients, increase the file descriptors limit before running the JRLY executable.

• At runtime, if you get the following message:

  [FRi JUNl 6 20:25:11 1997] JRLY:accept():accept failed,⇒
   err no: 23, strerror: File table overflow

  PeopleSoft recommends that you increase the MaxUSERS kernel parameter and regenerate the kernel.

• If you're unable to connect, make sure that you check the following items:

  • Port numbers do not match.

    Print out the jrly.cfg file and the psappsrv.cfg file and compare the port numbers that you specified.

  • Make sure that the application server is running.

  • Make sure that JRLY is running.

• Jolt Internet Relay can be installed on an intermediate machine rather than the web server machine if necessary. This extra level of indirection can cause performance degradation.

• Make sure that JRAD is running on the application server and that you configure JRAD using PSADMIN.