Applying all change files at once
The Nautical Information System (NIS) environment allows multiple production databases to be updated with edits that were applied to the Central Database Repository (CDR). Each time the instance is updated in the product library, an XML data change message is generated for each of the product's replicas. For example, in a common production workflow, data change messages are generated for typical edit operations performed within the NIS. These data change messages are stored within the product library and applied to the production database through the Apply Changes tool.
Within the NIS to product environment, data changes from the NIS are propagated to the production databases through a two-step process using the Update Instance command and Apply Changes tool.
The Apply Changes tool runs the Product Refresher processes automatically once the apply changes process is complete.
You can also apply change files individually.
- Start ArcMap.
- On the main menu, click Customize > Toolbars > Production Editing.
Click the Production Start Editing button on the Production Editing toolbar.
The Manage Features and Create Attributes, Update Attributes, or Metadata Attributes windows automatically appear when you start an edit session using the Production Start Editing tool.Tip:
If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Show/Hide Attributes button on the Manage Features window.
Click the Stop Editing button on the Production Editing toolbar.
The geodatabase becomes uneditable. If you have made edits, you will be prompted to save the changes if you want.
- On the main menu, click Customize > Toolbars > Nautical.
Click the Apply Changes button on the Nautical toolbar.
The Product Updates dialog box appears.
Click Apply All.
A message box appears saying the updates were applied. All existing data change messages are applied to the replica version from the oldest to most recent date.
A dialog box appears notifying you that there are updates to be applied.
You must be in a production database that was populated by using the Update Instance command in product library.