WAS v8.5 > Develop applications > Develop Client applications > Develop client applications > Develop stand-alone thin client applicationsUse JMS resources
If we are using JMS resources with the Thin Client for JMS with WebSphere Application Server, we can choose either to obtain these resources programmatically or using the JNDI. Stand-alone Java SE JMS thin client applications that connect to an external WebSphere MQ queue manager can get administratively-created WebSphere MQ messaging provider JMS resources from the WAS JNDI namespace. If we are using the Thin Client for JMS with WAS, we can obtain suitable JMS connection factories and references to JMS queues or topics programmatically without using JNDI. Alternatively, full JNDI support might be obtained from the Thin Client for EJB with WAS. For further information, refer to the Using JMS resources with the Thin Client for JMS with WAS topic.
If we are using a stand-alone Java SE JMS thin client application that connects to an external WebSphere MQ queue manager and want to obtain administratively-created WebSphere MQ messaging provider JMS resources from the WAS JNDI namespace, refer to the Obtaining WebSphere MQ JMS resources in the thin client environment topic.
Related
Use JMS resources with the Thin Client for JMS with WAS
Obtain WebSphere MQ JMS resources in the thin client environment