A single message queue can be the interface for all RepConnector replication events. In this case, the business process must be designed so that it manages all possible replication event types it needs to process. For example, a database event delivered in a RepConnector dbStream can be a tranBegin, tranCommit, tranAbort, insert, update, delete, execBegin, execEnd, or execSQL event.
To process the incoming replication events, you must know:
The types of events delivered to each message queue based on the configuration of all of the RepConnector instances
The database replication activity for each RepConnector, based on the application design
All the RepConnector events that each Unwired Orchestrator process requires
The scope of the business process, which may require knowledge of insert, update, and delete in to fulfill the required processing
Figure 9-1 shows RepConnector-to-Unwired Orchestrator single queue management, in which the flow of a message is delivered to a queue by RepConnector, and picked up by Unwired Orchestrator.
This technique simplifies the replication environment
but increases the complexity of the Unwired Orchestrator business
process, because the business process must handle different message
types. The process designer may want to distribute these events
using multiple message queues. In this case, a RepConnector runs
for each queue.
