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 version 6
must be deployed against a Java Connector
Architecture (JCA) 1.5 resource adapter instead of a listener port.
Procedure
- Open the EJB project in the Enterprise Explorer.
- Double-click the EJB project Deployment Descriptor file
in the Enterprise Explorer. The EJB deployment descriptor editor opens.
- Click the Bean tab to open the Bean page.
- For each EJB 2.1 message-driven bean in the EJB project,
do the following:
- Select the EJB 2.1 message-driven bean in the list of
beans on the left side of the Bean page.
- Under the heading WebSphere Bindings,
select the JCA Adapter button.
- Specify bindings deployment properties:
- 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 WebSphere Application
Server.
- 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.
- Destination JNDI name.
Type the JNDI
name that the message-driven bean uses to look up the JMS destination
in the JNDI name space.
- Save the changes and close the Deployment Descriptor editor.