JP2009187542A - Request processing system, request processing method, and request processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To control to suppress execution to a request from a user. <P>SOLUTION: This request processing system has an input-output response processing part for receiving request information sent from a client 10 through a network 5, and an application server part 100 for executing processing corresponding to the request information on the basis of a preset application. The application server part 100 is provided with an execution suppression determining means for specifying a transmission source of the request information on the basis of property information of the request information and determining whether to suppress the execution on the basis of the specified transmission source, and the input-output response processing part is provided with a suppressed state notifying means for notifying the client 10 that the execution is suppressed. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a server-side processing control system for a request from a client in a client-server system, and more particularly to a technique for suppressing execution processing performed on the server side in response to a request from a specific client.

Web (Web) systems are widely used in various fields, and interactive services and dynamic services that perform advanced processing on the Web server side are required.
In addition, when access is concentrated on the Web server, a large load is applied to the Web server, which may cause problems such as a decrease in processing speed and a Web server down.
For this reason, it is necessary to suppress execution processing for a request from a specific client or access source that is generally realized in a client-server system.

On the other hand, as the services provided by the Web server become more sophisticated, the processing performed by the Web server is also enlarged. For this reason, Web application servers that perform processing specialized for work to reduce the load on the Web server and respond to requests from clients have been utilized.
Furthermore, JAVA EE application servers are widely used in Web systems. The JAVA EE application server is a collection of general-purpose software specifications, and application servers that implement this JAVA EE application are provided by various vendors.

  On the other hand, for example, as a technique to suppress execution processing for HTTP requests sent from HTTP (HyperText Transfer Protocol) clients, load balancers and proxy servers accept HTTP requests and execute processing for the HTTP requests under certain conditions. Based on the above, it is possible to suppress the execution of requests by distributing to HTTP servers and application servers.

As this related technology, the representative server analyzes the content of the HTTP request sent from the client, specifies the content server that is the distribution destination of the execution process for the HTTP request based on the information added to the HTTP request, A technique is disclosed in which an HTTP request is redirected to a specified content server and HTTP requests are distributed (Patent Document 1).
Here, when distributing the HTTP request execution process, the HTTP request is returned to the client by redirection, thereby suppressing the specific HTTP request execution process.

JP 2001-109694 A

  However, in the related technology disclosed in Patent Document 1, data used in a server or application that performs an execution process in response to an HTTP request is exported to the server or application, and a condition for determining whether to suppress the execution process Information must be set in the load balancer or proxy server.

  In addition, in this case, there is a disadvantage that a complicated and troublesome work is required in operation such that it is necessary to create a logic for a distribution condition in a language unique to the load balancer or proxy server.

  Furthermore, in a general Web system, a system user's authority to access the system is centrally managed by an authentication method using an authentication server or the like. In this case, there is an inconvenience that it is difficult to set flexible usage restrictions according to users and applications, such as usage restrictions for each application set in the system.

[Object of invention]
It is an object of the present invention to provide a request processing system, a request processing method, and a request processing program that improve the disadvantages of the above-described conventional example and effectively reduce the load on execution processing for a request from a user. And

  In order to achieve the above object, a request processing system according to the present invention includes an input / output response processing unit that receives request information sent from a client, and an execution process according to the request information based on a preset application. A request processing system having an application server unit for performing the execution processing based on the specified transmission source, and the application server unit specifies a transmission source of the request information based on property information of the request information. When it is determined whether to suppress and includes an execution suppression determination unit that suppresses execution processing for request information of a transmission source set in advance, and the input / output response processing unit is suppressed, It has a configuration including suppression state notification means for notifying the client of the suppression state of the execution process.

  The request processing method according to the present invention includes an input / output response processing unit that performs mutual communication with a client, and an application server unit that performs an execution process in accordance with processing request information sent from the client. In the request processing method for controlling processing, a request analysis process for receiving a processing request sent from the client and analyzing the processing request, a transmission source specifying process for specifying a transmission source of the processing request, and the processing request An execution process determination process for determining whether or not to perform the corresponding execution process, and when the specified transmission source is a target for suppression of the execution process, the suppression state of the execution process is notified to the transmission source An execution suppression notification process is provided.

  The request processing program according to the present invention further includes an input / output response processing unit that performs mutual communication with a client, and an application server unit that performs an execution process according to processing request information sent from the client. In a request processing program for controlling processing, a request analysis function for receiving a processing request sent from the client and analyzing the processing request, a transmission source specifying function for specifying a transmission source of the processing request, and the processing An execution process determination function for determining whether or not to execute an execution process in response to a request; and when the specified transmission source is a target for suppression of an execution process, the execution process suppression state for the transmission source It is characterized by causing a computer to execute an execution suppression notification function that notifies

Since the present invention is configured and functions as described above, according to this, the application server that performs the execution process according to the process request information sent from the client performs the execution process based on the property information included in the process request information. By adopting a configuration that includes a means for determining whether to suppress or not, the processing load on the execution process according to the request from the client is reduced, and the request execution process for a specific client is effectively suppressed and controlled. A request processing system, a request processing method, and a request processing program can be provided.

