FileNet Deployment Manager requires that you work within a predefined folder structure called the deployment tree. This tree contains the files that FileNet Deployment Manager creates.
The first time you use FileNet Deployment Manager, you must specify the root folder for the deployment tree. By default, the root folder is <install_location>\FileNet\ContentEngine\tools\deploy\P8DeploymentData.
The following table describes the folders in the deployment tree and their contents.
ATTENTION You can move or copy the entire deployment tree structure; however, do not rename the individual folders or configuration files that are created by FileNet Deployment Manager.
Folder | Description |
---|---|
Environments | Provides a container for environment-specific information. When you define a source or destination environment, FileNet Deployment Manager creates a subfolder within the Environments folder for that environment. Within this folder, FileNet Deployment Manager places the XML files that contain the environment configuration and the object store and security principal information for the environment. In addition, FileNet Deployment Manager creates an Assets subfolder in each environment subfolder. If you want, you can use the Assets subfolder to store deployment-related files. For example, you can use this subfolder to store the export files, descriptor files, converted objects, and content required to deploy the application. |
Modules | Not used in the current release. |
Pairs | Provides a container for information related to source-destination pairs. When you define a source-destination pair, FileNet Deployment Manager creates a subfolder within the Pairs folder for that pair. This subfolder contains the pair configuration, object store data map, and principal data map files for the pair. |
Samples | Contains sample files, which you generate using FileNet Deployment Manager. For more information, see Create sample files. |
Temp | Provides a container for the deployment operation files that FileNet Deployment Manager creates during each session. You can use these files with the deployment command line interface. For more information, see Deployment command-line reference. |