Configure JMS activation specifications

We can configure JMS activation specification instances for JMS message listeners provided by resource adapters that comply with the Java EE Connector Architecture (JCA) specification.

To add JCA support for Liberty, edit server.xml using either the Source view of the Server configuration editor of the WebSphere Application Server Developer Tools for Eclipse, or some other text editor. Editing portions of the configuration for connection factories, administrative objects, activation specifications, and resource adapters in the Design view is not supported in the Beta.

Configure one or more JMS activation specification instances. When configuring the activation specification instances, supply a properties subelement, even if we do not want to override any configuration properties, to associate the jmsActivationSpec element with a JMS message listener provided by a particular resource adapter. The properties subelement always follows the pattern properties, <rar_identifier> for JMS activation specifications. The following example configures two instances of JMS activation specifications:

<jmsActivationSpec id="app1/module1/MyJMSMessageDrivenBean">
 <properties.MyAdapter destinationRef="topic1"/>
</jmsActivationSpec>

<jmsActivationSpec id="app1/module1/AnotherJMSMessageDrivenBean">
 <containerAuthData user="user1" password="{xor}Lz4sLCgwLTtu"/>
 <properties.MyAdapter destinationRef="queue1"/>
</jmsActivationSpec>

Note that this topic assumes that a resource adapter with a unique identifier of MyAdapter has already been configured in the server and that the jms-1.1 and mdb-3.1 features have been enabled, see topic Configure resource adapters for further details.

Limitation: Editing the properties of the resource adapter configuration for connection factories, administrative objects, activation specifications, and resource adapters in the Design view of WebSphere Development Tools (WDT) is not supported.