IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

End-to-End Monitoring (E2EM) for ACE Hosted Runtimes in IBM webMethods Hybrid iPaaS (IWHI)

By Jitendra Panda posted 9 hours ago

  

Introduction

As enterprises increasingly adopt hybrid integration platforms, observability becomes a cornerstone for ensuring reliability, performance, and rapid troubleshooting. IBM webMethods Hybrid iPaaS (IWHI) bridges cloud and on-premises applications, and with the release of ACE v13.0.3, we’ve taken a significant leap forward in simplifying End-to-End Monitoring (E2EM) for hosted runtimes. This blog outlines the enhancements introduced in this release, the automation of E2EM configuration, and the validation strategy used to ensure a seamless experience.

What’s New in ACE v13.0.3

  1. Introduction of ibmvault for Secure Credential Management.
    To streamline E2EM enablement, ACE now introduces a dedicated vault named ibmvault, designed to store credentials and configurations required for monitoring.

  2. Enhanced Observability with “More Info” UI Integration.
    A new “More Info” link has been added to the E2EM dashboard UI. Initially, this redirects users to the ACE /log page with pre-applied filters, enabling:

    • Quick access to runtime logs.
    • Easier debugging of integration flows.
    • Foundation for future enhancements like granular metrics and traceability.

Validating E2EM Transactions

To validate E2EM transactions, follow these steps:

  1. Navigate to the Home Page of IWHI.
    Home Page

  2. From the left-hand side menu (App Switcher), click on App Connect to open the application
    select App Connect

  3. Create a runtime environment and deploy your integration flow.
    Create a runtime environment

  4. Test your integration using curl commands to validate the endpoints and data flow.

    ✅ Successful Transaction:

    curl https://jitendra-test-https-acdev2529567.a-vir-d1.appconnect.ipaas.dev.ibmappdomain.cloud/hello

    Output: <HelloWorld>Hello, World!</HelloWorld>

    Failed Transaction:

    curl https://moni-ir-https-acdev2529567.a-vir-d1.appconnect.ipaas.dev.ibmappdomain.cloud/greet

    Output: 401 Authorization Required

  5. Navigate to the End-to-End Monitoring page to review transaction logs, performance metrics, and detailed flow activity.
    End to End Monitoring Page

    Performance Metrics
    Flow Activity

Future Enhancements

What’s Coming to the “More Info” Page in App Connect Monitoring

The current More Info page offers a basic filtering experience, helping users get a general overview of their transactions. But that’s just the beginning.

In upcoming releases, expect a major upgrade in how you monitor and troubleshoot integrations. The new enhancements will introduce granular filtering capabilities, allowing you to drill down into transaction-specific data using:

  • Span ID
  • Trace ID
  • Parent Span ID

These identifiers will make it easier to trace the journey of a transaction across distributed systems, giving you deeper visibility into performance bottlenecks and anomalies.

Conclusion

The enablement of App Connect transactions in the IWHI End-to-End Monitoring (E2EM) page marks a major milestone in hybrid integration observability. This enhancement allows users to seamlessly track and analyze transaction flows across cloud and on-premises environments, directly from a unified dashboard.

Additionally, the newly introduced “More Info” link provides quick access to filtered runtime logs, making it significantly easier to debug integration flows and pinpoint issues. Together, these features empower integration teams with deeper visibility, faster troubleshooting, and a more streamlined monitoring experience.

0 comments
12 views

Permalink