• / company
    • about us
      • / about us

        The partner of choice for data & product engineering to drive business growth & deliver an impact within your organization
    • product engineering
      • / product engineering
        We specialize in Software Product Engineering, transforming your concepts into impactful products.
    • technology
      • / technology
        250+ specialists skilled in software, BI, integration, offering end-to-end services from research to ongoing maintenance.
    • methodology
      • / methodology
        We specialize in software product engineering, transforming your concepts into impactful products.
    • careers
      • / careers
        Our team needs one more awesome person, like you. Let’s grow together! Why not give it a try?
    • do good
      • / do good
        We’re a team devoted to making the world better with small acts. We get involved and always stand for kindness.
    • events
      • / events
        LLMs in Action: Transforming How We Work, Communicate, and Innovate
    • blog
      • / blog
        Why Every Developer Should Care About AI Plugins, And What You Might Be Missing
        mindit chats with Andreea Moldovan: “At mindit.io people really put effort into making it happen.”
    • contact us
      • / contact us
        We would love to hear from you! We have offices and teams in Romania and Switzerland. How can we make your business thrive?
  • / get in touch

Event monitoring in IBM Integration Bus

As one of the most widely used enterprise integration solutions, IBM IntegrationBus (IIB—formerly known as WebSphere Message Broker) allows easy connections between different kinds of enterprise applications and services. As it’s usually used to integrate different types of services, it’s important to have visibility into how the connections between these services perform. Especially when something goes wrong in such a complex system, it can be difficult to identify the root cause of the problem—is the issue an erroneous service, or a design error in the message flow between services? It’s important to have a unified perspective over all parts of the systems to be able to make the right decisions.

We use the built-in monitoring feature to transmit messages about a successful or erroneous run of the integration flow.

A message flow publishes an event when something interesting happens. This event is a message that contains information about the source of the event, the time of the event, and the reason for the event. The event can include more details from the message body or from the integration flow context. A successful status message would provide details on the source and target system or application and identifiers for the data that was transmitted. These fields can be used to correlate messages that belong to the same transaction, or to convey business data to a monitoring application. In the case of an error, the message would include the error details.

The monitoring event is published to a topic each time a business message passes through a flow node terminal (like the output terminal).

By using the publish-subscribe mechanism, the business flow is decoupled from the monitoring platform and don’t affect each other’s performance.

To consume the monitoring events, we recommend using the ELK stack or a business analytics app like PowerBI.

Distribute: