Version 9.6	SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT

This section covers the following information:

• Organizations

• Users

• Asset Types and Virtual Types

• Taxonomies

• Lifecycle Models

• Design/Change-Time Policies

• Asset Instances

• Report Templates

• BPM Process Project

• Integration Server Assets

Important:
These sections describe the export sets produced by the predefined export handlers installed with CentraSite. If your site has installed custom export handlers for certain object types, consult your administrator for information about the export sets that they produce.

Organizations

When you export an Organization, the export set consists of:

• The definition of the organization itself

• The contents of the Supporting Documents library of the organization

Additionally, you can optionally export the following objects with the organization:

• Lifecycle models

• Policies

• Child organizations with their related objects

• Assets belonging to the organization

• Definitions of users, groups and roles, together with their associated permissions.

Notes:

1. 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.
2. If lifecycle models and policies are selected to be exported with the organization, users are automatically selected for export also. If lifecycle models and policies are not included in the export, you have the option to select the users for export.
3. 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 will not be exported with the organization. This is true even if the user is the Organization Administrator.
4. If the organization was exported without users or if the Organization Administrator belongs to a foreign organization, the Organization Administrator will be set to the importing user on import; otherwise the Organization Administrator will not change. An organization's Primary Contact will always be the importing user.
5. If the replace option was set and the imported organization is already present in the target registry, its associated groups and users will be updated. Furthermore, if the export included users, the groups are entirely replaced with the corresponding information of the export set, i.e., 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 will retain their users.
6. 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 will be imported to their original organization.

Users

When you export a user, the export set consists of:

• The user object itself.

• All groups that contain the user.

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 will be 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 was not already present in the target registry, the organization of the user in the target registry is decided as follows:

• If "Keep Organization" is selected during the import and the corresponding organization is not available in the target registry, then the import fails.

• If you select a new organization during the import, then the user is assigned to the selected organization in the target registry.

• The same rules apply for imported groups.

Asset Types and Virtual Types

When you export an asset type or a virtual type, the export set consists of:

• 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, i.e., 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 etc.) that are referred to by the type being exported.

See also the section Asset Instances for details of the information that is exported for asset instances.

Taxonomies

When you export a taxonomy, the export set consists of:

• The taxonomy object

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

• Repository resources (icons)

• Optionally, all objects classified by categories of this taxonomy.

Lifecycle Models

When you export a lifecycle model, the export set consists of:

• The lifecycle model object itself.

• 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/group referenced in the lifecycle state permission exists in the target registry, then the permissions will be saved, otherwise the references will be removed during the import.

Design/Change-Time Policies

When you export a design-time policy, the export set consists of:

• The design/change time policy

• Policy actions that the policy uses

For detailed information about exporting and importing design/change-time policies see the section Exporting and Importing Design/Change-Time Policies in the document Working with Design/Change-Time Policies.

Asset Instances

When you export an instance of an asset, the export set consists of:

• The asset object itself.

• All supporting documents associated with the asset.

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

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

• 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 option Include assets referenced by selected assets). If referenced assets themselves reference other assets, also those assets will be included; this selection process is repeated until all asset references are satisfied.

  Note:
  This option can cause the size of the export set to be very large.

Note:
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 will not be exported and a warning message will be logged.

Note:

If the asset is an instance of a composite asset, the export set will also include:

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

• All required objects associated with the asset.

For the list of shared and non-shared components associated with the predefined composite types installed with CentraSite, see the section Working with Composite Types in the document Object Type Management.

Report Templates

When you export a report template, the export set consists of:

• The report template itself.

• The associated RPT design file from the repository.

BPM Process Project

The asset type "BPM Process Project" is one of the webMethods 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 itself.

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

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

  For the list of shared and non-shared components associated with the predefined composite types installed with CentraSite, see the section Working with Composite Types in the document Object Type Management.

• All required objects associated with the asset.

Integration Server Assets

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

When you export an instance of an IS Package, the export set consists of:

• The asset itself.

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

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

  For the list of shared and non-shared components associated with the predefined composite types installed with CentraSite, see the section Working with Composite Types in the document Object Type Management.

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

www.softwareag.com

Copyright © 2005-2014 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT