SYSTEM AND METHOD FOR MONITORING WEB SERVICE

• US 20130305096A1
• Filed: 05/10/2013
• Published: 11/14/2013
• Est. Priority Date: 05/11/2012
• Status: Active Grant

• Current Assignee: Samsung SDS (China) Co., Ltd. (Samsung Group)
• Original Assignee: Samsung SDS (China) Co., Ltd. (Samsung Group)
• Inventors: KIM, Sundeuk, OH, Hyun-Taek
• Granted Patent: US 9,229,844 B2
• Time in Patent Office: Days
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/3668 Software testing software testing in telephone exchanges H04M3/242, testing of hardware G06F11/22
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

Provided are a system and a method for monitoring a web service. The web service monitoring system includes a management module configured to provide an interface for receiving an test scenario and a policy for a simulation test of a target system from an administrator and outputting the simulation test result of the target system to the administrator, a database configured to store the received policy and test scenario, and an agent configured to access the target system according to the test scenario and the policy stored in the database and carry out the simulation test of the target system.

Claims

1. A system, for monitoring a web service, comprising:

a processor executing computer readable instructions using a memory, and implementing at least a management module configured to provide an interface to input a test scenario and a policy for a simulation test of a target system;

a database configured to store the received test scenario and policy;

a service module configured to provide the stored test scenario and policy to the agent;

an agent configured to monitor the target system by;

accessing the target system according to the test scenario and the policy,

carrying out the simulation test of the target system according to the policy, and

generating the simulation test result;

the service module further configured to provide the generated simulation test result to the management module; and

the management module further configured to output the simulation test result.

2. The system of claim 1, wherein the test scenario includes at least one of:

an access address of the target system,

account information for accessing the target system, and

information on a target browser application program interface (API) and a target application.

3. The system of claim 2, wherein the information on the target browser API and the information on the target application includes at least one of:

installation directory locations of the target browser API and the target application, and

version information and registry information on the target browser API and the target application.

4. The system of claim 1, wherein the policy includes at least one of:

a monitoring type of the target system,

a monitoring period,

a number of reattempts upon occurrence of an error during monitoring,

a log record range,

a period for checking whether the policy is changed,

a test timeout limit upon occurrence of an error, and

whether to collect an accessed page address.

5. The system of claim 1, wherein the agent includes:

a first sub-agent, configured to generate a monitoring schedule for monitoring the target system, in accordance with the test scenario and the policy; and

a second sub-agent, configured to perform the monitoring of the target system, according to the schedule;

wherein the first sub-agent provides to the service module the simulation test result generated by the second sub-agent.

6. The system of claim 5, wherein, when an amount of the memory occupied by the second sub-agent exceeds a predetermined threshold, the first sub-agent restarts the second sub-agent.

7. A method of monitoring a web service, comprising:

receiving, at an agent of a web service monitoring apparatus, a browser application program interface (API) installation test request indicating a target system;

accessing a browser API installation web page, of the target system, that includes browser API installation information, using the agent;

downloading a browser API installation file, in accordance with the browser API installation information, using the agent;

executing the browser API installation file to install a browser API in a virtual machine accessible by the agent;

making a determination, at the agent, as to whether the installing of the browser API is a normal browser API installation.

8. The method of claim 7, further comprising:

before accessing the browser API installation web page, making a determination as to whether the virtual machine includes a previously installed instance of the browser API; and

when the determination indicates the previously installed instance is included in the virtual machine, removing the previously installed instance.

9. The method of claim 7, further comprising, after the installing of the browser API, making an attempt to load a predetermined browser API installation complete web page, wherein the making of the determination, as to whether the installing of the browser API was the normal browser API installation, is based at least in part on a determination as to whether the attempt to load the predetermined browser API installation complete web page results in a normal page load.

10. The method of claim 9, wherein:

the agent further comprises a web browser control; and

the normal page load is determined based on whether a completion of a download of the predetermined browser API installation complete web page is indicated by the web browser control.

