JPH0498556A - Network system - Google Patents

Abstract

PURPOSE:To attain the limited release of software by releasing the resources like the software, etc., based on the storage of an area to be released. CONSTITUTION:The software information stored in a storage 1-2 is compared with the corresponding contents of a storage of another release server 1-5 by the controller 1-1 through the communication equipments 1-3 and a LAN 1-4. In this case, the controller 1-1 specifies a server 1-5 for the comparison. If no coincidence is obtained with the contents of the storage, the software information is updated through the LAN 1-4 so that the latest content state is secured. Therefore the logical names showing the resources undergoing the limited release are unified among the releasing servers and also defined unique in each releasing server. Furthermore the correspondence is secured between the information which specifies a storing place of the resources and the information on the releasing server. As a result, the resources released to a releasing server are also released to this limited releasing server.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a system that automatically maintains a software research and development environment on a large scale or between remote locations and improves the efficiency of research and development. .

[Conventional technology]

When researching and developing software with a large number of people, files that need to be shared by multiple people are placed on a shared file server and used mutually. In larger projects, it becomes necessary to share files across multiple LANs (Local Area Networks), so a file server with the same content (shared file server) is required.
Prepare multiple copies and place them in the areas that need to be shared.

However, when modifications are made to shared files or when the number of shared files increases, it is necessary to manually update each shared file server, which requires a great deal of effort to manage the shared file servers. .

In order to solve this problem, the present inventors provided a release server in each LAN, provided a means for storing a release map representing attributes such as the location of files in this release server, and We have developed a system that includes means for transferring files to a file server, referring to a release map, and rewriting the release maps so that they match when they do not match.

[Problem to be solved by the invention]

However, with this system alone, it is difficult to change the predetermined release range.

In particular, for software development and testing, it has been difficult to limit the release of each piece of software to a specific region.

Therefore, an object of the present invention is to realize a limited release of software when automatically releasing software through a network.

[Means to solve the problem]

In order to achieve this object, the network system of the present invention has a plurality of regions and a network in each region. The present invention is characterized by comprising a release server having a control means for releasing resources such as software.

[Effect]

The operation of the present invention will be specifically explained by giving an example with reference to the drawings. FIG. 1 shows a schematic configuration of a release server used in the present invention.

The release server 1-5 includes a control device 1-1 and a storage device 1.
-2 and communication device 1-3.

The software information stored in the storage device 1-2 is sent to the communication device 1-3 and the LAN 1- by the control device 1-1.
4, it is compared with the corresponding contents of the storage of other IJ-servers. When comparing the contents, the control device 1-1 controls which IJ server is used for comparison, and if there is a difference in the contents, the L A Ni -4 to update the software information.

In this way, in the present invention, the logical names representing the limited IJ resources are unified among the releasing servers, and
It shall be unique within each IJ server. In addition, information identifying the storage location of the resource,
By associating the information of the name of the limited IJ IJ-server, you can assign IJ IJ-server to one IJ IJ-server.
J-sourced resources are similarly released to this limited IJ-source server.

〔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. 2 shows an embodiment of a network system according to the present invention.

Here, to simplify the explanation, three release servers 2-4a, 2-4b, and 2-4c are
Consider a situation where software is released for three domains D1, D2, and D3. With this assumption, software 5oftXXX is set to domain DI and 0
Let's consider a case where the release is limited to 2.

In order to implement such limited releases, each release server has a table called a release range specification table.

The release scope specification table contains a logical name indicating the resource to be released in a limited manner (in this case, software), the actual location where the resource is stored (in this case, a directory on the file server), and the list of releases to be released in a limited manner. This describes the relationship with the list of server names. 3rd
The figure shows the contents of the release range specification table.

Here, release range specification table 3-
1> 〲〇〇　 and the logical name ``5oftXXX'' are written. In this example, this is software 5
Assume that it is a logical name corresponding to ofXXX. however,
The resource name and logical name do not necessarily have to match.

This logical name must be an arbitrary name within the release server. The name must be the same among the release servers that release the resource.

The physical name corresponding to this logical name is [Re1ease-FS
]<5oftXX>, which in this case indicates the directory of the file server where this software is stored.

The next item is Release Server Names, which lists all the names of release servers that will be released in limited quantities.

The release server compares the contents of its own resources with resources with the same logical name that exist on the release servers written in the list, and always updates the contents.

For example, in the case of Figure 3, the logical name 5oftXXX is
It can be seen that it is shared between domains 01 and 02.

Therefore, software released in domain [11 with the logical name 5oftXXX will be automatically released in domain 021 through the network by comparing the contents of the resource with the logical name 5oftXXX in domain 01 and domain D2. However, domain D
The logical name 5oftXXX is not registered in the release range specification table of the IJ server No. 3. Therefore, this software will not be released to domain D3.

FIG. 4 shows the processing flow.

In this embodiment, a comparison is made between the IJ server and the corresponding resource in the release range designation table after a certain period of time to ensure that the content of the resource is up to date.

Specifically, processing is performed in the following steps.

Step 4-10: Sequentially select rows for appropriate logical names from the IJ lease range specification table.

Step 4-20: IJ in line IJ-Susa 7s1
From the name field, select an appropriate release sirnoi name in order.

Step 4-30: Compare the contents of the resource indicated by the selected release server and logical name with the contents of your own resource.

Step 4-40: Update the resources via the communication line so that the contents of the selected resources on both IJ-servers are up to date.

Step 4-50: Execute again from the beginning after a certain period of time.

Note that the resources to be released are not limited to software, but may be anything that can be sent over a network. Furthermore, the physical name indicating the location where the resource is stored need not be a directory of the file server, but may be anything that specifies the location where the resource is stored. Further, the information may be managed by being divided into two tables: logical name and physical name, and logical name and release server name.

Furthermore, it is not necessary for each release server's release range specification table to have a complete list of release server names.

It is only necessary that a bus be set between any two release servers to be accessed by the release range specification table.

This IJIJ-base range specification table can also be centrally managed by one release server. in this case,
The first release will be made to this centrally managed release server, and this release server will then release to each release server for limited release.

Release server names in the release range specification table can also be grouped. By doing this, there is no need to have a separate release server name.

〔Effect of the invention〕

As described above, according to the present invention, one resource released to one release server is automatically released only to previously registered release servers.

Therefore, simply by specifying the release server name in the release range specification table, resources are automatically released to other release servers. For example, when officially releasing software that has been tested, limited IJ IJ-
It will be officially released just by loosening the specifications. Further, the release can be stopped simply by changing the release range specification table, and the subsequent IJs will be automatically stopped. This simplifies software release work.

[Brief explanation of the drawing]

Fig. 1 is a detailed explanatory diagram of the present invention, Fig. 2 is a system diagram showing an embodiment of the invention, Fig. 3 is a diagram showing an example of a release range specification table according to the invention, and Fig. 4 is a processing flow. It is. Patent applicant: Fuji Xerox Co., Ltd. Agent: Masu Kobori 1-4) L
AN Figure 1 Figure 2 Figure 3

Claims (1)

[Claims] 1. In a network system having a plurality of regions and a network in each region, a storage means for storing the region to be released, and a control means for releasing resources such as software based on the memory in the storage means. A network system characterized by comprising a release server having: