AQ Topology

The following describes the AQ topology that supports the Saga framework. This information is available in the DBA_SAGA_PARTICIPANTS dictionary view. For the following example, let us assume that the broker named TestBroker is created on the Broker PDB.

Entity Name	Queue Name	Description
TestBroker	SAGA$_TESTBROKER_INOUT1	This queue represents the In/Out queue for a Saga broker. This queue is connected to other queues using AQ propagation.
TravelAgency	SAGA$_TRAVELAGENCY_IN_Q1	The initiator's IN queue stores incoming participant responses.
	SAGA$_TRAVELAGENCY_OUT_Q1	The initiator's OUT queue stores outgoing request messages.
TACoordinator	SAGA$_TACOORDINATOR_IN_Q1	For notification, use: "plsql://dbms_saga_adm.notify_callback_coordinator" The coordinator's IN queue stores incoming acknowledgements and finalization status messages.
	SAGA$_TACOORDINATOR_OUT_Q1	The coordinator's OUT queue stores outgoing acknowledgments and finalization requests.
Airline	SAGA$_AIRLINE_IN_Q1	The participant's IN queue stores the incoming payload requests and acknowledgments.
	SAGA$_AIRLINE_OUT_Q1	The participant's OUT queue stores the outbound messages bound to both initiators and coordinators.