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.

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_single
File name: twlp_msg_single.html

Enabling JMS messaging for a single Liberty profile server

Subtopics