+

Search Tips   |   Advanced Search

Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources

Message-driven beans can be configured as listeners on a Java EE Connector Architecture (JCA) 1.5 resource adapter, such as the default messaging provider or the IBM MQ messaging provider in WebSphere Application Server.

This task assumes that we have an EAR file containing an enterprise application, developed as a message-driven bean, that can be deployed in WAS.

We can continue to deploy message-driven beans against a listener port. We might want to do this for compatibility with existing message-driven bean applications. However, listener ports are stabilized, and we should plan to migrate all the message-driven beans to use JCA 1.5-compliant or 1.6-compliant resources.

We deploy message-driven beans against JCA 1.5-compliant resources, and configure the resources as deployment descriptor attributes and (for EJB 3) as annotations.


Tasks

  1. For each message-driven bean in the application, create a J2C activation specification. See Configure an activation specification for the default messaging provider or Create an activation specification for the IBM MQ messaging provider.

  2. For each message-driven bean in the application, configure the J2C deployment attributes.

  3. Use the WAS administrative console to install the application.


Subtopics


Related:

  • Message-driven beans - automatic message retrieval
  • Designing an enterprise application to use message-driven beans
  • Developing an enterprise application to use message-driven beans
  • Deploy an enterprise application to use message-driven beans with listener ports
  • Configure security for message-driven beans that use activation specifications
  • Deploy and administering enterprise applications
  • Install enterprise application files with the console