Use JMS resources

If using JMS resources with the Thin Client for JMS with WAS, we can choose either to obtain these resources programmatically or using the JNDI. Standalone 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 Java Naming and Directory Interface (JNDI) namespace.

If 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, see Use JMS resources with the Thin Client for JMS with WAS.

For a standalone 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, see Obtaining WebSphere MQ JMS resources in the thin client environment.