Job Management Partner 1/Software Distribution Description and Planning Guide

[Contents][Glossary][Index][Back][Next]

2.13.1 Installing distributed software

When an Install package job is executed on the managing server, the client automatically downloads the specified software and installs it on its own system. Because software downloading and installation are both executed automatically, the client normally does not control what is installed or when it is installed.

However, if automatic job execution is not appropriate for the operation of the client user, the two alternatives indicated below in (1) and (2) are available. In addition, alternative (3), in which the client's user selects and installs software manually, is also available.

Organization of this subsection
(1) Stopping the client
(2) Managing the job execution timing
(3) Installing by selecting the software

(1) Stopping the client

Starting Windows automatically starts the client. By using Client Manager, you can also shut down the client manually. In addition, a JP1/Software Distribution Client can be set up to make the client non-resident.

A client that has not been started or is non-resident cannot receive jobs from the managing server. Therefore, in such a situation, software installation cannot be executed. However, a client's user can execute the installation job by choosing the Execute Job Backlog icon at a convenient time. For details about the handling when stopping of clients is involved, see 11.1.2 Client startup and job execution in the manual Administrator's Guide Volume 1.

(2) Managing the job execution timing

The job execution time, such as for downloading or installing a package, is normally determined by the higher server (the managing server) and is transparent to the client. The client merely waits for the package to be transferred from the managing server or for automatic installation of the software.

In this mode, however, an installation job might activate suddenly in the midst of processing at the client and cause problems. The client user can forcibly prevent a job from being executed and specify that the job be executed at the user's convenience.

The client can use the following two methods to manage job execution timing:

(a) Using the job hold and cancellation facility

A method for preventing unilateral job execution by a higher server is the job hold and cancellation facility. When a job is transferred from a server, this facility displays the Hold or Cancel Software Distribution Job dialog box so that you can choose whether to execute the job. If you do not want to execute the job immediately, you can hold it for later execution or you can cancel it.

Figure 2-59 Hold or Cancel Software Distribution Job dialog box

[Figure]

Use of the job hold and cancellation facility is specified in the setup process for the client by selecting the Confirm jobs before execution check box on the Job Options page.

The following two types of jobs can be held or canceled, provided that no execution date (package installation date or job execution date) is specified:

For details about how to hold and cancel jobs, see 11.3.1 Holding or canceling a job in the manual Administrator's Guide Volume 1.

(b) Executing a job at an arbitrary time

You can have JP1/Software Distribution Client (client) execute jobs at any time by choosing the Execute Job Backlog icon.

When the Execute Job Backlog icon is chosen, the client connects to the higher system to perform polling to determine if there are any unprocessed jobs. If such jobs exist, the client executes them. You can also use the Execute Job Backlog icon to execute jobs that were held temporarily by the job hold and cancellation facility.

You can also specify in the setup that the client is not to start automatically whenever the system starts. When this specification is in effect, the client user can execute a job at their convenience by choosing the Execute Job Backlog icon.

(3) Installing by selecting the software

Software distributed by the managing server in a Send package, allow client to choose job is not installed automatically. Instead, it arrives in a status in which its installation is permitted. The client user evaluates the need at the local system for the software items and decides whether to install them. To display a list of software programs that can be installed and then select and install the desired software, use Package Setup Manager, which is a client subcomponent.

Figure 2-60 Package Setup Manager window

[Figure]

A client for which no user information has been set might not be able to use Package Setup Manager depending on the server settings. Note that Package Setup Manager cannot be shared among multiple non-Administrator users.

For details about how to use Package Setup Manager, see 11.4 Using Package Setup Manager in the manual Administrator's Guide Volume 1.