TOPOLOGY-DRIVEN DATA ANALYTICS FOR LOCAL SYSTEMS OF A SYSTEM LANDSCAPE

• US 20160147772A1
• Filed: 11/21/2014
• Published: 05/26/2016
• Est. Priority Date: 11/21/2014
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: Arndt Effern, Guenter Briam, Steffen Siegmund
• Inventors: SIEGMUND, Steffen, STAUFFER, Ralf, EFFERN, Arndt, BRIAM, Guenter
• Application Number:
  US14/550,204
• Publication Number:
  US 20160147772A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 43/14 using software, i.e. software packages network security related monitoring H04L63/1408

Abstract

A user interface (UI) manager may receive, at an analyzer agent executing within a system of a system landscape, a request for data analysis of component data of an infrastructure component of the system. A request controller may collect, in response to the request, topology data for the system, the topology data including a characterization of the infrastructure component. A content manager may filter, using the topology data, system-specific metadata, to obtain filtered system-specific metadata, and a a request processor may generate, based on the request and the filtered system-specific metadata, a query against the component data.

Claims

1. A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed, are configured to:

receive, at an analyzer agent executing within a system of a system landscape, a request for data analysis of component data of an infrastructure component of the system;

collect, in response to the request, topology data for the system, the topology data including a characterization of the infrastructure component;

filter, using the topology data, system-specific metadata, to obtain filtered system-specific metadata; and

generate, based on the request and the filtered system-specific metadata, a query against the component data.

2. The computer program product of claim 1, wherein the instructions, when executed, are further configured to cause the at least one processor to:

receive the request by way of a user interface of the analyzer agent.

3. The computer program product of claim 1, wherein the instructions, when executed, are further configured to cause the at least one processor to:

receive the request by way of a user interface, including generating the user interface based on the topology data and the filtered system-specific data.

4. The computer program product of claim 1, wherein the instructions, when executed, are further configured to cause the at least one processor to:

receive the request from a second analyzer agent within the system landscape.

5. The computer program product of claim 1, wherein the topology data includes product and version information for the infrastructure component.

6. The computer program product of claim 5, wherein the system-specific metadata includes potential products and versions of the infrastructure component, and the filtered system-specific metadata includes a subset of the products and versions relevant to the infrastructure component.

7. The computer program product of claim 1, wherein the system-specific metadata includes data models modeling system data of the system, and the filtered system-specific metadata includes a subset of the data models relevant to the infrastructure component.

8. The computer program product of claim 7, wherein the instructions, when executed, are further configured to cause the at least one processor to:

map the subset of the data models to a corresponding interface of the infrastructure component.

9. The computer program product of claim 7, wherein the instructions, when executed, are further configured to cause the at least one processor to:

return request results, based on the subset of data models, such that the request results are provided using a user interface consistent with a user interface of a second analyzer agent within the system landscape.

10. The computer program product of claim 1, wherein the instructions, when executed, are further configured to cause the at least one processor to:

execute the query during a runtime of the system

11. The computer program product of claim 1, wherein the instructions, when executed, are further configured to cause the at least one processor to:

execute communications between the analyzer agent and at least a second analyzer agent within the system landscape, using a language and format that is common to the analyzer agent and the at least a second analyzer agent, but independent of the infrastructure component.

12. The computer program product of claim 1, wherein the instructions, when executed, are further configured to cause the at least one processor to:

update the system-specific metadata independently of execution code of the analyzer agent, and without requiring downtime of the execution code.

13. A computer-implemented method for executing instructions stored on a non-transitory computer readable storage medium, the method comprising:

receiving, at an analyzer agent executing within a system of a system landscape, a request for data analysis of component data of an infrastructure component of the system;

collecting, in response to the request, topology data for the system, the topology data including a characterization of the infrastructure component;

filtering, using the topology data, system-specific metadata, to obtain filtered system-specific metadata, wherein the system-specific metadata includes data models modeling system data of the system, and the filtered system-specific metadata includes a subset of the data models relevant to the infrastructure component;

mapping the subset of the data models to a corresponding interface of the infrastructure component; and

generating, based on the request and the mapping, a query against the component data.

14. The computer-implemented method of claim 13, further comprising:

returning request results, based on the subset of data models, such that the request results are provided using a user interface consistent with a user interface of a second analyzer agent within the system landscape

15. The computer-implemented method of claim 13, further comprising:

executing communications between the analyzer agent and at least a second analyzer agent within the system landscape, using a language and format that is common to the analyzer agent and the at least a second analyzer agent, but independent of the infrastructure component.

16. The computer-implemented method of claim 13, further comprising:

updating the system-specific metadata independently of execution code of the analyzer agent, and without requiring downtime of the execution code.

17. A system including instructions recorded on a non-transitory computer-readable storage medium, and executable by at least one processor, the system comprising:

a user interface (UI) manager configured to cause the at least one processor to receive, at an analyzer agent executing within a system of a system landscape, a request for data analysis of component data of an infrastructure component of the system;

a request controller configured to cause the at least one processor to collect, in response to the request, topology data for the system, the topology data including a characterization of the infrastructure component;

a content manager configured to cause the at least one processor to filter, using the topology data, system-specific metadata, to obtain filtered system-specific metadata; and

a request processor configured to cause the at least one processor to generate, based on the request and the filtered system-specific metadata, a query against the component data.

18. The system of claim 17, wherein the infrastructure component is included in a component stack of the system, and wherein the request controller is configured to cause the at least one processor to generate the request processor specific to a type of the infrastructure component within the component stack.

19. The system of claim 18, wherein the request controller is configured to cause the at least one processor to:

generate a second request processor specific to a second type of infrastructure component within the component stack for generation of a second query against second component data of a second infrastructure component; and

coordinate query results of the query and second query results of the second query for providing of aggregated query results to the UI manager.

20. The system of claim 17, wherein the system-specific metadata is updatable independently of execution code of the analyzer agent, and without requiring downtime of the execution code.