| |
Foreign Destinations
Column Display Related Tasks Related Topics
A foreign destination (topic or queue) can be found on a remote server. When this destination is looked up on the local server, a look-up will be performed automatically on the remote JNDI directory, and the object will be returned from that directory.
This page summarizes the foreign destinations that have been created for this domain.
Column Display
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Name The name of this entity, represented in XML as an attribute.
Many of the elements within the JMS module are named entities. All of the named entities encased by a type in the XML file must be unique. This is the identifier used to delineate a particular entity within the JMS module.
This attribute cannot be modified externally from the module (for example, with a deployment plan) because it may be used inside the module referentially.
Changes take effect after you redeploy the module or restart the server.
Local JNDI Name The name that the remote object will be bound to in the local server's JNDI tree. This is the name that should be used to look up the object on the local server.
Changes take effect after you redeploy the module or restart the server.
Remote JNDI Name The name of the remote object that will be looked up in the remote JNDI directory.
Changes take effect after you redeploy the module or restart the server.
|