Working with Versions Oracle Fusion Middleware Online Documentation Library

Working with Version Management 18-7 1. In Designer Navigator or Operator Navigator, from the Solutions toolbar menu select New Solution.

2. In the Solutions editor, enter the Name of your solution and a Description.

3. From the File menu select Save.

The resulting solution is an empty shell into which elements may then be added.

18.4.1 Working with Elements in a Solution

This section details the different actions that can be performed when working with elements of a solution. Adding Elements To add an element, drag the object from the tree into the Elements list in the solution editor. Oracle Data Integrator scans the cross-references and adds any Required Elements needed for this element to work correctly. If the objects being added have been inserted or updated since their last checked in version, you will be prompted to create new versions for these objects. Removing Elements To remove an element from a solution, select the element you want to remove in the Elements list and then click the Delete button. This element disappears from the list. Existing checked in versions of the object are not affected. Rolling Back Objects To roll an object back to a version stored in the solution, select the elements you want to restore and then click the Restore button. The elements selected are all restored from the solutions versions.

18.4.2 Synchronizing Solutions

Synchronizing a solution automatically adds required elements that have not yet been included in the solution, creates new versions of modified elements and automatically removes unnecessary elements. The synchronization process brings the content of the solution up to date with the elements projects, models, etc stored in the repository. To synchronize a solution: 1. Open the solution you want to synchronize.

2. Click Synchronize in the toolbar menu of the Elements section.

3. Oracle Data Integrator scans the cross-references. If the cross-reference indicates that the solution is up to date, then a message appears. Otherwise, a list of elements to add or remove from the solution is shown. These elements are grouped into Principal Elements added manually, Required Elements directly or indirectly referenced by the principal elements and Unused Elements no longer referenced by the principal elements. 4. Check the Accept boxes to version and include the required elements or delete the unused ones.

5. Click OK to synchronize the solution. Version creation windows may appear for

elements requiring a new version to be created. You should synchronize your solutions regularly to keep the solution contents up-to-date. You should also do it before checking in a solution version. 18-8 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

18.4.3 Restoring and Checking in a Solution

The procedure for checking in and restoring a solution version is similar to the method used for single elements. See Section 18.2, Working with Versions for more details. You can also restore a solution to import scenarios into production in Operator Navigator or Designer Navigator. To restore a scenario from a solution:

1. Double-click a solution to open the Solution editor.

2. Select a scenario from the Principal or Required Elements section. Note that other

elements, such as projects and interfaces, cannot be restored.

3. Click Restore in the toolbar menu of the Elements section.

The scenario is now accessible in the Scenarios tab. Note that you can also use the Version Browser to restore scenarios. See Restoring a version with the Version Browser .

18.4.4 Importing and Exporting Solutions

Solutions can be exported and imported similarly to other objects in Oracle Data Integrator. ExportImport is used to transfer solutions from one master repository to another. Refer to Chapter 19, ExportingImporting for more information. Note: When restoring a solution, elements in the solution are not automatically restored. They must be restored manually from the Solution editor. 19 ExportingImporting 19-1 19 ExportingImporting This chapter describes how to manage export and import operations in Oracle Data Integrator. An introduction to the import and export concepts is provided. This chapter includes the following sections: ■ Section 19.1, Import and Export Concepts ■ Section 19.2, Exporting and Importing Objects ■ Section 19.3, Repository-Level ExportImport ■ Section 19.4, Exporting the Technical Environment

19.1 Import and Export Concepts

This section introduces you to the fundamental concepts of export and import operations in Oracle Data Integrator. All export and import operations require a clear understanding of the concepts introduced in this section.

19.1.1 Internal Identifiers IDs

Before performing export and import operations, it is essential to understand in detail the concept of internal identifiers ID in Oracle Data Integrator. To ensure object uniqueness across several work repositories, ODI uses a specific mechanism to generate unique IDs for objects such as technologies, data servers, Models, Projects, Integration Interfaces, KMs, etc.. Every object in Oracle Data Integrator is identified by an internal ID. The internal ID appears on the Version tab of each object. ODI Master and Work Repositories are identified by their unique internal IDs. This RepositoryID of 3 digits must be unique across all work repositories of an ODI installation and is used to compute the internal ID of an object. The internal ID of an object is calculated by appending the value of the RepositoryID to an automatically incremented number: UniqueNumberRepositoryID If the Repository ID is shorter than 3 digits, the missing digits are completed with 0. For example, if a repository has the ID 5, possible internal IDs of the objects in this repository could be: 1005, 2005, 3005, ..., 1234567005. Note that all objects created within the same repository have the same three last digits, in this example 005. This internal ID is unique for the object type within the repository and also unique between repositories for the object type because it contains the repository unique ID. This mechanism allows to: