Introduction
On-Prem Connectivity Options with Oracle Integration Cloud is one of the most critical topics for any Oracle integration consultant working in hybrid environments. In real implementations, you rarely see organizations fully on cloud—most enterprises still run legacy systems (ERP, payroll, manufacturing, banking systems) on-premises while adopting Oracle Fusion Cloud for modern processes.
As a consultant, your responsibility is to securely connect Oracle Integration Cloud (OIC Gen 3) with these on-prem systems without exposing internal networks or compromising security. This is where understanding connectivity options becomes essential.
In this blog, we will go deep into all available on-prem connectivity methods in OIC, how they work architecturally, and how to implement them in real projects.
What is On-Prem Connectivity in Oracle Integration Cloud?
On-prem connectivity refers to the ability of Oracle Integration Cloud (OIC Gen 3) to securely communicate with systems hosted inside an organization’s internal network (behind firewall).
Typical examples include:
- On-prem Oracle EBS
- SAP ECC systems
- Legacy databases
- Internal REST/SOAP services
- File systems (FTP/SFTP servers)
Since these systems are not publicly accessible, OIC requires a secure mechanism to access them without opening inbound firewall ports.
Real-World Integration Use Cases
1. Fusion HCM to On-Prem Payroll System
A global organization uses Oracle Fusion HCM but runs payroll on-prem.
Requirement:
- Extract employee data from Fusion
- Send to on-prem payroll system
Solution:
- Use OIC + Connectivity Agent to push data securely
2. Oracle ERP to On-Prem Banking System
Finance team processes payments via on-prem banking software.
Requirement:
- Send payment files from ERP Cloud to bank system
Solution:
- OIC File Server + Connectivity Agent
3. Real-Time API Integration with Legacy System
Customer data stored in on-prem CRM.
Requirement:
- Real-time API call from Fusion to CRM
Solution:
- REST Adapter via Connectivity Agent
Architecture / Technical Flow
Let’s understand how OIC connects to on-prem systems:
Core Concept
OIC does NOT directly connect to your internal systems.
Instead, it uses a Connectivity Agent installed inside your network.
Flow:
- OIC sends request → Oracle Cloud
- Connectivity Agent (inside firewall) pulls request
- Agent communicates with on-prem system
- Response sent back via secure channel
Key Point
- Communication is outbound only
- No firewall inbound ports required
- Uses HTTPS secure tunnel
On-Prem Connectivity Options in OIC
1. Connectivity Agent (Most Common)
This is the primary and recommended approach.
Key Features:
- Installed on on-prem server
- Uses outbound HTTPS (port 443)
- Supports multiple adapters:
- DB Adapter
- File Adapter
- REST/SOAP Adapter
- FTP Adapter
When to Use:
- Most enterprise integrations
- Secure environments
- No inbound firewall changes allowed
2. VPN / FastConnect (Network-Level Connectivity)
Used when deeper network-level integration is required.
Key Features:
- Private connection between OCI and data center
- Low latency
- High bandwidth
When to Use:
- Large data transfers
- Real-time integrations
- Performance-critical systems
3. Public Endpoint Exposure (Least Recommended)
Expose on-prem APIs to internet via firewall.
Risks:
- Security concerns
- Maintenance overhead
When to Use:
- Temporary or low-risk scenarios
4. Private Endpoint (OIC Gen 3 Feature)
OIC Gen 3 supports private endpoints within OCI.
Key Features:
- OIC deployed inside VCN
- Access private resources directly
When to Use:
- OCI-based hybrid architectures
- Advanced enterprise setups
Prerequisites
Before setting up connectivity, ensure:
Infrastructure Requirements
- Java (for Connectivity Agent)
- On-prem server (Linux/Windows)
- Network access to target systems
Security Requirements
- Firewall allows outbound HTTPS (port 443)
- Proxy configuration (if required)
OIC Requirements
- OIC Gen 3 instance provisioned
- Access to Integrations console
Step-by-Step Build Process (Connectivity Agent Setup)
Step 1 – Download Connectivity Agent
Navigation:
OIC Console → Settings → Connectivity Agent
- Download agent installer
- Extract files
Step 2 – Install Agent
Run:
Provide:
- Agent Group Name
- OIC URL
- Credentials
Step 3 – Register Agent
After installation:
- Agent registers with OIC
- Visible under Agent Groups
Step 4 – Create Connection Using Agent
Navigation:
Integrations → Connections → Create
Example: REST Adapter
- Select “Use Connectivity Agent”
- Choose Agent Group
Step 5 – Configure Endpoint
Provide:
- Host (on-prem server IP)
- Port
- Authentication details
Step 6 – Test Connection
Click Test
Expected:
- Successful connection message
Testing the Technical Component
Example Scenario
Invoke on-prem REST API
Test Payload:
Expected Response:
Validation Checks
- Response received
- No timeout errors
- Logs show successful agent communication
Common Errors and Troubleshooting
1. Agent Not Showing in OIC
Cause:
- Registration failure
Fix:
- Check credentials
- Verify internet connectivity
2. Connection Timeout
Cause:
- Firewall blocking internal system
Fix:
- Allow agent to access target system
3. SSL Certificate Issues
Cause:
- Self-signed certificates
Fix:
- Import certificates into agent keystore
4. Proxy Issues
Cause:
- Corporate proxy blocking traffic
Fix:
- Configure proxy in agent settings
Best Practices from Real Implementations
1. Use Agent Groups
- Multiple agents for load balancing
- High availability setup
2. Separate Environments
- DEV, TEST, PROD agents
- Avoid cross-environment usage
3. Monitor Agent Logs
Location:
Track:
- Connectivity issues
- Errors
4. Secure Credentials
- Use OIC Vault
- Avoid hardcoding passwords
5. Use Private Endpoints for Advanced Use Cases
- Better security
- Reduced latency
Real Consultant Insight
In one banking implementation, we had:
- Fusion ERP Cloud
- On-prem payment gateway
Initially, client wanted to expose APIs publicly.
We redesigned using:
- Connectivity Agent
- Secure outbound communication
Result:
- Passed security audit
- Reduced risk exposure
- Improved reliability
Summary
On-prem connectivity in Oracle Integration Cloud is a foundational concept for hybrid integrations.
Key takeaways:
- Connectivity Agent is the most widely used approach
- No inbound firewall exposure required
- VPN/FastConnect used for high-performance needs
- Private endpoints enhance security in OIC Gen 3
- Proper setup and monitoring are critical for stability
As a consultant, mastering these connectivity patterns ensures you can handle real enterprise integration scenarios confidently.
FAQs
1. What is the safest way to connect OIC with on-prem systems?
The Connectivity Agent is the safest option as it uses outbound HTTPS communication and avoids exposing internal systems.
2. Can we use multiple connectivity agents?
Yes, you can configure multiple agents in a group for high availability and load balancing.
3. When should we use VPN instead of Connectivity Agent?
Use VPN/FastConnect when you need network-level connectivity, large data transfers, or low latency requirements.
For more detailed technical documentation, refer to Oracle official docs:
https://docs.oracle.com/en/cloud/paas/application-integration/index.html