Software management process, software management apparatus, and computer-readable medium storing software management program

• US 8,255,893 B2
• Filed: 04/26/2007
• Issued: 08/28/2012
• Est. Priority Date: 09/05/2006
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Savva, Andreas
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Chowdhury, Ziaul A
• Application Number:
  US11/790,661
• Publication Number:
  US 20080059953A1
• Time in Patent Office: 1,951 Days
• Field of Search: None
• US Class Current: 717/168
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

In a software management process, a software management apparatus, and a computer-readable medium storing a software management program for managing software installed in clients: a profile for a client is updated in accordance with a change notice on receipt of the change notice from the client; settings of the software in other clients which belong to the same group as the above client are determined to be synchronized with the settings of the software in the above client by reference to group information when the above profile for the above client is updated; and a synchronization notice indicating that the update of the above profile is to be reflected in the settings of the software in the other clients is sent to the other clients, and each of one or more profiles for the other clients is updated in accordance with the synchronization notice.

Claims

1. A software management process for managing software installed in a plurality of client apparatuses, the software management process being executed by a computer, comprising:

(a) receiving from a first client apparatus among the plurality of client apparatuses a first change notice and updating a first profile for a first client apparatus among a plurality of profiles for the plurality of client apparatuses in accordance with the first change notice, where the plurality of profiles are respectively stored and respectively contain information on settings of said software installed in the plurality of client apparatuses, the first change notice indicating that the settings of said software installed in the first client apparatus are changed by the first client apparatus;

(b) referring to group information, which is stored and defines one or more groups each including one or more of said plurality of client apparatuses, and determining one or more second client apparatuses which belong to a same group as the first client apparatus, when the first profile is updated;

(c) sending to said one or more second client apparatuses a first synchronization notice indicating that a first change of the settings indicated by the first change notice is to be reflected in the one or more second client apparatuses;

(d) adding, when receiving from a second client apparatus among said one or more second client apparatuses a response indicating refusal of the first change of the settings, to a second profile for the second client apparatus a refusal record indicating the refusal of the first change of the settings; and

(e) omitting, when receiving a second change notice indicating a second change of the settings which is a same type as the first change of the settings, the second client apparatus from destinations of a second synchronization notice indicating that the second change of the settings is to be reflected, in accordance with the refusal record added to the second profile.

2. The software management process according to claim 1, wherein when a response indicating acknowledgment of the first change of the settings is received from another second client apparatus among said one or more second client apparatuses, another second profile for said another second client apparatus is updated in accordance with the acknowledgment.

3. The software management process according to claim 2, wherein when a failure occurs in communication with the one or more second client apparatuses in said (c), said one or more second client apparatuses are continuously monitored after the failure, and said first synchronization notice is sent to the one or more second client apparatuses when the communication with the one or more second client apparatuses becomes possible.

4. The software management process according to claim 2, wherein when the response indicating the refusal is received from the second client apparatus, a report of a failure in synchronization is displayed on a display device.

5. The software management process according to claim 1, further comprising,

(f) when a registration request designating a type of software is received from one of said plurality of client apparatuses before the (a), referring to an item list indicating one or more setting items which are to be included in said plurality of profiles for each type of software, and sending an item list for said type of software designated by said registration request to said one of said plurality of client apparatuses, and

(g) when information on settings corresponding to said item list for said type of software designated by said registration request is received from said one of the plurality of client apparatuses after the (f), producing one of said plurality of profiles for the one of the plurality of client apparatuses on a basis of the information on the settings corresponding to the item list for the type of software designated by the registration request, and storing the produced one of the plurality of profiles.

6. A software management apparatus for managing software installed in a plurality of clients, comprising:

a storage which stores a plurality of profiles for the plurality of clients, where each of the plurality of profiles contains information on settings of said software installed in one of the plurality of clients corresponding to said each of the plurality of profiles, and stores group information defining one or more groups each including one or more of said plurality of clients; and

a processor configured to perform a procedure comprising;

receiving from a first client among the plurality of clients a first change notice and updating a first profile for the first client among the plurality of profiles in accordance with the first change notice, the first change notice indicating that the settings of said software installed in the first client are changed by the first client;

referring to the storage, and determining one or more second clients belonging to a same group as the first client when the first profile is updated;

sending to said one or more second clients a first synchronization notice indicating that a first change of the settings indicated by the first change notice is to be reflected in the one or more second clients;

adding, when receiving from a second client among said one or more second clients a response indicating refusal of the first change of the settings, to a second profile for the second client a refusal record indicating the refusal of the first change of the settings; and

