JP2014021812A - Connection state management device and program of the same - Google Patents

Abstract

PROBLEM TO BE SOLVED: To manage the connection state of a client and a server such that mismatching can be prevented from being generated in the processing state of a user who operates a client or stored data by changing the connection state in a proper timing.SOLUTION: The connection state management device includes: a first connection state change processing execution section for, when a request for the change of a connection state is made, acquiring whether or not a function which is being used by a user is a function whose connection state is forcedly changeable from function information, and for, when the connection state is changeable, changing the connection state; and a second connection state change processing execution section for, when a request for the connection of the function of a server application is made from a client application, referring to the function which is being used by the user and the connection state of connection history information, and for, when the connection state is changeable, changing the connection state.

Description

  The present invention relates to a connection state management apparatus and a program thereof, and more particularly to a connection state management technique for managing a connection state by managing a connection state between a client application and a server application as session information in a client server type application. is there.

  In recent years, many client-server application execution models via computer networks have been adopted as computer application execution methods. In the client server type application execution model, application processing is performed in a distributed manner between client terminals and server devices. In general, in a client terminal application, an application processing request is input and an execution result display process is performed. The processing request input by the client terminal device is transmitted to the server device via the computer network, and the processing of the application function is executed in response to the processing request in the server device. The processing result in the server device is transmitted again to the client terminal via the computer network, and the processing result is displayed by the server device in the client terminal application.

  As a client-server type application execution model using such a network, for example, a mechanism such as a WEB (World Wide Web) application is known. In the WEB application, if the client terminal has a WEB browser as a client application, the client terminal is connected to the WEB server, which is a server device that performs processing as necessary, and the application processing is executed by the WEB server. It is possible to receive services of various applications provided by the WEB server without introducing any application other than the WEB browser on the side.

  Since the server application may be used by an unspecified number of client applications via the network, authentication processing is usually required in order to use the server application. In a client server type application that requires authentication processing, the server application accepts authentication processing from the client application, and manages the result of the authentication processing as a connection state. A client application that has been correctly authenticated is managed as being connected to the server application, and the server application can be used. If authentication processing is not performed, the client application and the server application are managed if they are not connected, and the server application cannot be used.

  In order to hold the client application state such as the connection state on the server application side, a technique for managing the client application state on the server application side using an identifier called a session is widely used. A session is information for managing client connection information held by a server. For example, in a WEB application, when a client connects to a server, a unique session identifier is assigned to each connected client on the server side, and session information is created on the server side corresponding to the session identifier. In the session information, information for managing the status of “connection, communication, disconnection” between the client and the server is recorded. Specifically, the session information was entered by the client application time, client connection time, client disconnection time from the server, server application processing results, and client application. Various information such as “information” is stored.

  The session identifier created on the server side is sent to the client application. The client application sends this session identifier to the server together with the processing request each time the server requests processing. Since the server stores session information in association with the session identifier, the previous connection information of the client application can be acquired from the session information based on the session identifier.

  In general, the session information is managed by the server by such a mechanism, and the connection state described above is generally managed by the session. Session information is stored on the server side, so if you continue to store it without deleting it, it may lead to compression on the server's disk capacity or a decrease in processing capacity due to an increase in the amount of data. Therefore, normally, session information is not stored indefinitely. If there is no connection from a client application for a certain period of time, session timeout processing occurs on the server side, and processing for deleting session information is performed. .

  However, if the processing is interrupted for a certain period of time even though the client is connected, the processing that has been performed on the server side in response to the request from the client is interrupted by the session timeout processing. It will be done. In such a case, the data being processed is suddenly lost, and there is a risk that the processing performed on the server side will be inconsistent and the consistency of the stored server data may be inconsistent.

  In this way, in order to prevent session inconsistencies and data inconsistencies from occurring due to session time-out processing during processing on the client side, the client operation status is changed. In response, a technique is known in which a dummy request is sent to the server to automatically extend the session timeout time.

