AutoPilot M6 TransactionWorks

The AutoPilot M6 TransactionWorks architecture is based on a distributed client-server model. The main components include: Agents, Collectors, and a Server. Agents are deployed on monitored systems and are responsible for collecting transaction data.

Collectors reside on the same systems as the agents and process the collected data, performing initial filtering and aggregation. The Server is the central component, responsible for storing, analyzing, and presenting the data through a web-based GUI. Agents communicate with Collectors using TCP/IP, sending data in a proprietary binary format.

Collectors then forward the processed data to the Server, also using TCP/IP. The Server uses a relational database for storing historical transaction data and configuration information. The web-based GUI provides real-time dashboards, historical reports, and alerting capabilities.

The REST API allows for integration with other monitoring tools and business intelligence platforms. The CLI provides commands for managing agents and configurations. The configuration files are typically stored on the server and are used to define the monitoring parameters, such as the transactions to monitor, the metrics to track, and the thresholds for alerts.

The system supports RBAC for access control, allowing administrators to define roles and assign permissions. Audit logging tracks user actions and system events. The product's ability to trace transactions through Websphere MQ, Websphere Application Server, and CICS on z/OS is a key differentiator.