METHOD AND APPARATUS FOR NON-INTRUSIVE WEB APPLICATION INTEGRATION TO STREAMLINE ENTERPRISE BUSINESS PROCESS

• US 20080072239A1
• Filed: 08/22/2007
• Published: 03/20/2008
• Est. Priority Date: 08/22/2006
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Sun, Wei, Zhu, Jun, Zhang, Xin, Liang, Haiqi, Zhang, Kuo
• Granted Patent: US 8,910,187 B2
• Time in Patent Office: Days
• US Class Current: 719/311
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: Y02P 90/80 Management or planning

Abstract

A method and apparatus for capturing Web page events of a client in a computer network, for performing Web event analysis of user interface event messages from a client to generate a Web application event message, and for capturing and analyzing Web page events of a client to generate a Web application event message in a computer network. Web page events at a client are captured to generate user interface event messages, A Web event analysis is performed on the user interface event messages to generate integration event messages, and a Web application event message is generated according to correlation patterns among the integration event messages so as to trigger a corresponding subsequent action.

Claims

1. A method for performing Web event analysis of user interface event messages from a client to generate a Web application event message, comprising steps of:

receiving useful user interface event messages from the client;

mapping the received user interface event messages into integration event messages;

determining to which sessions the received user interface event messages belong;

dispatching the generated integration event messages to different corresponding channels depending on the different sessions to which the received user interface event messages belong; and

generating a Web application event message within each channel according to correlation patterns among the integration event messages.

2. The method according to claim 1, wherein the step of generating the Web application event message within each channel according to the correlation patterns among the integration event messages further comprises steps of:

constituting an integration message sequence with said obtained integration event messages in each channel;

determining whether said integration message sequence conforms to said correlation patterns of the integration event messages; and

if said integration message sequence conforms to said correlation patterns, generating a corresponding Web application event message according to said correlation patterns.

3. The method according to claim 2, wherein said method further comprises a step of deleting said integration message sequence based on at least one of elapsed time and an instance when the corresponding application event message cannot be generated successfully.

4. The method according to claim 1, wherein said method further comprises a step of:

transmitting the generated corresponding Web application event message to a corresponding backend application system to trigger a corresponding action.

5. The method according to claim 1,

wherein said received user interface event messages are composed user interface event messages,

wherein the step of mapping the received user interface event messages into the integration event messages further comprises a step of mapping the composed user interface event messages into the integration event messages, and

wherein the mapping relationships between the user interface event messages and the integration event messages, and the correlation patterns among the integration event messages are all predefined.

6. An apparatus for performing Web event analysis of user interface event messages from a client to generate a Web application event message, comprising:

an event repository for storing mapping relationships between the user interface event messages and integration event messages;

a browser event handler for receiving useful user interface event messages from the client, mapping the received user interface event messages into the integration event messages according to the mapping relationships stored in the event repository, and obtaining necessary useful information from the user interface event messages;

an event session manager for determining which sessions the received user interface event messages belong to according to the useful information obtained by the browser event handler, and dispatching the integration event messages to different corresponding channels depending on the different sessions to which the user interface event messages belong;

an application event pattern repository for storing correlation patterns among the integration event messages; and

one or more application event pattern analyzers for generating a Web application event message within each channel according to the correlation patterns among the integration event messages.

7. The apparatus according to claim 6,

wherein each of said one of more application event pattern analyzers includes a memory for storing an integration event message sequence;

and

said application event pattern analyzer further determines whether said integration event message sequence conforms to the correlation patterns among the integration event messages stored in the application event pattern repository, and if it is determined that said integration event message sequence conforms to the correlation patterns, generates the corresponding Web application event message based on the correlation patterns.

8. The apparatus according to claim 6, wherein said apparatus further comprises:

one or more application event emitters for dispatching the corresponding Web application event message generated by the application event pattern analyzer to a corresponding backend application, so as to trigger a corresponding action.

9. The apparatus according to claim 6,

wherein said received user interface event messages are composed user interface event messages;

and

wherein the mapping relationships between the user interface event messages and the integration event messages, and the correlation patterns among the integration event messages are all predefined, and stored in the event repository and the application event pattern repository, respectively.

10. A method for capturing Web page events of a client in a computer network, comprises steps of:

identifying useful Web page events of the client in response to the client'"'"'s access to a Web application server through the Internet;

recording and monitoring Web page events as monitoring targets among the useful Web page events of the client, and picking up and collecting useful information therefrom; and

capturing Web page event messages of the client and performing a Web event process to generate user interface event messages.

11. The method according to claim 10, wherein the step of capturing the Web page event messages of the client and performing the Web event process to generate the user interface event messages further comprises a step of:

mapping the Web page event messages of the client to generate the user interface event messages according to predefined mapping relationships between the Web page event messages and the user interface event messages.

12. The method according to claim 10, wherein said method is implemented by downloading a script from the server and executing the script on the client.

13. The method according to claim 12,

wherein said script is a Java Script or VB Script, and

wherein said method further comprises steps of:

downloading a Web framework page from the server;

assembling an original Web page from said Web application server and said downloaded Web framework page to generate an assembled HTML framework page; and

displaying the assembled HTML framework page on the client.

14. The method according to claim 10, wherein said method is executed on a proxy server, and the client is set to access the Internet via the proxy server.

