JP2003141068A - Session management device, and session management method, program and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To manage a session under dialoguing without deteriorating the performance of a client/server system in the client/server system in a distributed object environment. SOLUTION: In this session management device, a cession management process 1 performs the session management between a client application 5 for performing a dialogue processing in the distributed object environment and a server application 4 mounted as a distributed object in cooperation with the server application 4. It controls, according to the request from the server application 4, a session management memory 3 for managing session state information provided in the process according, and also controls to manage the session state information which cannot be managed in the session memory 3 because of excessive session state information in a database 6 from the record accessed on the oldest day.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a session management device, a session management method, a program, and a recording medium that maintain a state during a session between a server and a client in a distributed object environment.

[0002]

2. Description of the Related Art There are two session states for client / server communication in a distributed object environment: stateless and stateful.

Stateless communication and stateful communication will be described below with reference to FIG.

FIG. 14 is a diagram for explaining the session state of both parties in the communication between the client and the server.

First, as shown in (a), "stateless" means that the server to be connected differs from the client in the first communication and the communication thereafter, and as shown in (b), the server connects to the server. It means that the information generated in the server cannot be maintained without some means when the client is different between the first communication and the subsequent communication.

On the other hand, stateful means that, as shown in (c), in the communication between the client and the server, the server process processed in the first communication and the subsequent communication is the same, so that the information generated in the server is maintained. The state that can be done.

Next, the server process is classified from the life cycle, and it is described whether the communication of the process is a stateless session or a stateful session.

Processes are classified into those that are resident in the system space in advance and wait for a service request from a client (type I), and those that are generated when a service request from a client (types II and III described later). . What is generated at the time of a service request from a client is a type that repeats generation and disappearance for each service request (Type II) and a series of service requests requested by the client (a plurality of service requests to realize processing. It is classified into a type that repeats generation and disappearance (type III) for each configuration.

Type I and type II are stateless sessions, and type III are stateful sessions.

Further, since the type II frequently produces and disappears the process which requires the overhead, it is considered that there are few products which perform such a process, and hence it is excluded from the targets of the process which performs the stateless session.

CORB for realizing a distributed object environment
A (Common Object Request Br)
The products that are compatible with the Maker Architecture) are those that realize only stateless sessions,
Some provide both stateless and stateful sessions.

[0012] CORBA is one of the standards for distributed object technology, and is OMG (Object Ma).
ORB (O approved by the management Group)
It is a specification of communication between the object request brokers. CORBA-compliant ORB provided by the vendor
By using the product, even if the client and server are heterogeneous machines, they can be easily connected.

A client requests a service from a server and a response is returned from the server to the client, which is referred to as a conversation here. This dialogue may be completed once or may be completed by a plurality of exchanges. The following dialogue (processing) refers to the case where the interaction is completed multiple times.

A shopping cart will be described below as an example of the dialogue.

(Request 1) The client requests the server to display a list of products of a particular group.

(Response 1) The server displays the requested product list.

(Request 2) From the product list, the client requests the server to insert the required number of specific products into the shopping cart and to display the product list of the next product group.

(Response 2) The server stores the requested products in the required number of shopping carts and displays the requested product list.

(Request 3) The client places a required number of specific products in the shopping cart,
Request the server to settle the items in the shopping cart.

(Response 3) The server puts the requested products in the requested number of products in the shopping cart, multiplies the product unit price by the product number for each product type in the shopping cart, and presents the total amount to the client.

Here, in the case of stateful communication, the above-mentioned shopping cart (information such as the product name and the number of purchases)
Can be in the server process.

However, in the case of stateless communication, the dialogue (request-response) is cut off each time,
Since the server process that processes each dialogue is not necessarily the same, it is not possible to have a shopping cart (information such as product name and purchase quantity) in the server process.

Hereinafter, a state such as a shopping cart having the above-mentioned product name and purchase quantity is referred to as session state information, and a mechanism for holding this during the interactive processing is referred to as session management.

Next, session management of the client / server system in the conventional distributed object environment will be described with reference to FIGS. In these figures, the ORB is used as a communication means between the client and the server.
IIOP (Internet Inter-O) is used as a communication protocol using (distributed object mechanism) communication.
RB Protocol).

FIG. 15 shows a client / server in which both the client and server are implemented as CORBA objects.
It is a block diagram which shows a server system.

When the communication between the client and the server in this figure is realized by a stateless session, even if a large number of clients connect to the server, there is no process generation / disappearance, the overhead is small, and the load on the system is low. Less than stateful. However, session management cannot be performed if session state information is included in the server application process.

On the other hand, when it is realized by a stateful session, when the number of clients connected to the server is large, the processes are frequently generated / erased, so that the load on the system is larger than that realized by the stateless. However, session state information can be included in the server application process.

However, even when realized in a stateful session, as shown in FIG. 15, the same client application 5 passes through the ORB 30 (CORBA compliant communication middleware) for the first time server application 4a and the second time server application 4b. In such a case, session management cannot be performed if the session state information is included in the server application process.

In such a case or when the above-mentioned stateless session is realized, a method of managing the session on the client application side can be considered.

However, if the client has the session state information, the session state information flows between the client and the server each time communication is performed, communication traffic increases, and there is a problem that the response is deteriorated.

FIG. 16 shows WWW (World Wide).
C) for both client and server in the Web environment.
It is a block diagram which shows the client / server system implemented as an ORBA object.

As shown in the figure, V of the Web browser 32
The client application 5 operating in the M (Virtual Machine) environment is the server application 4 via the Web server 33 in the communication of the ORB 30.
Call the services a to 4b.

In this case, the session management method and its problem are the same as in the case of FIG. Further, in addition to the problem of the session management method, when a firewall is built on the server side, the TCP / IP port of IIOP must be opened, which is a cause of being shunned in security management.

FIG. 17 is a block diagram showing an example of a client / server system in a form based on the problem in constructing the firewall shown in FIG.

As shown in the figure, only the server side, that is, Java (registered trademark) Servlet 34, server application 4a, and server application 4b are CO
It is implemented as an RBA object.