It is a schematic block diagram which shows one Embodiment of the request processing system by this invention. It is the sequence chart which showed the operation | movement process step in case the suppression object determination is performed in the HTTP request handling control part 120 in the request | requirement processing system disclosed in FIG. 3 is a sequence chart illustrating operation processing steps when a suppression target determination is performed by a JNDI lookup control unit 150 in the request processing system disclosed in FIG. 1. It is the sequence chart which showed the operation | movement process step in case the suppression object determination is performed in the HTTP request handling control part 120 in the request | requirement processing system disclosed in FIG. 6 is a sequence chart showing operation processing steps when an RMI over IIOP handling control unit 180 performs suppression target determination in the request processing system disclosed in FIG. 1. It is the flowchart which showed the operation | movement process step of the suppression target determination in the request | requirement processing system disclosed in FIG. It is explanatory drawing which shows an example of the execution suppression determination condition table in the request | requirement processing system disclosed in FIG. It is a schematic block diagram which shows one Embodiment of the table information management part in the request | requirement processing system disclosed in FIG. It is a schematic block diagram which shows one Embodiment of the table information management part in the request | requirement processing system disclosed in FIG. It is a schematic block diagram which shows one Embodiment of the table information management part in the request | requirement processing system disclosed in FIG. It is a flowchart which shows the processing step of the initialization operation | movement of the execution suppression determination information table in the request | requirement processing system disclosed in FIG. It is a flowchart which shows the operation | movement step of the update process of the execution suppression determination information table in the request | requirement processing system disclosed in FIG. It is a flowchart which shows the operation | movement process step of the execution suppression determination in the request | requirement processing system disclosed in FIG. It is a flowchart which shows the operation | movement process step of the execution suppression determination in the request | requirement processing system disclosed in FIG.

[Embodiment]
Next, the basic configuration content of the embodiment of the present invention will be described.

  As shown in FIG. 1, the request processing system according to the present embodiment includes an HTTP client 10 that is a Web system client and a JAVA EE (Enterprise Edition) application server that performs a request response to a request sent via a network 5. A server device 1 having 100 (hereinafter referred to as “JAVA EE server”) and an RMI client connected to the JAVA EE server 100 and calling a method by RMI-IIOP (Remote Method Invocation over Internet Inter ORB Protocol) as an RMI client 30 is provided.

  The server device 1 includes a central processing unit (CPU) that operates by program control, a program that controls the CPU, a memory that holds data controlled by the program, and a program and data that are permanently stored even when the power is turned off. The JAVA EE server 100 is set by the CPU executing an execution process based on the memory and an application program (business application) that is executably deployed in the storage device. .

  The JAVA EE server 100 operating in the server apparatus 1 is a JAVA EE application server operating in accordance with JAVA Enterprise Edition, and a session object 110 that is an object for managing connection processing on the JAVA EE server 100. , An HTTP request handling control unit 120 that handles an HTTP request from an HTTP client, and a user distribution policy setting unit 130 that inputs policy conditions to the HTTP request handling control unit 120.

  The JAVA EE server 100 provides (calls) application execution control information 140, a JNDI (JAVA Naming and Directory Interface) lookup handling control unit 150, an RMI over IIOP call control 170, and an RMI over IIOP handling control 180, In accordance with request information from the HTTP client 10 and the RMI client 30, the Web application program modules 210 and 230 set in advance and the EJB application program modules 220 and 240 are executed.

  This will be described in detail below.

  In the JAVA EE server 100, the Web container, EJB container, and JNDI server are set in accordance with Enterprise JAVABeans (EJB), method invocation, Enterprise Bean instance generation, etc. are set in the JAVA EE server 100. Control the execution of the EJB application.

The web container is set by the JAVA EE server 100 and monitors the web application modules 210 and 230.
Further, the Web container has a function equivalent to a servlet filter that works in common with the Web application modules 210 and 230 (hereinafter referred to as “container filter function”).

Furthermore, the web container handles the HTTP request sent to the web container by executing the container filter function, and property information (key = value in KEY = VALUE format is paired with the HTTP request. Information) is included, a function for determining whether or not the property information matches based on an execution suppression determination information table (FIG. 7: suppression determination condition) as preset table information, and an execution suppression state are notified. It has a request transfer function that transfers HTTP requests to the Web application module.
Thereby, for example, the Web container can suppress the execution of the Web application module requested from the HTTP client 10 and can notify the HTTP client 10 of the execution processing suppression state.

  In addition, the Web container has a class execution function that executes the class that implements the interface based on the JAVA EE specification, and customizes the suppression judgment condition of the execution process according to the request from the user of the server device 1 Is possible.

  The HTTP client 10 is a client program that makes a call request for a Web application, and includes an HTTP request transmission function that transmits an HTTP request to the JAVA EE server 100 via the network 5. The HTTP client 10 is generally realized by a Web browser or the like. In the present embodiment, one HTTP client 10 is connected to the network 5, but a plurality of HTTP clients 10 may be connected and executed.

The RMI client 30 is a client program that makes an EJB call request, and has an RMI request transmission function that transmits an RMI request to the JAVA EE server 100 via the network 5.
The RMI client 30 is assumed to be an entire program that makes an EJB method call request from a Stand Alone JAVA Application or a .Net application other than the JAVA EE application server program.

  The session object 110 is generated when the JAVA EE server 100 receives the first HTTP request sent from the HTTP client 10, and is an object representing a connection between the client (HTTP client) and the server (server device 10).

The HTTP request handling control unit 120 is executed as startup processing of the application server program when the JAVA EE server 100 is started. After the startup is completed, the HTTP request is specified as an argument every time an HTTP request is sent to the JAVA EE server 100. A function is called.
Further, the HTTP request handling control unit 120 can use HTTP header information that is a header of data in an HTTP request and data that is regularly referred to and updated by a business application executed by the JAVA EE server 100.
For this reason, the HTTP request handling control unit 120 can perform execution suppression processing of execution processing for requests according to business data.

  The user distribution policy setting unit 130 is called from the HTTP request handling control unit 120 and has a function of receiving an HTTP request object acquired by the HTTP request handling control unit 120.

  The application execution control information 140 is instance data expanded on the memory of the server device 1 and is set information of data and operation methods handled by the JNDI lookup handling control unit 150 and the RMI over IIOP handling control unit 180.

