Messaging and events

Put partner transactions on the messaging backbone you already run

Many enterprises move data between applications through message queues and event streams. ECOM's B2B gateway publishes partner transactions to those platforms and consumes messages from them, so orders, ship notices and invoices reach your applications in real time instead of waiting for batch files.

Talk to an EDI/API Expert Request a Demo

Summary: Messaging and Event Integration

  • Messaging integration connects applications through a message broker or event platform.
  • Many enterprises move data between applications through message queues and event streams.
  • What ECOM covers: Publish and consume, Transformation in the flow, Error handling.
  • What you gain: Real-time partner data, Decoupled systems, Use what you already run.
  • Next step: talk to an EDI/API expert about your trading partners, documents and systems.
Discuss messaging integration

At a glance

  • Publish and consume
  • Transformation in the flow
  • Error handling

What is messaging integration?

Messaging integration connects applications through a message broker or event platform. One system publishes a message, such as a new order, to a queue or topic, and other systems consume it when they are ready, which decouples applications and lets data flow in near real time.

Outcomes

What you can expect

01

Real-time partner data

Partner transactions reach applications as they arrive, rather than in periodic batch files.

02

Decoupled systems

Applications and partners can change independently, because the broker sits between them.

03

Use what you already run

The gateway connects to your existing messaging platform instead of introducing another one.

Approach

How ECOM delivers it

  • Publish and consume

    Partner documents are published to queues or topics, and outbound documents are created from consumed messages.

  • Transformation in the flow

    Messages are transformed between EDI and the JSON, XML or other payloads your applications use.

  • Error handling

    Messages that fail validation or delivery are held and reported, so nothing is silently lost.

Platforms

Messaging and event platforms

Platforms the B2B gateway connects to. The client libraries, versions and connection settings are confirmed during scoping.

More platforms

Enterprise event brokers

Scenarios

Common scenarios

Orders into an event-driven ERP landscape

Retail purchase orders are published to Kafka topics that order management and warehouse systems consume.

Mainframe and IBM MQ estates

Partner documents are delivered to IBM MQ queues that existing enterprise applications already read.

Cloud applications

Partner data flows to applications in AWS, Azure or Google Cloud through their managed messaging services.

Frequently asked questions

Can partner EDI documents be published to Kafka or IBM MQ?

Yes. The B2B gateway transforms partner documents into the message payload your applications expect and publishes them to the queue or topic you choose.

Does this replace our messaging platform?

No. ECOM connects to the messaging platform you already run; the broker stays under your control.

Which versions and client libraries are supported?

These depend on your platform and environment. ECOM confirms versions, authentication and connection settings during scoping.

Connect partners to your messaging platform

Tell us which messaging platform and applications you run. ECOM outlines the integration approach.