OIC · Fusion · Intermediate
Oracle Integration Cloud: Building Integrations That Survive Production
Nineteen modules, nineteen labs, and an integration delivered end to end
Building an integration is the easy part. Making one that still works after a credential rotates, a payload changes shape, the network drops mid-call and somebody reruns it twice — that is the job, and it is what this course is about. For the consultant or developer who has outgrown point-to-point calls and now has to connect Fusion to systems that were not designed to talk to it. It assumes you know what a REST call is; it does not assume you have seen OIC.
Live cohort · registration open
Live teaching starts 21 December 2026
One hour daily, Sunday to Thursday · 19:00 Riyadh, 18:00 Cairo · 9 weeks
Taught live by an Oracle consultant, with every session recorded for anyone who misses one. Places are limited — we teach these in small groups so questions get answered.
Your access starts the day you enrol, not the day the cohort starts. The written lessons, the quizzes and the final assessment open straight away, so you can come to the first session having already read the ground.
The sessions run online, and the joining details reach you by email before the first one.
Watch a free lesson
All free lessons in this course · 9 free lessons
EGP 8,625EGP 11,500Save 25%
175 lessons · 298 min
Buying for a team? See seat pricing.
Bundle · save 25%
Oracle Technical Track
All 4 courses together for EGP 34,500 instead of EGP 46,000.
Includes
- Oracle Fusion Technical: Reports, Data, Integrations and Extensions
- Oracle Integration Cloud: Building Integrations That Survive Production
- Oracle Apps DBA: Keeping E-Business Suite Alive
- Oracle Visual Builder: Applications That Outlive Their First Release
Who this is for
- Integration developers and consultants who have outgrown point-to-point calls.
- Technical leads connecting Fusion to systems that were never designed to talk to it.
- Anyone who has built an integration that worked once and then broke on a credential rotation, a changed payload or a retry.
What you will be able to do
- Decide whether a requirement needs OIC at all, and say so before the licence is bought.
- Build and secure connections to Fusion, to a database, and to a partner over FTP.
- Map between two schemas that disagree, and prove the mapping with data that is not the happy path.
- Design an integration that is safe to retry, so a duplicate payment is impossible rather than unlikely.
- Handle faults so a failure is visible, recoverable and attributable within minutes.
- Promote an integration between environments without carrying test endpoints into production.
- Monitor a live estate and answer "did it run, and did it work" without opening the design.
- Read an OIC quarterly update for the two things that actually break integrations.
What you should know first
- You know what a REST call is and can read JSON and XML without looking things up.
- You have seen at least one Fusion implementation, or have taken the Fusion Technical course.
- An OIC instance you can build in. A trial works for everything except the environment-promotion module, which needs two.
- No prior OIC, SOA or middleware experience is assumed.
What you will cover
Watch a free lesson
1. Module 0 · Orientation
What this course covers, what the Fusion Technical course already covered, and how to get an instance you can build in.
4 lessons8 min
2. Module 1 · What OIC is, and when you need it
The decision module, and the honest half of it. Most requirements do not need an integration platform, and recommending one that is not needed is a real failure.
8 lessons16 min
3. Module 2 · The console and your first integration
Getting something working end to end in one sitting, so the rest of the course has something concrete to improve.
9 lessons18 min
4. Module 3 · Connections and adapters
A connection is a credential plus an endpoint plus a contract. Getting these right is most of what makes an estate maintainable.
11 lessons22 min
5. Module 4 · The Fusion adapter in depth
The adapter you will use most. It hides a great deal, and knowing what it hides is the difference between a fast build and a long afternoon.
12 lessons24 min
6. Module 5 · Mappings and transformations
FLAGSHIP. Where two systems that disagree are reconciled. A mapping error does not fail — it posts wrong data with every appearance of success.
14 lessons28 min
7. Module 6 · Orchestration patterns
Putting several calls in an order, with branching and state. Where OIC earns its licence, and where an orchestration becomes a program nobody can maintain.
11 lessons22 min
8. Module 7 · Scheduled integrations and file handling
Most real integration is files on a schedule. Unglamorous, and where the majority of production incidents actually come from.
10 lessons20 min
9. Module 8 · Error handling, faults and retries
FLAGSHIP. Every integration fails eventually. Whether that is a five-minute recovery or a week of reconciliation is decided here, at design time.
13 lessons26 min
10. Module 9 · Idempotency and duplicate prevention
Its own module because this is where money gets paid twice. Every integration is retried eventually, by a scheduler, a partner, or a person clicking resubmit.
9 lessons18 min
11. Module 10 · Business events and publish/subscribe
Reacting to something happening, rather than asking repeatedly whether it has. Cheaper, faster, and harder to reason about when it fails.
8 lessons16 min
12. Module 11 · Lookups, libraries and reuse
Keeping the things that change out of the things that do not. Small module, and the difference between an estate you can maintain and one you rebuild.
7 lessons14 min
13. Module 12 · Security: credentials, certificates and network
FLAGSHIP. An integration holds credentials to several systems at once, which makes it the most valuable thing in the estate to compromise.
10 lessons21 min
14. Module 13 · Monitoring, tracking and alerting
Answering "did it run, and did it work" without opening the design. The module that decides whether you find out about a failure before the client does.
10 lessons20 min
15. Module 14 · Performance and throughput
What happens when the volume is ten times the demo. Mostly a design question, and almost never solved by tuning afterwards.
8 lessons16 min
16. Module 15 · Testing an integration properly
Integrations are hard to test because half the system belongs to somebody else. What to do about that, rather than testing the happy path and hoping.
8 lessons17 min
17. Module 16 · Environments and promotion
FLAGSHIP. Moving an integration from test to production. The module where a mistake sends live data to a test endpoint, or the reverse.
10 lessons20 min
18. Module 17 · Quarterly updates and OIC
OIC updates, and so does everything it talks to. Two calendars, and the integrations sit between them.
7 lessons14 min
19. Module 18 · Capstone: one integration, delivered
A realistic brief taken from requirement to handover, with every module in this course applied where it belongs.
6 lessons12 min