KR100461029B1 - Method and system for recording client requests and server responses to use later for performance test or performance analysis of server in client-server computing environment. - Google Patents

Abstract

The present invention relates to a system and method for collecting and managing information about a client's request and a server's response so that it can be repeatedly reused in performance measurement of individual requests of the client in a client-server computing environment or in a large load test on the server. More specifically, in a client-server computing environment using a communication protocol of request and response patterns, by executing an agent that connects the communication between the client and the server, the agent's request is received by the agent Each request by storing information about the client's request and the server's response, using the stored information to later reproduce the communication status, while the agent receives and forwards the server's response back to the client. Performance and server performance side The present invention relates to a system and method for collecting and managing information about a client's request and a server's response so that the information can be used for analysis. In particular, in a client and server computing environment using a communication protocol of a request-response pattern without depending on a specific communication protocol, it is possible to collect information about the client's request and the server's response. To this end, the present invention is characterized by including an agent, a repository, and a user interface. Specifically, the agent is responsible for ensuring that a communication protocol using request and response patterns has a data header portion of fixed length and a variable length data body portion in which the length of the data body in the data header is determined. A dummy handler that includes an Any Handler part that supports the protocol, and also supports a protocol of any request / response pattern when the Any handler part does not support, that is, does not have a fixed length data header part. (Dummy Handler) section, and also includes a log management unit for collecting the information about the request and response to the repository, and in the case of the protocol supported by the AnyHandler unit, the information in the data header and the characteristics of the protocol Includes a magic number processor that manages the magic number, which is a 34-digit colon-separated number string that sets , Repository is characterized in that a user interface for management, such as store information for each request and response, and including a management database, In addition, the agent and the magic number.

Description

System and method for collecting and managing information about client request and server response for replay of communication, measurement and analysis of server performance in client-server computing environment {Method and system for recording client requests and server responses to use later for performance test or performance analysis of server in client-server computing environment.}

The present invention relates to a system and method for collecting and managing information about a client's request and a server's response so that it can be repeatedly reused in performance measurement of individual requests of the client in a client-server computing environment or in a large load test on the server. More specifically, in a client-server computing environment using a communication protocol of request and response patterns, by executing an agent that connects the communication between the client and the server, the agent receives the client's request to the server Store the information about the client's request and the server's response, using the stored information to later reproduce the communication status, while the agent receives and forwards the server's response back to the client. Measure performance and server performance, min The present invention relates to a system and method for collecting and managing information about client requests and server responses. In particular, in a client and server computing environment using a communication protocol of a request-response pattern without depending on a specific communication protocol, it is possible to collect information about the client's request and the server's response.

One method of gathering information about the client's request and the server's response to measure the performance of the current server application or to reproduce the communication situation is to support the communication protocol used by the server and send a request to the server. It is to create and use a separate client application that has a function to store information about requests and responses each time it is received. As an example of an application using a database, the collection of information about SQL requested by an application for measuring the performance of the database has the function of the above application serving as an SQL client, and also sends an SQL request to the database server. This can only be achieved by creating a client application that has the ability to store information about each request and response each time it passes and receives a response. In this case, in order to collect a client's request for a specific server, it is possible to create a client that supports the communication protocol used by the server and supports the storage function for each request and response. Meanwhile, another method of collecting information about a client request and a server response for performance measurement of a server application or replaying a communication situation, and the like, may log information about a client request and a server response. There is a method of measuring the individual performance of each request or the performance of the server itself by repeatedly storing the information using the stored information and repeatedly reproducing the information using the stored client's request and response. To be able to do this, the server must provide storage for the client's request and response, and the server also provides the ability to store all of the minimal information needed to recreate the communication situation when storing the client's request. Should be. In the case of a database server, for example, the database should provide a function for storing information about a client's request (SQL) for measuring the performance of the database server. You should have all the minimum information you need to replay. That is, a method of collecting information about a client's request necessary to repeatedly perform load tests and performance tests on various servers supports a communication protocol of the corresponding server and also stores information on each request and response. Among the methods of producing and using a client providing a function and a function of a server, there is a method of collecting a client's request by using a log function that stores information about the client's request and response. The first method has the difficulty of creating a separate client application for each protocol used, and the second method requires that the server provide the capability to store all the minimum information necessary when the client application reproduces the communication situation. This exists.

