JPH06149737A - Device for operation control and computer system equipped with the same - Google Patents

Abstract

PURPOSE:To improve the efficiency of processing, control the system, and facili tate the maintenance while basically employing decentralized processing which is advantageous to processing, the decentralization of a load, the decentralization of danger in a system-down state, etc., when information of the system using a computer is controlled. CONSTITUTION:Plural control units are constituted by putting every optional number of client EWSs, having input parts, display parts, and memory parts, together, and each of the control units is provided with a control server 30 which controls users, respective EWSs, application programs, etc., and also provided with a master server 23 which has a control function in a higher hierarchy, thereby forming a three-hierarchy control structure on the whole.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention comprises a device for constructing a network of a system including a large number of processing devices having an input unit, a display unit, a storage unit and an arithmetic processing unit, and managing the information, and the device. Computer system.

[0002]

2. Description of the Related Art Conventionally, centralized processing and distributed processing are known as information processing methods using a computer. For centralized processing, a large-sized host computer is placed in the center, a large number of terminals having input / output units are connected to the host computer, and input / output is performed by the terminals.
All data are collected in the host computer and are processed centrally in the host computer. On the other hand, in distributed processing, a plurality of relatively small computers are connected to each other via a network, and each works by an application program to perform processing.

[0003]

According to the above-mentioned centralized processing using the host computer, the processing efficiency is high and the operation management of the system and information can be collectively and centrally performed in the center. There are advantages. However, it requires a large-sized host computer, especially when the number of terminals increases, the load on the host computer increases, which requires a very large processing capacity, which is disadvantageous in terms of cost, etc. The impact when the system goes down is also significant.

On the other hand, according to the distributed processing, the processing and the load are distributed, which is advantageous in cost and the like.
The danger is also dispersed.

However, it is difficult to comprehensively manage the whole computer by simply connecting a large number of computers to each other via a network. Further, even if a computer for overall management is provided and connected to each computer, it is not possible to process it when management data inquiries are concentrated on the computer for management.

When a new program is registered or a program is revised due to version upgrade, etc.,
In the conventional distributed processing method, it is necessary to perform the above-mentioned registration, revision, etc. processing on each of a large number of target computers, and it is also necessary to check the operating status and malfunction of each computer. The management and maintenance of was very troublesome.

In view of the above-mentioned circumstances, the present invention is based on distributed processing in which a large number of computers are connected, which is advantageous in terms of cost and risk distribution, but also has the advantages of a centralized processing system. It is an object of the present invention to provide a device for operating information management, which can improve the efficiency of system management and simplify system management and maintenance, and a computer system equipped with this device.

[0008]

In order to achieve the above object, a first gist of the present invention is to provide a large number of processing devices having an input section, a display section, a storage section and an arithmetic processing section, and data storage,
A device for operating and managing information by configuring a network with various function servers having functions such as data output, and managing a plurality of sets by grouping an arbitrary number of the above-mentioned processing devices into one management unit. Configure a unit and manage each user by managing users, managing each processing unit, managing application programs, managing usage time, managing function servers, and connecting each processing unit in a group to the network. In addition to providing a control server having the function of managing the above, the user management, the above-mentioned processing devices, the application program management, the usage time management, the function server management and A function that manages the network connection of each control server It is provided with a master server that you want to.

The second gist is a device for operation management having the above-mentioned configuration, a large number of client workstations as a processing device having an input unit, a display unit, a storage unit and an arithmetic processing unit, and data storage. , A computer system configured with a workstation having various function servers having functions such as data output.

[0010]

According to the above configuration, the control server takes charge of the processing performed by the application program in each of the processing units for each management unit, so that the processing is efficiently performed and the load on the master server is reduced. In addition, new registration and revision of the program are reflected from the master server to each control server, and the overall operation management is performed collectively and centrally.

[0011]

Embodiments of the present invention will be described with reference to the drawings.

