Automated application discovery and analysis system and method

• US 8,051,106 B2
• Filed: 12/15/2009
• Issued: 11/01/2011
• Est. Priority Date: 03/12/2003
• Status: Active Grant

• Current Assignee: Global SAAS Solutions Pte Limited
• Original Assignee: Intotality Phils Inc.
• Inventors: Bird, Stephen Anthony
• Primary Examiner(s): Hwa; Shyue Jiunn
• Application Number:
  US12/638,654
• Publication Number:
  US 20100094911A1
• Time in Patent Office: 686 Days
• Field of Search: None
• US Class Current: 707/802
• CPC Class Codes: G06F 16/287 Visualization; Browsing
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/0635 Risk analysis of enterprise or organisation activities
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change

Abstract

An object oriented design for an automated modeling system for mapping and monitoring the business roles and impact of elements within an IT Infrastructure that make up specific applications or business processes, spanning not only network elements, hosts, servers and programs but also users, company structure and processes. The design including: a series of collector modules for collecting relationship, modeling and status information from IT specific sources used to build a model of the application or process in the database and to gather data about activities occurring on the computer network from a business impact perspective; a series of visualizer modules for reporting monitoring activities; a modeling database for storing information collected by the collector modules; a series of correlator modules for automatically determining relationships between data objects stored in the database to build application models of individual applications.

Claims

1. A computer-implemented method for automated discovery and modelling of application services, the method including:

(a) for a given application service, identifying a plurality of policies describing software applications upon which the application service depends, wherein the policies include a policy that specifies guidelines to identify, without specifying directly, at least one of the following criteria for a particular application;

personal computers having the application loaded;

servers having the application loaded;

databases accessed by servers having the application loaded;

users for personal computers having the application loaded;

business units to which users for personal computers having the application loaded are assigned; and

network infrastructure that connects together elements described by any of the above criteria;

(b) for each policy, identifying a data category, and identifying a collector module for gathering data of that data category;

(c) instructing the identified collector modules to gather data;

(d) processing the gathered data thereby to create/maintain data objects representing elements that describe, in a specific manner, software applications and information technology infrastructure that supports those software applications, wherein each object is indicative of its relationship with one or more other objects, wherein the relationships include;

i. relationships in terms of information technology infrastructure; and

ii. business relationships;

(e) for each given application service, sorting and manipulating the data objects based on the policies, thereby to create a model for the application service;

(f) based on the model, automatically building an end-to-end application service map for each application service; and

(g) on the basis of the end-to-end application service map, performing impact prediction analysis in respect of the model, thereby to identify the impact of a failure in respect of an element, in terms of both infrastructure and business impact,

wherein the collector modules include Lightweight Directory Access Protocol/Directory Services collector(s) for mapping user, system and account data to common schema,

wherein the collector modules include a first collector module that makes use of traffic probing/analysis when identifying inter-application communication, mapping relationships into a common schema.

2. The method according to claim 1 wherein relationships in terms of an information technology infrastructure are used to form a map in terms of logical and physical connectivity relationships, and relationships in terms of business topology are used to form a map in terms of business topology.

3. The method according to claim 1 wherein policies are identified to describe each of the following criteria for the particular application:

personal computers having the application loaded;

servers having the application loaded;

databases accessed by the servers having the application loaded;

users for personal computers having the application loaded;

business units to which users for personal computers having the application loaded are assigned; and

network infrastructure that connects together elements described by any of the above criteria.

4. The method according to claim 1 wherein the collector modules include a software inventory collector for identifying applications loaded on personal computers and/or servers into a common application schema.

5. The method according to claim 4 wherein collector modules locate and identify structured query language databases utilized by the server process for the relevant application(s) and populate the data into a common database schema.

6. The method according to claim 1 wherein the collector modules include a structured query language collector for mapping data in a structured query language database to a common data schema.

7. The method according to claim 1 wherein the collector modules include a physical network discovery collector for mapping information technology infrastructure between identified application endpoints into a common infrastructure schema.

8. A computer-implemented method for automated discovery and modeling of application services, the method including:

(a) for a given application service, identifying a plurality of policies describing software applications upon which the application service depends, wherein the policies include a policy that specifies guidelines to identify, without specifying directly, at least one of the following criteria for a common schema;

personal computers having the application loaded;

servers having the application loaded;

databases accessed by servers having the application loaded;

users for personal computers having the application loaded;

business units to which users for personal computers having the application loaded are assigned; and

network infrastructure that connects together elements described by any of the above criteria;

(b) for each policy, identifying a data category, and identifying a collector module for gathering data of that data category;

(c) instructing the identified collector modules to gather data;

(d) processing the gathered data thereby to create/maintain data objects representing elements that describe, in a specific manner, software applications and information technology infrastructure that supports those software applications, wherein each object is indicative of its relationship with one or more other objects, wherein the relationships include;

i. relationships in terms of information technology infrastructure; and

ii. business relationships;

(e) for each given application service, sorting and manipulating the data objects based on the policies, thereby to create a model for the application service;

(f) based on the model, automatically building an end-to-end application service map for each application service; and

(g) on the basis of the end-to-end application service map, performing impact prediction analysis in respect of the model, thereby to identify the impact of a failure in respect of an element, in terms of both infrastructure and business impact,

wherein the collector modules include two or more of the following;

a first software inventory collector for identifying applications loaded on at least one of personal computers and servers;

a second software inventory collector that collects inventory data from third parties software inventory systems;

a third software inventory collector configured to identify structured query language databases accessed by server process users for the relevant application;

a Lightweight Directory Access Protocol/Directory Services collector for mapping user and account data to a common data schema;

a structured query language collector for mapping data in a structured query language database to a common database schema; and

a physical network discovery collector for mapping network infrastructure between identified application infrastructure endpoints;

one of the collector modules for transforming data from a business organizational data into a common data format.