You can prepare an XML file that contains only your user-defined
object store components.
About this task
These procedures show you how to create an object store
manually. You can use this object store as a prototype for testing
the imported objects. This can help you to detect and fix any duplicate
entries before you use the XML file for automatic imports, when duplicate
entries can cause object store creation to fail.
Procedure
To prepare an XML file for automatic import:
- Create an object store.
Important: During
object store creation, watch the status messages while the wizard
imports the default objects from the XML files that come with your
installation. This can help you understand how setting up a user-defined
XML file for automatic import can affect object store creation.
- Add new classes, objects, properties, and content that
you want added to every new object store.
- For each user-defined class or object you add to the object
store:
- Right-click the top-level object and click Add
to Export Manifest.
Tip: Do not
select any of the default objects or include any associated objects.
For example, do not right-click the Choice Lists node when you select
this option. Instead, select Choice Lists node to display all defined
choice lists in the details pane. Select all the choice lists in the
details pane, and then click Add to Export Manifest.
- In the Include Options page, select only user-defined
options that you have not already added to the export manifest.
Tip: Depending on the type of objects, choose either
Do not included any associated objects or Select associated objects
to be included manually. If you include all associated objects, you
are more likely to create duplicate entries because you cannot review
which objects are associated with the selected object.
- Click OK.
- Right-click Export Manifest and
click Export All Objects.
- Rename the default XML file and log file to help you identify
this set of object store components, and then click OK.
- Create an object store that you can use for testing this
XML file.
- Right-click the new object store and click .
- In the Import Helper screen:
- Select the XML file created in Step 5.
- Change the log file name to one that matches the name
of the XML file.
- Clear these check boxes as appropriate:
- Append if file already exists: If you are
using an existing log file, clearing this check box overwrites any
existing messages.
- Ignore duplicate error messages during import: When
this option is selected during an import procedure, the status messages
show duplicate errors as Ignoring Duplicate Import Error—<Object
Type>. After importing objects with duplicate errors, the
Import Helper displays a message indicating the import process was
successful. This option does not change or remove the errors recorded
in the log file. If you clear this check box before importing duplicate
objects, the Import Helper displays a message that reminds you to
check the log file for errors.
- Watch the status messages displayed while the Import Helper
imports objects.
- If the status messages show no duplicate errors, you are ready
to add the customized component to automatic object store population.
- If the Import Helper detected any errors, review the errors logged
to the file. Depending on the duplicate errors found, take one of
the following steps: