JP2007011645A - Module update program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a client-server system for eliminating replacement operation by a maintenance personnel for updating a module. <P>SOLUTION: A module update program connecting a server 100 to a network and managing a module to be operated on a client terminal 200, includes a storage module list 207 to store module information acquired by the client terminal 200 together with different versions of the module, a user module list 208 to store modules applied for each user, and an automatic update processing unit 202 having to obtain a module to be applied when it is determined that the update is needed in accordance with a version setting file obtained at starting of the use of a business service; and as an update proxy processing unit 203 operating with a manager right for the client terminal 200, managing back up of an obtained module, and copying the module information of the specified version from the storage module list 207 to the user module list 208. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a module update method when a module is updated in a client server system.

  In the system construction work, after an operation test is performed in a test environment for a module that has been corrected or created by handling a system failure or adding a function provided to a customer, the operation test is performed again in an operation environment.

  In the verification work in the operation environment, the schedule is adjusted with the customer (system user), and the module replacement work is performed. Usually, this work is often performed at midnight after the end of business hours or on a holiday when the customer does not use the system.

  However, it is actually the next working day that the customer verifies the function of the new module that has been replaced, and the failure is normally handled only after the customer uses it, or the requested function is normal. Confirmation that it has been added is performed. By receiving this confirmation, the verification work of the module updated in response to the failure of the program module or the function addition is completed.

  After the verification in the customer's system environment is completed, the updated modules are replaced for all client terminals scattered in each department of the customer. After the above operations are completed, the updated system is operated. Will be started.

This replacement work increases the number of clients to be replaced in accordance with the scale of the operating environment, so the larger the operating environment scale, the longer the time and labor required for the replacement work, resulting in human error in the workforce. The possibility increases.
Therefore, as the scale of the operating environment increases, the risk of inconsistencies in the entire system after the update increases.

  In addition, if the scale of the operating environment is large, the impact on customer operations due to inconsistencies in the entire system after the update also increases. It also leads to a greater degree of losing.

