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 tradicional 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.
Enabling the JMS application on WebSphere Application Server tradicional to connect to Liberty messaging
You can configure JMS applications that are running on the WebSphere Application Server tradicional server to connect to Liberty messaging.
Procedure
To enable JMS applications that are deployed in the WebSphere Application Server tradicional server to connect to Liberty messaging,
configure the Bus name and the ProviderEndPoint in the
WebSphere Application Server tradicional server to specify the host and port
where the Liberty messaging engine is running.
For more information about configuring the bus name in the connection factory in WebSphere Application Server tradicional, see Default messaging provider unified connection factory [Settings].
Note: The JMS resources that are pointing to the Liberty messaging engine must always specify the
Bus name as defaultBus (case sensitive).