Bind listeners for message-driven beans settings
To specify bindings for message-driven beans in the application or module.
To view this admin console panel, click...
Applications | Application Types | WebSphere enterprise apps | 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 spec JNDI name.
Provide a listener port name if the application uses any of the following JMS providers:
- V5 default messaging provider
- WebSphere MQ messaging provider
- Generic messaging provider
Provide an activation spec JNDI name if the 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 spec JNDI names results in the following errors:
- If neither a listener port name or an activation spec 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 we 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:
- In the list of mappings, select the Select check box beside each EJB module that you want mapped to a particular binding.
- Expand Apply Multiple Mappings.
- Specify a listener port name or select a target resource JNDI name for an activation specification.
- If 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 spec admin object.
- Target resource JNDI Name
- Specify the target resource JNDI name when mapping a message-driven bean to an activation specification.
- ActivationSpec authentication alias
- Specify an authentication alias 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 spec admin object.
- Click Apply.
- Click OK or Next.
- EJB module
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
Type of message-driven bean.
- Bindings
Listener port name or an activation spec JNDI name for the message-driven bean. When a message-driven enterprise bean is bound to an activation spec JNDI name we 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
Application bindings
Related tasks
Deploy an enterprise application to use message-driven beans with listener ports
Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources
Install enterprise application files with the console