Redwood Documentation

Product Documentation

 

You are currently viewing the legacy RunMyJobs documentation site. This site will be taken down later this month.
All current and future RunMyJobs documentation, including versions 2023.3 and later, can be found here.
Please update your bookmarks. Use the version dropdown menu to select the documentation you need.

›Privileges Required

Separate ComponentsGeneric Components

Catalog

  • Catalog

Connectors

  • Connections
  • Azure Subscriptions
  • Azure DataFactory
  • JSCAPE Component
  • IBM z/OS
  • Box Connector
  • Boomi
  • Databricks
  • Sharepoint
  • Informatica
  • Cognos
  • ServiceNow

Inbound REST

  • REST Services
  • API Key

Excel

  • Generic Excel Components

Platform Agent

  • Core Platform Functions

Oracle Data Services

  • Oracle Data Integrator

SAP Data Services

  • BTP Cloud Integration
  • SAP CI DS
  • SAP IBP
  • BusinessObjects
  • SAP SNC

SLA

  • SLA Component Installation
  • SLA Rules
  • SLA Dashboard
  • Advanced Configuration

On-Premises SSO

  • SSO Module

Privileges Required

  • Azure Subscriptions
  • Box Connections
  • Boomi
  • Databricks
  • Catalog
  • Connections
  • Azure Data Factory
  • Sharepoint
  • Informatica
  • REST Services
  • JSCAPE Connector
  • API Keys
  • Excel
  • ODI Connections
  • Queues
  • CloudIntegration Connections
  • HCI DS Connections
  • IBP Connections
  • SLA
  • ServiceNow
  • z/OS Connections
← ExcelQueues →

Privileges Required to use SAP ODI Connections

To use ODI Connection, you need one of the following:

  • scheduler-administrator or redwood-administrator role.
  • scheduler-user or redwood-login role in combination with the following system-wide, partition-wide or object-level privileges.

Built-in Roles

  • The scheduler-administrator or redwood-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.

See Also

  • ODI Connector Component
  • Privileges Required to use Applications
  • Privileges Required to use Objects
← ExcelQueues →
  • Built-in Roles
  • Creating and Modifying ODI Connections
  • Using the ODI Component
  • Deleting ODI Connections
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |