Exporting and Importing Specific Object Types

Important: If your site has installed custom export handlers for certain object types, consult your administrator for information about the export sets that they produce.

The definition of the organization

The contents of the Supporting Documents library of the organization

The definition of groups, and roles together with their associated permissions

Users belonging to the organization

Child organizations with their related objects.

Assets belonging to the organization.

Groups, Roles, and Permissions objects cannot be directly exported. You can only export these kinds of objects by exporting the organization to which they belong.

If lifecycle models and policies are selected to be exported with the organization, users are automatically selected for export . If lifecycle models and policies are not included in the export, you have the option to select the users for export.

If the organization is exported with users and a user is a member of one of the organization's groups without being related to the organization itself, then this user is not exported with the organization. This is true even if the user is the Organization Administrator.

If the organization was exported without users or if the Organization Administrator belongs to a foreign organization, the Organization Administrator is set to the importing user on import, else, the Organization Administrator does not change. An organization's Primary Contact is always the importing user.

If the replace option was set and the imported organization is already present in the target registry, its associated groups and users are updated. Furthermore, if the export included users, the groups are entirely replaced with the corresponding information of the export set, that is, users may be added to or deleted from the organization and the groups. However, if the export did not include users, the organization and its groups retain their users.

If an archive with one or more organizations is imported, then the Keep current organization option is implicitly switched on, thereby ensuring that all objects are imported to their original organization.

If the archive with an organization that was created using CentraSite 10.0 or earlier is imported, the newly introduced roles, for example, API Gateway Administrator and API Gateway Publisher are automatically included to the imported organization in the current version of CentraSite.

If an organization with users is imported where the user is already present in the target registry, the import of the user object is ignored and the object is not replaced.

This is also true when only the user name but not its Key attribute are identical; in this case the conflicting user is ignored at import and a warning message is displayed. The user is removed from its group and any Keep current owner settings referring to this user are ignored.

If a user is not already available in the target registry, then the user is imported into the original organization.

The type definition.

The XSD file that contains the type definition.

Optionally, all instances of the asset type or virtual type.

The user defined or customized predefined type definitions of all types and association types that are referred to by the asset type or virtual type being exported. This applies recursively, if a referenced asset type also contains such references, then these are also included in the export set. The instances of such referenced types are not included in the export set, even if the option Include instances is set.

Other user defined or customized predefined objects (taxonomies and so on) that are referred to by the type being exported.

Note that there is a compatibility level number stored with the asset type. Therefore, you may not always be able to import the asset type archive in different CentraSite versions.

All categories belonging to the taxonomy (the entire dependency tree).

Repository resources (icons)

Optionally, all objects classified by categories of this taxonomy.

The lifecycle model object

Optionally, all objects governed by the lifecycle model.

All references to lifecycle state permissions. During the import of the archive in the target registry, if the user or group referenced in the lifecycle state permission exists in the target registry, then the permissions is saved, otherwise the references is removed during the import.

The design/change time policy

Policy actions that the policy uses.

All supporting documents associated with the asset.

The asset's type definition and the used association type definitions, whether the type is a custom type or a modified predefined type.

The taxonomy associated with the asset type, whether the taxonomy is a custom taxonomy or a modified predefined taxonomy.

Optionally, all referenced objects to which the asset has an association.

For each exported asset instance, the export set contains all referenced asset types and association types. This means that when the export set is imported on the target machine, imported assets have no unsatisfied references.

Assets that are referenced by the assets that you wish to export (if you select the Include assets referenced by selected assets option). If referenced assets themselves reference other assets, those assets are also included. This selection process is repeated until all asset references are satisfied.

When you export a Service asset that refers to XML Schemas, the referenced XML Schemas are also exported automatically, provided that you have permission to export them. If you do not have permission to export a referenced XML Schema, the referenced XML Schema is not exported and a warning message is logged.

When you export a Virtual Service asset that refers to a runtime alias defined with its policy, the alias is also part of the export archive. On import, this alias will be overwritten if the object is not present on the target CentraSite. The alias remains unchanged when the Allow replace of registry objects option is set.

All components (shared and non-shared) associated with the asset.

All required objects associated with the asset.

The associated RPT design file from the repository.

The asset type BPM Process Project is one of the webMethods Product Suite asset types for which CentraSite provides an export function. When you export an instance of a BPM Process Project, the export set consists of:

The BPM Process Project asset

The BPM Process Project's type definition, whether the type is a custom type or a modified predefined type.

All components (shared and non-shared) associated with the asset.

All required objects associated with the asset.

The asset type IS Package is one of the webMethods Product Suite asset types for which CentraSite provides an export function.

The asset's type definition, whether the type is a custom type or a modified predefined type.

All components (shared and non-shared) associated with the asset.

IS server assets that are referenced by the assets you wish to export (if you select the option Include assets referenced by selected Assets). If the referenced assets reference other assets, those assets are also included. This selection process is repeated until all asset references are attained.