An object of the present invention is to solve the problems of the prior art, and when the client and the server send and receive data, the client receives the client's request and forwards to the server, and receives the server's response and delivers the agent to the client and the client If each communication protocol executed and used between servers takes the form of a request-response pattern and uses the information in a fixed length data header to characterize the entire forwarded data packet, each request It is intended to provide a system and method that can collect information on responses and responses universally. More specifically, the communication protocol used by the client and server has a data header portion having a fixed length and a variable length data body portion in which the length of the data body is determined in the data header. In the case of a protocol, it is variable according to a protocol using an Any Handler unit that supports such a protocol, and uses the character of the communication protocol and the information in the data header using a 34-digit colon separated string called a magic number. It is possible to provide a system and method for enabling the user to set the number, using the magic number processing unit for processing the magic number to collect information about the request and response of the client, and also to set the magic number using the user interface do.

In addition, another object of the present invention, when the client and the server transmits and receives data, receives the client's request to the server, and receives the server's response to run the agent between the client and the server, and also By simultaneously executing thread 1, which forwards the request to the server, and thread 2, which forwards the server's response to the client, if the client and server use any protocol in the request-response pattern, The present invention provides a system and method for collecting information on a request and response of a client regardless of a communication protocol by using a dummy handler having a function of analyzing and collecting and storing information.

In order to achieve the above objects, the present invention is characterized by including an agent, a repository, and a user interface. Specifically, the agent is responsible for ensuring that a communication protocol using request and response patterns has a data header portion of fixed length and a variable length data body portion in which the length of the data body in the data header is determined. A dummy handler that includes an Any Handler part that supports the protocol, and also supports a protocol of any request / response pattern when the Any handler part does not support, that is, does not have a fixed length data header part. (Dummy Handler) section, and also includes a log management unit for collecting the information about the request and response to the repository, and in the case of the protocol supported by the AnyHandler unit, the information in the data header and the characteristics of the protocol Includes a magic number processor that manages the magic number, which is a 34-digit colon-separated number string that sets , Repository is characterized in that a user interface for management, such as store information for each request and response, and including a management database, In addition, the agent and the magic number.

1 is a block diagram illustrating a general configuration of a system for collecting and managing information on a request of a client and a response of a server using an agent, a repository, and a user interface according to the present invention. 2 is a flowchart illustrating a process of processing a request of a client and a response of a server in the any handler unit according to an exemplary embodiment of the present invention. 3 is a flowchart illustrating a process of processing a request of a client and a response of a server in a dummy handler according to another exemplary embodiment of the present invention. 4 is a block diagram showing a format of a magic number used in a magic number processing unit according to another preferred embodiment of the present invention. 5 is a block diagram showing the contents of the number of each digit of the magic number used in the magic number processing unit according to another preferred embodiment of the present invention. FIG. 6 is a block diagram illustrating a structure of a data packet used in a protocol that can be processed by the any handler unit according to another exemplary embodiment of the present invention.

<Description of Symbols for Main Parts of Drawings>

10. Client Application

11.Client1 accessing Server1 using AnyHandler

12. Client 2 connecting to server 2 using dummy handler part

20. Agent

21. Any handler part, 22. Dummy handler part, 23. Log management part, 24. Magic number processing part

30. Server Application

31. Server 1 connected to Client 1 using AnyHandler

32. Server 2 connected to Client 2 using dummy handler part

40. Repository

50. User Interface

100. Data Packet

110. Data packet header, 120. Data packet body

200. Magic Number Format