There is a Servlet container in the Web server 33, and here, Java (registered trademark) Servl is provided.
Run et34 and run Java (registered trademark) Servl
et 34 communicates with the client application 5. When receiving a request from the client application 5, the Java (registered trademark) Servlet 34 calls the service of the corresponding server application 4a or server application 4b. The processing result of the called server application 4a or server application 4b is Java (registered trademark) S.
Returning to the servlet 34, Java (registered trademark) Se
The rvlet 34 returns a response to the client application 5.

That is, message information between the client application 5 and the server application 4a or the server application 4b is exchanged via the Java (registered trademark) Servlet 34. In this case, the client application 5 and Java
The communication protocol between the (registered trademark) Servlet 34 is HTTP (Hyper Text Transfer).
Protocol), and Java (registered trademark) Se
The communication between the rvlet 34 and the server application 4a or the server application 4b is IIOP.

In this form, when a firewall is constructed, it is only necessary to open the HTTP port, so the security management problem in the case shown in FIG. 16 is eliminated.

However, session management has the following problems.

For session management in the server application, the communication protocol between the client application 5 and the Java (registered trademark) Servlet 34 is HT.
Since it is a TP, it becomes a stateless session. Therefore, even if the communication between the Java (registered trademark) Settlet 34 / server application 4a or server application 4b is a stateful session, session management is difficult.

The other problems of session management are the same as those shown in FIG.

In this embodiment, as another method, S
AP for session management prepared for the servlet
There is a method of using I. Using this, you can save the session state information as an object. This object is identified by a session ID. The session ID is used during the interactive processing to manage the session information.

This form will be described below with reference to FIG.

Java (registered trademark) Servlet 34
When receiving the request from the client application 5, the client sends the message information from the client application 5 to the server application 4a.

After performing the process, the server application 4a provides the process result (telegram) and the session state information to Ja.
Return to va (registered trademark) Servlet 34.

Java (registered trademark) Servlet 34
Obtains the session ID of this object by converting the session state information into an object using the session management API. Java (registered trademark) Servlet 3
4 uses the client application 5 for session I
Returns the response of D and the message. Java (registered trademark) S
The servlet 34 receives a session ID and a message request from the client application 5.

Java (registered trademark) Servlet 34
Obtains session state information from the object corresponding to the session ID and passes the message and the session state information to the server application 4b. The same process is repeated thereafter.

This system is based on Java (registered trademark) Ser.
The session between the vlet 34 / server application 4a or the server application 4b is effective because it can be applied in either stateless or stateful, but it is used only in a limited environment such as WWW environment.

The examples shown in FIGS. 15 to 17 are the ORBs.
A session management method for a client / server system operating in a distributed object environment using communication.

In addition to the distributed object environment,
As a method of managing the session, there is a method of using an external disk file or memory.

As the external disk file, a method of using a database or a file with an index can be considered.

The session management method using the database and its problems will be described below.

In this method, a unique session ID is assigned to each client, that is, each interaction process, and the session ID is used as a database key. The session information is stored in the database record for each key.

Although this method is effective, the fact that such access must be performed in addition to the database access, which is business data, can cause a deterioration in performance.

Next, a method of using the memory will be described.

As a method of using the memory, there are a method of using the memory inside the process and a method of using the shared memory.

First, in the method of using the memory inside the process, there are a method of sequentially allocating the memory according to the interactive processing that occurs, and a method of securing the memory for the maximum number of simultaneous interactive processing that can occur in advance. . In the former case,
When high traffic occurs, it may cause a memory shortage depending on the system. On the other hand, in the latter case, there is no fear of running out of memory because the processing is performed in the memory secured in advance. However, if the traffic volume exceeds the predicted volume, the secured memory will be insufficient and it will be difficult to guarantee the session information.

In the method of using the shared memory, the process for accessing the shared memory is operated on the server,
Some server applications send and receive session information through this process, and some server applications use a shared memory access API provided by the system to send and receive session information. In these cases, when high traffic occurs, a large amount of shared memory is used, which may cause deterioration of server performance.

As a patent application which is a developed form of session management using a shared memory, Japanese Patent Laid-Open No.
001-14242. In the present invention, the session management server also has the function of the distributed management server, so it is possible to prevent the use of a large amount of shared memory during high traffic. However, the TP monitor for load balancing on the server side It is not applicable to applications that run under the control.

Further, the present invention is limited to the WWW environment, and the server application is implemented by CGI (Common Gateway Internet).
face) environment and is limited to implementation by CGI as a session management function, and is not widely applied to client / server systems operating in other environments.

[0061]

As described above, in the client / server system, when managing session state information, there are a method of managing by the client and a method of managing by the server. However, both of them have a problem of response, a problem of memory management, a problem of application environment, a problem of deterioration of server performance, etc. which occur due to an increase in communication traffic.

The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a client application that performs interactive processing in a distributed object environment and a server application implemented as a distributed object. A session management process implemented as a distributed object performs session management in cooperation with a server application implemented as the distributed object, and a controller in the session management process performs session management in response to a request from the server application. It controls the session management memory that manages the session status information provided in the process, and the session status information that cannot be managed in the session management memory due to excessive session status information is stored in the oldest During a dialog in a client / server system in a distributed object environment, by controlling the stored records (records with the longest elapsed time since the last access) to manage in a database provided outside the session management process. Session management can be performed without degrading the performance of the client / server system, and session management of the client / server system operating in a distributed object environment can be performed flexibly without depending on the platform. An object is to provide an apparatus, a session management method, a program, and a recording medium.

[0063]

A first aspect of the present invention is directed to a client application (client application 5 shown in FIG. 1) for interactive processing in a distributed object environment and a server application implemented as a distributed object (FIG. 1). In the session management device that manages the session with the server application 4) shown in FIG. 1, a session management process implemented as a distributed object (session management process 1 shown in FIG. 1 (executed by a CPU (not shown) of the server device 100)). However, the session management between the client application and the server application is performed in cooperation with the server application implemented as the distributed object.

In a second aspect of the present invention, the session management process includes a session management memory (session management memory 3 shown in FIG. 1) for managing session state information in the process, and control of the session management memory. And a controller (buffer controller 2 shown in FIG. 1) that performs session control, the controller controls the session management memory in response to a request from the server application that requires session management, and the session state information is excessive. It is characterized in that the session state information which can no longer be managed in the management memory is managed by a database provided outside the session management process from the record accessed the earliest.

