JPH04102151A - Information distributing method for decentralized network system - Google Patents

Abstract

PURPOSE:To improve efficiency for managing information by automatically distributing the resource information of a software to be presented on a network simultaneously with release. CONSTITUTION:When the bugging of the software is discovered in a work station 7, a bugging mail is prepared to register it on release service 3, and the bugging mail is transmitted through paths P1 and P2 to the release service 3 by mail service 5 so as to check whether required information is described or not. The release service 3 refers to a transmitting destination list 18 on a release range designation table prepare when releasing the software through a path P3 by the mail service 5 and distributes the bugging mail to the users of the software described in the transmitting destination list 18. Thus, labor can be saved when distributing the resource information.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a method for distributing resource information in a distributed network system.

[Conventional technology]

In a decentralized network system in which multiple information processing devices such as workstations and computers are connected via a local area network, and multiple local area networks are further connected via communication lines, new software is created. If a bug is discovered in the software, this information is distributed to each area via the local area network as IJ IJ-space information or bug information. Based on this information, for example, software installation or software modification is performed on each workstation.

[Problem to be solved by the invention]

However, in conventional network systems, when distributing this information, there is no unified management of release information, and the information is not always distributed to the users who are supposed to receive it. There was no guarantee that it would be done. For example, because software is distributed or bug information is distributed in each local network, resource information may not be transmitted to other local area networks, or even if it is transmitted to other local area networks, resource information may be electronically distributed for a certain period of time. Some users missed the information because it was only posted.

An object of the present invention is to perform unified management of resource information such as IJIJ-space information and bug information, and to reduce the effort involved in distributing resource information.

[Means to solve the problem]

In order to achieve the above object, the information distribution method in a decentralized network system of the present invention includes the following steps when distributing resource information from an information processing device connected to the decentralized network system to other information processing devices via the network: The resource information destination is registered in advance in the release service, and each time the resource information is distributed, the resource information is sent to the target information processing device by e-mail by referring to the destination registered in the pre-distribution lease service. It is characterized by

[Effect]

In the present invention, when resource information such as release information and bug information is distributed to other information processing devices, this information is first sent to the release service. In the release service, the destination of resource information is registered in advance, and this destination is referenced and the necessary resource information is notified by e-mail to the target information processing device via the network.

〔Example〕

DETAILED DESCRIPTION OF THE INVENTION Hereinafter, features of the present invention will be specifically described based on examples with reference to the drawings.

FIG. 1 shows a configuration diagram of a network system to which the information distribution method of the present invention is applied.

As shown in FIG. 1, the network system of this embodiment includes release services 3, 4, mail services 5.6, workstations 7.8.9.10, and communication services connected to each communication network 1.2. Service 1
It consists of 1.12. Each communication network 1.2 constitutes a local area network, and each communication network 1.2 is connected by a communication service 11.12.

The mail service 5.6 is for sending and receiving e-mails between devices connected to the communication network 1.2, and basically provides a service with a conventional e-mail system. That is, the content of the e-mail is sent to the specified address.

As shown in FIG. 2, the release service 3 includes a release range specification table 13 that stores information on which file service the released software is actually on.
, a storage device 14 that stores the contents of received mail, a control device 15 that controls writing and reading from and to the release range specification table 13 and the storage device 14, and is connected to a communication network 16.

The procedure for releasing software information in the network system shown in FIG. 1 will be described with reference to FIG. 3.

First, the user creates software to be released on the workstation 7 (step 10).
1). The user creates a release email to register it on the release service 3 (step 102).
. Figure 4 shows an example of a release email. The release email 17 includes the name of the software, the release source, the person in charge of the release, an explanation of the contents of the software, and the hardware I! on which the software is used. Information necessary for the release, such as the environment, software usage fee, software release destination, etc., is entered in each item column 17a to 17g. Note that the software release destination is entered only at the -th release or when the release destination is changed.

Release email 17 created on workstation 7
is sent as an e-mail by the mail service 5 to the nearest release service 3 via routes PI and P2 (step 103). The release mail 17 sent to the release service 3 is checked to see if necessary information is written on the release service 3 (step 104). This check, in the simplest example,
For example, each item column 17 to 17 of release email 17
This is done by detecting whether any character string is written in g. Furthermore, it may be detected whether the written character string matches data that is registered in advance and may be used.