There may be a plurality of embodiments of the present invention, and a preferred embodiment will be described in detail below with reference to the accompanying drawings. Those skilled in the art will be able to better understand the objects, features and advantages of the present invention through this embodiment. FIG. 1 is a block diagram illustrating a system of an agent, a repository, and a user interface according to a preferred embodiment of the present invention. FIG. 2 is a diagram illustrating a client's request and a server's response in an animation handler according to a preferred embodiment of the present invention. 3 is a flowchart illustrating a process of processing a request of a client and a response of a server in a dummy handler according to an exemplary embodiment of the present invention, and FIG. This is a block diagram showing the format of the magic number, a 34-digit colon-separated sequence of numbers used by the magic number processor. 5 is a block diagram showing the contents of each digit of the magic number. FIG. 6 is a block diagram of a data packet capable of expressing characteristics by a magic number used in an any handler according to an exemplary embodiment of the present invention. Referring to FIG. 1, a system for collecting and managing information about a client's request and a server's response for use in reproducing communication, measuring server performance, analyzing, etc. in a client-server computing environment includes an agent 20, a manager, and a server. It consists of a repository 40, a user interface 50, and also the agent 20 is composed of an animation handler unit 21, a dummy handler unit 22, a log management unit 23, a magic number processing unit 24 The repository 40 consists of a standard relational database, and the user interface 50 consists of a standard web browser. The two handlers 21 and 22 of the agent 20 wait for the connection of the client 11 and 12 at a specific port, and the client 11 and 12 are connected. Receives data from the server, and transmits each data to the corresponding server (31,32) specified in advance, and also receives the response from the server (31,32) and delivers back to the client (11, 12), respectively. At this time, by transmitting the information about each request and response to the repository 40 using the log management unit 23, and stores it, so that it can be reused when reproducing the communication situation later. In particular, the animation handler unit 21 processes the information on the communication method between the request and the response by using the magic number 200 and the magic number processing unit 24 to use the communication data packet 100. It is possible to collect more detailed information than the dummy handler unit 22 for the communication protocol using a. In the request-response information collection and management system having the above configuration, the operation process of the animation handler unit 21 and the dummy handler unit 22 will be described in detail.

<Any Handler>

An operation process of the any handler unit 21 will be described in detail with reference to FIGS. 1, 2, 4, 5, and 6 as follows. When the agent 20 process is started, the any handler unit 21 listens to thread 0 that listens to the port set using the user interface 50 by using a socket. Start (S201). When the client 1 (11) is connected to the listening port of the animation handler unit 21 of the agent 20 to connect to the server 1 (31) (S202), the animation handler unit 21 is the client 1 ( 11) creates a new thread 1 (thread1) to be dedicated to the communication between the server 1 (31) (S203), and thread 0 waits while listening to new connections of other clients (S204, S201). Meanwhile, the generated thread 1 prepares to transmit the request and response data packet 100 by analyzing the information on the communication protocol using the magic number processor 24 (S205). In addition, the thread 1 is connected to the server 1 (31) using the preset IP address and port number of the server 1 (31) (S206), magic number 1 (mn1, hereinafter referred to as magic number k mnk) If the server 1 31 first sends the data packet 100 (mn1 = 0), the server 100 reads the packet 100 from the server 1 31 and delivers it to the client 1 11 (S208, S209). . If the client 1 (11) first sends data (mn1 = 1), the data packet 100 is read from the client 1 (11) and started to be transmitted to the server (S210). At this time, first, as much as the header length (mn2) of the data packet 100. The byte offset of the read header 110 data converts mn3 to mn4 into numbers according to mn5 to obtain the length of the entire data packet 100. The length of the data body 120 is obtained by referring to mn6 from the length of the entire data packet thus obtained, and the server 1 (31) is read by reading both the header 110 and the body 120 of the data packet 100 sent by the client 1 (11). To pass). The determination of whether all the data packets requested from the client 1 (11) have been delivered is determined according to the values of mn11, mn12, mn13, mn14, and mn15. According to the value of mn11, the position of the request data packet continuation condition value is found in the header 110 or the body 120 of the data packet 100, and the values are determined and compared (S211). If it is determined that all of the request data packets 100 sent by the client 1 11 have been delivered to the server 1 31, the response data packet 100 is read from the server 1 31 and transmitted to the client 1 11. Beginning (S212). At this time, the request data packet 100 is read from the client 1 (11) and transferred using a method similar to the case where the server 1 (31) is transferred. In the same manner as in the case of the request, the magic numbers are analyzed to determine the last response packet 100 (S213). In this way, after relaying both the request data of the client 1 (11) and the response data of the server 1 (31), the annie handler unit 21 processes the one request processed using the log management unit (23) and 1 for this. The meeting response, that is, request-response information for one session may be stored (S214). At this time, among the information about the request-response to be stored, the information about the request command is analyzed by magic numbers of mn7, mn8, mn9, and mn10, and the information about the requested resource (requested resource, URL, SQL, etc.) is from mn25 to mn34. Analyze the magic numbers, and store the information about the response code by analyzing mn16, mn17, mn18, and mn19. The protocol used by storing the information of the request resource (URL, SQL, etc.) requested by the client 1 (11) into two types: URI (Uniform Resource Identification, mn25 to mn29) and parameter (mn30 to mn34). By selectively applying to, more detailed request information can be collected. As described above, the system using the animation handler unit 21, the magic number processing unit 24, the log management unit 23, and the user interface 50 of the present invention is represented in FIG. 6 in a client-server computing environment. A data packet having the same structure as that of the data packet 100 is used for transmitting and receiving data, and in particular, the information of the protocol is represented by the magic number 200 shown in FIGS. 4 and 5 in the header corresponding to the header of the data packet. Provides the ability to collect information about requests and responses for clients and servers using any protocol.