Therefore, in a system composed of a plurality of terminals and servers, there is Patent Document 1 as a technique for unifying the versions of modules installed in each terminal throughout the system. Japanese Patent Application Laid-Open No. 2004-228561 discloses a technique for improving the efficiency of client software installation work and version upgrade work by automatically performing client machine program installation processing and version upgrade processing by a server on a network. .
JP-A-10-31590

  In Patent Document 1, modules applied to all clients are stored in a server on the network, and information on all clients on the network is centrally managed. The client information managed by the server includes the version of the module applied to each client and the module storage location. And in the method of patent document 1, a module is applied with respect to the some client utilized by a system by the process of the server based on an instruction | indication of an administrator.

  Since the module application process is performed based on information managed centrally by the server process, there is a problem that the load on the server increases according to the number of clients. In order to cope with this problem, a server having a performance capable of withstanding the load has been introduced, or the number of clients to which the module is applied is limited in the server processing within a certain period of time. It has been done to smooth the load. In the former case, as the scale of the system increases, the equipment cost for the maintenance work of the system also increases, which is not economically efficient. In the latter case, since maintenance work is performed in a divided manner, as the scale of the system increases, more time is required to ensure the consistency of the entire system, which adversely affects customer operations that use the system. Arise.

  As a method for solving the above problem, there is a method in which a module used by a client is downloaded and dynamically applied prior to the start of use of the system. In this method, it is possible to always maintain the module used in the client at the latest version, and to distribute the load on the server.

  However, in the method of applying dynamically prior to the start of system use, in order to ensure the security of resources on the client, there are restrictions on the functions that can be realized by the module to be applied, or they can be applied dynamically. There are restrictions on user rights. Therefore, when applying a module that does not limit the functions that can be realized, it is necessary to prepare for use of the system by a user who has been given specific authority. However, general users in normal system operation are not given the authority to execute dynamic application. Therefore, even if the method is applied dynamically prior to the start of use of the system, replacement work by maintenance personnel having specific authority is required for each client. The number of man-hours for replacement work by maintenance personnel is enormous, including when returning to the test environment after verification fails in the operating environment, or when comparing the operation in the operating environment with the operation in the test environment. Become.

  Therefore, an object of the present invention is to provide a client server system that eliminates the need for replacement work by maintenance personnel when updating a module.

  The present invention relates to a computer system that provides a business service, a version setting file storage unit that stores a version setting file that describes an identifier and version information of a program module to be applied to the business service, and an application that stores the module A module file storage unit, a storage module file storage unit that stores the modules stored in the application module file storage unit, a user identifier reception unit that receives input of a user identifier, an identifier of the module, version information, and A storage module list storage unit that stores storage locations on the storage module file storage unit, and a user module that is defined for each user identifier and stores the identifier of the module and the storage location on the storage module file storage unit List If the module identifier and version information set in the version setting file are not in the storage module list storage unit, the module is acquired from the application module file storage unit and stored in the storage module file storage unit An automatic update processing unit that requests an update of information related to the module, and the acquired module is stored in the storage module file storage unit based on a request from the automatic update processing unit, and the acquired module identifier, version The information and the storage location on the storage module file storage unit are registered in the storage module list storage unit, and the identifier of the module and the storage location on the storage module file storage unit are obtained from the storage module list storage unit, and User module list storage And updating proxy processing unit registered, characterized by comprising the.

  Further, the present invention is a module update program that stores a program module to be applied to a client terminal and uses the client terminal connected to a server that notifies the client terminal of an identifier and version information of the module. An identifier of the module, and a version of the module identifier and version information in an area that can be updated only by an administrator authority of the client terminal. And an accumulation module file storage for storing the module, and an accumulation for storing the identifier of the module, version information, and a storage location on the storage module file storage in an area that can be updated only by an administrator authority of the client terminal. List of modules A user module list storage unit that is defined for each user identifier and stores the module identifier and the storage location on the storage module file storage unit, and the module identifier and version notified from the server If the information is not in the storage module list storage unit, an automatic update processing unit that obtains the module to be applied from the server and requests an update of the information on the module stored in the storage module file storage unit, and a client terminal The acquired module is stored in the storage module file storage unit based on the request of the automatic update processing unit, and the acquired module identifier, version information, and the storage module are operated. The storage module stores the storage location on the file storage unit. Update agent that registers in the list storage unit, acquires the module identifier notified from the server and the storage location on the storage module file storage unit from the storage module list storage unit, and registers in the user module list storage unit It functions as a processing unit.

  Further, the present invention provides the module update program, wherein the identifier of the module stored in the storage module file storage unit is further updated in an area where the client terminal can be updated only with administrator authority of the client terminal And the module list storage unit that stores the storage location on the storage module file storage unit, and the update agent processing unit is further acquired by the automatic update processing unit based on a request from the automatic update processing unit The module is registered in the module list storage unit.

  Further, the present invention provides the module update program, wherein the automatic update processing unit has an identifier of the module notified from the server when the module to be applied is determined as a module that does not need to be backed up. Then, the version of the module registered in the module list storage unit is compared with the version information of the module notified from the server, and if the version information of the module notified from the server is newer, The client terminal is caused to function so as to obtain a module to be applied from the server.

  Further, the present invention is the module update program, wherein the automatic update processing unit determines whether the module to be applied is a module that requires backup or a module that does not require backup based on a control code notified from the server. The client terminal is made to function so as to determine whether or not.

  In the present invention, even a general user having non-administrator authority can dynamically apply modules prior to the start of use of the system, and can simultaneously execute different versions of modules. It becomes. Furthermore, it is possible to prevent the wrong version from being applied by checking at the client terminal whether the module acquired from the server is the version to be applied.

  As described above, replacement work by maintenance personnel is not required at the time of module update, and inconsistency of the entire system due to human error can be suppressed. Furthermore, since different versions of modules can be executed on the same client terminal, the number of client terminals in the verification work can be saved.

  Embodiments will be described below with reference to the drawings.

  An embodiment of the present invention will be described below with reference to FIG.

  FIG. 1 is a diagram showing an embodiment of the system configuration of the present invention. The system of the present invention is composed of one or more clients 200 connected to the server 100 via a network. The server 100 includes a Web server 101, a version setting file 102, a screen configuration file 103, and an application module file 104. The Web server 101, the version setting file 102, the screen configuration file 103, and the application module file 104 do not necessarily need to be on the same server.

  The version setting file 102 stores version information of the automatic update processing unit 202, the number of application modules, version information of each application module, and the like.

  The client 200 includes a browser 201, an automatic update processing unit 202, an update proxy processing unit 203, and a self-update processing unit 204, and further includes a module list 205, a storage module file 206, a storage module list 207, and a user module list 208. Consists of.

  The browser 201 is, for example, a Web browser, and specifically includes an HTTP protocol transmission / reception function, an HTML document rendering function, and the like. The automatic update processing unit 202 has a function of performing a module update process in response to a request from the browser 201, and is executed with the same authority as that of the user, similar to the browser. The update agent processing unit 203 has a function of applying a module on the client terminal in response to a request from the automatic update processing unit 202. Depending on the client operating system, the update proxy processing unit 203 is equal to or more than the administrator who manages the client resources. It is executed with authority. The self-update processing unit 204 has a function of updating the automatic update processing unit 202 and the update proxy processing unit 203 in response to a request from the automatic update processing unit 202.

The module list 205, the storage module list 207, and the user module list 208 store information on existing modules held in the client 200.
Specifically, as shown in FIG. 3, module IDs 2051, 2071, 2081 for uniquely specifying modules and module storage locations 2052, 2072, 2082 are stored.

  The storage module file 206 indicated by the module storage location 2052, 2072, 2082 of the module list 205, storage module list 207, and user module list 208 includes a module ID 2061, version information 2062, and binary data 2063 as shown in FIG. Is stored.

Next, the flow of module application processing will be described with reference to FIG.
First, the browser 201 of the client 200 transmits an acquisition request for a system use start screen to the server 100 in response to a user instruction (S101 in FIG. 2). The Web server 101 of the server 100 receives the system usage start screen acquisition request of the client 200 via the network, and acquires the system usage start screen file from the screen configuration file 103 (S102 in FIG. 2).
Further, the Web server 101 of the server 100 returns the acquired system use start screen file to the client 200 (S103 in FIG. 2).

The client 200 analyzes the system use start screen file received from the server 100 (S104 in FIG. 2), and executes the initialization process of the module described in the use start screen file (S105 in FIG. 2). The content example of the screen configuration file shown in FIG. 6 shows the content example of the usage start screen file, and the module ID of the module to be used is specified by the attribute CLASSID of the <OBJECT> tag (1031 in FIG. 6). ). In the <SCRIPT> tag, a command for calling a process implemented in the module is described (1032 in FIG. 6). In this example, an example of contents for executing the module initialization process is shown, and the URL of the server storing the version setting file is specified as an argument thereof.
At this time, the browser that has received the above-described screen configuration file acquires from the module list 205 the module registered with the content that matches the module ID defined by the attribute CLASSID of the <OBJECT> tag, and the <OBJECT> tag The obtained module is associated with the identifier defined by the attribute ID (“SYSTEM_START” in the example of FIG. 6).
The processing of the command described in the <SCRIPT> tag described above is defined in the module defined in the <OBJECT> tag, and the browser identifies the necessary module by referring to the above module list, and < Execute the process described in the SCRIPT> tag.

In the example shown in FIG. 6, the module is stored in the module storage location 2052 “/ddworks21/AutoUpdate/FDDAxUpd.ocx” registered in the module list 205 with the attribute ID {xxxx-xxxx-0001} of the <OBJECT> tag. The module defines the processing of the command “ExecActiveXCheck” described in the <SCRIPT> tag. The command stored in the module “/ddworks21/AutoUpdate/FDDAxUpd.ocx” has the argument “” http: // www .system.ftk.fujitsu.co.jp / "" and will be executed.
Note that the module list 205 requires administrator authority of the client terminal when updating its contents, but can be executed with general user authority that does not have administrator authority if it is only a reference that does not involve updating. It has become.

  Upon receiving the module initialization process execution instruction, the automatic update processing unit 202 transmits a version setting file acquisition request to the server 100 having the URL specified in 1032 of the system start screen file (S106 in FIG. 2). .

  The Web server 101 of the server 100 that has received the acquisition request for the version setting file acquires the version setting file 102 stored in the location defined in the setting file (not shown) (S107 in FIG. 2), and the acquired version setting file 102 is returned to the client 200 (S108 in FIG. 2).

  The client 200 analyzes the version setting file 102 received from the server 100 (S109 in FIG. 2), and performs a self version check process (S110 in FIG. 2).

