An installation of FME Server includes the libraries that are required for using JMS messaging with Apache ActiveMQ 5.6.0. For all other message brokers, vendor-specific JMS libraries must be acquired and installed alongside FME Server.
Typically, vendor-specific JMS libraries are either available in the message broker’s installation, or available in a separate message broker client. In the case of IBM WebSphere MQ 7, for example, a separate client installation is available.
The table below provides links to appropriate software. For additional information, consult your vendor's documentation.
To install the JMS Libraries
- Download and install the software containing the vendor-specific JMS implementation library to the machine with the installation of FME Server.
- Locate the required libraries. (See the table below, under "Libraries.")
- Note the directory containing the required libraries. When Configuring FME Server as a JMS Client, this directory is added to the java classpath.
| Message Broker | Libraries | Sample Path (Windows) |
|---|---|---|
| Apache ActiveMQ | none (Apache ActiveMQ 5.6.0 libraries bundled with FME Server) | -- |
| IBM WebSphere 7.1 |
com.ibm.mq.jmqi.jar com.ibm.mqjms.jar dhbcore.jar fscontext.jar providerutil.jar |
C:\Program Files (x86)\IBM\WebSphere MQ\java\lib |
| HornetQ |
hornetq-jms.jar hornetq-jms-client.jar jnp-client.jar |
C:\hornetq-x.y.z\lib |
| Oracle Weblogic | wlthint3client.jar |
What's Next?
Depending on your message broker, additional configuration may be required to enable JMS. See Configuring the JMS Provider