Exporting/Importing from a Development Environment to a Test Environment

When you export and import configurations between a development environment and a test environment, you can take a less rigorous approach than when you import configurations into a production environment.

  1. In the development environment, run Verify Configurations (cdverify) to ensure that the configurations you want to export are valid in the current environment.
  2. In the development environment, export the configurations you want to later import to the test environment. You can use the Export option within the Configuration Console in the development environment or run the Configuration Data Export utility.

    Administration Console > Configuration and Personalization > Configuration > Export Configurations

    or at the command line in the development environment, type

    cdexport -z fileName.zip [Options] prodline [ExportActor [=ImportActor]]

    For more information on cdexport syntax, see scexport - Security Class Export.

  3. If you use Configuration Console Actions > Export, copy the export file to the test environment.
  4. Import the file from the development environment. Run Configuration Data Import.

    Administration Console > Configuration and Personalization > Import Configurations and Personalizations

    or at the command line in the test environment, type

    cdimport -I fileName.zip [--keepactor] prodline

    When you run the cdimport command, you can use the --keepactor option or you can skip this option. Without this option, the system deletes all actor related data before doing the import. Since there is a global actor associated with configurations, this means all application and security configurations are deleted before any data is imported. If you want to start with a clean slate--that is, just the configurations you import--then you can leave out the --keepactor option.

    If you want to override any duplicate records on the import, use the -o parameter.

  5. If you run cdimport from the command line, after the import is complete, run cdverify in the production environment to check that the configurations are valid.