After checking the release email 17, it is determined whether the release is the first release or not (step 1).
05), that is, it is determined whether the software is already registered in the release range table, and the release range specification table 13 (second
(see figure), a destination list 18 for the software as shown in FIG. 5 is created (step 106). This destination list 18 describes the correspondence between software names and destinations of the software. The release service 3 distributes the release mail 17 as an e-mail via the route P3 by the mail service 5 to the users of the software listed in the destination list 18 (see FIG. 5) (step 107). In addition, at the time of the second and subsequent releases such as version upgrades, the release range specification table 13 created at the -th release
(Step 108), a release email is distributed to software users and related parties (Step 1
07).

Next, the procedure for transmitting bug information in the network system shown in FIG. 1 will be described with reference to FIG. 6.

First, when a user discovers a software bug on a workstation (step 201), the user creates a bug mail to register it on the IJ service 3 (step 202).

FIG. 7 shows an example of the bug mail 19. Bug Mail 19 contains information necessary for bug notification, such as the name of the software, the release source, the person in charge of the release, the hardware environment in which the software is used, an explanation of the content of the bug, the cause of the bug, and countermeasures. 19a-19g are filled in. The created bug mail 19 is sent by the mail service 5 to the release service 3 via routes PI and P2 (
Step 203). The bug mail 19 sent to the release service 3 is checked on the release service 3 to see if it contains the necessary information (step 2).
04).

This check is performed in the same way as the release email described above. After checking the bug mail 19, the release service 3 uses the mail service 5 to send the destination list 1 on the release range specification table 13 (see Figure 92) created at the time of software release via route P3.
8 (see FIG. 5), the bug mail 19 is distributed to the users of the software listed in the destination list 18 (step 206).

In addition, in each of the above-mentioned embodiments, the case where software or bug information is released was explained as an example.
The objects to be released are not limited to these, but any object that can be used as a workstation resource may be used. For example, in addition to software, document files, data files, etc. can be released, and in addition to bug information, maintenance information, etc. may also be released.

Moreover, in the above-mentioned embodiment, the 51st! Software or bug information has been released based on the destination list shown in I. However, using the installation map, which is a correspondence table between the software and the workstations on which it is installed, the software or bug information should be sent to the workstation where the software is installed. - You can also send a smail or bug mail.

〔Effect of the invention〕

As described above, according to the present invention, resource information such as software release information and bug information provided on a network is automatically distributed at the same time as the software is released.

Therefore, the effort required to distribute resource information is greatly reduced, and the efficiency of information management is improved. Furthermore, since the release service retains information on past releases and information on bug discovery, it is possible to avoid missing information, delays, etc., and to improve work efficiency. Furthermore, the history of the software can be preserved by accumulating release emails or bug emails.

[Brief explanation of drawings]

FIG. 1 is a configuration diagram of a network system to which the information distribution method of the present invention is applied, FIG. 2 is an explanatory diagram showing a configuration example of a release service used in the network system shown in FIG. 1, and FIG. Figure 1 is a flowchart showing an example of the software release procedure in the network system, Figure 4 is an explanatory diagram showing an example of a release email used to distribute release information, and Figure 5 is an IJ
An explanatory diagram showing an example of a destination list used by the IJ-S service to determine the IJ-Smail distribution destination, FIG. 6 is a flowchart showing an example of the IJ-Smail procedure for bug information, and FIG. FIG. 2 is an explanatory diagram showing an example of a bug mail used for distributing bug information. 1.2: Communication network 3.4: Release service 5.6; Mail service 7 to 10: Workstation 11.12: Communication service 13: Release range specification table 14: Storage device 15: Control device 16: Communication network 17: Release email 18: Recipient list back email

Claims (1)

[Claims] 1. When distributing resource information from an information processing device connected to a decentralized network system to other information processing devices via the network, the destination of the resource information is registered in advance in the release service, and the resource information is distributed to other information processing devices via the network. 1. An information distribution method in a decentralized network system, characterized in that resource information is notified to a target information processing apparatus by e-mail by referring to a destination registered in the release service for each distribution.