NETeXPERT Version Control Distribution System (VCDS) was designed and developed to aid customers in versioning Events, Rule Methods, and Dialogs as well as deploying these objects from one NETeXPERT system to another.

Initial configuration of the product requires creating a new project in the CVS repository, also known as importing. Typically, the directory used to create the new project would come from exporting objects from the NETeXPERT MIB using NETeXPERT’S PA utility program.

When using NETeXPERT’s PA utility, objects are organized in directories by Object Type.

Example 1:

Export all Events, RuleMethods and Dialogs for the Alcatel1353_Mgr and FujiFlexMgr Manager Classes.

The directory structure is organized by Object Type, not by Manager Class as follows:

PADIR/event (All events for all classes chosen will be in this directory)
PADIR/rulemethod (All rulemethods for all classes Chosen will be in this directory)
PADIR/dialog (All dialogs for all classes Chosen will be in this directory)

If the output from PA were used directly while creating a new project in CVS, then the directory structure would be by Object Type. It might make more sense, logically, to place each object in a directory under its own Manager Class.

A script called convertpa.sh was created that takes the output from PA and reorganize the exported objects into a new directory structure. The new directory is organized by Class and each object associated with that class is in that directory. Using this new directory structure, the CVS Project will be organized by class.

Example 2:

Using the output from Example 1 above, run the convertpa.sh script.

The new directory structure will look as follows:

Newdir/Alcatel1353_Mgr (Events, Methods, Dialogs etc will be in this directory) Newdir/FujiFlexMgr (Events, Methods, Dialogs etc will be in this directory)

Currently the script only supports Events, Methods, Dialogs and Classes, but this can easily be modified to support any number of NETeXPERT object types.

Add Comments