Importing and Exporting Solutions

ExportingImporting 19-5

19.1.4 Tips for ImportExport

This section provides tips for the import and export operations. Repository IDs As a general rule, always use different internal IDs for your repositories in order to avoid any ID conflicts. Import Reports The import report is displayed after every import operation. It is advised to read it carefully in order to determine eventual errors of the import process. The import report gives you details on the: ■ Import Mode ■ Imported Objects . For every imported object the object type, the original object name, the object name used for the import, the original ID, and the new, recalculated ID after the import is given. ■ Deleted Objects . For every deleted object the object type, the object name, and the original ID is given. ■ Created Missing References lists the missing references detected after the import. ■ Fixed Missing References lists the missing references fixed during the import. You can save the import report as an.xml or .html file. Click Save... to save the import report. Missing References In order to avoid missing references, use solutions to manage dependencies. See Section 18.4, Working with Solutions for more information. Import Replace This import mode replaces an already existing object in the target repository by one object of the same object type specified in the import file. This import mode is only supported for scenarios, Knowledge Modules, actions, and action groups and replaces all children objects with the children objects from the imported object. Note the following when using the Import Replace mode: If your object was currently used by another ODI component like for example a KM used by an integration interface, this relationship will not be impacted by the import, the interfaces will automatically use this new KM in the project. Warnings : ■ When replacing a Knowledge module by another one, Oracle Data Integrator sets the options in the new module using option name matching with the old modules options. New options are set to the default value. It is advised to check the values of these options in the interfaces. ■ Replacing a KM by another one may lead to issues if the KMs are radically different. It is advised to check the interface’s design and execution with the new KM. Import Mode Description 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: