Application Manager

Managing Applications to the Business

The Owl™ Application Manager is designed to manage Applications as a network of related Business Service and Application entities. It provides users with an ability to define business specific Views of Applications, to create rules that are used to identify Problems, to analyze the situation in a rich network context, to invoke Application controls both for Problem determination and resolution, to analyze historical behavior of Applications, and to manage Problem lifecycle.

Role Based Security — all users of Owl are assigned a user identity. The identities belong to groups that determine the capabilities of the user, including access to components and metrics within component, authority to execute controls within applications, or simply displaying Views.

Network(Status) Map — The networks of Applications can be displayed graphically. As Applications are discovered by Owl, they automatically appear on the Status Map. As connections are asserted, they too appear on the Status Map and their status changes based on the assertion of the Application. The Status Map can be laid out using either the auto-layout algorithms that come with Owl or manually by the user. In addition to the graphic nodes drawn, user defined icons can be used. The Status Map is updated in real-time without any need to be manually refreshed.

(click for larger view)

Business Views — Owl allows users to create Views of the Applications based on their privileges. View creation is aided by a filtering system that is keyed off the Application’s identity and associated attributes. Creation of Views is highly flexible allowing for hierarchies and specifically defined drill downs all the way down to the Applications. Business Views can be used to show the business impact of a failure.

Tabular Display — The Views can be displayed in a tabular format for users that do not need to see the network context. This display also refreshes automatically.

Rule System — Users have the ability to define Rules that are invoked each time a new observation arrives from the Application. The Rules define value ranges for metrics that can be used to trigger change in the coloring of nodes in the Status Map. Owl uses a simple Red/Yellow/Green model for the performance coloring of the components. If several metrics in a set of Application components can cause a color change, the highest severity color propagates to the next layer up. Additionally, color change can be limited to only a subset of active metrics in the Application.

Schedules — Each component or group of components can have a schedule associated with it. The schedule reflects the expected hours when the components should be in service. If an Application is down when it should be up, Owl will take notice, if an Application is up when it should be down, Owl will take notice and alert if desired.