If the asset or any referenced object in the archive already exists in the gateway instance of CentraSite, the existing object will be overwritten according to the conditions described in the CentraSite Administrator’s Guide.

To export an asset, you must have the instance-level "View" permission on the asset.

To import an asset successfully, you must belong to a role that includes the “Manage Assets” permission for the organization in which the selected asset resides.

The export process does not export the selected asset's instance-level permissions.

The export operation creates an archive file on the file system. The archive file contains a copy of the assets that you have exported. The archive file can be imported afterwards into the same CentraSite registry or into a new registry.

When you import the asset on the gateway instance, CentraSite assigns instance-level permissions to the imported asset just as though you created the asset manually. (In other words, the imported asset receives the same permission settings as the assets you create from scratch.)

When an imported asset replaces (updates) an existing asset in the target registry, all of the asset's properties, except for its permission settings, are updated according to the asset object in the archive. This includes the asset's organizational scope and its lifecycle state. If the referenced organization and/or lifecycle model does not already exist on the target registry, the import process will fail.

If the archive file contains a reference to an object that is not already present in the target registry or is not included in the archive file itself, the asset will not be imported.

If design/change-time policies exist for the events that the import process initiates (for example, creation of an asset), those policies will be triggered.

The archive you wish to import must reside in the file system of the computer where your browser is running.

This is of specific relevance to REST and XML based service assets. Beginning with version 9.7, CentraSite supports the enhanced interface for REST services (in contrast, earlier versions of CentraSite supported a standardized interface for REST services). Documentation of the prior REST service interface is available to Software AG customers who have a current maintenance contract in Empower, Software AG's global extranet (https://empower.softwareag.com/).

Starting with this version 9.7, you cannot import a REST service implemented by current version of CentraSite to previous versions of CentraSite. This is because, CentraSite prior to version 9.7 do not support the enhanced REST interface.