Enabling JMS messaging between two Liberty 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-2.0
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
transportSecurity-1.0
feature to enable the TLS communication between the two Liberty servers.
Before you begin
wasJmsClient-2.0
feature supports the features of both JMS 1.1 and JMS 2.0 specifications. However, you can choose to use the wasJmsClient-1.1
feature if you want to use only the features that are compliant with JMS 1.1 specification.