2.7 Submit
Recall we strongly recommended you create and edit changes on your SA prior to modifying your OC. You must then follow the import procedures as described below after transferring these modified files to your OC.
The Import/Upload Process
Importing a configuration file allows the file to be saved to the local datastore. The Configuration Manager sets the filename to NameVersionStatus.xml.
Where:
- Name is the configuration file ID.
- Version is the version number of the configuration file.
- Status is default if it is the active file, a version number if it is inactive.
Synchronizing
Uploading a configuration (file) requires synchronizing all modified and added configuration files with the Central Database.
Caution! Only upload files after testing them on the SA in order to prevent corrupting the Central Database!
The Configuration Manager provides each configuration file with a unique Master Controller ID.
Optimistic Locking
A procedure called optimistic locking stores the latest changes made to a configuration. If other people are working on configuration, it might not save your changes!
During the period between downloading a configuration and uploading a modified configuration, someone else could have made a change to the same configuration. The Configuration Manager will not deal with this possibility.
Communicate with other members of the RFC to ensure only one person is changing a configuration file, as only the last change is saved.
If an error occurs while uploading the new configuration, the configuration rolls back to the previous version.