Sequence of Calls

Programming Guides › Programming Guide for Perl › Policy Management Operations › Policy Store Object Migration › Sequence of Calls

Sequence of Calls

To move objects from a source policy store to a target policy store, call the following methods in the order shown below:

Exporting from the source policy store:

$dataMgrSource=$session‑>CreateDataManager();
$dataMgrSource‑>Export();

Importing to the target policy store:

$dataMgrTarget=$session‑>CreateDataManager();
$dataMgrTarget‑>Import();

The following steps describe these calls in more detail:

CreateDataManager(). This method creates the data manager object (PolicyMgtDataMgr) for the export operation. The method is called from a PolicyMgtSession object. It generates two export files with the following default names:
- migration.smdif—Contains data about the object being exported. This is the information that will be imported into the target data store.
- migration.cfg—Contains installation-specific properties, such as IP addresses and URLs, which are subject to change during migration.
  You can edit migration.smdif with Microsoft Excel. After you edit this file appropriately for the target site, rename it, and store it at the target site, you can reference the file in subsequent Import() calls.
  
  If you specify the target site’s .cfg configuration file as an argument to an Import() call, the settings in the specified .cfg file override those in the migration.cfg file returned from the export operation.
  
  The settings in migration.cfg are a subset of the settings in migration.smdif, and they override the corresponding settings in migration.smdif once edited.
Export(). After creating the PolicyMgtDataMgr object at the source site, call Export() to export the specified object data and the source-site configuration information to the two export files.
If you are using separate scripts for the export and import operations, call CreateDataManager() from the import script to create the data manager object for the import operation.
Import(). The import call imports the data in the migration.smdif file (its default name) into the target data store. Optionally, you can specify the following information:
- The name of the file containing site-specific information for the target site.
- The parent object that will contain the objects being imported.
  For imported objects (such as realms, rules, and policies) that are dependent upon other policy store objects, you must specify a parent object. For top-level objects in the data store (such as agents, administrators, and domains), no parent object is required.

Optionally, you can set flags to fine-tune the export and import operations.

The PolicyMgtDataMgr object provides several methods for setting export and import flags. To change a flag setting, call the associated method before calling Export() or Import().

After you set a flag, the flag retains that setting throughout the current instance of the PolicyMgtDataMgr object unless you reset the flag.

The following table describes the methods that set export and import flags:

Method	Applies to	Description
ClearText()	Export()	Export passwords and shared secrets in encrypted form or as clear text. Default is 0 (exported data is encrypted).
IncludeDependencies()	Export(), Import()	Include or exclude object dependencies in an export or import operation. Default is 1 (include dependencies). Dependencies are objects that the current object depends on. For example, an agent object is a dependency for a realm object. Child objects, such as the realms in a domain, are always included when the parent object is imported or exported.
OverwriteObjects()	Import()	Overwrite or protect existing objects in the target data store during an import operation. Default is 1 (overwrite existing objects). CreateDataManager() provides a flag for protecting or overwriting existing data and configuration files during export operations.

Method

Applies to

Description

ClearText()

Export()

Export passwords and shared secrets in encrypted form or as clear text. Default is 0 (exported data is encrypted).

IncludeDependencies()

Export(),
Import()

Include or exclude object dependencies in an export or import operation. Default is 1 (include dependencies).

Dependencies are objects that the current object depends on. For example, an agent object is a dependency for a realm object.

Child objects, such as the realms in a domain, are always included when the parent object is imported or exported.

OverwriteObjects()

Import()

Overwrite or protect existing objects in the target data store during an import operation. Default is 1 (overwrite existing objects).

CreateDataManager() provides a flag for protecting or overwriting existing data and configuration files during export operations.