Deploying 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 WebSphere 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 WebSphere Application Server.
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 you should plan to migrate all the message-driven beans to use JCA 1.5-compliant or 1.6-compliant resources.
You deploy message-driven beans against JCA 1.5-compliant resources, and configure the resources as deployment descriptor attributes and (for EJB 3) as annotations.
- For each message-driven bean in the application, create a J2C activation specification.
For more information, see Configure an activation specification for the default messaging provider or Create an activation specification for the WebSphere MQ messaging provider.
- For each message-driven bean in the application, configure the J2C deployment attributes, as described in Configure deployment attributes for a message-driven bean against JCA 1.5-compliant resources.
- Use the WAS administrative console to install the application.
Subtopics
- Configure deployment attributes for a message-driven bean against JCA 1.5-compliant resources
We can configure the message-driven bean deployment attributes for a Java EE Connector Architecture (JCA) 1.5-compliant enterprise application, to override the deployment attributes defined within the application EAR file.
- Configure servant regions for message-driven beans with JCA version 1.5 resource adapters
For any message-driven beans (MDBs) that are not driven by asynchronous messaging or the IMS Connect for Java (IC4J) resource adapter, you must redefine the servant region for those beans that are connected to JEE (Java EE) Connector Architecture (JCA) Version 1.5 resource adapters that support inbound message processing.
Related concepts
Message-driven beans - automatic message retrieval
Related tasks
Design an enterprise application to use message-driven beans Develop 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