3.3.1 Installing
This subsection describes the procedure for installing APM.
- Organization of this subsection
(1) In UNIX
Before you install APM, specify kernel parameters. For details, see C.2 Kernel parameters of APM.
There are two ways to install the program. One method uses Hitachi Program Product Installer, and the other uses JP1/Software Distribution. If a remote installation by JP1/Software Distribution fails, use Hitachi Program Product Installer to install the program. You need superuser permissions to install the program.
(2) In Windows
There are two ways to install the program. One method uses the installation medium, and the other uses JP1/Software Distribution. If online distribution by JP1/Software Distribution fails, use the installation medium to install the program. You need Administrator permissions to install the program.
To install the program from installation media:
-
Install any required software if necessary.
-
Exit all the software.
-
Set the installation media.
Follow the instructions provided by the installer that starts up.
(3) Notes on installation
-
Install the required software before installing APM.
-
In Windows, if the services indicated below are running, stop them before installing or applying patches to APM. If you have accessed Control Panel and then Administrative Tools to open the Service window, close it before installing this program or applying patches to this program.
-
SNMP System Observer - Agent for Process service
-
SNMP Service service
-
-
You can upgrade APM by performing an overwrite installation.
-
You must not interrupt the program while installing APM.
-
In Windows, after installing APM, the daemon processes of APM will not be running. Start these processes as appropriate to the environment in use. In UNIX, after installing APM, the daemon processes of APM will be running.
-
In UNIX, during an overwrite installation, the apmstart file (in systems other than Linux) or sub_apmstart file (in Linux) provided by APM is overwritten. If you have customized the SNMP reception port number in the apmstart file (in systems other than Linux) or sub_apmstart file (in Linux), you must re-customize the port number after the overwrite installation.
-
Error data collection commands are customizable shell script files. If you perform an overwrite installation of a regular version of this product or if you apply a modified version of this product, $APM_BIN\jp1apmlog.bat or $APM_BIN/jp1apmlog.sh is not updated, but $APM_NEWCONF\jp1apmlog.bat or $APM_NEWCONF/jp1apmlog.sh is updated to preserve any user customization. Follow the procedure described below to manually replace the modules and then customize the files as needed.
In Windows
-
Save $APM_BIN\jp1apmlog.bat under any different name.
Example:
RENAME $APM_BIN\jp1apmlog.bat $APM_BIN\org_jp1apmlog.bat
-
Copy $APM_NEWCONF\jp1apmlog.bat.
Example:
COPY /A $APM_NEWCONF\jp1apmlog.bat $APM_BIN\jp1apmlog.bat
-
Apply any previous customization to $APM_BIN\jp1apmlog.bat as necessary.
-
Delete $APM_BIN\org_jp1apmlog.bat if you do not need it.
Example:
DEL $APM_BIN\org_jp1apmlog.bat
In UNIX
-
Save $APM_BIN/jp1apmlog.sh under any different name.
Example:
mv $APM_BIN/jp1apmlog.sh $APM_BIN/org_jp1apmlog.sh
-
Copy $APM_NEWCONF/jp1apmlog.sh.
Example:
cp -p $APM_NEWCONF/jp1apmlog.sh $APM_BIN/jp1apmlog.sh
-
Apply any previous customization to $APM_BIN/jp1apmlog.sh as necessary.
-
Delete $APM_BIN/org_jp1apmlog.sh if you do not need it.
Example:
rm $APM_BIN/org_jp1apmlog.sh
-