JMS 1.1 Client for Message Server
This feature provides applications with access to message queues hosted on WebSphere Application Server through the JMS 1.1 API. It enables access both to the messaging engine enabled via the wasJmsServer feature, and to a service integration bus hosted in a full profile server.
Enabling this feature
To enable the JMS 1.1 Client for Message Server feature, add the following element declaration inside the featureManager element in your
server.xml file:
<feature>wasJmsClient-1.1</feature>
Supported Java™ Versions
- JavaSE-1.6
- 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 1.1 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-1.1; type="osgi.subsystem.feature"
Standard API packages provided by this feature
- javax.jms
Feature configuration elements
You can use the following elements in your server.xml file to configure the JMS 1.1 Client for Message Server feature:
- activationSpec
- adminObject
- application
- applicationManager
- applicationMonitor
- authData
- channelfw
- classloading
- connectionFactory
- connectionManager
- javaPermission
- jmsActivationSpec
- jmsConnectionFactory
- jmsDestination
- jmsQueue
- jmsQueueConnectionFactory
- jmsTopic
- jmsTopicConnectionFactory
- library
- resourceAdapter
- tcpOptions
- transaction
- wasJmsOutbound