If you are using WebSphere® Default
Messaging or WebSphere MQ,
you should obtain the jars required.
Note: The classpath information provided in this section
is intended as a starting point for your implementation. Depending
upon the JMS, JNDI, and JDK you are using you may need to add or remove
jars from the lists given here.
Both WebSphere and
MQ have jars which are required for running the agent and integration
servers. You can obtain these jars from the WebSphere or MQ server.
IBM WebSphere
If you
are using WebSphere Default
Messaging, include the following jars:
- <WAS_HOME>/runtimes/com.ibm.ws.sib.client.thin.jms_version_number.jar
- <WAS_HOME>/runtimes/com.ibm.ws.ejb.thinclient_version_number.jar
- <WAS_HOME>/runtimes/com.ibm.ws.orb_version_number.jar (for
non-IBM JREs only)
where version_number is the version of WebSphere you are using.
Note: If you are using WebSphere version
7.0.0.7 or higher, set the following property to true in the WebSphere console under Application
Servers >
your server name > web container >
custom properties:
com.ibm.ws.webcontainer.dispatcherRethrowSER=true
IBM WebSphere MQ using "fscontext"
jndi
When using WebSphere MQ you should obtain the following
jars from MQ_HOME/java/lib:
- com.ibm.mq.jar
- com.ibm.mqjms.jar
- fscontext.jar
- dhbcore.jar
- jms.jar
- jta.jar
providerutil.jar