FIG. 1 schematically shows a computer system including an operation management mechanism and an apparatus for the operation management according to an embodiment of the present invention. In the figure, reference numeral 1 denotes a client workstation as a processing device, which has an input section, a display section, a storage section and an arithmetic processing section, and is formed by an EWS (engineering workstation). Hereinafter, this EWS 1 will be referred to as a client EWS.

A large number of clients EWS1 are divided into a plurality of groups, each of which is a group. Each of these groups becomes a management unit (hereinafter referred to as an island) 5 on the network, and an EWS having a control server for each island 5 (hereinafter referred to as a control EWS).
2) is provided. Furthermore, an EWS that has a master server as a higher-level server than the control server (hereinafter referred to as the master EWS)
3 is provided. This master EWS 3 has a console.

At least one master EWS 3 is provided in the entire system and is always in operation. The control EWS 2 is provided for each island 5. And the client EW on each island 5
S1 and control EWS2 are connected by a communication line, and each control EWS2 and master EWS3
Are connected by a communication line to form a network, and the master EWS 3, control EWS 2, and client EWS 1 form a three-level management system.

In FIG. 1, for simplicity, the client E
Although only two islands 5 each including two WS1 are shown, the number of client EWS1s on the island 5 is the control EWS.
The number of islands 5 can be arbitrarily increased without exceeding the processing capacity of 2.

In addition, each island 5 has an EWS having various function servers having functions such as data storage and data output.
6, 7, 8 and 9 (hereinafter referred to as function EWS) are provided. For example, CA running on client EWS1
D A server that receives a request from an application and has a function of storing CAD data and a function of submitting CAD data to the application, as well as a request from an application that operates on the client EWS1, waits for plotter control and output requests. Plot server with each function of matrix management and conversion to output format, calculation server with high-speed calculation processing function, host server with database management function and plot output service function that the conventional host computer has , The above-mentioned functions EWS6, 7, 8 and 9 exist. These functions EWSs 6 to 9 are provided for multiple islands 5
Each control EWS2 is connected to each control EWS2 by a communication line so as to be shared with each other, or is connected to a specific control EWS2 by a communication line so as to be dedicated to one island 5.

FIG. 2 shows an example of the hardware configuration. In this figure, three islands 5 are shown, and each island 5 is provided with one control EWS2 and one or a plurality of clients EWS1. The control EWS 2 and the client EWS 1 of each island 5 are connected to each other, and the master EWS 3 and the various functions EWS 6 to 9 are a LAN (premise information communication network) using optical fibers.
The DDI 11 is connected via a concentrator 12, a bridge / router 13, a remote bridge 14, a gateway 15, etc., and communication among them is possible.

FIG. 3 shows a logical arrangement of network constituent elements. In this figure, a portion surrounded by a one-dot chain line is a network virtual machine 20 which constitutes an apparatus for operation management.
Is. In this virtual machine 20, the master EW
On the S3 side, there is a tapper 22 and a master server 23 under the operation information management application 21, and an operation information master database common access 24 for accessing data of various tables described later.
The tapper 22 is an application having a function of monitoring the network status and detecting a server failure. An introduction management application 25 is provided for the master server 23.

The operation information management application 21
Is application software used by the administrator 26, and is the master console 3a of the master EWS3.
It operates in response to input from the system, controls information in the system, and is used for network log display, network maintenance, etc. Further, the introduction management application 25 is
This is application software that is set in the EWS when the programs as the above-mentioned various servers and clients are installed in the EWS that constitutes the system and is used by the administrator 26.

The master server 23 is used for user management and W / S (workstation) as described later.
It has various functions such as management, program management, account management, function server management and control server management. Further, the control servers 30a, 30b, 30c existing in the control EWS2 for each island mainly target the client EWS1 in the corresponding island, and perform user management, W / S management, program management, account management, function server management and It has various functions for network log management on the island.

