The messagingClient-3.0 feature provides applications with access to the message queues that are hosted on WebSphere Application Server through the Jakarta Messaging 3.0 API. The messagingClient-3.0 feature is compliant with Jakarta Messaging 3.0 specifications. It enables access to the messaging engine that is enabled through the messagingServer-3.0 feature, and also to the Service Integration Bus that is hosted on a full profile server.
Enabling this feature
To enable the Messaging Server 3.0 Client feature, add the following element declaration into your server.xml
file, inside the featureManager
element:
<feature>messagingClient-3.0</feature>
Feature configuration elements
Standard API packages provided by this feature
-
jakarta.jms
-
jakarta.resource
-
jakarta.resource.cci
-
jakarta.resource.spi
-
jakarta.resource.spi.endpoint
-
jakarta.resource.spi.security
-
jakarta.resource.spi.work
Liberty API packages provided by this feature
-
com.ibm.websphere.endpoint
-
com.ibm.ws.jca.cm.mbean
Features that this feature enables
Supported Java versions
-
JavaSE-1.8
-
JavaSE-11.0
-
JavaSE-17.0
-
JavaSE-21.0
-
JavaSE-22.0
Features that enable this feature
Developing a feature that depends on this feature
If you are developing a feature that depends on this feature, include the following item in the Subsystem-Content
header in your feature manifest file.
io.openliberty.messagingClient-3.0; type="osgi.subsystem.feature"