In a third aspect of the present invention, the controller secures the session management memory and activates a connection to the database when the session management process is activated (memory securing section shown in FIG. 1). 21), a record control unit (record control unit 22 shown in FIG. 1) that controls the session management memory in response to a request from the server application, and session state information that cannot be managed in the session management memory due to excessive session state information. At the request of the record control unit to write to the database from the record accessed the earliest, and the session state information in the database required by the record control unit is requested by the record control unit. From the database, the session management Characterized in that it comprises a record monitor unit for performing it back to re (record monitoring unit 23 shown in FIG. 1).

In a fourth aspect of the present invention, the record control unit secures a record for storing session state information in the session management memory, which is requested by the server application. Record allocation service 22a), a record reading service that acquires session state information from the record in the session management memory (record reading service 22b shown in FIG. 1), and a record writing service that stores the session state information in the record. (Record writing service 22c shown in FIG. 1)
And a record release service (record release service 22d shown in FIG. 1) that releases the record in which the session state information that is no longer required to be stored is released.

According to a fifth aspect of the present invention, each service of the record control unit is a session ID given by the server application that requires session management.
The session management memory is controlled based on the above.

A sixth aspect of the present invention is characterized in that an interface from the server application that requires session management of each service of the record control unit does not depend on an environment in which the session management process operates. To do.

A seventh invention according to the present invention is characterized in that all the information generated during the session is managed as the session state information.

An eighth invention according to the present invention is implemented as a distributed object in a session management method for managing a session between a client application which performs interactive processing in a distributed object environment and a server application which is implemented as a distributed object. A session management process (session management process 1 shown in FIG. 1) is used to manage a session between the client application and the server application in cooperation with the server application implemented as the distributed object.

In a ninth aspect of the present invention, the session management process includes a session management memory (session management memory 3 shown in FIG. 1) for managing session state information in the process, and control of the session management memory. And a controller (buffer controller 2 shown in FIG. 1) that performs session control, the controller controls the session management memory in response to a request from the server application that requires session management, and the session state information is excessive. It is characterized in that the session state information which can no longer be managed in the management memory is managed by a database provided outside the session management process from the record accessed the earliest.

In a tenth aspect of the present invention, the controller secures the session management memory and activates a connection to the database when the session management process is activated (memory securing section shown in FIG. 1). 21), a record control unit (record control unit 22 shown in FIG. 1) that controls the session management memory in response to a request from the server application, and session state information that cannot be managed in the session management memory due to excessive session state information. At the request of the record control unit to write to the database from the record accessed the earliest, and the session state information in the database required by the record control unit is requested by the record control unit. From the database the session management Characterized in that it comprises a record monitor unit for performing it back into memory (record monitoring unit 23 shown in FIG. 1).

In an eleventh aspect of the present invention, the record control unit secures a record for storing session state information in the session management memory, which is requested by the server application. Steps S301 to S304), a record reading service that acquires session state information from the record in the session management memory (steps S401 to S408 in FIG. 8), and a record writing service that stores the session state information in the record (FIG. 8). 9
Of steps S501 to S507) and a record release service (steps S601 to S605 of FIG. 10) for releasing the record in which the session state information that is no longer required to be managed is stored.

In a twelfth aspect of the present invention, each service of the record control unit is a session I provided from the server application that requires session management.
The session management memory is controlled based on D.

A thirteenth invention according to the present invention is characterized in that an interface from the server application which requires session management of each service of the record control unit does not depend on an environment in which the session management process operates. To do.

A fourteenth aspect of the present invention is characterized in that all the information generated during a session is managed as the session state information.

The fifteenth invention according to the present invention is as follows.
14 is a program for realizing the session management method described in any one of 14 above.

The sixteenth invention according to the present invention is as follows.
The program for executing the session management method described in any one of 14 is recorded on a recording medium in a computer-readable manner.

[0079]

BEST MODE FOR CARRYING OUT THE INVENTION First, an outline of a session management apparatus of the present invention will be described.

In an environment in which the server of the client / server system that performs interactive processing is implemented as a distributed object, a resident process that manages sessions (hereinafter,
Session management process) is implemented as a server for distributed objects.

Here, a method of implementing as a distributed object by using a CORBA compliant ORB product will be shown.
The server application performing the interactive processing and the session management process cooperate with each other in the distributed object environment to realize session management.

The session management process uses the internal memory and database table of the process to manage session state information. The memory is used to speed up session management, and the database table is used to solve the memory shortage problem that occurs in the memory management.

Since the interface for accessing the session management process of the server application which is performing the interactive processing is implemented as a CORBA-compliant distributed object, no matter where the session management process operates in the distributed object environment. No need to change. This requires optimization of only the session management process in addition to the interaction processing between the client and server, and the machine type and OS (Ope).
It means that it may be possible to select a platform such as a rating system. For example, if a machine with a high cost performance of physical memory is selected, a large amount of memory can be consumed, so that session management can be speeded up.

In the session management process, an area for session state information is secured inside. Session state information for each interactive process is managed here. When the number of conversation processes that occur at the same time increases, that is, the session state information to be managed increases and the session state information area overflows, the oldest managed session state information is extracted from the session state information area, Manage it in the database. As a result, the latest session state information is managed in the memory, which contributes to returning a high-speed response to the client who makes frequent service requests.

Since the session status information area is secured when the session management process is started, there is no fear of memory shortage caused by long-time operation.

In order to maximize the performance of session management, the size of the secured session state information area is set to the maximum number of interactive processes that can occur at the same time (hereinafter also referred to as the maximum traffic amount) as long as the system performance allows. ) And set. Even if access exceeds the maximum traffic volume, it is safe because it is managed by the database. Further, the fact that it is managed by the database also eliminates the need to secure an area with a safer amount, that is, a redundant area, in the memory in addition to the expected maximum traffic volume.

The session management process assigns a unique session ID to each interactive process, and the session I
The session state information is managed using the session state information area in the memory and the table record of the database table for each D. Further, using this session ID, session management is performed by cooperating with a server application that performs interactive processing.

The functions of the session management apparatus of the present invention described above will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing an overall client / server system to which a client / server session management device operating in a distributed object environment according to an embodiment of the present invention can be applied. It shows the cooperation of the management processes, the structure of the session management process, and the structures of the memory and the database table managed by the session management process.