omitting, when receiving a second change notice indicating a second change of the settings which is a same type as the first change of the settings, the second client from destinations of a second synchronization notice indicating that the second change of the settings is to be reflected, in accordance with the refusal record added to the second profile.

7. The software management apparatus according to claim 6, wherein when the software management apparatus receives from another second client among said one or more second clients a response indicating acknowledgment of the first change of the settings, the processor updates another second profile for said another second client in accordance with the acknowledgment.

8. The software management apparatus according to claim 7, wherein the processor starts continuous monitoring of said one or more second clients when the processor fails in communication with the one or more second clients, and sends the first synchronization notice to the one or more second clients when the processor detects that communication with the one or more second clients becomes possible.

9. The software management apparatus according to claim 7, wherein when said software management apparatus receives from the second client the response indicating the refusal, the processor displays in a display device a report of a failure in synchronization.

10. The software management apparatus according to claim 6, wherein:

the storage stores, for each type of software, an item list indicating one or more setting items which are to be included in said plurality of profiles, and

the procedure further comprises referring to the storage and sending to one of said plurality of clients an item list for a type of software designated by a registration request when the software management apparatus receives from the one of said plurality of clients the registration request designating the type of software, and thereafter producing one of said plurality of profiles for the one of the plurality of clients on a basis of information on settings corresponding to said item list for the type of software designated by the registration request and storing the produced one of the plurality of profiles in the storage when the software management apparatus receives from the one of the plurality of clients the information on settings corresponding to said item list for the type of software designated by the registration request.

11. A computer-readable, non-transitory medium storing a software management program for managing software installed in a plurality of clients, the software management program causing a computer to perform a method comprising:

receiving from a first client among the plurality of clients a first change notice and updating a first profile for the first client among a plurality of profiles for the plurality of clients in accordance with the first change notice, the plurality of profiles being stored in a storage and containing information on settings of said software in the plurality of clients, the first change notice indicating that the settings of said software installed in the first client are changed by the first client;

referring to group information which is stored in the storage and defines one or more groups each including one or more of the plurality of clients, and determining one or more second clients belonging to a same group as the first client, when the first profile is updated;

sending to said one or more second clients a first synchronization notice indicating that a first change of the settings indicated by the first change notice is to be reflected in the one or more second clients;

adding, when receiving from a second client among said one or more second clients a response indicating refusal of the first change of the settings, to a second profile for the second client a refusal record indicating the refusal of the first change of the settings; and

omitting, when receiving a second change notice indicating a second change of the settings which is a same type as the first change of the settings, the second client from destinations of a second synchronization notice indicating that the second change of the settings is to be reflected, in accordance with the refusal record added to the second profile.

12. The computer-readable, non-transitory medium according to claim 11, wherein when the computer receives from another second client among said one or more second clients a response indicating acknowledgment of the first change of the settings, the computer updates another second profile for said another second client in accordance with the acknowledgment.

13. The computer-readable, non-transitory medium according to claim 12, wherein the computer starts continuous monitoring of said one or more second clients when the computer fails in communication with the one or more second clients, and sends the first synchronization notice to the one or more second clients when the computer detects that communication with the one or more second clients becomes possible.

14. The computer-readable, non-transitory medium according to claim 12, wherein when the computer receives from the second client the response indicating the refusal, the computer displays in a display device a report of a failure in synchronization.

15. The computer-readable, non-transitory medium according to claim 11, wherein:

the storage stores, for each type of software, an item list indicating one or more setting items which are to be included in said plurality of profiles, and

the method further comprises referring to the storage and sending to one of said plurality of clients an item list for a type of software designated by a registration request when the computer receives from the one of said plurality of clients the registration request designating the type of software, and thereafter producing one of said plurality of profiles for the one of the plurality of clients on a basis of information on settings corresponding to said item list for the type of software designated by the registration request and storing the produced one of the plurality of profiles in the storage when the computer receives from the one of the plurality of clients the information on settings corresponding to said item list for the type of software designated by the registration request.

16. The computer-readable, non-transitory medium according to claim 11, wherein the storage stores one or more files necessary for execution of said software, and the computer acquires from the storage a file and sends the file together with said first synchronization notice to said one or more second clients when the first change of the settings indicated by the first synchronization notice includes addition of said file.

17. The computer-readable, non-transitory medium according to claim 16, wherein the storage stores information on a license for said software, and the computer refers to the information on the license when the computer acquires said file from the storage, and sends the file together with said first synchronization notice to each of said one or more second clients only when said addition of the file in said each of the one or more second clients does not violate the license.