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.

Before you begin

Before you can run an application client, you must create a client and add a configuration for your client application in the client.xml file. See the Creating a Liberty application client manually topic for examples of how you would create the application client.

Procedure

To run the messaging application on the client, add the javaeeClient-7.0 feature to the client.xml file.
```
<featureManager>
    <feature>javaeeClient-7.0</feature>
</featureManager>
```

Add the connection factory definitions to the client.xml file.

For Point-to-Point domain:


<jmsQueueConnectionFactory jndiName="jndi_JMS_BASE_QCF" connectionManagerRef="ConMgr6">
      <properties.wasJms remoteServerAddress="localhost:7276:BootstrapBasicMessaging" /> 
</jmsQueueConnectionFactory>
<connectionManager id="ConMgr6" maxPoolSize="10"/>

<jmsQueue jndiName="jndi_INPUT_Q">
    <properties.wasJms queueName="QUEUE1" />
</jmsQueue>

For Publish-Subscribe domain:


<jmsTopicConnectionFactory jndiName="eis/tcf">
    <properties.wasJms
    clientID="defaultID" />
</jmsTopicConnectionFactory>

<jmsTopic jndiName="eis/topic1">
    <properties.wasJms topicName="Football" />
</jmsTopic>

The JMS application is ready to run on the Liberty application client container.