ODI - Security component

• ODI security is used to secure any action performed by authenticated users against the design-time and run-time artifacts and components of Oracle Data Integrator.
• Security is built around users and profiles, to which security administrators grant methods (edit, delete, and so forth) on objects types (projects, models, interfaces, and so forth) or on specific object instances (Data warehouse Project, ODS Project, and so forth).
• All the security information for Oracle Data Integrator is stored in the master repository.

Security has the following components:

• "Objects, Instances and Methods"
• "Profiles"
• "Users"

Objects, Instances and Methods:

An Object is a representation of a design-time or run-time artifact handled through Oracle Data Integrator. 

For example, agents, models, datastores, scenarios, interfaces and even repositories are objects. Specific objects have a double name (Agent/Context, Profile/Method, and so forth). These objects represent links between objects. These links are also objects. For instance, Agent/Context corresponds to a physical/logical agent association made through the contexts. Privileges on this object enable to change this association in the topology.

An Instance is a particular occurrence of an object. For example, the Datawarehouse project is an instance of the Project object.

A Method is an action that can be performed on an object. Each object has a predefined set of methods.


Profiles

A Profile contains a set of privileges for working with Oracle Data Integrator. One or more profiles can be assigned to a user to grant the sum of these privileges to this user.

A Profile Method is an authorization granted to a profile on a method of an object type. Each granted method allows a user with this profile to perform an action (edit, delete, and so forth) on an instance of an object type (project, model, datastore, and so forth).

Methods granted to a profile appear under this profile in the Profiles accordion of the Security Navigator. When a method does not appear for a given profile, this profile does not have access to this method.

A method can be granted as a generic or non-generic privilege:

• A method granted as a generic privilege is granted by default on all the instances of this object.

• A method granted as a non-generic privilege is not granted by default on all object instances, but may be granted per instance.

Generic vs. Non-Generic profiles

Generic profiles have the Generic privilege option selected for all object methods. This implies that a user with such a profile is by default authorized for all methods of all instances of an object to which the profile is authorized.

Non-Generic profiles are not by default authorized for all methods on the instances since the Generic privilege option is not selected for all object methods. The administrator must grant the user the rights on the methods for each instance.

If the security administrator wants a user to have the rights on no instance by default, but wishes to grant the rights by instance, the user must be given a non-generic profile.

If the security administrator wants a user to have the rights on all instances of an object type by default, the user must be given a generic profile.

Built-In Profiles

Oracle Data Integrator has some built-in profiles that the security administrator can assign to the users he creates.

Build in profiles in details:

CONNECT - Profile granted with the basic privileges to connect Oracle Data Integrator. It should be granted with another profile.

DESIGNER - Profile granted with privileges to perform development operations. Use this profile for users who will work mainly on projects.

NG_DESIGNER - Non-generic version of the DESIGNER profile.

METADATA_ADMIN - Profile granted with privileges to manage metadata. Use this profile for users that will work mainly on models.

NG_METADATA_ADMIN - Non-generic version of the METATADA_ADMIN profile.

OPERATOR - Profile granted with privileges to manage run-time objects. Use this profile for production users.

REPOSITORY_EXPLORER - Profile granted with privileges to view objects. Use this profile for users who do not need to modify objects.

NG_REPOSITORY_EXPLORER - Non-generic version of the REPOSITORY_EXPLORER profile.

SECURITY_ADMIN - Profile granted with privileges to edit security. Use this profile for security administrators.

TOPOLOGY_ADMIN - Profile granted with privileges to edit the Topology. Use this profile for system or Oracle Data Integrator administrators.

VERSION_ADMIN - Profile granted with privileges to create, restore and edit versions and solutions. Use this profile for project managers, or developers who are entitled to perform version management operations.

NG_VERSION_ADMIN - Non-generic version of the VERSION_ADMIN profile.

Users:

A User is an Oracle Data Integrator user, and corresponds to the login name used to connect to a repository.

A user inherits the following privileges:

• All the privileges granted to its various profiles

• Privileges on objects and/or instances given to this user

To create the user:

Step1: In security navigator, expand users accordian and click new user.

Step2: provide the name, initials, password, expiry date, and privide the profile priviledges

Step3: Go to Authorization tab and select required objects or methods to grant the users.

Step4: Save and user will be created.

ODI - Oracle 12c database installation

 Steps:

Step1: Go to oracle site from google and download the file.

Step2: open it a d run setup in admin mode

Step3:oracle universal installer will start.

 

Step4: next

Step5: next

Step6: choose create and configure a databse.