In the figure, reference numeral 200 denotes a client device, which is constituted by an information processing device such as a personal computer or a workstation. The client application 5 operates on this client device 200 (executed by a CPU (not shown) of the client device 200). Further, reference numeral 100 denotes a server device, which is constituted by an information processing device such as a personal computer or a workstation. Information processing device 100, 20
Reference numeral 0 has a CPU, a ROM, a RAM, and other recording media such as a hard disk (HD), and the CPU can load a program stored in the ROM or another recording medium into the RAM and execute the program. . The server application 4 operates on this server device 100 (executed by a CPU (not shown) of the server device 100). Furthermore, the client device 200 and the server device 100 are connected to a network 31 such as a LAN or the Internet.
It is configured to be capable of bidirectional communication via.

The client / server system including the client application 5 and the server application 4 is a client / server system which operates in a distributed object environment using ORB communication, and is shown in FIGS. It may be either case.

In the server device 100, 1 is a session management process (a CPU (not shown) of the server device 100).
When the server (server application 4) of the client / server system that performs interactive processing as described above is implemented as a distributed object, it is implemented as a distributed object server by a CORBA-compliant ORB product. , Has a buffer controller 2 and a session management memory 3 inside, is resident in the system space, and can bidirectionally communicate with the server application 4 via the ORB 30. The buffer controller 2 is composed of a memory securing unit 21, a record control unit 22, and a record monitoring unit 23.

A memory securing unit 21 secures the session management memory 3 in the RAM (not shown) when the session management process 1 is started, and connects to the database 6 on the HD (not shown) to access the table record of the session management table 61. Prepare to do.

The record control unit 22 controls a record in the session management memory based on the session ID in response to a request from an application (server application 4) that wants to manage session state information.
The ORB 30 has the following four services (22a to 22d) provided to the server application 4.

Record allocation service 22a The record allocation service 22a assigns a unique session ID to each interactive process and secures a record in the session management memory 3 for storing a pair of session ID and session state information. Then, the session ID is returned to the server application 4 which is performing the interactive processing.

Record read service 22b The record read service 22b acquires the session state information from the record in the session management memory 3 based on the session ID from the server application 4 which is performing the interactive processing.

Record write service 22c The record write service 22c stores the session state information in the record based on the session ID from the server application 4 which is performing the interactive processing.

Record release service 22d The record release service 22d releases the record in which the session state information that is no longer required to be stored is stored based on the session ID from the server application 4 which is performing the interactive processing. .

The record monitoring unit 23 controls the following three functions (-).

Session status information that cannot be managed in the session management memory due to excessive session status information (for example, the earliest record accessed in the session management memory 3 (the record having the longest elapsed time since the last access). )) Is written to the session management table 61 of the database 6 by using the session ID as a key in response to a request from the record allocation service 22a. The written record in the session management memory 3 is released.

Upon request from the record reading service 22b, the record writing service 22c, or the record releasing service 22d, the record control unit 2
Session status information (database session management table 6 of database 6) in the database table required in 2.
(The requested record in 1) is written to the released record in the session management memory 3. The table record in the written session management table 61 is deleted. When there is no released record in the session management memory 3, the earliest accessed record in the session management memory 3 is written to the session management table 61 using the session ID as a key, and the written session management memory 3 is written. After releasing the relevant record in the session management table 6
Write out the requested record in 1.

The time-out record is deleted from the time stamps on the records in the session management memory 3 and the session management table 61.

Next, in the client device 200,
The client application 5 uses the network 31
The service of the server application 4 can be called (requested) via the. The server application 4 realizes cooperation with the session management process 1 by calling each service of the record control unit 22 in the ORB 30, executes a process according to a request from the client application 5, and displays the process result. Client application 5 as a response
Reply to.

The session management process 1 uses the CO
Since it is implemented as an RBA-compliant distributed object, the interface from the server application 4 that is performing interactive processing for each service 22a to 22d of the record control unit 22 depends on the environment as long as the session management process operates in the distributed object environment. do not do. That is, even if the operating machine is changed, the server application that implements the interface is not changed.

Therefore, in FIG. 1, the server application 4, the session management process 1, and the database 6 are
The case where it is implemented on the same server device 100 has been described, but the server application 4, the session management process 1, and the database 6 are configured to be implemented on different devices (any platform may be used). It is also possible.

With the above configuration, the problem of response caused by the increase in conventional communication traffic,
A server application 4 which solves memory management problems, application environment problems, and server performance deterioration problems by constructing a resident process that manages sessions, and is implemented as a distributed object that performs interactive processing.
The session state information can be managed by cooperation with the session management process 1 implemented as a distributed object resident in the system space.

As the session state information, all information generated during the session such as a shopping cart is targeted.

FIG. 2 is a diagram showing the flow of session management of the client / server system shown in FIG. 1. The same components as those in FIG. 1 are designated by the same reference numerals. The flow of session management will be described below with reference to FIG.

When the session management process 1 is started, the memory securing unit 21 in the buffer controller 2 stores the maximum record that can store session state information from the property file 7 stored in the HD (not shown) in the server apparatus 100. Read the number and session state information area length.

Next, the memory securing section 21 secures an area of (maximum number of records × session state information area length) as the session management memory 3. Also, the database 6 is connected to prepare for accessing the table record of the session management table 61.

When the client application 5a starts a dialogue with the server application 4a, the server application 4a receives the record allocation service 22a.
Request for record allocation.

The record allocation service 22a finds a record in the session management memory 3 that is not currently used. In FIG. 2, the record 3a is found. The record allocation service 22a assigns a unique key code as the session ID. In FIG. 2, “1” is assigned. The record allocation service 22a stores the session ID "1" in the session ID area of the record 3a. The record allocation service 22a has a session ID
“1” is returned to the server application 4a.

The server application 4a passes the session ID "1" and the session state information to the record writing service 22c after processing such as database access (not shown) (processing according to the request from the client application 5). . The record writing service 22c stores the session state information in the session state information area of the record 3a whose session ID is "1".

The server application 4a returns the session ID "1" and the processing result to the client application 5a.

Next, the client application 5a
However, when the server application 4a makes a service request including the session ID "1", the server application 4a passes the session ID "1" to the record reading service 22b.

The record reading service 22b reads the session state information from the record 3a having the session ID "1" and returns the session state information to the server application 4a.

