JPH0454634A - Software resources distribution management system - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a software resource distribution management system that distributes various software resources distributed from hosts and terminals according to distribution conditions.

[Conventional technology]

Conventionally, as described in the host computer system or terminal system, the identifier of the target terminal system into which software is to be installed is recorded in the provision medium, and when software resources are downloaded, the download control of the host computer system and terminal system is performed. There is a way to check the identifier of the terminal system in which the function is installed and execute the download only when there is a match. As a result, the provided software is provided only to the terminal system based on the software usage contract.

Furthermore, Japanese Patent Application Laid-Open No. 1-245346 describes a method of distributing a program while checking its versigon number.

As described above, there are a variety of distribution methods, including one that manages distribution according to contract details, and one that manages distribution using information unrelated to the contract, such as a virgin number.

In systems that perform such distribution, distribution conditions are uniformly determined for each system. For example, as shown in FIG. 2, when a program or map 3 is distributed from a host 2 to a terminal 1, the distribution methods of the distributing host and terminal 2 are A and B, respectively.

In the C method, each system distributes software only by this distribution method.

[Problems to be Solved by the Invention] In the above conventional technology, when software such as a program is distributed from a host to a terminal, the distribution conditions are uniformly determined, and the user can select various distribution methods or There is a problem that a combination of methods cannot be specified.

For example, as shown in FIG. 2, a system that supports method A can only be distributed using method A, and the user is A.

There is a problem in that it is not possible to freely select methods B and C, or to request distribution using both methods A and B.

In addition, since distribution to all network system hosts and terminals is managed by one host, there is a problem in that the load of distribution management processing is placed on the other hosts.

An object of the present invention is to provide a software resource management system that allows a user to freely specify a distribution method for each distribution item.

[Means to solve the problem]

In order to achieve the above object, in the present invention, in a software resource distribution management system that distributes software resources from an upper system to lower systems connected thereto, distribution control information corresponding to software resources is stored in the upper system. and a means for distributing software resources according to the distribution control information.

[Effect]

A distribution management table in which a user defines a distribution method for each distribution item is managed by the host or terminal that executes the distribution.

When a request is made to distribute a program, the host or terminal executing the distribution controls the distribution of the program according to the distribution method defined in the distribution management table, so the user can freely choose the distribution method. When performing distribution, the distribution management table and distribution items are distributed as a set, and the distribution destination host or terminal is requested to distribute to the terminals, etc. that they manage. There is no need to manage the distribution of

〔Example〕

Hereinafter, one embodiment of the present invention will be described in detail based on the drawings.

FIG. 1 is an overall configuration diagram showing an embodiment of the present invention. The terminal device 101 is a management terminal, and inputs a distribution management table indicating the program to be distributed, the system that has been generated or has undergone system integration, and the distribution method required at the time of distribution, and inputs it into the databases 401 and 402 managed by the host system 201. accumulate. A database 401 stores distributed items such as programs and systems to be distributed, and a database 402 stores a distribution management table.

The host system 201 distributes programs and systems according to the contents of the distribution management table stored in the database 402.

In FIG. 1, from the host system 201 to the terminal system 1
03-a, b, C, a, 8. Instead of distributing directly to f, the host system 201 requests distribution to the host system 202 or terminal system 102 and
- An example of distribution to a, b, c, d, e, and f is shown.

The terminal system 102 is a distribution terminal, and is a terminal system that distributes programs and systems. The host system 201 is connected to the host system 202 and the terminal system 102.
The distribution destination terminal of each system (host system 202
are terminal systems 103-a, b, c, terminal system 10
2 distributes necessary distribution items (programs, systems, etc.) and distribution management tables defined for each distribution item to the terminal systems 103-d, e, f).

The host system 202 stores the received programs and systems in the database 411 and stores the received distribution management table in the database 412. Similarly, the terminal system 102 stores each piece of information in databases 421 and 422. Thereafter, the host system 202. The terminal system 102 distributes programs, systems, and distribution management tables to the terminal system 103 according to the distribution management table. The terminal system 103 that has received the distribution loads the program or system or performs different redefinition for each terminal system to make the program or system usable. Further, the distributed management table is accumulated in the database 432 of each terminal system, and the programs, systems, etc. that each terminal system currently has are managed by this database 432. what if.

If there are programs, systems, etc. that are no longer used in the terminal system, delete them and at the same time delete the information in the corresponding management table. Furthermore, if a management table for the same distribution exists at the distribution destination before distribution, the distribution destination system updates the management table to the newly sent management table.

FIG. 3 is a diagram showing a distribution management table before distribution stored in the database 402 of FIG. 1.

Program A and System B are programs that perform generation and system inch graying.

It is a system. The structure of this management table consists of an attribute type and an attribute value indicating a distribution method for each distribution item.

FIG. 4 explains the meanings of various attribute values (attribute values) defined in the management table of FIG. 3. In this way, the values entered for each attribute are different and are used during distribution. Further, there are types of attributes other than those in this embodiment, and the present invention does not care about the types of attributes.

