JPH09258967A - Client application management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make work from the development of client application to distribution to be efficient, to prevent the occurrence of a system fault owing to the non-matching of versions and to secure the security of data by means of the constitution management of a client. SOLUTION: When a machine (general) 2 requests service to a server machine 1, the version of client AP(application) 223-2 is compared with the version of client AP123. When they are not matched, client AP 123 is transferred to the machine (general) 2. Client AP 323 which is version-up from a machine (developer) 3 is registered in the server machine 1 and client AP management DB122 is updated. The client which can receive service from a machine (manager) 4 and the constitution of client AP are registered.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a management system for a client side application (hereinafter abbreviated as client AP) in a client / server system.

[0002]

2. Description of the Related Art It is widely practiced to connect a plurality of machines via a network and use a service (resource) provided by one machine from another machine. In such a system, a machine that provides a service is called a server, and a machine that uses the service is called a client. In this client / server system, an application generally exists in the client in order to receive the service provided by the server, and the version U of the client application is changed as the service provided by the server is changed.
P is required.

According to Japanese Patent Laid-Open No. 5-128031,
The server manages the configuration of the client side application, and when the client requests a service, the client application can be automatically updated if the version of the application owned by the client is old.

However, registration of the developed client application in the server and registration of the client configuration management are generally performed manually by the client application developer and the server machine administrator.

When the client AP is registered in the server, the client AP developed by each client is
A file transfer command is used to transfer to the server, and the server manually changes the directory in which the client AP is to be stored. After the file transfer, the client AP is stored.
Of the storage AP, the client AP name, its version, the storage directory, etc. are recorded in the storage medium for management of the client AP.

In the case of the version UP of the client AP, the client AP name, its version, the storage directory, etc. are read from the recording medium, the version is confirmed, and then one version is updated by itself and recorded again in the recording medium. ing.

When the client configuration management is registered in the server machine, the client machine name, OS, and available client APs are manually recorded in the client configuration information storage medium.

When a new client AP is released, the storage medium of the client configuration information is manually searched based on the client machine name, the currently owned client AP is checked, and if there is no new client AP, the client configuration is released. A new quaint AP name, version, etc. are manually recorded on the information storage medium.

[0009]

In the above-mentioned prior art, since the management of the client AP and the management of the client are performed manually, a mistake is likely to occur, a version mismatch and an incorrect client AP are sent to the client. There is a problem that the version management of the client side application on the server and the management of the client that can receive the service provided by the server are not reliably performed, such as transferring the client AP to the wrong directory of the server. There is.

An object of the present invention is to prevent the occurrence of a system failure due to version mismatch and to secure the data security by managing the configuration of the client by combining the automatic updating means of the client application with the client application managing means and the client managing means. And, a client application management system for performing a series of release work (from the developer to the user) after the development of the client application is made efficient.

[0011]

A client application management system of a first invention is a client application management means for storing the latest version of an application used by a client, and a client application management system for storing client application information of the client application. Client application registration means for registering a database and a client application developed by a developer in the client application storage means, and registering the client application information in the client application management database, and client management for storing client information of a client to be serviced Database and client classes that receive the above services A server machine provided with client management means for registering and managing client information in the client management database and client application version updating means for transferring the latest version of the client application to the client and upgrading the client application version upon request, A client machine for developers provided with a client application registration requesting means for transferring the developed client application and the client application information to the server machine, and transferring the client information of the client to the server machine and registering the same. And a client machine for an administrator having a client management requesting means for performing.

A client application management system according to a second aspect of the present invention is the client application management system according to the first aspect of the present invention, which has a client machine for a developer / administrator, which includes client application registration requesting means and client management requesting means. It is characterized by that.

The client application management system of the third invention is characterized in that, in the client application management system of the first or second invention, the client machine has an identifier of a server machine which manages the client application.

A client application management system of a fourth invention is the client application management system of the first, second or third invention,
The client application information is characterized by including a service name which is an identifier of the client application, version information, update date and time, and available client information.

The client application management system of the fifth invention is the client application management system of the first, second, third or fourth invention, wherein the client information is the client machine name which is the identifier of the client and the client. Is characterized by including a service name which is an identifier of a client application used by the client, version information, update date and time, and client type information indicating a difference in service usage such as OS of the client.

[0016]

Next, an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a client application management system according to an embodiment of the present invention.

As shown in FIG. 1, a client application management system according to an embodiment of the present invention includes a server machine 1 for providing a service and a client machine (development) used by a developer who develops an application and upgrades the version. Person) 3, a client machine (administrator) 4 used by an administrator who integrally manages the client application management system, and a client machine (general) 2 used by a developer or a person other than the administrator. . Generally, a plurality of client machines (general) 2 and client machines (developer) 3 can exist, but there is only one client machine (administrator) 4.

