The Content Platform Engine automatically
populates each new object store with a default set of AddOn components.
You can extend this functionality by setting up a customized XML file
to import user-defined AddOn components into new object stores. You
can also associate scripts to run at various points during the import
process. These customized XML files are not supported by FileNet® Deployment
Manager for import.
About this task
Automatically populating an object store with a customized
XML file works differently than importing an XML file to an existing
object store:
- Automatic import process: If you set up Enterprise Manager to import an XML file
automatically to populate all new object stores with user-defined
components, the Import Helper is unavailable. Instead, the system
attempts to import all objects included in the XML file. If the Create
an Object Store wizard detects duplicate objects, it fails to create
an object store.
- Manual import process: When you import an XML file to populate
an existing object store, you use the Import Helper to choose the
objects to import from the XML file. If the Import Helper finds duplicate
objects, it logs the duplicate errors to a file and does not overwrite
any of those existing components. However, the Import Helper can still
import all object store components that do not exist in the target
object store.
Procedure
To set up your system to populate new object stores with
user-defined AddOn components:
- Prepare the user-defined XML file for automatic import
- Prepare the scripts you want to run at various points during
the import process.
- Use the Auto-Import Scripts feature to add customized AddOn
components with associated scripts to run automatically during object
store population.
- Test the automatic object store population.