Show TOC

Procedure documentationUsing the SAP Host Agent in ACC 7.1 Locate this document in the navigation structure

 

You configure the SAP host agent to enable the start and stop of services on every computer system, and monitor the status of computer systems.

Prerequisites

Check the Product Availability Matrix (PAM) at service.sap.com/pam to ensure that:

  • Your OS version is on the list of the supported OS versions for SAP NetWeaver, as the Host Agent is not supported by every OS

  • The minimum OS requirement is met before installing the Host Agent

Procedure

1. Installing the SAP Host Agent

On each host having an SAP component, which needs to be managed by ACC, should be checked whether the SAP host agent is installed and running.

From SAP NetWeaver 7.1 onwards the SAP host agent is installed as part of the installation process.

More information: Downloading and Installing Package SAPHOSTAGENT

Note Note

However, ACC 7.1 needs the latest version of the host agent. To upgrade the host agent, perform the following activities:

End of the note.

  1. Logon to the computer system with the root user

  2. Create a temporary upgrade directory and extract the new host agent archive to it.

    mkdir <upgrade_dir>

    cd <upgrade_dir>

    /path/to/SAPCAR -xvf SAPHOSTAGENT.SAR

  3. Start the host agent upgrade procedure, by running the following command:

    /saphostexec -upgrade

2. Registering the SAP Host Agent in the System Landscape Directory

To register a the SAP host agent with the SLD, call the executable sldreg on that host.

More information: Registering Hosts with the SLD Using sldreg

3. Installing SAPACOSPrep Partner Libraries (Optional)

The SAP Host Agent depends on SAPACOSPrep libraries that implement the functionality to manage virtual hostnames and data storage. Libraries shipped with the Host Agent allow managing virtual hostnames for Linux and Windows, and managing NFS-based data storage for Linux.

To get the SAPACOSPrep partner libraries for your specific environment, perform the following activities:

  1. Contact your SAP technology partner representative.

    SAP technology partners provide libraries for platforms and data storage solutions.

  2. SAPACOSPrep partner libraries may require additional setup procedures. Follow the instructions provided by the partner.

For more information, refer service.sap.com/adaptive.

4. Preparing Linux machines for ACC 7.1

On Linux, the SAP host agent (and other 7.1 based SAP kernel components) require additional OS packages (libstdc++ and libgcc version 4.1) that are not a part of the standard SLES9 and REHL4 distributions.

  1. Install the libstdc++ and libgcc version 4.1 packages.

    For more information, refer SAP Note 1021236.

  2. If the packages are not yet available, then create the OS user sapadm.

    The OS user is either a local user or a user managed by a central directory (For example, LDAP or NIS).

  3. If the packages are not yet available, create the OS user group sapsys and add the sapadm user to this group.

  4. If not yet available, then perform the following activities:

    1. Create the saposcol work directory /usr/sap/tmp

    2. Create a temporary installation directory, and extract the SAP host agent archive to it.

      mkdir <install_dir>

      cd <install_dir>

      /path/to/SAPCAR -xvf SAPHOSTAGENT.SAR

    3. Start the host agent installation procedure, by running the following command:

      /saphostexec -install

5. Web Service Authentication

Ensure that the prerequisites for Web Service Authentication are fulfilled.

For more information, refer SAP Note 927637.

For example, to create a PAM authentication policy for service sapstartsrv on Linux, perform the following activities:

  1. Create file /etc/pam.d/ sapstartsrvand add the following lines:

    • auth sufficient pam_unix2.so

    • auth required pam_unix_auth.so

    • account sufficient pam_unix2.so

    • account required pam_unix_acct.so

  2. In case of SLES10 ensure that md5is used as the default encryption method.

    For more information, refer SAP Note 958253.