A JNDI lookup handling control unit (hereinafter referred to as “JNDI lookup control unit”) 150 is an implementation of JAVA Naming and Directory Interface (JNDI), and an InitialContext Factory that an EJB client acquires when EJB (Enterprise JAVABeans) is called. Has the ability to provide classes.
In addition, the JNDI lookup control unit 150 determines whether or not to suppress based on the JNDI name specified in the lookup method from the JNDI client, the name object, and the property information specified when the InitialContext is generated. It has a function.
Here, when it is determined as a suppression target, a predetermined exception is transmitted to the EJB client.
Further, the JNDI lookup control unit 150 has a function of delegating the processing of a lookup method from a client determined to be out of the suppression target to a JNDI server managed by the JAVA EE server 100.

Here, the preset EJB clients (Web applications 210 and 230) have a function of acquiring a Context object via the JNDI lookup control unit 150.
In addition, the JNDI lookup control unit 150 determines whether or not to be a suppression target based on the JNDI name specified in the lookup method from the JNDI client, the name object, and any property information specified when the InitialContext is generated. It has a target judgment function.

Here, the JNDI lookup control unit 150 has an exception information transmission function for transmitting an error notification (exception information) to the Web applications 210 and 230 as EJB clients when the JNDI client is determined to be suppressed. .
Thereby, execution suppression by the JNDI lookup control unit 150 from the EJB client can be performed.

  Further, the JNDI lookup control unit 150 has a class execution function for executing a class in which an interface is implemented using a lookup method, and can customize execution suppression determination conditions by changing the class setting by the user. it can. It is also possible to implement a determination logic according to serializable business data included in the map object specified when the InitialContext is generated.

  The user distribution policy setting unit 160 is called by the JNDI lookup handling control unit 150 and has a function of receiving a map object including the user property information acquired by the JNDI lookup handling control 150.

The RMI over IIOP call control unit 170 is provided by the JAVA EE server 100 and has a function of receiving an RMI request from a client including the RMI client 30 and calling a method of a remote object based on the RMI specification.
Further, the RMI over IIOP call control unit 170 has a function of calling a method of the RMI over IIOP handling control 180 which is an implementation class of ServerRequestInterceptor when calling a remote method.

The RMI over IIOP handling control unit 180 is an implementation class of the ServerRequestInterceptor interface, and each time an EJB method is called, a method that takes a request object as an argument is called.
The RMI over IIOP handling control unit 180 has a function of analyzing the request object in the called method and determining whether the request source of the request object is a suppression target based on the property information.
Here, when it is determined that the request source is a suppression target, it has an exception information transmission function that returns (transmits) exception information (CORBA exception) to the RMI client.

  The RMI over IIOP handling control unit 180 is an interface in JAVA of the Portable Interceptor defined in the CORBA specification that suppresses the execution of EJB method invocation requests made via RMI over IIOP, and is org.omg.PortableInterceptor. Use ServerRequestInterceptor (hereinafter referred to as "ServerRequest interceptor part") to handle EJB method call requests sent to the EJB container. If the RMI request includes preset property information, the property information matches the execution suppression condition based on the execution suppression determination information table (suppression determination condition: FIG. 7) that is preset table information. In this case, it has a function to suppress the execution of subsequent EJB methods.

  The ServerRequest interceptor is an RMI request handling unit that has a class execution function that executes a class that implements the interface. The user can customize the execution suppression judgment condition by changing the class setting. It can be carried out. It is also possible to implement decision logic according to serializable business data included in the RMI request.

  The user distribution policy setting unit 190 has a function of receiving a request object including a user property that is called from the RMI over IIOP handling control 180 and acquired by the RMI over IIOP handling control 180.

Web application program modules (hereinafter referred to as “Web application modules”) 210 and 230 are set in a state where they can be executed on the JAVA EE server 100, and are uniquely defined by the Context-path within the Web container managed by the JAVA EE application server program. A program module is specified.
The Web application program modules 210 and 230 are executed when the JAVA EE server 100 distributes to the Web application program having the corresponding Context-path based on the URI included in the HTTP request from the HTTP client 10. Is done.

  The EJB application program modules (hereinafter referred to as “EJB application modules”) 220 and 240 are set in an executable state on the JAVA EE server 100 and are uniquely identified by the JNDI name in the JNDI tree managed by the JAVA EE application server program. A program module is specified.

  The RMI client 30 and the Web application program modules 210 and 220 that function as an EJB client access the JNDI tree structure when the EJB application module is called, and acquire a remote object of the EJB application program module to be called. Then, the method call function provided in the EJB application modules 220 and 240 is executed via this remote object.

  In addition, the JAVA EE server 100 includes a table information management unit configured to manage information in the execution suppression determination table 102 that is referred to when performing suppression target determination, and to perform initialization and update.