11. The method of claim 7, wherein the agent responds to the determination that the installing of the browser API is not the normal browser API installation by outputting an error message including:

installation error web page information,

an installation location of the browser API, and

version information and registry information on the browser API.

12. A method of monitoring a web service, comprising:

receiving, at an agent of a web service monitoring apparatus, an application installation test request indicating a target system;

accessing an application installation web page, of the target system, that includes browser application program interface (API) installation information, using the agent;

installing, in accordance with the browser API installation information, in a virtual machine accessible by the agent, a browser API, wherein the installed browser API includes application installation information;

downloading an application installation file from the target system according to the application installation information;

executing the application installation file to install an application in the virtual machine; and

making a determination, at the agent, as to whether the installing of the application is a normal installation.

13. The method of claim 12, further comprising:

before accessing the application installation web page, making a determination as to whether the virtual machine includes a previously installed instance of the application; and

when the determination indicates the previously installed instance is included in the virtual machine, removing the previously installed instance.

14. The method of claim 12, further comprising, after the installing of the application, making an attempt to load a predetermined application complete web page, wherein the making of the determination, as to whether the installing of the application was the normal application installation, is based on one or more of:

a determination as to whether the attempt to load the predetermined application installation complete web page results in a normal page load; and

receiving an installation normal finish message from an application installation process of the virtual machine.

15. The method of claim 14, wherein:

the agent further comprises a web browser control; and

the normal page load is determined based on whether a completion of a download of the predetermined application installation complete web page is indicated by the web browser control.

16. The method of claim 12, wherein the agent responds to the determination that the installing of the application is not the normal application installation by outputting an error message including:

installation error web page information,

an installation location of the application, and

version information and registry information on the application.

17. A method of monitoring a web service, comprising:

receiving, at an agent of a web service monitoring apparatus, a browser application program interface (API) execution test request for a target system;

accessing a browser API-installed web page, of the target system, that includes browser API information, using the agent;

executing a browser API in accordance with the browser API information; and

making a determination, at the agent, as to whether the executing of the browser API is a normal browser API execution.

18. The method of claim 17, further comprising, after the executing of the browser API, making an attempt to load a predetermined browser API execution complete web page, wherein the making of the determination, as to whether the executing of the browser API was the normal browser API execution, is based at least in part on whether the attempt to load the predetermined browser API execution complete web page results in a normal page load.

19. The method of claim 18, wherein:

the agent further comprises a web browser control; and

the normal page load is determined based on whether a completion of a download of the predetermined execution complete web page is indicated by the web browser control.

20. The method of claim 17, wherein the agent responds to the determination that the executing of the browser API is not the normal browser API execution by outputting an error message including:

execution error web page information,

an installation location of the browser API, and

version information and registry information on the browser API received from the target system.

21. A method of monitoring a web service, comprising:

receiving, at an agent of a web service monitoring system, an application execution test request for a target system;

accessing an application-installed web page, of the target system, that includes browser application program interface (API) information, using the agent;

executing a browser API, in accordance with the browser API information, that includes application information;

executing an application in accordance with the application information; and

making a determination, at the agent, as to whether executing of the application was a normal application execution.

22. The method of claim 21, further comprising:

executing the application in a virtual machine; and

after the executing of the application, making an attempt to load a predetermined application execution complete web page;

wherein the making of the determination as to whether the executing of the application was the normal application execution, is based on one or more of;

a determination as to whether the attempt to load the predetermined application execution complete web page results in a normal page load; and

receiving an execution normal finish message from an application execution process of the virtual machine.

23. The method of claim 22, wherein:

the agent further comprises a web browser control; and

the normal page load is determined based on whether a completion of the download of the predetermined application execution complete web page is indicated by the web browser control.

24. The method of claim 21, wherein the agent responds to the determination that the executing of the application is not the normal application execution by outputting an error message including:

execution error web page information,

an installation location of the application, and

version information, registry information and process information on the application received from the target system.