An example of the contents of the version setting file 102 is shown in FIG.
The version setting file 102 in FIG. 5 includes self-version information 102a (definition body starting with [UpdaterVersion] in the example of FIG. 5) and application module list information 102b (definition body of ModuleNum, Module [n] in the example of FIG. 5). Module version information 102c (definition body starting with [FDCFileCtl] in the example of FIG. 5) is stored.
The automatic update processing unit 202 compares the self version 1022 indicated by the self version information 102a of the version setting file with the versions of the automatic update processing unit and the update proxy processing unit of the client 200, and determines that the update is necessary. In this case, the self-update processing unit 204 performs update processing of the automatic update processing unit 202 and the update proxy processing unit 203.

  FIG. 7 shows the flow of the self-version check process described above.

  First, the self version information 102a is acquired from the version setting file, and the version specified in the acquired self version information 102a is compared with the module versions of the automatic update processing unit and the update proxy processing unit (S200 in FIG. 7). . As a result, when the update is unnecessary (Yes in S200 of FIG. 7), the process proceeds to execution of the process S111 without doing anything.

  When it is determined that the update is necessary (No in S200 of FIG. 7), the automatic update processing unit 202 executes the download of the self module from the download URL 1023 (DownloadUrl) specified by the self version information of the version setting file ( S201, S202 and S203 in FIG.

  The automatic update processing unit 202 that has downloaded the self-module has the module ID 2061 and version information 2062 stored in the downloaded self-module, the module ID and the module ID stored in the modules of the existing automatic update processing unit and update proxy processing unit, and The version specified by the self version information of the version setting file is compared to confirm that they match (S204 in FIG. 7).

  The replacement mode flag (ModeFlag) 1026 of the self version information 102a controls the operation of the automatic update processing unit when applying the self module.

  For example, when “1” is set in the replacement mode flag (ModeFlag) 1026, only the consistency between the version specified by the server and the version applied to the client is determined. That is, even if the client version is newer than the version specified from the server, the older version specified from the server is downloaded.

  If the replacement mode flag (ModeFlag) 1026 is set to “0”, not only the version specified by the server and the version already applied to the client, but also the version specified by the server When newer than the version, the specified new version is downloaded from the server.

  By setting “0” in the replacement mode flag 1026 by the above control, even if the old version of the module to be applied is stored in the server by mistake, the module is not acquired from the server. It is possible to maintain the latest module on the client terminal.

  In addition, if a failure occurs in the applied module, by setting "1" in the replacement mode flag 1026, it becomes possible to apply the previous version that has not failed on each client terminal, It is possible to easily switch between a verification environment in which module operation is verified and a production environment in which operation is performed with a verified module.

  If there is an error in the definition of the version setting file stored on the server by checking the version of the self module after downloading, for example, the version specified in the self version information of the version setting file and the self module Can be prevented from being applied to the client in the wrong version (S204 in FIG. 7). In the example shown in FIG. 7, when the version specified by the self-version information of the version setting file and the version stored in the self-module do not match (No in S204 in FIG. 7), the automatic update processing unit 202 performs the server 100 The Web server 101 of the server 100 that has received the error information displays a warning message on the screen or transmits a warning mail to the administrator's mail address designated in advance (S205 in FIG. 7).

  In the self-version check after downloading described above, if the version of the downloaded self-module matches the specified version (Yes in S204 in FIG. 7), application of the module is requested to the update proxy processing unit 203 (FIG. 7). S206). Upon receiving the request, the update agent processing unit 203 activates the self-update processing unit 204 (S207 in FIG. 7). The self-update processing unit 204 that receives the activation instruction from the update proxy processing unit 203 operates with the same authority as the update proxy processing unit 203 (S207 'in FIG. 7). In other words, the self-update processing unit 204 enters an operating state having administrator authority to manage client resources, and can stop the activity of the update agent processing unit 203 having the same authority. In the above operating state, it is also possible to stop the activity of the automatic update processing unit that operates with the general user authority.

The self-update processing unit 204 ends the browser 201 (S208 in FIG. 7), and notifies the automatic update processing unit 202 and the update proxy processing unit 203 of a stop command (S209 in FIG. 7).
The automatic update processing unit 202 and the update agent processing unit 203 that have received the stop command receive a stop command from the self-update processing unit 204 that operates with the same or higher authority as the authority that operates. The processing is stopped (S209 ′ in FIG. 7).

  The self-update processing unit 204 that has received the suspension of the automatic update processing unit 202 and the update proxy processing unit 203 replaces the modules of the automatic update processing unit 202 and the update proxy processing unit 203 with the downloaded self-module (S210 in FIG. 7).

Next, the self-update processing unit 204 restarts the automatic update processing unit 202 and the update proxy processing unit 203 using the replaced module (S211 and S211 ′ in FIG. 7).
At that time, the automatic update processing unit 202 is executed with the authority of the user, and the update proxy processing unit 203 is executed with the same authority as the self-update processing unit 204.

  After the automatic update processing unit 202 and the update proxy processing unit 203 have started normally, the self-update processing unit 204 starts the browser 201 (S212 in FIG. 7), and re-executes module application processing to the browser 201. After commanding (S213 in FIG. 7), the process is terminated.

  The above is the flow of the self version check process.

  Next, the automatic update processing unit 202 checks whether the application module is a module that requires backup (S111 in FIG. 2).

  First, the automatic update processing unit 202 acquires the number of modules to be applied based on the module number 1027 (ModuleNum) specified in the application module list information 102b, and acquires the application module information name (Module [n]) 1028. That is, the number of application module information names defined is the number specified by the module number 1027.

  The automatic update processing unit 202 acquires module information 102c having module information name 1029 that matches the acquired applied module information name 1028, and acquires a replacement mode flag (ModeFlag) 1034 specified by the acquired module information 102c To determine the necessity of backup.

  For example, if “1” is set in the replacement mode flag 1034, it is determined that backup is necessary, and if “0” is set, it is determined that backup is not necessary.

  If backup is not necessary (No in S111 of FIG. 2), the designated version of the application module is compared with the version of the same module stored in the storage module file 206 (S112 of FIG. 2).

The automatic update processing unit 202 acquires the module information 102c having the module information name 1029 that matches the acquired application module information name 1028, and sets the module ID 2051 that matches the module ID 1032 (CLSID) specified by the acquired module information 102c. The module storage location 2052 registered in association is acquired from the module list 205.
Further, the version information 2062 is acquired from the storage module file 206 specified by the module storage location 2052, and compared with the version information 1030 of the module information 102c specified by the version setting file.

If the version information 1030 of the module information 102c specified in the version setting file is newer, including the case where the module ID 2051 matching the module ID 1032 (CLSID) specified in the version setting file does not exist in the storage module file 206 (Yes in S112 of FIG. 2), the automatic update processing unit 202 downloads the application module from the download URL 1031 (DownloadUrl) specified by the module information 102c of the version setting file 102 (S113, S114, and S115 of FIG. 2). ).
The automatic update processing unit 202 that has downloaded the application module compares the module ID and version information stored in the application module with the module ID and version information specified by the module information in the version setting file, and they match. This is confirmed (S116 in FIG. 2).

  If there is an error in the definition of the version setting file stored on the server by checking the version of the applied module after downloading, for example, it is stored in the version and module specified in the module information of the version setting file. If the version does not match (No in S116 of FIG. 2), it is possible to prevent the wrong version of the module from being applied to the client.

  In the example shown in FIG. 2, when the version specified in the module information of the version setting file and the version stored in the module do not match (No in S116 in FIG. 2), the automatic update processing unit 202 gives an error to the server 100. Upon receiving the information and receiving the error information, the Web server 101 of the server 100 displays a warning message on the screen or transmits a warning mail to the administrator's mail address designated in advance (S117 in FIG. 2).

  If the downloaded version of the module matches the specified version in the version check after downloading (Yes in S116 in FIG. 2), the automatic update processing unit 202 requests the update proxy processing unit 203 to store the module. (S118 in FIG. 2). The update proxy processing unit 203 stores the module in the storage module file 206 and registers it in the module list 205 (S119 in FIG. 2). At this time, if a module having the same module ID as the designated module ID exists in the storage module file 206, this module is deleted and a new module is stored. If module information having the same module ID 2051 as the specified module ID is already registered in the module list 205, the storage location 2052 is rewritten.

  With these processes, for example, when applying a backward-compatible module, it is treated as a backup-free, and only the latest version is retained, so that even if an old module is specified, a new download is not required. Can receive service.

  Thereafter, the browser 201 displays the system usage start screen of the business system, and the usage of the business system is started (132 in FIG. 2).

  If the version is the same or the version information 1030 of the module information 102c specified in the version setting file is older (No in S112 in FIG. 2), the update process is terminated as no update is necessary, and the browser 201 The system use start screen is displayed and the use of the business system is started (132 in FIG. 2).

  When backup is necessary (Yes in S111 of FIG. 2), the automatic update processing unit 202 checks whether or not a backup exists in the storage module list 207 (S120 of FIG. 2).

  The automatic update processing unit 202 acquires, from the storage module list 207, the module storage location 2072 registered in association with the module ID 2071 that matches the module ID 1032 (CLSID) of the module information 102c specified in the version setting file. Further, if the version information 2062 is acquired from the storage module file 206 specified by the module storage location 2072 and matches the version information 1030 of the module information 102c specified by the version setting file (Yes in S120 of FIG. 2), this The update proxy processing unit 203 is requested to apply (S130 in FIG. 2). The update proxy processing unit 203 copies the module ID 2071 and storage location 2072 of this module from the storage module list 207 to the user module list 208 and registers them as the module ID 2081 and storage location 2082 (S131 in FIG. 2). Thereafter, the browser 201 displays the system usage start screen of the business system, and the usage of the business system is started (132 in FIG. 2).

  If it has not been backed up (No in S120 of FIG. 2), that is, if the module ID 2071 that matches the module ID 1032 (CLSID) of the module information 102c specified in the version setting file does not exist in the storage module list 207, or version setting The module ID 2071 that matches the module ID 1032 (CLSID) of the module information 102c specified in the file exists in the storage module list 207, but the version information 2062 of the storage module file in the corresponding storage location 2072 is specified in the version setting file If the module information 102c does not match the version information 1030, the automatic update processing unit 202 downloads the application module from the download URL 1031 (DownloadUrl) specified by the module information 102c of the version setting file 102 (FIG. 2). 121, S122 and S123).

  The automatic update processing unit 202 that has downloaded the application module compares the module ID and version information stored in the application module with the module ID and version information specified by the module information in the version setting file, and they match. This is confirmed (S124 in FIG. 2).

  If there is an error in the definition of the version setting file stored on the server by checking the version of the applied module after downloading, for example, it is stored in the version and module specified in the module information of the version setting file. If the version does not match (No in S124 in FIG. 2), it is possible to prevent the wrong version of the module from being applied to the client.

  In the example shown in FIG. 2, when the version specified in the module information of the version setting file and the version stored in the module do not match (No in S124 in FIG. 2), the automatic update processing unit 202 gives an error to the server 100. The Web server 101 of the server 100 that has transmitted the information and received the error information displays a warning message on the screen or transmits a warning mail to the administrator's mail address designated in advance (S125 in FIG. 2).

  If the downloaded module version matches the specified version (Yes in S124 in FIG. 2), the automatic update processing unit 202 requests the update proxy processing unit 203 to store the module (S126 in FIG. 2). The update proxy processing unit 203 stores the module in the storage module file 206 and registers it in the module list 205 (S127 in FIG. 2). At this time, even if a module having the same module ID as the designated module ID exists in the storage module file 206, this module is not deleted and a new module is additionally stored. If module information having the same module ID 2051 as the specified module ID is already registered in the module list 205, the storage location 2052 is rewritten.

  Subsequently, the automatic update processing unit 202 requests the update proxy processing unit 203 to back up the application module (S128 in FIG. 2). Upon receiving the backup request, the update proxy processing unit 203 copies the module ID 2051 and storage location 2052 of the application module from the module list 205 to the storage module list 207 to obtain the module ID 2071 and storage location 2072, and further exists in the storage location 2072. The version information 2062 of the storage module file 206 is copied to the storage module list 207 as version information 2073, and these are additionally registered (S129 in FIG. 2).

  The automatic update processing unit 202 further requests the update proxy processing unit 203 to apply the module (S130 in FIG. 2). Upon receiving the application request, the update proxy processing unit 203 copies the module ID 2071 and storage location 2072 of the application module from the storage module list 207 to the user module list 208 and registers them as the module ID 2081 and storage location 2082 (S131 in FIG. 2). ).

  With these processes, for example, when applying a module that is not backward compatible, treat it as a backup necessity and accumulate each version of the module so that a different version of the module is downloaded each time it is specified. You can receive business services without.

  Further, when backup is unnecessary, the storage module list 207 may be backed up. In this case, for example, only the latest version is placed in the storage module file 206, and all storage locations of the same module ID in the storage module list 207 are storage locations of the latest version. By doing this, even if the backward compatibility of this module is no longer guaranteed at a later date, the old version of the module is backed up, and the service can be used continuously without taking any special measures.

