F4. Examples of Administrating the Repository with a Modification of the Status File

Full synchronization of a product:

stop the Server,

delete the content of the product folder, except for the .id and the .config files,

write 0 to the .id file,

launch the Server,

update the product.

 

0 revision has a special meaning, as it disables propagation, therefore the "empty" status of the product is not propagated to the Agents.

 

Disabling of propagation:

1.Stop the Server.

2.Write 0 to the .id file.

3.Comment the sync-with instruction in the .config, file to disable synchronization.

4.Restart the Server.

5.Update the product.

Shift from the "frozen" status to a new version:

1.Replace the content of the .id file

<new_revision> <previous_revision> frozen

with

<new_revision>,

2.Restart the Server.

3.Update the product.

Roll back from the "frozen" status to the previous version:

replace the content of the .id file

<new_revision> <previous_revision> frozen

with

<new_revision> <previous_revision>,

restart the Server,

update the product.

 

At future attempts to synchronize to the <new revision>, the repository will go into the "frozen" status again. Saving an <old revision> with updates rejecting is reasonable when a suitable revision is available, for example, after successful tests in the lab.