15. The method according to claim 10,

wherein which Web page events of the client needed to be monitored and which useful information to be picked up and collected are preset, and said useful information includes session IDs, and

wherein said method further comprises steps of:

determining whether the user interface event messages need to be composed or not; and

if it is determined that the composition is needed, composing the user interface event messages to generate composed user interface event messages.

16. An apparatus for capturing Web page events of a client in a computer network, comprises:

a browser navigation monitor for monitoring whether a target Web page to be accessed by a user of the client belongs to Web pages required to be monitored or not;

an event configuration repository for storing event configuration information indicating what information is required to be recorded and monitored for capturing and monitoring the Web page events of the client;

an event listener register for storing the Web page events required to be recorded and monitored and useful information thereof;

an event listener for capturing Web page event messages of the client, and performing a Web event process to generate user interface event messages; and

a Web information collector for picking up and collecting useful information from the captured Web page event messages and sending them to the event listener.

17. The apparatus according to claim 16, wherein said event listener maps the Web page event messages of the client to generate the user interface event messages according to predefined mapping relationships between the Web page event messages and the user interface event messages.

18. The apparatus according to claim 16,

wherein said apparatus is included inside the client, and

wherein said client downloads a Web framework page from a server, assembles the target Web page to be accessed by the client and said downloaded Web framework page to generate an assembled HTML framework page, and displays the assembled HTML framework page on a display of the client.

19. The apparatus according to claim 16, wherein said apparatus is included inside a proxy server, and said client is set to access the Internet via the proxy server.

20. The apparatus according to claim 16,

wherein which Web page events of the client needed to be monitored and which useful information to be picked up and collected are preset, and said useful information includes session IDs, and

wherein said event listener determines whether the user interface event messages need to be composed or not;

and if it is determined that the composition is needed, composes the user interface event messages to generate the composed user interface event messages.

21. A system for capturing and analyzing Web page events of a client to generate a Web application event message in a computer network, comprising:

one or more clients capable of accessing a Web application server via the Internet;

the apparatus for capturing the Web page events of the client in the computer network comprising;

a browser navigation monitor for monitoring whether a target Web page to be accessed by a user of the client belongs to Web pages required to be monitored or not;

an event configuration repository for storing event configuration information indicating what information is required to be recorded and monitored for capturing and monitoring the Web page events of the client;

an event listener register for storing the Web page events required to be recorded and monitored and useful information thereof;

an event listener for capturing Web page event messages of the client, and performing a Web event process to generate user interface event messages; and

a Web information collector for picking up and collecting useful information from the captured Web page event messages and sending them to the event listener; and

an event analyzing and integrating server including the apparatus for performing the Web event analysis of the user interface event messages from the client to generate the Web application event message comprising;

an event repository for storing mapping relationships between the user interface event messages and integration event messages;

a browser event handler for receiving useful user interface event messages from the client, mapping the received user interface event messages into the integration event messages according to the mapping relationships stored in the event repository, and obtaining necessary useful information from the user interface event messages;

an event session manager for determining which sessions the received user interface event messages belong to according to the useful information obtained by the browser event handler, and dispatching the integration event messages to different corresponding channels depending on the different sessions to which the user interface event messages belong;

an application event pattern repository for storing correlation patterns among the integration event messages; and

one or more application event pattern analyzers for generating a Web application event message within each channel according to the correlation patterns among the integration event message.

22. The system according to claim 21, wherein said apparatus for capturing the Web page events of the client is included inside the client.

23. The system according to claim 22,

wherein said system further comprises:

a Web framework page;

a script repository for storing a script which can be downloaded by the client and used to capture the Web page event messages of the client;

an event configuration repository for storing event configuration information; and

a Web application registry for registering Web pages required to be monitored therein, and

wherein said client downloads said Web framework page and the script, displays an assembled HTML framework page obtained by assembling an original target Web page and said Web framework page on a display of the client, and executes said downloaded script on said client.

24. The system according to claim 21,

wherein said apparatus for capturing the Web page events of the client is included in a proxy server, and said client is configured to access the Internet via the proxy server, and

wherein said system further comprises:

an event configuration repository for storing event configuration information; and

a Web application registry for registering Web pages required to be monitored therein.

25. A computer readable storage medium with computer program codes stored thereon, said computer program codes, when being executed on a computer device, causing said computer device to perform method steps for capturing Web page events of a client in a computer network, said method comprises steps of:

identifying useful Web page events of the client in response to the client'"'"'s access to a Web application server through the Internet;

recording and monitoring Web page events as monitoring targets among the useful Web page events of the client, and picking up and collecting useful information therefrom; and

capturing Web page event messages of the client and performing a Web event process to generate user interface event messages.

26. A computer readable storage medium with computer program codes stored thereon, said computer program codes, when being executed on a computer device, causing said computer device to perform method steps for performing Web event analysis of user interface event messages from a client to generate a Web application event message, said method comprising steps of:

receiving useful user interface event messages from the client;

mapping the received user interface event messages into integration event messages;

determining to which sessions the received user interface event messages belong;

dispatching the generated integration event messages to different corresponding channels depending on the different sessions to which the received user interface event messages belong; and

generating a Web application event message within each channel according to correlation patterns among the integration event messages.