Adding scripts to the import process

When developing a production application, you can use a test environment to create, test, and modify your system before you deploy it in a production environment. Although the Enterprise Manager import process effectively transfers Content Engine objects from one system to another, it does not customize those objects for the new environment.

NOTE  The use of Enterprise Manager or its related command-line tool to create an export manifest, or to export or import objects, is deprecated and it is recommended that you use FileNet Deployment Manager instead for these operations. For more information, see Exporting and importing.

To customize the import process for your production environment, you can associate VBScript or JScript files with the XML import file. These scripts can modify the imported objects or the data associated with those objects.

This feature is available for both manual and automatic import methods:

The methods used for applying scripts to your import process depend on the type of data and objects you want to modify.

Object and data types

You can use scripts to modify the properties and values that depend on the development environment of each imported object. You can program a script to perform the following actions:

Script run types

You can run each script at various points during the import process by using one of the following run types:

The import processor determines the order in which scripts run as follows:

  1. All pre-import scripts run in the order they appear in the Import Helper script list.
  2. All pre-save scripts run in order each time the processor imports an object.
  3. All post-save scripts run in order each time the processor saves an object.
  4. All post-import scripts run in the order they appear in the Import Helper script list.