Sap Ag

Sap Se

Janko Budzisch

Stephen Pfeiffer

Pavel Kojevnikov

An IS monitoring approach is described that is capable of monitoring the availability of various software components. A further capability is that the availability of the individual software components upon which a specific business logic process depends may each be individually and continuously checked, in a combined fashion that is referenced to the specific business logic process, so that the status of the business logic process itself (e.g., operable or non-operable) can be continuously determined on an on-going basis. Moreover, operability or non-operability can be established over a wide range of different business logic processes on a process by process basis.

Infrastructure for maintaining cognizance of available and unavailable software components

An Information Systems (IS) monitoring approach is described that is capable of monitoring and displaying the availability of various software components, including 'foundational' operation features of the IS infrastructure. A further capability is that the availability of the individual software components upon which a specific business logic process depends may each be individually and continuously checked, in a combined fashion that is referenced to the specific business logic process, so that the status of the business logic process itself (e.g., operable or non-operable) can be continuously determined. Moreover, operability or non-operability can be established over a wide range of different business logic processes on a process by process basis. In this manner, an IS administrator can keep abreast of the status of the IS infrastructure and its ability to execute business logic processes dependent on lower level software.

Application for testing the availability of software components

An IS monitoring approach is described that is capable of monitoring the availability of various software components. A further capability is that the availability of the individual software components upon which a specific business logic process depends may each be individually and continuously checked, in a combined fashion that is referenced to the specific business logic process, so that the status of the business logic process itself (e.g., operable or non-operable) can be continuously determined on an on-going basis. Moreover, operability or non-operability can be established over a wide range of different business logic processes on a process by process basis. In various embodiments, the results of the monitoring may be continuously updated and displayed in a display so that an IS administrator can visually ascertain the status of the enterprise's various business logic processes.

Growing community of inventors

Reilingen, Germany

Janko Budzisch