ODI 12c - Use unique temporary object name

When ODI loads data from source table or datastore to Staging table, it stores to C$_default table then from there it sends the data back to Target table or datastore.

If we want to use unique object name like the unique staging area C$_12unique...default table then we have to go to mapping - physical tab and select option - "Use Unique Temporary object names".

ODI - Import OOTB Knowledge modules

By default, ODI will provide us few of the Global Knkwledge modules. Apart from that, we can also import Oracle provided KMs.

Steps to import:

Step1: Go to your created project and right click on the Knowledge modules object and traverse the following directory and select the required KMs and  press ok 

Path: C:\Oracle\Middleware\Oracle_Home\odi\sdk\xml-reference

ODI 12c - Model creations with constraints

Here, We will create a primary key constraints on dept no. On dept model datastore.

Steps:

Step1: Create a model folder.

Step2: provide folder name

Step3: right click on the created folder and create new model.

Step4: provide model name, technology, logical schema and agent if any and save.

Step5: Go to Reverse engg for masking if any

 

Step6: Go to selective reverse engg and select objects to revers engg and select tables as needed and click reverse engg.

 

Step7: tables will be created.

Step8: Expand dept data store and click on Constraints and new key

Step9:select primary key

Step10: go to attributes and select deptno

Primary key created. This key will be created in ODI level not on db level.

To create db level key, go to control of the constraint and select defined in the database.

ODI 12c - Scheduling ODI load plans

Implementation Steps:

Step1: Locate the ODI load plan you created. And expand your load plan by clicking on the + sign next to the name of the load plan.  This can be found within the “Load Plans and Scenarios” tab. Highlight the “Scheduling” option and right mouse click..  Then select New Scheduling.

Step2: Within the definition tab you, you will need to enter in execution options such as, “Context, Agent, and Log Level.”  Once you have entered that you will need to select a Status. Here in our example we will leave this “Active.”  Once you have selected your status, then you will need to enter you execution options.  Here you will need to select when you want your load plan to run.  Once the following definitions have been set, click the save button. 

Step3: Next you will need to click on the “Topology” tab and expand the “Agents” listed under the “Physical Architecture” sub tab. Select the agent in which you are using to execute your load plan.  Then highlight and right mouse click.  Here a list of options will appear in which you will need to select “Update Schedule.”  This will update the ODI agent to reflect your scheduled changes.

In addition, to make sure your ODI load plan has been added to the ODI scheduler you can view the scheduler by selecting the “View Schedule” when highlighting and right mouse clicking the ODI agent.

ODI - Create Model and Topology objects using Wizard option

 Implementation steps: 

Step1: Go to Design tab and Models Accodian and click the folder sign and New Model and Topology Objects.

Step2: provide Model name, select technology , Logical Schema name and context.

Step3: provide Data server details like Name, User, password, driver, url etc. Next and test connection.

Step4: Provide Physical schema nane, db schema names.

Step5: Model will be created.

Step6: Go to Reverse Enginner and do mask for selecting tables if you need.

Step7: Go to selective Reverse engg a d select objects to reverse engg.

Step8: Datastores tables will be created. Just right click on any table and click view data

ODI - Move file using OdiFileMove command

OdiFileMove: Use this command to move or rename files or a directory into files or a directory.

Here, I have created two referesh variables and one to store source path and another to store archive path. Now connect these two variables with OdiFileMove cmd to move files from source to target.

Once this package created, then create a scenario and run and check in operator tab for execution status.

For more details on cmd and paramters:

https://docs.oracle.com/middleware/1213/odi/reference/opentools.htm#BEIBHCBC

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.