Allowing Non-Administrators to Execute Jobs in the Pipeline

As a service administration, you can allow non-administrators to execute an individual Pipeline job type using proxy administrator user credentials for which they have process ownership. Optionally, you can manage which Pipelines a non-administrator can see on the Data Integration home page by the location(s) assigned to them in Location Security.

If the user executing a job is a non-administrator and no proxy administrator user credentials are specified, the system executes all jobs as non-administrator users. In this case, only jobs that do not require a service administrator to execute them, are included in the jobs run in the Pipeline, for example, an integration job. If jobs require an service administrative to execute them and a non-administrator without a proxy administrator user credentials attempts to execute them, then the Pipeline process fails.

Location Security is an additional framework in which service administrators can secure access to the Pipeline. When Location Security is enabled, Data Integration evaluates the user groups by location to which a non-administrator has been assigned and determines the following view access:

• When location security is enabled, non-administrators can view Pipeline jobs in ready-only mode (cannot edit or create a Pipeline) and run individual jobs in the Pipeline based only on the users groups by location to which they have been assigned in Location Security. (The service administrator can create, edit, and run any job type in the Pipeline.)

  For more information about location security, see Defining Location Security in Administering Data Management for Oracle Enterprise Performance Management Cloud .

• When location security is not enabled, non-administrators can view all Pipeline jobs in read-only mode (cannot edit or create a Pipeline) and run any individual job in the Pipeline. (The service administrator can create, edit, and run any job type in the Pipeline.)

To create a proxy server user credential:

1. From the Data Integration page, then the Actions menu, select System Settings.

2. From the System Settings page, then in the Enable Pipeline Execution for Non-Admin, select Yes.

   This setting enables non-administrator users to view Pipelines on the Data Integration home page

3. Click Save.

4. From the Data Integration home page, click (Create), and then select Pipeline.

5. From the Create Pipeline page, complete the following:

   • Pipeline Code—specify the user-assigned code for the Pipeline.

     The code can contain up to 30 alphanumeric characters with a minimum of 3 characters and a maximum of 30 characters. This code cannot be updated after a Pipeline is created. Use the pipeline code to execute the Pipeline using a REST API.

   • Maximum Parallel Jobs—When jobs are run in parallel mode, specify the maximum number of jobs to run in parallel mode

     When jobs are run in parallel mode, at runtime, the system runs jobs together in parallel (not sequentially). You can enter between 1 to 25 jobs to run in parallel mode.

6. In Location, specify a new location or select an location to associate with the Pipeline.

   Note:

   The name of the location selected for the Pipeline cannot be the same as a name of a location selected for an integration.

7. In Proxy User, enter the username with the service administrator role.

   If the username is different from the current username, then the system prompts the user to enter the password.

   For information on how roles are defined in the Oracle Enterprise Performance Management Cloud, see Overview of Access Control in Administering Access Control for Oracle Enterprise Performance Management Cloud.

   If the Proxy User name is the same name as the service administrator, the system does not prompt for a password.

8. In Proxy Password, enter the password for the proxy user.

9. Click Save and Continue.