Deploying messaging applications to Liberty
JMS applications deployed within the Liberty server can make use of the internal embedded messaging provider or the external IBM MQ as its JMS messaging provider.
Subtopics
- Deploying JMS applications to connect to the embedded messaging server
To deploy messaging applications that use the Java™ Messaging Service (JMS), you must add the wasJmsServer-1.0 and wasJmsClient-2.0 features to the server.xml file, and define the connection factory and destination properties. If you want to perform a JNDI lookup, then you must add the jndi-1.0 feature along with the other two features. - Deploying JMS applications to Liberty to use the IBM MQ messaging provider
Through the IBM MQ messaging provider in Liberty, Java Message Service (JMS) messaging applications can use your IBM MQ system as an external provider of JMS messaging resources. - 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. - Deploying JMS applications on the Liberty application client container
You can configure messaging applications that use wasJmsClient-2.0 feature to run on the Liberty application client container. - Enabling JMS tracing for the Liberty embedded messaging
JMS traces can be used in Liberty for problem determination and troubleshooting. - Deploying message-driven beans within Liberty
Liberty supports the configuration and deployment of message-driven beans (MDB) to process the JMS messages asynchronously from various destinations. - Configuring connection pooling for JMS connections
You can customize the number of concurrent connections (default is 50) that can be created from a JMS connection factory. You can configure connection pooling for a specific JMS connection factory by defining the <connectionManager> element and then associate that element with the JMS connection factory in the server.xml file.
Parent topic: Deploying applications in Liberty
Related concepts:


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twlp_dep_messaging
File name: twlp_dep_messaging.html