Configuring the server for enabling JMS messaging between multiple Liberty servers

To enable JMS messaging on multiple servers, you must configure the wasJmsServer-1.0 feature on a different Liberty server.

Procedure

On the Liberty server that is hosting the messaging engine, enable the wasJmsServer-1.0 feature to initialize the messaging engine to accept the incoming requests.
```
<featureManager>
	<feature>wasJmsServer-1.0</feature>
</featureManager>

<messagingEngine>
    <queue id="libertyQ"/>
</messagingEngine>
```
Optional: Configure additional properties.
The messaging engine listens on port 7276 (unsecured) and 7286 (secured) by default. If you want to bind the messaging engine to a different port, you must use the <wasJmsEndpoint> element.
```
<featureManager>
	<feature>wasJmsServer-1.0</feature>
</featureManager>

<wasJmsEndpoint 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.
Optional: You can make the wasJmsServer-1.0 feature work in a secure mode. For more information, see Enabling secure JMS messaging for Liberty.
Optional: You can secure JMS communications by using SSL. For more information, see Securing JMS communications in Liberty by using SSL.

For a detailed information about secure communications, see Securing communications with Liberty.

The messaging engine is configured on the Liberty server.