JPH10289145A - Resource sharing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a means capable of freely giving names for resources developed in respective systems without unifying rules and sharing individually developed system resources without restrictions even in the other system relating to the sharing of the resources at the time of connecting plural computer systems. SOLUTION: This resource sharing system for which the plural systems are connected by a communication network and the resources utilized in the respective systems are shared among the systems is constituted of a conversion procedure part 5 provided in at least one system for converting resource names in the respective systems in correspondence, a storage part 2 for managing the resource names in the respective systems in correspondence among the systems and a registration procedure part 1 for inputting the resource names in the respective systems and registering the resource names corresponding to the conversion in the storage part.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to sharing resources when a plurality of computer systems are connected.

[0002]

2. Description of the Related Art In recent years, with the spread of client / server systems, different systems have been connected by a line or the like, and resources (databases, applications, etc.) individually owned by the respective systems have been used mutually.

[0003] Applications and databases developed in each system are given symbols or names indicating or identifying their contents. For example, a name such as "SEISAN-XX" is given for a production application, and "KEIRI-YY" is given for an accounting application.

[0004] However, such naming is generally set independently on the development side for convenience in development and operation and system maintenance for each system.
At that time, the relationship with the name in other systems was not considered.

FIG. 8 shows an example in which a plurality of systems are connected via a line, and is a schematic diagram of the systems and a network.
In the figure, 10 indicated by a bold frame indicates one system,
Reference numeral 11 denotes a communication control unit, and reference numeral 12 denotes an operating system (hereinafter, abbreviated as OS). 14 is an application, 15 is a database, 16 is a terminal, 1
7 is a communication line. The letters attached to the above symbols are used to identify each system.

In the case of the above system combination, the system 10
The application 14A developed in A is given a name "PR", and the database 15A is given a name "DB". On the other hand, the application 14B developed by the system 10B is given a name "group", and the database 15B is given a name "data".

[0007]

As described above, the resources used in each system are often individually designed for the purpose of use on the installation side of the system.
Due to restrictions on the size of the computer and hardware resources, there are restrictions on the naming of databases and applications to be developed. For example, "alphanumeric and up to 8 digits"
Or, in Japanese, only "Katakana" is used, and there is a problem that the character types and the number of characters that can be used are limited.

Therefore, when sharing resources between systems connected by a network as shown in FIG. 7, "unification of names" is required. As a second specific example, there is no duplication in naming.

When a name is changed in order to share a resource once developed and named in the system, it is necessary to recompile an application related to the resource whose name has been changed and reorganize a database.

The present invention has been made in view of the above points, and is an invention created by the present invention. A name for a resource developed in each system can be freely named without unifying rules, and a system resource developed individually can be used for another system resource. It is an object to provide means that can be shared without restriction even in a system.

[0011]

The above-mentioned object is achieved by the present invention having the following construction. FIG. 1 is a principle diagram for explaining the configuration of the present invention.

A resource sharing system in which a plurality of systems are connected by a communication network and resources used in each system are shared between the systems. The resource sharing system is provided in at least one system, and a resource name in each system is made to correspond. Conversion procedure unit 5 for conversion, and storage unit 2 for managing resource names in each system in association with each other
And a registration procedure unit 1 for inputting a resource name in each system and registering the resource name corresponding to the conversion in the variable storage unit. Further, the storage unit 2 stores all the resource names in each system. The ledger section 4 to be registered and the processing area section 3 to which the commonly used resource names have been transcribed. Further, the configuration of the conversion procedure section 5 is output by the processing area section 3 as resource names for each system. A conversion unit 6;
A ledger management unit 7 for transferring resource names from the ledger unit 4 to the processing area unit 3.

[0013]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 2 is an overall schematic diagram of a system to which the present invention is applied. In the system and network schematic diagram shown in FIG. 8, a name conversion device 13A of the present invention is provided between a communication control unit 11A and an operating system 12A in a system 10A. It was arranged,
Other symbols are the same as those described in FIG.

Referring to FIG. 2, the system 10B is changed from a "group" which is an application 14B in the system 10B.
The protocol when using the database 15A in A will be described with reference to FIG.

