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.
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
Real-time partner data
Partner transactions reach applications as they arrive, rather than in periodic batch files.
Decoupled systems
Applications and partners can change independently, because the broker sits between them.
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.
-
IBM MQ
IBM's enterprise message queuing platform, widely used for reliable application-to-application messaging.
-
Apache Kafka and Confluent
The distributed event streaming platform, including the Confluent distribution, for high-volume event flows.
-
RabbitMQ
The open-source message broker commonly used for queues and publish-subscribe between applications.
-
Amazon SQS
The managed message queue service from Amazon Web Services.
-
Microsoft Azure Service Bus
Microsoft's managed enterprise message broker with queues and topics in Azure.
-
Apache ActiveMQ and Artemis
The open-source Java message brokers, ActiveMQ Classic and ActiveMQ Artemis.
-
Google Cloud Pub/Sub
Google Cloud's managed publish-subscribe messaging service.
-
Oracle Advanced Queuing and TxEventQ
Message queuing built into Oracle Database, including Transactional Event Queues.
More platforms
Enterprise event brokers
-
Solace PubSub+
The event broker used for event-driven integration across on-premises and cloud environments.
-
TIBCO Enterprise Message Service
TIBCO's enterprise messaging service used for application messaging in many large organizations.
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.