<Dummy handler part>

The operation of the dummy handler unit 22 will be described in detail with reference to FIGS. 1 and 3 as follows. When the agent 20 process starts, the dummy handler unit 22 starts thread 0 that listens to the port set by using the user interface 50 by using a socket (S301). When the client 2 12 is connected to the listening port of the dummy handler 22 of the agent 20 in order to connect to the server 2 32 (S302), the dummy handler 22 is connected to the client 2 ( 12) create a new thread 1 (thread1) to be dedicated to the communication between the server 2 (32) (S303), thread 0 waits again listening to a new connection of another client (S304, S301). On the other hand, the generated thread 1 is connected to the server 2 (32) using the IP address and port number of the server 2 (32) previously set by the user interface (50) (S305), from the server 2 (32) to the client 2 Create a new thread 2 dedicated to passing data to (12) (306). Thread 1 dedicated to reading the data of client 2 (12) and passing it to server 2 (32) and thread 2 dedicated to reading the data of server 2 (32) and passing it to client 2 (12) are executed at the same time. do. Referring to the operation of the thread 1, the thread 1 checks whether the read socket stream of the client 2 12 is blocked (S311), and if not, blocks the client 2 (12). In step S312 and S317, data is read from the server and transmitted to the server 2 (32). At this time, by checking the state of the request display flag (S316) (S313), if 0, the repository 40 is read using the log management unit 23 by reading information on the latest request-response session stored in the temporary storage. Store in (S314). Then, the request display flag is set to 1 again (S315), the read request data is stored in the temporary storage (S317), and the data read in S312 is transmitted to the server 2 32 (S318). If the request display flag is 1 in S313, the data read in S312 is stored in the temporary storage (S317), and the data read in S312 is transferred to the server 2 32 (S318). Thread 1 repeatedly performs this operation when the read socket stream of the client 2 12 is not blocked (S311 to S318). On the other hand, the thread 2 checks whether the read socket stream of the server 2 32 is blocked at the same time as the execution of the thread 1 (S321), and reads data from the server 2 32 when the thread 2 is not in the block state (S322). In step S326, the client 2 starts to deliver it. At this time, the request display flag is set to 0 (S323), and the response data read in S322 is stored in the temporary storage (S325). At this time, it is assumed that the thread 2 does not operate while the thread 1 operates, and conversely, the thread 1 does not operate while the thread 2 operates. This is because after the dummy handler unit 22 communicates the pattern of request and response, that is, the client's request data is completely transmitted to the server, the response data of the server begins to be delivered to the client, and all of the server's response data is transmitted to the client. After delivery, it is assumed that the client supports a communication method that starts sending another request data. That is, the dummy handler 22 reads the data from the server 2 32 and passes it to the client 2 12 while the thread 1 reads the data from the client 2 12 and transfers the data to the server 2 32. If this situation occurs, it is determined that one request is completed at this time, and also while thread 2 reads data from server 2 32 and passes it to client 2 12, thread 1 receives data from client 2 12. If a situation occurs that is read and delivered to the server 2 (32), it is determined that one response has been completed at this time. And this one request and one response is treated as one session. The dummy handler unit 22 stores and manages information on the request and the response in the repository 24 using the log manager 23 in units of such sessions. As described above, the system using the dummy handler unit 22, the log management unit 23, and the user interface 50 of the present invention is a client-server computing environment, all clients using the protocol of request and response pattern Provides the ability to collect information about requests and responses for servers and servers.

