Track Hybrid and Multi-Cloud Processes
Can one BPM follow a process that runs partly on-premise and partly in the cloud? Yes. Anything that can log to Nodinite can be a step on a BPM, whether it runs on-premise, in Azure or another cloud, or as SaaS.
- ✅ Platform-agnostic: log through the Log API, a Logging Agent, or files and queues the Pickup LogEvents Service collects
- ✅ Format-independent: JSON, XML, and flat-file messages appear side by side on the same BPM
- ✅ No connector per BPM: Nodinite matches the events you already log to it
- ✅ Change platforms without redrawing: the BPM refers to Services, not technology
The Business Context
The Order-to-Cash demo spans four systems: a customer Portal, an ERP, a WMS, and ERP-Finance. In real landscapes these rarely share a platform: the Portal may run in the cloud, the ERP on-premise, and the WMS as SaaS. The demo also rotates its messages between JSON, XML, and flat file.
The Problem
Each platform has its own monitoring. To follow one order, you open the Portal's log, the integration platform's run history, and the WMS console, and match them by time. Tracking tied to one platform sees only its own steps.
The Solution
Each system logs Log Events to Nodinite, and every event of one order carries the same correlation key, in the demo the Application interchange id.
cloud · JSON] --> N[fa:fa-server Nodinite] E[fa:fa-building ERP
on-premise · XML] --> N W[fa:fa-warehouse WMS
SaaS · flat file] --> N N --> B[fa:fa-arrow-progress One BPM
Order-to-Cash] style P fill:#9E59BB style E fill:#9E59BB style W fill:#9E59BB style N fill:#2678BD style B fill:#93d16d
Purple: the systems, in any location and format (illustrative). Blue: Nodinite collects the events. Green: one BPM shows the order.
Pick what fits each system:
- Log API - Any system that can make an HTTP call; the demo uses PowerShell.
- Logging Agents - For example Microsoft BizTalk Server, Azure Logic Apps, MuleSoft Anypoint, Boomi, or Serilog in custom .NET code. See all Logging Agents.
- Pickup LogEvents Service - Collects Log Events from file folders, Azure Service Bus, AMQP brokers, Azure Storage, and databases.
From there every platform is treated the same: events bind to Services by Endpoint and Message Type, Search Fields extract the Order Number from JSON, XML, or flat file, a Log View groups them by the correlation key, and Nodinite finds the BPMs that can display them. See End-to-End Process Tracking.
Because no logging code references a BPM, moving an integration to another platform doesn't break it: bind the new Endpoint to the same Service, and the BPM keeps showing the step.
The Results
- One search from the BPM instead of opening the Portal, ERP, and WMS logs.
- New systems join by logging to Nodinite, with no new connector.
- Integrated Monitoring and Remote Actions for the systems behind each step, from the same BPM.
Compare with platform-bound tracking: Why Nodinite BPM is superior to Azure Business Process Tracking and Why Nodinite BPM is superior to Kovai Atomic Scope.
How This Scenario Uses Nodinite Features
- Log API, Logging Agents, and the Pickup LogEvents Service - Get events in from any platform
- Services and Search Fields - Tie events to steps and extract the Order Number from any format
- BPM Log Search - Follow one order across all systems