The server application 4a performs processing (processing according to a request from the client application 5) based on the data from the client application 5 and the session state information.

The server application 4a passes the session ID "1" and the session state information to the record writing service 22c.

The record writing service 22c stores the session state information in the session state information area of the record 3a whose session ID is "1".

The server application 4a returns the session ID "1" and the processing result to the client application 5a.

Next, the client application 5a
Makes a service request including the ID "1" to the server application 4b, the server application 4b
Session ID to the record reading service 22b
Pass "1".

The record reading service 22b reads the session state information from the record 3a whose session ID is "1" and returns the session state information to the server application 4b.

The server application 4b processes based on the data and session state information from the client application 5a (client application 5a
Process according to the request from).

The server application 4b passes the session ID "1" and the session state information to the record writing service 22c.

The record writing service 22c stores the session state information in the session state information area of the record 3a whose session ID is "1".

The server application 4b returns a response including the session ID "1" to the client application 5a.

The client application 5a requests the server application 4b to end the interactive processing including the session ID "1".

The server application 4b passes the session ID "1" to the record reading service 22b.

The record reading service 22b reads the session state information from the record 3a having the session ID "1" and returns the session state information to the server application 4b.

The server application 4b performs termination processing based on the data and session state information from the client application 5a.

The server application 4b passes the session ID "1" to the record release service 22d.

The record release service 22d releases the record 3a whose session ID is "1".

The server application 4b returns a final response to the client application 5a.

The dotted line in FIG. 2 indicates that the client application 5b calls the services of the server application 4c and the server application 4d, the server application 4c and the server application 4d cooperate with the session management process 1, and the session status for the record 3b. Indicates that information is being written or read.

The record allocation service 22a requests the record monitoring unit 23 to release the record when all the records have been allocated and cannot be newly allocated.

The record monitoring unit 23 saves the contents of the oldest accessed record in the session management table 61 of the database 6 using the session ID as a key. Then, the record is released. The released result is returned to the record allocation service 22a.

The record allocation service 22a continues the processing.

Record read service 22b, record write service 22c, record release service 22
When each of the d's accesses the session management memory 3 and cannot find the record corresponding to the session ID, the record monitoring unit 23 displays the session I
A request is made to search the session management table 61 for a corresponding record in which D matches.

The record monitoring unit 23 searches the session management table 61 using the session ID as a key.
If the record exists, the session management memory 3
Return the record to the empty record of. If there is no free space, the above-mentioned release processing is performed.

The record monitoring unit 23 responds to the request source that the record has been returned to the session management memory 3.

Record read service 22b, record write service 22c, record release service 22
Each of d continues processing.

The record monitoring unit 23 constantly monitors the time stamps on the records in the session management memory 3 and the session management table 61, and deletes the records that have timed out.

The above is the flow of session management.

The session management procedure of the client / server system shown in FIG. 1 will be described below with reference to the flowcharts of FIGS.

FIG. 3 is a flow chart showing an example of the first control processing procedure in the embodiment of the present invention.
It corresponds to the processing in the client application 5 shown in FIG. In addition, the process of this flowchart is as shown in FIG.
It is assumed that the CPU (not shown) of the client device 200 shown in FIG. 2 executes the program based on the program stored in the recording medium. Further, S101 to S108 indicate each step.

First, in step S101, the client application 5 transmits a dialog start request (start request) to the server application 4, and in step S102, when the session ID and the processing result are received from the server application 4 as a response, step S103 At, the received processing result is displayed.

Next, in step S104, it is determined whether or not the dialogue is to be ended. If the dialogue is not to be ended yet, in step S105, the client application 5 requests the service request including the session ID in the server application 4 ( Request) and the process returns to step S102.

On the other hand, when ending the dialogue in step S104, the client application 5 issues a termination request (termination request) of the dialogue processing including the session ID to the server application 4 in step S106.

Next, in step S107, the final response from the server application 4 is received, and in step S108, the final processing result is displayed, and the processing ends.

Incidentally, steps S101 and S10 in FIG.
5, the request made to the server application in S106 may be for different server applications (for example, the server applications 4a to 4b shown in FIG. 2). However, it is assumed that the request and the response form one set and are performed between the same client application and server application.

4 to 6 are flowcharts showing an example of the second control processing procedure in the embodiment of the present invention, and correspond to the processing in the server application 4 shown in FIG. Note that the processing of this flowchart is executed by the CPU (not shown) of the server apparatus 100 shown in FIG. 1 based on the program stored in the recording medium. Further, S201 to S218 indicate each step.

First, in step S201, a request from the client application 5 is received, and in step S202, it is determined whether the request is a dialogue start request. If it is determined that the request is a dialogue start request, In S203, a request for record allocation is made to the record allocation service 22a of the session management process 1, and in step S204, the session ID is acquired from the record allocation service 22a of the session management process.

Next, in step S205, the processing requested by the client application 5 at the time of the dialogue start request is executed, and in step S206,
The session ID and session state information are transmitted to the record writing service 22c of the session management process 1 to request writing of the session state information.

Next, in step S207, the session ID and the processing result are transmitted to the client application 5, and the process returns to step S201.

If it is determined in step S202 that the request from the client application 5 is not the dialogue start request, in step S208
It is determined whether the request from the client application 5 is a dialogue end request, and if it is determined that the request is not a dialogue end request, in step S209, the record reading service 22 of the session management process 1
Send the session ID to b and request the reading of the session state.

When the session state information is acquired from the record reading service 22b of the session management process 1 in step S210, the process requested by the client application 5 is executed in step S211, and the server application 4 executes the session in step S212. The session ID and session state information are transmitted to the record writing service 22c of the management process 1 to request writing of the session state.

Next, in step S213, the session ID and the processing result are transmitted to the client application 5, and the process returns to step S201.

On the other hand, when it is determined in step S208 that the request from the client application 5 is the dialogue end request, in step S214,
The session ID is sent to the record reading service 22b of the session management process 1 to request reading of a record (session state).

When the session state information is acquired from the record reading service 22b of the session management process 1 in step S215, the ending process is executed in step S216.

Next, in step S217, the record release service 22d of the session management process 1 is requested to release the record, in step S218, the final response is transmitted to the client application 5, and the process returns to step S201.

