+

Search Tips   |   Advanced Search

Remote mediation points [Collection]

The remote mediation points that are producing messages to mediation points on remote messaging engines.

To view this page in the console, click the following path:

Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> Runtime > [Remote message points] Remote mediation points.

To browse or change the properties of a listed item, select its name in the list.

To act on one or more of the listed items, select the check boxes next to the names of the items to act on, then use the buttons provided.

To change which entries are listed, or to change the level of detail displayed for those entries, use the Filter settings.

A remote mediation point represents a remote proxy for a mediation point that exists at a remote messaging engine to which messages are sent by an application or client connected to this messaging engine. The remote mediation point manages an outbound message stream to the mediation point at the remote messaging engine.

Identifier

The remote mediation point identifier.

Messaging engine

The remote messaging engine where this mediation point is localized.

Current outbound messages

The current number of outbound messages queued to the mediation point.

Outbound messages sent

The total number of messages sent to the mediation point since the messaging engine started.


Buttons

Button Description
Delete all messages Delete all messages from the outbound message stream of the selected remote queue point. Messages in "Pending Acknowledgment" state might already have been received at the remote queue point. We cannot delete messages in "Committing" state; first commit their transactions.
Move all messages Move all messages from the outbound message stream of the selected remote queue point to the exception destination configured for the destination. Messages in "Pending Acknowledgment" state might already have been received at the remote queue point. Moving these messages to the exception destination results in two copies of the message in the bus. We cannot move messages in "Committing" state; first commit their transactions.