Skip to content

Import service model definitions

Perform the procedures in this section to import a service export file in graphml format that contains service model definitions.

The service models in the export file are imported into a non-operational "sandbox" environment on the target system. The service model remains hidden in the sandbox through the reconcile phase, and does not appear in the browser interface until you perform the final commit.

The import and reconcile process typically supports files that were exported by the same or different Resource Manager instance and version (older or newer), and Service Impact versions (older or newer). If an export file's content is incompatible with a version of import, incompatibilities can usually be resolved by adjusting the graphml file content or structure.

Reconciling originating and target system entities

The reconcile phase is an iterative process in which you attempt to match devices or components from the originating system with their equivalents on the target system.

Multiple attempts to reconcile are often required before you can commit a service model that originated on another system. For faster progress, make multiple small changes and frequent attempts to reconcile.

Begin by reviewing the reconcile.<date>.txt file that the initial import generated.

For each service model member, one of the following results or actions exists. When the attempt to reconcile succeeds, results are reported. When you must manually correct exceptions in the model, actions provide guidance. <NodeID> identifies the imported service model member. Do not modify the node ID. <TargetNodeID> is the DMD ID, name, or GUID of the target entity to apply to the imported service model member.

The result for any member on the originating system that the service model references but which cannot be identified on the target system.
MAP <NodeID> <TargetNodeID>

The result if a matching entity was found on the target system or an action to take for an UNRECONCILED service model member. Replace UNRECONCILED with MAP and specify the DMD ID, name, or GUID for the target entity. For example, you might MAP to specify that device "stage-AppSvr1" should reference "prod-AppSvr1" in production.

MAP stage-AppSvr1  prod-AppSvr1

Note: Some cases might require that you first define and model a device in Resource Manager so that the next reconcile attempt can detect it either automatically or manually through use of the MAP action.


An action to take when no matching entity was found in the target system, but an entity can be created through import. For example, you might CREATE to add a device for production when a similar device does not exist in staging.

CREATE prod-AppSvr1

The result when a matching entity was found in the target system, and it is marked to be deleted in the import file, or an action to take when an entity is not needed. Use DELETE to delete the device, not just remove it from the service model. Replace UNRECONCILED with DELETE and specify the DMD ID, name, or GUID.

For example, you might DELETE to remove a device in production.