Middleware-Free, Bi-Directional File Integration Between Oracle OTM and a Custom ERP
A US-based manufacturer needed a cost-effective way to integrate Oracle OTM Cloud with its custom ERP system (Decade) to streamline shipping operations without middleware. CES delivered a bi-directional, XML-based batch integration using a shared directory and reverse proxy, enabling secure file exchange, operational control, and order reprocessing.
Scroll down for the whole story
The Challenge
the client
Manufacturing (Sinks, Faucets, Kitchen Cabinetry)
Technology Stack
- Oracle OTM Cloud
- Custom ERP (Decade)
- XML
- Shared Directory
- Reverse Proxy Scripts
Solution Area
- Oracle OTM–ERP Integration for Shipping Operations
the impact
Streamlined Shipping Operations
Cost-Effective XML Integration
Secure, Controlled File Exchange
Order Reprocessing on Demand
The shift was integration-led. The result?
Controlled, cost-effective shipping execution.
The Need
The manufacturer needed a reliable, batch-mode integration between Oracle OTM Cloud and its custom ERP system to support day-to-day shipping operations. Leadership wanted a file-based model that could exchange shipping data in both directions, avoid the cost and complexity of middleware, support guaranteed delivery, and ensure secure connectivity between the cloud-based TMS and the on-premise ERP.
Challenges
- Cloud OTM Integration Without Middleware: The organization needed to integrate Oracle OTM Cloud with an on-prem custom ERP (Decade) without introducing a middleware platform, while still maintaining control and traceability.
- Bi-Directional, Batch File Exchange Requirements: Shipping information had to move in both directions between systems on a periodic, batch basis, requiring a consistent file format and reliable orchestration of inbound and outbound flows.
- Guaranteed Delivery and Security Constraints: The design needed one-time guaranteed delivery of messages and a secure way to connect the on-premise environment to Oracle OTM in the cloud, without exposing internal systems.
CES implemented a shared-directory, XML-based batch integration between Oracle OTM Cloud and the custom ERP to enable secure, bi-directional shipping data exchange without middleware.
Shared Directory Model
- Intermediate shared directory enabled batch file exchange between Oracle OTM and ERP.
- Eliminated the need for middleware and enabled reliable, periodic processing.
Oracle OTM → ERP Inbound
- Oracle OTM dropped shipping files into the shared directory.
- ERP programs picked up and processed data into Decade.
ERP → Oracle OTM Outbound
- ERP generated XML files for outbound data.
- Files stored in the shared directory for Oracle OTM consumption.
Security & Connectivity Controls
- Reverse proxy enabled secure cloud-to-on-prem access.
- Credentials stored within programs; only shipping data exchanged.
Operational Control & Reprocessing
- Supported order-level reprocessing in batch mode.
- Maintained reliability without changing integration design.
- Streamlined Shipping Operations – Oracle OTM and the custom ERP now exchange shipping information reliably in batch mode, improving day-to-day execution.
- Cost-Effective Integration Model – XML-based, file-driven integration avoided middleware licensing and reduced overall integration spend.
- Secure, Controlled Connectivity – Reverse proxy and in-program credentials addressed security concerns while maintaining connectivity between cloud and on-premise systems.
- Bi-Directional Data Exchange – Shipping data moves between Oracle OTM Cloud and the ERP in both directions, supporting complete transportation workflows.
- Reprocessing on Demand – The ability to reprocess individual orders improved operational control and reduced the impact of exceptions.
