Bind listeners for message-driven beans settings
Use this page to specify bindings for message-driven beans in your application or module.
To view this administrative console page, click Bind listeners for message-driven beans page on the application installation and update wizards.
. This page is the same as theEach 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 either of the following Java Message Service (JMS) providers:
- WebSphere® MQ messaging provider
- Generic messaging provider
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 page.
- 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:
- In the list of mappings, select the Select check box for each EJB module that you want mapped to a particular binding.
- Expand Apply Multiple Mappings.
- Complete one of the following steps:
- Specify a listener port name.
- Select a target resource JNDI name for an activation specification. Optionally specify the
following parameters:
- 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.
- Click Apply.
- Click OK or Next.
Module
Specifies the name of the module that contains the enterprise bean.
Bean
Specifies name of an enterprise bean in the application.
URI
Specifies the location of the module relative to the root of the application EAR file.
Messaging Type
Specifies the type of message-driven bean.
Listener 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.
Store
application might be
StoreMdbListener
. The binding definition is stored in IBM® bindings files such as ibm-ejb-jar-bnd.xmi. However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.
The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions.