Introduction: Oracle Integration Cloud (OIC) Gen 3 comes with several roles that define what users can do in the system. These roles ensure that only the right people have access to specific features. Service Administrator sets up OIC for a company, creating user roles and configuring settings.
1. Service Administrator
This role gives full control over everything in OIC.
- Set up and manage integrations, processes, and applications.
- Adjust system settings and assign user permissions.
Example: factory manager see that everything, assign tasks, and ensure operations run smoothly.
Can be used IT admins team managing the platform.
Note: Only the Service Administrator will have the access to the service screen as they manage things of the project instance and assign the tasks
In a Project the role Service administrator is assigned to preferable the Integrations Leads
Service Administrator Screen
2. Service Developer
This role is for building integrations and automating workflows.
- Create integrations, like connecting a customer database to a billing system.
- Set up APIs and process flows.
Change system-wide settings or manage other users.
Can be used Developers or technical consultants solutions.
Note: Service Developers screen does have the SETTINGS in the list as they are having only access to develop the integrations but not to manage the OIC instance
Service Developer Screen
3. Service Monitor
This role focuses on keeping track of how things are running.
- View logs, check integration performance, and identify issues.
- They can’t make any changes or fix problems themselves.
- Focuses on monitoring and troubleshooting integrations
- Can view the dashboards and activity streams but cannot create or manage integrations
Example: A security guard watching over the factory. They monitor everything and report issues but don’t operate the machines.
Can be used Support teams or people responsible for monitoring system performance.
4. Service User
This is for people who need to use OIC features but don’t build or manage anything.
- Access APIs or integrations provided to them.
- Run reports or trigger pre-built workflows.
Example: A business user using a dashboard to view sales data or run a report. They don’t create the system but use it for their tasks.
Can be used by Business users or anyone consuming OIC’s services.
5. Service Invoker
This role allows users or systems to trigger specific actions in OIC.
- Call APIs or run integrations, usually for automated tasks.
Can be used by Automated systems or scripts that need to trigger OIC actions.
Conclusion
By using these right roles to the right people, Oracle Integration Cloud (OIC) makes it easier to manage your system securely and efficiently.
- Service Developer builds an integration that connects a sales CRM to an invoicing tool.
- Service Monitor checks if the integration is running smoothly and alerts the team if there are errors.
- Service User accesses a dashboard to run a report using that integration.
- Service Viewer reviews the setup but doesn’t make changes.
- Service Invoker (like a script or app) triggers the integration automatically when new sales data is entered.
Integration Styles in Oracle Integration Cloud (OIC)
Oracle Integration Cloud (OIC) supports various integration styles to meet different business needs. Here are the main styles simplified for easy understanding:
1. Basic Routing
Moves data directly from one system to another without any changes. Ideal when data formats and protocols match.
Example: Sending data from a CRM to a database without modification.
2. Orchestration
Coordinates multiple systems to complete a task involving several steps or logic.
Example: Processing an order across inventory, payment, and shipping.
3. Publish/Subscribe
Sends a single message to multiple systems subscribed to a topic.
Example: Sharing a price update from ERP to all e-commerce platforms.
4. Batch Data Integration
Transfers large amounts of data periodically instead of real-time.
Example: Updating customer records nightly between systems.
5. Real-Time Synchronization
Keeps systems updated instantly with the latest data.
Example: Syncing inventory between an online store and a warehouse.
