JP2001249801A - Software installation device and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically set up software environment before generation of a fault in a newly set storage medium in a client when the fault is generated in a storage medium embedded in the client. SOLUTION: When notification that software is installed/uninstalled is received from the client connected via a network, a CPU 11 in this software installation device 10 creates a history file to store a client name, a software name and its date. And when the fault is generated in the storage medium in the client, the CPU 11 reads the software stored in installation history of the created history file from the storage medium 16 and a magnetic disk 19, outputs it to the client and makes the client install it.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software installation device used to install software on an electronic device, and a storage medium for the software installation device.

[0002]

2. Description of the Related Art When installing software in a server and a plurality of clients connected via a network, the software is installed for each machine, or the software stored in a storage medium built in the server. Is installed by each client, and a database is created and managed by each client, or software installed by the server is automatically installed on each client.

[0003]

However, when each client manages the installed software, if the storage medium (hard disk or the like) built in the client becomes unreadable for some reason, the client will not be able to read the installed software. There was a fear that it became unknown which software was stored in the past.

[0004] When all software installed by the server is automatically installed in each client, software unnecessary for a user who uses each client must be installed, and the efficiency of memory resource utilization is reduced. There was a problem of lowering.

An object of the present invention is to automatically clear software stored in a past storage medium in a new storage medium when a storage medium built into a client becomes unreadable and a new storage medium is installed. Is to install.

[0006]

According to the first aspect of the present invention,
Installation history storage means (for example, CPU 11 in FIG. 2; steps S3 to S5 of the history storage process in FIG. 4) for storing software installation history in a client connected via a network; Uninstallation history storage means for storing the installation history (for example, C in FIG. 2)
PU11; steps S7 to S8 of the history storage processing in FIG. 4)
When a failure occurs in a storage medium built in the client, software is stored in a storage medium newly installed in the client based on the history stored by the installation history storage unit and the uninstall history storage unit. Installation processing means (for example, CPU 11 in FIG. 2; clear installation processing in FIGS. 5 and 7) for installing software and automatically setting up a storage medium newly installed in the client in the software environment before the failure occurred. , Is provided.

According to the first aspect of the present invention, the installation history storage means stores the software installation history of the client connected via the network, and the uninstall history storage means stores the software installation history of the client. When a failure occurs in a storage medium built in the client, the installation processing means stores the installation history storage means in the storage medium newly installed in the client, and the uninstallation history. Software is installed based on the history stored by the storage means, and a storage medium newly installed in the client is automatically set up in the software environment before the occurrence of the failure.

Therefore, since the software installation device (server) manages the installation / uninstallation history of the client, if a failure occurs in the storage medium of the client, the software environment can be automatically set up before the failure, The clear installation time can be greatly reduced.

[0009]

Embodiments of the present invention will be described below in detail with reference to the drawings. (First Embodiment) FIGS. 1 to 5 are diagrams illustrating a software installation apparatus (hereinafter, simply referred to as a server) according to a first embodiment of the present invention. First, the configuration will be described. FIG. 1 is a block diagram showing a network configuration 1 connected to a server 10 according to the first embodiment of this invention. In FIG. 1, a magnetic disk reader 18 is connected to a server 10, and clients A to D are connected via a network 2.

FIG. 2 is a block diagram showing the internal configuration of the server 10. In FIG. 2, the server 10
Are a CPU 11, a display unit 12, a RAM 13, an input unit 1.
4, a storage device 15, a storage medium 16, a transmission control unit 17, a magnetic disk reader 18, and a magnetic disk 19.
Are connected by a bus 20. The storage medium 16 is fixedly connected to the storage device 15, while the magnetic disk 19 is detachably mounted on the magnetic disk reader 18.

CPU (Central Processing Unit) 11
Expands a system program stored in a storage medium 16 included in a storage device 15 and an application program designated from various application programs corresponding to the system in a work area in a RAM 13, RAM according to data
13 or in accordance with an application program stored in the storage medium 16, and stores the processing results in a predetermined area in the RAM 13.
It is displayed on the display unit 12. The processing result stored in the RAM 13 is input from the input unit 14 to the storage medium 16.
Save to the save destination in.