The distribution method of each distribution item in FIG. 3 will be explained. The distribution process explained next is 202.10 in Figure 1.
Distribution is performed from 2 to 103. These distribution management tables may be input at the same time as the distribution items are input, or the distribution management tables may be input after the distribution items have been distributed.

Distribution is performed according to the attribute type and attribute value in the distribution management table. The distribution method differs depending on the attribute type, for example, as follows.

Distribution destination attribute: The distribution object is distributed only to the distribution destination indicated by the attribute value.

Distribution quantity attribute: Do not distribute more than the value indicated by the attribute value 0 For example, if the attribute value is 5, it means that the distribution will be made to only 5 places and will not be distributed to more than 6 places.

Distribution destination attribute: Means that distribution will start after the date indicated by the attribute value.

Application date attribute: Indicates the date by which the user at the distribution destination will replace the old distribution with the new distribution. This attribute is useful when you want to replace all systems at once at the same time; this attribute is not directly related to the distribution method. It simply sends the value of this attribute to the distribution destination.

Version attribute: Indicates the version number of the distribution. If the distribution destination has the same distribution (identified by the distribution base), if the version number of the distribution is newer than the version number of the distribution, distribute the distribution.

Distribution system (in this example, 201 and 2 in Figure 1)
02.102), control is performed according to the various attributes (distribution methods) as described above.

Next, distribution of program A will be explained using the management table of FIG. 3 and FIG. 5. FIG. 5 is a flowchart showing the distribution process of program A.

The distribution mortar is specified in the management table of program A, and a check is made to see if it is after the distribution mortar. The check is performed immediately after starting up the system (501). If it is after the distribution date, distribution will be executed according to the distribution number. First, check whether the number of distributed items is 0 (502
), if it is O, distribution ends because no more distribution is possible. If the distribution frequency is 0 or more, the program becomes ready for distribution, and if there is a distribution request from the distribution destination wS, the program A will be distributed (503). Then subtract 1 from the number of distributed items (504)
If the number of distributed items reaches O, the distribution ends, and if it is not 0, the distribution request for all ws items is awaited (505).

After distribution, on the WS side, the program A is updated by the user after the application date.

Furthermore, distribution of system B will be explained using the management table of FIG. 3 and FIG. 6. Figure 6 shows system B
3 is a flowchart showing the distribution process of FIG.

The distribution mortar is specified in the management table of system B, and a check is made to see if it is after the distribution date. The check is performed immediately after starting up the system (601). If it is after the distribution date, it becomes ready for distribution, and if there is a distribution request from the distribution destination WS (602), and if the name of the distribution requested WS is among the distribution destinations in the management table (603), System B will be distributed. (604).

If not, the distribution is refused (605). Processing continues in this manner until the distribution host finishes operating.

In this way, in this embodiment, distribution attributes can be specified for each distribution item, and management can be executed in accordance with the user's system. In addition, there is a distribution management table for distributed items at the distribution destination, and by collecting the distribution management table, it is possible to know the distribution status of which programs have been distributed to which systems.

In addition, in this embodiment, as shown in FIG. 1, the host system 201 distributes the distribution object and the distribution management table as a set to the host system 202 and the terminal system 102, and the distribution management table is distributed to these systems. Since the request for distribution is based on the host system 201, distributed processing can be performed without placing a load on a single host system 201.

〔Effect of the invention〕

According to the present invention, a system administrator can define distribution attributes indicating distribution methods for various distribution items from a management terminal, thereby allowing a user to freely select distribution.

[Brief explanation of drawings]

FIG. 1 is an overall configuration diagram showing an embodiment of the present invention, FIG. 2 is a diagram showing a conventional distribution method, FIG. 3 is a diagram showing the format of a distribution management table, and FIG. 4 is an attribute diagram in FIG. 3. 5 is a flow chart showing the distribution process of program A, and FIG. 6 is a flow chart showing the distribution process of system B. 101...Terminal system (management terminal), 102...
Terminal system (distribution terminal), 103... terminal system, 201, 202... host system. Figure 1 Figure 1 Collection of Figures Figure 1

Claims (1)

[Scope of Claims] 1. A software resource distribution management system that includes an upper system and a lower system connected to the upper system, and distributes software resources from the upper system to the lower system, wherein the software resource is distributed to the upper system. 1. A software resource distribution management system comprising: means for storing distribution control information corresponding to the distribution control information; and means for distributing the software resource according to the distribution control information. 2, comprising a higher-level system, a first lower-level system connected to the higher-level system, and a second lower-level system further connected to the first lower-level system, from the higher-level system to the second lower-level system; A software resource distribution management system for distributing software resources, comprising means for storing distribution control information corresponding to the software resource in the first lower system, and means for distributing the software resource according to the distribution control information. A software resource distribution management system characterized in that the distribution control information and the software resources distributed from the upper system are stored in the storage means and distributed to the second lower system by the distribution means.