Hereinafter, this table information management unit (referred to as embodiment A) will be described.
As shown in FIG. 8, the table information management unit is used for execution suppression determination, and an execution suppression determination information reference unit 101 set as an API (Application Program Interface) that can be used at an arbitrary point in the application execution process. A determination information table storage unit that stores an execution suppression determination information table 102 including keyword information and the like, and a permanent information storage that stores information held in the execution suppression determination information table 102 as file information (execution suppression determination information permanent information) The management request is received from the means 103, the execution suppression determination information management unit 104 for executing the initialization and update processing of the information in the execution suppression determination information table 102, and the management request received from the management request transmission unit 107 described later. A management request receiving unit 105 that calls the execution suppression determination information management unit 104 based on the Management of the registration information and management request sent via the execution suppression determination information management unit 104 and the initialization requesting unit 106 for setting the startup of the management request receiving unit 105 and the execution suppression determination information input unit 108 Reference and update of the management request transmission unit 107 that transmits to the request reception unit, information registered in the execution suppression determination information table 102 sent from the outside (registration information), and information in the execution suppression determination information table 102 The execution suppression determination information input unit 108 for inputting a management request indicating a message requesting the management request to the management request transmission unit 107 is provided.

  It is assumed that the execution suppression determination information table 102 is read into the same Java memory as the application running on the Java EE server 100 and is implemented as HashMap. As a result, the processing operation of the execution suppression determination information reference unit 101 can be speeded up.

  Further, as described above, the execution suppression determination information reference unit 101 is provided as an API that can be used at an arbitrary point in the application, refers to the execution suppression determination information table 102, and includes keywords set in advance as arguments. It is determined whether or not there is a matching keyword.

  The permanent information storage unit 103 stores information held in the execution suppression determination information table 102 as file information (execution suppression determination information permanent information). As a result, even when the Java process of the JAVA EE application server 100 is restarted after normal or abnormal termination, the information in the execution suppression determination information table before the termination of the java process can be retained.

  The execution suppression determination information input unit 108 includes registration information sent from the outside to the JAVA EE application server 100, a management request, and registration information sent from a Web container set in the JAVA EE application server 100, The management request is received and input to the management request transmitting unit 107 is performed.

  In addition, since the execution suppression determination information management unit 104 and the management request transmission / reception unit 105 for updating and managing the execution suppression determination information table are installed, the user of the JAVA EE application server 100 can execute the execution suppression control. It is possible to focus on the design of the part that performs the execution suppression determination and the character string used for the execution suppression determination, which are essential parts.

  Next, the operation of the table information management unit will be described based on the flowcharts shown in FIGS.

  First, an operation for initializing the execution suppression determination information table 102 will be described with reference to the flowchart of FIG.

  First, when the application execution process is started in the Java EE server 100, the initialization unit 106 is executed (step S221). Here, the initialization unit 106 performs initial operation setting of the execution suppression determination information management unit 104 (step S221). S222).

  Here, when the execution suppression determination information management unit 104 stores the information held in the execution suppression determination information table 102 as file information in the permanent information storage unit 103 in advance, the permanent information storage unit 103 stores the execution information. The suppression determination information permanent information use flag is set.

  Next, the execution suppression determination information management unit 104 confirms the existence of the execution suppression determination information persistence information in the persistence information storage unit 103 (step S223), and the execution suppression determination information persistence information exists and is initialized. When the execution suppression determination information persistence information use flag at the time of conversion is set (step S224), the information included in the execution suppression determination information persistence information is used to initialize the execution suppression determination information table 102 Is performed (step S225).

  On the other hand, if the execution suppression determination information persistence information 103 does not exist or the execution suppression determination information persistence information use flag at initialization is not set, the execution suppression determination information management unit 104 executes the execution suppression determination The information table 102 is initialized in an empty state (no stored data) (step S226).

  As a result, the execution suppression determination information table 102 is set to a state that can be referred to by the execution suppression determination information reference unit 101.

  Further, when the initialization unit 106 is called by the application execution process (step S221), the initialization unit 106 sets the management request reception unit 105 to the operation activated state (step S227). The management request receiving unit 105 exists in the application execution process and enters a management request reception waiting state (step S228).

Next, an operation for performing the update process of the execution suppression determination information table 102 will be described based on the flowchart of FIG.
When updating the information in the execution suppression determination information table 102, first, as input information to the execution suppression determination information table 102, the management request transmission destination and the connection authority information with the management request transmission destination are the management request transmission unit. 107 is input (step S301).
Note that the input information to the management request transmission unit 107 may be set by an operator of the JAVA EE application server.
Next, the management request transmission unit 107 performs connection with the transmission destination of the management request using the connection authority information (step S302).

Further, the management request transmitting unit 107 calls the management request receiving unit 105 (step S303), and the management request receiving unit 105 calls the execution suppression determination information management unit 104 to make an update request for the execution suppression determination information table 102 ( Step S304).
Here, when the execution suppression determination information persistence flag is set (step S305: YES), the execution suppression determination information management unit 104 reflects the update information in the execution suppression determination information persistence information 103 (step S306). .
In addition, the execution suppression determination information management unit 104 reflects the update information in the execution suppression determination information table 102 (step S307). Next, the execution suppression determination information management unit 104 returns the update processing result of the execution suppression determination information to the management request transmission unit 107 via the management request reception unit 105 (step S308).

  Next, the operation flow of execution suppression determination performed by the execution suppression determination information reference unit 101 will be described based on the flowchart of FIG.

First, the execution suppression determination information reference unit 101 is called by specifying a keyword to be used for execution control determination from the HTTP request handling control unit 120, the JNDI lookup handling control unit 150, or the RMI over IIOP handling control unit 180 (step S401). .
Next, the execution suppression determination information reference unit 101 refers to the execution suppression determination information table 102 and confirms whether or not there is a keyword that matches the keyword specified in the argument of the execution suppression determination information reference unit 101 (step) S402). When the matching keyword is included in the execution suppression determination information table 102 (step S403: YES), the execution suppression determination information reference unit 101 determines that it is in the execution suppression state and returns the determination result (true) to the caller. (Step S404).

  On the other hand, when the matching keyword is not included in the execution suppression determination information table 102, the execution suppression determination information reference unit 101 determines that it is not in the execution suppression state, and returns the determination result to the caller (step S405).

[Other Embodiments of Table Information Management Unit]
Next, another embodiment (referred to as embodiment B) of the table information management unit will be described.

  The table information management unit (embodiment B) of the present embodiment has substantially the same configuration as the above embodiment, but as shown in FIG. 9, the execution suppression determination information reference unit 101, the execution suppression determination information table 102, and The execution suppression determination information management unit 104, the management request reception unit 105, and the initialization unit 106 are different from each other in that a java process 200 of a Java EE application server having an internal configuration is provided. Other configurations are the same as those in the above embodiment, and the same reference numerals are given to the same portions as those in the embodiment A of the table information management unit described above.

  The execution suppression determination information reference unit 101 is provided as an API that can be used at an arbitrary point of an execution process in an application set in the Java EE application server 100.

  The execution suppression determination information table 102 includes keyword information used for execution suppression determination. Here, a table is used for convenience of description, but it is different from the table information on the database. In this embodiment, it is implemented as a HashMap and expanded in the memory of the java process of the Java EE application server 100. .

