Skip to content

Enterprise connectivity

Integration Architecture

Keep the business process moving across systems.

Decide when a caller needs an answer, when a consumer can catch up, and how the business will know that every transaction arrived.

Explore integration patterns ↓
A cloud application deck and an on-premises systems deck connected to user channels and industrial assets. Cloud2CloudUser2CloudThing2CloudOnPremise2CloudUser2OnPremiseThing2OnPremiseOnPremise2OnPremise
Integration domains inspired by SAP ISA-M

What has to cross the system boundary?

Business outcome

Does the caller need a confirmed posting, a receipt for later processing or a periodic balance? Each answer implies a different contract.

Authority

Identify who creates the business key, which system can change the record and when downstream teams may rely on it.

Failure window

Agree how long work can wait, how operators detect a gap and who can authorize replay or correction.

Choose the exchange pattern.

Use the timing of the business decision to compare four ways to exchange information.

Request / Reply

A customer needs an order number before leaving checkout.

Interface contract
Define what the response confirms and how long the caller can wait.
Recovery design
After a timeout, look up the original request by its business key before submitting again.

Business Event

Several consumers need to know that a sales order has been accepted.

Interface contract
Publish a stable event identity and define the meaning of the committed change.
Recovery design
Track consumer lag and deduplicate deliveries before applying business effects.

Queued Command

A warehouse can accept a fulfillment instruction later.

Interface contract
Name the receiving owner and distinguish queue acceptance from business completion.
Recovery design
Separate transient failures from rejected instructions and assign a resolution queue.

Batch / File

A partner settles transactions at the end of each business day.

Interface contract
Agree the cutoff, time zone, file schema, delivery window and control totals.
Recovery design
Detect missing or repeated files and reconcile rejected rows before closing the period.

Give each platform a clear role.

SAP integration

Evaluate SAP Integration Suite for SAP-facing flows. Check the available interfaces, mappings and monitoring against the actual business contract.

Enterprise services

Place API access policies and event distribution with the teams that operate the enterprise gateway and broker. Agree where transformation belongs.

End-to-end ownership

Carry a correlation identifier across hops. Give support teams a way to trace a business key from the sender through delivery to the receiving application.

Architecture Deliverables

Architecture in Practice

The order posted. The reply timed out.

The sales channel retains the request key. Support can check the SAP order reference before allowing a retry, reducing the risk of creating a second order.

A legacy feed crosses the cutover window.

Agree a final extraction watermark, drain pending messages and reconcile counts and values. Activate the replacement route once the receiving team confirms the boundary.

From order to fulfillment

Sales order accepted

Request / replyReturn the order number to the sales channel.
Business eventNotify fulfillment after the order commits.
ReconciliationMatch accepted orders to fulfillment records.