The process of the server application shown in FIGS. 4 to 6 is resident in the system space in advance and waits for a service request from the client, like the type I shown in the section of the prior art. Alternatively, it may be generated at the time of a service request from the client, like the types II and III shown in the column of the conventional technique, and the processing from the step S203 to the start request from the client application. S207,
Steps S209 to S213, which are processes for requests other than start / end requests, and steps S214 to S218, which are processes for end requests, may be performed by the same server application (process), or the server shown in FIG. Different server applications (processes) such as the applications 4a and 4b may be used.

Each service of the session management process 1 will be described below with reference to FIGS. 7 to 10. In addition,
The session management process 1 is configured in advance by the memory securing unit 21 in the session buffer controller 2 at the time of activation.
The maximum number of records that can store the session state information and the session state information area length are read from the property file 7 stored in the HD (not shown) in the server apparatus 100, and the session management memory 3 stores (maximum number of records x session). It is assumed that an area of (state information area length) is secured, and further connection with the database 6 is made and preparations for accessing the table record of the session management table 61 are made.

FIG. 7 is a flow chart showing an example of the third control processing procedure in the embodiment of the present invention.
It corresponds to the processing of the record allocation service 22a of the session management process 1 shown in FIG. Note that the processing of this flowchart is executed by the CPU (not shown) of the server apparatus 100 shown in FIG. 1 based on the program stored in the recording medium. In addition, S301 to S304
Indicates each step.

Upon receiving the record allocation request from the server application 4, in step S301, the record allocation service 22a determines that the session management memory 3
To determine if there are any records currently unused in
If it is determined that there is a record that is not currently used, the process proceeds to step S303. On the other hand, if it is determined that there is no record that is not currently used, step S30
In 2, the record monitoring unit 23 saves the oldest accessed record in the database 6.

Next, in step S303, the record allocation service 22a allocates a unique record as the session ID and stores it in the session management memory 3, and in step S304, the record allocation service 22a causes the server application 4 to store the session ID.
D is transmitted, and the process ends.

FIG. 8 is a flow chart showing an example of the fourth control processing procedure in the embodiment of the present invention.
It corresponds to the processing of the record reading service 22b of the session management process 1 shown in FIG. Note that the processing of this flowchart is executed by the CPU (not shown) of the server apparatus 100 shown in FIG. 1 based on the program stored in the recording medium. In addition, S401 to S4
08 indicates each step.

Upon receiving the record read request from the server application 4, the record read service 22b receives the session I in step S401.
It is determined whether or not the record corresponding to D exists in the session management memory 3, and if it is determined that there is, a step S
Proceed to 406. On the other hand, if it is determined that there is not, in step S402, the record monitoring unit 23 determines whether or not the record corresponding to the session ID exists in the database 6, and if it is determined that there is no record, step S402.
At 408, the error information is transmitted to the server application 4, and the process ends.

On the other hand, in step S402, the session I
When it is determined that the record corresponding to D exists in the database 6, in step S403, the record monitoring unit 23 determines whether or not there is a record that is not currently used in the session management memory 3, and it is determined that there is a record. If so, the process proceeds to step S405. On the other hand, when it is determined that there is no record that is not currently used, the record monitoring unit 23 saves the record accessed earliest in the database 6 in step S404.

Next, in step S405, the record monitoring unit 23 returns the record from the database 6 to the session management memory 3.

Next, in step S406, the record reading service 22b reads the session state information of the record corresponding to the session ID, and in step S407, the record reading service 22b.
Sends the session state information to the server application 4 and ends the process.

FIG. 9 is a flowchart showing an example of the fifth control processing procedure in the embodiment of the present invention.
It corresponds to the processing of the record writing service 22c of the session management process 1 shown in FIG. Note that the processing of this flowchart is executed by the CPU (not shown) of the server apparatus 100 shown in FIG. 1 based on the program stored in the recording medium. In addition, S501 to S5
07 indicates each step.

When a record write request is received from the server application 4, in step S501,
The record writing service 22c determines whether or not the record corresponding to the session ID is present in the session management memory 3, and if it is determined that the record is present, the step S50 is performed.
Go to 6. On the other hand, if it is determined that there is not, step S
In 502, the record monitoring unit 23 determines whether or not there is a record corresponding to the session ID in the database 6, and if it is determined that there is not, a step S50.
In 7, the record writing service 22c sends error information to the server application 4 and ends the processing.

On the other hand, in step S502, the session I
If it is determined that the record corresponding to D exists in the database 6, the record writing service 22c determines in step S503 whether or not there is a record currently unused in the session management memory 3, and it is determined that there is. If so, the process proceeds to step S505. On the other hand, if it is determined that there are no records currently unused,
In step S504, the record monitoring unit 23 stores the earliest record accessed in the database 6
To evacuate.

Next, in step S505, the record monitoring unit 23 returns the record from the database 6 to the session management memory 3.

Next, in step S506, the record writing service 22c writes the session state information in the record corresponding to the session ID, and ends the processing.

FIG. 10 shows a sixth embodiment of the present invention.
2 is a flowchart showing an example of a control processing procedure of the record release service 22d of the session management process 1 shown in FIG. Note that the processing of this flowchart is executed by the CPU (not shown) of the server apparatus 100 shown in FIG. 1 based on the program stored in the recording medium. In addition, S601 to S60
Reference numeral 5 indicates each step.

When the record release request is received from the server application 4, in step S601, the record release service 22d determines whether or not the record corresponding to the session ID exists in the session management memory 3, and when it is determined that there is a record. In step S602, the record release service 22d releases the record corresponding to the session ID from the session management memory 3, and ends the process.

On the other hand, in step S601, the session I
When it is determined that the record corresponding to D does not exist in the session management memory 3, the record monitoring unit 23 determines in step S603 whether or not the record corresponding to the session ID exists in the database 6, and determines that there is no record. If so, the record release service 22d transmits error information to the server application 4 in step S605, and the process ends.

On the other hand, in step S603, the session I
When it is determined that the record corresponding to D exists in the database 6, the record monitoring unit 23 deletes the record corresponding to the session ID from the database 6 in step S604.

Hereinafter, the session management process 1 and COR
The relationship with BA will be described.

