How Repository Bridge Works

Replicating Objects in the WorldView Repository › How Repository Bridge Works

How Repository Bridge Works

During initialization, the Repository Bridge performs the following operations:

Scans the configuration and parses the bridging policy.
Initializes and begins logging.
Repository Bridge provides complete logging facilities with a configurable level of detail.
Establishes repository connections.
Establishes connections to both the source and destination repository. The Repository Bridge must obtain a connection to both databases to operate.
Registers for notifications.
Registers the Repository Bridge with the source repository for the receipt of object state change notifications, which are used to drive the object replication process.
Builds Bridging decision binary.
Builds an in-memory binary of the bridging policy. This process is analogous to the Event Manager or Security Manager building in-memory binaries of message records and actions. When notification is received, the Repository Bridge can rapidly analyze the notification to see if it should bridge any information to the destination repository.
Synchronizes repositories.
Scans the source repository for all objects that satisfy the bridging policy criteria, and then cross checks the destination repository to ensure the bridged objects exist with the same property values. Any previously bridged objects that no longer conform to policy are deleted from the destination repository.

After these startup procedures are complete, the Repository Bridge is driven by notifications from the source repository. When a notification is received, the object to which it relates is analyzed to determine the following:

The object is bridged, so the notification is bridged.
The object should be bridged as a consequence of the notification, so the object is replicated in the destination repository.
The object is bridged, but no longer conforms to bridging policy as a consequence of the notification, so the replicated object is deleted.