Key Points:

1. Service Viewer: Can view resources but cannot edit or invoke

integrations.
2. Service Invoker: Can invoke integrations through SOAP or REST
APIs but cannot access the OIC Console or design anything.
3. Service User: Combines the Viewer and Invoker roles. Can view
and invoke integrations.
4. Service Monitor: Can monitor the runtime state of integrations,
but cannot view design-time details or invoke integrations.
5. Service Developer: Can create, edit, and delete integrations and
resources, and can invoke integrations at runtime. Cannot access
administrative settings.
6. Service Administrator: Has full access to the OIC console, can
create, edit, test, and administer integrations, and can invoke
anything through APIs.
The Service Developer role is most commonly needed for those creating
or editing integrations in OIC.
Key Points:
1. Unified Workspace: Projects offer a central place to design, manage,
and monitor integrations, reducing the need to navigate multiple pages.
2. Efficient Reuse: Once integrations are created, components like
connections and libraries can be reused, speeding up the development
process for new integrations.
3. Deployment Management: Projects allow for easy deployment
management, helping with versioning and export to different
environments.
4. Role-based Access Control: You can control who can view, edit, and
monitor integrations using RBAC, ensuring security and organization.
5. Accelerators: Pre-built integrations from Oracle or third-party integrators
can be easily customized within projects, accelerating development.
6. Three Sections of a Project: Design (create and access integrations),
Deploy (group and export integrations), and Observe (monitor the
performance and status of integrations).
7. Streamlined Process: Projects make it easier to manage integrations,
monitor their status, and perform release management, ultimately
keeping everything more organized and efficient.
Oracle now recommends creating integrations within projects, as it helps
manage the entire lifecycle of integrations—from design and deployment to
monitoring—making it the most organized and efficient way to work in OIC.
OIC Connection Resource Setup – Checklist
🔧 Before You Start:
 Identify the adapter you need (e.g., REST, SOAP, NetSuite, FTP, DB, etc.)
 Review Oracle documentation for prerequisites:
o Endpoint URLs

o Required credentials (username/password, OAuth, etc.)

o Roles and permissions needed in the external system

o SSL certificate (if needed)

o Confidential client setup in OCI (if required)

 For on-premise targets, install the OIC connectivity agent

🔗 Creating the Connection:
 Select the adapter in OIC
 Provide:
o Connection name

o Identifier (auto-generated or custom)

o Description (optional but helpful)

 Choose the role:

o Trigger

o Invoke

o Both (if supported by the adapter)

🔐 Configure Properties:
 Fill in connection-specific properties (depends on adapter)
 Choose and set security policy
 Input security details (user credentials, keys, OAuth info)
✅ Final Step:
 Test the connection
 Fix any errors based on logs or error prompts

📊 Table Summary

Step Description

Adapter Selection Choose correct adapter, check documentation

Documentation Review Review endpoint URL, roles, SSL, OAuth, etc.

Step Description

On-Prem Setup (if

Install OIC connectivity agent
needed)

Connection Details Name, identifier, description

Role Assignment Choose Trigger, Invoke, or Both

Adapter-specific setup (e.g., endpoint, schema

Connection Properties
name, etc.)

Security Configuration Set security policy and provide credentials

Test Connection Validate everything works; troubleshoot errors

Reuse Connection Use in one or many integrations as needed

1. Connection Resource = reusable configuration that allows OIC to

connect to external systems (e.g., databases, SaaS apps).
2. A connection is created using an adapter, which must meet
prerequisites (documented in Oracle docs).
3. One connection can serve multiple integrations, but you might need
multiple connections for the same app if:
o Different credentials or roles are required

o They are project-specific (non-global)

4. Each connection can have Trigger, Invoke, or both roles depending on

use case and adapter.
5. Setting up includes:
o Selecting adapter

o Naming the connection

o Setting connection & security properties (adapter-specific)

o Testing the connection

6. Some integrations with on-premise systems require installing the OIC

Connectivity Agent.
7. Not all adapters support both roles – some only allow invoke.
8. Access to systems and actions like uploading SSL certificates may need
admin privileges.
OIC Adapters – Role & Features
🔧 At Design-Time:
 Uses a configuration wizard on the OIC Integration Canvas
 May create a temporary connection to discover:
o Business objects

o Services/events

o Tables, views, stored procedures (for DBs)

 Simplifies configuration of SaaS/on-prem systems

🕒 At Runtime:
 Creates a secure physical connection between OIC and the external
system
 Handles session management and error handling (standard/custom)
 Adapts protocols/transports without user needing to manage
complexity

🔍 Types of Adapters (Trigger vs Invoke)