FIG. 7 shows a TCP / IP protocol (Tran
Smmission Control Protocol-
FIG. 7 is an explanatory diagram of a protocol at the time of access taking Internet Protocol (Internet Protocol) as an example, where the name used by the application 14B on the right end of the figure is “data 1”, and the name of the database 15A on the left end of the figure is “DB-
1 ". The one described in the center of the figure is a database access command (SQL: St).
structured Query Language). (1) The CONNECT command is issued from the system 10B, and the application 14B of the system 10B requests the use of the database 15A of the system 10A.
At this time, the application 14B notifies that it is being used under the name "data 1". (2) The processing result of the CONNECT instruction is notified from the system 10A. (3) Issue a SELECT instruction from the system 10B,
The application 14B of the system 10B makes a data search request for the data “DB-1” of the database 15A of the system 10A. (4) The system 10A notifies the result of the SELECT instruction and, if the operation is normally completed, notifies search data. (5) The DISCONNECT command is issued from the system 10B, and the application 14B of the system 10B transmits the data “DB-
Request the end of use of "1". (6) The processing result of the DISCONNECT instruction is notified from the system 10A.

Next, a detailed description will be given with reference to FIGS. FIG. 3 is an explanatory diagram of the configuration of the name conversion device, which discloses details of the name conversion device 13 shown in FIG.

The name converter 13 has three functions as shown. The first function is a preset function of the conversion table creation unit 131, and the correspondence between names used in each system is registered in the memory 132.

The second function is a conversion table holding function, which is a memory 132 mainly including the conversion ledger 202 and assisting the high-speed conversion table, which will be described in detail with reference to FIG.
The last third function is a conversion function of the conversion unit 133,
Reception control unit 301 for receiving a conversion request co-command
A conversion ledger access management unit 304 that manages access to the conversion ledger 202; a high-speed conversion table access management unit 303 that manages access to the high-speed conversion table 201; Conversion control unit 302 that activates one of access management units 303
It is composed of

In the above configuration, the names of the resources used in each system are indicated by lines or terminals 16 (not shown).
Is input to the registration reception unit 102 by the
01 is stored in the conversion ledger 202 in the state shown in FIG.

FIG. 4 is a diagram showing an example of the layout of a conversion ledger and a high-speed conversion table.
This is a case where the resource names related to (B, C) are registered. In FIG. 4, the conversion correspondence is held in a state of being classified into two groups. Two applications and one database are registered in the group-1.
The application (type: APL) has the name “PR-A1” in system A, the name “group A1” in system B, and the name “application A” in system C.
1 ". Similarly, the database (type:
DB), the name in the system A is "DB-1", the name in the system B is "Davy 1", and the name in the system C is "search-1". Since the group-2 has the same configuration, the description is omitted.

The high-speed conversion table 201 is classified into two areas: a group development area 2011 and an individual area 2012. That is, the conversion ledger 20 is displayed in the group development area 2011.
2 is transcribed, and a database (type: DB) commonly used from the group 2 of the conversion ledger 202 is transcribed in the individual area 2012.

FIG. 5 shows a process of accessing the conversion ledger 202 and the high-speed conversion table 201 in the conversion unit 133. That is, FIG. 5 is a processing flowchart of the conversion ledger and the high-speed conversion table. Step S1: The conversion request signal is an SQL command (FIG. 7).
), Received by the reception control unit 301, and notified to the conversion control unit 302.

Step S2: The conversion control unit 302 activates the high-speed conversion table access management unit 303, first searches the high-speed conversion table 201 for the request name, and if successful, proceeds to step S3. Branches to step S5.

Step S3: The detected data is in the individual area 201
If it has been detected in the group development area 2011, the flow branches to step S8.
Branch to 4.

Step S4: The storage positions of the names of the detected data are exchanged, and the flow branches to step S8. Step S5: The conversion control unit 302 activates the conversion ledger access management unit 304, causes the conversion ledger 202 to search for the request name, shifts to step S6 if detected, and branches to step S7 if not detected.

Step S6: The name of the data detected in the conversion ledger 202 is transferred to the individual area 2012 of the high-speed conversion table 201, and the flow branches to step S8. Step S7: Since the request name is not registered in the memory 202, an error is notified to the request source.

Step S8: The resource name data corresponding to the detected request name is output to the request source. Next, a search state in the group expansion area 2011 in the high-speed conversion table 201 will be described.

FIG. 6 is an explanatory diagram of the retrieval state of the high-speed conversion table. In the figure, reference numeral 20 denotes an address in a pointer section, and reference numeral 21 denotes a table section in which resource names in respective systems are registered in the same column. .

(1) In the initial state, the ten applications of the system A assign "PR-A1" (from address 100) and "PR-A2" (address 20), respectively.
0), ..., "PR-A10" (address 10
00), and ten applications of the system B are registered with names of “group A1”, “group A2”,..., “Group A10”, respectively, and ten applications of the system C are further registered. The applications are “Application A1”, “Application A2”,.
Registered in the table section 21-1 under the name of "application A10", the pointer section 20-1 has (100, 200,...,
1000).

