JMS Provider Client Jar Files for Outbound

As mentioned in JMS Provider Client Jar Files, set-up and use of the JMS Connector is dependant on the JMS provider being used.

Each JMS provider is specific to its vendor implementation; thus, it will have vendor specific setup and configuration that needs to take place before you can run JMS operations. Specifically, the Universal Command Agent for SOA: JMS Connector requires the JMS provider client jar files to connect and communicate with the JMS provider.

When you have acquired these client jar files from your JMS provider vendor, you would place them in the following directory:

For example, if you are using the JMS functions in IBM's WebSphere Application Server, you would need the sibc.jms.jar, sibc.jndi.jar, and sibc.orb.jar files.

If you were using Apache's ActiveMQ JMS provider you would need the apcache-activemq-4.1.1.jar file.