Oracle Integration Service Roles
Oracle Integration predefined roles govern access to various Oracle Integration features.
For details on what you can do in each Oracle Integration feature by service role, see Oracle Integration Roles and Privileges.
About the Roles
The following table lists the predefined roles available in Oracle Integration, and the general tasks that users assigned the roles can perform. You can assign one or more of these roles to Oracle Integration users and groups.
| Oracle Integration | Description |
|---|---|
|
ServiceAdministrator |
A user with the ServiceAdministrator role is a super user who can manage and administer the features provisioned in an Oracle Integration instance. |
|
ServiceDeveloper |
A user with the ServiceDeveloper role can develop the artifacts specific to the features provisioned in an Oracle Integration instance. For example, a user assigned the ServiceDeveloper role can develop process applications in Process Automation, whereas the same user can design integrations in Integrations. |
|
ServiceMonitor |
A user with the ServiceMonitor role can monitor the features provisioned in an Oracle Integration instance. For example, the user can view instances and metrics, find out response times, and track whether instance creation completed successfully or failed. This role provides privileges for users with limited knowledge of Oracle Integration, but with high-level knowledge of monitoring it. This user role does not grant permissions to change anything. The ServiceMonitor role does not have any privileges in File Server, and Visual Builder. |
|
ServiceDeployer |
A user with the ServiceDeployer role can publish the artifacts developed in a feature. This role is not applicable for the Integrations feature. The ServiceDeployer role does not have any privileges in File Server, B2B for Oracle Integration, and Visual Builder. |
|
ServiceUser |
A user with the ServiceUser role has privileges to utilize only the basic functionality of a feature such as access to the staged and published applications. For example, in Integrations the user can navigate to resource pages (such as integrations and connections) and view details, but can’t edit or modify anything. The user can also run integrations. |
|
ServiceInvoker |
A user with the ServiceInvoker role can invoke any
integration flow in an Oracle Integration instance that is
exposed through SOAP/REST APIs or a scheduled integration. See
Run an
Integration Flow. A user with ServiceInvoker role
cannot:
The ServiceInvoker role does not have any privileges in Process Automation, File Server, B2B for Oracle Integration, and Visual Builder. |
|
ServiceViewer |
A user with the ServiceViewer role can navigate to all Integration resource pages (for example, integrations, connections, lookups, libraries, and so on) and view details. This user cannot edit any resources or navigate to the administrative setting pages. The ServiceViewer role does not have any privileges in Process Automation, File Server, B2B for Oracle Integration, and Visual Builder. |
Privileges Vary by Technology or Service
In Oracle Integration, you assign a role to a group. All users in the group are granted that role for all the technologies and services in an instance. However, each role grants different privileges for each technology or service. For example:
- For the Integrations technology, users can design integrations.
- For the Process Automation service, users can develop process applications.
Some predefined roles give access for only some features. For details on the privileges that each role grants, see Oracle Integration Roles and Privileges.