Enabling the JMS application on Liberty to connect to the service integration bus

You can configure the JMS application that is running in Liberty to connect to the service integration bus.

Procedure

To enable the JMS application to connect to the service integration bus that is running on the WebSphere® Application Server traditional server, add the wasJmsClient-2.0 feature in the server.xml file. If you want to perform a JNDI lookup, then you must also add the jndi-1.0 feature.

<featureManager>
     <feature>wasJmsClient-2.0</feature>
     <feature>jndi-1.0</feature>
</featureManager

<jmsQueueConnectionFactory jndiName="jndi_JMS_BASE_QCF">
     <properties.wasJms
          busName="Bus1"
          remoteServerAddress="localhost:7276:BootStrapBasicMessaging" 
          targetTransportChain="InboundBasicMessaging"/>
</jmsQueueConnectionFactory>

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

Note: The <remoteServerAddress> must specify the host and port of the server on which the messaging engine is running instead of specifying a bootstrap server.

What to do next

Important: If you are using SSL communication in Liberty, then refer to Securing JMS communications in Liberty by using SSL to ensure your security configuration is correct.