When you create an environment or a source-destination pair, FileNet Deployment Manager places a set of XML files into the deployment tree. As you define the environment or source-destination pair, FileNet Deployment Manager populates the XML files with the information you specify.
Environment configuration
The EnvironmentConfig.xml file defines the configuration for a specific source or destination environment. This file contains the following elements:
Object store half map
The HalfMap_ObjectStore.xml file lists the object stores in the source or destination environment. The half map contains the following information for each object store:
Principal half map
The HalfMap_Principal.xml file lists the security principals extracted from the source or destination environment. The half map contains the following information for each user or group:
Pair configuration
The PairConfig.xml file identifies the source and destination environments for a specific deployment. In addition, the file indicates whether FileNet Deployment Manager is to use the object store data map and principal data map when you convert the objects for import. For example, you might choose not to use the principal data map if the source and destination environments use the same LDAP server. For more information about converting objects, see Convert objects for import.
Object store data map
The DataMap_ObjectStore.xml file identifies the object store in the destination environment that corresponds to each object store in the source environment. When you convert objects for import, FileNet Deployment Manager uses this map to replace references to object stores from the source environment with references to object stores from the destination environment.
To create the object store data map, FileNet Deployment Manager merges the object store half maps for the source and destination environments and maps the object store pairs based on matching names. You must assign labels to map any object stores that FileNet Deployment Manager cannot match. For information on assigning labels, see Edit labels in half maps,
NOTE If you use labels to resolve unmapped entries, be aware that FileNet Deployment Manager supports only a one-to-one correspondence between mapped object stores. That is, you can use a given label for only one source object store and one destination object store. Assigning the same label to multiple object stores in either environment can cause unexpected behavior.
Principal data map
The DataMap_Principal.xml file identifies the user or group in the destination environment that corresponds to each user and group in the source environment. When you convert objects for import, FileNet Deployment Manager uses this map to determine the users and groups that are to have access to each object.
To create this data map, FileNet Deployment Manager merges the principal half maps for the source and destination environments and maps the principal pairs based on matching short names. You must assign labels to map any principals that FileNet Deployment Manager cannot match. For information on assigning labels, see Edit labels in half maps.
NOTE If you use labels to resolve unmapped entries, be aware that FileNet Deployment Manager supports only a one-to-one correspondence between mapped principals. That is, you can use a given label for only one source principal and one destination principal. Assigning the same label to multiple principals in either environment can cause unexpected behavior.
FileNet Deployment Manager creates a DeploymentOperation.xml file whenever you perform one of the following operations:
The DeploymentOperation.xml file provides a record of the specific operation along with the parameters you specify. You can then use the DeploymentOperation.xml file with the command line interface to automate the deployment of an application. For information, see Deployment command-line reference.
FileNet Deployment Manager stores each DeploymentOperation.xml file in a separate subfolder under the Temp folder of the deployment tree. The subfolder name indicates the date and time the file was created. For example, the DeploymentOperation.xml file created for an operation run at 2:30 p.m. on 8 December 2008 is placed in the subfolder named Run.2008.12.08.14.30.00.
The log files used for FileNet Deployment Manager, which are created using Apache log4j, are placed in the current working directory used to start the tool.
The level of detail in the log is determined by the setting in the configuration file, log4j.properties, located in the current working directory. The FileNet Deployment Manager software includes a default log4j.properties file, which is installed in the folder features\com.filenet.deployment.rcp.feature_4.5.0\rootfiles. However, if a log4j.properties file exists in the current working directory, FileNet Deployment Manager uses that file instead of the default file provided with the software. For information about the logging levels and about modifying the configuration file, see Working with the Apache log4j Configuration File.