Configuring RepConnector for JMS messaging systems

Use this section to set up the RepConnector environment, so that RepConnector can communicate with:

WebLogic Server (WLS) JMS
SonicMQ JMS

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 it is configured correctly.

Configuring 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 configure a connection to a WebLogic server using JMS queues.

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

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

/work/bea/weblogic81/server/lib/weblogic.jar:$CLASSPATH
/work/bea/weblogic81/server/lib/weblogic.jar:$BOOTCLASSPATH

Restart EAServer.

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

Configuring for SonicMQ JMS

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

Verify that the line in repra_env.sh that defines the SONICMQ_HOME environment variable is not commented out and points to the installation location for SonicMQ.
```
SONICMQ_HOME= /work/SonicSoftware/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.
```
REPRA_CLASSPATH=$SONICMQ_HOME/lib/sonic_Client.jar
CLASSPATH=$CLASSPATH:$REPRA_CLASSPATH
BOOTCLASSPATH=$BOOTCLASSPATH:$REPRA_CLASSPATH
```
Restart your application server.