The execution suppression determination information perpetuation information 103 is data information in which the information held in the execution suppression determination information table 102 is made permanent, and is set as normal file data.
The execution suppression determination information management unit 104 is a controller of the execution suppression determination information table 104 as in the above-described embodiment A.

  The management request reception unit 105 receives the management request from the management request transmission unit 107 and calls the execution suppression determination information management unit 104 based on the received management request. In the present embodiment, it is implemented as a managed object that conforms to the JMX specification of Java EE. It may be implemented as an original communication method using Socket.

The initialization unit 106 executes initialization processing that is invoked by the Java EE application server 100 when the Java process of the Java EE application server 100 is activated.
The management request transmission unit 107 transmits a management request such as referring to and updating information in the execution suppression determination information table 102. In this embodiment, it is implemented as a JMX client program. It is possible to implement an original communication method using Socket.

The execution suppression determination information input unit 108 inputs information to be registered in the execution suppression determination information table 102. In the present embodiment B, it is implemented as a command.
Next, the operation of the embodiment B will be described in detail with reference to the flowcharts of FIGS.

  First, the processing flow related to the initialization processing of the execution suppression determination information table 102 executed when the Java process of the Java EE application server is started will be described with reference to the flowchart of FIG.

First, the initialization unit 106 is called by the Java EE application server 100 (step S221), and the initialization unit 106 performs activation setting of the execution suppression determination information management unit 104 (step S222).
The execution suppression determination information management unit 104 checks the existence of the execution suppression determination information persistence information (step S223), the execution suppression determination information persistence information exists in the persistence information storage unit 103, and the initialization When the execution suppression determination information persistence information use flag is set (step S224), the execution suppression determination information table 102 is initialized using information included in the execution suppression determination information persistence information 103 (step S224). Step S225).
On the other hand, if the execution suppression determination information persistence information 103 does not exist or the execution suppression determination information persistence information use flag at initialization is not set, the execution suppression determination information management unit 104 executes the execution suppression determination. The information table 102 is initialized in an empty state (step S226).
As a result, the execution suppression determination information table 102 can be referred to from the execution suppression determination information reference unit 101.

  When the initialization unit 106 is called by the Java EE server 100 (step S221), the initialization unit 106 generates a management request reception unit 105 (step S227). The management request receiving unit 105 exists in the java process of the Java EE application server, and enters a management request reception waiting state (step S228).

  Next, an operation for performing the update process of the execution suppression determination information table 102 will be described based on the flowchart of FIG.

When updating the execution suppression determination information table 102, the operator inputs the input information to the execution suppression determination information table as the transmission destination of the management request and the connection authority information with the transmission destination of the management request (step S301). The management request transmission unit 107 connects to the management request transmission destination using the connection authority information (step S302). The management request transmission unit 107 calls the management request reception unit 105 (step S303), and the management request reception unit 105 calls the execution suppression determination information management unit 104 and makes an update request for the execution suppression determination information table 102 (step S304). ).
When the execution suppression determination information persistence flag is set, the execution suppression determination information management unit 104 reflects the update information on the execution suppression determination information persistence information (step S306).
The execution suppression determination information management unit 104 reflects the update information in the execution suppression determination information table 102 (step S307). The execution suppression determination information management unit 104 returns the update processing result of the execution suppression determination information to the management request transmission unit 107 through the management request reception unit 105 (step S308).

  Next, the operation flow of execution suppression determination performed by the execution suppression determination information reference unit 101 will be described based on the flowchart of FIG.

The execution suppression determination information reference unit 101 is called by specifying a keyword that is a character string as an argument (step S401). The execution suppression determination information reference unit 101 refers to the execution suppression determination information table 102 and confirms whether there is a character string that matches the character string specified in the argument of the execution suppression determination information reference unit 101 (step S402).
When the matching character string is included in the execution suppression determination information table 101, the execution suppression determination information reference unit 101 determines that the execution suppression state is set, and returns true to the caller (step S403).

  On the other hand, when the matching character string is not included in the execution suppression determination information table 102, the execution suppression determination information reference unit 101 determines that it is not in the execution suppression state and returns false to the caller (step S404).

Next, another embodiment (referred to as embodiment C) of the table information management unit will be described.
The embodiment C of the table information management unit includes a java process 200 (hereinafter referred to as “java process 200”) of the Java EE application server in the embodiment B, as shown in FIG. A management request transmission unit 309 that is connected to the management request reception unit 105 and transmits the management request to the outside of the java process 200 is provided.
In addition, a java process 300 of a Java EE server having an internal configuration substantially similar to that of the java process 200 of the Java EE server is provided along with the java process 200, and a persistent information storage means 313 provided in connection with the java process 300 is provided. Is different from Embodiment B described above.

The java process 300 (hereinafter referred to as “java process 300”) of the Java EE server includes the execution suppression determination information reference unit 101, the execution suppression determination information table 102, the execution suppression determination information management unit 104, the management request reception unit 105, and the initial stage. The execution suppression determination information reference unit 311, the execution suppression determination information table 312, the execution suppression determination information management unit 314, the management request reception unit 315, and the initialization unit 316 provided respectively corresponding to the conversion unit 106 are internal configurations. I have.
The management request receiving unit 315 is connected to the above-described management request transmitting unit 309 and is configured to receive information such as a management request sent from the java process 200.

  In addition, about the other structure in this Embodiment C, it is the same as that of the said embodiment, The same code | symbol shall be attached | subjected about the part same as Embodiment A and B of the table information management part mentioned above.

Here, the present embodiment C is configured to have a master-slave relationship among a plurality of different java processes. For example, the java processes are set on servers installed at remote locations and connected via a communication line. A configuration may be adopted.
In addition, the java process 200 of the Java EE application server and the java process 300 of the Java EE application server are set in a primary and secondary relationship, and the java process 300 of the Java EE application server is the java process 200 of the Java EE application server. Under the control of

  The plurality of different java processes may be executed on different Java EE application servers (Java EE servers).

  The java process 200 of the Java EE server holds attribute information of the java process 300 of the Java EE server, and operations on the java process 300 of the Java EE server are executed via the java process 200 of the Java EE server. be able to.

  Next, update processing of the execution suppression determination information table 102 and the execution suppression determination information table 312 in Embodiment C will be described.

