Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Servicecontrol Manager 3.0 User's Guide > Chapter 2 Installing HP Servicecontrol Manager

Installing Servicecontrol Manager on Linux

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

This section provides steps to successfully install the Servicecontrol Manager (SCM) central management server (CMS) on a server running a supported version of Linux. “System Requirements” to verify which versions of Linux are supported.

If you are installing SCM on HP-UX, see “Installing Servicecontrol Manager on HP-UX”.

The CMS install procedure for Linux utilizes a bin file (self-extracting tar files) to simplify the process. Using the bin files automatically installs all the rpm files in the correct order. You can extract the rpm files from the bin files and install them manually if preferred.

Before You Install CMS Software on a Linux Server

Before you install SCM, you need to verify which version of several dependent software packages are installed. Based on this information, you may be able to skip portions of the SCM install.

NOTE: If you need to remove Tomcat or MySQL, verify that it isn’t being used by another application. If one or both of these applications cannot be removed, you must select a different server to be the CMS.

Procedure 2-4 To verify dependent software packages:

  1. Verify that Tomcat version 4.1.12 is installed:

    rpm -q tomcat4 xml-commons xml-commons-apis

    If a different version is installed, you need to remove it.

    To remove Tomcat:

    1. Uninstall the Tomcat products:

      rpm -e tomcat4 xml-commons xml-commons-apis

    2. Verify that Tomcat is removed:

      rpm -q tomcat4 xml-commons xml-commons-apis

    3. Remove or rename the following Tomcat directories if they exist:

      /var/tomcat

      /etc/tomcat

    NOTE: If you plan to install using the bin files, you may skip the remaining verification steps. See “Installing CMS Software on a Linux Server” to continue with the installation.
  2. Verify that MySQL version 3.23 is installed:

    rpm -qa | grep mysql

    If the correct version of MySQL is already installed, you can skip installing it during the CMS software installation. If a different version is installed, you need to remove it before installing SCM.

    To remove MySQL:

    1. Identify the MySQL product names including MySQL, MySQL server, MySQL shared, and MySQL client:

      rpm -qa | grep mysql

    2. Uninstall the MySQL products that you identified in step a:

      rpm -e mysql_product1 mysql_product2 mysql_product3

      where mysql_product1 mysql_product2 mysql_product3 are the names of each of the products.

    3. Verify that MySQL is removed:

      rpm -qa | grep mysql

  3. Verify that Java SDK version 1.4 is installed:

    rpm -q j2sdk

    If the correct version of Java SDK is already installed, you can skip installing it during the manual CMS software installation. If a different version is installed, multiple versions of Java SDK can coexist on the same Linux server.

Installing CMS Software on a Linux Server

This installation process includes installing Java SDK, MySQL, and Tomcat in addition to SCM. To install the CMS software, you can either:

  • automatically install the CMS software using the bin files

  • manually install the CMS software using individual rpm files

Procedure 2-5 To automatically install the CMS software on a Linux server:

  1. Download the required bin files identified below to the local file system or copy them from a network location if they are already available. To download, go to:

    http://software.hp.com/products/SCMGR/download.html

    • For Red Hat Linux 7.2 and 7.3. CMS Software: SCM.3.0_RH.7.2_7.3_mxserver.bin

      Agent Software: SCM.3.0_RH.7.2_7.3_mxagent.bin

    • For SuSE Linux 8.0. CMS Software: SCM.3.0_SuSE.8.0_mxserver.bin

      Agent Software: SCM.3.0_SuSE.8.0_mxagent.bin

  2. Give all users permission to execute the bin files.

    chmod +x *.bin

  3. Install SCM directly from the bin files:

    • For Red Hat Linux 7.2 or 7.3:

      SCM.3.0_RH.7.2_7.3_mxserver.bin

    • For SuSE Linux 8.0:

      SCM.3.0_SuSE.8.0_mxserver.bin

  4. Initialize and configure the CMS:

    /opt/mx/bin/mxinitconfig -a server

Procedure 2-6 To manually install the CMS software on a Linux server:

  1. Download the required bin files identified below to the local file system or copy them from a network location if they are already available. To download, go to:

    http://software.hp.com/products/SCMGR/download.html

    • For Red Hat Linux 7.2 and 7.3. CMS Software: SCM.3.0_RH.7.2_7.3_mxserver.bin

      Agent Software: SCM.3.0_RH.7.2_7.3_mxagent.bin

    • For SuSE Linux 8.0. CMS Software: SCM.3.0_SuSE.8.0_mxserver.bin

      Agent Software: SCM.3.0_SuSE.8.0_mxagent.bin

  2. Give all users permission to execute the bin files.

    chmod +x *.bin

  3. Extract the rpm files from the bin file.

    mxfile.bin --keep --confirm

    where mxfile is the name of the bin file.

  4. Respond negatively to the prompt to run scripts.

    The extracted files will be placed in a subdirectory with the name of the bin file, mxserver or mxagent.

  5. Install the appropriate rpm files in the following order:

    • j2sdk-1.4.1_04-fcs-linux-i386.rpm

    • tomcat4-4.1.12-1e.2jpp.noarch.rpm

    • xml-commons-1.0-0.b2.1jpp.noarch.rpm

    • xml-commons-apis-1.0-0.b2.1jpp.noarch.rpm

    • For Red Hat 7.2 only:

      • mysql-3.23.36-1.i386.rpm

      • mysql-server-3.23.36-1.i386.rpm

      • mysqlclient9-3.23.22-4.i386.rpm

    • For Red Hat 7.3 only:

      • mysql-3.23.49-3.i386.rpm

      • mysql-server-3.23.49-3.i386.rpm

      • mysqlclient9-3.23.22-4.i386.rpm

    • For SuSE 8.0 only:

      • mysql-3.23.48-35.i386.rpm

      • mysql-shared-3.23.48-35.i386.rpm

      • mysql-client-3.23.48-35.i386.rpm

    • mxagent-B.03.00.04.i386-1.rpm

    • mxrepository-B.03.00.04.i386-1.rpm

    • mxcms-B.03.00.04.i386-1.rpm

  6. Initialize and configure the CMS:

    /opt/mx/bin/mxinitconfig -a server

Next Steps

Servicecontrol Manager is now installed. The next step is to add managed nodes, see “Adding Managed Nodes” for details.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2002-2003 Hewlett-Packard Development Company, L.P.