Enabling JMS messaging for a single Liberty 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-2.0
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.
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.