FileNet® Deployment Manager requires that you work within a predefined folder structure that is called the deployment tree. A deployment tree contains the files that FileNet Deployment Manager creates. The first time that you use FileNet Deployment Manager, you must specify the root folder for a deployment tree. By default, the root folder is <install_location>/FileNet/ContentEngine/tools/deploy/P8DeploymentData. When first created, a deployment tree is a set of empty folders.
Because there are no schema changes, you can use this version of FileNet Deployment Manager with a deployment tree created from an earlier version. However, when you begin to use a deployment tree with the latest version of FileNet Deployment Manager, it does not always work with previous versions of FileNet Deployment Manager. For a staged upgrade, you must use the version of FileNet Deployment Manager that matches your Content Platform Engine (if you are exporting Content Platform Engine assets) or workflow systems server version (if you are exporting workflow systems assets).
Characteristics of deployment trees:
The following table describes the folders in the deployment tree and their contents.
| 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, service, and security principal information for the environment. In addition, FileNet Deployment Manager creates an Assets subfolder for both the source and the destination environment. The Assets folder serves as the default location for exported and converted assets. For the source environment, assets consist of exported objects and a Content folder with exported content. For the destination environment, assets consist of exported objects that are converted and a Content folder with exported data. You can use subfolders within the Assets folder to manage multiple exports, for both Content Platform Engine and workflow systems assets. Tip: Although not required, you can use the
default Assets folder co-locates a set of assets with its corresponding FileNet Deployment
Manager environment, simplifying
the management of that environment.
|
| Modules | Not used in the current release. |
| Pairs | Provides a container for information that is 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, service data map, and principal data map files for the pair. |
| Samples | Contains sample files, which you generate by using FileNet Deployment
Manager. For more information, see Create sample files. |
| Temp | Provides a container for the deployment operation files that
the FileNet Deployment
Manager graphical
user interface (GUI) creates during each session. Each time a deployment
operation is performed from the GUI, FileNet Deployment
Manager creates a timestamped
subfolder in Temp, and puts both an operation file and log file output
in that subfolder. The GUI-generated operation files use the same XML format as the operation files used with the FileNet Deployment Manager command-line interface. Therefore, you can use the GUI-generated operation files as a guide for starting operations from the command-line interface. For use with the command-line interface, you can locate an operation file in any directory. When you start the operation, the command-line interface saves a log file in the same directory as the operation file. For more information, see Deployment command-line reference. |