IBM FileNet P8, Version 5.2.1            

Creating a source-destination pair definition

Create source-destination pair definitions by using source and destination environment definitions and half maps.

A source-destination pair definition connects a source environment to a destination environment and provides a mechanism to create data maps. The data maps are created from the combination of the various half maps that are associated with the source and destination environments. The object store, service, security principal, and connection point half maps for the source and destination environments are used to create object store, service, security principal, and connection point data maps.

Use the following checklist to identify the tasks that are required to create or update a source-destination pair definition.

This checklist table lists tasks. If a task is conditional, the table also lists the conditions under which to perform the task.
Task Perform this task if:
Identify the pair of environments to be used for a specific deployment. For example, you might create a source-destination pair for deploying your application from a development environment to a test environment.

See Create a source-destination pair.

  • You are going to create a new association between a source environment and a destination environment.
Create or update the object store data map with the data from the object store half maps.

See Create an object store data map.

  • This is the first time you are defining a source-destination pair for this deployment.
  • The object store half map for the source or destination environment changed.
Use the drop-down selections in the data map or add labels in the object store half map to resolve unmapped entries in the object store data map.

See Edit labels in a half map.

  • The data map contains source object stores that are not mapped to destination object stores.
  • The data map contains source storage areas that are not mapped to destination storage areas.
  • The data map contains source storage policies that are not mapped to destination storage policies.
Create or update the security principal data maps with the data from the security principal half maps.

See Create a security principal data map.

The users and groups are different in the source and destination environments and:
  • This is the first time you are defining a source-destination pair for this deployment.
  • The security principal map for the source or destination environment changed.
Use the drop-down selections in the data map or add labels in the security principal half maps to resolve unmapped entries in the security principal data map.

See Edit labels in a half map.

  • The data map contains source security principals that are not mapped to destination security principals.
Create or update the service data map with the data from the service half maps.

See Create a service data map.

  • This is the first time you are defining a source-destination pair for this deployment.
  • The service half map for the source or destination environment changed.
Use the drop-down selections in the data map or add labels in the service half map to resolve unmapped entries in the service data map.

See Edit labels in a half map.

  • The data map contains source service data that is not mapped to destination service data.
Create or update the connection point data map with the data from the connection point half maps.

See Creating a connection point data map.

  • This is the first time you are defining a source-destination pair for this deployment.
  • The connection point half map for the source or destination environment changed.
Use the drop-down selections in the data map or add labels in the connection point half map to resolve unmapped entries in the connection point data map.

See Edit labels in a half map.

  • The data map contains source connection point data that is not mapped to destination connection point data.


Last updated: October 2015
deploy_mgr_checklist_pair_def.htm

© Copyright IBM Corporation 2015.