First, when updating the execution suppression determination information table 102, the operator inputs the input information to the execution suppression determination information table as the transmission destination of the management request and the connection authority information with the transmission destination of the management request.
The management request transmission unit 107 connects to the transmission destination of the management request using the connection authority information. Next, the management request transmission unit 107 calls the management request reception unit 105, and the management request reception unit 105 calls the execution suppression determination information management unit 104 to make an update request for the execution suppression determination information table 102.
At this time, if the management request transmission information received by the management request receiving unit 105 includes the java process 300 of the Java EE application server, which is the process to be managed by the java process 200 of the Java EE application server, The request reception unit 105 calls the management request transmission unit 109.
The management request transmission unit 109 calls the management request reception unit 315, and the management request reception unit 315 calls the execution suppression determination information management unit 314 to make an update request for the execution suppression determination information table 312.
When the execution suppression determination information persistence flag is set for the java process 200 of the Java EE server, the execution suppression determination information management unit 104 reflects the update information in the execution suppression determination information persistence information 103. When the execution suppression determination information persistence flag is set for the java process 300 of the Java EE application server, the execution suppression determination information management unit 314 reflects the update information in the execution suppression determination information persistence information 313. To do.
Next, the execution suppression determination information management unit 104 reflects update information in the execution suppression determination information table 302, and the execution suppression determination information management unit 314 reflects update information in the execution suppression determination information table 312.
Here, the execution suppression determination information management unit 314 returns the update processing result of the execution suppression determination information table 312 to the management request transmission unit 109 via the management request reception unit 315. The execution suppression determination information management unit 104 returns the update processing results of the execution suppression determination information table 102 and the execution suppression determination information table 312 to the management request transmission unit 107 via the management request reception unit 105.

Next, the operation flow of the execution suppression determination performed by the execution suppression determination information reference units 101 and 311 will be described based on the flowchart of FIG.
Although the execution suppression determination information reference units 101 and 311 perform the same operation process, the operation of the execution suppression determination information reference unit 311 will be described here.

The execution suppression determination information reference unit 311 is called by specifying the property KEY = VALUE (step S501). Here, the execution suppression determination information reference unit 311 refers to the execution suppression determination information table 312, and confirms whether there is an entry that matches the KEY specified in the execution suppression determination information reference unit 311 (step S502). ).
If a matching entry is included in the execution suppression determination information table 312 (step S503: YES), the execution suppression determination information reference unit 311 confirms whether the entry includes a value that matches VALUE. This is performed (step S504).

  Here, when the entry includes a value that matches VALUE (step S505: YES), the execution suppression determination information reference unit 311 determines that it is in the execution suppression state, and returns true to the caller ( Step S506).

On the other hand, if the entry that matches in step S503 is not included in the execution suppression determination information table 312, or if the entry does not include a value that matches VALUE in step S505, the execution suppression determination information reference unit 311 It is determined that the caller is not in the execution suppression state, that is, it is determined that the caller is not subject to execution suppression, and false is returned to the caller (step S507).
As described above, when execution suppression is performed, the java process of the Java EE server may notify the management request transmission unit 107 of an error (error notification function).

  By configuring the table information management unit as described above, the user of the JAVA EE application server 100 can focus on the design of the location where execution suppression determination is performed and the character string used for execution suppression determination. .

[Description of Operation of Embodiment]
Next, the overall operation of this embodiment will be described.
First, a processing request sent from the HTTP client 10 is received, the processing request is analyzed (request analysis process), a transmission source of the processing request is specified (transmission source specifying process), and an execution process corresponding to the processing request is performed. It is determined whether or not to perform (execution process determination process).
Next, when the specified transmission source is a target for suppression of execution processing, the HTTP client 10 is notified of the suppression status of the execution processing to the transmission source (execution suppression notification process).

  Here, regarding the request analysis process, the transmission source identification process, the execution process determination process, and the execution suppression notification process, the execution contents may be programmed and executed by a computer.

  Next, the operation when the suppression target determination is performed in the HTTP request handling control unit 120 of the above embodiment will be described based on the sequence chart of FIG.

First, the HTTP client 10 transmits an HTTP request, which is a Web application module execution request, to the JAVA EE application server 100 (step S11).
The Web container operating in the JAVA EE application server 100 receives this HTTP request (step S21) and calls the HTTP handling control unit 120 (step S22).

Next, the HTTP handling control unit 120 analyzes the HTTP request (step S31), and when the HTTP request includes preset property information, the HTTP request transmission source executes the HTTP request. A process of determining whether or not it is a suppression target is performed (step S32).
Here, when it is determined that it is not an execution suppression target, the HTTP handling control unit 120 returns execution processing control for the HTTP request to the Web container (step S32: NO).

  Next, the web container executes the web application module corresponding to the HTTP request (step S23), and returns the processing result as an HTTP response to the HTTP client (step S24).

  On the other hand, when it is determined based on the property information that the transmission source of the HTTP request is a suppression target (step S32: YES), the HTTP handling control unit 120 notifies the Web application module 210 that notifies the preset processing blocking state. The HTTP request is forwarded (Forward), and the execution process control for the HTTP request is returned to the Web container (step S33).

  Next, the Web container executes the Web application module 210 that is the transfer destination of the HTTP request, and transmits the execution processing result (processing suppression state notification) to the HTTP client 10 as an HTTP response (step S25).

  The operation when the suppression target determination is performed by the JNDI lookup handling control unit 150 of the above embodiment will be described based on the sequence chart of FIG.

  First, the Web application modules 210 and 230 as the EJB / JNDI client, or the RMI client 30 (generally referred to as “lookup client”) instantiates (generates) the ContextFactory class provided by the JNDI lookup handling control 150 ( Together with step S41), the InitialContext of the JNDI lookup handling control 150 is acquired from the Factory class object (step S42).

  The lookup client specifies a JNDI name or name object in the home interface of the EJB to be called through the obtained InitialContext object, executes a lookup method and transmits a lookup request (step S43).

  The JNDI lookup handling control 150 suppresses the lookup request sent based on the JNDI name specified by the lookup method execution, the name object, and the properties (load information) stored in the map object set when the InitialContext was generated. It is determined whether or not it is a target (step S51: suppression target determination).

  Here, the JNDI lookup handling control 150 returns a preset exception notification to the lookup client when the lookup request transmission source (lookup client) is determined to be a suppression target (step S51: YES) (step S51). S52).

  If it is determined that the source of the lookup request (lookup client) is not subject to suppression (step S51: NO), the JNDI lookup handling control 150 sets the lookup request execution process in the JAVA EE server 100 in advance. Delegate to the given JNDI server (step S53).

