Automatic object store population

You can set up Enterprise Manager to populate an object store automatically with user-defined objects. You can also add scripts to the import process that customize the imported objects for the new environment.

NOTE  The use of Enterprise Manager or its related command-line tool to create an export manifest, or to export or import objects, is deprecated and it is recommended that you use FileNet Deployment Manager instead for these operations. For more information, see Exporting and importing.

When can I customize automatic object store population?

Consider setting up automatic object store population only if all new object stores need the same set of user-defined components. In this case, populating all new object stores with user-defined components saves you from manually importing objects after creating the object store.

How does the Content Engine populate a new object store?

The Content Engine comes with a set of XML files called add-on features that define the default objects and properties that Enterprise Manager automatically imports into each new object store. Each time you create an object store, the object store wizard offers (under its Advanced page) to install all files found in the local Program Files\FileNet\Content Engine directory for XML files with "AddOn" in the file name. You can refer to the property sheet of the FileNet P8 domain root Import AddOns page later to view or modify.

How do I customize the default objects and properties added to a new object store?

You can extend the default set of objects and properties added to each new object store. This requires creating an XML file that contains only user-defined object store components. By using Enterprise Manager, you can add your user-defined components to the registry list of FileNet P8 components that load automatically during object store creation.

Why must I prepare customized XML files?

You cannot use automatic object store population to import objects selectively. Instead, the system attempts to import all objects included in the XML file. If the Create an Object Store wizard detects duplicate object store components in an XML file, Enterprise Manager cannot create an object store. Therefore, you must carefully prepare your XML file for automatic object store population.

How do I add user-defined components to automatic object store creation?

Use the Auto-Import Scripts utility to add user-defined components that the system installs automatically during object store creation. Use the utility, available through the Enterprise Manager root property sheet, to select an XML file and to associate scripts to run automatically at various points during the import process.

When are customized objects created?

During object store creation, the system first populates the default objects and properties imported from the original set of XML files. Next, the system populates the object store with the components included in your customized XML file in a predefined order. The system also runs any associated scripts according to the run type as defined when you added the scripts through the Auto-Import Scripts feature.

What can I do if the object store creation fails because of duplicate objects?

If the object store creation fails because of duplicate objects in the XML file, you can remove the XML file by using the Auto-Import Scripts feature.