The server machine 1 comprises a storage unit 12 for storing data and the like, and a processing unit 11 for performing various processes.

The storage unit 12 stores a client AP management DB for storing client AP information for managing the client AP, a client AP 123 for storing one or more client APs, and client information for managing the clients. DB for client management 124 to store, client and client AP
And a normal service DB 121 for storing information on services normally performed by the server machine 1 other than the information for managing the.

In the processing unit 11, the client AP developed by the developer or updated in version and a client AP in response to a registration request of the client AP information.
123 and the client AP registration means 112 for registering in the client AP management DB 122, and referring to the client management DB 124 and the client AP management DB 122 in response to a client AP version check inquiry, the client validity is checked. If the client AP version is different, the latest version of client A
DB for client management by transferring P to the client 12
4 to update client AP version UP means 11
3 and client management means 114 for registering in the client management DB 124 in response to a registration request of the client information of the client from the administrator.

Client machines (general) 2, client machine (developer) 3 and client machine (administrator) 4 store client APs 223-2, 223-3 and 223, respectively.
-4 and input / output devices 23 and 33 for input and output
And 43 and the client AP from the server machine 1
A normal service using means 211 for using and processing the service and other normal services is provided.

Further, the client machine (developer) 3
Is a client AP registration request means 312 for requesting registration of the client AP 323 for version UP storing the client AP developed for version UP and the client AP developed and version of the client AP information.
The client machine (administrator) 4 is provided with a client and a client management requesting means 412 for requesting registration of the client information.

Version UP client A developed for version UP on the client machine (developer) 3
P323 is the version UP information (service name, version information, update date and time, service content, available client type (described later), etc.) input by the client machine (developer) 3 and the server machine 1 by the client AP registration request means 312. Transferred to.

The client AP registration means 112 updates the client AP management DB 122 to the latest version information, and the client AP updates the client AP 12
3 is stored in a predetermined place.

When the normal service using means 211 is executed on the client machine (general) 2, the client AP version UP means 113 of the server machine 1 accesses the client management DB 124 to determine whether the service is available (is the client registered?). I will be checked.

If registered, the client AP 223 obtained simultaneously from the client management DB 124
2 client information, that is, client machine name, service name, version information, client type,
The client AP management DB 122 is accessed based on the update date and time, and it is checked whether the version UP of the client AP 223-2 is necessary.

When version UP is required, the latest client AP 123 is sent to the client machine (general) 2.
Is transferred.

When the client machine cannot receive the service (is not registered), the administrator is requested to request the service of the client. The client machine name, service name, client type (described later), etc. in the client information input by the client management request means 412 of the client machine (administrator) 4 are registered in the client management DB 124 by the client management means 114.

FIG. 2A shows a client AP management DB.
122 is a configuration diagram of 122, a process flow diagram of the client AP registration requesting unit 312 of FIG. 1, and a process flow diagram of the client AP registration unit 112 of FIG.

The client AP management DB 122 shown in FIG. 2A is composed of the service name provided to the client machine, the service version, the update date and time, the service content, the available client type, and the like. The service name and version are used as unique keys so that multiple versions of a certain service name are not registered by mistake. The usable client type classifies the client into a plurality of types according to the difference in OS and the like, and only the clients belonging to the types described in this column are the client APs.
Indicates that is available.

FIG. 2B shows the client AP shown in FIG.
It is a processing flow of the registration request means 312. When the process starts, the input / output device 33 shown in FIG. 1 waits for input (waits for registration execution) (loop of steps 2101, 2102), and the client AP developer inputs the client AP information to the server machine 1. When you execute the registration request,
The input client AP information and client AP are transferred to the server machine 1 (step 2103). When the transfer is completed, it waits for a response from the server machine 1 (loop of steps 2104 and 2105). Server machine 1
When the fact that the processing on the server machine 1 has been completed is received from (the client AP registration means 112 in FIG. 1) (step 2106), it is displayed on the input / output device 33 (step 2107).

FIG. 2C shows the client AP shown in FIG.
It is a processing flow of the registration means 112. When the process is started, the process from the client machine 3 (client AP registration requesting means 312 in FIG. 1) is accepted (step 22).
(YES branch of 01, 2202), the client AP transferred from the client machine 3 is stored in a predetermined storage location (step 2203). If the storage is successful (YES branch of step 2204), the client AP information is registered in the client AP management DB 124 (step 2).
205). After that, the client machine 3 is notified of normal termination (abnormal termination when an error occurs) (step 2206).

