The following are requirements for implementing database event management.
To build and run business processes that use database event management, Unwired Orchestrator with Database Event Management must be licensed and installed and an existing implementation of Replication Server must be available in your environment.
All database events that are to be managed using an Unwired Orchestrator business process must be identified. Examples of database events include: tranBegin, trancommit, tranAbort, insert, delete, execBegin, execEnd, and execSQL.
Verify that database events do not include data that is recursive. Recursive Element References are not supported by Unwired Orchestrator.
A least one message queue is required to deliver database events to business processes. Tibco, WebSphere MQ, and JMS messaging are supported by both RepConnector and Unwired Orchestrator.
You must determine whether one queue or multiple queues will be used to move database events to Unwired Orchestrator.
A single queue can be used for multiple replication events types, however the business process must be designed so that it recognizes all of the possible replication event types it needs to process. Using a single queue simplifies the replication environment but increases the complexity of the business process because the business process must handle different message types.
Multiple queues can be used to move database events to Unwired Orchestrator; each queue must be associated with a separate RepConnector instance. The replication environment must be designed so that database events are replicated to specific queues. Each queue is then associated with a business process. Using multiple queues increases the complexity of the replication environment, but simplifies the business process design because each business process has a limited scope of expected events.
Installed with Unwired Orchestrator with Database Event Management, the RepConnector component is configured to listen for database events from Replication Server. RepConnector transforms each database event to an XML document, then uses a message transport to push the events to Unwired Orchestrator.
To get started with configuring Sybase RepConnector Manager from Unwired Orchestrator, do one of the following:
Open the RepConnection Manager view. From any perspective, select Window > Show View > Other. Click to expand the Sybase RepConnector Manager node, select Sybase RepConnector Manager, and click OK.
Go to the RepConnector Welcome screen by selecting Help > Welcome and choosing the Sybase RepConnector option. Follow the steps outlined on the welcome page.
See the RepConnector Configuration and User's Guide for detailed information. The steps required to configure RepConnector for Unwired Orchestrator are covered in chapters 5 and 6.
Unwired Orchestrator with Database Event Management must be licensed and installed.
Database Event Management is implemented in a business process using a Replication Event Service. A Replication Event Service is uni-directional, handling only inbound replication events. Outbound events must be implemented as a database or messaging service.
Unwired Orchestrator uses XML formats that are imported from the RepConnector XSD, dbeventstream.xsd. The XSD is automatically imported to a project when the project is defined. The structure of dbeventstream.xsd can be viewed in the Schema Editor.
If you have imported a project that was originally designed using Integration Orchestrator 4.0.x and want to add replication event services to the project in Unwired Orchestrator 4.3, the dbeventstream.xsd must be manually imported into the project. The dbeventstream.xsd is located in <server install directory>\IOdsgntime-4_3\eclipse\plugins\com.sybase.ebd.eai.internal.tools_4.3.0\foldertemplates\Unzipped\schemas.
Consider the following when designing the business processes to handle database events:
Using Unwired Orchestrator to poll the database. A business process can be designed to poll the source database looking for insert entries. New inserts can be queried to check a processed/sent flag in the table to indicate the record is new, thus ensuring that the query returns only new inserts. Each record must be processed individually and sent to the target database.
The polling must be repeated periodically and the business process must be designed to manage errors
Handle multiple rows of data
Nested loops are required to process multiple sets inside of the polling loops
Polling must be started by putting a dummy message on the queue
Add activities to the business process to stop the polling and to stop the process; stopping the instance stops the process and the process resumes again where it left off when the instance is started again
Using Unwired Orchestrator to handle re-formatting source data and send it to the target database.
After these requirements have been completed, you are ready to Configure Database Event Management.
Planning for Database Event Management
