[This is preliminary documentation and subject to change]

Edit-While-Running Scenario 5

This scenario illustrates how edit-while-running works under the following conditions:

• An administrator programmatically deletes a site within the in-memory metabase, and another administrator saves changes to the same site by editing MetaBase.xml with Notepad.

What you will learn:

• How edit-while-running allows an administrator to recover from this situation by reporting an error.
• Why allowing multiple administrators to simultaneously make changes to the same site is not recommended.

Actions Taken:

• Administrator 1 programmatically deletes Site4 in the in-memory metabase.
• Administrator 2 opens the MetaBase.xml file, changes a property value under the Site4 node, and then saves the MetaBase.xml file.

1. IIS receives a file change notification that the MetaBase.xml file has been saved.
2. IIS looks within the MetaBase.xml file for the HistoryMajorVersionNumber value.
3. IIS looks within the history folder for the corresponding history file. The corresponding history file is the file with the same HistoryMajorVersionNumber value as was found in step 2, with the highest minor version number.
4. IIS verifies that the MetaBase.xml file can be parsed and is free of schema errors.
5. IIS compares the MetaBase.xml file against the corresponding history file to determine whether changes were made.
6. IIS verifies that the metabase level exists in the in-memory metabase that the changes were made to. Because Site4 was deleted from the in-memory metabase, an error is sent to the event log.
7. IIS copies the MetaBase.xml file to the history folder and renames the file in the following format:
           MetaBase_majorversion_minorversion.xml
8. The in-memory metabase is written to disk to overwrite the non valid MetaBase.xml file, and an error is sent to the event log.

© 1997-2001 Microsoft Corporation. All rights reserved.