A maintenance path of operation information is formed between the master server 23 and each of the control servers 30a to 30c as indicated by an arrow a in FIG. 3, and a new registration, a change, a deletion of a user or an EWS is performed. As for the maintenance, if the predetermined processing is performed at one place as described later, the information can be given from the master server 23 to the control servers 30a to 30c. In addition, status information indicating the operating state of each EWS is transmitted via the route shown by the arrow b in FIG. 3 to the master server 23 side and each control server 3 side.
0a to 30c and each function server 31a, 31b, 3
Communication is carried out between 1c, 131a and 131b.

An application control 32, which is an application starting menu program, is running on each client EWS1 provided in an arbitrary number on each island. The application control 32 can start the user application 33 distributed to the client EWS 1 by a simple operation by the login process by the user 35 and the program distribution function described later, and between the client side and the server side. Can be updated at. User 35
However, if login is performed using a client EWS1 on an island other than the one to which the user belongs, for example, a user 35 belonging to the island corresponding to the control server 30c uses the client EWS1 belonging to the island corresponding to the control server 30b. When the user logs in by using the control server 30b, the control server 30b discriminates this and logs in again to the control server 30c that manages the user 35 as indicated by the arrow c, thereby temporarily changing the island configuration. Then, communication with the control server 30c is enabled.

The various functions of the master server 23 and the control servers 30a to 30c and the outline of the processing contents based on the functions will be described below.

User Management As shown in FIG. 4, a login process in the client EWS1 establishes a connection state in which the client EWS1 can communicate with the corresponding control EWS2, and a logout process disconnects the connection. These processes will be described in detail later.

Further, as shown in FIG.
List display of (recognition name that virtual machine 20 identifies a user), registration of user ID, deletion or change processing, list display of accounting code (recognition code identifying a department to which a user belongs), registration of accounting code The delete or change process is performed on the console of the master EWS3. Then, in accordance with the above processing, the user table and the accounting code table in the table 41 held in the master EWS 3 are rewritten, reflected in the control server 2 in question, and provided for the control server 2. The user table A and the user table B in the table 42 are rewritten. Therefore, collective maintenance becomes possible.

Network configuration management This is related to each function of workstation management, function server management, and control server management. Figure 5
As shown in, the data of various workstations (location host name, network address, model, installed application name, etc.) are displayed on the console of the master EWS3.
Can be listed. The above server can be used to change the affiliation of the function server and maintain the program type table.

When defining, changing or removing a workstation, a control server, a function server, or a client, the operation information management application 21 or the introduction management application 25 can be used to enter the definitions. The various tables 41 of the master server 23 are rewritten. Further, the workstation table, the function server table, the program table, etc. in the table 42 held in the control EWS 2 are rewritten by being reflected in the corresponding control server when necessary.
Therefore, it is possible to add, change, or delete network components in 1
Can be easily done in place.

Program distribution This corresponds to program management. As content,
A program managed by a device for operation management and program-related files can be distributed to a target EWS. Further, it is possible to collectively revise a program by bug FIX, revise by version upgrade, register and distribute a new program.

That is, registration, deregistration, revision registration, etc. of the program are performed in the master EWS3, and the information is distributed from the master EWS3 to the operating control EWS2. On the other hand, with respect to the control EWS2 that is not operating, the program is automatically registered and revised in the control EWS2 by being distributed when the control EWS2 is restarted. Furthermore, the distribution to the client EWS1 is performed by the client EWS1.
This is done by retrieving the program from the control EWS2 when restarting.

Account management All the account information provided by the application control can be collected.
2 and the account total table held in the master EWS 3, the total contents can be displayed and printed out.

The present invention relates to each function of fault management workstation management, function server management, program management, and control server management.

