Table of Contents:
- Objective
- Questionnaire
- Sources Endpoints Connection
- Target Endpoint Connection
- Users & IAM Configuration
- Integration Style
- Mapping Requirements
Key Takaways for Oracle Integration Cloud Requirements
• Successful Oracle Integration Cloud projects rely on gathering precise technical requirements using structured templates.
• Key data points must include source and target endpoint URLs, OAuth authentication credentials, and specific payload volume estimates (under 50MB for standard support).
• Security configuration requires defining IAM roles like ServiceAdministrator and ServiceDeveloper early in the project lifecycle.
• For on-premises connectivity, validation of the Connectivity Agent requirements (8GB RAM, JDK 17) is critical.
• Integration styles should be categorized immediately as App-Driven (real-time) or Scheduled (batch) to determine the correct license edition.
Objective
As many applications are now hosted on cloud, the need for integration/data synchronization is becoming essential.
Use cases known are ERP, CRM, Document Archiving, Project Planning, File Storage, Databases and many others.
While it is crucial to have it in-hand, data collection/gathering can be sometimes a tedious process.
This post provides the templates to gather main details about the integration project before you start your implementation. By sharing this with your client it can help in proper estimation of effort, time and cost and having the initial project phase mutually agreed with the least effort.
In some cases, the client for Oracle Integration Cloud might not (or be able to) provide answers to all of the questions in the template, however you will still be able to have more light about the general requirement.
Questionnaire for Oracle Integration Cloud Requirements
Sources Endpoints Connection
| Question | Answer |
|---|---|
| External Application Connection Source / Service Name | |
| On Premises / On Public Cloud / On Private Cloud Network | |
| Clustered (Yes / No) | |
| Adapter Exists in OIC standard / enterprise / NA | |
| Prerequisites Document exists (Y/N) | |
| ERP / HCM / IaaS / Productivity & Social / CX / Healthcare / Technology / SCM / Database / Enterprise Messaging | |
| Security Method: • User and Password • OAuth Authorization Credentials • Username password token with pgp key support • No security Policy (like in rest api) |
|
| Connection details: connection URLs | |
| Security tokens (Y/N) | |
| User Credentials | |
| Trigger Role / Invoke Role / Trigger & Invoke roles | |
| Is local agent required | |
| Access Type: Public Gateway / Private endpoint / connectivity agent | |
| Payload Limits |
Target Endpoint Connection(s)
| Question | Answer |
|---|---|
| External Application Connection Source / Service Name | |
| On Premises / On Public Cloud / On Private Cloud Network | |
| Clustered (Yes / No) | |
| Adapter Exists in OIC standard / enterprise / NA | |
| Prerequisites Document exists (Y/N) | |
| ERP / HCM / IaaS / Productivity & Social / CX / Healthcare / Technology / SCM / Database / Enterprise Messaging | |
| Security Method: User and Password / OAuth Authorization Code Credentials / Username password token with pgp key support | |
| Connection details: connection URLs | |
| Security tokens (Y/N) | |
| User Credentials | |
| Trigger Role / Invoke Role / Trigger & Invoke roles | |
| Is local agent required | |
| Access Type: Public Gateway / Private endpoint / connectivity agent | |
| Payload Limits |
Users – to be added to OCI IAM and to OIC
| Question | Answer |
|---|---|
| Number of users, names, emails and roles
Roles: |
|
| Network Connection | |
| Clustering |
Integration Style
To be defined/assigned as per each entity (table) also in the flowchart draft
| Question | Answer |
|---|---|
| Integration Style: • Application Driven • Event Driven • Scheduled Driven |
|
| Describe the event: | |
| Schedule (once / minute / hour / day…) |
Mapping
One of the key tasks to any integration is defining how data is transferred, or mapped, between two applications.
| Source | Data Type | Document Attached? | Transformation/Conversion Function | Destination | Data Type |
|---|---|---|---|---|---|
1.What are the system requirements for the Oracle Connectivity Agent?
The OIC Connectivity Agent requires a dedicated host (Linux OEL 7/8 or Windows Server 2016) with at least 8GB of RAM and 4GB of heap size dedicated to the JVM. It requires Oracle JDK version 17 (or 8 for older versions) and outbound access to port 443.
2.What is the payload size limit in Oracle Integration Cloud?
Oracle Integration Cloud enforces a 50 MB limit for structured payloads (JSON/XML) on cloud adapters. However, agent-based database adapters are restricted to 10 MB. Unstructured payloads (attachments) support up to 1 GB via MTOM/attachment streaming.
3.When is OIC Enterprise Edition required over Standard Edition?
You need the Enterprise Edition if your requirements include on-premises application adapters (such as Oracle EBS, SAP, JD Edwards, or Siebel) or if you require Process Automation (BPM) capabilities. The Standard Edition supports SaaS and technology adapters only.
4.What IAM roles are required for OIC developers?
Key Identity and Access Management (IAM) roles include ‘ServiceAdministrator’ for full access, ‘ServiceDeveloper’ for building integrations, ‘ServiceMonitor’ for tracking instances, and ‘ServiceInvoker’ for triggering endpoints. Assigning the correct granular role is critical for security compliance.
5.Does OIC require a VPN for on-premises integration?
No, a VPN is not required. The OIC Connectivity Agent functions by making an outbound connection from your on-premises network to OIC over standard HTTPS (Port 443). It polls for work requests, eliminating the need to open inbound firewall ports.
6.How are messages calculated for OIC licensing?
OIC licensing is often based on ‘Message Packs’. A single message is defined as a payload of 50 KB. If a payload is 150 KB, it counts as 3 messages. Synchronous and asynchronous flows both consume messages based on this 50 KB increment.
7.What are the prerequisites for an Oracle ERP Cloud connection?
Prerequisites include a valid Oracle Cloud account with IDCS or IAM enabled, the specific WSDL/Swagger URL for the service, and a service account with appropriate roles (e.g., ‘Integration Specialist’). For ERP Cloud, the ‘Interface Catalog URL’ is specifically required.
8.What are the different integration styles in OIC?
OIC supports three primary patterns: ‘App Driven Orchestration’ for real-time APIs (REST/SOAP), ‘Scheduled Orchestration’ for batch processing (FTP/File), and ‘File Transfer’ for moving files without logic. Choose ‘Publish/Subscribe’ for decoupled event-driven architectures.
9.How long does Oracle Integration Cloud retain instance logs?
Oracle generally retains instance trace data for 3 days for successful instances and slightly longer for faulted instances to aid debugging. For long-term retention requirements, data must be pushed to external storage or an Autonomous Database.
10.Does OIC support automatic retry for failed integrations?
Yes, OIC provides built-in error handling via ‘Global Fault Handlers’ and specific scopes. You can configure retry policies (e.g., retry 3 times with exponential backoff) directly in the integration canvas to handle transient network issues automatically.