In this way, the client AP management D
B122 and the client AP registration means 112 of FIG.
By using the client AP registration request means 312, the developed client AP can be easily registered in the server machine 1 and managed.

FIG. 3A shows a client management DB 12
4 is a configuration diagram of FIG. 4, (b) is a process flow diagram of the client management requesting unit 412 of FIG. 1, and (c) is a process flow diagram of the client managing unit 114.

DB for client management shown in FIG. 3 (a)
Reference numeral 124 denotes a client machine name, a service name received by each client machine, a service version,
It consists of client type, update date and time, etc. The client machine name and service name are used as unique keys so that multiple service names of a client machine are not registered by mistake.

Security is ensured not only by registering the client machine in the client management DB 124 but also by limiting the services provided to the client machine. That is, the client machine q in FIG.
The services that qq456 can receive are a1. exe ~ f
1. exe is the client AP management D of FIG.
By referring to B122, in this case, data registration, data approval, and other data updates can be performed. On the other hand, the service that the client machine kkk123 can receive is d
1. With exe, in this case only data search can be performed, and k
Data destruction due to kk123 can be prevented.

There is a case where the client AP developed by one client cannot be used by another client due to the difference in the OS of the client. Therefore, the "client type" is used as the client information to represent the difference in the OS of the client, and the "client type" is used as the available client type in the client AP management DB 122.

FIG. 3B is a processing flow of the client management request means 412 shown in FIG. When the processing is started, the input / output device 43 shown in FIG. 1 waits for input (waits for an inquiry) (loop of steps 3101 and 3102), and the system administrator inputs a client name and registration information of the client AP to make an inquiry. By executing, the input client name is transferred to the server machine 1 (step 3103). When the transfer is completed, it waits for a response from the server machine 1 (steps 3104 and 3105).
Loop). When the end of processing on the server machine 1 is received from the server machine 1 (client management means 114 in FIG. 1), the registration information for the client requesting the inquiry (when the client machine is newly registered, there is no registration information) and the current The client AP information and the client AP information are simultaneously displayed on the input / output device 43 (step 3106). Next, waiting for input from the input / output device 43 shown in FIG. 1 (waiting for registration) (loop of steps 3107 and 3108),
When the system administrator inputs client information (selected from the client AP information displayed on the input / output device 43) and executes registration in the server machine 1, the input client information is transferred to the server machine 1 (step 3109). When the transfer is completed, the server machine 1 waits for a response (loop of steps 3110 and 3111). Server machine 1 (client management means 1 in FIG. 1
When the processing end on the server machine 1 is received from 14) (step 3112), it is displayed on the input / output device 43 (step 3113).

FIG. 3C is a processing flow of the client management means 114 shown in FIG. When the process starts
Accept the process from the client machine 4 (client management request means 412 in FIG. 1) (Y in step 3202).
ES branch), based on the client machine name transferred from the client machine 4, the client management DB 124 is searched to obtain client information. Client A at the same time
The P management DB 122 is searched and the current client AP is searched.
Obtain information (step 3203). Both are transferred to the client machine 4 (step 3204). Next, the processing from the client machine 4 (client management requesting means 412 in FIG. 1) is accepted (YES in step 3206).
Branch), the client information transferred from the client machine 4 is registered in the client management DB 124 (step 3207). After that, the client machine 4 is notified of the normal end (abnormal end when an error occurs) (step 3208).

In this way, the client management DB1
24 and the client management means 114 and the client management request means 412 of FIG. 1 are used to limit the services that can be received by each client (for example, a service that can update data and a service that can only reference data are client machines). The security of the data managed by the server machine 1 is ensured.

FIG. 4A is a processing flow chart of the client AP version UP means 113 and FIG. 4B is a processing flow chart of the client AP normal service utilizing means 211.

FIG. 4A is a processing flow of the normal service using means 211 shown in FIG. When the process starts
The client AP version check is activated (step 4101). After that, it waits for a response from the server machine 1 (loop of steps 4102 and 4103).
Server machine 1 (client AP version U in FIG. 1
Upon receiving from the P means 113) that the processing on the server machine 1 is completed (step 4104), the normal service is activated (step 4105).