As shown in FIG. 6, as a failure response, for example, a process restart, a refresh when the management table of the control server 30 has a failure, a workstation or a server when the initialization file has an error, or This includes redefining clients and defining alternate workstations in case of workstation hardware failure. Then, when the above redefinition or the like is performed, the master server 23 rewrites the workstation table, the function server table, the control server table, etc. in the table 41 and is reflected in the server,
The required items in the tables 42 to 45 of the server are rewritten. In this way, failure recovery is facilitated.

It corresponds to a network status monitoring tapper. All Es in the network
You can check whether WS is up or down. Also,
It is possible to confirm whether all control servers 30 and all function servers 31 are up or down. This will be described in detail later.

Common Processing Common processing for starting and ending the network component process and notifying the status is performed. Also, the master Q is managed. The master Q is a place for commonly storing maintenance commands issued from the master server 23 to the control server 30 when the control server is stopped, and these commands are processed when the control server is started.

Therefore, the above maintenance command is immediately given to the operating control server 30, while the operating control server 3 is stopped.
Even for 0, it is given when it is started. In this way, the reflection of the maintenance on the control server 30 is achieved, and it is possible to process with the same command system regardless of whether the control server 30 is operating or stopped. Further, it is possible to confirm the execution of the instruction, cancel the instruction, and change the order.

There is a startup server 36 for processing at startup (see FIG. 6).

Batch setting process A simple process desired to be executed collectively can be registered by the console of the master EWS3. Then, the registered collective setting process in the master server 23 is distributed to each island.

[0038] Other print amount, plot output amount, disk access volume, disk usage, etc., each function server can grasp the amount of function you are managing. In other words, as will be described later, the function EWSs 6 to 9 have the function use log tabulation tables, and the master EWS 3 also has the function use log tabulation table, which enables the usage amount to be grasped. As a result, each server is optimized. In addition, data backup and recovery are possible.

The above is an outline of the main functions and processing contents.

Further, the EWSs constituting each server and client are provided with a table for storing the data required for the above various functions and processing, and the table is as shown in FIGS. 7 to 11. There is something.

That is, FIG. 7 shows a table 41 held in the master EWS 3, which includes a user table, an accounting code table, a workstation (W / S) table, a program type table, a program table,
Collective setting processing table, account aggregation table, function usage log aggregation table, function server table, control server table, master Q (master QUE
UE), master log, etc. Then, for example, user IDs, passwords, accounting codes (department codes) for all users, and other user-related data are written in the user table, and the accounting code table stores department-related data such as accounting codes. , Required data is written in each table.

FIG. 8 shows a table 42 held by the control EWS2, which includes a user table A, a user table B, a workstation (W / S) table, a program table, a batch setting processing table, an account table, and an affiliated function server table. There is a log table in the island, a control server initial setting table, etc.
There are two types of user tables, of which the user table A is written with data about users belonging to the island 5 corresponding to the control EWS 2 and the user table B is written with data about all users.

FIG. 9 shows a table 43 held by the client EWS1, which is a client initialization table,
Introductory application table, login user profile table, etc.

FIG. 10 shows a table 44 held in the function EWS, which includes a function use log totaling table, a function server initial setting table, and the like.

FIG. 11 shows a table 45 common to each EWS, such as a machine profile table.

The above is the table held in the EWS. It should be noted that FIGS. 7 to 11 show only the main items and the items corresponding to the processing specific examples described later regarding the contents of the table.

12 to 1 show some examples of characteristic processes among various processes performed based on the above functions.
Next, referring to FIG.

User Login, User Logout The process of user login is shown in FIG. For this processing, first, the user uses the client EWS1
A user ID, a password, a project ID (development model code), and the like are input on the screen through the input unit and the display unit (step S101). In response to this, a network login request is issued from the client EWS1,
Data such as the user ID, password, project ID, and operation host ID obtained from the machine profile (in FIG. 11) are sent to the corresponding control server 30 (step S102).

