IBM FileNet P8, Version 5.2.1            

Creating an object store data map

After you define the object store half maps for the source and destination environments, you can combine them to create an object store data map.

Create an object store data map for a source-destination pair:

  1. In the FileNet® Deployment Manager tree view pane, expand the Source-Destination Pairs node, and then double-click the source-destination pair.
  2. Click the Map Data radio button for Object Store Map to create an object store data map. FileNet Deployment Manager maps the object stores in the source environment to the corresponding object stores in the destination environment and updates the object store data map to reflect these mappings.
  3. If the data map contains object store half map items that FileNet Deployment Manager cannot map, perform one of the following steps if you want to resolve the unmapped entries:
    • Modify the object store data in the source and destination environments to eliminate the inconsistencies. Then, re-create the half maps and the data map.
    • Edit the object store data map to add matching labels for any unmapped object stores. For more information, see Update a data map.
    • Edit the object store half maps directly to add matching labels for any unmapped object stores. Then, re-create the object store data map. For more information, see Edit labels in a half map.
      Restriction: 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 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.
    The object store data map can contain tabs for submaps, which provide information about the object stores storage policies and storage areas. These submaps appear if the object store half maps were extracted with the options to also extract the storage policy or storage area information. Storage areas and storage policies maps are a subset of the object store data and are mapped when the Map Object Stores operation is started. The algorithm maps the source object stores with the appropriate destination object stores first. Then, the storage areas and storage policies for each successfully mapped source object store are mapped. If an object store is later mapped or the mapping is changed, the submaps for the associated storage policies and storage areas are automatically regenerated, based on the default map processing rules. Complete the object store mapping before you move onto the mapping of the storage policies and storage areas to avoid the remapping that might occur if an object store mapping is modified. By default, mapping of the storage areas and policies within the submaps for an object store pairing are based first on matching labels, then on ids, then for any remaining unmatched entries on display names. Multiple source storage areas or policies can be mapped to the same destination storage area or policy that supports a many-to-one mapping of storage areas and policies.


Last updated: March 2016
deploy_mgr_howto_object_store_data_maps.htm

© Copyright IBM Corporation 2016.