AutoPilot M6 is designed to monitor and control distributed IT services such as application servers, middleware, user applications, workflow engines, brokers, Service Oriented Architecture (SOA) and Enterprise Service Bus (ESB) based applications and their impact on business services.
It reduces time and effort required to monitor IT services end-to-end without the need for custom development, complex configuration and customization. M6 is based on SOA and can run on a variety of platforms. It employs a policy-based approach to monitoring across heterogeneous platforms and applications.
(Complex Event Processor) CEP-based Event Stream Processing and Correlation engine is at the core of M6 technology. This engine allows aggregation, sorting, filtering, merging and joining of various events and metric streams in real-time using a wizard driven GUI interface.
CEP instances can be replicated or auto-failed over with M6-GRID within minutes or even seconds and can be consolidated or distributed on one or more hardware or Virtual Machines (VM) - such as VMWare or XEN. The replacement hardware/operating system does not have to be identical. CEP has fault, performance and security isolation. Each CEP instance is independent of one another. A crash or malfunction in one instance does not affect another instance. Its hardware includes CPU and memory isolation. The entire state of the CEP is stored in a single deployment file. The entire CEP configuration can be transferred easily regardless of operating system, architecture or processor.
Benefits of using AutoPilot
M6 Virtual CEP Environment (VCE) does the following:
▶ Reduces time to install and configure a new monitoring domain from days/weeks to minutes.
▶ Reduces the time to move a CEP instance to a new server or VM from days to minutes with uninterrupted operation.
▶ M6-GRID provides automatic CEP instances provisioning in case one or more are offline for maintenance or any other reason.
▶ CEP instances can simply be allocated on the fly without service interruptions.
▶ Resource allocations can be made dynamically.
▶ Policies can be reassigned and redeployed within seconds to any CEP instance.
M6 is highly effective in environments where one or more mission critical applications run by technologies such as J2EE, .NET, ESB, JMS, JMX, JMS Messaging, as well as homegrown applications.
M6 provides several types of monitoring services: experts, managers, policies, and business views:
- Experts are data collection components, which reside on CEP servers.
- Managers are distributed software components equipped with policies (components that proactively monitor and automate).
- Business views are top-level visual automation tools that can be deployed as and serve as policies.
M6 uses a collaboration model and collects all related system and application metrics (facts) from managed resources. It correlates the facts via intelligent business views, which can be shared among teams within the organization.
M6 provides security based on the mutual authentication between a client and a server, or between one server and another, before a network connection is opened between them.
It is important to note that understanding of M6 terms, concepts, and architecture is essential for M6 administrators. M6 introduces new terms that may not be commonly used in the systems and application management space. Understanding AutoPilot M6 architecture and organization becomes critical, since M6 employs a blend of n-tier and network architecture, which is contrary to traditional 3-tier application and system management platforms. This architecture allows M6 to scale beyond the limitations of standard 3-tier models and provide users with un-matched flexibility, scalability, and performance.