Step7: choose Desktop class

Step8: use virtual account.

Step9: provide oracle db name . By default it is orcl

Step10: it checks all prerequisites

Step11: Install

Step12: it will install the db after certain period of time.

ODI - Import and Export techniques

Exporting and importing ODI objects means transferring objects between different repositories. When exporting an ODI object, an XML export file is created. ODI objects have dependencies that will also be exported in the XML export file. 

Exporting one ODI object:

Exporting one ODI object means export one single ODI object in order to transfer it from one repo to another.

Step1: select the object to be exported in the design tab and right click on the object and select export.

Step2: provide the export path, export name and "CHILD components export " this is very important checked it if you want to get the objects linked to the object to be exported. These objects are those visible under the exported object in the tree. And other options as required.

Export Multiple ODI objects:

We can export one or multiple objects at knce using the Export Multiple Objects action. This lets you export ODI objects to a zip file.

Step1: Select Export from the designer, Topology, Security or operator Navigator

Step2: In the export selection dialog, select Export Multiple Options

Step3: Provide directoy path, select Export as a zip file if needed or exported as .xml files directly in the directory. Drag and drop objects to be exported.

Smart Export and Import:

It is recommended to use the Smart Export and Import feature to avoid most of the common issues that are encountered during an export or import such as broken links or ID conflicts. The Smart Export and Import feature is a lightweight and consistent export and import mechanism providing several smart features.

The Smart Export automatically exports an object with all its object dependencies. It is particularly useful when you want to move a consistent lightweight set of objects from one repository to another and when you want to include only a set of modified objects, for example in a patching use case, because Oracle Data Integrator manages all object dependencies automatically while creating a consistent sub-set of the repository.

The Smart Import provides:

• Automatic and customizable object matching rules between the objects to import and the objects already present in the repository

• A set of actions that can be applied to the object to import when a matching object has been found in the repository

• Proactive issue detection and resolution that suggests a default working solution for every broken link or conflict detected during the Smart Import

Perform a smart export:

Step1: Select Export ... from Designer  Topology or Operator tab

Step2:  in the Export selection dialog, select Smart Export. Click ok

Note: This option is only available if you are connected with  a Work repo.

Step3: in the smart export dialog  specify the export parmeters:

Export directory and export file name

Export as Zip.

To Encrypt file

Encoding options: keep default.

Step4: In the Dependencies section, drag and drop the objects you want to add to the smart export from ODI into the selected Objects list on the left. 

The objects to export appears in a tree with all its related parent child objects that are required to support.

Step5: Modify the list of objects to export.

Step6: click export to start the export process

Importing an ODI object:

Step1: In the Navigator, select the object or object node under which you want to import the object. Right click the object and select import and select the type of object to import.

Step2: in the import dialog, select the import type and enter file import directory and select the files to import.

Perform a smart import:

Step1: select import... from the designer, topology or operator tab

Step2: In the import selection dialog, select Smart import. Click ok.

Step3: The smart import wizard opens. In 1st step, select the file and response file(optional).

Step4: In 2nd step, Import actions, verify the result of the matching process and fix eventual issues.

In the Object Match Details section, expand the nodes in the import object column to navigate to the objects available to import during the smart import.

In the Action column, select the action to peform on the object.

MERGE

OVERWRITR

CREATE COPY

REUSE

IGNORE

In the repository Object column, select the required repo objects.

Check the issue details table and to fix any issue, select Action to perform in the Action Column.

Possible actions to fix issues:

Ignore

Change

Do not change

Fix link

Step5: Review the import file name and eventual issues and click Finish.

ODI - Topology steps and model creations

 Step1: Create Repository connection

Step2: Go to Physical architecrure and choose 1 technology for example Oracle and new data server.

Step3: provide db connection details

Step4: provide jdbc details.

Step5: right click on the created data server and create new physical schema.

Step6:provide schema and work schema details. Context part we have to do once we created the logical schema.

Step7: Create context

Step8: create new logical schema

Step9: and map context to physical schema

Step10: Now go to design and tab create new model based on logical schema. And reverse enggineer to get all the datastores.

ODI - Reusable mappings

Reusable mappings allow us to encapsulate a multi step integration or a portion of an integration into a single component which we can save and use as any other components in our mappings. Reusable mappings are a convenient way to avoid the labor of creating a similar or identical subroutine of data manipulation that we will use many times in our mappings.

Steps:

Step1: Projects - Reusable mappings - New reusable mapping. - ok.

Step2: Create new mapping and drag and drop the reusable component and add source to resuable component and outputs to target.