Exporting Design/Change-Time Policies
When exporting a design/change-time policy, keep the following points in mind:
You can export a policy that is active or inactive. You do not need to deactivate a policy to export it.
The export process does not export the following objects that a policy references:
Lifecycle State
Organization
The export process does not export the policy's instance-level permissions. When an administrator imports the policy on the target instance, the import process assigns instance-level permissions as described in
Importing Design/Change-Time
Policies.
If the policy includes a custom action,
CentraSite will export the action template for the custom action along with the action's associated Java archive file (if the action has been implemented as a Java program) or Groovy script (if the action has been implemented as a Groovy script).
If the policy's object scope includes a custom asset type,
CentraSite will export that type along with the policy. (Note that many of the predefined types that are installed with
CentraSite are treated as custom asset types and will be exported if they are within the policy's scope. For a list of the predefined types that are treated as custom types, see the
CentraSite Administrator’s Guide.
If the policy scope is
Assets, then the type information will not be exported. So any basic attributes referenced in the policies have to be edited in the target registry (for example, if the policy has assertions such as
Set Attribute value or
Validate Attribute value). There is one exception, namely if the policy uses classification attributes in the policy assertions; in this case, the type information is included in the export.
The export process will export the parameter values assigned to the actions in the policy. If the parameter value is a reference to an instance of one of the following object types, you must export the referenced object and import it on the target instance of
CentraSite before you import the policy:
Organization
User
Group
If referenced User/Group objects do not already exist on the target instance of CentraSite when you import the policy, the import will remove the references to these objects and the import will be successful. After the import, you can edit the policy to reference the necessary user/group objects. If a parameter references any other type of object, the export process will export the referenced object with the policy and that object will be imported as necessary into the target registry.
If the policy executes on a PreStateChange or PostStateChange event, the lifecycle model and state information on the policy's
States tab will be exported. If the specified lifecycle model and states do not exist in the target instance of
CentraSite when the policy is imported, the import process will fail (that is, the policy will not be imported).
To export a policy
1. In CentraSite Control go to Policies > Design/Change Time to list the available policies.
2. Locate the policy that you want to export and choose Export from its context menu.
3. Specify the options in the Export dialog box and click OK. If you need information about export options, see the CentraSite Administrator’s Guide.
4. Save the archive file when prompted to do so.
5. Examine the export log that is displayed by CentraSite Control and check for any errors that occurred during the export process.
