Using the Type Manager 3-21
Figure 3–28 Load Dialog
3. Click OK. The XML schema display is displayed, as shown in
Figure 3–29 .
Figure 3–29 XML Schema Display
The display window does not allow editing of the schema. However, the schema may be saved to the local file system for later use. Click Save in the windows File
menu.
3.9.3 Using the Type XML Editor
The XML Editor allows unvalidated modifications of the XML source for Asset Types, Compliance Templates, and Policy Types.
1.
In the Type Manager, select XML Editor from the Support menu. The following warning message displays:
Changes made in the XML Editor are not validated and may render a Type unavailable
2. Click OK. A blank dialog is displayed.
Note: The schema may also be copiedpasted into a local document
to use for validation of Type XML documents.
Caution: Improper changes to the XML source may render all types
inoperable.
3-22 Oracle Fusion Middleware Users Guide for Oracle Enterprise Repository
3. Click OK. The XML schema display opens.
4. Select Load from the File menu in the blank window.
5.
In the Load dialog, as shown in Figure 3–30
, select the type of XML schema to be edited from the Type list.
Figure 3–30 Load Dialog
6.
Select Editor or Viewer from the XML Type list. These selections refer to the Editor and Viewer tabs in the Type Manager.
7. Click OK. The selected schema is displayed, as shown in
Figure 3–31 .
Figure 3–31 XML Schema Display
8. Edit the schema as necessary.
9. Save the changes by selecting Save on the File menu.
4
Import Export Tool 4-1
4
Import Export Tool
This chapter describes the features of the Import Export tool and how to use it to import items into and export items from the Oracle Enterprise Repository.
This chapter contains the following topics:
■
Section 4.1, Overview
■
Section 4.2, Using the ImportExport Tool
■
Section 4.3, Starting the ImportExport Tool
■
Section 4.4, Export Items from Oracle Enterprise Repository
■
Section 4.5, Importing Items into Oracle Enterprise Repository
4.1 Overview
The Oracle Enterprise Repository ImportExport Tool is designed to allow the interchange of assets and related metadata between instances of Oracle Enterprise
Repository.
Archives must be completely self-contained. That is, all dependent data required to fully describe all exported items are also exported. The dependencies are as follows:
■
Assets, Compliance Templates, and Policies rely on Types
■
Asset Types, Compliance Template Types, and Policy Types rely on Categorization Types and Relationship Types
For example, when exporting a single Asset, the resultant archive contains that Asset, its associated Asset Type, and any Categorization Types and Relationship Types on
which that Asset Type depends. When importing, all data contained within the archive is imported into the destination instance of Oracle Enterprise Repository. Conflicts
resulting from the existence of items with the same name are resolved in the following manner:
■
Assets, Compliance Templates, Policies, and their respective Types must have unique names within the system. When an imported item has the same name as an
item already in the destination Oracle Enterprise Repository instance, then v2 is appended to the name of the new imported item. Each iteration of this
occurrence results in a new version of the item: v3, v4, and so on. If the name of an imported item is already appended with a Vn designation, then v2 is further
appended to that name.
■
Categorization Types merge data in the event of a destination Categorization Type of the same name. Categorizations in the source archive that are not present on the
destination system are added to the existing destination Categorization Type.
