WAS v8.5 > WebSphere applications > Service integration > Bus destinations > Message pointsRemote message points
A remote message point is a messaging engine runtime view of any message point associated with a remote messaging engine. Remote message points are dynamically created and destroyed when they are required by the bus; we do not have to configure them explicitly.
Message points provide a physical location to reliably store messages. In a bus containing many messaging engines, message points can be defined on a subset of the messaging engines in that bus. However, an application can attach to any messaging engine in the bus, and can therefore produce or consume messages to or from destinations that do not have a suitable message point on the messaging engine to which the application is attached.
When an application produces messages, the messages must be moved from the messaging engine for the application to a messaging engine with a suitable message point, and vice versa when an application consumes messages. Remote message points provide a reliable mechanism to move these messages from one messaging engine to another; the remote message points maintain information required to ensure messages are delivered correctly according to the messages' reliability.
Where necessary, messages are queued on a remote message point while awaiting delivery to the intended message point. This runtime information can be monitored and, where appropriate, managed by an administrator.
Each remote message point that exists on a messaging engine has a corresponding representation on the messaging engine that owns the message point.
Subtopics
- Message production and consumption using remote message points
When an application produces or consumes messages to or from a messaging engine not the same as the messaging engine to which the application is connected, remote message points are used to manage the flow of messages between the messaging engines.- Point-to-point messaging example using remote queue points
When a producing or consuming application is remote from its destination, remote queue points are used to manage the flow of messages between the messaging engine where the destination is located, and the messaging engine to which the application is attached.- Publish/subscribe messaging example using remote publication points
When a publishing or subscribing application is remote from its destination, remote publication points are used to manage the flow of messages between the messaging engine where the destination is located, and the messaging engine the application is attached.
Related information:
Inbound messages [Collection]
Message requests [Collection]