Bind listeners for message-driven beans settings

Use this panel to specify bindings for message-driven beans in your application or module.

To view this administrative console panel, click Applications > Enterprise Applications > application_name > Message Driven Bean listener bindings. This panel is the same as the Bind listeners for message-driven beans panel on the application installation and update wizards.

Each message-driven bean must be bound to a listener port name or to an activation specification Java Naming and Directory Interface (JNDI) name.

Provide a listener port name if your application uses any of the following Java Message Service (JMS) providers:

• V5 default messaging

• WebSphere MQ

• Generic

Provide an activation specification JNDI name if your application's resources are configured using the default messaging provider or any generic J2C resource adapter that supports inbound messaging.

Not providing valid listener port names or activation specification JNDI names results in the following errors:

• If neither a listener port name or an activation specification JNDI name is specified for a message driven bean, then a validation error is displayed after you click Finish on the Summary panel.

• If the module containing the message-driven bean is deployed on a 5.x deployment target and a listener port is not specified, then a validation error is displayed after you click Next.

• If multiple message driven beans are linked to the same destination, specify the same destination JNDI name for each message driven bean. If you specify different destination JNDI names, a validation error is displayed and all JNDI specifications after the first one are ignored.

To apply binding changes to multiple mappings:

1. In the list of mappings, select the Select check box beside each EJB module that you want mapped to a particular binding.

2. Expand Apply Multiple Mappings.

3. Specify a listener port name or select a target resource JNDI name for an activation specification.

4. If you are defining a binding for an activation specification, optionally specify the following:

   Destination JNDI name

   For resource adapters that support JMS, specify javax.jms.Destinations so the resource adapter can service messages from the JMS destination. A destination JNDI name set as part of application deployment take precedence over properties set on an activation specification administrative object.

   ActivationSpec authentication alias

   Specify an authentication alias that is used to access the user name and password that are set on the configured J2C activation specification. Authentication alias properties set as part of application deployment take precedence over properties set on an activation specification administrative object.

5. Click Apply.

6. Click OK.

EJB module

Specifies the name of the module that contains the enterprise bean.

EJB

Specifies name of an enterprise bean in the application.

URI

Location of the module relative to the root of the application EAR file.

Messaging type

Timeype of message-driven bean.

Bindings

Specifies a listener port name or an activation specification JNDI name for the message-driven bean. When a message-driven enterprise bean is bound to an activation specification JNDI name you can also specify the destination JNDI name and the authentication alias.

Bindings specify JNDI names for the referenceable and referenced artifacts in an application. An example JNDI name for a listener port to be used by a Store application might be StoreMdbListener. The binding definition is stored in IBM bindings files such as ibm-ejb-jar-bnd.xmi.

Related concepts

Related tasks

Reference topic