IBM FileNet P8, Version 5.2.1            

Deployment trees in FileNet Deployment Manager

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.

Start of changeThe first time that you use FileNet Deployment Manager, you must specify the root folder to use for a deployment tree. By default, the deployment tree root folder is saved to the following path: cpe_install_path/ContentEngine/tools/deploy/P8DeploymentData. The cpe_install_path variable is the installation location for Content Platform Engine, such as C:\Program Files\IBM\FileNet\ or /opt/IBM/FileNet/. For example, if you are on a Windows system and you use the default path, but you choose to create a new my_deployment_tree_1 folder in that path, then the full path to the deployment tree is C:\Program Files\IBM\FileNet\ContentEngine\tools\deploy\P8DeploymentData\my_deployment_tree_1.End of change

You can use this version of FileNet Deployment Manager with a deployment tree that was created from an earlier version. However, when you use trees that were created earlier than FileNet Deployment Manager version 5.2.1, you must first upgrade the tree. This upgrade occurs automatically when you use the user interface to open the tree. If you use the command-line interface to open the tree, you must use the UpgradeDeploymentTree operation. For a staged upgrade, you must use the version of FileNet Deployment Manager that matches your Content Platform Engine.

Characteristics of deployment trees:

When first created, a deployment tree is a set of empty folders. 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.
Start of changeOptionSetsEnd of change Start of changeProvides an optional storage location for import options set files that you might want to reuse, customize, or share with other team members. This folder is provided as a convenience only; you can save these files in other folders of your choosing.End of change
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 creates during each session. Each time that a deployment operation runs from the graphical user interface, FileNet Deployment Manager creates a time-stamped subfolder in the Temp folder, and saves files such as the deployment operation file, the import options set file, and log file output in that subfolder. These files provide a single point of historical reference that you can use to view the details for one instance of a deployment operation.

The 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 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.



Last updated: October 2015
deploy_mgr_concepts_deploy_trees.htm

© Copyright IBM Corporation 2015.