The module list 205, the storage module file 206, and the storage module list 207 are arranged in a storage area that can be updated only by a process having a specific authority. For example, the process is updated in a user application process that is executed with a general user authority. Can not do it. The update agent processing unit 203 described above has authority to update the module list 205, the storage module list 207, and the user module list 208 regardless of the authority of the client user depending on the client operating system. Have and run. Therefore, even if the user of the client has general user authority, the module list 205 and the storage module list 207 can be updated, and module application can be dynamically performed regardless of the user authority. In particular, since a normal user uses a client with general user authority, the user often does not have authority to update a module when using the system.
However, the above-mentioned update agent processing unit can automatically improve the client environment while continuing to use the client with general user authority, greatly reducing the load on the user and avoiding update omissions. It also prevents quality and leads to quality improvement.

  After the above-described module application processing is completed, the browser 201 of the client 200 displays the system usage start screen of the business system and starts using the business system (132 in FIG. 2). When the use of the business system is started, the operating system of the client 200 searches the user module list 208 defined for the user of the browser 201 for the business module to be executed and executes it. If the necessary business module is not found in the user module list 208, it is searched for in the module list 205 and executed.

  In the above-described embodiment, the update target is a module, but various definition bodies may be used. As the definition body, for example, a form definition body, a template in OA software such as spreadsheet or word processing software, and the like can be considered. In this case, in the conventional technology, a template in OA software such as a spreadsheet or word processor is embedded in a form and sent to the client. However, since various definition bodies and templates are replaced in advance, the client Only data (value) is transmitted to the network, and the amount of traffic on the network can be reduced.