The JNDI server returns the EJB Home interface object mapped to the JNDI name or name object specified in the lookup method to the lookup client (step S61).
Next, the lookup client acquires an EJB object using the acquired EJB Home interface object and calls an EJB method (step S45).

  Next, the operation when the suppression target determination is performed by the RMI over IIOP handling control unit 180 of the above embodiment will be described based on the sequence chart of FIG.

First, the lookup client calls an EJB method by sending an RMI request via the acquired EJB object (step S71).
Next, the RMI over IIOP communication control unit 170 receives the RMI request for the EJB method call, and calls the RMI over IIOP handling control unit 180 which is an implementation class of ServerRequestInterceptor (step S81).

  The RMI over IIOP handling control unit 180 determines whether or not the RMI request of the EJB method call is transmitted from the suppression target based on the EJB JNDI name, method name, and property included in the RMI request (determination target determination). (Step S91: execution suppression determination).

Here, when the RMI over IIOP handling control unit 180 determines that the transmission source of the RMI request of the EJB method call is a suppression target (step S91: YES), it returns an exception notification to the lookup client (step S92).
Further, the RMI over IIOP handling control unit 180 delegates the RMI request execution process to the EJB container set in advance in the JAVA EE application server 100 when the transmission source of the RMI request for the EJB method invocation is out of the suppression target. (Step S91: NO).

  Next, the EJB container executes the EJB method and returns an execution processing result to the lookup client (step S101). The EJB client and JNDI client obtain the EJB method call result (step S73).

  Next, based on the sequence chart of FIG. 5, the operation in which the HTTP request handling control unit 120 performs the suppression target determination when the user distribution policy class is set in the user distribution policy setting unit 130 of the above embodiment. explain.

First, the HTTP client 10 transmits an HTTP request that is an execution request for the Web application module 210 or 230 to the JAVA EE server 100 (step S111).
Next, the Web container set in advance on the JAVA EE server 100 receives the HTTP request (step S121) and calls the HTTP handling control unit 120 (step S122).

  Next, when there is a user distribution policy class implemented in an interface preset in the user distribution policy setting unit 130, the HTTP request handling control unit 120 uses a HTTP request as an argument based on the interface. A method of the distribution policy class is called (step S131).

Next, in the user distribution policy setting unit 130 class, the sent HTTP request is analyzed (step S141), and the HTTP request transmission source (HTTP client) suppresses execution processing based on the user's own distribution policy. It is determined whether or not it is a target.
If it is determined that the execution process is to be suppressed, a suppression target flag is set (step S142), and execution control for the HTTP request is returned to the HTTP request handling control unit 120.

Next, the HTTP request handling control unit 120 performs suppression target determination based on whether or not the suppression target flag is set (step S132: execution suppression determination).
Here, when it is determined that the transmission source of the HTTP request is not the suppression target (there is no suppression target flag), the HTTP request handling control unit 120 returns the HTTP request execution control to the Web container (step S132: NO).

  The web container executes the web application module corresponding to the HTTP request (step S123), generates the execution processing result and transmits it as an HTTP response to the HTTP client 10 (step S124), and the HTTP client 10 sends the HTTP response. Receive (step S112).

  Here, when it is determined that the transmission source of the HTTP request is the suppression target (there is a suppression target flag) (step S132: YES), the HTTP request handling control unit 120 notifies the preset execution process blocking state The HTTP request is transferred to the Web application module 210 to be forwarded (Forward), and the Web application module returns execution control of the HTTP request to the Web container (step S133).

  The web container executes the forward-destination web application module 210 and returns the processing result as an HTTP response to the HTTP client 10 (step S125). The HTTP client 10 receives the HTTP response (suppression state notification) (step S125). S113).

  Although the case where the user distribution policy class is set in the user distribution policy setting unit 130 has been described here, the user distribution policy setting units 160 and 190 may also be set in the case where the user distribution policy class is set. The lookup control unit 150 and the RMI over IIOP handling control unit 180 respectively perform suppression target determination in the same manner.

  Here, the operation of the suppression target determination in steps S32, S51, S91, and S132 will be described based on the flowchart of FIG.

  First, it is determined whether or not the sent HTTP request, lookup request, or RMI request (generically referred to as request information) is an execution request for an application included in the application name of the execution suppression determination condition table (FIG. 7). Perform (step S201).

Here, when the request information is an execution request not included in the execution suppression determination condition table, the transmission source of the execution request is determined as a non-execution suppression target (step S202).
Next, it is determined whether or not there is a condition setting for the application name (step S203). If there is no condition setting, the transmission source of the execution request is determined as an execution suppression target (step S210).

  Here, if there is a condition setting in the application name, it is determined whether there is a user (sender) key setting in the execution suppression determination condition table (step S204). If there is a user key setting, Thereafter, the user key is used as the suppression determination key (step S205). If no user (sender) key is set in the execution suppression determination condition table, a default key set in advance as a suppression determination key is used (step S206).