When a notification signal indicating that software is installed or uninstalled is input from each client, the CPU 11 creates a history file 21 as shown in FIG. To be stored. The history file 21 is data that summarizes the date of installation or uninstallation, the name of software (hereinafter simply referred to as software), and the name of a client. For example, according to FIG. 3, client A, on December 24, 1999,
It is stored that the software a has been installed.

[0013] When a signal requesting clear installation is input from the client, the CPU 11 reads the software installed by the client in the past from the history file 21 stored in the storage device 15. Then, the software that has not been uninstalled in the history file 21 is output to the client. At this time, when installing the software stored in the storage medium 16 on the client, the CPU 11 reads the software from the storage medium 16 and outputs the software to the client. However, when software that is not stored in the storage medium 16 is installed in the client, the CPU 11
The desired software is read from the magnetic disk 19 by the magnetic disk reader 18 and output to the client.

The display unit 12 is a CRT (Cathode Ray Tub).
e) composed of liquid crystal or plasma, etc.
The display data input from 11 is displayed.

A RAM (Random Access Memory) 13
When the CPU 11 executes the application programs stored in the storage medium 16, the CPU 11 has an area for expanding the programs, and has a work area for storing input instructions, input data, and processing results. Furthermore,
In the RAM 13, a program and various software for causing the CPU 11 to execute a history storage process and a clear install process, which will be described later, are stored in advance.
Data and the like processed by various software in response to an instruction signal from the CPU 11 are stored.

The input unit 14 includes a keyboard and a pointing device such as a mouse provided with a cursor key, numeral input keys, various function keys, and the like, and outputs to the CPU 11 a pressing signal pressed on the keyboard and a mouse position signal.

The storage device 15 has a storage medium 16 in which programs, data and the like are stored in advance, and the storage medium 16 is formed of a magnetic or optical recording medium or a semiconductor memory. The storage medium 16 is the storage device 1
5, the storage medium 16 includes various system programs, various application programs corresponding to the system, a history storage processing program,
The history file 21 generated by the clear install processing program and the history storage processing program, data processed by each processing program, document data, and the like are stored.

The programs and data stored in the storage medium 16 may be partially or wholly transmitted from another device to a transmission control unit 17 via a transmission medium such as a network line.
It may be configured to receive from and store the information.

The transmission control unit 17 has a modem (MODEM:
MOdulator / DEModulator) or a terminal adapter (TA), and controls communication with an external device via a communication line such as a telephone line or an ISDN line. The modem modulates the digital data processed by the CPU 11 into an analog signal in the frequency band of the telephone line in order to communicate with an external device such as a personal computer via the telephone line. A terminal adapter converts an existing interface into an interface corresponding to ISDN in order to communicate with an external device such as a personal computer via an ISDN line. It is a device to do.

The magnetic disk reader 18 includes a CPU 11
When a read instruction is input from the CPU 11, the contents stored in the magnetic disk 19 are read and output to the CPU 11. The magnetic disk 19 stores programs and data in advance, and can be detachably mounted on the magnetic disk reader 18.

Next, the operation of the first embodiment will be described. History storage processing executed by the CPU 11,
The clear install process will be described with reference to the flowcharts shown in FIGS. Here, a program for realizing each function described in these flowcharts is stored in a recording medium (storage medium 16 or magnetic disk 19) in the form of a readable program code. Perform actions according to the code sequentially. Also, CPU
11 can also sequentially execute the operation according to the above-mentioned program code transmitted via the transmission medium. That is, an operation unique to this embodiment can be executed using a program / data externally supplied via a transmission medium in addition to a recording medium.

FIG. 4 is a flowchart illustrating a history storage process executed by the CPU 11 in the server 10 when the client A installs or uninstalls the software a in the network configuration 1. C
The PU 11 creates and updates the history file 21 shown in FIG. 3 by the history storage processing.

In FIG. 4, the client A selects whether to install or uninstall the software a (step S1). In step S1,
When installing, when the client A installs the software a (step S2), the client A outputs a software a installation notification to the server 10.

