Component upload

The component upload enables the comparison of components on different servers on a regular basis by using jobs. This is achieved without the need to synchronize the entire data present on the server.

This can be used in environments employing different server systems (for example, at headquarters (HQ) and on the production line) in a wide range of different scenarios.

Example scenario 1:

 

The component versions of individual servers are uploaded to the master server and are then compared with the master version. The component upload is carried out on the master server.

This process can be used to ensure that the versions of the components at the individual locations are up to date. By uploading strategically important components, you have the option to monitor how the update is progressing and can, if needed, take any necessary steps.

 

Example scenario 2:

 

The component upload is carried out on the relevant server at individual locations. The locations actively load the most up-to-date component version of the master service onto their respective servers then compare these versions with the newest version.

We recommend using this procedure when issuing instructions or information to the locations or when you want to deploy the newest version.

Key features and functions

Individual component type for the upload of versiondog components

Automatic recognition of differences between components on different servers

Clear presentation of complete change history

---