What are the ODI Security Profiles ?

Answer:- 



Profile 

A profile represents a generic rights model for working with Oracle Data Integrator. One or more profiles can be assigned to a user.



Predefined profile types



1) CONNECT :-Minimum generic profile for connecting to Oracle Data Integrator. All users must have at least this profile.



2) DESIGNER:-Generic profile for Mapping developers, or users working on the Mappings. This profile give access to any project and project sub components (folders, Mapping , knowledge modules, etc.) stored in the repository. It also authorize users to perform journalizing actions (start journal, create subscriber, etc.) or to run static controls over models and datastores.



3) METADATA ADMIN :- Generic profile for users responsible for managing models and reverse-engineering. Users having this profile are allowed to browse any project in order to select a CKM, RKM or JKM and to attach it to a specific model.



4) OPERATOR :-Generic profile for operators. It allows users to browse execution logs.



5) REPOSITORY EXPLORER :- Generic profile for meta-data browsing through Metadata Navigator. It also allows scenario launching from Metadata Navigator.



6) SECURITY ADMIN :- Generic profile for administrators of user accounts and profiles.



7) TOPOLOGY ADMIN :- Generic profile for users responsible for managing the information system topology. Users granted with this profile are allowed to perform any action through the Topology Manager module.



8) VERSION ADMIN :- Generic profile for managing component versions as well as solutions. This profile must be coupled with DESIGNER and METADATA ADMIN.



9) NG DESIGNER :- Non-Generic profile for DESIGNER.



10) NG METADATA ADMIN :- Non-Generic profile for METADATA ADMIN.



11) NG REPOSITORY EXPLORER :-Non-generic profile for meta-data browsing through Metadata Navigator.



12) NG VERSION ADMIN :- Non-generic profile for VERSION ADMIN. It is recommended that you use this profile with NG DESIGNER and NG METADATA ADMIN.



Generic vs Non-Generic profiles :-

Generic profiles have the Generic privilege option checked for all objects' methods. This implies that a user with such a profile is by default entitled for all methods of all instances of an object to which his profile is entitled.



Non-Generic profiles is not by default entitled for all methods on the instances, as the Generic privilege option is unchecked for all objects' methods. The administrator must grant the user the rights for the methods for each instance.



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



If an administrator wants a user to have the rights on all instances of an object type by default, he must grant the user with a generic profile.



The following operations are possible on a profile:

• Creating a new profile


• Assigning a profile to a user


• Assigning an authorization by profile


• Deleting an authorization by profile


• Removing a profile from a user


• Deleting a profile