As described above, this embodiment eliminates the need for replacement work by maintenance personnel when updating modules, and prevents inconsistencies in the entire system due to human error. Furthermore, since different versions of modules can be executed on the same client terminal, the number of client terminals in the verification work can be saved.
(Additional remark 1) The following additional remark 1 is disclosed regarding embodiment including the said Example 1. FIG.

A computer system that provides a business service, a version setting file storage unit that stores a version setting file that describes an identifier and version information of a program module to be applied to the business service, and an application module file storage unit that stores the module A storage module file storage unit that stores the modules stored in the application module file storage unit, a user identifier reception unit that receives input of a user identifier, an identifier of the module, version information, and the storage module file A storage module list storage unit that stores a storage location on the storage unit; a user module list storage unit that is defined for each user identifier and stores the identifier of the module and the storage location on the storage module file storage unit; ,in front If the module identifier and version information set in the version setting file are not in the storage module list storage unit, the module is acquired from the application module file storage unit, and information about the module stored in the storage module file storage unit An automatic update processing unit that requests updating, and the acquired module is stored in the storage module file storage unit based on a request from the automatic update processing unit, and the acquired module identifier, version information, and the storage The storage location on the module file storage unit is registered in the storage module list storage unit, the identifier of the module and the storage location on the storage module file storage unit are obtained from the storage module list storage unit, and the user module list Register in memory Computer system, wherein the new proxy processing unit, in that it consists of.
(Additional remark 2) The following additional remark 2 is disclosed regarding embodiment containing the said Example 1. FIG.

A program module to be applied to the client terminal is stored, and the client terminal connected to a server for notifying the client terminal of the module identifier and version information is received from the server, and an input of a user identifier is received from the server. A user identifier reception unit that receives notification of an identifier and version information, a storage module file storage unit that stores the module identifier, version information, and the module in an area that can be updated only by an administrator authority of the client terminal; A storage module list storage unit that stores the module identifier, version information, and storage location on the storage module file storage unit in an area that can be updated only with administrator authority of the client terminal, and is defined for each user identifier And the module User module list storage unit that stores the identifier of the module and the storage location on the storage module file storage unit, and if the module identifier and version information notified from the server are not in the storage module list storage unit, the application An automatic update processing unit that obtains a module to be acquired from the server, and requests update of information related to the module stored in the storage module file storage unit, and operates with an administrator authority of the client terminal, and the automatic Based on the request from the update processing unit, the acquired module is stored in the storage module file storage unit, and the acquired module identifier, version information, and storage location on the storage module file storage unit are stored in the storage module list storage. The module notified from the server. The module update is made to function as an update agent processing unit that obtains the identifier of the message and the storage location on the storage module file storage unit from the storage module list storage unit and registers them in the user module list storage unit program.
(Additional remark 3) The following additional remark 3 is further disclosed regarding embodiment containing the said Example 1. FIG.

The module update program according to attachment 2, wherein the module further stores the identifier of the module stored in the storage module file storage unit in an area where the client terminal can be updated only with an administrator authority of the client terminal The module that functions as a module list storage unit that stores a storage location on the storage module file storage unit, and the update proxy processing unit is further acquired by the automatic update processing unit based on a request from the automatic update processing unit Is registered in the module list storage unit.
(Additional remark 4) The following additional remark 4 is further disclosed regarding embodiment including the said Example 1. FIG.

