WAS v8.5 > Reference > Sets

Bind listeners for message-driven beans settings page

Use this page to specify bindings for message-driven beans in the application or module.

To view this dmgr console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Message Driven Bean listener bindings. This page is the same as the Bind listeners for message-driven beans page on the application installation and update wizards.

Each message-driven bean must be bound to a listener port name or to an activation specification JNDI name.

Provide a listener port name if the application uses either of the following JMS providers:

• WebSphere MQ messaging provider
• Generic messaging provider

Provide an activation specification 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 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 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:

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

2. Expand Apply Multiple Mappings.

3. Complete one of the following steps:

   • Specify a listener port name.

   • Select a target resource JNDI name for an activation specification. Optionally specify:

     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 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.

4. Click Apply.

5. Click OK or Next.

Module

Name of the module containing the enterprise bean.

Bean

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.

Listener Bindings

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 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.

For IBM extension and binding files, the .xmi or .xml file name extension is different depending on whether you are using a pre-Java EE 5 application or module or a Java EE 5 or later application or module. An IBM extension or binding file is named ibm-*-ext.xmi or ibm-*-bnd.xmi where * is the type of extension or binding file such as app, application, ejb-jar, or web. The following conditions apply:

• For apps and modules that use a Java EE version prior to version 5, the file extension must be .xmi.

• For apps and modules that use Java EE 5 or later, the file extension must be .xml. If .xmi files are included with the application or module, the product ignores the .xmi files.

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. sptcfg

Related concepts:

Application bindings

Related

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

+

Search Tips   |   Advanced Search