JP 2008-026945 A

  In the prior art, it is possible to prevent session information from being discarded by not generating session timeout processing. However, when performing maintenance on the server device, the server must be stopped or restarted even if there is a client connected to the server. In such a case, it is necessary to refer to the session information held on the server side, and to stop or restart the server if there is a connected client.

  For example, in a WEB application, session information is created when a user using a client performs login processing to the server application, and session information is discarded by performing logout processing. The connection state is recorded in the session information. Therefore, if the session information can be referred to, if there is a connected user, the server is not stopped or restarted, and all users log out and wait for the connection to stop and stop or restart the server. You can make it start.

  However, since it is uncertain when the user performs logout processing, if the user does not perform logout processing for a long time, the server cannot be stopped or restarted after any time. Therefore, it is possible to forcibly execute the user logout process, discard the session information, or change the connection status, but the user suddenly interrupts the process while performing the operation. There is a bug that is done. Furthermore, there is a possibility that the processing that has been performed so far may be inconsistent or data inconsistency may occur due to the processing being interrupted in the middle.

  The present invention has made it possible to solve the above-mentioned problems. The connection state between the client and the server is changed at an appropriate timing, and there is no inconsistency in the processing state of the user who operates the client and the retained data. It is possible to manage the connection state so that it does not occur.

  In order to solve the above-described problem, the connection state management device according to the present invention includes a usage history information storage unit that stores, as usage history information, a function of a server application requested to be connected by a client application, and connection of the client application to the server application. A connection history information storage unit that stores the status as connection history information, an application information storage unit that stores function information indicating whether the connection status can be forcibly changed while using the function of the server application, When the connection status change processing accepting unit that accepts a change request and the connection status change request are accepted, the connection status to be changed is determined from the usage history information, connection history information, and function information, and recorded in the connection history information A first connection status change processing execution unit that performs the client and the client When a connection request is made to the function of the server application from an application, a usage status acquisition unit that records the requested function as the usage history information, and when usage history information is recorded in the usage status acquisition unit In addition, it is determined whether or not to change the connection status from the usage history information, connection history information, and function information, and if so, a second connection status change process is executed to record the changed connection status in the connection history information. It consists of parts.

The outline of this connection state management apparatus is as follows.
(1) The usage history information storage unit stores the function of the server application requested for connection from the client application as usage history information. The usage history information records which function running on the server application is being used from the client application for each user who uses the client application. The user is specified by the user ID or the session ID, and the function being used is specified by the function ID.

  (2) The connection history information storage unit stores the connection status of the client application to the server application as login history information. The connection history information is a record of the connection status between the client application and the server application for each user who uses the client application. The connection status includes connection status such as “online”, “forced logout”, and “logout”. "Online" means that the client application is using the server application, and "forced logout" means that the client application is using the server application but is waiting for logout processing (disconnection processing). “Logout” indicates that the client application is not using the server application, that is, is disconnected.

  (3) The application information recording unit stores function information indicating whether the function of the server application can forcibly change the connection status. The function information that indicates whether the connection status can be forcibly changed is information that specifies whether the connection status of the user who is using each function can be changed for each function of the server application. is there.

  (4) The connection status change process accepting unit accepts a connection status change request. That is, a user who is using the server application is specified by specifying a user ID and a session ID, and a request for changing the connection status of the specified user is accepted. For example, the user may be specified by specifying a function ID and acquiring a user who uses the specified function ID from the usage history information.

  (5) When the connection status change processing accepting unit receives the connection status change processing request, the first connection status change processing execution unit determines the connection status to be changed from the usage history information and function information, and the connection Processing to record in history information is performed. Specifically, the first connection status change processing execution unit acquires what the function of the server application that the client application is using from the usage history information, and the function being used forcibly changes the connection status. Acquire from the function information whether the function is possible. For example, if it is a function that can forcibly change the connection status, the connection status in the connection history information is recorded as “logout”, and if it is not a function that can forcibly change the connection status, the connection history information connection Record the situation as "forced logout".

  (6) When there is a connection request from the client application to the function of the server application, the usage status acquisition unit records the requested function in the usage history information. As a result, the function of the server application being used by the client application is recorded in the usage history information.

  (7) The second connection status change processing execution unit determines whether to change the connection status from the usage history information, the connection history information, and the function information when the usage history information is recorded in the usage status acquisition unit. When changing the connection status, record the changed connection status in the connection history information. For example, the second connection status change processing execution unit refers to the connection status of the connection history information when a connection request is made from the client application to the function of the server application and the usage history information is recorded in the usage status acquisition unit. If it is in the "forced logout" status, the function that can be used to acquire the server application function being used by the client application from the usage history information and forcibly change the connection status. If it is a function that can be obtained from the function information and forcibly change the connection status, the connection status in the connection history information is recorded as “logout”.

  Also, in one aspect of the present invention, the usage status acquisition unit determines whether a connection request can be processed from the connection history information when a connection request is made from the client application to the function of the server application. , Has a function of suppressing processing of a function requested to be connected. For example, the usage status acquisition unit acquires the connection status in the connection history information when a connection request is received from the client application to the function of the server application. If the connection status is “logout”, the connection request is By not performing the processing of the function, the use of the server application can be suppressed when the connection state between the client application and the server application is not connected.

  Furthermore, as another configuration of the connection status management device according to the present invention, the configuration of the connection status management device further includes a connection status providing unit that transmits the use connection history information to the client application, and the connection status change processing acceptance The unit may be a connection state management device having a function of simultaneously accepting a plurality of connection status change requests. That is, the connection status providing unit transmits the connection history information recorded in the connection history information storage unit to the client application. As a result, the user of the client application can know the connection status of the user who is currently using the server application. The connection status change processing accepting unit simultaneously accepts a plurality of connection status change requests, so that the user of the client application can change the connection status of a plurality of users who are currently using the server application in a batch. can do.

  According to the present invention, even when a connection status change request is made, the connection status management device does not immediately change the connection status but is currently using the user who has requested the connection status change. Since the connection status is changed only when the server application function is a function that does not cause a problem even if the connection status is changed, the connection is made in the middle of the process even though the user is using the server application function. It is possible to avoid a situation in which the situation has changed and processing cannot be continued. Furthermore, even when the user's connection status is desired to be changed, but the function being used is a function that is not permitted to change the connection status, the process of using the user's server application function is completed. If there is no problem even if the connection status is changed, the connection status can be changed automatically, so problems occur according to the user's processing status without interrupting the user's processing. It becomes possible to change a user's connection condition safely when it becomes the situation which does not carry out.

