Exporting and importing workspace logic with the export/import utility

Use the export/import utility to transfer Opportunity Detect workspace logic from one environment to another.

The export/import utility operates at the workspace level. You can export all workspaces or specify the workspaces you want to export.

The utility creates an XML file that contains a specification of the workspace logic and all of its dependencies. The export includes all the defined data sources, audience level codes, and named value lists regardless of their usage in the exported workspace.

After export, you can transfer the XML file to the target environment and import the logic. After an export/import cycle, the logic transferred is functionally equivalent in both environments.

The active to passive model

The utility supports only an active-to-passive environment model. In this model, the following assumptions are made.

  • The source environment that generates the export is the only environment in which active development occurs.
  • No regular development occurs in the target environment where the logic is imported.
  • If development occurs in the target, the changes must be applied manually to the source environment so that the changes are not lost in the next export/import cycle

If changes are not made in the target environment between export/import cycles, the import process creates new a workspace in the target if the imported workspace does not exist, or overwrites the workspace in the target if the imported workspace does exist.

If changes are made in the target environment between export/import cycles, conflict resolution rules are applied.

Password security

The information the export/import utility uses to connect with the design time database is saved in an XML file located in the tools/librarymgr/conf directory under your Opportunity Detect installation. This information includes the user name and password for an account in the database. As described in the setup procedures, you can encrypt the password that is stored in this file to avoid storing the password in clear text.

Logging

When the utility has finished running, you can check the log to verify the dependencies. For example, it is possible to import a workspace that includes components referenced in other workspaces. These dependencies are listed in the log file.