Deploying JMS application to connect to the Service Integration Bus running on WebSphere Application Server traditional
To deploy the messaging applications that use the Java™ Messaging Service (JMS) to connect to the messaging engine that is running on WebSphere® Application Server traditional, you must add the wasJmsClient-2.0 and jndi-1.0 features to the server.xml file. If you want to perform a JNDI lookup, then you must add the jndi-1.0 feature. You must also define the connection factory and destination properties.
Before you begin
Ensure that you created a Liberty server on which you want to deploy the messaging application that uses JMS. For more information, see Creating a Liberty server manually.
Important: The wasJmsClient-2.0 feature supports the features of both JMS 1.1 and JMS 2.0 specifications. However, you can choose to use the wasJmsClient-1.1 feature if you want to use only the features that are compliant with JMS 1.1 specification.
About this task
The wasJmsClient-2.0 feature provides support for applications that use Java Messaging Service 1.1 specifications.