JP2005309843A - Asset distribution system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an asset distribution system by which a load burdened on a network is lowly retained in asset distribution. <P>SOLUTION: A PC (Personal Computer) 20 for distribution acquires a file 11 for distribution of interest from an asset management server 10. An asset reflection means 21 compresses and divides an asset prepared by compiling the acquired file 11 for distribution of interest and prepares a file 26 for distribution of interest. The file 26 for distribution of interest is transmitted to a business server 30 and a client PC group 40. The business server 30 and the client PC group 40 combine and elongate the received file 26 for distribution of interest received by asset reflection means 31, 41. A performing asset is updated by a newly distributed asset. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an asset distribution system, and more particularly to an asset distribution system that distributes software assets (resources) to a plurality of computers connected via a network.

  In general, a plurality of PC terminals are connected to a network such as an in-house LAN. In such a case, if each PC terminal performs update work such as version upgrade of software assets (hereinafter also simply referred to as assets) such as application programs of each PC terminal, it takes a lot of time and effort to process. Need. Conventionally, an asset is placed on a server, and the asset is distributed (transferred) to each PC terminal from the server via a network to reduce the processing load of the update work.

  As a technique for managing assets of a plurality of PC terminals when there are a plurality of PC terminals connected to the network, there is a technique described in Patent Document 1. In this technique, asset information of each PC terminal can be updated with the latest information by automatically acquiring asset version information from a plurality of PC terminals.

