Job Management Partner 1/Software Distribution Client Description and User's Guide

2.4.6 Note on remote installation

Note the following at remote installation.

Organization of this subsection

(1) Stopping the system during remote installation

(2) Installing packages during system operation

(3) Overwriting distributed packages

(4) Initializing the temporary package storehouse automatically

(5) Messages that are issued during command processing by the client workstation

(6) Installation result from installation at system startup or system shutdown

(1) Stopping the system during remote installation

If you stop the system during remote installation, an error, such as a communication error, occurs. If you stop the system during installation, the package at the installation destination may be damaged. Before you stop the system, confirm the users of the managing server that JP1/Software Distribution Client is not currently executing remote installation.

(2) Installing packages during system operation

When you install a package during system operation, installation fails if it is executed while the target package is being started or used. Before you perform remote installation during system operation, check that the distribution-destination system is not currently using the package to be distributed.

(3) Overwriting distributed packages

Distribution is not usually executed if a job is issued to distribute the package which has the same name as the package that is already installed in the local system. However, distribution is executed when you specify overwriting at distribution.

This is also true for installation via the temporary package storehouse in a relay system. Even if you distribute a package that has the same name as a package that is already stored in the storehouse, the package is distributed to the clients when you specify overwriting at distribution (overwrite installation ). However, because overwrite installation creates more package transfer traffic and results in a longer transfer time than normal installation, we do not recommend that you perform overwrite installation to distribute a package to many clients. The following procedure shows how you can distribute a package to many clients efficiently:

For the relay system, execute a Transfer package to relay system job with overwriting specified.

Delete the user resource installation information for the target clients.

Use normal installation to distribute the package.

Overwrite installation of a package should be performed on a specific distribution-destination system for recovery purposes as a protection, for example, against the inadvertent deletion of files in the package after installation.

However, for the Solaris version of another company's software, overwriting is not performed even when a package which has the same name as a package that is already installed in the local system is distributed with overwriting specified. To perform overwriting in this case, you must edit the installation management file. For details, see the documentation for the OS.

(4) Initializing the temporary package storehouse automatically

If storage processing is executed when no package is stored in the temporary package storehouse, the storehouse is initialized and then new packages are stored.

If there is no file that manages the packages in the temporary package storehouse, the storehouse is automatically initialized.

(5) Messages that are issued during command processing by the client workstation

Messages that are issued during command processing by the client workstation are not displayed on the screen, but are stored in the following files. For details about the messages that are output during command processing, see 12.1 Checking failure information by messages in PART 4.

MAIN.LOGF file
For systems other than HP-UX: /NETMRDS/rdsprm/MAIN.LOGF
For HP-UX: /var/opt/NETMDMW/rdsprm/MAIN.LOGF

PPINS.LOGF file
For systems other than HP-UX: /NETMRDS/rdsprm/PPINS.LOGF
For HP-UX: /var/opt/NETMDMW/rdsprm/PPINS.LOGF

(6) Installation result from installation at system startup or system shutdown

When BOOT or SHUTDOWN is specified for the installation timing, the installation result is sent to the managing server at the following timing:

For a relay system or client workstation
The installation result is sent when the machine is booted up next time.

For an end workstation
The installation result is sent when the system is connected to the managing server next time.

[Contents][Back][Next]

[Trademarks]