Internal Identifiers IDs Import and Export Concepts

19-6 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator Import Mode Choose the import mode carefully. See Section 19.1.3, Import Modes for more information.

19.2 Exporting and Importing Objects

Exporting and importing Oracle Data Integrator objects means transferring objects between different repositories. When exporting an Oracle Data Integrator object, an XML export file is created. ODI objects have dependencies, as described in Section 19.1.2, Relationships between Objects . These dependencies will be exported in the XML export file. The content of this XML file will depend on the export method you will use: ■ Exporting an Object with its Child Components ■ Exporting an Object without its Child Components The choice will depend on your goal, if you need to do a partial export then the Export Without Child Components is the one to use. The Export Multiple ODI Objects feature is useful when you need to regularly export the same set of Objects. Once the export has been performed, it is very important to choose the import strategy to suite your requirements. Exporting an Object with its Child Components This option is the most common when you want to export an object. It allows you to export all subcomponents of the current object along with the object itself. When an Object is exported with its child components, all container-dependent Objects – those which possess a direct parentchild relationship - are also exported. Referenced Objects are not exported. For example, when you choose to export a Project with its child components, the export will contain the Project definition as well as all objects included in the Project, such as Folders, Interfaces, Procedures, Packages, Knowledge Modules, Variables, Sequences, Functions, etc. However, this export will not contain dependent objects referenced which are outside of the Project itself, such as Datastores and Columns, as defined previously in Section 19.1.2, Relationships between Objects . Only the numeric ID references of these Objects will be exported. Exporting an Object without its Child Components This option can be useful in some particular situations where you would want to take control of the import process. It allows you to export only the top-level definition of an object without any of its subobjects. For example, if you choose to export a Model without its children, it will only contain the Model definition but not the underlying Sub-models and Datastores when you import this model to a new repository. Partial ExportImport If you have a very large project that contains thousands of interfaces and you only want to export a subset of these to another work repository, you can either export the entire Project and then import it, or choose to do a partial manual exportimport as follows: ExportingImporting 19-7 1. Export all Models referenced by the sub-items of your project and import them in “Synonym mode” in the new repository to preserve their IDs 2. Export the Project without its children and import it in “Synonym mode”. This will simply create the empty Project in the new repository with the same IDs as in the source. 3. Export every first level Folder you want, without its children, and import them in “Synonym mode”. The empty Folders will be created in the new repository. 4. Export and Import all Markers, Knowledge Modules, Variables, Sequences, etc. that are referenced by every object you plan to export, and import them in “Synonym mode”. Refer to section “Import in “Synonym Mode” or Duplication and Impact on Object IDs” for special caution regarding import of Knowledge Modules in Synonym Mode. 5. Finally, export the Interfaces you are interested in and import them in “Synonym mode” in the new repository.

19.2.1 Exporting one ODI Object

Exporting one Oracle Data Integrator Object means export one single ODI object in order to transfer it from one repository to another. To export an object from Oracle Data Integrator: 1. Select the object to be exported in the appropriate Oracle Data Integrator Navigator. 2. Right-click the object, and select Export... If this menu item does not appear, then this type of object does not have the export feature. 3. In the Export dialog, set the Export parameters as indicated in Table 19–2 . Table 19–2 Object Export Parameters Properties Description Export Directory Directory in which the export file will be created. Export Name Name given to the export Child Components Export If this option is checked, the objects linked to the object to be exported will be also exported. These objects are those visible under the exported object in the tree. It is recommended to leave this option checked. Refer to Exporting an Object with its Child Components for more details. Note that when you are exporting a Load Plan, scenarios will not be exported even if you check this option. Replace exiting files without warning If this option is checked, the existing file will be replaced by the ones of the export. If a file with the same name as the export file already exists, it will be overwritten by the export file. Advanced options This set of options allow to parameterize the XML output file format. It is recommended that you leave the default values. XML Version XML Version specified in the export file. Parameter .xml version in the XML file header. ?xml version=1.0 encoding=ISO-8859-1?