Next, it is determined whether or not a suppression determination key is included in the request information (step S207). If not included, the transmission source of the request information is determined as a non-execution suppression target (step S208).
If the suppression information is included in the request information, it is determined whether or not the value set in the suppression determination key matches the suppression determination value set in the execution suppression determination condition table (step S209). If they do not match, the request information transmission source is determined as a non-execution suppression target (step S208), and if they match, the request information transmission source is determined as an execution suppression target (step S210).

As described above, in this embodiment, it is possible to suppress and control an execution request for an application on a server without using other components such as a proxy server.
In addition, it is possible to quickly identify the request source based on the execution request (request information) in each of the Web application and EJB implemented on the JAVA EE application server. Changes can be made.

  Furthermore, because business applications executed on the JAVA EE application server are handled and controlled on the EJB container, resources such as database tables that can be used on the JAVA EE application server can be used to execute execution suppression judgment in the same way as normal applications. Can be used.

  The preset internal structure of the business application is a structure in which only a minimum amount of logic can be incorporated, and is a structure that is incorporated outside the application. For this reason, the mechanism shown in the present invention can be incorporated into an application implemented in a JAVA EE application server within a range that conforms to the JAVA EE standard.

  Furthermore, according to this embodiment, in order to meet the demands of each user and the application to be used, the JAVA EE application server operation system specifies the execution suppression target in addition to the standard functions based on general-purpose specifications. A function for limiting the request execution process can be added, and the specified execution suppression condition can be changed by the setting by the user.

Since the present invention can control system use temporary restriction from a specific request source and access source, it can be applied to use restriction control as a sanction procedure from a service provider to a user in a service via a network.
Further, the present invention can be applied to a specific user group in system maintenance on the server side and a temporary execution suppression for each time zone.
Furthermore, it can be applied as a technique for acquiring processing performance information for an HTTP request on the JAVA EE application server based on entry / exit information of server-side processing.

DESCRIPTION OF SYMBOLS 1 Server apparatus 5 Network 10 HTTP client 30 RMI client 100 JAVA EE application server 110 Session object 120 HTTP request handling control part 130, 160, 190 User distribution policy setting part 140 Application execution control information 150 JNDI lookup handling control part 170 RMI over IIOP call control unit 180 RMI over IIOP handling control unit 210, 230 Web application module 220, 240 EJB application module

Claims (11)

A request processing system having an input / output response processing unit that receives request information sent from a client, and an application server unit that performs an execution process according to the request information based on a preset application,
The application server unit specifies the transmission source of the request information based on the property information of the request information and determines whether to suppress the execution process based on the specified transmission source and is set in advance. An execution suppression determination unit that suppresses execution processing for the request information of the transmission source,
The request processing system, wherein the input / output response processing unit includes suppression state notification means for notifying the client of a suppression state of the execution process when the execution process is suppressed. In the request processing system according to claim 1,
The request processing system, wherein the application server unit is set in accordance with JAVA EE, which is a Java (registered trademark) standard for building a corporate information system. In the request processing system according to claim 1,
Request type execution in which the execution suppression determination unit specifies the request type of the request information based on the property information of the request information and determines whether to suppress the execution process based on the specified request type A request processing system comprising a suppression determination function. In the request processing system according to claim 2,
The application server unit includes a suppression determination condition setting unit that sets a suppression determination condition indicating a condition for determining whether or not to suppress the execution process based on a preset execution policy. Processing system. In the request processing system according to claim 4,
The application server unit includes a memory area in which the application is read during the execution process,
The request processing system, wherein the suppression determination condition is read in a state written together with the application in the memory area during the execution process. In the request processing system according to claims 4 and 5,
The request processing system, wherein the application server unit includes suppression condition information storage means for storing contents of the set suppression determination condition as file information. In the request processing system according to claim 4,
The application server unit includes an information search unit that determines whether information that matches the property information of the request information is included in the suppression determination condition;
An execution error notification for notifying a request execution error indicating that an execution process for the request information is suppressed to the transmission source of the request information when information that matches the property information is included in the suppression determination condition And a request processing system. In the request processing system according to claim 7,
The application server unit includes remote execution request means for transmitting a remote execution request to a different application unit connected via a preset network when performing the execution process, and property information included in the remote execution request. A remote execution determination unit that determines whether or not to suppress the remote execution process in response to the remote execution request based on the remote execution process, and when the remote execution process is suppressed, the remote execution process is set in advance for the requester of the remote execution process And a remote execution error notifying means for notifying the received error. In the request processing system according to claim 8,
A remote execution determination condition setting means for setting a remote execution suppression determination condition indicating whether or not to suppress the remote execution processing based on a preset execution policy is provided in the remote execution determination means. Request processing system. In a request processing method comprising: an input / output response processing unit that performs mutual communication with a client; and an application server unit that performs an execution process according to processing request information sent from the client, and controls the execution process
Whether to perform a request analysis process for receiving a processing request sent from the client and analyzing the processing request, a transmission source specifying process for specifying a transmission source of the processing request, and an execution process corresponding to the processing request And an execution suppression notification process for notifying the transmission source of the suppression state of the execution process when the specified transmission source is a target for suppression of the execution process. A request processing method characterized by the above. In a request processing program for controlling the execution process, comprising an input / output response processing unit that performs mutual communication with a client, and an application server unit that performs an execution process according to the process request information sent from the client.
Whether to perform a request analysis function for receiving a processing request sent from the client and analyzing the processing request, a transmission source specifying function for specifying a transmission source of the processing request, and an execution process corresponding to the processing request An execution process determination function for determining the execution process, and an execution suppression notification function for notifying the transmission source of the suppression state of the execution process when the identified transmission source is a target for suppression of the execution process. A request processing program characterized in that the request processing program is executed.

Images