Overview

As each JMS provider implementation is vendor-specific, you must acquire the client jar files that allow third-party applications to connect and communicate with your JMS provider.

For example, if you are using the JMS functions in IBM's WebSphere Application Server on Linux or Windows, you need the following files:

sibc.jms.jar
sibc.jndi.jar
sibc.orb.jar

Location of Client Jar Files

You must place the JMS provider client jar files in the following location:

Linux	`/opt/universal/uac/container/webapps/axis2/WEB-INF/lib`
Windows	`\Program Files\Universal\uac\container\webapps\axis2\WEB-INF\lib`.

The names of the jar files differ depending on which JMS provider you are using.

Queue or Topic Infrastructure

The Universal Event Monitor for SOA JMS or MQ Series Connector does not provide the queue or topic infrastructure.

You must have a JMS provider or MQ Series Broker with queues or topics configured to use the JMS or MQ Series inbound operations.

Browser not supported