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