Home Stays
The ERP and the legacy stack keep running. Integration is the layer that connects them to the channels.
Application integration
The core stays. The systems start talking to each other.
Oracle, SAP, Banner, or a legacy system is not rewritten to connect a process. MC3D takes the layer that already joins them. The flow is written down, it can be followed, and it stops breaking into manual tasks.
It is written down
The process can be followed, audited, and resumed. It does not live in an email or a spreadsheet.
It lands on top
A new channel or application joins the integration that is already there. It does not start from zero.
On what already runs
Integration fits the ecosystem
The solution is built on the platform the client already has, not the other way around.
Oracle
OIC, SOA Suite, BPM Suite, Process Cloud, Visual Builder, and Data Integrator.
SAP and the crossing
SAP Integration Studio, and the point where Oracle ERP Cloud has to meet SAP.
Bus
Mule, Apache Camel, ServiceMix, Red Hat Fuse, OpenESB, and Azure Hub Connector.
Process
Camunda, Bonita, Bizagi, Signavio, Intalio, and Orchestra.
Custom
Java, .NET, Python, or Node.js when the suite does not include the connector the flow needs.
What changes
Continuity, not only a connection
Between areas
Fewer manual tasks and fewer breaks from one system to the next.
Traceability
The information that moves can be followed and audited.
Response
Less rework and less waiting between the business and technology.
Evolution
A new process or channel comes in without rebuilding the base.
On the premises
AIRE leaves the process in BPEL 2.0
When the process has to stay next to the operation, AIRE writes it and, when needed, administers it on the engine.
It is edited without the engine
The BPEL is built as a tree: sequence, flow, invoke, decision, scope, and compensation. Apache ODE is not required to create it or to review it, and it is not opened as raw XML.
It runs when it is time
AIRE connects to Apache ODE to see processes and instances. It does not replace Oracle or SAP. The explicit process stays beside the suite that already runs. From Falcon it opens as integrate applications.
In operation
The same layer, in telecommunications.
At Entel, SOA Suite and BPM carried the integration of Oracle ERP Cloud with SAP. The core was not rewritten. It was connected.