Further, as a technique for managing software assets by a software development support system, there is a technique described in Patent Document 2. In this technique, software assets are stored in a plurality of asset storage locations. When a software asset stored in any asset storage location is updated, the update information is distributed to other asset storage locations that store the same software asset logically. In this technique, software assets stored and stored in a plurality of asset storage locations are centrally managed in this way, thereby making it possible to efficiently search and reference software assets.
JP 2001-290937 A JP-A-7-141169

  However, in the method of placing assets on the server, there is a problem that when the assets are transferred to the PC terminal, a load is applied to the network and the distribution time becomes long. In Patent Documents 1 and 2, it can be confirmed that the versions are synchronized only for the same logical asset. In a two-layer system (hierarchical system) composed of a server and a client, Since the asset is logically different between the server asset and the client asset, the server asset and the client asset cannot be synchronized.

  The present invention has been made to solve the above-described problems of the prior art, and an object of the present invention is to provide an asset distribution system that can reduce the load on the network during asset distribution.

  In addition, the present invention provides an asset distribution system that can achieve version synchronization between a server asset and a client asset after asset distribution in a two-layer structure system after achieving the above object. The purpose is to do.

  In order to achieve the above object, an asset distribution system of the present invention includes: a compression unit that compresses software assets stored in a storage device using a predetermined algorithm, and stores the compressed software assets in the storage device; A dividing unit that reads the compressed software asset, divides the read compressed software asset by a predetermined size to generate a plurality of divided files, and stores the plurality of divided files in a storage device; A distribution device comprising: a transmission unit that reads and transmits a divided file from a plurality of computers, each of which is connected to the distribution device via a network, receives the divided file from the distribution device, and receives the divided file Split file receiver for storing the split files in the storage device and multiple split files corresponding to itself When the divided file receiving unit accumulates all in the storage device, the plurality of accumulated divided files are combined, and a decompression unit that decompresses the file obtained by the combination using an algorithm reverse to the predetermined algorithm; And a plurality of computers including an updating unit that updates software assets that are in operation with software assets expanded by the expansion unit.

  In the asset distribution system of the present invention, the assets distributed to each of a plurality of computers are compressed and divided, so that the load on the network when distributing the assets can be reduced.

  In the asset distribution system of the present invention, the plurality of computers may be divided into a plurality of layers to constitute a layered system. For example, one of a plurality of computers can be configured as a business server that operates a basic application, and the other computer can be configured as a client in charge of a user interface or the like.

  In the asset distribution system of the present invention, it is preferable that the distribution device assigns the same version information to each of the software assets transmitted to a plurality of computers. In this case, after distributing the assets, it is possible to check whether the versions are synchronized by checking the version information in operation on each of the plurality of computers. In particular, when multiple computers are configured as a layered system, the assets distributed to each computer are logically different assets. Even in such a case, the same version information is given to each asset. Thus, it is possible to check whether or not a version mismatch has occurred in the layered system.

  In the asset distribution system of the present invention, each of the plurality of computers includes a version information acquisition unit that acquires software software version information that is in operation, and the distribution device includes version information acquisition units of the plurality of computers. When the acquired version information does not match each other, it is preferable to redistribute software assets. By redistributing assets, the versions of assets distributed to each computer can be matched.

  In the asset distribution system of the present invention, it is preferable that the update unit backs up and holds the asset before the update in a storage device when updating the asset, and the update unit operates from the distribution device at the present time. When the version information of the previous asset is received, the operating asset is preferably updated with the asset backed up in the storage device. In this case, when a defect or the like is found in the updated asset, it becomes easy to restore the asset before the update.

  Since the asset distribution system of the present invention compresses and divides assets for distribution, the load on the network during asset distribution can be kept low. Further, when the same version information is given to the asset to be distributed, it is possible to synchronize the versions among the assets distributed to a plurality of computers.

  Hereinafter, with reference to the drawings, the present invention will be described in more detail based on exemplary embodiments of the present invention. FIG. 1 is a block diagram showing the configuration of the asset distribution system according to the first embodiment of the present invention. The asset distribution system 100 includes an asset management server 10, a distribution PC 20, a backbone server 30, and a client PC group 40. The asset management server 10, the distribution PC 20, and the backbone server 30 are each configured as a computer system such as a personal computer or a workstation. The client PC group 40 is configured as a set of a plurality of computer systems each sharing a predetermined function.

  The backbone server 30 and the client PC group 40 are configured as a two-layer structure system based on a client-server system. More specifically, the backbone server 30 is configured as a business backbone server having a backbone application that actually performs business, and each PC in the client PC group 40 has a client interface that has an input screen application and the like and provides a user interface. Configured as a terminal. Each means in the asset management server 10, the distribution PC 20, the backbone server 30, and the client PC group 40 is realized by a program executed on a computer system.

  The asset management server 10 includes a distribution target file 11 and a version information property file 12. The distribution target file 11 is a file serving as a basis for assets distributed to the backbone server 30 and the client PC group 40, respectively. The version information property file 12 stores version information of distributed assets.

  The asset management server 10 transmits the distribution target file 11 to the distribution PC 20 in accordance with a request from the distribution PC 20. The distribution PC 20 includes an asset reflection unit 21, a version check unit 22, a compile directory 23, a division directory 24, and a distribution folder 25 configured in the storage device. The asset reflecting means 21 creates a distribution target file 26 based on the distribution target file 11 received from the asset management server 10, and sends the created distribution target file 26 to each PC of the backbone server 30 and the client PC group 40. Distribute (forward).

  The core server 30 includes asset reflection means 31, version check means 32, and an execution environment directory 33, a backup directory 34, a first temporary area 35, and a second temporary area 36 that are configured in the storage device. The plurality of computers constituting the client PC group 40 are respectively an asset reflecting means 41, a version checking means 42, an execution environment directory 43, a backup directory 44, a first temporary area 45, and a storage area. A second temporary area 46 is provided. In the core server 30 and the client PC group 40, the assets that are in operation stored in the execution environment directories 33 and 43 are updated by the asset reflecting units 31 and 41, respectively.

  The version check unit 42 of the client PC group 40 transmits the version information stored in the version information property file 47 to the version check unit 32 in the backbone server 30. The version check means 32 of the backbone server 30 compares the version information received from the client PC group 40 with the version information stored in the version information property file 37 in the backbone server 30, and compares the comparison result with the distribution PC 20. It transmits to the version check means 22. The version check unit 22 executes a process of synchronizing the assets of the core server 30 and the assets of the client PC group 40 based on the received comparison result.

  FIG. 2 is a flowchart showing a processing procedure when distributing assets to the core server 30 and the client PC group 40. Upon receiving the asset transmission request from the distribution PC 20, the asset management server 10 transmits the distribution target file 11 corresponding to the requested asset to the distribution PC 20 (step S21). The distribution PC 20 stores the received distribution target file 11 in the storage device by the asset reflection means 21, creates a file compressed and divided based on the stored distribution target file 11, and creates the compressed / The divided files are transmitted to the core server 30 and the client PC group 40 (step S22). The core server 30 and the client PC group 40 update the assets based on the received files by the asset reflecting means 31 and 41, respectively (steps S23 and S24).

  FIG. 3 is a flowchart showing the detailed procedure of the file creation / distribution process in step S22. The asset reflection unit 21 requests input of a file division size suitable for the network load capacity (step S301), and checks whether the input file division size is within a specified range (step S302). When the file division size is within the specified range, the asset reflection unit 21 sets the file division size to the file division size input in accordance with the request in step S301 (step S303). When the file division size is not within the specified range, the asset reflection unit 21 displays an error (Step S304) and ends the process.

  The asset reflection unit 21 reads the distribution target file 11 received from the asset management server 10 from the storage device (step S305), and is corrected in the assets currently operating on the core server 30 and the client PC group 40. It is confirmed that bugs and added functions are reflected in the distribution target file 11 (step S306). The asset reflecting means 21 stores the distribution target file 11 in the compile directory 23 to update the compile environment (step S307), and executes compilation (step S308).

  The asset reflection unit 21 determines whether an error has occurred in the compilation in step S308 (step S309). When a compilation error occurs, the asset reflection unit 21 displays an error (step S310), and ends the process in order to have the asset reviewed again. When the compilation error does not occur, the asset reflection unit 21 stores the distribution target execution file obtained by the compilation in the division directory 24 (step S311).

  The asset reflection unit 21 reads the distribution target execution file from the division directory 24, performs compression processing, and writes the compressed distribution target execution file to the division directory 24 (step S312). This compression processing is performed on the entire function or on a subsystem basis for each function. Further, the asset reflection means 21 reads the version information corresponding to the distribution target file 11 from the version information property file 12 of the asset management server 10 (step S313), and increments the version information (adds 1) (step 1). S314), the version information is stored in the division directory 24. For example, when the asset version information of the core server 30 and the client terminal group 40 at the present time indicates “2”, the asset reflection unit 21 reads the corresponding version information “2” and adds 1 to the version information. Information “3” is stored in the division directory 24. The version information incremented by the distribution PC 20 is stored in the version information property file 12 of the asset management server 10.

  The asset reflecting unit 21 divides the file stored in the division directory 24 and having a size equal to or larger than the file division size set in step S303 with the file division size (step S316). At this time, the asset reflection unit 21 simultaneously creates tools for combining (replacement) the divided files by the asset reflection units 31 and 41 of the core server 30 and the client PC group 40. The asset reflection unit 21 determines whether an error has occurred in the division process (step S317). If the asset reflection unit 21 determines that an error has occurred in the division process, the asset reflection unit 21 displays an error (step S318) and ends the process. If the asset reflecting means 21 determines that the error has not occurred and the dividing process has been normally completed, the asset reflecting means 21 stores the divided file in the distribution folder 25 (step S319). The asset reflection means 21 sends the distribution target file 26 including the divided, compressed and divided assets stored in the distribution folder 25, version information, and a tool for combination, to the core server 30 and the client PC group 40. (Step S320).

  FIG. 4 is a flowchart showing the detailed procedure of the file replacement process in step S23 in the backbone server 30. The file replacement process in step S24 in the client PC group 40 is executed in the same procedure as the replacement process in the backbone server 30 shown in FIG. The backbone server 30 replaces the files in the execution environment directory 33 based on the files transmitted from the distribution PC 20 according to the processing procedure described below.

  The asset reflection unit 31 receives the distribution target file 26 that is divided and transmitted from the distribution PC 20 (step S401), and determines whether all the divided files have been received (step S402). The asset reflecting unit 31 repeatedly executes step S401 until all the divided files are received while accumulating the received files in the storage device. When all the divided files are received, the asset reflection unit 31 copies the execution environment AP file currently running from the execution environment directory 33 to the backup directory 34 to perform backup (step S403).

  The asset reflecting means 31 activates a tool for replacing assets created on the distribution PC 20 (step S404). By starting this tool, the asset reflection unit 31 copies the execution environment AP file stored in the execution environment directory 33 to the first temporary area 35 (step S405). At this time, the asset reflection unit 31 decompresses / decompresses a file existing in a compressed (archive) state in the execution environment directory 33 and copies it to the first temporary area 35.

  The asset reflection unit 31 combines the transmitted files divided from the distribution PC 20 with a tool, decompresses and expands the combined files, and stores the obtained file in the second temporary area 36. (Step S406). The asset reflecting means 31 copies the file stored in the second temporary area 36 by overwriting to the first temporary area 35 (step S407), and confirms whether or not the copy has been performed normally (step S408). . The asset reflection unit 31 displays an error (step S409) and ends the process when the overwrite copy in step S407 is not performed normally.

  The asset reflection unit 31 performs a compression process on the uncompressed file stored in the first temporary area 35, and sets the file stored in the first temporary area 35 to a compressed state (step S410). The asset reflection unit 31 confirms whether or not the compression process has been completed normally (step S411). When the compression process has been completed normally, the file stored in the first temporary area 35 is transferred to the execution environment directory 33. Copying is performed (step S412). When the compression process does not end normally, the asset reflection unit 31 displays an error (step S413) and ends the process. The asset reflection unit 31 updates the version information stored in the version information property file 37 with the version information received from the distribution PC 20 (step S414), and clears the first temporary area 35 and the second temporary area 36. (Step S415), and the process ends.

  FIG. 5 is a flowchart showing a procedure for checking the version of the asset between the client and the server. When the respective assets are updated in the core server 30 and the client PC group 40 in steps S23 and S24 of FIG. 2, the version check means 42 receives the version information from the version information property file 47 in each PC of the client PC group 40. The acquired version information is transmitted to the backbone server 30 (step S51).

  In the core server 30, the version check unit 32 acquires version information from the version information property file 37 (step S52), and performs a matching check between the acquired version information and the version information received from the client PC group 40 (step S52). S53). When it is determined that the two do not match as a result of the matching, the version check means 32 generates an error code and transmits an error code indicating that the two do not match to the distribution PC 20 (step S54). When the version check unit 22 of the distribution PC 20 receives an error code from the core server 30 indicating that the version information of the asset in the core server 30 and the version information of the asset in the client PC group 40 do not match, the asset management The server 10 is requested again to transmit the asset, and the asset is updated again from step S21 (FIG. 2) (step S55).

  In the present embodiment, the distribution PC 20 compresses the distribution assets, divides the compressed assets into a plurality of divided files, and then transfers the divided files to the backbone server 30 and the client PC group 40, respectively. The core server 30 and the client PC group 40 that have received the divided files accumulate all of the divided files addressed to themselves, and combine the divided files to generate a compressed asset. Decompress and expand to update the asset in operation with the newly received asset. With such a configuration, the asset distribution system 100 can reduce the network load when updating the assets of the core server 30 and the client PC group 40.

  In this embodiment, the distribution PC transmits version information to the core server 30 and the client PC group 40 at the time of asset distribution, and the version information in the client PC group 40 and the core server 30 are updated after the asset is updated. Check against the version information inside. In the asset distribution system 100, the distribution PC 20 redistributes the assets when the version information does not match, so that the assets of the core server 30 and the assets of the client PC group 40 can be kept synchronized. In the client-server two-layer structure system, the assets of the core server 30 are logically different from the assets of the client PC group 40, but in this embodiment, the same version information is given to both. Assets can be synchronized between the core server 30 and the client PC group 40.

  FIG. 6 shows a procedure for returning the assets of the core server 30 and the client PC group 40 to the assets before the asset update after the asset update. For example, when a serious problem is found in the assets distributed by the distribution PC 20, the assets of the core server 30 and the client PC group 40 are converted to the assets of the previous generation by the procedure shown in FIG. We cope by returning to.

  When returning the assets of the core server 30 and the client PC group 40 to the previous generation, the distribution PC 20 reads the version information of the distributed assets from the version information property file 12 of the asset management server 10 (step S601). The received version information is decremented (1 is subtracted) to correct the version information (step S602). The distribution PC 20 transfers the decremented version information to the backbone server 30 and the client PC group 40 (steps S603 and S609). For example, when the version information of the assets of the core server 30 and the client terminal group 40 currently indicates “3”, the distribution PC 20 reads the version information “3” and decrements the version information “2”. The data is transferred to the server 30 and the client PC group 40, respectively.

  In the core server 30, upon receiving the decremented version information, the asset reflection unit 31 creates a list of files stored in the backup directory 34 (step S604), and creates a list of files stored in the execution environment directory 33. Create (step S605). The asset reflection unit 31 compares the file list created in step S604 with the file list created in step S605, and calculates a difference between the two (step S606). The asset reflection unit 31 performs difference replacement from the backup directory 34 to the execution environment directory 33 according to the difference calculated in step S606 (step S607). When this difference replacement is completed normally, the asset reflection unit 31 performs a process of replacing the version information in the version information property file 37 with the version information transferred in step S603 (step S608).

  When each PC in the client PC group 40 receives the decremented version information, the asset reflection unit 41 creates a list of files stored in the backup directory 44 in the same procedure as steps S604 to S606 in the core server 30. (Step S610), a list of files stored in the execution environment directory 43 is created (Step S611), and a difference between the two is calculated (Step S612). Further, the asset reflection unit 41 performs difference replacement from the backup directory 44 to the execution environment directory 43 in accordance with the difference calculated in step S611 (step S613). When the difference replacement ends normally, the version information property file 47 The version information is replaced with the version information transferred in step S609 (step S614).

  In the core server 30 and the client PC terminal group 40, when the asset is returned to the asset of the previous generation, the version information is matched according to the procedure similar to the procedure shown in FIG. When the distribution PC 20 receives that the version information stored in the version information property file 37 of the core server 30 and the version information stored in the version information property file 47 of the client PC group 40 do not match, the asset management server 10 is requested to transmit the distribution target file 11 corresponding to the previous generation asset, and the previous generation asset is distributed to the core server 30 and the client PC group 40, respectively.

  Although the present invention has been described based on the preferred embodiment, the asset distribution system of the present invention is not limited to the above embodiment, and various modifications and changes can be made to the configuration of the above embodiment. Changes are also included in the scope of the present invention.

