To use the external program processing after market software installation:
1. Create the program of the external program processing after market software installation and distribute it to the distribution-destination systems.
Create the external program processing after market software installation to return the following return codes after the processing:
Normal end: 0
Abnormal end: Other than 0
Note the following when you create the external program processing after market software installation:
• Do not include spaces in command path names (except for command arguments).
• The external program processing after market software installation is started by a user with superuser permissions.
• Do not include processing that waits for responses.
• Do not output messages to the standard output and the standard error output.
• The environment variables are inherited from the ones that are active when JP1/IT Desktop Management 2 -Agent is operating.
• To implement file operations, such as copying files and logging records to a file, in an external program that will be executed after software installation, make sure that the files are specified with their absolute path names.
2. In the packaging-information file, set the following attribute:
APafterGeneration path-name-of-external-program-processing-after-market-software-installation
Use the absolute path name to specify the path name of the external program processing after market software installation. However, if you create the processing under the /NETMRDS/usrcom/ or /opt/NETMDMW/
usrcom/ (for HP-UX) directory, you can use the relative path name.
Even if the external program processing after market software installation ends abnormally, the setup of the distributed program product is normally ended.
2.2.4 Notes on packaging
• When registering the software under the /tmp directory, grant the users with the reference, update, and execute privileges so all the users can access the /tmp directory.
• The file attributes of the distributed packages (user IDs, ID groups, access modes) are the same as those of the packager.
• Start the system as a superuser when registering Hitachi program products, another company's software, and OS patches. Any user can start the system when registering user programs and user data.
• You cannot package a resource from an end workstation to JP1/IT Desktop Management 2 - Agent (relay system) (for Windows).
• If another distribution-destination system is currently registering a resource into the cabinet that you attempt to register a resource into, you cannot register the resource. When the KDDM1528-Q message is displayed, press the Return key to re-execute registration.
• Packages registered to a Windows managing server by setting the prerequisite version, pre-installation process programs, and monitoring time will be invalid, regardless of whether the distribution-destination is a Windows or UNIX machine.
• When registering a Hitachi program product and distributing it from JP1/IT Desktop Management 2 - Manager, do not change the contents of the following programs if they are specified for external program processing after market software installation (external programs that are to be started immediately following installation):
• For a Hitachi program product not for HP-UX: /NETMRDS/COM/ppsetup
• For a Hitachi program product for HP-UX: /opt/NETMDMW/lbin/ppsetup
• If the higher system is a relay system (client workstation), the software is installed to the relay system. To perform packaging to the managing server, change the settings so that the relay system is directly connected to the managing server (end workstation) beforehand.
• JP1/IT Desktop Management 2 - Agent for UNIX can be used to remotely install Hitachi program products as a whole or in part. However, when packaging program products for distribution, you must package program products as a whole. (You cannot package only part of a program product.) In addition, when you use the rdslst command to display the ID of the whole or part of a program product, the IDs are not displayed in a hierarchy but are displayed on the same line.
2.3 Package distribution
To distribute a package, register a distribution job that specifies the package to be distributed and the distribution destination in the managing server.
There are many types of distribution jobs depending on the distribution method. In this manual, they are generically referred to as a distribution job. This section describes the procedure for distribution of a package from a package storehouse of the managing server to the distribution destination system.
When the distribution job is executed, the package is distributed in the following sequence.
1. The managing server starts the relay system or end workstation, and then sends the distribution job.
2. The relay system or the end workstation executes the rdsft -a command to check whether there is any distribution job on the managing server. If there is a distribution job, package distribution is started according to the specification of the job.
3. After starting JP1/IT Desktop Management 2 - Agent (distribution-destination system) according to the distribution job, the relay system distributes the package to the client workstation.
If the client workstation is not active, JP1/IT Desktop Management 2 - Agent (distribution-destination system) is started when the client workstation starts. Then the distribution request is given to the relay system, and package distribution is automatically executed.
The distributed package is normally installed into the distribution-destination system automatically. However, you might sometimes need to perform installation operations at the distribution destination system.
If an error occurs during distribution, distribution is re-executed as follows after recovery from the error:
• If the error occurs between the managing server and a lower-level system, package distribution is re-executed from the point at with distribution was interrupted.
• If the error occurs between the relay system and the client, package distribution is re-executed from the beginning of the package.
2.3.1 Checking whether a distribution job exists
The end workstation executes the rdsft -a command to check whether there is a distribution job on the managing server for the local UNIX machine. If there is a distribution job, the package is distributed according to the contents of the job. If there is no distribution job, the process ends. When the distribution process is executed, the program name of the distributed package is output to the log file.
When the client workstation starts, JP1/IT Desktop Management 2 - Agent (distribution-destination system)
automatically executes the rdsrf -a command to check whether there is a distribution job from the relay system. If there is a distribution job, the package is distributed to the client workstation according to the contents of the job. When the distribution process is executed, the program name of the distributed package is output to the log file. If no distribution job is found, monitoring for jobs continues. Monitoring is retried at the time interval specified in
WatchTimeofOrders of the settings file.
If an error occurs during processing of multiple distribution jobs for the local UNIX machine, one of the following will occur:
• If an error occurs during installation
That distribution process is canceled, and the processing of another distribution job is executed.
• If an error occurs during communication with the managing server
All the processes are canceled immediately.
Execute the following commands to stop a package distribution that was started with the rdsma -a command or the rdsrf -a command, or to resume distribution after a stop:
• End workstation: rdsma -q command (stop), rdsma -a command (resume)
• Client workstation: rdsrf -q command (stop), rdsrf -a command (resume)
2.3.2 Notes on package distribution
Note the following at package distribution.