Enabling JMS messaging between two Liberty profile servers

In a typical production scenario, users might want to run the wasJmsServer-1.0 and the JMS applications on separate servers to distribute the workload. In such scenarios, you can configure the wasJmsClient-1.1 Liberty feature on one server, which acts as the client, and configure the wasJmsServer-1.0 feature on a different server. The JMS applications that are deployed on a remote server always use TCP/IP to connect to the messaging engine that is running on a different server. You can also configure the wasJmsSecurity-1.0 feature to make your applications to connect securely to the messaging engine, and configure the ssl-1.0 feature to enable the SSL communication between the two Liberty servers.

Task topic

Terms and conditions for information centers | Feedback

Timestamp icon

Last updated: Wednesday, 22 May 2013
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=twlp_msg_multi
File name: twlp_msg_multi.html

Enabling JMS messaging between two Liberty profile servers

Subtopics