IBM FileNet P8, Version 5.2.1

Deployment files used by FileNet Deployment Manager

When you create an environment or a source-destination pair, FileNet® Deployment Manager creates a set of XML files in the deployment tree. When you define the environment or source-destination pair, FileNet Deployment Manager populates the XML files with the information you specify.

See Deployment configuration files for complete descriptions of these deployment output XML files.

Environment files

Environment configuration

The EnvironmentConfig.xml file defines the configuration for a specific FileNet P8 environment. This file contains the following elements:

Connection: Specifies the information that FileNet Deployment Manager requires to connect to FileNet P8. This information is derived from the fields on the FileNet P8 Connection tab for the environment.
Map files: Identifies the half map files that are created for the environment.

Half maps

Object store half map: The HalfMap_ObjectStore.xml file contains a list of the object stores in the environment and might contain lists of storage areas and storage policies for each object store.
Security principal half map: The HalfMap_Principal.xml file contains a list of the security principals that were extracted from the environment.
Service half map: The HalfMap_Service.xml file contains a list of the service-related information that were extracted from the environment.

Connection point half map: The HalfMap_ConnectionPoint.xml file contains a list of the workflow system connection points that were extracted from the environment.

Source-destination pair files

Pair configuration: The PairConfig.xml file identifies the source and destination environments for specific deployments. In addition, the file indicates whether FileNet Deployment Manager is to use the principal data map and the storage area or storage policy submaps 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.

Remember: The use entry can be set to no for the principal data map, storage policy submaps, and storage area submaps only. For the object store data map and the service data map configuration, leave the use entry set to yes; otherwise, the attempt to convert the objects for import fails.

Data maps

To create the data maps, FileNet Deployment Manager merges the half maps for the source and destination environments and maps the object pairs that are based on the following algorithm:

Source objects that are labeled are mapped to destination objects that have the same labels in the corresponding type of list.
Mapping is done by symbolic name, display name, or ID if labels were not used to match the source objects.
Any source objects that cannot be mapped to a destination object are added to the data map as unmapped objects.
Use the drop-down selection fields in the data map editor or assign labels in the half maps to map any objects that FileNet Deployment Manager cannot match. For information about using the data map editor, see Editing a data map. For information about assigning labels, see Editing labels in a half map.

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. It can also identify the storage policy or storage area in each mapped destination object store that corresponds to each storage policy or storage area in each source object store. When you convert objects for import, FileNet Deployment Manager uses this map to replace references to object stores, storage policies, and storage areas from the source environment with references to object stores, storage policies, and storage areas from the destination environment.

Storage areas and policies are a subset of object store data and, if they are included in the half maps, are mapped when the Map Object Stores™ operation is performed. The operation maps the source object stores with the appropriate destination object stores first. Next, the storage areas and policies for each successfully mapped source object store are mapped.

You can map multiple source storage areas from an object store to the same destination storage area and multiple source storage policies from an object store to the same destination policy.

Security 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 replace user and group information wherever it appears in the source information. For example, FileNet Deployment Manager converts users and groups in permission lists, notification lists, or collections of user preferences.

You can map multiple source users or groups to the same destination user or group. You can also map users to a group and a group to a user.

Service data map

The DataMap_Service.xml file identifies the service items in the destination environment that correspond to service items in the source environment. When you convert objects for import, FileNet Deployment Manager uses this map to replace references to service items from the source environment with references to service items from the destination environment.

Service items are mapped according to type. For example, all service items of type F_WebServer in the source half map are mapped to service items of type F_WebServer in the destination half map.

Connection point data map

The DataMap_ConnectionPoint.xml file identifies the workflow system connection point in the destination environment that corresponds to each connection point in the source environment. When you convert objects for import, FileNet Deployment Manager uses this map to replace connection point information wherever it appears in the source information. For example, FileNet Deployment Manager converts the connection point in workflow system configuration data. You can map multiple connection points to the same destination connection point. Although many-to-one mappings are allowed, the connection points that are mapped must communicate a one-to-one mapping for the isolated region that they reference. All connection points associated with an isolated region in the source must be mapped to connection points that reference a single isolated region in the destination.

Deployment operation files

For information, see Deployment operation files.

FileNet Deployment Manager log files

For information about log file location and logging configuration and usage, see FileNet Deployment Manager log files.