Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 - Agent (For UNIX Systems)


2.3.2 Notes on package distribution

Note the following at package distribution.

Organization of this subsection

(1) Stopping the system during package distribution

If you stop the system during package distribution, an error, such as a communication error, occurs. If you stop the system during installation, the package at the installation destination might be damaged. Before you stop the system, confirm the users of the managing server that JP1/IT Desktop Management 2 - Agent is not currently executing package distribution.

(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 package distribution 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.

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) 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 9.1 Checking failure information by messages in PART 4.

(5) 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:

(6) Owner of the package and group

If the owner or the group of the file or directory that was packaged by using the rdscm command is an undefined owner or group of the distribution-destination system, this package cannot be distributed. In this case, if an installation directory that does not exist in the distribution-destination system is specified, the installation directory will not be created either.

(7) Directory attributes of the installation directory

During package distribution, if the installation directory is an existing directory, the directory attribute of the installation directory might temporarily change during distribution as shown below:

(8) Distributing packages compressed in high level

If a package was packaged by a Windows packager using High level as the compression method, you cannot distribute the package to a UNIX distribution-destination system.

(9) Simultaneously distributing multiple software packages provided by other companies

If you are distributing software programs provided by other companies from the managing server, remember that the simultaneous distribution of more than one software package provided by other companies with just one job is not possible. You have to use one job to distribute each one of the software packages.

(10) Distributing an rpm file to Linux agents

You cannot distribute multiple RPM files at one time.