Features of Update Installation

1. If there are no MDM repositories created in the updated repository, create an MDM repository using the repository manager.

2. Use the object navigator in the updated repository to create:

3. • Database.

   • MDM repository using the created database.

   • Time series databases using the created MDM repository.

3. Open the repository containing the required modeling container.

4. Create an update and add a modeling container with all nested objects to it.

5. Use the update manager to arrange objects of the created update by dependency.

6. Set the required update options: type, method, update condition, and so on.

7. Save updates to the file.

8. Open the repository to be updated and start update installation from the created file.

9. During the update the messages are displayed about failure to update the following objects used by the modeling container:

   • Database. Replace it with the database created in the updated repository.

   • Units dictionary (UNITS). Replace it with the units dictionary from the MDM repository created in the updated repository.

   • MDM repository. Replace it with the MDM repository created in the updated repository.

NOTE. Always use specified objects to update.

After all the steps are executed, the modeling container and all its internal objects are updated.

1. If there are no MDM repositories created in the updated repository, create an MDM repository using the repository manager.

2. Use the object navigator in the updated repository to create:

3. • Database.

   • MDM repository using the created database.

   • MDM dictionaries. Created dictionaries must have the same structure as dictionaries that are included into time series databases used by the modeling container.

   • Time series database using the created MDM repository.

3. Open the repository containing the required modeling container.

4. Create an update and add a modeling container with all nested objects and all used time series databases to it.

5. Use the update manager to arrange objects of the created update by dependency.

6. Set the required update options: type, method, update condition, and so on.

7. Save update to the file.

8. Open the repository to be updated and start update installation from the created file.

9. During the update the messages are displayed about failure to update the following objects used by the modeling container:

   • Database. Replace it with the database created in the updated repository.

   • Units dictionary (UNITS). Replace it with the units dictionary from the MDM repository created in the updated repository.

   • MDM dictionaries used by time series databases. Replace them with identical MDM dictionaries created in the updated repository.

   • MDM repository. Replace it with the MDM repository created in the updated repository.

   • Measures dictionary (MEASURES). Replace it with the measures dictionary from the MDM repository created in the updated repository.

NOTE. Always use specified objects to update.

After all the steps are executed, the modeling container and times series databases used in it are updated.

1. All dependent objects were added to the update. Update is correct.

2. Not all dependent objects are included to update, and objects with the specified keys are not found in consumer. It is checked if empty value is allowed for an MDM dictionary reference attribute:

• For MDM dictionary attributes that allow for an empty value, empty value is written.

• For MDM dictionary attributes that do not allow for an empty value, dictionary update is aborted, and an error is shown that attribute does not allow for empty values.

3. Not all dependent objects are added to the update but in consumer:

• Correspondence is found by keys between repository objects. MDM dictionary is updated correctly by linking to existing objects.

• correspondence is not found by keys between objects and linked objects that are not included into update. A dialog box opens for replacing a missing object. If the user:

• Agrees to replace an object. It is required to select an appropriate repository object. MDM dictionary is linked to the selected object.

• Rejects to replace an object. The attributes that allow for an empty value are set to NULL. For the attributes that do not allow for an empty value, an error is shown that attribute does not allow for empty values.