CORBA contains interface definition language IDL (Interface Definition).
(Language) is specified. The IDL describes the operations that can be used by the server. Here, an operation is a method, a method attribute, and a method parameter, and in FIG. 2, the record allocation service 22a and the record reading service 22 are shown.
b, the record writing service 22c, and the record releasing service 22d are operations.

When IDL is compiled by a CORBA-compliant IDL compiler, a stub for the client and a skeleton class for the server (hereinafter referred to as a skeleton) are generated.

Stubs are used by clients to invoke server operations via the ORB. The skeleton describes attributes and parameters of server operations. Implement this operation by inheriting this from the class.

FIG. 11 is a diagram showing a structure for generating a stub and a skeleton from the IDL definition.

As shown in the figure, the four operations (services) of the record control unit 22 in the session management process 1 shown in FIG. 2 are controlled by the IDL definition 20a defined by the interface of each operation to the IDL compiler 20b. By being compiled, each service stub 20c in the record control unit and each service skeleton 20d in the record control unit are generated.

FIG. 12 shows each service stub 20c in the record control unit and each service skeleton 20 in the record control unit generated by the IDL compilation shown in FIG.
It is a figure which shows the usage method of d.

In the figure, 11a is each service access API in the record control unit, which is the server application 4
To each service of the record control unit, and includes each service stub 20c in the record control unit generated by IDL compilation.

Reference numeral 11b is each service in the record control unit.
Each service skeleton 20d in the record control unit generated by IDL compilation is inherited, and each service in the record control unit is implemented.

As shown in the figure, the server application 4 uses each service access API 11 in the record control unit.
When a is called, each service 11b in the record control unit can be called via the ORB 30.

As described above, in the present embodiment, the session management between the client application 5 and the server application 4 that perform interactive processing in the distributed object environment is linked with the session management process 1 implemented as a distributed object resident in the server. The buffer controller 2 in the session management process 1 manages the session state information by the combination of the session management memory 3 and the session management table 61 in the database 6, and further, the buffer controller 2
Is a memory reservation unit 21 that internally reserves a memory, and a session management memory 3 that stores session state information.
It has a record control unit 22 for managing the records in it, a record monitoring unit 23 for inputting / outputting records among the session management memory 3 and the session management table 61. Further, the record control unit 22 has a distributed object service inside. As services of this distributed object, a record allocation service 22a for allocating records in the session management memory 3, a record reading service 22b for reading the records from the session management memory 3, and a record writing service for writing the records in the session management memory 3. 22c and a record release service 22d that releases the record in the session management memory 3. Each service is configured to be requested by the server application 4 in the distributed object environment. As a result, in the client / server system in the distributed object environment not limited to the WWW environment, the performance of the client / server system is deteriorated even if the session between the dialogues is stateless or stateful even if the communication between the client / server is stateless or stateful. You can manage without doing.

As described above, according to the present invention, the session state information is managed in the memory of the server resident process (process management memory 3 shown in the figure), which enables high-speed management.

Further, even when the predicted amount of status information to be managed exceeds, the excess is managed by the external storage device, so that the data loss can be prevented and the management can be safely performed.

Furthermore, the following two effects are exhibited.

First, the interactive processing server process operating machine (server device in which the server application 4 operates) and the status information management process machine (session management device in which the session management process 1 operates) are separated and the status information management process If the machine is a machine considering only this performance, it is possible to manage the state information at high speed without degrading the performance of the interactive server process operating machine. Furthermore, even if a cost-effective machine such as an inexpensive memory is selected as the state information management process machine, and it becomes a different model (different OS) from the interactive processing server process operating machine, CORBA can The linkage can be easily constructed.

Second, regardless of the type of state information management process machine, there is only one method of the interactive processing server process for accessing the state information management process machine.
That is, even if there is a change in the machine on which the status information management process operates, the interactive processing server process does not need to be changed at all, and a flexible session management environment can be provided.

The structure of a data processing program that can be read by a system to which the session management apparatus according to the present invention can be applied will be described below with reference to the memory map shown in FIG.

FIG. 13 is a diagram for explaining a memory map of a recording medium for storing various data processing programs readable by a system to which the session management device according to the present invention can be applied.

Although not particularly shown, information for managing the program group recorded on the recording medium, for example, version information, creator, etc. is also recorded, and information depending on the OS and the like on the program reading side, such as the program, is stored. In some cases, an icon or the like for identification and display is also recorded.

Further, the data dependent on various programs are also managed in the above directory. Also, if the program or data to be installed is compressed,
The decompressing program etc. may be recorded.

The functions shown in FIGS. 4 to 6, FIG. 7, FIG. 8, FIG. 9, and FIG. 10 in the present embodiment may be performed by the host computer by a program installed from the outside. And in that case, the CD-ROM
The present invention can be applied to a case where an information group including a program is supplied to an output device from a recording medium such as a flash memory or an FD, or from an external recording medium via a network.

As described above, the recording medium recording the program code of the software that realizes the functions of the above-described embodiments is supplied to the system or apparatus, and the computer (or CPU or MP of the system or apparatus is supplied.
It goes without saying that the object of the present invention can also be achieved by U) reading and executing the program code stored in the recording medium.

In this case, the program code itself read from the recording medium realizes the novel function of the present invention, and the recording medium recording the program code constitutes the present invention.

As a recording medium for supplying the program code, for example, a floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, C
D-ROM, CD-R, DVD-ROM, magnetic tape,
A non-volatile memory card, ROM, EEPROM, silicon disk or the like can be used.

Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also the OS (operating system) running on the computer based on the instruction of the program code. It goes without saying that this also includes the case where the above) performs a part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

Further, after the program code read from the recording medium is written in the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, based on the instruction of the program code, The CPU or the like provided in the function expansion board or function expansion unit performs a part or all of the actual processing,
It goes without saying that the processing includes the case where the functions of the above-described embodiments are realized.

The present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Further, it goes without saying that the present invention can be applied to the case where it is achieved by supplying a program to a system or an apparatus. In this case, by reading the recording medium storing the program represented by the software for achieving the present invention into the system or device, the system or device can enjoy the effects of the present invention. .

Furthermore, by downloading and reading a program represented by software for achieving the present invention from a database on a network using a communication program, the system or apparatus can be
It is possible to enjoy the effects of the present invention.

[0208]

