Scripting
Even the basic version of the data management system versiondog supports the automation systems and devices that are most commonly used in the field. Nonetheless, you won’t come across homogeneous automated landscapes when you pay companies a visit. Backups may also need to be made for devices that are outside versiondog’s range of functions.
After spending some time on research, you can judge whether a device can be “upgraded†with a specifically designed script and if the customer’s requirements can be met. Experience has shown that this is possible for up-to-date devices without too much effort / expenditure. The chance of finding a solution for older devices is not as high.
Nowadays, manufacturers are careful to allow for data storage of their own products and provide tools to carry out the backup. Nowadays, manufacturers are careful to allow for data storage of their own products and provide tools to carry out the backup. This is where versiondog steps in to create added value for the customer through scripting.
The manufacturer’s tools are often integrated into the upload process via scripting and are therefore included in versiondog’s range of functions.
Mode of operation
Scripts in versiondog are linked to events, in other words, an action within the software triggers the execution of the script. These events are divided into server and client events.
Events on the server
- After a Check-In on the server
- After a Check-Out from the server
- Before/after a comparison
- After the execution of a job
- Before/after a backup job
Events on the client
- Before/ after a change checking for changes
- Before/ after a comparison
- Before starting an editor
- Before and/ after recovery of a version (for example, before and/or after a Check-Out)
Reacting to an event
Generally speaking, scripting has to be activated under the global server settings, as it is not selected by default. Once it has been activated, when it is triggered, versiondog checks whether a script is assigned to this trigger, and executes it accordingly.
Writing scripts
A script can be written using a variety of tools and coding languages. The easiest way is to use a text editor, which is included in every Windows installation. The most elaborate and costliest way is to use a development environment such as Microsoft VisualStudio. The options available for scripting are closely linked to the tools that have been used. The most common tools that have proven themselves to be totally adequate in practice are:
- versiondog’s own scripting language
- Batch files from the Windows environment
- Powershell as a development environment
With access to these tools you can manage almost all (special) tasks in the area of scripting.