Configuring an EJB 2.1 message-driven bean to use a JCA adapter

Message-driven beans that have been migrated from Enterprise Java™ Bean (EJB) 2.0 to the EJB 2.1 specification level and are deployed to WebSphere® Application Server v6 must be deployed against a Java Connector Architecture (JCA) 1.5 resource adapter instead of a listener port.

The following steps describe how to change the deployment descriptor of EJB 2.1 message-driven beans to use a JCA adapter:

1. Open the EJB project in the Project Explorer.

2. Double-click the EJB project's

   Deployment Descriptor file in the Project Explorer. The EJB deployment descriptor editor opens.

3. Click the

   Bean tab to open the

   Bean page.

4. For each EJB 2.1 message-driven bean in the EJB project, do the following:

   1. Select the EJB 2.1 message-driven bean in the list of beans on the left-hand side of the Bean page.

   2. Under the heading

      WebSphere Bindings, select the

      JCA Adapter button.

   3. Specify bindings deployment properties:

      1. ActivationSpec JNDI name.

         Type the JNDI name of the J2C activation specification that is to be used to deploy this message-driven bean. This name must match the name of a J2C activation specification that you define to WAS.

      2. ActivationSpec Authorization Alias.

         The name of a J2C authentication alias used for authentication of connections to the JCA resource adapter. A J2C authentication alias specifies the user ID and password that is used to authenticate the creation of a new connection to the JCA resource adapter.

      3. Destination JNDI name.

         Type the JNDI name that the message-driven bean uses to look up the JMS destination in the JNDI name space.

5. Save the changes and close the Deployment Descriptor editor.

 

Related reference

J2EE 1.3 to 1.4 specification level migration

Enterprise JavaBean projects (EJB 2.0 to EJB 2.1)

Enterprise JavaBean projects (EJB 2.0 to EJB 2.1)

---