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:
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:
To apply binding changes to multiple mappings:
Specifies the name of the module that contains the enterprise bean.
Specifies name of an enterprise bean in the application.
Specifies the location of the module relative to the root of the application EAR file.
Specifies the type of message-driven bean.
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.