Export IS mapping to a new object store
This topic describes how to export IS class and property mapping information
from one object store and import it into another. For more details, see FileNet Content Federation Services for Image Services Planning and Configuration Guide.
The IS class mapping information for an object store is contained in the DocClassAndPropertyMappingXML
property of the custom object named IS Mapping Object (of the ISMappingCustomObject
class). This custom object is created by the CFS-IS Extensions AddOn. The XML property in the AddOn is empty
until you map the IS class and IS property. For details about class mapping and property mappings see the following topics:
NOTE When
you export any object from one object store and then attempt to import it into
a new object store, the import fails if an identical object already exists
in the target object store. Because the IS Mapping Object custom object is created
in each new object store by the object store wizard, importing it fails
due to duplicate key errors unless you first delete the IS Mapping Object custom
object from the new object store.
To export IS mapping information into another object store
- Log on to the source object store as an object
store administrator of that object store.
- Create class and property
mapping in the source object store.
- Export the IS Mapping Object custom object.
NOTE Because
custom objects are not included in the object store's Add
to Export Manifest command, you must run
a search to display it. When the IS Mapping Object appears in the Enterprise
Manager's Search Results node, right click it and select Add
to Export Manifest. The custom object will then appear in the Export
Manifest, and you can proceed with exporting it from the source object store.
- In the target object store, log on as an object
store administrator of that object store.
NOTE The
target object store must have identical Content Engine document classes (same
name, same properties) as those referenced in the exported class and mapping
information from the source object store. Also, it must have the exact same
IS fixed content device that the source object store did as well as a fixed
file store referencing that IS fixed content device. You will have to create
that fixed file store, making sure that the Content Engine document classes
referenced in the mapping information are configured to store their content
in the fixed file store.
- Run a search like you did above and delete the IS Mapping Object custom
object when it appears in the search results node of the target object store.
- Import the IS Mapping Object custom object into the target object store.
See Exporting and importing
for help in importing and exporting.