To enable JMS messaging on multiple servers, you must configure the wasJmsClient-1.1 feature on a different Liberty profile server.
<featureManager>
<feature>wasJmsClient-1.1</feature>
<feature>jndi-1.0</feature>
</featureManager>
<jmsQueueConnectionFactory jndiName="myQCF" connectionManagerRef="ConMgr4">
<properties.wasJms
remoteServerAddress="meserver.ibm.com:7276:BootstrapBasicMessaging" />
</jmsQueueConnectionFactory>
<connectionManager id="ConMgr4" maxPoolSize="2"/>
<jmsQueue jndiName="myQ">
<properties.wasJms queueName="libertyQ" />
</jmsQueue>
remoteServerAddress="hostname:port:mode"
where
the hostname is the name of the host where the
messaging engine is running; port is the JMS inbound
port that is configured at the server side; and mode is BootstrapBasicMessaging if
SSL is not used, and BootStrapSecureMessaging if
SSL is used.If the <remoteServerAddress> is not specified, then the JMS application tries to connect to a local messaging engine by default in the same Liberty profile.
<featureManager>
<feature>wasJmsClient-1.1</feature>
<feature>jndi-1.0</feature>
</featureManager>
<wasJmsOutbound id=”CustomChain”/>
<jmsQueueConnectionFactory jndiName="myQCF" connectionManagerRef="ConMgr4">
<properties.wasJms
remoteServerAddress="meserver.ibm.com:7276: CustomChain" />
</jmsQueueConnectionFactory>
<connectionManager id="ConMgr4" maxPoolSize="2"/>
<featureManager>
<feature>wasJmsClient-1.1</feature>
<feature>jndi-1.0</feature>
</featureManager>
<wasJmsOutbound id=”CustomChainSecured” useSSL=”true”/>
<jmsQueueConnectionFactory jndiName="myQCF" connectionManagerRef="ConMgr4">
<properties.wasJms
remoteServerAddress="meserver.ibm.com:7276: CustomChainSecured" />
</jmsQueueConnectionFactory>
<connectionManager id="ConMgr4" maxPoolSize="2"/>