Message destination reference settings
If the application uses message-driven beans, use this page to specify the JNDI name of the J2C administered object to bind the message destination reference to the message-driven beans. We must map each message destination reference defined in the application to an administered object.
From the admin console, click...
Applications > Application Types > WebSphere enterprise applications > application_name > Message destination references.
This page is the same as the Bind message destination references to administered objects page on the application installation and update wizards.
If the message destination reference is from an EJB 3.0 or later module, then the JNDI name is optional and the run time provides a container default value.
If multiple message destination references link to the same message destination, only one JNDI name is collected. When a message destination reference links to the same message destination as a message-driven bean and the destination JNDI name has been collected already, the destination JNDI name for the message destination reference is not collected.
To apply binding changes to multiple mappings:
- In the list of mappings, select the Select check box for each EJB module that we want mapped to a particular binding.
- Expand Apply Multiple Mappings.
- Complete one of the following steps:
- Specify a message destination name.
- Select a target resource JNDI name for a message destination.
- Click Apply.
- Click OK or Next.
Module
Name of the module containing the bean.
Bean
Specifies name of a bean in the application.
URI
Location of the module relative to the root of the EAR file.
Message destination object
Message destination object.
Type
Type of object.
Target Resource JNDI Name
JNDI name of the bean.
This is a data entry field. To change the JNDI name bound to this bean, type the new name in this field.
Related:
Application bindings Install enterprise application files with the console