Upon receipt of the above data, the control server 30 receives the corresponding user I in the user table A.
D is checked to determine whether or not the corresponding record exists (steps S111 and S112). If the corresponding record exists, the password is further checked for correctness (step S11).
3). If the password is correct, the status, operation host ID, and login time of the record are updated (step S114), and a login user profile is created from the record and sent to the client (step S115). The status is written in the island log table (step S116), and the return code (RC) is "0".
And returned to the client (step S11)
7). If the control server 30 determines that there is no corresponding record, the corresponding user ID in the user table B is checked to determine whether or not there is a corresponding record (steps S118 and S119). If the corresponding record exists, RC = y And the host ID of the belonging control server are returned to the client (step S120). If it is determined in step S113 that the password is incorrect, a return code RC = x is returned to the client (step S121), and step S11.
When it is determined that there is no corresponding record in step 9, the return code RC = z is returned to the client (step S12).
2).

The client receiving the return code RC checks the value (step S103), and when RC = 0, moves to the next process (step S103).
104), and when RC = x or z, step S101.
When RC = y, the process returns to the process of step S102 after resetting the obtained belonging control server host ID (step S105).

In this way, the user can perform the login process for the predetermined control EWS2 also by the client EWS1 on an island other than the originally belonging island.

The process of user logout is shown in FIG. 13. As this process, if the user selects the user logout menu, or if the specified time has elapsed in the application inactive state after login (step S131), the network logout is performed. A request is issued from the client, and data such as user ID and status is sent to the corresponding control server 30 (step S132). Upon receiving this data, the control server 30 updates the status of the corresponding user ID in the user table A (step S1).
41), the user status is transferred to the island log (step S142).

Then, the return code RC is returned from the control server 30 to the client, and the login user profile is deleted accordingly (step S1).
33) and display of the login request screen (step S13)
4) is performed.

Workstation Definition This process is shown in FIG. As this processing,
Using the installation management application on the workstation to be added, the operation manager uses the control server host ID to which he / she belongs (or the host ID of the control EWS itself if it is added), the program type number (N
O), the model name and the installation location are input on the screen (step S201). In response to this, the data of the workstation record for defining the workstation is given to the network and sent to the master server 23 (step S202).

In the master server 23, the record of the corresponding host ID is added to the workstation table (step S211), and at the same time, the workstation table addition information (workstation table record) is sent to the control server 30 (step S211). Step S212). Then, after the record of the corresponding host ID is added to the workstation table in the control server 30 (step S
221), the return code RC is the master server 23.
Returned to. Further, the master server 23 returns a return code RC to the corresponding host (workstation). In addition, in the case of adding the control EWS2, the processes of step S212 and step S221 are not performed.

Upon receipt of the return code, the relevant host sends its own host ID to the master server 23 to obtain the machine profile of the relevant host from the network (step S203). Accordingly, in the master server 23, the machine profile is created after the corresponding host ID is checked from the workstation table, and this and the return code R
C and C are sent to the corresponding host (step S213).

Client Definition This process is shown in FIG. The installation management application is also used for this processing, and the operation manager selects the client definition menu at the workstation to be the client (step S231). Accordingly, a client bit is set for each workstation type in the machine profile table (step S232), and a host ID, an ON bit number of the workstation, etc. for defining the workstation as a client are given to the network. The data is given and sent to the master server 23 (step S233).

In the master server 23, the designation bit of the workstation type of the corresponding host ID in the workstation table is turned on (step S).
241) together with the corresponding control server 30,
Host I as change information in workstation table
Data for each type of D and workstation is sent (step S242). Then, the control server 30 updates the workstation type field of the corresponding host ID record in the workstation table (step S251), and then returns the return code RC to the master server 23. Further, the master server 23 returns a return code RC to the corresponding host (client EWS).

