Subtopics
Enabling JMS messaging for a single Liberty profile server
In a development environment, if you want to run the JMS application and JMS messaging run time components on the same server, you can configure the wasJmsServer-1.0 and wasJmsClient-1.1 features on the same server. In this scenario, the application is deployed on the same server where the messaging engine and the JMS resources exist. When the application and the messaging engine are deployed on the same server, the application can connect to the messaging engine either over TCP/IP or in-memory API function calls. You can also configure the wasJmsSecurity-1.0 feature to enable secure connection of the application to the messaging engine.- 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. - Enabling secure JMS messaging for the Liberty profile
Use the wasJmsSecurity-1.0 Liberty feature to make the wasJmsServer-1.0 feature work in a secure mode. Securing the messaging resources ensures that only authenticated and authorized users can access the messaging resources such as queues, topics, and messages. - Enabling interoperability between the Liberty profile and WebSphere Application Server full profile
The JMS applications that are deployed within the Liberty profile can connect to the messaging engine that runs in the WebSphere Application Server full profile (that is, service integration bus). Similarly, the JMS applications that are deployed within the WebSphere Application Server full profile can connect to the messaging engine that runs in the Liberty profile. - Securing JMS communications in the Liberty profile by using SSL
You can configure the ssl-1.0 feature to enable secure communication between the two Liberty servers.
Parent topic: End-to-end paths for the Liberty profile
End-to-end paths for the Liberty profileRelated tasks:
Task topic