JPH05342175A - Distributed property managing system - Google Patents

Abstract

PURPOSE:To easily manage the substance of property by purposes by separating the management of common property in a distributed processing system into the property substance and profile information and preventing the secondary storage device of a terminal controller from being huge by centralized management. CONSTITUTION:A terminal controller 1 to control plural work stations 3-5 is provided with a virtual library 2 which is composed of only the profile information such as the existent place or name of the property substance and is not equipped with the property substance, and the property substance is separately stored in libraries 6-9 on the respective work stations 3-5. With the virtual library 2 of the terminal controller 1 as a base, the property substances in the libraries 6-9 on the respective work stations 3-5 can be freely accessed. In the case of new preparation, the management can be simplified and the number of times for transferring the property substances can be reduced by registering them on the prepared libraries of the work stations.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a distributed asset management system, and more particularly to a terminal controller for controlling a plurality of workstations in a distributed processing system, which consists only of profile information indicating the name and location of an asset and has no asset entity. The present invention relates to a distributed asset management method in which a virtual library is provided, and asset entities are distributed and stored in libraries on individual workstations.

[0002]

2. Description of the Related Art Conventionally, a common asset management method in a distributed processing system composed of a plurality of workstations is such that all asset entities and profile information for managing them are displayed on a terminal controller for controlling a plurality of workstations. The centralized management method was common.

[0003]

In the above-mentioned conventional asset management method, since there is only one library for storing the asset entity, the assets are managed according to the purpose, or the assets are managed by changing the security level for each library. However, there is a problem that the secondary storage device of the terminal controller becomes excessive when the amount of assets increases.

An object of the present invention is to provide a decentralized asset management system which does not require a large secondary storage device in the terminal controller even when the amount of assets increases and which can be managed separately by avoiding concentration of assets. It is in.

[0005]

According to the distributed asset management system of the present invention, a terminal controller for controlling a plurality of workstations in a distributed processing system has an asset entity consisting only of profile information indicating the name and location of the asset. There is no virtual library, asset entities are distributed and stored in libraries on individual workstations, and when a new asset that is commonly used in the system is created, the asset entity is created in the library on the created workstation. And the profile information is registered in the virtual library on the terminal controller, and at the time of referencing / updating / deleting the asset, the location of the asset entity is searched from the profile information in the virtual library on the terminal controller and the work requested from that library Transfer it to the station, If it is positive, the modified asset entity is written back to the library of the original workstation and the profile information of the virtual library is modified. If it is deleted, the asset entity is deleted from the workstation library where the asset entity existed. At the same time, the profile information of the virtual library is also deleted.

[0006]

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

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention.

In the distributed asset management system of this embodiment, as shown in FIG. 1, in a distributed processing system composed of workstations 3 to 5 and a terminal controller 1 for controlling them, the terminal controller 1 stores the assets. It has a virtual library 2 which consists only of profile information indicating names and locations and does not have an asset entity, and the asset entity is a library 6 on each workstation 1-3.
9 are distributed and stored.

When a user newly creates and registers a common asset such as a program using this system, for example, if the workstation 4 creates the common asset and issues a registration instruction, the asset entity becomes the workstation. While being registered in the designated library 7 or 8 of 4, the registration instruction is transferred to the terminal controller 1 and profile information (created date, name, location of the asset entity, etc. is shown to the virtual library 2 on the terminal controller 1). Information) is registered. The same is true when registered from another workstation 3 or 5, the asset entity is stored in the library 6 or 9, respectively, and the profile information is registered in the virtual library 2 on the terminal controller 1. Since newly created assets are likely to be used frequently at the place where they are created, registering them in the library of the workstation thus created simplifies management and at the same time registers and uses them. It is possible to reduce the number of transfers in.

Next, a case of referring / updating / deleting an already registered asset entity will be described. In the case of reference, when the name of the asset entity is designated from an arbitrary workstation, the designation is transferred to the terminal controller 1 and the profile information in the virtual library 2 is searched. If the specified name exists, the location of the asset entity (workstation I
D) and the information such as the library name are acquired, and the corresponding library of the corresponding workstation is accessed based on the information, and the corresponding asset entity is taken out from there. If the requesting workstation and the workstation in which the asset entity exists are different, the asset entity is transferred to the requesting workstation via the terminal controller 1.

In the case of updating, as in the case of reference, the asset entity is taken out, and after the updating process by the user is completed, the asset entity in the library of the workstation from which it is taken out is replaced with the updated contents, and the terminal controller is also used. The relevant profile information (information such as version number and update date) in the virtual library 2 on 1 is rewritten.

In the case of deletion, the asset entity is taken out in the same manner as in the case of updating, and after the user's confirmation is requested, the corresponding asset entity is deleted from the library of the workstation from which it is taken out by the deletion confirmation instruction. At the same time, the corresponding profile information is deleted from the virtual library 2 on the terminal controller 1.

FIG. 2 is an explanatory diagram showing an example of the configuration of profile information in the virtual library 2 on the terminal controller 1. The profile information includes a serial number (Seq. NO.) As shown in FIG. 2, an asset entity name, a workstation ID (location of the asset entity),
In addition to information such as library name, version number, and creation date, supplementary information such as update date, creator name, and updater name can be managed.

[0014]

As described above, in the distributed asset management system of the present invention, the terminal controller has only a virtual library consisting only of profile information, and the asset entity is distributed to the libraries on each workstation. Therefore, it is possible to manage each library in accordance with the purpose, and even if the amount of assets increases, the assets do not concentrate on the terminal controller, so there is no need to enlarge the secondary storage device of the terminal controller.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an exemplary embodiment of the present invention.

FIG. 2 is an explanatory diagram showing an example of the configuration of profile information in the present embodiment.

[Explanation of symbols]

 1 Terminal Controller 2 Virtual Library 3-5 Workstation 6-9 Library

Claims (1)

[Claims] 1. A terminal controller for controlling a plurality of workstations in a distributed processing system has a virtual library which is composed only of profile information indicating the name and location of an asset and has no asset entity, and the asset entity is an individual workstation. Stored in the above library in a distributed manner, and when a new asset commonly used in the system is created, the asset entity is stored in the created library on the workstation and the profile information is a virtual library on the terminal controller. Register with
When referring / updating / deleting an asset, the location information of the asset entity is searched from the profile information in the virtual library on the terminal controller and transferred to the workstation requested from that library. In the case of modification, the modified asset entity is transferred. To restore the original workstation library again, modify the profile information of the virtual library, and in the case of deletion, delete the asset entity from the workstation library where the asset entity existed and also delete the profile information of the virtual library. A decentralized asset management method.