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 IBM MQ messaging provider in WebSphere® Application Server.

Before you begin

This task assumes that you have an EAR file that contains an enterprise application, developed as a message-driven bean, that can be deployed in WebSphere Application Server.

Note: You can continue to deploy message-driven beans against a listener port. You 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 your message-driven beans to use JCA 1.5-compliant or 1.6-compliant resources.

About this task

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.

Procedure

  1. For each message-driven bean in the application, create a J2C activation specification.

    For more information, see Configuring an activation specification for the default messaging provider or Creating an activation specification for the IBM MQ messaging provider.

  2. For each message-driven bean in the application, configure the J2C deployment attributes, as described in Configuring deployment attributes for a message-driven bean against JCA 1.5-compliant resources.
  3. Use the WebSphere Application Server administrative console to install the application.

指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:16
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=tmb_depap
檔名:tmb_depap.html