JMS 2.0 Client for Message Server
The wasJmsClient-2.0 feature provides applications with access to the message queues 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.
Enable this feature
To enable the JMS 2.0 Client for Message Server feature, add the following element declaration into server.xml, inside the featureManager element:
<feature>wasJmsClient-2.0</feature>
Feature configuration elements
- activationSpec
- adminObject
- application
- applicationManager
- applicationMonitor
- authData
- channelfw
- classloader
- classloading
- connectionFactory
- connectionManager
- javaPermission
- jmsActivationSpec
- jmsConnectionFactory
- jmsDestination
- jmsQueue
- jmsQueueConnectionFactory
- jmsTopic
- jmsTopicConnectionFactory
- kerberos
- library
- resourceAdapter
- tcpOptions
- transaction
- wasJmsOutbound
Standard API packages provided by this feature
- javax.jms
- javax.resource
- javax.resource.cci
- javax.resource.spi
- javax.resource.spi.endpoint
- javax.resource.spi.security
- javax.resource.spi.work
Liberty API packages provided by this feature
- com.ibm.websphere.endpoint
- com.ibm.ws.jca.cm.mbean
Supported Java versions
- JavaSE-1.8
- JavaSE-11.0
- JavaSE-17.0
- JavaSE-21.0
- JavaSE-24.0
Platform Versions
- javaee-7.0
- javaee-8.0
- jakartaee-8.0
Features that enable this feature
Develop a feature that depends on this feature
If we are developing a feature that depends on this feature, include the following item in the Subsystem-Content header in your feature manifest file.
com.ibm.websphere.appserver.wasJmsClient-2.0; type="osgi.subsystem.feature"