The HELIXsystem Process Assembler (HSPA) is comprised of four main components:
- Collector Framework
- Time Harmonisation Framework
- Message ID Framework
- Correlation Engine
- Notifications and Alerts Engine
The Collector Framework consists of a library of lightweight, non-intrusive, messaging environment specific monitors. This framework continuously records and time-stamps all messaging events. This is achieved without altering the messages, reconfiguring the services, installing agents on data-stores, or refactoring the production environment.
Time Harmonisation Framework
Different messaging systems use different time stamps. Sometimes these may be in different formats, or different levels of granularity, or both. Harmonising time stamp data across a fragmented complex environment requires considerable manual effort.
The HSPA eliminates this problem via its unique Time Harmonisation Framework. This framework ensures every time stamp across every messaging event is consistent, regardless of the heterogeneity of the host systems. This ensures a highly accurate and consistent time stamp is assigned to every messaging event regardless of the fragmentation of the underlying infrastructure.
Message ID Framework
The Message ID Framework creates a Synthetic ID attached to each message. This is achieved without inserting an additional identity field into the body of the message, changing message identify information or in any other way changing or altering the message. This Synthetic ID enables each message to be tracked across co-operating applications, even though these may be supported by different types of messaging middleware. As a message migrates from one messaging system to another, the Synthetic ID is dynamically updated. Each update is linked, enabling a chain of messaging identities to be constructed regardless of the complexity of the underlying environment.
The Correlation Engine assembles the recorded messaging events into sets of unique execution paths. As each new path is identified, the Correlation Engine maintains a message count. The unique paths are then aggregated into an end-to-end system representation.
The HSPA is specifically designed to monitor and capture every message interaction, executing between all co-operating applications, across every messaging system.
Notifications and Alerts Engine
Complex business processes generate hundreds of thousands, possibly millions of messages a minute. From time to time, messaging events and process flows not previously observed will arise. In order to rapidly identify and analyse these events the HSPA will automatically generate alerts and notifications. This enables any previously unobserved activity to be rapidly isolated and examined.