As described above, according to the present invention, when using the any handler unit, when a client and a server transmit / receive data, they use a communication protocol in a pattern of request and response, and communicate with a specific type of data packet. By using an agent that mediates communication between the client and the server, and using the magic number setting function that describes the characteristics of the communication protocol, it is possible to collect and manage information on requests and responses for various protocols. In addition, when the dummy handler part is used, information about each request and response can be collected and managed by using an agent that mediates communication between a client and a server using an arbitrary communication protocol using a request and response pattern. Will be. Therefore, using the system and method of the present invention, it is more convenient to collect and manage information about client requests and server responses for reproducing communication situations, measuring and analyzing server performance, and so on for various communication protocols. It becomes possible.

Claims (4)

Client-server computing using a data packet with a header of fixed length and a body whose length and other characteristics are determined by the content of the header, and using a request and response communication protocol. In an environment, a method of collecting information on a request of a client and a response of a server, comprising: executing an agent between the client and the server to mediate both communication data, and when interpreting the communication data, Determining information about a request and a response by using a set 34-digit magic number; and transmitting and storing the information about the request and the response as a repository. How to collect information about requests and responses from the server In a client-server computing environment using a request-and-response communication protocol, a method of collecting information about a request of a client and a response of a server, comprising: executing an agent between the client and the server to transmit both communication data. Mediating, using the dedicated thread 1 to deliver the request data of the client to the server when interpreting the communication data, and transmitting response data of the server to the client when interpreting the communication data. Using the dedicated thread 2 simultaneously with the thread 1 and when interpreting the communication data, the response data of the server does not begin to be transmitted until after all of the client's request data has been delivered to the server, After all response data has been delivered to the client Finally, the client uses the characteristic of initiating another request to determine one session information consisting of one client's one request and one server's response and return information about the request and the response. Method of collecting information about the request of the client and the response of the server, characterized in that it comprises the step of transmitting to the repository and storing An agent 20, a repository 40, and a user interface 50, wherein the agent 20 transmits and receives data in a request and response manner using a specific type of data packet 100. Any handler unit 21 that is responsible for communication between the server and the server; A log management unit (23) for transmitting information about the client's request and the server's response collected by the any handler unit (21) to the repository (40); A magic number (200) used to analyze the request and response transmitted from the any handler unit (21) and determine the characteristics of the protocol; A magic number processor 24 for processing and managing the magic number 200; Wherein the repository 40 includes means for communicating with the agent 20 to store information about requests and responses, and the user interface 50 between the agent 20 and the user. Means for setting information used by the agent 20, such as the magic number 200 and the IP address and port number of the server 31, for the client's request and the server's response. System to collect and manage information It includes an agent 20, a repository 40 and a user interface 50, the agent 20, the dummy handler unit responsible for the communication medium between the client and the server for transmitting and receiving data in a request and response manner (22); A log management unit 23 which transmits information about the client's request and the server's response collected by the dummy handler unit 22 to the repository 40; Wherein the repository 40 includes means for communicating with the agent 20 to store information about requests and responses, and the user interface 50 between the agent 20 and the user. Means for setting information used by the agent 20, such as an IP address and a port number of the server 32, and collecting and managing information on the client's request and the server's response.