JCA activation specifications and service integration

A Java EE Connector Architecture (JCA) 1.5 activation specification enables a message-driven bean to communicate with the default messaging provider.

We create a JMS activation specification to use a message-driven bean to communicate with the default messaging provider through Java EE Connector Architecture (JCA) 1.5. JCA provides Java connectivity between application servers such as WebSphere Application Server, and enterprise information systems. It provides a standardized way of integrating JMS providers with Java EE application servers, and provides a framework for exchanging data with enterprise systems, where data is transferred in the form of messages.

One or more message-driven beans can share a single JMS activation specification.

All the activation specification configuration properties apart from Name, JNDI name, Destination JNDI name, and Authentication alias are overridden by appropriately named activation-configuration properties in the deployment descriptor of an associated EJB 2.1 or later message-driven bean. For an EJB 2.0 message-driven bean, the Destination type, Subscription durability, Acknowledge mode and Message selector properties are overridden by the corresponding elements in the deployment descriptor. For either type of bean the Destination JNDI name property can be overridden by a value specified in the message-driven bean bindings.

Related concepts

J2C activation specification configuration and use

Related tasks

Configure an activation specification for the default messaging provider

createSIBJMSActivationSpec command

deleteSIBJMSActivationSpec command

listSIBJMSActivationSpecs command

modifySIBJMSActivationSpec command

showSIBJMSActivationSpec command