WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the default messaging provider > Use JMS from stand-alone clients to interoperate with service integration resourcesUse 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 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 WebSphere MQ JMS resources in the thin client environment
A stand-alone Java SE JMS thin client application that connects to an external WebSphere MQ queue manager can get administratively-created WebSphere MQ messaging provider JMS resources from the WAS JNDI namespace.
Related
Secure JMS client and JMS resource adapter connections
Add tracing and logging for stand-alone clients