When the server 10 receives the installation notification of the software a from the client A, the server 10 reads the history file 21 stored in the storage medium 16 and checks whether or not the installation history of the client A includes the software a. (Step S3). If not, the server 10 adds the software a and the installation date to the installation history of the client A (step S4).

In step S3, if there is a record of installing software a in the installation history of client A, the software a and date in the installation history of client A are overwritten (step S5).

On the other hand, when the client A uninstalls the software a in step S1, when the client A uninstalls the software a (step S6), the client A outputs a notification that the software a has been uninstalled to the server 10.

When the server 10 receives the uninstallation notification of the software a from the client A, the server 10
Then, the history file 21 stored in the client 6 is read, and it is determined whether or not the installation history of the client A includes the software a (step S7).

In step S7, if there is no software a in the installation history of client A, the process is terminated. If there is, the date of uninstalling software a of client A in history file 21 is added (step S7).
8), end.

Next, when the storage medium built in the client A shown in FIG. 1 becomes unreadable, the server 1
The clear installation process executed by the CPU 11 of the CPU 0 based on the history file 21 shown in FIG. 3 will be described below with reference to the flowchart shown in FIG.

First, the CPU 11 sets the arguments i, j, k to "i = 1, k = 0, j = 0", respectively (step S10). Then, it is confirmed whether or not a signal requesting clear installation has been input from the client A (step S11). If not, the process ends.

In step S11, if a clear install request signal has been input, the CPU 11 reads the history file 21 from the storage medium 16 and numbers the software to be installed on the client A.

That is, the CPU 11 sets the history file 21
Is searched for software i, that is, the "i = 1" -th software (step S12). As a result, software a has j
= 0 (that is, software 0) is determined. Next, the CPU 11 adds 1 to the argument j to make j = 1 (step S13), and adds 1 to the argument i to make i = 2 (step S14).

Next, the CPU 11 checks whether or not i = EOF is satisfied (step S15). According to the history file 21 of FIG. 3, the final code of the installation history of the client A is EOF = 5. However, since i = 2 at this stage, the condition of step S15 is not satisfied. Therefore, the process returns to step S12 to search for the “i = 2” th software, and assigns a number j = 1 (ie, software 1) to the software b.

Thus, steps S12 to S15 are repeated until i = EOF is satisfied. Thus, the numbers “0 to 3” are given to the software a to d, respectively.

When the condition is satisfied in step S15, C
The PU 11 checks whether or not the software k (= 0 = software a) in the history file 21 has an uninstall history (step S16). If the software k has an uninstall history, the process proceeds to step S19.

In step S16, the client A
If there is no uninstall history of software k, CPU
11 judges that the software k is to be installed in the client A, and searches whether or not the storage medium 16 has the software k. If so, the software k is output to the client A and installed (step S18). If there is no software k in the storage medium 16, the magnetic disk 19 storing the software k is set in the magnetic disk reader 18 (step S17), and the software k is installed in the client A (step S18).

When the installation of the software k on the client A is completed, the CPU 11 adds 1 to the argument k and sets
= 1 (step S19). Then, it is determined whether or not the argument k matches the final value (j = 4) of the argument j (step S20). If not, steps S16 to S2
Repeat 0. If the value of the argument k matches the final value of the argument j, the process ends.

As described above, in the first embodiment,
The CPU 11 of the server 10 stores a software installation / uninstallation history of a client connected via the network 2. If the storage medium of the client becomes unreadable, the CPU 11
Reads the software stored in the installation history of the client in the history file 21 from the storage medium 16 or the magnetic disk 19 and performs a clear installation on the storage medium newly installed in the client. Therefore,
The client can be automatically set up in a pre-failure environment.

(Second Embodiment) A software installation apparatus (hereinafter, simply referred to as a server) according to a second embodiment of the present invention will be described with reference to FIGS. FIG. 6 is a block diagram illustrating a network configuration 3 connected to the server 10. In FIG. 6, each of the clients A to D communicates with the server 1 via the network 2.
0 is connected. Note that the server 10 in the second embodiment has the same configuration as the server 10 shown in FIG. 2 in the first embodiment, and thus illustration and description thereof are omitted.