Adapter
Use Case
Role

Initiates the integration (via interface, event, or

Trigger
message)

Invoke Calls an external application or service

📚 Adapter-Specific UI & Functionality

 Shows supported operations (e.g., create, update, query)
 Offers event subscriptions for trigger-based adapters
 Provides business object catalogs for many SaaS apps
 Supports native query languages for some platforms (e.g., Salesforce)

Built-in Adapter Library

 100+ prebuilt adapters (Cloud, on-prem, DBs, FTP, REST, SOAP, etc.)
 Updated list and documentation available at the Oracle Help Center – OIC
Adapters

✅ Key Takeaways
 Every connection is built on an adapter
 Connections can be:
 o Trigger (source)

o Invoke (target)

 Adapters provide both design-time convenience and runtime

management
General Steps for Creating a Connection
1. Select Adapter (e.g., Oracle ERP Cloud, Salesforce, Database).
2. Provide a Unique Name and Role (Invoke or Trigger).
3. Define Connection Properties (e.g., host URL, instance type).
4. Set Security Properties (authentication method like OAuth or
username/password).

Oracle Fusion Cloud Applications (ERP, HCM, CX)

 Connection Property: Hostname URL of the instance.
 Security Options:
o OAuth (Authorization Code Credentials) – requires setup.

o Username & Password.

 For File Upload to UCM: Option to upload PGP encryption keys.

☁️Other Oracle Cloud & On-Prem Apps

 Each has unique security policies and connection details.
 Refer to adapter documentation for specific requirements.

🔄 Salesforce Adapter
 Connection Properties:
o Instance type (Production/Sandbox/Government).

o API version.

o Custom domain (mandatory for Government Cloud).

 Security Options:
o Username & Password.

o OAuth (Authorization Code or Resource Owner Credentials).

ServiceNow Adapter
 Connection Property: Instance name URL.
 Security Options:
o Username & Password.

o OAuth (Authorization Code or Resource Owner).

🛒 Shopify Adapter
 Connection Properties:
o Hostname, API version.

o Comma-separated connection IDs (required for Trigger role).

 Security Options:
o Username & Password.

o Access Token (Admin API).

o Shopify Security Policy (Username + Password + Shared Secret).

🧮 Oracle Autonomous Databases (ATP, ADW)

 Pre-req: Download client credentials wallet.
 Security Policies:
o JDBC over SSL: Upload wallet + provide wallet password + DB
user credentials.
o JDBC with OCI Signature: Wallet + Object Storage credentials +
DB user.
o JDBC Basic Auth: Use info from tnsnames.ora + DB user
credentials.

Other Oracle Databases (Cloud/On-Premise)

 Use:
o Oracle Wallet policy, or

o Username-Password Token policy (tnsnames.ora required).

 For on-premise, need a connectivity agent.

🧱 Microsoft SQL Server

 Connection Property: SQL Server instance info from administrator.
 Security Policy: Username-Password Token only.
 Connectivity: Requires connectivity agent (on-prem or cloud network).

📌 Key Reminders
 Each adapter has unique connection and security requirements.
 Always check prerequisites before configuring.
 Refer to adapter documentation for exact setup details.
 Trigger roles often need additional configuration, like connection IDs
(Shopify).

Let me know if you want these points in a downloadable or visual format!

🔐 Connection & Security Properties – Part 2

1. Messaging Systems
🟠 OCI Streaming Service
 Availability: Easily accessible if you or someone with permission
provisions a stream in OCI tenancy.
 Stream Bootstrap URL: Includes the OCI region.
 Security Policy: Only SASL (Simple Authentication and Security Layer) is
used.
 Username Format:
bash
CopyEdit
tenancy_name/oci_username/stream_pool_OCID
 Password: OCI authentication token generated for the user.
 Optional: Upload a JKS (Java Key Store) file with TrustStore generated
from the root certificate using keytool.
 Documentation: Adapter documentation provides detailed steps.
 Trigger Role Requirement: Must be associated with an installed
connectivity agent.

🟠 External Kafka Messaging System

 Cluster Info: May include multiple bootstrap servers; provide host &
port for each.
 Security Similarity: Similar to OCI Streaming only if SASL/SSL is used.
 Username Format: Defined by the target system.
 Security Options:
o SASL Plain over SSL

o No Security Policy (if permitted by system)

 Trigger Role Requirement: Must be associated with a connectivity

agent.

🟦 Azure Event Grid

 Prerequisites:
o Find subscription ID, API version, and create resource group.

o Register an application in Azure portal.

o Obtain client ID, client secret, and tenant ID.

 Trigger Role Requirement:

o Add shared secret from Azure.

o Click “Provide Consent” button to authorize OIC.

 Access Type:
o Connectivity agent required if private network.

o Otherwise, public gateway is sufficient.

2. Social & Productivity Adapters

🟢 Eventbrite Adapter
 Supported Role: Only Invoke.
 Prerequisites:
o Create Eventbrite application management account.

o Get application key.

o OIC Admin must upload Eventbrite public certificate to OIC.

 Security Policies:
o Generic OAuth: Requires security token.

o Custom Policy: Requires client ID (application key) and secret

(security token).

🟢 Google Calendar Adapter

 Supported Role: Only Invoke.
 Prerequisites:
o Create Google account and project.

o Enable Calendar API under library section.

o Create OAuth client credentials to get client ID and secret.

o Define scope: Full access or read-only.

o OIC Admin must upload GeoTrust Global CA certificate.

🟢 Slack Adapter
 Security Policy: One custom policy.
 Prerequisites:
o Sign up for a Slack developer account.

o Create an OAuth app.

o Slack auto-generates client ID and client secret.

o Add one or more OAuth scopes for required operations.

o Review Slack documentation for scope details.

3. Generic Technology Adapters

🧩 REST Adapter
 Roles:
o Invoke: Call external REST service.

o Trigger: Define REST endpoint for integrations.

🧩 SOAP Adapter
 Roles:
o Invoke: Call SOAP service using WSDL.

o Trigger: Define SOAP-based integration interface.

🧩 FTP Adapter
 Role: Only Invoke – used to upload/download files from FTP/SFTP.
🧩 File Adapter
 Requires: Always used with OIC connectivity agent.
 Roles:
o Invoke: Read/write to on-premises file system.
 o Trigger: Agent polls for new files to process in integration.

These technology adapters are widely used and will be covered in detail in
future lessons.

4. Testing Connections
 Status: Connections stay in Draft status until successfully tested.
 How to Test: Click Test (next to Save).
 Duration: A few seconds to a couple of minutes.
 Errors: Usually due to invalid credentials or wrong connection
details.
 After Fixing Errors: Click Test Again.
 Successful Test: Connection becomes Configured and usable in
integrations.

✅ Final Recommendations
 Ensure all prerequisite tasks are completed by authorized users.
 Review each adapter's official documentation thoroughly.
 Properly configure security settings before attempting to test or use a
connection in OIC.

Here are all the important points from the lesson on defining connections
using the generic SOAP technology adapter in Oracle Integration Cloud
(OIC), with nothing skipped:

🔹 Two High-Level Use Cases for SOAP Adapter

1. Trigger Role:
o Used to design an interface based on a WSDL that integration
clients will call.
2. Invoke Role (more common):
o Used to access external SOAP-based web services from within your
integration.
🔸 Note: SOAP adapter supports only HTTP-based SOAP; other transport
protocols (like JMS or SMTP) are not supported.

🔹 SOAP Adapter in the Invoke Role

✅ Capabilities:
 Sends SOAP payload to the external endpoint.
 Receives and processes the response in the integration.
✅ Payload Limits:
 Structured XML payload:
o 100 MB limit (cloud).

o 50 MB limit (via on-premises connectivity agent).

 MTOM attachments (binary/non-binary content): up to 1 GB.

✅ Header Support:
 Supports HTTP and SOAP headers:
o Standard headers.

o Custom headers (in both request and response).

✅ Security Options:
1. SSL over HTTP (default).
2. Two-way SSL (if client certificate required).
3. Security Policies:
o Username/password in HTTP or SOAP header.

o OAuth:

 Client Credentials.
 Authorization Code.
o No security policy (if service doesn’t require one).

🔸 Optional security section used only if credentials must be sent in SOAP

body or HTTP header instead of default SOAP header.

🔹 Message Exchange Patterns Supported:

 Synchronous (Request-Response).
 One-Way Request.
 Asynchronous Request with Callback (uses SOAP addressing header).

🔹 Dynamic Endpoint Support

 Adapter supports dynamic discovery of endpoints based on runtime
logic.
 Useful when endpoint varies and needs to be set programmatically.
🔹 Configuration Steps Summary:
1. Name the connection.
2. Select role: Invoke.
3. Provide WSDL:
o Enter URL.

o Or upload the WSDL file.

4. Choose security policy:

o OAuth (client credentials or auth code).

o Username/password.

o No security.

5. Access Type:
o Public Gateway (default, for internet-accessible services).

o Private Endpoint (must be set up by OIC admin for private

network).
o Connectivity Agent (used if service is in a private cloud or on-
premises).