Configuring JMS activation specifications

You can configure JMS activation specifications that are provided by resource adapters that comply with the Java™ EE Connector Architecture (JCA) specification.

About this task

You can configure one or more JMS activation specification instances for JMS message listeners that are provided by an installed resource adapter.

Note:

To add JCA support for Liberty, you must edit the server.xml file 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.

Procedure

Configure one or more JMS activation specification instances.

When you configure the activation specification instances, you must supply a properties subelement, even if you do not want to override any configuration properties, to associate the jmsActivationSpec element with a JMS message listener that is 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: 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 Configuring 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.