However, the magnetic disk reader 18 according to the second embodiment includes four magnetic disk readers 18a to 18d as shown in FIG. 6, and sets a plurality of magnetic disks at one time. Storage area, and a plurality of magnetic disks can be read by a magnetic disk reader 18a.
It has a disc changer that sets / unsets to ~ 18d. Then, the magnetic disk reader 18
According to an instruction signal input from the PU 11, a specified magnetic disk is selected from a plurality of magnetic disks,
When set in the designated magnetic disk readers 18a to 18d, the designated software is read and output to the CPU 11.

Therefore, in the second embodiment, the CPU
11 is a history file 21 created by the history storage process
When the software is clearly installed on the client based on the above, the magnetic disk storing the software is automatically selected and set in the magnetic disk readers 18a to 18d. Hereinafter, a clear installation process when a plurality of magnetic disks can be set will be described based on the history file 21 shown in FIG.

FIG. 7 is a flowchart showing a clear installation process executed by the CPU 11 in the server 10 in the second embodiment. In FIG. 7, CP
U11 sets the arguments i, j, k, and m to "i = 1, j = 0, k
= 0, m = 0 ”(step S30), and it is determined whether a clear install request signal has been input from the client A (step S31). If the input has not been made, the present process ends.

If a clear install request signal has been input in step S31, the CPU 11 reads the history file 21 stored in the storage medium 16 and searches for the i-th software (step S32). Thus, the number j = 0 is given to the software a.

Subsequently, 1 is added to the argument j and 1 is added to the argument i (step S33). Therefore, the argument j is 1,
The argument i becomes 2. Next, the CPU 11 determines whether or not i = EOF (step S34). If this condition is not satisfied, the process returns to step S32, and the process returns to step S3.
Steps 2 to S34 are repeated until the condition of i = EOF is satisfied. In this way, the numbers “0 to 3” are assigned to the software a to d written in the history file 21.

In step S34, if the condition i = EOF is satisfied, the CPU 11 determines whether or not to install the software k (= 0 = software a) from the uninstallation history of the history file 21 (step S35). ).

Then, in the case of installation, the array (k) (ie, array (0)) is set to 1 (step S3).
6). That is, the code “1” of “install” is added to the number k (= 0) characterizing the software a.
On the other hand, when the software k is not installed, the array (k) is set to 0 (step S37). That is, the code “0” of “do not install” is added to the number k (= 0) characterizing the software a.

Next, the CPU 11 adds 1 to the argument k (step S38), and sets the argument k to 1. Then, it is determined whether or not the argument k is the final value of the argument j (j = 4) (step S39). If the condition of k = j is not satisfied, the steps S35 to S39 are changed to the condition of k = j. Repeat until satisfied.

If the condition of k = j is satisfied in step S39, the CPU 11 determines whether or not the array (m) is "1" (step S40). That is, the number m
It is determined whether the code added to (= 0 = software a) is “1”, that is, “install”. Array (m) =
If it is not 1, the process proceeds to step S43.

If the array (m) = 1 at step S40, the CPU 11 searches the storage medium 16 for software corresponding to the number m, and calls the software m. Then, if the client A can be installed, the software m is output to the client A and installed (step S42). If the client A is not in the installable state, the CPU 11 waits until a notification signal indicating the installable state is input from the client A.

On the other hand, if the software m does not exist in the storage medium 16, the CPU 11 outputs an instruction signal to the magnetic disk reader 18 to select the magnetic disk 19 storing the software m and read the magnetic disk readers 18a to 18d. (Step S41), and the software a is read. If the client A can be installed, the software m is output to the client A and installed (step S42). If the client A is not in an installable state, it waits until a notification signal indicating that the client A is in an installable state is input.

When the software m is output to the client A,
The CPU 11 adds 1 to the argument m (step S4
3), the argument m is set to 1; Then, it is determined whether or not m = j (final value of j) is satisfied (step S44). If not, step S40 is performed until the condition of m = j is satisfied.
To S44 are repeated to output all the software having the code of “1” to the client A and install it.

