WO2011135629A1 - 計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム - Google Patents
計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム Download PDFInfo
- Publication number
- WO2011135629A1 WO2011135629A1 PCT/JP2010/003077 JP2010003077W WO2011135629A1 WO 2011135629 A1 WO2011135629 A1 WO 2011135629A1 JP 2010003077 W JP2010003077 W JP 2010003077W WO 2011135629 A1 WO2011135629 A1 WO 2011135629A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- software
- client
- representative
- software image
- client computer
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
Definitions
- the present invention relates to a software distribution management method in a computer system and a computer system for software distribution management.
- P2P-type software programs are distributed among a plurality of clients to reduce the number of communications and the communication load between the server and the clients.
- this prior art discloses that the number of representative clients is determined so that the degree of parallelism of the software distribution process is sufficient so that the software program distribution deadline specified by the administrator is satisfied. ing.
- an object of the present invention is to provide one or both of the following two.
- the present invention provides a plurality of clients, a server including software distributed to one or a plurality of the plurality of clients, a network connecting the servers and the plurality of clients, Is provided.
- the server classifies the plurality of clients into a plurality of groups based on information from the plurality of clients, selects a representative client for each group, and distributes the software to the representative client.
- the representative client that has received the distribution of the software distributes the software to other clients belonging to the same group.
- the server outputs management display information to the management screen based on the software distribution management information.
- the software distribution from the server to the representative client may be performed in advance.
- the convenience of the software distribution management system using the representative client can be improved.
- FIG. 3 shows a flowchart for achieving the main function of the server. Part of the client information table. It is another part of the client information table. It is an example of a client information history table. It is an example of a client grouping table. It is an example of a software list table. It is an example of a software distribution priority and a redundancy coefficient value table. It is an example of a software distribution status table. It is an example of the flowchart corresponding to the process in which a server transmits software to a representative client.
- FIG. 12 shows an example of the software distribution task table. It is an example of the flowchart of a software delivery process of a representative client. It is an example of the flowchart of the reception process and installation process of a software of the request origin client of a software. It is an example of the flowchart which shows the outline
- Embodiments of the computer system according to the present invention will be described below.
- the information of the present invention will be described using expressions such as “aaa table”, “aaa list”, “aaaDB”, “aaa queue”, etc., but these information are not necessarily limited to tables, lists, DBs, queues,
- the data structure may be expressed by a data structure other than these.
- aaa table “aaa list”, “aaaDB”, “aaa queue”, etc. may be referred to as “aaa information” to indicate that they do not depend on the data structure.
- program is used as the subject.
- the program performs processing determined by being executed by the CPU using the memory and the communication port (communication control device), the CPU is used as the subject.
- the explanation may be as follows.
- processing disclosed with the program as the subject may be processing performed by a computer that executes the program.
- a part or all of the program may be realized by dedicated hardware.
- Various programs may be installed in each computer by a program distribution server computer or a storage medium.
- FIG. 1 is a block diagram of a computer system for distributing software programs from a management server computer to a client computer group.
- the computer system includes a file including a software program, a server computer (hereinafter simply referred to as “server”) 10 that manages distribution of software images corresponding to the software program to a client computer, and a plurality of client computers (hereinafter referred to as “server”). 14) are connected by a wide area network 26 such as the Internet.
- server server computer
- server client computers
- the software image corresponding to the software program includes information and / or a program for enabling execution of the software program to be installed by the client. Further, when “corresponding” is expressed for a software program and a software image, it has the above-mentioned meaning. Since the expression “software image corresponding to a software program” is long as the description in the embodiment, it may be simply expressed as “software image”. Examples of the “information for enabling execution” and / or the “program” described above are as follows.
- Software program file and its setting information Software program file and its setting information.
- the software image may be a software program file itself.
- the client may download a part or all of the files (or data) of the software program from the server 10 or other computers.
- the client may extract the software program from the data embedded in the installation program file and make it executable.
- the software image may include an identifier of the corresponding software program.
- the software image corresponding to the predetermined software program stored in the representative client and the software image corresponding to the predetermined software program stored in the distribution server may not be the same data. This is because the software image data is not particularly limited as long as a predetermined software program designated as a request source client can be installed.
- the software image corresponding to the predetermined software program stored in the first representative client and the software image corresponding to the predetermined software program stored in the second representative client may not be the same data. . This is because the software image data is not particularly limited as long as a predetermined software program designated as a request source client can be installed.
- the software image that the representative client sends to the client is not the same as the software image received by the representative client, as long as it corresponds to the same software program. Good.
- distributed refers to transferring a software image to be distributed between computers.
- An example between computers is as follows.
- “distribution” may be read as “send”, “receive”, and “forward” with the server, client, or representative client as the subject. Further, the “distributed” computer may or may not include installing the corresponding software program using the distributed software image.
- installation refers to processing that enables execution of a software program to be installed.
- An example of processing that can be executed is as follows.
- the server 10 classifies a plurality of clients into groups, and determines clients to which software images should be distributed for each group. In order to distinguish a client receiving software image distribution from other clients, the client is hereinafter referred to as a representative client.
- a client requesting a software image receives software image distribution from a representative client of the same group. In order to distinguish this client from the representative client, it is referred to as a requesting client.
- the computer system distributes the software image of the server to the representative client in advance so that the pull-type software image can be distributed at high speed in an environment where the relay server is omitted.
- This software image is formed in the representative client so that it can be transferred to another client, in other words, a temporary copy of the software image is formed in the representative client, and in other words, the software image is cached.
- the first main function is to select a software image distributed from the server to the representative client.
- the requesting client cannot receive the software image corresponding to the target software program from the representative client, the requesting client accesses the server and receives the distribution of the target software image.
- the server determines the software program characteristics and the download status managed by the server, and distributes the software image with a higher priority to the client in preference to other software images as long as the client's free disk space permits. .
- the second main function assumes the probability per unit time that the requesting client can access the software image corresponding to the target software program, and sets the representative client that stores the software image to satisfy this probability. It is to set redundantly.
- the server When the requesting client needs to distribute the software program (or software image), the server causes a plurality of clients to exist redundantly in the computer system so that the requesting client can access the representative client.
- the server selects the representative client so as to satisfy the target value. Note that the server determines the representative client by using the operating rate information of the client.
- the third main function is to perform maintenance on the arrangement of software images within the group.
- the server changes the representative client and the software image held by the representative client.
- Reference numeral 14A denotes a client whose hardware configuration is shown in detail. Other clients are similarly configured.
- Reference numeral 12 denotes a disk device which is a storage area of the server 10.
- Reference numeral 14B denotes a disk device of the client 14A. Disk devices are also connected to other clients. The plurality of clients 14 are connected to each other by a LAN 76. A client 28 for displaying server management information is connected to the server-side LAN.
- the server 10 controls communication between the disk device 12 and the memory 16 that stores the program code necessary for executing the distribution control of the software image, the processor 18 that executes the distribution control of the software, based on the program.
- An interface 22 that controls communication with the client, and a bus 24 that interconnects these elements.
- the memory 16 stores a software distribution management program 16000. When the CPU 18 executes the program, the server 10 performs software distribution management processing.
- the software distribution management process of the server 10 is achieved from a plurality of functions.
- the memory 16 is shown as a functional block diagram in which a block is assigned to each of a plurality of functions.
- the processing units (30, 32, 34, 36, 40, and 42) are included in the software distribution management program 16000.
- the description regarding each processing unit can be rephrased as the description regarding the software distribution management program 16000.
- the client information management processing unit 30 manages client information, mainly inventory information.
- the client information management processing unit includes a processing unit 30A that collects client information from the client, and a processing unit 30B that groups a plurality of clients based on the client information.
- the software information management processing unit 36 manages information on the software image of the server 10, and a priority determination processing unit for the manager to determine the priority for distributing the software image to the client for each group of clients.
- 36A and a redundancy coefficient value calculation processing unit 36B that calculates a characteristic value (redundancy coefficient value) relating to redundancy of a copy of a software image (software image cache) existing for each group of clients.
- the representative client management processing unit 32 manages a client (representative client) to which a software image is to be distributed in advance for each group of clients. Based on this priority, the processing unit 32A determines the priority of the client. And a processing unit 32B for determining a representative client.
- the communication processing unit 40 controls communication with the client, and includes a distribution processing unit 40A that performs software image distribution processing, and a result reception processing unit 40B that receives a distribution result from the client.
- the rearrangement processing unit 34 performs processing for reconstructing the arrangement of software images in the client group, and the distribution status screen display processing unit 22 executes processing for displaying a management screen on the screen display client. It is.
- the disk device 12 connected to the server includes a software image data 12A distributed from the server 10 to the client, a software program list table 12B, a client information table 12C, and a table 12D of information grouping clients.
- a software image distribution priority and redundancy coefficient value table 12E and a software image distribution status table 12F are provided.
- the client 14B includes a communication interface 50 that controls communication with the server, a disk interface 52 that controls communication with the disk difference 14B, processing for receiving distribution of software images from the server 10 or the representative client, A processor 58 for controlling the process of distributing the software image to the requesting client, a memory 60 in which a program for the process is stored, and an internal bus 56 for connecting these elements to each other.
- the memory 60 stores a client side distribution management program 64000, and the CPU 58 executes the program to realize software distribution processing on the client 14 side.
- the client-side distribution management program 64000 includes a client common processing unit 62 that implements processing common to a plurality of clients, and a representative client unique processing unit 64 that implements processing unique to the representative client.
- client common processing unit 62 that implements processing common to a plurality of clients
- representative client unique processing unit 64 that implements processing unique to the representative client.
- description regarding each process part (62, 64) can be paraphrased with the description regarding the client side distribution management program 64000.
- the client common processing unit 62 includes a client information transmission unit 62A that transmits client information to the server, a software reception processing unit 62B that receives a software image from the server 10 or the representative client, and software that uses the software image received from the representative client.
- the representative client unique processing unit 64 includes a software transmission processing unit 64A that transmits the software image received from the server 10 to the requesting client.
- the client disk 14B includes a software image data 70 received by the client, a software image distribution task table 72 from the representative client to the requesting client, and a software image transmission status table from the representative client to the requesting client. 74.
- each processing unit stored in the memory 16 and the memory 60 may be a program code. However, as described above, some or all of the processing may be replaced by hardware. Further, when considered as the storage resource of the server 10, both the memory 16 and the disk 12 included in the storage resource may be included, but either the memory 16 or the disk 12 may be included in the storage resource. Good. In this case, it can be considered that the storage resource of the server 10 stores a program and information included in the memory 16 and a table (information) included in the disk 12.
- the storage resource of the client 14A may also include both the memory 60 and the disk 14B included in the storage resource, but either the memory 60 or the disk 14B may be included in the storage resource. In this case, it can be considered that a program and information included in the memory 60 and a table (information) included in the disk 14B are stored as storage resources of the client 14A.
- FIG. 2 shows a flowchart for achieving the main function of the server 10.
- the server 10 collects client information from each of the plurality of clients 14 existing in the computer system (S200), and groups the clients 14 based on the collected information (S202).
- the server 10 determines the priority order of the software images to be distributed to the client 14 (S204), and further calculates a characteristic value (redundancy coefficient value) regarding redundancy when the software image exists in the client group (S206). ).
- the server 10 calculates priorities for a plurality of clients in each group (S208), and determines a representative client to which the software image is to be distributed (S210). Next, the server 10 distributes the software image and updates the distribution result (S212).
- the collection processing unit 30A of the client information management processing unit 30 accesses the plurality of clients 14 periodically (or repeatedly), and receives client information, mainly inventory information and performance information from the client information transmission unit 62A of each client.
- the collected information is updated and stored in the client information table 12B of the disk device 12.
- Examples of inventory information collected from the client are address information (IP address and subnet mask), disk capacity, and free capacity of each client 14. This inventory information is used for grouping the clients 14.
- the collection processing unit 30A further calculates an average operating rate of the client and registers it in the client information processing table 12C.
- the client information management processing unit 30 obtains the average operating rate as follows, for example.
- the server 10 accesses each client 14 at regular intervals, and checks whether the client is operating each time.
- the client information management processing unit 30 determines the total time during which the client 14 is operating as the connectable time, calculates the ratio of the connectable time to the total value of the client business hours, and calculates this for each client.
- the average occupancy rate For example, 12 hours from 08:00 to 20:00 is the total value of the business hours per day, and the server 10 sends a request for connection confirmation 12 times to the client 14 every hour, and the client 14 9 times. If there is a response, the daily operating rate is 0.75 (9/12).
- the client information management processing unit 30 cumulatively records the operation rate for a specified number of days in a predetermined area of the memory 16, and sets the average value of the accumulated values as the average operation rate.
- the daily operation rate for each client is stored in the client information history table (FIG. 4).
- a client information history table is also stored in the disk device 12.
- the client history table updates and stores the history of various client performances, and the average CPU usage rate, average disk I / O amount, and average network I / O amount are calculated using the average utilization rate. It is the same as the calculation method.
- the grouping processing unit 30B of the client information management processing unit 30 refers to the client information table 12C and automatically classifies the plurality of clients 14 into groups. There are the following methods.
- (E) Classify multiple clients depending on the department to which the client belongs.
- the server 14 requests the administrator to input the identification information of the department to which each client 14 belongs, and registers the input result in the client information table 12C.
- the grouping processing unit 30B registers the result of grouping a plurality of clients 14 in the grouping table 12D of the disk device 12.
- FIG. 5 shows an example of a grouping table, which includes an entry for a group name and an entry for a client belonging to the group.
- the priority determination processing unit 36A of the software information management processing unit 36 of the management server 10 determines the priority order for the administrator to distribute the software image arranged on the server 10 to the client 14 for each group of the clients 14. The priority determination process is performed.
- the priority determination processing unit 36A performs priority determination processing for a plurality of types of software programs having entries in the software list table 12B illustrated in FIG.
- the software list table 12B is stored in the disk device 12, and is referred to or updated by the software information management unit 36. There are the following methods for setting priorities in software programs.
- the higher priority is set for a software program corresponding to a software image that has a large capacity and takes a long time to transfer.
- the priority of the server 10 administrator is determined for each order set in a plurality of software programs. Alternatively, the priority is set to a value set by the administrator for the software program.
- the software list table 12B includes the software program name and the size of the software image corresponding to the software program.
- the capacity may be a value according to a predetermined rule such as a maximum value, an average value, or a minimum value of the image.
- the software list table may include an installation rate and an increase rate of the installation rate.
- the determined priority or the priority and priority set by the administrator are set in the software distribution priority and redundancy coefficient value table 12E. An example of this table is shown in FIG.
- the priority for the software program for each group in addition to the redundancy coefficient value calculated by the software information management processing unit 36, the priority for the software program for each group, the software corresponding to the software program from the server The number of image downloads and the total number of downloads are registered.
- download means “send” to be downloaded if the subject of the download source is the subject, and “receive” to be downloaded if the subject of the download destination is the subject.
- the “redundancy coefficient value” is an index relating to redundancy in causing a copy of a specific software image to exist in each group.
- the redundancy coefficient value increases, the software image is distributed within the group. The number of clients is increased. Therefore, when the client 14 needs a specific software image, the actual probability that the software image can be acquired from the representative client is high.
- the corresponding software image can be copied as long as it corresponds to the specific software program that is the source of the image, even if the data is not the same as the specific software image. You may consider it.
- the server 10 is made redundant by an input from the administrator. Set the coefficient value.
- the redundancy coefficient value is determined by calculation and / or setting, assuming a target value of the probability that a copy of a software image accessible by the client per unit time exists in the group.
- the calculation or setting of the redundancy coefficient value is performed in order from one of the following j to n for a plurality of software programs having entries in the software list table.
- the redundancy coefficient value calculation processing unit 36B sets the redundancy coefficient value of the software program corresponding to the software image with the largest capacity to a value designated by the administrator, and increases the capacity of the software image in proportion to the decrease in the capacity of the software image. Decrease the value.
- the redundancy coefficient value calculation processing unit 36B sets the initial value to a specific value or a value determined by any of j to l. Thereafter, the redundancy coefficient value calculation processing unit 36B includes a software list table (capacity for each software) 12B and a software distribution priority / redundancy coefficient value table (the number of downloads of software programs from the management server, the total number of downloads of software) 12E. Referring to FIG. 6, for each client group, “software capacity in FIG.
- the total number of downloads is the total number of times that the software image corresponding to the software program is downloaded to the software request destination client 14 from the server 10 and the number of times that the software image is downloaded from the representative client in the same group.
- the “number specified by the administrator” will be specifically described.
- the server 10 has already distributed a plurality of software images corresponding to 10 types of software programs to the representative client, and wants to adjust the redundancy coefficient of each software program.
- the server 10 first sorts the software programs in order of priority, and wants to increase the redundancy coefficient for the upper three types, and conversely, to decrease the redundancy coefficient for the lower three types.
- “3” is “the number specified by the administrator”.
- the representative client management processing unit 32 of the server 10 determines a representative client to which the software image should be distributed in advance by a push method in order to prepare for a pull-type software image distribution request from the client.
- the representative client is a representative client that receives the distribution of the software image from the server 10 in each group and retransmits the software image to the subordinate clients.
- the representative client management processing unit 32 performs client priority determination processing. 32A and a software image distribution destination determination processing unit 32B.
- the server 10 After completing the prioritization of software programs (S204) and the calculation of software coefficient redundancy coefficient values (S206), the server 10 prioritizes the clients (S2008) and the representative client to be the distribution destination of the software. A determination process (S2010) is performed.
- the priority determination processing unit 32A of the server 10 prioritizes clients for each group in order to determine or select a client as a representative client candidate to which a software image corresponding to the software program is distributed.
- the priority determination processing unit 32B refers to one or a combination of the following viewpoints in order to determine the priority order of the clients, that is, the priority.
- the client is not a notebook PC. Lower the priority of clients that can be disconnected from the network.
- the priority determination processing unit 32A determines the priority order related to (o) to (s) with reference to the client information table 12C. Further, priorities listed in (t) and (u) are determined with reference to the software distribution status table 12F.
- the priority determination processing unit 32A associates the software list table 12C and the software distribution status table 12F with the software name as a key, and obtains the capacity of the software image (or software program) distributed to the representative client.
- the distribution destination determination processing unit 32B determines a representative client (group) to distribute the software image corresponding to the software program (S210).
- the distribution destination determination processing unit 32B refers to the grouping table 12D and grasps clients belonging to the group for each group.
- the clients are sorted in the priority order determined in S2010, and the average operation rate for each client is obtained in order based on the client information table 12C, and the average operation rate is integrated.
- the distribution destination determination processing unit 32B refers to the integrated value and the redundant coefficient value of the software program registered in the software distribution priority / redundant coefficient table, and sorts clients until the integrated value exceeds the redundant coefficient value. Continue to end client sorting when the coefficient value is exceeded.
- the sorted client becomes the representative client for the software program in which the redundancy coefficient value compared with the integrated value is set.
- One or more clients are classified as representative clients.
- the distribution destination determination processing unit 32B sorts the next client based on the priority. .
- the distribution destination determination processing unit 32B determines a representative client to which a software image corresponding to the software program is to be distributed, an entry of the representative client is added to the software distribution status table 12F.
- FIG. 8 is an example of a software distribution status table.
- the software distribution status table includes a group name entry, a software name entry to be distributed, a representative client entry for each group, and a corresponding software image distribution status entry for each software program.
- the distribution destination determination processing unit 32B When determining the representative client, the distribution destination determination processing unit 32B adds an entry of the representative client to the software distribution state table and registers “distribution schedule” in the distribution state of the software program (800). When a software image corresponding to the software program is distributed, the status is changed to “distributed” (802).
- the server 10 determines the client to which the software image corresponding to the software program should be distributed regardless of the software redundancy coefficient value. For example, the server 10 maximizes the redundancy coefficient value of the software program, that is, the group There are a method of distributing a software image corresponding to a software program to all clients, a method of minimizing disk usage, and a mode of distributing a software image corresponding to a software program only to a client having the highest priority in the group.
- the distribution processing unit 40A transfers the software image stored on the disk to the representative client group.
- Software images are distributed in descending order of software program priority.
- An administrator can set a restriction on a group to which a software image corresponding to the software program should be distributed for a predetermined software program.
- the distribution processing unit 40A When there are a plurality of representative clients in the group, the distribution processing unit 40A attempts unicast communication with the representative clients in descending order of priority. A software image and list information for identifying other representative clients are transmitted to the representative client who has successfully communicated.
- the representative client that receives the distribution of the software image performs unicast communication with another representative client of the same group based on the list information, and transfers the software image.
- the status column of the software distribution status table 12F is set to “Distribution schedule”. To “distributed” (802).
- the server 10 transmits a software image to the representative client 14, the second process in which the representative client 14 receives the software image from the management server 10, and There is a third process in which the representative client transmits the software image to another representative client in the same group.
- FIG. 9 is a flowchart corresponding to the first process
- FIG. 10 is a flowchart corresponding to the second process
- FIG. 11 is a flowchart corresponding to the third process.
- the distribution processing unit refers to the software distribution status table 12F and identifies the representative client to which the software image is to be distributed.
- the distribution processing unit 40A transmits a request for confirming the acquisition status of the software image to be distributed to the representative client with the highest priority, and receives a response result to the request (S900).
- the distribution processing unit 40A selects a software image corresponding to the software program to be distributed based on the software distribution status table 12F.
- the result reception processing unit 40B determines whether or not the representative client has acquired the software image corresponding to the software program based on the response result from the representative client that has received the request (S902). Then, the software image is transmitted to the representative client (S904). If affirmative in S902, the process jumps to S904.
- the result reception processing unit 40B updates the state of the representative client that acquired the software image to “distributed” in the software distribution status table 12F (S906).
- the result reception processing unit 40B refers to the software distribution status table 12F and searches for other representative clients that belong to the same group as the representative client that distributed the software image (S908).
- the result reception unit 40B selects a table entry that satisfies all of the following from the software distribution status table 12F.
- the group name is the same as the group name corresponding to the representative client who received the software image.
- the software name is the same as the name of the software program corresponding to the software image distributed to this representative client.
- the distribution processing unit 40A transmits the client name belonging to the selected entry or entries to the representative client that transmitted the software image in S904 (S910).
- the processing for receiving a software image from the server 10 4 performed by the representative client 14 will be described with reference to FIG.
- the software reception processing unit 62B of the client 14 has already acquired the software image by referring to the software image data in the disk device 14B. It is determined whether or not (S1002).
- the software reception processing unit 62B denies this determination, it responds that the software image has not been acquired to the result reception processing unit 40B of the server 10 (S10004).
- the software reception processing unit 62B receives the software image from the server 10 via the communication interface 50, and stores it from the disk interface 52 in the software image storage area of the disk 14B (S1006).
- the software distribution task table 72 manages a task for a representative client that has received a software image to transmit a software image to another representative client in the same group.
- Figure 12 shows an example of the software distribution task table.
- the software distribution task table includes a task entry, an entry of a corresponding software program name of a software image to be transmitted, an entry of a representative client to which a software image corresponding to the software program is to be transmitted, and an entry of a transmission state. Is provided.
- a software image identifier may be used instead of the software program name.
- the transmission state is set to “incomplete”. If S1002 is negative, the process jumps to S1006.
- the former representative client is designated as the first representative client and the latter representative client is designated as the second representative client, and the two are distinguished for convenience.
- the software transmission processing unit 64A of the first representative client refers to the software distribution task table 72, selects the second representative client whose status is not “completed”, and selects the second representative client via the communication interface 50 and the LAN 76. It is determined whether or not the second representative client can be connected (S1100).
- the software transmission processing unit 64A determines whether the second representative client has acquired the software image based on the response (S1104).
- the software transmission processing unit 64A reads the software image from the disk device 14B and transmits it to the second representative client (S1106).
- the software transmission processing unit 64A reads a list of representative client names from the software distribution task table 72 and transmits it to the second representative client (S1108).
- the software transmission processing unit 64A of the first representative client updates the “status” of the second representative client, which is the transmission destination of the software image, to “sent” in the software distribution status table 72 (S1110).
- the server 10 is notified that the software image has been transmitted from the first representative client to the second representative client (S1112).
- the distribution status screen display processing unit 42 of the server 10 creates a software image transmission status table based on the report from the second representative client, and displays this to the administrator. Details of this table will be described later.
- the software transmission processing unit 64A updates the “status” entry of the second representative client for the transmission target software name to “completed” in the software distribution task table 72 (S1114).
- the software transmission processing unit 64A makes a negative determination in S1104, the “status” in the software distribution task table is updated to “not connectable” and the process ends. Furthermore, if the software transmission processing unit 64A makes a positive determination in S1104, the process jumps to S1110.
- the client acquires a list of representative clients belonging to the same group as the client from the server, and sequentially accesses the representative clients in the list.
- the client can communicate with one of the representative clients. If the representative client holds a software image corresponding to a desired software program, the client receives this software image from the representative client. When communication with all representative clients is not possible or when all the representative clients do not have a software image corresponding to the desired software program, the client acquires a software image corresponding to the desired software program from the management server. .
- the client If the server needs to distinguish between a download from the server and a download from the representative client in determining the software priority and redundancy factor values, the client must Report the type (management server or representative client). Then, the client installs a desired software program using the received software image.
- the server manages the license for using the software program, or when the number of installations of the software program is used as a parameter for managing the distribution of the software program, the client reports to the server that the software program has been installed.
- the representative client holds the software image corresponding to the software program in the memory (temporary copy) in the memory without installing the software program like the requesting client.
- the software may be installed using a software image cache.
- FIG. 13 is a flowchart of software distribution processing of the representative client.
- the software transmission processing unit 64A of the representative client receives a connection request from the client (S1300), it determines whether or not it holds a software image corresponding to the software program requested by the client (S1302), and affirms this.
- Information indicating that the software image corresponding to the requested software program is held is transmitted to the requesting client (S1304), and then the software image corresponding to the requested software program is transmitted (S1306).
- the representative client transmits information indicating that the software image corresponding to the requested software program is not held to the requesting client (S1308).
- FIG. 14 is a flowchart of software image reception processing and installation processing of the software requesting client.
- the software reception processing unit 62B of the client 14 receives an input of a software program name to be installed from the user (S1400).
- the software receiving unit 62B acquires information on a list of representative clients that hold software images corresponding to the software program designated by the user in S1400 in the group to which the software receiving unit 62B belongs (S1404).
- the software receiving unit 62B that has acquired the list information performs the process described below for each representative client in the list.
- the software reception processing unit 62B of the request source client 14 transmits a software image acquisition request to the representative client (S1406).
- the name of the software program is specified in the request, an identifier of the software image may be specified.
- the request source client 14 determines whether or not the representative client holds a software image corresponding to the target software program based on the response from the representative client (S1407).
- the software reception processing unit 62B receives the software image corresponding to the target software program from the software transmission processing unit 64A of the representative client (S1408).
- the request source client 14 reports to the server that the software image corresponding to the software program has been downloaded from the representative client (S1410), and then executes S1416 described later (S1410).
- the request source client 14 accesses another representative client (sends an acquisition request) and tries to acquire a software image corresponding to the software program. If the acquisition of the software image is successful (S1412: No), the software program is installed using the acquired software image (S1416), and the fact is transmitted to the server (S1418).
- the server 10 is accessed and the distribution processing unit 40B of the server 10 Receive software image distribution (S1414).
- the installation processing unit 62C of the client 14 that has received the distribution of the software image installs the software program using the distributed software image (S1416), and transmits that fact to the server (S1418).
- the representative client or server sets one of the requesting clients as a new representative client. Set and parallelize the transmission process. The processing related to the representative client will be described with reference to the flowchart.
- FIG. 15 is a flowchart showing an outline of the operation of the representative client.
- the representative client receives a connection request from the client requesting the software image (S1500), it is determined whether or not the representative client holds a software image corresponding to the requested software program (S1502).
- the software transmission processing unit 64A of the representative client transmits information indicating that the software image corresponding to the software program is held to the requesting client (S1504).
- the software transmission processing unit 64A of the representative client transmits a software image corresponding to the software program to the requesting client, and creates a new representative client (S1506).
- the details of this step are as shown in the flowchart of FIG.
- the software transmission processing unit 64A of the representative client stores the target client that transmits the software image in a predetermined work area of the memory 60 (S1600).
- the plurality of target clients are stored in the work area.
- the software transmission processing unit 64A sets this as the number of objects for which parallel transmission of software is executed, that is, the number of parallel processes (S1602).
- the software transmission processing unit 64A compares the number of parallel processes and the specified number (S1604), and if it is determined that the number of parallel processes is equal to or greater than the specified number, registers necessary information in the software transmission status table 74 of the disk device 14B.
- FIG. 17 is an example of a software transmission status table.
- the software transmission status table includes an entry for a software program name, an entry for a software destination client name, an entry for a new representative flag, an entry for an interruption flag, and an entry for the name of the client that receives the software image corresponding to the software program. And have.
- the software transmission processing unit 64A of the representative client selects a new representative client from a certain client, and sets a new representative flag in an entry having the client as the destination client name in the software transmission status table 74 (S1605). Note that this processing is not actually performed when a representative flag is already set for at least one of the plurality of destination clients.
- a client that is scheduled to transmit a software image corresponding to a software program having the smallest number of bytes is a new representative client.
- the representative client who is requested to distribute the software image makes an inquiry to the central server, and the client with the highest priority among the software image distribution destination client groups is set as the new representative client.
- the software transmission processing unit 64A determines that the number of parallel processes is smaller than the specified number or ends the processing of S1605, the client transmission target name is added to the software transmission status table 74 (S1606).
- the software transmission processing unit 64A performs processing for transmitting a software image. This process will be described in detail with reference to FIG. Note that the transmission process is achieved by dividing the software image into a plurality of blocks and sequentially transferring them.
- the software transmission processing unit 64A of the representative client sets the type of packet for transmitting the block as “software” (S1800). Next, the packet is sent to the client to be transmitted (S1802).
- the software transmission processing unit 64A searches the software transmission state table, confirms the interruption flag for the transmission target client (S1804), and determines the presence or absence of the interruption flag (S1806).
- the software transmission processing unit 64A of the representative client sets the packet type to “interruption” (S1810), transmits the packet to the transmission destination client,
- the client information of the software transmission status table 74 is transmitted to the client that transmitted the packet (S1812), and the process proceeds to S1610 in FIG.
- the software transmission processing unit 64A of the representative client sets the packet type to “completed” (S1613).
- the software transmission processing unit 64A of the representative client refers to the software transmission status table 74 and determines whether or not a new representative flag is set on the transmission target client (S1614). If it is determined that the new representative flag is not set, the transmission target client is notified that it is not the new representative (S1616). If it is determined that the new representative flag is set, the transmission target client is notified that it will become the new representative client (S1618). Further, the server is notified that the transmission target client has become a new representative (S1620).
- the software transmission processing unit 64A selects half of the clients undergoing transmission processing or the designated ratio, and sets an interruption flag for the client entry in the software transmission status table 74 (S1622).
- the name of the new representative client that has set the new representative flag is recorded as the receiving client of the entry of the destination client that has set the relay flag (S1624).
- the packet type is determined (S1902). If the packet type is “completed”, the packet data is confirmed (S1904), it is determined whether there is a command for setting new representative flag data (S1906). All blocks of the software image received from the client are stored in the distribution software data storage area of the disk 14B (S1908).
- the received block is stored in the disk 14B (S1912). If the packet type is “suspended”, the client whose software image distribution is suspended by receiving the suspended packet accesses the receiving client in the software transmission status table 74 as a new representative, and The interrupted software image is retransmitted from the client (S1910).
- the server for example, checks the addition or removal of clients or periodically calculates the priority of the software program and the required redundancy coefficient value, and the copy of the software image is biased against the latest calculation result. If so, the software image copy in the client group is rearranged.
- the server reallocation processing unit 34 periodically executes the following processing.
- the server collects inventory information from clients connected to the server, and confirms the increase or decrease of clients in each group. The increase / decrease is calculated based on the difference between the previous collection result and the latest collection result. Each time inventory information is collected, the server records the last update date, and determines that clients that have not been updated for more than the time specified by the administrator have been removed.
- (A) a recalculated method of matching the software and / or client priority with a software image arrangement state corresponding to the software program in the client group, (B) a software image corresponding to the current software program
- the distribution status of the software image does not satisfy the redundancy desired by the administrator or exceeds the redundancy desired by the administrator, and the corresponding software image is rearranged.
- the relocation processing unit 34 of the management server obtains one or a plurality of candidates for a new representative client for the client group that has undergone expansion or reduction.
- the rearrangement processing unit 34 compares an existing representative client with a new representative client, and determines a client that is not a representative and a client that is a new representative.
- the relocation processing unit 34 sends the address of a client to be a new representative client to any one of the existing representative clients, and gives a command to send software from the existing representative client to the new representative client.
- the software transmission processing unit 64 of the representative client that has received this software transmission command transmits the software image to each of the newly representative clients, and when the transmission is completed, the transmission is completed to the relocation processing unit 34 of the server. To report.
- the server receives the report of the completion of transmission, the server sends a command for deleting the software image to the client that is not represented.
- the reallocation processing unit 34 refers to the current representative client by referring to the client information table 12C, acquires the latest average operating rate, and accumulates these.
- the relocation processing unit 34 selects one of the existing representative clients, for example, selects a client with the smallest I / O load, and newly transmits a software image to the representative client. Send instructions.
- the redundancy coefficient value is exceeded, the one with the lowest priority among the existing representative clients is removed in order from the target for integrating the average operating rate, and the integration result shows the corrected redundancy coefficient value. Continue this until below. A client that has been removed until just before the integration result falls below the redundancy coefficient value is determined to be excluded from the representative, and an instruction to delete the software image is sent to the client.
- the server distribution status screen display processing unit 42 receives a screen display request from the administrator, it generates management display information based on the updated table information of the disk 12 and uses this for screen display. A display output is performed on the management screen of the client 28.
- FIG. 20 shows an example of the management screen. This management screen has the following entries.
- the group name corresponds to the group name column in the software distribution status table 12F.
- the ⁇ total disk capacity, total free disk capacity ⁇ for each group corresponds to the total disk capacity column and free disk capacity column of the client information table 12C.
- the total capacity of software images distributed for each group is obtained by associating the software distribution status table 12F and the software list table 12B with respect to software program names, and the “size” of the entry whose status column of the software distribution status table 12F is “distributed”. "Is a value compiled for each group.
- the software name corresponds to the software name column in the software distribution status table 12F.
- “Representative client count, representative client name” for each group and software corresponds to the client name column in the software distribution status table 12F.
- the redundancy coefficient value of the software program for each group and each software program corresponds to the software distribution priority and the value of the redundancy coefficient value column of the redundancy coefficient value table 12E.
- the software distribution status table 12F and the client information table 12B are combined with respect to the client name.
- the average operating rate for each date corresponds to a value that is summarized for each group and each software program.
- the client In response to an instruction from the server, it is determined whether or not the client is a representative client. In the case of the representative client, information (address, capacity, etc.) of the area where the software is cached is transmitted to the server. The server distributes software to the client in accordance with information from the client.
- the push type distribution example from the server to the representative client has been described.
- the method of distributing the software program to the representative client does not prevent the pull type based on the request from the representative client. Absent.
- a pull-type client (or representative client) requests acquisition of a software image for a representative client or server
- a software program name is specified in the request (representative clients or representative clients). And between servers may be the same).
- distribution management since there may be a plurality of software images for installing one software program, distribution management (storage of necessary information or / and execution of processing) is performed as a software program. It was disclosed mainly.
- a software image identifier may be used instead of the software program name specified at the time of acquisition.
- distribution management of software images may be performed as software images instead of software programs.
- the computer system of the present invention can be incorporated into a system in which a management server has a software image and the software image is distributed to clients based on a request from a client that requires the software image.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
Description
従って、「配布」は、サーバ、クライアント、または代表クライアントを主語として「送信」「受信」「転送」と読み替えてもよい。さらに、「配布」された計算機が配布されたソフトウェアイメージを用いて対応するソフトウェアプログラムをインストールすることを含めてもよく、または含めなくてもよい。
クライアント情報管理処理部30の収集処理部30Aは複数のクライアント14に定期的(または繰り返し)にアクセスして、各クライアントのクライアント情報送信部62Aから、クライアント情報、主に、インベントリ情報や性能情報を収集し、収集した情報をディスク装置12のクライアント情報テーブル12Bに更新格納する。
次に、クライアント情報管理処理部30のグルーピング処理部30Bは、クライアント情報テーブル12Cを参照して、複数のクライアント14をグループに自動分類する。その方式として、次のものがある。
管理サーバ10のソフトウェア情報管理処理部36の優先度決定処理部36Aは、クライアント14のグループ毎に、管理者が、サーバ10に配置されたソフトウェアイメージをクライアント14に配布するための優先順位を決定する優先度決定処理を行う。
次に、サーバ10のソフトウェア情報管理処理部36の冗長係数値計算処理部は、ソフトウェアの冗長係数値の計算処理を実行する。
サーバ10の代表クライアント管理処理部32は、各グループについて、クライアントからのプル型のソフトウェアイメージ配信要求に備えるために、ソフトウェアイメージをプッシュ方式によって予め配布すべき代表クライアントを決定する。
次いで、サーバ10の通信処理部40は、フローチャートのS214に示されるように、S212で決定された、ソフトウェアプログラムに対応したソフトウェアイメージの配布先である代表クライアントにソフトウェアイメージの配布処理と、配布結果を代表クライアントから受付けてソフトウェア配状況テーブル12Fに登録する、配布結果受付処理とを実行する。
なお、複数の送信先クライアントのうち少なくとも一つのクライアントに代表フラグが既に立っている場合には、この処理を実際には行わない。
グループ毎、ソフトウェアプログラム毎の、ソフトウェアプログラムの冗長係数値は、ソフトウェア配布優先度と冗長係数値テーブル12Eの、冗長係数値カラムの値に対応する。
12・・・サーバのディスク装置
14・・・クライアント
14A・・代表クライアント
14B・・クライアントのディスク装置
28・・・画面表示用クライアント
Claims (14)
- 計算機システムにおけるソフトウェアプログラムに対応するソフトウェアイメージの配布管理方法であって、
前記計算機システムは、
複数のクライアント計算機と、
前記複数のクライアント計算機の一つ又は複数に配布するソフトウェアイメージを含むサーバと、
前記サーバ計算機と前記複数のクライアント計算機とを接続するネットワークと、
を備え、
前記サーバ計算機は、
前記複数のクライアント計算機からの情報に基づいて、前記複数のクライアント計算機を複数のグループに分類する第1のステップと、
各グループについて代表クライアント計算機を選定するステップと、
前記代表クライアント計算機へ前記ソフトウェアプログラムに対応するソフトウェアイメージを配布するステップと、
を実行し、
前記ソフトウェアイメージの配布を受けた前記代表クライアント計算機は、同一グループに属する他のクライアント計算機からの要求に基づいて前記ソフトウェアイメージを当該他のクライアント計算機に配布する、
計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、
前記ソフトウェアイメージを複数含み、
当該複数のソフトウェアプログラム又はソフトウェアイメージの属性に基づいて夫々の優先度を決定し、
当該優先度に基づく優先順位にしたがって前記代表クライアント計算機へ前記複数のソフトウェアイメージを配布する、
請求項1記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、
前記複数のクライアント計算機のリソース情報に基づいて夫々の優先度を決定し、
前記優先度に基づく優先順位にしたがって前記代表クライアント計算機へ前記ソフトウェアイメージを配布する、
請求項2記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、
前記複数のグループの少なくとも一つに、前記ソフトウェアイメージを存在させる割合に関する目標値を設定し、
前記複数のクライアント計算機から収集したリソース情報に基づいて、前記複数のクライアント計算機夫々の稼働状況を判定し、
前記目標値が設定されたグループに属する複数のクライアント計算機の中から、前記クライアント計算機の優先度にしたがって、一つのクライアント計算機を順番に選択し、
選択したクライアント計算機の前記稼働状況情報の合算値が前記目標値に到達するまで前記クライアント計算機の選択を継続し、
前記選択された一つ又は複数のクライアント計算機を前記代表クライアント計算機として設定する、
請求項3記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、前記ソフトウェアプログラムの優先度が高いほど前記目標値を高く設定する、請求項4記載の計算機システムにおけるソフトウェアイメージの配布管理方法。
- 前記サーバ計算機は、
同一グループに複数の前記代表クライアント計算機を設定し、
前記複数の代表クライアント計算機の一つに前記優先度順にアクセスして、一つの代表クライアント計算機に前記ソフトウェアイメージを配布し、
前記ソフトウェアイメージの配布を受けた代表クライアント計算機は、他の代表クライアント計算機に当該ソフトウェアイメージを配布する、
請求項3記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記代表クライアント計算機が、同一のソフトウェアイメージの配布要求を前記複数のクライアント計算機から受信すると、
前記サーバ計算機は、
前記複数のクライアント計算機の少なくとも一つを新代表クライアント計算機に設定し、
前記新代表クライアント計算機から、前記複数のクライアント計算機のうち前記新代表クライアント計算機以外のクライアント計算機に前記ソフトウェアイメージを配布する、
請求項3記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、前記複数のクライアント計算機のうち、前記優先度が高いクライアント計算機を前記新代表クライアント計算機に設定する、
請求項7記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記代表クライアント計算機は、前記新代表以外の前記複数のクライアント計算機への前記ソフトウェアイメージの配布を中断し、
前記新代表クライアント計算機は、前記ソフトウェアイメージの配布が中断されたクライアント計算機に対して前記ソフトウェアイメージの配布を実行する、
請求項7記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、
前記ソフトウェアイメージを前記代表クライアント計算機に配布した後、当該代表クライアント計算機に変更を設定し、
変更後の代表クライアント計算機に対して前記ソフトウェアイメージの配布を再配置する、
請求項1記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 前記サーバ計算機は、
前記クライアント計算機の増設及び/又は減設を判定し、
当該判定に基づいて前記変更を設定し、
前記変更の設定に基づく新たな代表クライアント計算機は、前記変更の設定の前の代表クライアント計算機から前記ソフトウェアイメージの配布を受け、
前記変更の設定に基づいて、前記代表クライアント計算機から除かれたクライアント計算機は、前記配布されたソフトウェアイメージを削除する、
請求項11記載の計算機システムにおけるソフトウェアイメージの配布管理方法。 - 複数のクライアント計算機と、
前記複数のクライアント計算機の一つ又は複数に配布するソフトウェアイメージを含むサーバ計算機と、
前記サーバ計算機と前記複数のクライアント計算機とを接続するネットワークと、
を備える計算機システムであって、
前記サーバ計算機は、
前記複数のクライアント計算機とのインターフェースと、
前記ソフトウェアイメージの配布管理プログラムを含む第1のメモリと、
前記ソフトウェアと前記ソフトウェアイメージの配布管理情報を含む第2のメモリと、
前記配布管理プログラムと前記配布管理情報とに基づいて、前記ソフトウェアイメージの配布管理処理を実行するCPUと、
を備え、
前記CPUは、前記複数のクライアント計算機からの情報に基づいて、前記複数のクライアント計算機を複数のグループに分類し、各グループについて代表クライアント計算機を選定し、前記代表クライアント計算機へ前記ソフトウェアイメージを配布し、
前記ソフトウェアイメージの配布を受けた前記代表クライアント計算機は、前記ソフトウェアイメージを当該他のクライアント計算機に配布し、
前記CPUは、前記第2のメモリの前記ソフトウェアイメージの配布管理情報に基づいて、管理用表示情報を生成し、当該管理用表示情報を管理画面に出力する、
計算機システム。 - 前記第2のメモリは、前記ソフトウェアイメージを複数含み、
前記CPUは、
当該複数のソフトウェアイメージの属性に基づいて夫々の優先度と前記複数のクライアント計算機のリソース情報に基づいて夫々の優先度とを夫々決定し、
当該決定された優先度に基づく優先順位にしたがって前記代表クライアント計算機へ前記複数のソフトウェアイメージを配布し、
前記複数のグループの少なくとも一つに、前記ソフトウェアイメージを存在させる割合に関する目標値を設定し、
前記複数のクライアント計算機から収集したリソース情報に基づいて、前記複数のクライアント計算機夫々の稼働状況を判定し、
前記目標値が設定されたグループに属する複数のクライアント計算機の中から、前記クライアント計算機の優先度にしたがって、一つのクライアント計算機を順番に選択し、
選択したクライアント計算機の前記稼働状況情報の合算値が前記目標値に到達するまで前記クライアント計算機の選択を継続し、
前記選択された一つ又は複数のクライアント計算機を前記代表クライアント計算機として設定し、
同一グループに複数の前記代表クライアント計算機を設定し、
前記複数の代表クライアント計算機の一つに前記優先度順にアクセスして、一つの代表クライアント計算機に前記ソフトウェアイメージを配布し、
前記ソフトウェアイメージの配布を受けた代表クライアント計算機に、他の代表クライアント計算機に当該ソフトウェアイメージを配布させ、
前記代表クライアント計算機が同一のソフトウェアイメージの配布要求を前記複数のクライアント計算機から受信すると、前記複数のクライアント計算機の少なくとも一つを新代表クライアント計算機に設定し、
前記新代表クライアント計算機に、前記複数のクライアント計算機のうち前記新代表クライアント計算機以外のクライアント計算機に前記ソフトウェアイメージを配布させ、
前記代表クライアント計算機は、前記新代表以外の前記複数のクライアント計算機への前記ソフトウェアイメージの配布を中断し、
前記新代表クライアント計算機は、前記ソフトウェアの配布が中断されたクライアント計算機に対して前記ソフトウェアイメージの配布を実行し、
前記CPUは、
前記クライアント計算機の増設及び/又は減設を判定すると、前記ソフトウェアイメージを前記代表クライアント計算機に配布した後、当該代表クライアント計算機に変更を設定し、前記変更の設定に基づく新たな代表クライアント計算機に、前記変更の設定の前の代表クライアント計算機から前記ソフトウェアイメージの配布を受けさせ、
前記変更の設定に基づいて、前記代表クライアント計算機から除かれたクライアント計算機に、前記配布されたソフトウェアイメージを削除させる、
請求項12記載のソフトウェアイメージの配布管理のための計算機システム。 - サーバ計算機と、第1のクライアント計算機と、に接続された第2のクライアント計算機が読み取り可能な記憶媒体であって、
前記記憶媒体は、
前記第2のクライアント計算機に、前記サーバから代表クライアントを特定する情報を受信させ、前記代表クライアントを特定する情報に基いて、前記第1のクライアント計算機と前記第2のクライアント計算機とから代表クライアント計算機を特定させる、代表クライアント特定プログラムコードと、
前記代表クライアント計算機が前記第2のクライアント計算機の場合は、前記第2のクライアント計算機に、以下の(A1)乃至(A3)を実行させるソフトウェア配布プログラムコードと、
(A1)前記サーバ計算機からソフトウェアプログラムのソフトウェアイメージを受信して前記第2のクライアント計算機のメモリ又はディスクに格納させ、
(A2)前記ソフトウェア取得要求を受信し、前記ソフトウェア取得要求によって指定されたソフトウェアプログラムに対応するソフトウェアイメージを、前記第2のクライアント計算機のメモリ又はディスクに格納しているか確認させ、
(A3)前記(A2)の確認の結果、前記指定されたソフトウェアプログラムのソフトウェアイメージを格納している場合は、前記指定されたソフトウェアプログラムに対応するソフトウェアイメージを送信させ、
前記代表クライアント計算機が前記第1のクライアント計算機の場合は、前記第2のクライアント計算機に、以下の(B1)乃至(B4)を実行させるソフトウェアインストールプログラムコードと、
(B1)インストール対象の所定のソフトウェアプログラムを指定したインストール入力を受信させ、
(B2)前記所定のソフトウェアプログラムを指定したソフトウェア取得要求を、前記代表クライアント計算機又は前記サーバに送信させ、
(B3)前記ソフトウェア取得要求に応じた所定のソフトウェアプログラムに対応する所定のソフトウェアイメージを受信させ、
(B4)前記所定のソフトウェアイメージを用いて前記所定のソフトウェアプログラムをインストールさせ、
前記第2のクライアント計算機に、前記代表クライアント計算機の識別子を表示させる、代表クライアント表示プログラムコードと、
を格納することを特徴とした記憶媒体。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2010/003077 WO2011135629A1 (ja) | 2010-04-28 | 2010-04-28 | 計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム |
JP2012512540A JPWO2011135629A1 (ja) | 2010-04-28 | 2010-04-28 | 計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム |
US12/864,184 US20110271275A1 (en) | 2010-04-28 | 2010-04-28 | Software distribution management method of computer system and computer system for software distribution management |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2010/003077 WO2011135629A1 (ja) | 2010-04-28 | 2010-04-28 | 計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011135629A1 true WO2011135629A1 (ja) | 2011-11-03 |
Family
ID=44859360
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/003077 WO2011135629A1 (ja) | 2010-04-28 | 2010-04-28 | 計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20110271275A1 (ja) |
JP (1) | JPWO2011135629A1 (ja) |
WO (1) | WO2011135629A1 (ja) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016132454A1 (ja) * | 2015-02-17 | 2016-08-25 | 富士通株式会社 | アプリケーション配信方法、アプリケーション配信プログラム、およびサーバ |
JP2017021566A (ja) * | 2015-07-10 | 2017-01-26 | 日本電気株式会社 | ネットワーク管理装置、通信装置、プログラム更新システムおよびプログラム更新方法 |
WO2017209049A1 (ja) * | 2016-06-02 | 2017-12-07 | 住友電気工業株式会社 | プログラム配信システム、サーバ、プログラム配信方法、およびコンピュータプログラム |
WO2018142751A1 (ja) * | 2017-02-01 | 2018-08-09 | 住友電気工業株式会社 | 制御装置、プログラム更新方法、およびコンピュータプログラム |
US10229207B2 (en) | 2012-10-11 | 2019-03-12 | Thomson Licensing | Solution for distributed application life-cycle management |
JP2021043545A (ja) * | 2019-09-06 | 2021-03-18 | キヤノン株式会社 | 管理システムおよびその制御方法、並びにプログラム |
US11144295B2 (en) | 2016-03-02 | 2021-10-12 | Sumitomo Electric Industries, Ltd. | Program updating system, program updating method, and computer program |
JP2022551560A (ja) * | 2019-10-09 | 2022-12-12 | トヨタ モーター ノース アメリカ,インコーポレイティド | 輸送装置ソフトウェアアップデートの管理 |
US11755314B2 (en) | 2019-10-09 | 2023-09-12 | Toyota Motor North America, Inc. | Management of transport software updates |
JP7389949B2 (ja) | 2019-09-20 | 2023-12-01 | 章弘 長谷川 | ファイル配布システム、及びファイル配布プログラム |
US11868764B2 (en) | 2019-10-09 | 2024-01-09 | Toyota Motor North America, Inc. | Management of transport software updates |
US11868757B2 (en) | 2019-10-09 | 2024-01-09 | Toyota Motor North America, Inc. | Management of transport software updates |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2452325A (en) * | 2007-08-31 | 2009-03-04 | Sony Corp | Method and system for distributing software to a portable device using software on a pre-recorded medium. |
JP5449044B2 (ja) * | 2010-06-10 | 2014-03-19 | シャープ株式会社 | サーバ装置、端末装置およびアプリケーション制御システム |
US8762521B2 (en) * | 2011-03-14 | 2014-06-24 | 1E Limited | Monitoring the distribution of software |
CN102521031B (zh) * | 2011-12-13 | 2014-11-05 | 华为终端有限公司 | 移动终端预置应用程序的管理方法和移动终端 |
JP2013238949A (ja) * | 2012-05-14 | 2013-11-28 | Ricoh Co Ltd | 情報配信装置、及び情報配信システム並びにプログラム |
US20130332522A1 (en) * | 2012-06-08 | 2013-12-12 | Microsoft Corporation | Fast channel for system management |
US9432452B2 (en) * | 2012-09-10 | 2016-08-30 | Joosy, Inc. | Systems and methods for dynamic networked peer-to-peer content distribution |
US9411571B2 (en) * | 2013-02-28 | 2016-08-09 | Adobe Systems Incorporated | Method and apparatus for deploying software as a service |
JP2014216943A (ja) * | 2013-04-26 | 2014-11-17 | 株式会社東芝 | 電子機器、方法、及びプログラム |
US9696982B1 (en) * | 2013-11-05 | 2017-07-04 | Amazon Technologies, Inc. | Safe host deployment for a heterogeneous host fleet |
JP6365070B2 (ja) * | 2014-07-28 | 2018-08-01 | 富士通株式会社 | 検索プログラム、装置、及び方法 |
US9395969B2 (en) * | 2014-09-23 | 2016-07-19 | International Business Machines Corporation | Complex computer environment installation |
US10200416B2 (en) * | 2015-02-24 | 2019-02-05 | Vizio Inc | Global setting for casting content to networked renderer |
WO2018103033A1 (en) * | 2016-12-08 | 2018-06-14 | Hewlett Packard Enterprise Development Lp | Software classification |
CN110896404B (zh) * | 2018-09-12 | 2021-09-14 | 华为技术有限公司 | 数据处理的方法、装置和计算节点 |
US11221837B2 (en) | 2019-04-11 | 2022-01-11 | Microsoft Technology Licensing, Llc | Creating and deploying packages to devices in a fleet based on operations derived from a machine learning model |
US11029936B2 (en) * | 2019-04-11 | 2021-06-08 | Microsoft Technology Licensing, Llc | Deploying packages to devices in a fleet in stages |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002124945A (ja) * | 2000-10-12 | 2002-04-26 | Ntt Comware Corp | ファイル多重配信方法及びシステム装置 |
JP2006172305A (ja) * | 2004-12-17 | 2006-06-29 | Nec Corp | 無線基地局装置及びプログラムダウンロード方法並びにそのプログラム |
JP2009271904A (ja) * | 2008-04-10 | 2009-11-19 | Hitachi Ltd | 配布管理方法、配布管理システム、および配布管理サーバ |
JP2010032976A (ja) * | 2008-07-31 | 2010-02-12 | Daiichikosho Co Ltd | 通信カラオケシステム |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8898256B2 (en) * | 2004-07-13 | 2014-11-25 | International Business Machines Corporation | Prioritization of application component distribution |
US7770168B1 (en) * | 2005-05-25 | 2010-08-03 | Landesk Software Limited | Systems and methods for distributing software using nodes within a network group |
WO2009007967A2 (en) * | 2007-07-09 | 2009-01-15 | Nolio Ltd. | System and method for application process automation over a computer network |
US8201164B2 (en) * | 2007-07-20 | 2012-06-12 | Microsoft Corporation | Dynamically regulating content downloads |
US9665729B2 (en) * | 2009-04-13 | 2017-05-30 | Microsoft Technology Licensing, Llc | Revocation of application on mobile device |
-
2010
- 2010-04-28 JP JP2012512540A patent/JPWO2011135629A1/ja active Pending
- 2010-04-28 US US12/864,184 patent/US20110271275A1/en not_active Abandoned
- 2010-04-28 WO PCT/JP2010/003077 patent/WO2011135629A1/ja active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002124945A (ja) * | 2000-10-12 | 2002-04-26 | Ntt Comware Corp | ファイル多重配信方法及びシステム装置 |
JP2006172305A (ja) * | 2004-12-17 | 2006-06-29 | Nec Corp | 無線基地局装置及びプログラムダウンロード方法並びにそのプログラム |
JP2009271904A (ja) * | 2008-04-10 | 2009-11-19 | Hitachi Ltd | 配布管理方法、配布管理システム、および配布管理サーバ |
JP2010032976A (ja) * | 2008-07-31 | 2010-02-12 | Daiichikosho Co Ltd | 通信カラオケシステム |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10229207B2 (en) | 2012-10-11 | 2019-03-12 | Thomson Licensing | Solution for distributed application life-cycle management |
JPWO2016132454A1 (ja) * | 2015-02-17 | 2018-01-18 | 富士通株式会社 | アプリケーション配信方法、アプリケーション配信プログラム、およびサーバ |
WO2016132454A1 (ja) * | 2015-02-17 | 2016-08-25 | 富士通株式会社 | アプリケーション配信方法、アプリケーション配信プログラム、およびサーバ |
JP2017021566A (ja) * | 2015-07-10 | 2017-01-26 | 日本電気株式会社 | ネットワーク管理装置、通信装置、プログラム更新システムおよびプログラム更新方法 |
US11144295B2 (en) | 2016-03-02 | 2021-10-12 | Sumitomo Electric Industries, Ltd. | Program updating system, program updating method, and computer program |
WO2017209049A1 (ja) * | 2016-06-02 | 2017-12-07 | 住友電気工業株式会社 | プログラム配信システム、サーバ、プログラム配信方法、およびコンピュータプログラム |
WO2018142751A1 (ja) * | 2017-02-01 | 2018-08-09 | 住友電気工業株式会社 | 制御装置、プログラム更新方法、およびコンピュータプログラム |
JPWO2018142751A1 (ja) * | 2017-02-01 | 2019-02-07 | 住友電気工業株式会社 | 制御装置、プログラム更新方法、およびコンピュータプログラム |
US10705826B2 (en) | 2017-02-01 | 2020-07-07 | Sumitomo Electric Industries, Ltd. | Control apparatus, program updating method, and computer program |
JP2021043545A (ja) * | 2019-09-06 | 2021-03-18 | キヤノン株式会社 | 管理システムおよびその制御方法、並びにプログラム |
JP7374675B2 (ja) | 2019-09-06 | 2023-11-07 | キヤノン株式会社 | 管理システムおよびその制御方法、並びにプログラム |
JP7389949B2 (ja) | 2019-09-20 | 2023-12-01 | 章弘 長谷川 | ファイル配布システム、及びファイル配布プログラム |
JP2022551560A (ja) * | 2019-10-09 | 2022-12-12 | トヨタ モーター ノース アメリカ,インコーポレイティド | 輸送装置ソフトウェアアップデートの管理 |
US11755314B2 (en) | 2019-10-09 | 2023-09-12 | Toyota Motor North America, Inc. | Management of transport software updates |
JP7376695B2 (ja) | 2019-10-09 | 2023-11-08 | トヨタ モーター ノース アメリカ,インコーポレイティド | 輸送装置ソフトウェアアップデートの管理 |
US11868764B2 (en) | 2019-10-09 | 2024-01-09 | Toyota Motor North America, Inc. | Management of transport software updates |
US11868757B2 (en) | 2019-10-09 | 2024-01-09 | Toyota Motor North America, Inc. | Management of transport software updates |
Also Published As
Publication number | Publication date |
---|---|
JPWO2011135629A1 (ja) | 2013-07-18 |
US20110271275A1 (en) | 2011-11-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011135629A1 (ja) | 計算機システムにおけるソフトウェアの配布管理方法、及び、ソフトウェアの配布管理のための計算機システム | |
JP4265245B2 (ja) | 計算機システム | |
US11082512B2 (en) | Routing and filtering event notifications | |
US8346843B2 (en) | System and method for scalable data distribution | |
JP4621273B2 (ja) | データ同期方法、データ同期プログラム、データベースサーバ装置、および、データベースシステム | |
CN102170396B (zh) | 一种基于区分服务的云存储系统QoS控制方法 | |
US8819080B2 (en) | System and method for collection, retrieval, and distribution of data | |
US20140237071A1 (en) | Caching in Mobile Networks | |
US8661055B2 (en) | File server system and storage control method | |
US9361474B2 (en) | Network filesystem asynchronous I/O scheduling | |
KR20120072907A (ko) | 오브젝트를 복수 개의 데이터 노드들의 위치에 기반하여 분산 저장하는 분산 저장 시스템 및 그 위치 기반 분산 저장 방법 및 컴퓨터에 의하여 독출 가능한 저장 매체 | |
US8086629B2 (en) | Content delivery apparatus, content delivery method, and content delivery program | |
JP2014044677A (ja) | 送信制御プログラム、通信ノード、および送信制御方法 | |
EP2203840A2 (en) | Exchange of syncronization data and metadata | |
US20160234129A1 (en) | Communication system, queue management server, and communication method | |
JP2004199578A (ja) | コンテンツ配信方法及び装置並びにプログラム及び記録媒体 | |
JP6011786B2 (ja) | 分散ストレージシステム、分散ストレージデータ配置制御方法及び分散ストレージデータ配置制御用プログラム | |
JP3672483B2 (ja) | コンテンツ配信装置、コンテンツ配信方法、コンテンツ配信プログラムを記録した記録媒体 | |
WO2013065151A1 (ja) | 計算機システム、データ転送方法、および、データ転送プログラム | |
CN114124971B (zh) | 一种基于边缘缓存的cdn-p2p网络的内容副本放置方法 | |
JP4064162B2 (ja) | ファイル蓄積装置および方法 | |
JP6617087B2 (ja) | 分散処理システム、分散処理方法および分散処理プログラム | |
JP2021170289A (ja) | 情報処理システム、情報処理装置およびプログラム | |
JP4483633B2 (ja) | ハードウェアリソースの状態を管理するための情報処理装置、方法及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 12864184 Country of ref document: US |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10850650 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012512540 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10850650 Country of ref document: EP Kind code of ref document: A1 |