Service providers with multiple NETeXPERT systems must sometimes deal with the problem of synchronizing NETeXPERT object types among certain NETeXPERT systems. When an object type is added or modified in one system, other NETeXPERT systems need to be similarly modified. VCDS does this synchronization automatically and seamlessly.

In addition to NETeXPERT rules, methods, and dialogs, VCDS also synchronizes Dialog Substitutions, Alert Filters, Alert Column Definitions, Alert Summaries, and NETeXPERT Operator objects.

When an object is created or edited in a VSM editor, VCDS triggers in the VSM database insert this information into the VCDS database. VCDS commits the change to the CVS repository, then deploys to the agents on each VSM system. The agents perform a Package Administration import to the VSM database, synchronizing the system to the original change.

In general, the processing is as follows:

Create / Update

1. Create / Edit / Save an object in a VSM editor.

2. A VCDS trigger on the VSM table inserts this information into a VCDS database table. There is one trigger and table per object type.

3. The VCDS polling server picks up the step 2 information and processes it.

4. VCDS creates the object (if it does not exist), or updates the object in the server cache and broadcasts a jms message.

5. The VCDS object auto-sync service is initiated by the jms message.

6. VCDS commits to the CVS repository.

7. VCDS deploys a Package Administration file of the the object/version to the agent on all other active VSM systems.

8. The agent performs a PA import to the VSM database. Other VSM systems start from step 2 above, and processing stops at step 5, as the identical object already exists in the repository.

Delete

1. Delete a NETeXPERT object.

2. A VCDS trigger on the VSM table inserts this information into the VCDS table for that type.

3. The VCDS polling service picks up this information.

4. The VCDS server deletes this object from its cache and broadcasts a jms message.

5. The VCDS object auto-sync service is initiated by the jms message.

6. The repository object is removed.

7. The object is removed from all other active VSM systems.
Add Comments