Oracle Integration Cloud
Integration is where enterprise programmes are won.
Application, scheduled and event-driven integrations on Oracle Integration Cloud, engineered with error handling, observability and CI/CD so they run for years, not just through go-live.
Source systems
- Oracle EBS
- Salesforce
- Banks
- Partners
- SFTP
- External APIs
Integration
Oracle Integration Cloud
Adapters · Orchestration · Events · B2B
Cloud services
- OCI
- Autonomous DB
- Object Storage
- Functions
- API Gateway
Enterprise applications
- Fusion ERP
- SCM
- HCM
Experiences
- Web
- Mobile
- Analytics
Overview
Oracle Integration, done properly.
Most OIC estates start well and decay. Integrations are built quickly, error handling is an afterthought, nobody can tell which flow failed last night, and every change is a manual export and import. AMTEX builds OIC the way we would build any production software: designed, versioned, tested, observable and deployed by pipeline.
We work across OIC Gen 2 and Gen 3, with Fusion ERP, HCM and SCM adapters, E-Business Suite, databases, SFTP, REST and SOAP endpoints, OCI services and the SaaS platforms enterprises rely on.
Technologies
- Oracle Integration Cloud
- REST APIs
- SOAP Web Services
- SFTP & File Integration
- OCI API Gateway
- OCI Streaming & Events
- OCI Functions
- Autonomous Database
- OCI Object Storage
- OCI Vault & IAM
- GitLab CI
- GitHub Actions
What we deliver
Capabilities
Everything AMTEX builds, configures and runs across Oracle Integration.
Application integrations
Real-time request and response flows between Fusion, EBS, CRM, e-commerce and partner systems using native adapters and REST.
Scheduled integrations
Batch extracts, FBDI/HDL loads, bank files and reconciliations with incremental processing and restartability.
Event-driven architecture
Fusion business events, OCI Streaming and Events driving downstream systems without polling.
REST & SOAP APIs
APIs designed and documented first, exposed through OIC and OCI API Gateway with authentication and throttling.
SFTP & file processing
Stage files, parse fixed-width and CSV at scale, encrypt with PGP, archive to Object Storage.
Fusion ERP, HCM & SCM adapters
Deep use of the Fusion adapters: business objects, events, BIP report calls, FBDI callbacks and HCM Extracts.
Database & EBS integrations
ATP, on-prem Oracle via connectivity agent, and EBS adapter for coexistence during migration.
OCI integrations
Functions for complex transforms, Object Storage, Vault, Notifications and Queue as part of the integration fabric.
Error handling
Global fault handlers, resubmission strategies, dead-letter patterns and business-readable error notifications.
Monitoring & observability
Tracking identifiers, OCI Logging and Monitoring dashboards, alerting on business SLAs rather than just technical failures.
Performance optimisation
Parallelism, paging, payload sizing and scheduling tuned against real volumes.
CI/CD
Integration export, versioning, environment-specific connections and promotion via GitLab CI or GitHub Actions using the OIC REST APIs.
Gen 2 to Gen 3 migration
Assessment, remediation of unsupported patterns, migration tooling and cut-over with rollback.
The hard parts
Where these projects become difficult
The places programmes slip, and what we do about each one.
- 01
Silent failures
The problem
Integrations fail overnight and nobody knows until the business notices.
How AMTEX approaches it
Fault handling on every flow, business-level alerts, a daily health summary and dashboards a support analyst can act on.
- 02
Environment drift
The problem
Test and production differ because changes were made by hand.
How AMTEX approaches it
Every integration lives in source control and is promoted by pipeline; connections are parameterised per environment.
- 03
Fusion API limits
The problem
Large extracts time out or hit throttling.
How AMTEX approaches it
BIP-based extracts for volume, REST for transactions, paging and incremental watermarks, tested at production scale.
- 04
Security
The problem
Credentials in plain connections, over-privileged integration users.
How AMTEX approaches it
OAuth 2.0 client credentials where supported, least-privilege integration roles, secrets in OCI Vault, certificate rotation planned.
- 05
Reliability
The problem
Duplicate processing after retries corrupts data.
How AMTEX approaches it
Idempotency keys, tracking variables, controlled resubmission and reconciliation reports.
Architecture
What a well-built OIC estate looks like.
Sources on top, OIC in the middle doing orchestration only, OCI services doing the heavy lifting, targets below.
Sources
- Fusion ERP / HCMBusiness events · REST · BIP
- E-Business SuiteEBS adapter · PL/SQL APIs
- External appsREST · SOAP
- SFTP / filesCSV · fixed width · PGP
Integration
Oracle Integration Cloud
App-driven · Scheduled · Event · B2B · Connectivity agent · Lookups · Libraries
Supporting OCI services
- ATP staging
- Functions (transforms)
- Object Storage (archive)
- Vault (secrets)
- Queue / Streaming
Targets
- SaaS platforms
- Partner systems
- API Gateway → apps
- Data warehouse
Engineering standards
Five concerns every integration must satisfy.
These are the review criteria for every integration we build or take over.
- One pattern per interface type: request/response, scheduled batch, event-driven, file exchange. Documented once, applied everywhere.
- Canonical models for the objects that cross many boundaries (supplier, invoice, employee, order), with source-specific maps at the edges.
- OIC orchestrates; heavy transforms go to Functions, staging to ATP, files to Object Storage. Each service does what it is good at.
- Projects and packages structured by business domain so ownership is obvious and deployments are scoped.
- OAuth 2.0 client credentials to Fusion and OCI services; basic auth only where a legacy endpoint leaves no choice, and then flagged for retirement.
- Dedicated integration users with least-privilege roles per system. No shared human accounts.
- Every credential and certificate referenced from OCI Vault. Rotation is a scheduled task, not an incident.
- PGP for files at rest and in transit with partners; TLS everywhere; payload logging redacted for personal data.
- Idempotent writes: tracking keys, upserts, check-before-create. Resubmission never duplicates.
- Typed business faults separate from technical faults, each with a defined handler and audience.
- Restartable batch processing with watermarks and chunking so a failure at record 40,000 resumes at 40,000.
- Volume testing against production-shaped data before go-live, not after the first month-end.
- Business identifiers as tracking variables on every instance, so monitoring speaks the business's language.
- OCI Logging and Monitoring dashboards per environment covering OIC, Functions and databases together.
- Alerts routed to owners with the record, the reason and the fix; repeated faults aggregated into digests.
- A daily health summary and SLA reporting on the integrations the business depends on.
- Integrations exported as IAR into Git; every change reviewed as a merge request.
- GitLab CI or GitHub Actions pipelines import, apply per-environment connection values from a vault, and activate via the OIC REST API.
- Lookups and libraries versioned alongside integrations; environment drift eliminated.
- Gen 2 to Gen 3 migration executed environment by environment through the same pipelines, with rollback.
How we work
From first conversation to steady state
01
Inventory
Every interface, its owner, its volume, its failure mode.
02
Design
Canonical models, patterns per interface type, error and monitoring standards.
03
Build
Integrations built to the standards, peer reviewed, tested with production-shaped data.
04
Operate
Pipelines, dashboards, runbooks and a support model that improves the estate each quarter.
Proof
Related work
FAQ
Common questions
Related solutions
Oracle Fusion Cloud ERP
Financials, Procurement, Projects and Order Management, implemented and extended with the integrations, reporting and automation a real enterprise needs around them.
Oracle Cloud Infrastructure
OCI architecture for the workloads that live around Fusion: Autonomous Database, Functions, API Gateway, Object Storage, networking, identity and observability, designed for security and high availability.
Process Automation & RPA
Oracle Process Automation for the human-task workflows around Fusion, and RPA for the steps that have no API: intake, approvals, exceptions, re-keying and legacy screens, orchestrated together through OIC.
Logging, Observability & Monitoring
OCI Logging, Logging Analytics, Monitoring, Application Performance Monitoring and Service Connector Hub, applied across OIC, OCI workloads and Fusion so one dashboard tells the truth about the whole estate.
Ready to make your integrations boring?
Boring means monitored, versioned and reliable. Let us look at your estate.