(2) When “Group A4” is notified as a request name from the system B, the high-speed conversion table access management unit 303 uses the table unit 2 based on the pointer unit 20-1.
A search is made in the second column 1-1 (resource name corresponding to system B). Then, since the above-mentioned "group A4" can be searched from the position from the address 400, it is found that the resource name in the system A is "PR-A4".
A4 "is output to the system B. In order to search for the resource name once searched in the next search in as short a time as possible, the address of the pointer section 20 is replaced, and the address 400 is entered at the top. When this update is performed, the pointer unit 20-2 sets (40
0, 100, 200,..., 1000).

(3) When registering a new case name in the table unit 21, a definition table for conversion is created in advance,
For example, it is read from the terminal device 16 and rewritten to the least frequently used resource (PR-A10 at the address 1000).
Subsequently, the pointer unit 20 is set to (1000, 400, 10
0, 200,..., 900).

Although the embodiment of the present invention has been described in detail above, in the embodiment of the present invention, the name conversion device is provided in the system on the shared resource supply side. The arrangement is not limited to this, and it can be installed in any system connected to the communication line or as a dedicated system, and furthermore, it can be arranged in a distributed manner at a plurality of locations .

As a memory applied to the conversion apparatus of the present invention, a large-capacity rewritable or write-once storage medium can be used for the conversion ledger regardless of whether it is portable or fixed. The conversion table is not limited to the system memory as long as the conversion table is high speed, and a memory corresponding thereto can be used.

The amount of data arranged in the conversion ledger and the high-speed conversion table is not particularly limited, and can be specified by the initial value of the system or by the user.

[0035]

According to the present invention, since there is no need to convert the names of various resources, there is no need to limit the naming convention in each system, and it is not necessary to recompile applications and reorganize the database. Therefore, there is an effect that the man-hour for system development can be significantly reduced.

Further, there is an effect that it is possible to easily combine different systems represented by the client / server system. In addition, the effect of being able to operate with high-speed conversion according to the frequency of use of request names from other systems is remarkable.

By using the group development area and the individual area for the high-speed conversion area, the effect that the speed can be further increased is remarkable.

[Brief description of the drawings]

FIG. 1 is a principle diagram illustrating a configuration of the present invention.

FIG. 2 is an overall schematic diagram of a system to which the present invention is applied.

FIG. 3 is an explanatory diagram of a configuration of a name conversion device.

FIG. 4 is an example of an arrangement of a conversion ledger and a high-speed conversion table.

FIG. 5 is a processing flowchart of a conversion ledger and a high-speed conversion table.

FIG. 6 is an explanatory diagram of a search state of a high-speed conversion table.

FIG. 7 is an explanatory diagram of a protocol at the time of access.

FIG. 8 is a schematic diagram of a system and a network.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Registration procedure part 2 Storage part 3 Processing area part 4 Ledger part 5 Conversion procedure part 6 Conversion part 7 Ledger management part 10 System 11 Communication control part 12 Operating system (OS) 13 Name conversion device 14 Application (APL) 15 Database (DB) 16 terminal 17 communication line 20-1, 20-2, 20-3 pointer unit 21-1, 21-2, 21-3 table unit 101 creation control unit 102 registration reception control unit 131 conversion table creation unit 132 memory 133 Conversion unit 201 High-speed conversion table 202 Conversion ledger 301 Reception control unit 302 Conversion control unit 303 High-speed conversion table access management unit 304 Conversion ledger access management unit 2011 Group development area 2012 Individual area

Claims (5)

[Claims] 1. A resource sharing system connected to a plurality of other systems and sharing resources with the plurality of other systems, wherein a resource name in the own system is associated with a resource name in the plurality of other systems. A storage unit for storing and storing, and a conversion unit for mutually converting resource names based on the contents stored in the storage unit; and inputting a resource name in each system, and storing the resource corresponding to the conversion in the storage unit. A resource sharing system having a registration procedure unit for registering a name. 2. The resource sharing system according to claim 1, wherein said storage unit comprises a ledger unit for registering all resource names in each system and a processing area unit to which a commonly used resource name is transcribed. system. 3. The resource sharing system according to claim 2, wherein the configuration of the processing area unit is divided into groups and individual areas. 4. A conversion unit configured to output a resource name as a name for each system in the processing area unit, and a ledger management unit transferring the resource name from the ledger unit to the processing area unit. 2. The apparatus according to claim 1, wherein
And a resource sharing system according to claim 2. 5. A computer-readable storage medium connected to a plurality of other systems and storing a computer program for sharing resources with the plurality of other systems, wherein a resource name in the own system and the plurality of other systems are stored. A conversion function unit for mutually converting resource names based on the content stored in a storage unit that stores the resource names in the system in association with each other; A computer-readable storage medium storing a computer program having a registration function unit for registering a conversion-compatible resource name.