Overview of a migration and deployment process with FileNet Deployment Manager

For assets that are created with FileNet® P8 tools, you can use FileNet Deployment Manager for parts of the migration and deployment process.

The following three-part diagram provides an overview of the various tasks in a migration and deployment operation that uses FileNet Deployment Manager. The first part of the diagram shows the standard migration and deployment tasks in a flow. The remaining two parts of the diagram show how a deployment package moves through the migration and deployment tasks.

The following information summarizes the actions in the standard deployment flow.

1 and 2. Define the source and destination environments in the FileNet Deployment Manager. See Create or edit an environment definition and Checklist: Environment definitions for more information.

3. Export the necessary data from the source environment by exporting the assets that are listed in an export manifest to create a deployment data set. For information about creating an export manifest, see Create or update an export manifest. For information about creating a deployment data set, see Create deployment data set.

4 and 5. Retrieve the object store, security principal, and service information from the source environment and the destination environment. For information, see Extract an object store half map, Extract a security principal half map, and Extract a service half map.

6. Create an export manifest and add the assets to be exported from the object store or a workflow system of a source environment. For more information, see Creating or updating an export manifest.

7. Convert the environment-specific attributes in the deployment data set to produce the data suitable for import into the destination environment. The convert operation uses a data map to convert any environment-specific information for the exported objects. For more information, see Convert objects for import.

8. Analyze the export files intended for import to assess whether the import operation is likely to be successful. Although this step is optional, it can be an important step, depending on the nature of your destination environment. For example, assessing the potential impact on the destination environment might be of little concern when the destination is a test environment that is easily reconfigured. However, when importing into a live, deployed environment, performing this analysis can be extremely useful. For more information, see Analyze objects for import.

9. Import the converted deployment data set to the destination environment. .