After you define the connection point half maps for the
source and destination environments, you can combine them to create
a connection point data map.
Create a connection point data map for a source-destination
pair:
- In the FileNet® Deployment Manager tree
view pane, expand the Source-Destination Pairs node and double-click
the source-destination pair.
- If connection point data is not to be used when data is
converted for import, clear the Use check box for
the connection point map. If you clear this check box, the connection
point data map is not used and, therefore, it is not necessary that
you populate the data map. If you use this option, you can skip steps
3 and 4. Clear the Use check box only if you
are sure that all referenced connection points have the same names
in both environments. If you are not sure, leave this check box checked
and create a connection point data map.
- Click the Map Data for Connection Point Map radio
button to create a connection point data map.
FileNet Deployment Manager maps the connection points
in the source environment to the corresponding connection points in
the destination environment and updates the connection point data
map to reflect these mappings. Connection points are first matched
by using any user-defined labels that might be present. Then, they
are matched by using the connection point name.
- If the data map contains half map items that FileNet Deployment Manager cannot map, perform one
of the following steps to resolve the unmapped entries:
- Modify the data in the source and destination environments
to eliminate the inconsistencies. Then, re-create the half maps and
the data map.
- Edit the data map to add matching labels for any unmapped
connection points. For more information, see the Viewing or updating a data map section of the
help topic.
- Edit the half maps directly to add matching labels for any
unmapped connection points. Then, re-create the data map. For more
information, see the Editing labels in a half map help
topic.
-
Restriction: If you use labels to resolve unmapped
entries, be aware that FileNet Deployment Manager supports only a
one-to-one and many-to-one correspondence between mapped connection
points. That is, you can use a label for several source connection
points but only one destination connection point. Assigning the same
label to multiple connection points in the destination environment
can cause unexpected behavior.
Restriction: 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.