The module update program according to attachment 3, wherein the automatic update processing unit has an identifier of the module notified from the server when the module to be applied is determined as a module that does not need to be backed up, The version of the module registered in the module list storage unit is compared with the version information of the module notified from the server. If the version information of the module notified from the server is newer, the version is applied. A module update program for causing the client terminal to function so as to obtain a module to be obtained from the server.
(Additional remark 5) The following additional remark 5 is disclosed regarding embodiment containing the said Example 1. FIG.

The module update program according to appendix 4, wherein the automatic update processing unit determines whether the module to be applied is a module that requires backup or a module that does not require backup based on a control code notified from the server. A module update program that causes the client terminal to function so as to make a determination.
(Additional remark 6) The following additional remark 6 is further disclosed regarding embodiment including the said Example 1. FIG.
The module update program according to any one of appendices 2 to 5, wherein the automatic update processing unit confirms consistency between the module identifier and version acquired from the server and the module identifier and version notified from the server. And a module update program for notifying a warning to the server and causing the client terminal to function so as not to register the module acquired from the server when the two are not matched.
(Additional remark 7) The following additional remark 7 is disclosed regarding embodiment containing the said Example 1. FIG.

The module update program according to any one of appendices 2 to 6, wherein the client terminal is further operated with the same authority as the update agent processing unit, and the execution of the automatic update processing unit and the update agent processing unit is stopped, Update the module of the automatic update processing unit and the update proxy processing unit, and function the client terminal as a self-update processing unit that restarts the automatic update processing unit and the update proxy processing unit using the updated module The automatic update processing unit further compares the version of the module update program notified from the server with the version of the module update program registered in the module list storage unit, and determines that the update is necessary. The module update program module notified from the server Module Update, characterized by al acquired.
(Additional remark 8) The following additional remark 8 is further disclosed regarding embodiment including the said Example 1. FIG.

The module update program according to appendix 7, wherein the automatic update processing unit registers the version of the module update program notified from the server in the module list storage unit based on the control code notified from the server It is updated only when it is newer than the version of the installed module update program, or updated when the version of the module update program notified from the server does not match the version of the module update program registered in the module list storage unit A module update program which causes the client terminal to function so as to switch between the two.
(Additional remark 9) The following additional remark 9 is disclosed regarding embodiment containing the said Example 1. FIG.

A program module to be applied to a client terminal is stored in the client terminal connected to a server for notifying the client terminal of the module identifier and version information. The client terminal accepts an input of a user identifier from the server. A user identifier receiving unit that receives a notification of a module identifier and version information, and a storage module file storage unit that stores the module identifier, version information, and the module in an area that can be updated only by administrator authority of the client terminal A storage module list storage unit that stores the module identifier, version information, and a storage location on the storage module file storage unit in an area that can be updated only by administrator authority of the client terminal, and each user identifier. Defined above A user module list storage unit that stores a module identifier and a storage location on the storage module file storage unit, and the application and the module identifier and version information notified from the server are not included in the storage module list storage unit. An automatic update processing unit that obtains a module to be acquired from the server, and requests update of information related to the module stored in the storage module file storage unit, and operates with an administrator authority of the client terminal, and the automatic Based on the request from the update processing unit, the acquired module is stored in the storage module file storage unit, and the acquired module identifier, version information, and storage location on the storage module file storage unit are stored in the storage module list storage. Registered in the department and notified from the server An update agent processing unit that acquires a module identifier and a storage location on the storage module file storage unit from the storage module list storage unit and registers the module in the user module list storage unit. .
(Additional remark 10) The following additional remark 10 is disclosed regarding embodiment containing the said Example 1. FIG.

The client terminal according to attachment 9, wherein the module identifier stored in the storage module file storage unit and the storage module file storage unit are further updated in an area that can be updated only by an administrator authority of the client terminal. A module list storage unit for storing the storage location above, and the update agent processing unit further stores the module acquired by the automatic update processing unit based on a request from the automatic update processing unit in the module list storage A client terminal characterized by being registered in a department.
(Additional remark 11) The following additional remark 11 is further disclosed regarding embodiment including the said Example 1. FIG.

The client terminal according to attachment 10, wherein the automatic update processing unit has an identifier of the module notified from the server when the module to be applied is determined as a module that does not need to be backed up, Compare the version of the module registered in the module list storage unit with the version information of the module notified from the server. If the version information of the module notified from the server is newer, the version should be applied. A client terminal, wherein a module is obtained from the server.
(Additional remark 12) The following additional remark 12 is disclosed regarding embodiment containing the said Example 1. FIG.

The client terminal according to attachment 11, wherein the automatic update processing unit determines whether the module to be applied is a module that requires backup or a module that does not require backup based on a control code notified from the server A client terminal.
(Additional remark 13) The following additional remark 13 is disclosed regarding embodiment containing the said Example 1. FIG.
The client terminal according to appendices 9 to 12, wherein the automatic update processing unit confirms consistency between the module identifier and version acquired from the server and the module identifier and version notified from the server. A client terminal characterized by notifying a warning to the server and not registering a module acquired from the server when they do not match.
(Additional remark 14) The following additional remark 14 is disclosed regarding embodiment containing the said Example 1. FIG.