FIG. 4B shows the client AP shown in FIG.
It is a processing flow of the version UP means 113. When the process is started, the process from the client machine (normal service using means 211 in FIG. 1) is accepted (step 42).
(YES branch of 02), the client management DB 124 is searched based on the requested client machine name and existence check is performed (step 4203). If the client exists (YES branch of step 4204), the version of each service obtained at the time of existence check is compared with the latest version of each service managed by the client AP management DB 122 (step 4205). . If they do not match (YES branch of step 4206), the latest client AP is transferred from the client AP 123 on the server machine 1 to the client machine, and the client management DB 124 is updated (step 42).
07). After that, the client machine is notified of normal termination (abnormal termination when an error occurs) (step 4).
208).

In this way, the client AP management D
B 122 and client management DB 124, client AP version UP means 113 and normal service using means 211 of FIG.
It is possible to easily prevent a system failure due to version mismatch.

As described above, the client application management system according to the present embodiment accurately manages the version management of the client AP on both the server machine 1 and the client machine and the management of the client machine that uses the service of the server machine 1. By registering the client AP in the server machine 1 and systematizing registration of the client machine, system failure due to version mismatch is prevented, data destruction is prevented by client configuration management, and a series of releases after client application development The work (from the developer to the user) can be drastically reduced.

In the above description, the client machine for the developer and the client machine for the administrator are separate machines, but the present invention is not limited to this, and the client shared by the developer and the administrator is used. You can also configure the machine. That is, the client machine is provided with the normal service using means 211, the client AP registration requesting means 312, the client management requesting means 412, the storage means for storing the client AP, the version UP client AP 323 and the input / output device. be able to. This is the second aspect of the present invention.

In the above description, the number of server machines is one, but the present invention is not limited to this, and can be applied to the case of a plurality of server machines. In this case, the client AP registration means 112 and the client A
P version UP means 113, client management means 1
14, each client machine that receives the service has the identification information of the specific server machine that includes the client AP management DB 122, the client AP 123, and the client management DB 124. Can receive service. This is the invention of claim 3.

[0049]

According to the present invention, the version management of the client AP on both the server machine and the client machine and the management of the client machine using the service of the server machine are accurately performed, and the client AP is registered in the server machine. By systematizing work and client machine registration, system failure due to version mismatch is prevented, data destruction is prevented by client configuration management, and a series of release work after client application development (until the developer reaches the user) This has the effect of making a significant reduction.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a client application management system according to an embodiment of the present invention.

FIG. 2A is a configuration diagram of a client AP management DB 122, and FIG. 2B is a client AP registration request unit 312.
Is a flow chart of the client AP registration means 112.

3A is a configuration diagram of a client management DB 124, FIG. 3B is a flowchart of a client management request unit 412, and FIG. 3C is a flowchart of a client management unit 114.

4A is a flow chart of a normal service using means 211, FIG. 4B is a client AP version UP means 11 FIG.
3 is a flowchart of FIG.

[Explanation of symbols]

 1 server machine 11 processing unit 12 storage unit 111 normal service providing unit 112 client AP registration unit 113 client AP version UP unit 114 client management unit 121 normal service DB 122 client AP management DB 123 client AP 124 client management DB 2 client Machine (general) 21 Processing unit 22 Storage unit 211 Normal service using means 223 Client AP 23 Input / output device 3 Client machine (developer) 31 Processing unit 32 Storage unit 312 Client AP registration means 323 Version UP client AP 33 Input / output device 4 Client Machine (Administrator) 41 Processing Unit 42 Storage Unit 412 Client Management Request Means 43 Input / Output Device

Claims (5)

[Claims] 1. A client application storage means for storing the latest version of an application used by a client, a client application management database for storing client application information of the client application, and a client application developed by a developer. Client application registration means for registering the client application information in the client application management database and the client management database for storing the client information of the client receiving the service, and the client information of the client receiving the service for the client management. A client who registers and manages in a database A server machine including a client management means and a client application version upgrade means for transferring the latest version of the client application to the client in response to a request, and the client application version upgrade means, and the developed client application and its client application information. A client machine for a developer, which has a client application registration requesting means for transferring to a machine and making a registration request, and an administrator having a client management requesting means for transferring a client information of a client to a server machine and making a registration request. A client application management system having a client machine. 2. The client application management system according to claim 1, further comprising a client machine for a developer / administrator, which has a client application registration requesting means and a client management requesting means. 3. The client application management system according to claim 1, wherein the client machine has an identifier of a server machine that manages the client application. 4. The client application management according to claim 1, wherein the client application information includes a service name which is an identifier of the client application, version information, update date and time, and available client information. system. 5. The client information includes a client machine name which is an identifier of the client, a service name which is an identifier of a client application used by the client, version information, an update date and time, and a service use such as OS of the client. The client application management system according to claim 1, 2 or 3 or 4, further comprising client type information indicating the above difference.