As described above, the first aspect of the present invention
According to the inventions of 16 to 16, the session management between the client application performing the interactive processing in the distributed object environment and the server application implemented as the distributed object is performed by the session management process implemented as the distributed object. The controller in the session management process controls the session management memory that manages the session state information provided in the session management process in response to a request from the server application. The session state information that cannot be managed in the session management memory due to excessive session state information is provided outside the session management process from the record that was accessed the earliest. And controls to manage the database can be managed fast and safety performance without cause the deterioration of the session in interactive client / server system in a client / server system in a distributed object environment.

Also, the session management of the client / server system operating in the distributed object environment can be flexibly performed without depending on the platform.

[Brief description of drawings]

FIG. 1 is a block diagram showing an overall client / server system to which a client / server session management device operating in a distributed object environment according to an embodiment of the present invention can be applied.

FIG. 2 is a diagram showing a flow of session management of the client / server system shown in FIG.

FIG. 3 is a flowchart showing an example of a first control processing procedure in the embodiment of the present invention.

FIG. 4 is a flowchart showing an example of a second control processing procedure according to the embodiment of the present invention.

FIG. 5 is a flowchart showing an example of a second control processing procedure according to the embodiment of the present invention.

FIG. 6 is a flowchart showing an example of a second control processing procedure in the embodiment of the present invention.

FIG. 7 is a flowchart showing an example of a third control processing procedure according to the embodiment of the present invention.

FIG. 8 is a flowchart showing an example of a fourth control processing procedure according to the embodiment of the present invention.

FIG. 9 is a flowchart showing an example of a fifth control processing procedure according to the embodiment of the present invention.

FIG. 10 is a flowchart showing an example of a sixth control processing procedure according to the embodiment of the present invention.

FIG. 11 is a diagram showing a configuration for generating a stub and a skeleton from an IDL definition.

12 is a diagram showing a method of using each service stub in the record control unit and each service skeleton in the record control unit generated by the IDL compilation shown in FIG.

FIG. 13 is a diagram illustrating a memory map of a recording medium that stores various data processing programs that can be read by a system to which the session management device according to the present invention is applicable.

FIG. 14 is a diagram illustrating session states of both parties in communication between a client and a server.

FIG. 15 is a block diagram showing a client / server system in which both a client and a server are implemented as CORBA objects.

FIG. 16 is a block diagram showing a client / server system in which both a client and a server are implemented as CORBA objects in a WWW (World Wide Web) environment.

FIG. 17 is a block diagram showing an example of a client / server system in a form based on the problem of firewall construction in FIG.

[Explanation of symbols]

1 Session management process 2 buffer controller 3 Session management memory 4 server application 5 Client application 6 database 7 Property file 21 Memory securing unit 22 Record control unit 22a Record allocation service 22b Record reading service 22c Record writing service 22d Record release service 23 Record Monitor 30 ORB 31 network 61 Session management table 100 server device 200 client devices

Claims (16)

[Claims] 1. In a session management device that manages a session between a client application that performs interactive processing in a distributed object environment and a server application that is implemented as a distributed object, a session management process implemented as a distributed object, A session management apparatus, which manages a session between the client application and the server application in cooperation with a server application implemented as an object. 2. The session management process includes a session management memory that manages session state information in the process, and a controller that controls the session management memory, and the controller requires session management. The session management memory is controlled by a request from the server application, and the session status information that cannot be managed in the session management memory due to excessive session status information is transferred from the earliest accessed record to the outside of the session management process. The session management device according to claim 1, wherein the session management device is managed by a database provided. 3. The controller secures the session management memory and activates the session management memory at the time of starting the session management process, and a memory securing unit that connects to the database. The record control unit, writing out the session state information, which cannot be managed in the session management memory due to excessive session state information, from the record accessed the earliest to the database according to a request from the record control unit; 3. A record monitoring unit for returning session state information in the database required by the unit from the database to the session management memory in response to a request from the record control unit. session Management device. 4. The record control unit secures a record for storing session state information in the session management memory requested by the server application, and a session state from the record in the session management memory. A record reading service for acquiring information, a record writing service for storing the session state information in the record, and a record releasing service for releasing the record in which the session state information which is no longer required to be stored are released. The session management device according to claim 3, wherein 5. The session according to claim 4, wherein each service of the record control unit controls the session management memory based on a session ID provided from the server application that requires session management. Management device. 6. The session management according to claim 4, wherein an interface from the server application that requires session management of each service of the record control unit does not depend on an environment in which the session management process operates. apparatus. 7. The session management device according to claim 2, wherein all the information generated during the session is managed as the session state information. 8. A session management method for managing a session between a client application that performs interactive processing in a distributed object environment and a server application that is implemented as a distributed object, comprising: A session management method for managing a session between the client application and the server application in cooperation with a server application implemented as an object. 9. The session management process comprises a session management memory that manages session state information in the process, and a controller that controls the session management memory, and the controller requires session management. The session management memory is controlled by a request from the server application, and the session status information that cannot be managed in the session management memory due to excessive session status information is transferred from the earliest accessed record to the outside of the session management process. 9. The session management method according to claim 8, wherein the session management method is performed by a database provided. 10. The controller secures the session management memory and activates the session management memory in response to a request from the server application, which secures the session management memory and connects to the database when the session management process is started. The record control unit, writing out the session state information, which cannot be managed in the session management memory due to excessive session state information, from the record accessed the earliest to the database according to a request from the record control unit; 10. The record monitoring unit for returning the session state information in the database required by the unit from the database to the session management memory in response to a request from the record control unit. Session Management method. 11. The record control unit secures a record for storing session state information in the session management memory, which is requested by an application, and a record allocation service that stores session state information from the record in the session management memory. A record reading service for acquiring, a record writing service for storing the session state information in the record, and a record releasing service for releasing the record in which the session state information that is no longer required to be stored is released. 11. The session management method according to claim 10, which is characterized in that. 12. Each service of the record control unit,
12. The session management memory is controlled based on a session ID given by the server application that requires session management.
Session management method described. 13. The interface from the server application which requires session management of each service of the record control unit does not depend on an environment in which the session management process operates.
The session management method described in 1. 14. The session management method according to claim 9, wherein all the information generated during the session is managed as the session state information. 15. A program that realizes the session management method according to any one of claims 8 to 14. 16. A computer-readable recording medium having a program for executing the session management method according to claim 8 recorded therein.