Upon receipt of the return code RC, the host sends data such as host ID and application control program ID to the network to define the introduction of the application control program to the workstation (step S2).
34). In the master server 23 that received this data, the corresponding host ID in the workstation table
Introduced program ID is added to the record (step S243) and the control server 30
The data of the host ID and the additional installation program ID is sent as the change information of the workstation table (step S244). Then, in the control server 30, the installation program ID field is added with the maintenance flag ON to the record of the corresponding host ID in the workstation table (step S25).
At the same time, the relevant program type is read from the program table and the presence or absence of the program type entity is checked (step S253). If yes, it ends, but if no, save processing is called,
In response to this, the master server 23 sends the program to the storage area (step S245), and the substance of the program is acquired. Further, the return code RC is returned to the master server 23, and the return code RC is returned from the master server 23 to the corresponding host.

Subsequently, in the host, the host ID of itself is sent to the master server 23 in order to obtain the client initial setting profile of the host from the network (step S235). Accordingly, in the master server 23, the workstation type of the corresponding host ID record is checked from the workstation table, the client initial setting profile is created, and this and the return code RC are sent to the corresponding host (step S246). ).

Server Failure Detection FIG. 16 shows a failure detection process for all control servers 30, and FIG. 17 shows a failure detection process for all function servers 31. These processes are performed by the tapper 22. Be seen.

The process for detecting a failure with respect to the control server 30 is performed according to the control server table by sequentially checking the control servers 30 and requesting a response from the control server 30 whose status in the control server table is up. It is designed to detect a failure that the control server 30 that should be operating is not operating.

That is, determination of completion of check (EOF) for all control servers 30 (step S30)
If 1) is NO, it is determined whether or not the status of the unchecked control server 30 is up (UP) (step S302). If not, the process returns to step S301 and the next control server 3
Move on to 0 check. If the status is up, a signal for confirming the up status is transmitted to the corresponding control server 30 (step S303). In the control server 30 which receives this, a return code of RC = 0 is returned as a signal indicating that it is actually operating (step S311). If it is not actually running, you will not get such a return code.

Return code R in tapper 22
C is checked (steps S304, S305), RC =
If it is 0, it is operating normally, so step S
Returning to step 301, if RC = 0 is not satisfied, a warning message is output to the master log (step S306), the number of checks N is incremented (step S307), and the number of checks N is determined (step S30).
Based on 8), for example, when the number of times of determination of the number of checks is 3, the checking process from step S303 is repeated until the number of checks N is smaller than “3”, and the number of checks N becomes “3”. When it reaches, the status of the corresponding control server 30 is set to down (DN) (step S309).

The process for detecting a failure in the function server 31 is also performed in the same manner as in the case of the control server 30. That is, the processes of steps S321 to S329 are similar to steps S301 to S309 except that the target is the function server 31, and the signal for confirming the up state is transmitted to the function server 31. Return code RC
Is returned (step S341). Then, when there is a failure in which the function server 31 is not operating, the status of the function server is down. In this case, the status update information is further sent to the control server 30.
(Step S330), the control server 30 receives the request and updates the status of the corresponding server ID record in the function server table to down (step S351).

By such processing, the operating conditions of the control server and the function server can be accurately grasped.

As a specific example of management of various data using the CAD data management network, a load / replacement save process among various processes for CAD data management is shown in FIGS. 18 and 19.

The CAD data loading process shown in FIG. 18 is performed by the CAD application program. As this processing, the user inputs the CAD data name, the group name and the project name (step S401), and the CAD
CAD data server 3 to which the group name, project name and CAD data name correspond for data loading
1 is transmitted (step S402).

In the CAD data server 31 receiving this, the status of the CAD data is checked (step S411), the load information is described in the index (step S412), and the CAD data is transferred to the corresponding client. (Step S41
3).

The CAD data replacement save process shown in FIG. 19 is also performed by the CAD application program. As this process, C saved by the user
By designating the AD data name, group name and project name (step S421), C
The CA to which the group name, project name, CAD data name, and CAD data correspond to save the AD data.
It is transmitted to the D data server (step S42).
2).

In the CAD data server which receives this, the CAD data is the CA of the project under the group.
It is merged as D data (step S431).