When m = j is satisfied in step S44, the CPU 11 terminates this processing.

As described above, in the second embodiment,
The CPU 11 performs an operation of checking whether or not all software written in the installation history of the client A in the history file 21 is installed before actually installing the software. Accordingly, the CPU 11 reads the next software m + 1 from the storage medium 16 while the client A is installing the software m, or transfers the magnetic disk 19 storing the software m + 1 to the magnetic disk readers 18a to 18d. It can be set and wait, and the clear installation process can be executed more efficiently.

Also, since four magnetic disk readers 18 are provided, even if the magnetic disk storing the software currently being installed is set in the magnetic disk reader, the magnetic disk storing the software to be installed next will not be replaced. It can be set in advance.

Further, since the magnetic disk reader 18 has a plurality of magnetic disk storage areas and can select the specified magnetic disk 19 in accordance with an instruction signal input from the CPU 11, all the steps of the clear install process can be performed. It can be completed without human intervention.

The present invention is not limited to the contents shown in the first and second embodiments, but can be appropriately changed without departing from the spirit of the present invention. For example,
In the history storing process, when uninstalling software possessed by the client, the date is added to the uninstall history of the history file. However, the software may be deleted from the installation history.
At that time, in the clear installation process, all software stored in the installation history of the designated client read from the history file may be changed to be installed on the client.

In the second embodiment, the magnetic disk reader 18 is provided with four magnetic disk readers. However, the present invention is not limited to this number, and is not limited to this number. Of course, it can be changed according to the number or the number of magnetic disks to be accommodated.

[0058]

According to the software installation apparatus of the first aspect and the storage medium of the third aspect, a software installation / uninstallation history in a client connected via a network can be stored. When a failure occurs in the storage medium of the client, the software environment can be automatically set up before the failure based on the stored installation / uninstallation history.

According to the software installation apparatus of the second aspect of the present invention, software installation / uninstallation histories in a plurality of clients can be stored. Automatic setup according to installation / uninstallation history is possible.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a network configuration 1 according to a first embodiment of the present invention.

FIG. 2 is a block diagram showing an internal configuration of the server 10.

FIG. 3 is a diagram illustrating a history file 21 generated by a CPU 11 in a history storage process.

FIG. 4 is a flowchart illustrating a history storage process executed by a CPU 11;

FIG. 5 is a flowchart illustrating a clear installation process executed by a CPU 11 in the first embodiment.

FIG. 6 is a block diagram showing a network configuration 3 according to the second embodiment.

FIG. 7 is a flowchart illustrating a clear installation process executed by a CPU 11 according to the second embodiment.

[Explanation of symbols]

 Reference Signs List 1 network configuration 2 network 3 network configuration 10 server 11 CPU 12 display unit 13 RAM 14 input unit 15 storage device 16 storage medium 17 transmission control unit 18 magnetic disk reader 19 magnetic disk 20 bus 21 history file

Claims (3)

[Claims] 1. An installation history storage unit for storing software installation history in a client connected via a network, an uninstallation history storage unit for storing software uninstallation history in the client, and When a failure occurs in the built-in storage medium, the software is installed on the storage medium newly installed in the client based on the history stored by the installation history storage unit and the uninstall history storage unit, A software installation device, comprising: installation processing means for automatically setting up a storage medium newly installed in the client in a software environment before a failure occurred. 2. The installation history storage means includes an installation history file for storing a previous installation history corresponding to a plurality of clients, and the uninstall history storage means stores the uninstall history corresponding to a plurality of clients. The installation processing unit performs automatic setup of the software environment corresponding to each of a plurality of clients based on the installation history file and the uninstallation history file. Item 2. The software installation device according to item 1. 3. A storage medium storing a computer-executable program for performing software installation on a client connected via a network, and storing a software installation history in the client. A computer-executable program code, a computer-executable program code for storing a software uninstallation history in the client, and a failure in a storage medium built in the client. A computer for installing software on a storage medium newly installed on the client based on the stored history and automatically setting up the storage medium newly installed on the client in the software environment before the failure occurred. Storage medium characterized by but storing a program comprising a program code executable.