Privileges Required to use SAP ODI Connections
To use ODI Connection, you need one of the following:
scheduler-administrator
orredwood-administrator
role.scheduler-user
orredwood-login
role in combination with the following system-wide, partition-wide or object-level privileges.
Built-in Roles
- The
scheduler-administrator
orredwood-administrator
built-in role provides full control over all ODI connections.
Creating and Modifying ODI Connections
You need all of the following privilege ranks to be able to create and modify ODI connections:
- View - on partitions GLOBAL and REDWOOD.
- View - on applications GLOBAL.Redwood and REDWOOD.DataIntegrator.
- View - on the Redwood_DataIntegrator extension point.
- View - on the Redwood_Connections extension point.
- View - on the existing ODI process server and queue, if applicable.
- Create - on process server and queue if a new process server and queue are required.
- Edit - on ODIConnection.
Using the ODI Component
You need all of the following privilege ranks to be able to use an ODI connection:
- View - on partitions GLOBAL and REDWOOD.
- View - on application REDWOOD.DataIntegrator.
- View - on the Redwood_ODI extension point.
- Edit - on ODIConnection. This object is modified when the token gets updated.
- View - on the Redwood_ODIConnectionConstraint constraint definition.
- View - on Redwood_ODI library.
- Submit - on process definitions Redwood_DataIntegrator_RunLoadPlan and/or Redwood_DataIntegrator_RunScenario (depending on the functionality you want).
- View - on the process server of the ODI connection.
- JobAdministrator - on queue the queue of the ODI component.
Deleting ODI Connections
- View - on partitions GLOBAL and REDWOOD.
- View - on applications REDWOOD.ODI and REDWOOD..
- View - on the Redwood_ODI extension point.
- View - on the Redwood_Connections extension point.
- Edit - on ODIConnection.