1 is an overall configuration diagram of a system in which a connection status management apparatus is used. It is a process flowchart showing the conventional session information management. It is a process flowchart showing the management method of the conventional connection state. It is an example of the screen which instruct | indicates the login status change. It is a process flowchart which instruct | indicates a connection status change. It is a process flowchart which performs the process of a connection status change. It is a process flowchart which performs the process of a connection status change. It is a figure which shows the example of login log information. It is a figure which shows the example of usage history information. It is a figure which shows the example of application information. It is a figure which shows the example of session management information.

  Hereinafter, embodiments of the connection status management device and the program disclosed in the present application will be described in detail with reference to the drawings. In the following embodiment, in the client server type application execution method, the connection between the client application and the server application is established by the login process from the user who operates the client application and uses the function of the server application. When the system administrator who manages the server application other than the user forcibly executes the forced logout process to disconnect the connection between the client application and the server application when the connection is disconnected by the logout process from the user An example will be described. However, the connection status management device and the embodiment of the program disclosed in the present application are not limited to those described below, and are similarly applied to various devices that manage the connection status between the client application and the server application. Is possible.

  First, an overview of the overall configuration of the connection status management apparatus according to the present embodiment will be described. FIG. 1 is a diagram illustrating an overall configuration of a connection status management apparatus according to the present embodiment. The connection status management apparatus 1 manages the connection status between the client application 2 and the server application 3 by being controlled by the server application 3. The connection status management apparatus 1 includes an application information storage unit 110, a connection history information storage unit 120, a usage history information storage unit 130, a connection status change process reception unit 101, a usage status acquisition unit 102, and a connection status change process execution unit 103. , The connection status providing unit 104.

  First, each storage unit included in the connection status management apparatus 1 will be described.

  The application information storage unit 110 stores application information indicating whether the function of the server application 3 and the connection status of a user who is using the function can be forcibly changed. FIG. 10 is a diagram illustrating an example of application information in the present embodiment. As shown in FIG. 10, the application information storage unit 110 includes information on “function screen ID”, “function screen name”, and “connection status change permission / inhibition”. “Function screen ID” is an identifier for uniquely identifying a function of the server application 3, and “Function screen name” is a name of a function assigned in correspondence with “Function screen ID”. “Connection status change permission / rejection” stores whether or not the connection status of the user who is using the function of the function screen ID can be forcibly changed.

  For example, if "Function screen ID" is stored as "Top010", "Function screen name" is stored as "Top screen", and "Connection status change possibility" is stored as "Possible", the identifier of the function screen name "Top screen" Is “Top010”, which means that the connection status of the user who is using the top screen can be forcibly changed. “Function screen ID” is “JyuEntry002”, “Function screen name” is “Order entry screen”, When "Not available" is stored for "Connection status change possibility", the identifier of the function screen name "Order entry screen" is "JyuEntry002", and the connection status of the user who is using the order entry screen is forced It means that it cannot be changed.

  The connection history information storage unit 120 stores the connection status between the client application 2 and the server application 3 operated by the user. FIG. 8 is a diagram showing an example of connection history information in the present embodiment. As shown in FIG. 8, the connection history information includes information of “user ID”, “user name”, “company name”, “connection source IP address”, “login date / time”, and “connection status”. “User ID” is an identifier that uniquely identifies a user who operates the client application 2 and uses the function of the server application 3. “User name” is a usage that is assigned in correspondence with the “user ID”. "Company name" is the name of the company to which the user belongs. The “connection source IP address” represents an IP address set in the client application 2 operated by the user. “Connection status” represents the connection status between the client application 2 and the server application 3 operated by the user.

  For example, “User ID” is “User0001”, “User Name” is “Test User 1”, “Company Name” is “Test Corporation”, “Connection IP Address” is “192.168.10.5”, “Login If "Date and time" is stored as "2012/04/07 18:21:31" and "Connection status" is stored as "Online", the user ID is "User0001", the user name is "Test user 1", the company The IP address set in the client application 2 operated by the user of the name “Test Corporation” is “192.168.10.5”, and the user is assigned to the server application “2012/04/07 18:21:31” The login process is performed, and the connection status between the client application 2 and the server application 3 operated by the current user is “online”.

  The “connection status” stores statuses such as “online”, “forced logout”, and “logout”. “Online” indicates that the login process from the client application 2 to the server application 3 is executed and is in a connected state, that is, it is in use. “Forced logout” indicates that the client application 2 and the server application 3 are connected. In other words, it indicates that it is in use but is waiting for logout processing (disconnection processing), and “logout” indicates that the client application 2 is not using the server application 3, that is, is disconnecting. .

  The usage history information storage unit 130 stores which function of the server application 3 is being used by the user. FIG. 9 is a diagram showing an example of usage history information in the present embodiment. As illustrated in FIG. 9, the usage history information storage unit 130 includes information on “user ID”, “user name”, “function screen ID”, “function screen name”, and “processing time”. “User ID” is an identifier that uniquely identifies a user who operates the client application 2 and uses the function of the server application 3. “User name” is a usage that is assigned in correspondence with the “user ID”. The name of the person. The “functional screen ID” is a “functional screen ID” that is an identifier for the user corresponding to the “user ID” to identify the function of the server application 3 that is currently operating by operating the client application 2. “Function screen name” is the name of the function screen corresponding to “Function screen ID”. “Processing time” represents the processing start time when the user started using the function.

  For example, “User ID” is “User0001”, “User name” is “Test user 1”, “Function screen ID” is “JyuEntry002”, “Function screen name” is “Order entry screen”, “Processing time” Is stored as “2012/04/07 19:30:43”, the user ID “User0001” and the user name “test user 1” function with the function screen ID “JyuEntry002”. This indicates that the function of the server application 3 whose screen name is “order input screen” is being used from the processing time “2012/04/07 19:30:43”. Usage history information is created for each user ID, and when the function used by the user is changed, the “functional screen ID” and “functional screen name” are rewritten to the functional screen ID and functional screen name being used by the user. The time when the use of the function is started is recorded in the “processing time”.

  Next, each processing unit included in the connection status management apparatus 1 will be described.

  The connection status change process accepting unit 101 accepts a connection status change request from the server application 3. Specifically, when the user operates the client application 2 to execute the login process function of the server application 3 and the login process is successful, the server application 3 sends a connection status to the connection status change process reception unit 101. Request to change to “online”. Similarly, when the user operates the client application 2 to execute the logout process function of the server application 3 and the logout process is successful, the server application 3 notifies the connection status change process reception unit 101 of the connection status by “logout”. Request to change to "". Although the user can only change the connection status of the user himself, the system administrator operates the client application 2 to execute the forced logout processing function of the server application to change the connection status of any user. It is also possible to make a request to the connection status change process reception unit 101. In this case, the system administrator inputs a list of user IDs whose connection status is changed to “logout” from the client application 2 and transmits it to the server application 3. The server application 3 transmits a request for changing the connection status of the received user ID to “logout” to the connection status change process reception unit 101.

  When the connection status change process accepting unit 101 accepts the connection status change request, the connection status change process accepting unit 101 transmits the accepted change process request to the connection status change process executing unit 103. When the connection status change processing execution unit 103 receives the connection status change request from the connection status change processing reception unit 101, the connection status change processing execution unit 103 identifies the user ID for changing the connection status from the change request and stores it in the connection history information storage unit 120. The connection status of the connection history information of the user ID is changed. For example, in the case of a request to change the connection status to “online”, the connection history information stored in the connection history information storage unit 120 is acquired from the connection status change request as the connection history information of the user ID. Record "User ID", "User name", "Company name", "Source IP address", etc., record the connection status as "Online", and change the connection status to "Online". Record as. Here, even when a request to change the connection status to “online” is received, for example, when the server application 3 is in the maintenance mode, or when the server application 3 is set in a state where the server application 3 cannot be used. Can also prevent the connection status from changing to "online". As a result, even if the login process is successful, the use of the server application 3 can be suppressed by not changing the connection status to “online” depending on the state of the server application.

  Next, for example, in the case of a request to change the connection status to “logout”, the connection status change processing execution unit 103 refers to the usage history information corresponding to the user ID from the usage history information storage unit 130, and The function screen ID being used by the user is acquired. And the application information corresponding to the said function screen ID is acquired from the application information storage part 110, and the information of the connection status changeability of the said function screen ID is acquired. When the acquired connection status changeability is “possible”, the connection status of the connection history information of the user ID stored in the connection history information storage unit 120 is recorded as “offline”. If the acquired connection status change permission / inhibition is “impossible”, the connection status of the connection history information of the user ID stored in the connection history information storage unit 120 is recorded as “forced logout”.

  When the user operates the client application 2 to make a usage request for the function of the server application 3, the usage status acquisition unit 102 identifies the user who operates the client application 2 according to the request from the server application 3. Information such as the ID and the function screen ID of the server application 3 that requested the use, and the processing time of the request is stored in the use history information storage unit 130. Since the usage history information is created as unique information for each user ID, the usage history information corresponding to the corresponding user ID is updated every time there is a function processing request from the client application 2 to the server application 3. It becomes. Further, when the user operates the client application 2 to request the use of the function of the server application 3, the usage status acquisition unit 102 connects the connection history information corresponding to the user ID that made the request. The connection status of the user ID is confirmed by referring to the history information storage unit 120. Here, when the confirmed connection status is a status for changing the connection status of the user, for example, when the connection status is “forced logout”, the usage status acquisition unit 102 performs the connection status change process. The execution unit 103 is requested to change the connection status of the connection history information storage unit 120 corresponding to the user ID to “logout”.

  Thereafter, the usage status acquisition unit 102 notifies the server application 3 of the usage status. If the connection status is changed when a connection status change request is made to the connection status change processing execution unit 103, the connection status after the change is notified. The server application 3 notified of the connection status determines what processing is to be performed in response to the function use request from the client application 2 in accordance with the notified connection status. For example, when the connection status is “online” or “forced logout”, the server application 3 processes the function requested to be used by the client application 2 and returns the processing result to the client application 2. If the connection status is “logout”, the client application 2 is not authenticated, and the server application 3 and the client application 2 are not connected. In response to a function usage request from the client application 2, a process for prompting authentication, such as returning the authentication request function screen without performing the requested function processing, or returning a message screen indicating that the function cannot be executed, etc. Process.

  Upon receiving a connection status acquisition request from the server application 3, the connection status providing unit 104 acquires a list of connection history information from the connection history information storage unit 120 and returns it to the server application 3.

  Next, a specific processing flow of how the connection status management apparatus manages the connection status will be described using a flowchart.

  In the connection status management apparatus 1, session management information is used to identify the user ID of the user who is operating the client application 2. The session management information is generated when a request for processing is first made from the client application 2 to the server application 3, and the session ID is notified from the server application 3 to the client application 2.

  FIG. 2 is a process flowchart for generating general session management information. The server application 3 receives a request request from the client application 2 as a processing request for the function of the server application 3 (S201). When the session ID is not transmitted from the client application 2, the server application 3 generates a unique session ID that is unique for each client application (S202). When the session ID is generated, session management information corresponding to the session ID is generated (S203). The session management information is, for example, information as shown in FIG. 11. For example, “user ID”, “user name”, and the like are recorded so as to correspond to the session ID. The generated session ID is notified to the client application 2, and thereafter, the client application 2 transmits the session ID together with the processing request when making a processing request to the server application 3. By adopting such a configuration, the server application 3 can manage and use unique information for each user who uses the client application 2 from the session management information based on the session ID transmitted from the client application 2. it can.

  For example, when the function of the server application 3 that performs the authentication processing function is used from the client application 2, the processing of the authentication processing function is performed when information necessary for the authentication processing including the user ID is transmitted from the client application 2 to the server application 3. As shown in FIG. 11, the user ID is recorded as session management information in a form corresponding to the session ID.

  FIG. 3 is a processing flow when connection state management is performed using general session management information. By managing the connection status using session management information, if the authentication process is being performed, it is regarded as the connection state, and the function of the server application 3 requested by the client application 2 is processed and authenticated. When the processing is not performed, it is assumed that the client application 2 is not in a connected state, and control is performed to suppress processing of the function of the server application 3 that has been requested by the client application 2.

  How such control is performed will be described according to the processing flow of FIG. First, when the server application 3 receives a processing request from the client application 2, the server application 3 acquires a session ID from the processing request (S301). Then, the user ID corresponding to the session ID is acquired from the session management information (S302). Next, what is the connection status of the acquired user ID is acquired (S303). For example, if the connection status of a user is recorded as connection history information as shown in FIG. 8, information such as “online” and “logout” can be acquired as the connection status from the acquired user ID. . If the connection status can be acquired, it is determined from the connection status whether the user is in a login state (S304). For example, if the connection status is “online”, the client application 2 determines that the server application 3 is logged in (S304, YES), and the server application 3 processes the function requested by the client application 2. Is executed, and the function screen of the execution result is transmitted to the client application 2 and displayed (S306). When the connection status is “offline”, the client application 2 determines that the server application 3 is not logged in (S304, NO), and the server application 3 performs processing of the function requested by the client application 2. For example, the function of the server application 3 is prevented from being processed by performing a process forcibly transitioning to the authentication processing function screen without executing the process (S305).

  The embodiment that manages the connection status using the session management information that is generally performed has been described above with reference to FIGS. 2 and 3. In the connection status management apparatus according to the present invention, the connection status is managed by the administrator by specifying the connection history information, usage history information, etc. of the user by using the session management information, and the connection status at an appropriate timing. The change process is realized. Next, the processing flow for changing the connection status in the present invention will be described.

  FIG. 5 is a flowchart of the entire process of the forced logout process flow in the connection status management apparatus 1. The instruction to perform the forced logout process is given by, for example, a system administrator who is responsible for starting and stopping the server application, monitoring the usage status, and the like. The system administrator operates the client application 2 to request the server application 3 to display a list of users having authority to use the server application 3. Then, the server application 3 inquires the connection status providing unit 104 about the list of connection statuses of the users, and the connection status providing unit 104 refers to the connection history information storage unit 120 and acquires the connection status for each user. The acquired connection status for each user is returned to the server application 3, and the server application 3 shows the connection status for each user based on the returned connection status information for each user as shown in FIG. 2 and the client application 2 displays a connection status information display screen (S501). On the connection status information display screen, the users whose connection status is to be displayed can be narrowed down by “company name”, “user name” or the like.

  The system administrator refers to the information on the connection status information display screen, and selects a user ID to be subjected to the forced logout process from the list based on information such as “user ID”, “login date”, and “connection status” (S502). Then, an instruction to execute the forced logout process is given to the connection status management apparatus 1 via the server application 3 by, for example, pressing a forced disconnection button (S503).

  FIG. 6 is a processing flow of forced logout performed in the connection status management apparatus 1 after receiving a list of user IDs to be subjected to forced logout processing. When the server application 3 receives the list of user IDs to be subjected to the forced logout process from the client application 2, the server application 3 transmits the target user ID list to the connection status change process accepting unit 101, and displays the connection status of the transmitted user ID. Request to change to logout. The connection status change process accepting unit 101 transmits the received user ID list to the connection status change process execution unit 103, and requests execution of a process for changing the connection status to logout. The connection status change processing execution unit 103 changes the connection status information corresponding to the user ID stored in the connection history information storage unit 120 to “forced logout” for each user ID of the received user ID. Is executed (S601). Here, when the connection status is “logout”, the logout process has already been completed, and thus the process of changing the connection status information to “forced logout” is not performed.

  Next, the connection status change process accepting unit 101 repeatedly performs the process for each user ID until the process for all user IDs is performed on the received user ID list (S602). First, the function ID corresponding to the user ID is acquired by referring to the use history information storage unit 130 to determine what function is being used by the user ID to be processed (S603). Then, whether or not the function with the acquired function ID is a function that can be forcibly logged out is confirmed by referring to the application information storage unit 110 and acquiring information on whether or not the connection status can be changed corresponding to the function ID (S604). . When the acquired connection status change permission / inhibition is “possible” (S604, YES), the connection status information corresponding to the user ID stored in the connection history information storage unit 120 is changed to “logout”. If the acquired connection status change permission / inhibition is “impossible” (NO in S604), the connection status information corresponding to the user ID stored in the connection history information storage unit 120 is not changed and “forced logout” is performed. Will remain. When the process for one user ID is completed and all the target user IDs have been processed (S606, YES), the forced logout process is completed. If all the processing of the target user ID is not completed (S606, NO), the process returns to S602 and the next user ID is processed.

  With the above processing flow, the connection status of the user ID that has received the request to change the connection status to logout is changed to “forced logout” or “logout”. Next, processing for changing the connection status in the “forced logout” state to “logout” will be described. The forced logout status management process that determines whether or not to change the connection status to “logout” when the connection status is “forced logout” is the conventional general process described above using the processing flow of FIG. This is realized by incorporating a connection status change determination into the process for managing the connection status using session management information.

  That is, when the user makes a function use request from the client application 2 to the server application 3, the connection status is managed by using the session management information, so that the connection status is displayed when the authentication process is performed. It is assumed that the server application 3 that has received a processing request from the client application 2 performs processing of the function of the server application 3 that has received a processing request from the client application 2, and assumes that the client application 2 has not been connected. Control is performed to suppress the processing of this function, which is realized by incorporating a connection state change determination into this processing.

  How such control is performed will be described according to the processing flow of FIG. First, when the server application 3 receives a processing request from the client application 2, the server application 3 acquires a session ID from the processing request (S701). Then, the user ID corresponding to the session ID is acquired from the session management information (S702). Next, what the connection status of the acquired user ID is is acquired (S703). For example, if the connection status of the user is recorded as connection history information as shown in FIG. 8, information such as “online”, “forced logout”, “logout”, etc. is obtained as the connection status from the acquired user ID. Can be acquired. If the connection status can be acquired, it is determined from the connection status whether the user is in the login state (S704). For example, if the connection status is “online” or “forced logout”, the client application 2 determines that it is logged in to the server application 3 (S704, YES), and if the connection status is “offline”, The client application 2 determines that the server application 3 is not logged in (S704, NO).

  If it is determined that the login state is not established based on the connection status (NO in S704), the server application 3 does not execute the function requested by the client application 2 but forcibly displays the authentication processing function screen, for example. The function of the server application 3 is prevented from being processed by performing a process of transitioning automatically (S710).

  If it is determined from the connection status that the user is in the login state (S704, YES), it is determined whether or not to change the connection status, and whether or not the requested function is to be processed is determined. Before making these decisions, information such as “user ID”, requested “use function”, and “access time” is used as use history information in order to manage which function the user is using. It records in the usage history information storage unit 130 (S705). With this process, it is possible to always manage which function the user has in the server application 3.

  Next, it is confirmed by referring to the connection status corresponding to the user ID stored in the connection history information storage unit 120 whether or not the connection status of the user is the “forced logout” status. If the connection status is not "forced logout", it is not necessary to change the connection status to "logout" (NO in S706), so the server application 3 executes the processing for the function requested by the client application 2. Then, the function result screen is transmitted to the client application 2 and displayed (S709).

  When the connection status is “forced logout” (S706, YES), it is determined whether or not to change the connection status to “logout”. Specifically, by referring to the function screen ID corresponding to the user ID stored in the connection history information storage unit 120, which function the user is currently using is acquired. Then, in order to confirm whether the function being used is a function that can be forcibly logged out, it is used by referring to the connection status changeability corresponding to the function screen ID recorded in the application information storage unit 110. Judge whether the function inside can change the connection status. If it is determined that the change of the referenced connection information is “impossible” (NO in S707), the server application 3 executes the function requested by the client application 2 without changing the connection status, The execution result function screen is transmitted to the client application 2 and displayed (S709).

  When it is determined that the referred connection information can be changed (YES in S707), the connection status information corresponding to the user ID stored in the connection history information storage unit 120 is changed to "logout" ( S708). In this case, the server application 3 does not execute the function requested by the client application 2 but performs, for example, a process of forcibly transitioning to the authentication processing function screen, so that the server application 3 functions. The processing is suppressed (S710).

  The connection status of the user is managed by performing the processing as described above on the connection status management apparatus 1. With this process, even if the administrator requests a forced logout process, the connection status is not changed immediately, but the connection is made at an appropriate timing according to the user's usage status. You can change the status to logout. As a result, it is possible to prevent the information input by the user and the business information from being lost. In addition, because users can select a user who requires forced logout processing and instruct the forced logout processing, only users who need to log out can be forcibly logged out, and the administrator can grasp the login status of the user. Therefore, it is possible to know the appropriate maintenance timing.

  Further, the connection status management device can be realized by a computer and a software program, and the program can be recorded on a computer-readable recording medium or provided through a network. Each component of each device shown in the figure is functionally conceptual and does not necessarily need to be physically configured as shown. In other words, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in an arbitrary unit depending on the processing unit or usage status. Can be configured. Further, all or a part of each processing function performed in each device can be realized by a CPU and a program analyzed and executed by the CPU, or can be realized as hardware by wired logic.

