To enable JMS messaging on multiple servers, you must configure the wasJmsServer-1.0 feature on a different Liberty profile server.
<featureManager>
<feature>wasJmsServer-1.0</feature>
</featureManager>
<messagingEngine>
<queue id="libertyQ"/>
</messagingEngine>
<featureManager>
<feature>wasJmsServer-1.0</feature>
</featureManager>
<wasJmsEndpoint id="InboundJmsCommsEndpoint" host="*" wasJmsPort="9011" wasJmsSSLPort="9100" />
<messagingEngine>
<queue id="libertyQ"/>
</messagingEngine>
The <wasJmsEndpoint>
element defines an inbound JMS communication endpoint, to which the
JMS client applications can connect by using the <wasJmsPort> element
if SSL is not being used, and by using the <wasJmsSSLPort> element
if SSL is being used. The port number is the one that you specified
in the <remoteAddressServer> property on the client.In the previous code example, the messaging engine listens on port 9011 (unsecured) and port 9100 (secured) for accepting the incoming requests.
For a detailed information about secure communications, see Securing communications with the Liberty profile.
The messaging engine is configured on the Liberty profile server.