The client terminal according to appendices 9 to 13, further operating with the same authority as the update agent processing unit, stopping execution of the automatic update processing unit and the update agent processing unit, The self-update processing unit that updates the module of the update proxy processing unit and restarts the automatic update processing unit and the update proxy processing unit using the updated module, and the automatic update processing unit further includes: The version of the module update program notified from the server is compared with the version of the module update program registered in the module list storage unit, and when it is determined that the update is necessary, the version is notified from the server. A client terminal, wherein the module update program module is acquired from the server.
(Additional remark 15) The following additional remark 15 is disclosed regarding embodiment containing the said Example 1. FIG.

  The client terminal according to attachment 14, wherein the automatic update processing unit registers the version of the module update program notified from the server in the module list storage unit based on the control code notified from the server. It is updated only when it is newer than the version of the installed module update program, or updated when the version of the module update program notified from the server does not match the version of the module update program registered in the module list storage unit A client terminal characterized by switching and operating.

The figure which shows one Embodiment of the structure of the system by this invention Flow chart showing the flow of module application processing The figure which shows the contents example of the module list, the accumulation module list and the user module list Figure showing an example of the contents of a storage module file Figure showing example contents of version setting file A diagram showing an example of the contents of a screen configuration file Flow chart showing the flow of self-version check process

Explanation of symbols

100: Server 101: Web server 102: Version setting file 103: Screen configuration file 104: Applicable module file 200: Client 201: Browser 202: Automatic update processing unit 203: Update proxy processing unit 204: Self-update processing unit 205: Module list 2051, 2061, 2071, 2081: Module ID
2052, 2072, 2082: Storage location 206: Storage module file 2062, 2073: Version information 2063: Binary data 207: Storage module list 208: User module list

Claims (5)

A computer system that provides business services,
A version setting file storage unit for storing a version setting file describing an identifier and version information of a program module to be applied to the business service;
An application module file storage for storing the module;
A storage module file storage for storing the modules stored in the application module file storage;
A user identifier receiving unit for receiving an input of a user identifier;
A storage module list storage unit for storing the module identifier, version information, and a storage location on the storage module file storage unit;
A user module list storage unit that is defined for each user identifier and stores the identifier of the module and the storage location on the storage module file storage unit;
If the module identifier and version information set in the version setting file are not in the storage module list storage unit, the module is acquired from the application module file storage unit, and the module is stored in the storage module file storage unit An automatic update processor that requests information update;
Based on the request of the automatic update processing unit, the acquired module is stored in the storage module file storage unit, and the acquired module identifier, version information, and storage location on the storage module file storage unit are stored in the storage. An update proxy processing unit that registers in the module list storage unit, acquires the identifier of the module and the storage location on the storage module file storage unit from the storage module list storage unit, and registers the module in the user module list storage unit;
A computer system characterized by comprising: Storing the program module to be applied to the client terminal, the client terminal connected to a server notifying the client terminal of the identifier and version information of the module;
A user identifier receiving unit that receives an input of a user identifier and receives a notification of the module identifier and version information from the server;
An accumulation module file storage unit that stores the module identifier and version information and the module in an area that can be updated only by administrator authority of the client terminal;
A storage module list storage unit that stores the module identifier, version information, and a storage location on the storage module file storage unit in an area that can be updated only by administrator authority of the client terminal;
A user module list storage unit that is defined for each user identifier and stores the identifier of the module and the storage location on the storage module file storage unit;
If the identifier and version information of the module notified from the server are not in the storage module list storage unit, the module to be applied is acquired from the server, and information on the module stored in the storage module file storage unit is stored. An automatic update processor that requests an update,
Operates with the administrator authority of the client terminal, and based on the request of the automatic update processing unit, stores the acquired module in the storage module file storage unit, the acquired module identifier, version information and the The storage location on the storage module file storage unit is registered in the storage module list storage unit, and the module identifier notified from the server and the storage location on the storage module file storage unit are acquired from the storage module list storage unit. As an update proxy processing unit registered in the user module list storage unit,
A module update program characterized by functioning. The module update program according to claim 2,
The client terminal is further
Functions as a module list storage unit that stores an identifier of the module stored in the storage module file storage unit and a storage location on the storage module file storage unit in an area that can be updated only by administrator authority of the client terminal Let
The update agent processing unit further registers the module acquired by the automatic update processing unit in the module list storage unit based on a request from the automatic update processing unit. The module update program according to claim 3,
When the automatic update processing unit determines that the module to be applied is a module that does not need to be backed up, the automatic update processing unit has an identifier of the module notified from the server, and the module registered in the module list storage unit The client compares the version with the version information of the module notified from the server and, if the version information of the module notified from the server is newer, acquires the module to be applied from the server. A module update program for causing a terminal to function. The module update program according to claim 4,
The automatic update processing unit causes the client terminal to function so as to determine whether the module to be applied is a module that requires backup or a module that does not require backup based on a control code notified from the server. Feature module update program.

Images