Exportable object store assets

You can choose to add all the exportable assets of an object store in one operation. This operation does not add the entire ObjectStore object to the export manifest, only its exportable assets. Exportable assets also do not include the workflow system that might be associated with the object store.

For information about which object store assets are exportable, see Content Cortex assets.

Tip: For an object store with a large number of filed documents, you can use a SQL search to divide the objects into distinct sets instead of exporting the object store as a single operation. You can use this method to gain more control over the entire process and to process the sets concurrently. For more information, see the example Divide large set of objects into distinct result sets in SQL search examples for generating a list of assets.

When you add an ObjectStore object to an export manifest, the following categories of object store asset are added. The include option specification of each asset is set to All.

  • ChoiceList objects
  • PropertyTemplate objects
  • Exportable ClassDefinition objects
  • RootFolder folder
  • All instances of system management objects and configuration objects, such as the following objects:
    • XMLPropertyMappingScript objects
    • DocumentLifecycleAction objects
    • DocumentLifecyclePolicy objects
    • EventAction objects
    • StoragePolicy objects
    • DocumentClassificationAction objects
    • SecurityPolicy objects
    • Sweep Management objects

Because the include option specification for each asset is set to All, the following assets are also exported from the object store during the export operation:

  • Any ClassDefinition objects that are subclasses of the exportable ClassDefinition.objects.
  • All subfolders of the RootFolder folder. These subfolders include business data that is represented as a folder, such as an IBM® Content Navigator teamspace or an IBM Case Manager case.
  • All Document and CustomObject objects that are filed in a folder in the object store. These objects include application assets that are represented as a document or custom object, such as a workflow definition or an entry template. Additionally, they include any business data that is stored as an instance of Document or CustomObject.
  • All dependent objects in the object store that are implicitly included by the export process. For information about which dependent objects are implicitly included, see Content Cortex assets.

Any Document or CustomObject objects that are unfiled are not included in the export operation.

Some objects are listed individually in the export manifest instead of being incorporated by using export include options. Any instances of those objects that are created after the export manifest is created are not included in the export data unless they are associated with some other object that is being exported and that association is recognized as a part of the export include options. For example, a recently created EventAction object that is associated with an InstanceSubscription object of a document is exported if that document is filed in a folder because the include option Include associated actions is automatically set. An example of a recently created object instance that is not included is a Search Function Definition object that is referenced by the SQL search that is used by a Background Search Template object.