DESCRIPTION OF SYMBOLS 1 Connection status management apparatus 2 Client application 3 Client application 101 Connection status change process reception part 102 Usage status acquisition part 103 Connection status change process execution part 104 Connection status provision part 110 Application information storage part 120 Connection history information storage part 130 Usage history information Memory

Claims (4)

A usage history information storage unit that stores, as usage history information, the function of the server application requested for connection by the client application;
A connection history information storage unit for storing the connection status of the client application to the server application as connection history information;
An application information storage unit for storing function information as to whether or not the connection status can be forcibly changed while using the function of the server application;
A connection status change process reception unit for receiving the connection status change request;
A first connection status change processing execution unit for determining a connection status to be changed from the usage history information and function information and recording the connection status information when receiving the connection status change request;
A usage status acquisition unit that records the requested function as the usage history information when there is a connection request from the client application to the function of the server application;
When the usage history information is recorded in the usage status acquisition unit, it is determined whether or not to change the connection status from the usage history information, connection history information, and function information. A connection status management apparatus comprising a second connection status change process execution unit for recording in connection history information. 2. The connection status management apparatus according to claim 1, wherein the usage status acquisition unit determines whether a connection request can be processed from the connection history information when a connection request is made from the client application to the function of the server application. And a connection status management apparatus having a function of suppressing processing of a function requested to be connected. The connection status management apparatus according to claim 1 or 2, further comprising a connection status information providing unit that transmits the connection history information to the client application.
The connection status processing accepting unit has a function of simultaneously accepting a plurality of connection status change requests. The connection condition management program for functioning a computer as each process part with which the connection condition management apparatus of any one of Claim 1 to 3 is provided.