Application messaging resources
This pane provides an expandable tree view of all the references to messaging resources declared in the deployment descriptors for the current application. As many of the references as possible are resolved to links to the associated configuration panel for the referenced object.
To view this page in the console, click the following path:
Applications -> Application Types -> WebSphere enterprise applications -> application_name -> [Enterprise Java Bean Properties] Default messaging provider references.
Use this panel to inspect the configuration from the application to the queue (destination) to ensure that the configuration is correct.
Using the default messaging provider, a JMS activation specification refers to a JMS destination (JMS Queue or JMS Topic) that in turn points to a service integration bus destination (queue destination or a topic space destination). JMS resources are referenced through JNDI names and service integration resources are referenced through bus and resource identifiers. This panel allows us to review the dependencies within the configuration, making it easier to detect inconsistencies, for example as a result of references being entered incorrectly, or JNDI or resource names being changed or deleted without the associated configuration having been updated.
Problems with the configuration are usually detected in one of two ways:
- An application can no longer send or receive messages.
- A destination becomes full and can no longer receive messages because the existing messages are not being consumed.
This panel can help us find the cause of the problem by giving us a high level view of relevant resources.
For a related view of the applications and JMS resources for a given destination see: Application resources for this destination.
Local Topology tab
Topology properties for this object. These properties detail how this object relates to other objects in the system topology.