Connecting Oracle EBS with Oracle Fusion SaaS : Using OIC Connectivity Agent & Integrated SOA Gateway
If you're running Oracle E-Business Suite (EBS) on-premises and Oracle Fusion SaaS in the cloud, you're not alone — and neither is the challenge of getting them to talk to each other reliably. Most organizations we work with have spent years building out EBS for Finance, HR, Supply Chain, and Order Management. Now they're layering Fusion HCM, Fusion Finance, or Fusion SCM on top and need seamless data flow between the two.
The Architecture: Understanding the Big Picture
Before touching any configuration,
it helps to understand why these two components exist and how they fit
together.
OIC lives in Oracle Cloud. Your
EBS lives behind your firewall on-premises (or on a private cloud). By default,
Oracle Cloud cannot reach your EBS environment — firewalls, private networks,
and security policies prevent it. That's the problem both components solve, in
different ways.
OIC Connectivity Agent is a lightweight Java process you install on your EBS
server or a server within your network. It creates a secure outbound tunnel
from your network to OIC. Because the connection is outbound, you don't need to
open any inbound firewall ports — a major operational advantage. OIC channels
integration traffic through this tunnel to reach your on-premises EBS.
Integrated SOA Gateway (ISG) is a component built into EBS that exposes EBS business
functions as REST or SOAP web services. This is important: instead of OIC
writing directly to EBS database tables — which bypasses business logic,
validations, and security — it calls standard EBS APIs through ISG. Your data
integrity stays intact, EBS security is respected, and your integrations remain
upgrade-safe.
Put them together and you get a
clean, secure, end-to-end integration pipeline:
Oracle Fusion SaaS
←→ OIC ←→ OIC
Agent ←→
ISG ←→ EBS
This architecture is monitored,
reusable, and built to grow. Whether you're connecting one Fusion module today
or ten applications tomorrow, the foundation is the same.
Setting Up the OIC Connectivity Agent
Here's what you need and how to
get it running:
FOR additional info on OIC and ISG Setup instructions,please refer our blog : Setting UP OIC Connectivity Agent & Integrated SOA Gateway
•
Java 17 on the server
(Amazon Corretto 17 is a solid free option)
•
Outbound internet access on
port 443
•
An active OIC instance
provisioned in Oracle Cloud
1.
Create an Agent Group in
OIC Console. Go to Settings → Agents and create a new
group (e.g. EBS_AGENT_GROUP). Note the Agent Group Identifier.
2.
Get your IDCS OAuth
credentials. From your IDCS console, find your OIC
application under Oracle Cloud Services → OAuth Configuration. You'll need the
Client ID, Client Secret, and Primary Audience.
3.
Download and configure
the agent. Download the installer ZIP from OIC Console
(Settings → Agents → Download). Extract it and edit InstallerProfile.cfg with
your OIC runtime URL, Agent Group Identifier, IDCS URL, Client ID, Client
Secret, and scope (built from your Primary Audience value).
4.
Run the installer. Execute java -jar
connectivityagent.jar. When you see "Agent Started Successfully" —
you're connected. Register it as a Linux systemd service so it restarts
automatically on reboot.
Setting Up Integrated SOA Gateway (ISG)
ISG ships with EBS but needs a
one-time configuration before it's ready to serve APIs to OIC:
6.
Run ISGRestSetup.pl. This is Oracle's
official script for configuring ISG REST services. Run it as the oracle OS user
— and critically, use the EBS-bundled Java (not Java 17). You'll be prompted
for your APPS password and WebLogic admin credentials. A successful run ends
with: Configuration script completed successfully.
7.
Deploy EBS APIs. Log into EBS and
navigate to the Integrated SOA Gateway responsibility → Integration Repository.
Search for the API you need — for example, HZ_PARTY_V2PUB for Customer/Party
data or PER_EMPLOYEES for HR. Set a Service Alias and click Deploy. First
deployments can take 15–30 minutes.
8.
Grant API access. On the Grants
tab, grant access to the EBS user that OIC will authenticate as. This step is
easy to overlook and will block your integration if skipped.
9.
Test before you build. Use a direct curl
call against the deployed API endpoint to confirm it responds correctly. Don't
start building in OIC until this test passes cleanly.
The Payoff
Once both components are in place,
you have a reliable, governed integration layer between EBS and any Oracle Fusion
SaaS module. New employee hired in EBS? It flows to Fusion HCM automatically.
Customer record updated? Synced to Fusion Finance without a batch job. Purchase
order created? Visible in Fusion SCM in near real time.
The days of custom batch programs
and fragile point-to-point code are behind you. OIC with the Connectivity Agent
and ISG gives you integrations that are visual, monitored, error-handled, and
ready to scale.
Integration. Insight. Innovation.
Website:https://www.bizinsightinc.com/contactus
Contact:inquiry@bizinsightinc.com