1 is a block diagram showing a configuration of an asset distribution system according to an embodiment of the present invention. The flowchart which shows the asset distribution processing procedure in an asset distribution system. The flowchart which shows the detailed procedure of a file creation / distribution process. The flowchart which shows the detailed procedure of a file replacement process. The flowchart which shows the processing procedure of the version check of the asset between a client and a server. The flowchart which shows the procedure at the time of returning to the asset before asset update after asset update.

Explanation of symbols

100: Asset distribution system 10: Asset management server 11: Distribution target file 20: Distribution PC
21: Asset reflection means 22: Version check means 23: Compilation directory 24: Division directory 25: Distribution folder 26: Distribution target file 30: Core server 31: Asset reflection means 32: Version check means 33: Execution environment directory 34: Backup directory 35, 36: Temporary area 37: Version information property file 40: Client PC group 41: Asset reflection means 42: Version check means 43: Execution environment directory 44: Backup directory 45, 46: Temporary area 47: Version information property file

Claims (6)

A software unit stored in the storage device is compressed by a predetermined algorithm, the compressed software asset is stored in the storage device, and the compressed software asset is read from the storage device, and the read compressed A distribution apparatus comprising: a division unit that divides a software asset at a predetermined size to generate a plurality of division files; and stores the plurality of division files in a storage device; and a transmission unit that reads and transmits the division file from the storage device; ,
A plurality of computers each connected to the distribution device via a network, receiving the divided file from the distribution device, and storing the received divided file in a storage device; When the divided file receiving unit accumulates all of the corresponding divided files in the storage device, the plurality of accumulated divided files are combined, and the file obtained by the combination is an algorithm opposite to the predetermined algorithm An asset distribution system comprising: a plurality of computers each including an expansion unit that expands in step 1; and an update unit that updates software assets that are in operation with software assets expanded by the expansion unit.   The asset distribution system according to claim 1, wherein the plurality of computers are divided into a plurality of layers to constitute a layered system.   The asset distribution system according to claim 1, wherein the distribution device assigns the same version information to each of software assets transmitted to a plurality of computers. Each of the plurality of computers further includes a version information acquisition unit that acquires software asset version information in operation.
4. The asset distribution system according to claim 3, wherein the distribution device redistributes software assets when the version information acquired by each of the version information acquisition units of the plurality of computers does not match each other.   The asset distribution system according to claim 3 or 4, wherein the updating unit backs up an asset before the update in a storage device when the asset is updated.   The update unit according to claim 5, wherein the update unit updates the operating asset with the asset backed up in the storage device when receiving the version information of the previous asset currently operating from the distribution device. Asset distribution system.

Images