Use JMS to connect to a WAS default messaging provider messaging engine

The Thin Client for JMS with WebSphere Application Server is an embeddable technology that provides Java Message Service (JMS) V1.1 connections to a WAS default messaging provider messaging engine.

Subtopics

• Install and configure the Thin Client for JMS with WAS
  To use the Thin Client for JMS with WAS copy the com.ibm.ws.sib.client.thin.jms_8.5.0.jar and any other required files from the application server or application client %WAS_HOME%/runtimes directory.
• Use JMS resources with the Thin Client for JMS with WAS
  Suitable JMS connection factories and references to JMS queues or topics might be obtained programmatically without using JNDI. Alternatively, full JNDI support might be obtained from the Thin Client for EJB with WAS.
• Obtain IBM MQ JMS resources in the thin client environment
  A stand-alone Java SE JMS thin client application that connects to an external IBM MQ queue manager can get administratively-created IBM MQ messaging provider JMS resources from the WAS JNDI namespace.

Secure JMS client and JMS resource adapter connections

Add tracing and logging for stand-alone clients