WAS v8.5 > Reference > SetsSave changes to the master repository
Use this topic to update the master repository with your dmgr console changes, to discard your dmgr console changes and continue working with the master repository, or to continue working with your dmgr console changes that are not saved to the master repository.
Until you save changes to the master repository, the dmgr console uses a local workspace to track your changes.
Total changed documents
Total number of documents that you changed for the session, but that are not saved to the master repository. By clicking the +/- toggle key, we can see additional information about the changed documents:
- Changed items
When you change your local configuration, each path and configuration file that we can apply the update to in the master repository is displayed in the list.
- Status
The status can contain the following options:
- Added: If we save your changes to the master repository, a new configuration file is created on the indicated path.
- Updated: If we save your changes to the master repository, an existing configuration file is updated on the indicated path.
- Deleted: If we save your changes to the master repository, an existing configuration file is deleted on the indicated path.
Synchronize changes with nodes
Whether to force node synchronization at the time that you save your changes to the master repository, rather than when node synchronization normally occurs.
Save conflict
Specifies that another user changed some configuration information since you began making changes. We can either click Save to overwrite the other user information, or Discard to discard your changes and keep the changes the other user made.
Related
Start and log off the dmgr console
Reference:
Administrative console buttons