Besides this, reference of CAD data, CAD
The CAD application program performs various processes such as data movement save and CAD data release.

In connection with the user login and logout of the security check description and the CAD data management, as described in the above-mentioned user login and logout regarding the access security check to the distributed resource, the user is the conventional computer. It performs the same function as the login check to the system by checking the login to the network virtual machine. On the other hand, regarding the access check to CAD data, which is an important resource, since the data handled at work differs for each department, it is possible to set the CAD data access authority for each island.

For example, the control server 30 shown in FIG.
The user of the island belonging to a can refer (READ) and update (WRITE) as the processing for the CAD server (group A) to the function server 31a, but the CAD
When the data (group B) is processed to the function server 31b, only reference can be performed. Further, the user of the island belonging to the control server 30b can only refer to the processing for the CAD server (group A) function server 31a, but the processing for the CAD data (group B) function server 31b is not possible. It can be referenced and updated.

In this way, the security check for the user and the security check for the resource can be performed.

[0076]

As described above, according to the present invention, an arbitrary number of processing devices each having an input unit, a display unit, a storage unit, and an arithmetic processing unit are grouped together to form a plurality of sets of management units, and each management unit thereof. By providing a control server having functions of user management, management of each processing device, management of application programs, etc., and a master server having a management function in a higher hierarchy, each control unit is managed by the control server. By managing the necessary information for each and reducing the load on the master server, the master server manages each control server to enable the collective and centralized management. For this reason, the distributed processing, which is advantageous in terms of processing and load distribution, risk distribution when the system is down, etc., is basically used, and further, processing efficiency can be improved and system management and maintenance can be simplified. It is a thing.

[Brief description of drawings]

FIG. 1 is a schematic diagram of an operation management mechanism and a computer system according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of a hardware configuration.

FIG. 3 is a diagram showing a logical arrangement of network components.

FIG. 4 is an explanatory diagram showing an example of management content.

FIG. 5 is an explanatory diagram showing another example of management contents.

FIG. 6 is an explanatory diagram showing still another example of management contents.

FIG. 7 is a chart of a table held in the master EWS.

FIG. 8 is a chart of a table held in the control EWS.

FIG. 9 is a chart of a table held in the client EWS.

FIG. 10 is a diagram of a table held in the function EWS.

FIG. 11 is a chart of a table common to each EWS.

FIG. 12 is a flowchart showing a first example of various specific processes.

FIG. 13 is a flowchart showing a second example of various specific processes.

FIG. 14 is a flowchart showing a third example of various specific processes.

FIG. 15 is a flowchart showing a fourth example of various specific processes.

FIG. 16 is a flowchart showing a fifth example of various specific processes.

FIG. 17 is a flowchart showing a sixth example of various specific processes.

FIG. 18 is a flowchart showing a seventh example of various specific processes.

FIG. 19 is a flowchart showing an eighth example of various specific processes.

[Explanation of symbols]

 1 Client EWS 2 Control EWS 3 Master EWS 5 Island (Management Unit) 23 Master Server 30 Control Server

Claims (2)

[Claims] 1. A network for a large number of processing devices having an input unit, a display unit, a storage unit, and an arithmetic processing unit and various functional servers having functions of data storage, data output, etc., for operating and managing information. The device of
An arbitrary number of the above processing devices are combined to form a plurality of management units, and for each management unit, user management, management of each processing device, application program management, and use A control server having the functions of time management, function server management, and network connection of each of the above processing units in the group is provided, and the user management is performed at a higher hierarchy than the control server. For operation management characterized by having a master server having a function of managing each processing unit, managing application programs, managing usage time, managing function servers, and connecting each control server to the network Equipment. 2. The device for operation management according to claim 1, a large number of workstations for clients as a processing device having an input unit, a display unit, a storage unit, and an arithmetic processing unit, data storage, and data output. A computer system configured with a workstation having various function servers having functions such as.