Importing the XML file (Infrastructure)

Configuration must Already Exist

An import can only be performed into an existing ICDB. It is not possible to create the ICDB by importing an XML file.

Consistency Check of the XML File

The DSMC checks the XML file for consistency during import. The check corresponds to that performed by the DSMC if you save a changed configuration there.

Logging the Import

A log file is created specifically for the import: NcpImport.log.

Administration Permissions Required

When importing the XML file, the administration permissions of the user performing the import are checked for each object. If the user does not have the required write permissions for a particular object, that object is skipped during import. This means:

• If he has no write permission to the site configuration, the data of the objects in question is not changed.
• If he has no write permission to an object of the site structure, no objects are entered in the context of this object.
• If he has no write permission to the administration permissions, no administrator accounts are entered in the context of this object, and no changes will be applied to administration permissions.

Identification of Objects

If "comparable" objects already exist in the target configuration, the system decides, by means of the logic described below, whether an object is to be "synchronized" or a new object created.

The decision is based on a comparison between the target configuration and the configuration to be imported with regard to name, context ("path" of the object up to the ORG) and ID of the object:

Object name	Object context	Object ID	Result of the import	Explanation
Same	Same	Same	The existing object adopts the new values.	Only object values have been changed.
Different	Same	Same	The existing object takes on the new name and adopts the new values.	The object has evidently been renamed.
	Different	Same	A new object is created. The existing object remains unchanged.	Although the object has the same ID, it has a different context -> it is evidently a different object .
Same	Same	Different	The existing object adopts the new values.	Because the name and path are the same, it is evidently the same object. However, it was created in a different site structure (different ID).
All other cases			A new object is created.

Adopting the Object ID from the XML File into the Target Configuration

In order to create a new object, the object ID provided in the XML file is adopted. If this is not possible because the ID already exists in the site structure, you can choose between two options when launching the import module:

• Cancel import, output an error code
• Ignore ID.
  The object is imported. Another object ID is created automatically.