| Previous | Next |  | Contents | Index | Glossary

## Synchronizing Systems

Synchronizing systems means replicating all the Event Manager objects that are defined on the source system to the target system. You can use the Synchronize Event Systems event to synchronize systems with each other.

#### To Synchronize Systems

1. Sign up the source and target systems with each other. See: Signing Up Systems.

2. On the source system, modify the predefined subscription to the Seed Event Group with the Local source type.

- Specify the inbound agent on the target system that you want to receive the event message, or specify a workflow process that sends the event message to the target system.

> Note: If you want to send the event message to more than one target system, you can either define additional subscriptions or specify a workflow process that sends the event message to multiple systems.

- Enable the subscription.

> Note: If you do not have access to the Oracle Workflow installation on the source system, ask the workflow administrator for that system to perform this step.

3. On the target system, enable the predefined subscription to the Seed Event Group with the External source type.

> Note: If you do not have access to the Oracle Workflow installation on the target system, ask the workflow administrator for that system to perform this step.

4. On the source system, raise the Synchronize Event Systems event (oracle.apps.wf.event.all.sync) using the Raise Event web page. Enter a unique event key, but leave the Event Data field blank. See: Raising Events

> Note: If you do not have access to the Oracle Workflow installation on the source system, ask the workflow administrator for that system to perform this step.

When the Synchronize Event Systems event is raised on the source system, it triggers the subscription to the Seed Event Group with the Local source type. The Event Manager generates the event message, which contains the definitions of all the Event Manager objects on the local system, including events, event groups, systems, agents, and subscriptions. Then the event message is sent to the specified inbound agent on the target system, or to the specified workflow process that sends the event message to the target system.

When the Synchronize Event Systems event is received on the target system, it triggers the subscription to the Seed Event Group with the External source type. Oracle Workflow loads the object definitions from the event message into the Event Manager on the target system, creating new definitions or updating existing definitions as necessary.

#### Automatic Replication

After you enable the predefined subscriptions in steps 2 and 3, these subscriptions will also replicate any subsequent changes you make to Event Manager object definitions on the source system. Whenever you create, update, or delete events, event group members, systems, agents, or subscriptions, Oracle Workflow raises the corresponding predefined events. These events trigger the Local subscription to the Seed Event Group on the source system, which sends the object definition data to the target system. The External subscription to the Seed Event Group on the target system receives the data and adds, updates, or deletes the object definition in the Event Manager there.

If you do not want to continue automatically replicating changes on the source system to the target system, you can either disable the subscriptions after you finish synchronizing the systems, or disable the predefined events corresponding to those changes.

#### Master/Copy Systems

If you choose, you can treat one system as a master system that replicates its own Event Manager object definitions to its associated copy systems, but does not accept any object definition changes from those systems. To set up master/copy replication, perform the steps to synchronize the target copy systems with the source master system, as usual. Then, to prevent object definitions from being sent from the copy systems, ensure that the Local subscription to the Seed Event Group on the copy systems is disabled. To prevent object definitions from being received into the master system, ensure that the External subscription to the Seed Event Group on the master system is disabled as well.

### See Also

Predefined Workflow Events

Synchronize Event Systems Event

Seed Event Group

To Define an Event Subscription

| Previous | Next |  | Contents | Index | Glossary