US 6,983,321 B2 | ||
System and method of enterprise systems and business impact management | ||
Jean-Marc Trinon, Liege (Belgium); Philippe Moitroux, Bassenge (Belgium); Bernard Lemercier, Braine-I'Alleud (Belgium); and Olivier Pignault, Elancourt (France) | ||
Assigned to BMC Software, Inc., Houston, Tex. (US) | ||
Filed on Jul. 06, 2001, as Appl. No. 9/900,283. | ||
Claims priority of provisional application 60/217178, filed on Jul. 10, 2000. | ||
Prior Publication US 2002/0138571 A1, Sep. 26, 2002 | ||
Int. Cl. G06F 15/173 (2006.01); G06F 17/60 (2006.01) |
U.S. Cl. 709—224 | 15 Claims |
1. In an information technology infrastructure where users rely on business services to submit business transaction involving
an orderly sequence of application transactions along a plurality of paths of the structure forming aggregates, a method for
managing impact of events of the infrastructure on the business services, the method comprising:
configuring a management backbone comprising an abstraction layer for intermediate processing, wherein configuring the abstraction
layer comprises;
installing at least one peer-to-peer domain processor in the infrastructure,
configuring the at least one peer-to-peer domain processor with a prepackaged set of event structures, data structures, and
rules such that the at least one peer-to-peer domain processor can deliver at least one abstraction service,
installing at least one peer-to-peer object directory services processor in the infrastructure, and
configuring the at least one peer-to-peer object directory services processor with a pre-packaged set of event structures,
data structures, and rules such that the at least one peer-to-peer object directory services processor can deliver at least
one object directory service, and
wherein configuring the management backbone further comprises:
installing at least one peer-to-peer service processor in the infrastructure, and
configuring the at least one peer-to-peer service processor with a pre-packaged set of event structures, data structures,
and rules such that the service processor can deliver business impact statements;
monitoring the paths used by the application transactions to form monitoring information;
monitoring the aggregates to supplement the monitoring information;
automatically abstracting the monitoring information into business impact information;
using the business impact information to manage the impact of events on the business services;
decomposing at least one of the business services into at least one of the business transactions, wherein each of the business
transactions branches to at least one site specific instance defined as a site business transaction;
decomposing each of a site business transactions into at least one site application transaction;
organizing each of the site application transactions into an orderly sequence;
defining one of the paths for each of the site application transactions;
associating to each of the site application transactions at least one first parameter to remotely submit a sample site application
transaction at an associated source location of the infrastructure;
associating to each of a site application transactions at least one second parameter to request the management backbone to
capture related execution information for each of the sample site application transactions executed at the associated source
location of the infrastructure; and
defining at least one business user group as a resource dependent on at least one of the site business transactions of the
at least one business service.
|