JMS 2.0 Client for Message Server

The wasJmsClient-2.0 feature provides applications with access to the message queues that are hosted on WebSphere Application Server through the JMS 2.0 API. This feature supersedes wasJmsClient-1.1. The wasJmsClient-2.0 feature is compliant with JMS 2.0 specifications and is supported only on JDK 7 or later. It enables access to the messaging engine that is enabled through the wasJmsServer feature, and also to the service integration bus that is hosted on a full profile server.

Enabling this feature

To enable the JMS 2.0 Client for Message Server feature, add the following element declaration inside the featureManager element in your server.xml file:
<feature>wasJmsClient-2.0</feature>

Supported Java™ Versions

  • JavaSE-1.7
  • JavaSE-1.8

Developing a feature that depends on this feature

If you are developing a feature that depends on the JMS 2.0 Client for Message Server feature, include the following item in the Subsystem-Content header in the feature manifest file for your new feature:
com.ibm.websphere.appserver.wasJmsClient-2.0; type="osgi.subsystem.feature"

Standard API packages provided by this feature

  • javax.jms

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: Saturday, 3 December 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rwlp_feature_wasJmsClient-2.0
File name: rwlp_feature_wasJmsClient-2.0.html