4.1.11 Saving work

As you work with the configuration, your changes are saved to temporary workspace storage. For the configuration changes to take effect, they must be saved to the master configuration. If you have a distributed server environment, a second step is required to synchronize, or send, the configuration to the nodes. Consider the following:

1.	If you work on a page, and click Apply or OK, the changes are saved in the workspace under your user ID. This allows one to recover changes under the same user ID if you exit the session without saving.

2.	We need to save changes to the master repository to make them permanent. This can be done from the Navigation tree by selecting System administration  | Save Changes to Master Repository from the Messages area, or when you log in if you logged out without saving the changes.

3.	The Save window presents you with the following options:

Save

Discard

Discard reverses any changes made during the working session and reverts to the master configuration.

Cancel

Cancel does not reverse changes made during the working session. It just cancels the action of saving to the master repository for now.

Synchronize changes with nodes

This distributes the new configuration to the nodes in a distributed server environment.

Before deciding whether you want to save or discard changes, you can see the changed items by expanding Total changed documents in the Save window.

Important: All the changes made during a session are cumulative. Therefore, when you decide to save changes to the master repository, either at logon or after clicking Save on the taskbar, all changes are committed. There is no way to be selective about what changes are saved to the master repository.

4.	When you are finished, log out of the console using the Logout option on the taskbar.