Configuring a J2C activation specification

J2C activation specifications are part of the configuration of inbound messaging support of a JCA 1.5 resource adapter. A JCA 1.5 resource adapter supports inbound messaging by implementing its own message listener interface. The message listener is the interface that the resource adapter uses to communicate inbound messages to the message endpoint. A message-driven bean is a message endpoint and implements one of the message listener interfaces provided by the resource adapter.

When an application that contains a message-drive bean is deployed, the deployer must select a resource adapter that supports the same type of message listener that the message-driven bean implements. As part of the message-driven bean deployment, the deployer needs to specify the properties to set on the J2C activation specification. Later, during application startup, a J2C activation specification instance is created, and these properties are set and used to activate the endpoint.

The IMSActivationSpec class is the implementation of J2C activation specifications in IMS TM resource adapter. When you deploy a message-driven bean in WebSphere® Application Server, you must select the IMS TM resource adapter, and configure the activation specification by specifying the values for IMSActivationSpec properties that describe the inbound communication from IMS.

If multiple data stores and multiple tpipes are involved, the IMS TM resource adapter thread pool might quickly exhaust and the callout processing might stall. In this case, you might want to configure the WebSphere Application Server to add your own thread pool. After the thread pool is added, reference the thread pool in the Thread pool alias field for the IMS TM resource adapter.