Using JMS resources

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

About this task

If you are using the Thin Client for JMS with WebSphere Application Server, you 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 WebSphere Application Server. For further information, refer to the Using JMS resources with the Thin Client for JMS with WebSphere Application Server topic.

If you 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 WebSphere Application Server JNDI namespace, refer to the Obtaining WebSphere MQ JMS resources in the thin client environment topic.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=tcli_standaloneclient_resource
File name: tcli_standaloneclient_resource.html