Configuring RepConnector for JMS Messaging Systems

This section provides instructions for setting up the RepConnector environment so that RepConnector can communicate with the following JMS Messaging Systems:

NoteInstructions for EAServer JMS and TIBCO JMS messaging systems are not included in this section:

Sybase recommends that you configure your environment before you proceed with configuring the RepConnector connection. This enables you to ping the JMS Messaging System during configuration to verify that you have configured it properly. If you do not configure your RepConnector environment before configuring the RepConnector connection, RepConnector Manager allows you to create the connection even if the ping has failed. However, you must go back to verify this once you have set up the RepConnector environment.

StepsConfiguring WebLogic Server JMS

If you are using RepConnector on EAServer and you are configuring a RepConnector connection to send events to a WebLogic JMS server, modify the RepConnector batch or script file to correctly configure a connection to a WebLogic server using JMS queues.

NoteNo additional steps are required if you are running RepConnector on WebLogic Server.

  1. Verify that the lines in repra_env.bat (Windows) or repra_env.sh (UNIX) that add the weblogic.jar library file to the CLASSPATH/BOOTCLASSPATH variable setting are not commented out and are correct for your environment:

  2. To effect the changes, restart EAServer.

  3. Create a RepConnector connection or, if one already exists, use RepConnector Manager to validate the connection configuration. See “Creating RepConnector connections” for more information.

StepsConfiguring for SonicMQ JMS

Verify that the path to the SonicMQ library files are defined correctly in the RepConnector environment batch or script files:

  1. Verify that the lines in repra_env.bat (Windows) or repra_env.sh (UNIX) that define the SONICMQ_HOME environment variable are not commented out and point to the installation location for SonicMQ.

    Verify that the lines that define the directory structure for the SonicMQ library file, sonic_Client.jar, are not commented out and are correct for your environment.

  2. To effect the changes, restart your application server.