Deploying messaging applications to the Liberty profile
JMS applications deployed within the Liberty profile can
make use of the internal embedded messaging provider or the external WebSphere® 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-1.1 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 application to connect to the Service Integration Bus running on full profile WebSphere Application Server
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 full profile, you
must add the wasJmsClient-1.1 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.
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.