Installation SAPHOSTAGENT 71
Installation SAPHOSTAGENT 71
Installation SAPHOSTAGENT 71
SAPHOSTAGENT
The SAPHOSTAGENT package contains some of the required elements for centrally
monitoring any host with the Alert Monitor or the SAP Solution Manager. Depending on the
release of the central system you also need to install the CCMS agent to monitor a host
centrally. It is automatically installed during the installation of all of the components of SAP
NetWeaver 7.1. However, on each host with an SAP component managed by the Adaptive
Computing Controller (ACC), check whether the host agent is installed and running.
You can also install the host agent using the installation tool SAPinst. The files required for
this are on the kernel DVD for the current release. For more information, see the SAP Service
Marketplace at http://service.sap.com/instguidesnw. To find the installation guide, choose the
required release and the Installation area.
Note
If you are using a System Landscape Directory (SLD), register the host with the SLD
after installing the host agent, as described in Registering Hosts with the SLD Using
sldreg. You need this data in the SLD, for example, for the Adaptive Computing
Infrastructure.
End of the note.
Service Local
Socket SAPOsCol
Userer
Root SAPHostExec controls
or Local
System Account sapacosprep
saphostexec
SAP Online Help 29.09.2010
sapstartsrv
sapacosprep
saposcol
Prerequisites
You have the archive SAPHOSTAGENT.SAR.
Note
Procedure
Installation Under Windows
Note
Before the installation, ensure that you have installed the specified Microsoft
security patch in accordance with the instructions in SAP Note 1375494.
For the installation, there must be a sapadm user with administrator authorizations on the
host and a SAP_LocalAdmin group. The procedure for Microsoft Windows XP is presented
here as an example. In other versions of Microsoft Windows, the procedure differs slightly:
1. Do the following:
2. In the navigation bar, choose Groups, and then choose the menu path
Action New Group... . Create a new group called SAP_LocalAdmin,
and then close the New Group window.
3. In the navigation bar, choose Users, and then choose the menu path
Action New User... . To create the sapadm user make the required
settings, and then close the New User window.
4. So that the user has the required authorizations, switch back to the Users tab
page in the User Accounts window, and double-click the sapadm that you
have just created. On the Group Membership tab page, add the user to the
Administrators and the SAP_LocalAdmin group.
Note
3. Add the sapadm user to the list by choosing the Add User or
Group… button and entering this user.
3. Decompress the SAPHOSTAGENT.SAR archive with the SAPCAR tool. Take SAP
Note 212876 into account when doing so. Normally, you use the following command
for decompression, and execute it in the directory of the archive:
saphostexec -install
5. In the next step, a window appears in which you can enter information about the
required operation and the user to be used for the operation. Enter the password of
the sapadm user.
Note
The default setting for the user is .\sapadm, that is, sapadm is a local user. If
sapadm is a domain user, delete the prefix .\.
End of the note.
2. If the sapsys group does not yet exist on the host, create it using, for example, the
command groupadd.
3. If the user sapadm does not yet exist on the host, create it using, for example, the
command useradd.
4. If the SAPOSCOL working directory does not yet exist on the host, create the
directory usr/sap/tmp.
5. Decompress the SAPHOSTAGENT.SAR archive with the SAPCAR tool, following SAP
Note 212876. Normally, you use the following command for decompression and
executing it in the directory of the archive:
6. Among other things, the archive contains the saphostexec program. Install
SAPHOSTCONTROL by entering the following command:
saphostexec -install
Installation on IBM i
Preparation
If you had to install option 33 during this step, we recommend that you install the
latest PTFs for your operating system release according to SAP Note 83292.
2. Make sure your system startup program (specified in system value QSTRUPPGM)
contains the command to start subsystem QSYS/QUSRWRK. This is needed because
SAPHOSTAGENT is started as an autostart job in subsystem QSYS/QUSRWRK.
3. Download the PASE version of SAPCAR from the SAP Service Marketplace as
described in SAP Note 863821. To download SAPCAR, goto
http://service.sap.com/swdc and then choose SAP Software Distribution Center
Support Packages and Patches Support Packages and Patches - Entry by
Application Group SAP Technology Components SAPCAR SAPCAR 7.10
OS/400.
If it does not exist on your server, create the directory /tmp/hostctrl and then
copy or move the downloaded archive SAPHOSTAGENT<…>.SAR and SAPCAR to the
directory /tmp/hostctrl.
Note
This document refers to the directory /tmp/hostctrl in some of the steps below. If
you want to use a different directory, you have to adjust the commands appropriately.
5. If user profile R3GROUP does not exist on your server, it will be created during the
installation of SAPHOSTCONTROL. If you have already installed SAP systems on
other servers, we recommend that you use the same group ID (GID) for all sapsys
and R3GROUP groups in the systems landscape. To obtain the group ID (GID) for
R3GROUP on another IBM i server in your landscape, enter the command DSPUSRPRF
USRPRF(R3GROUP) and scroll down until you see the value for “Group ID number”.
Installation
1. Log on with user profile QSECOFR or a user profile with equivalent special authorities.
Note
CALL PGM(QP2TERM)
3. Make the directory that contains SAPCAR and the archive SAPHOSTAGENT<…>.SAR
your current directory using the following command:
cd /tmp/hostctrl
4. Decompress the archive SAPHOSTAGENT<…>.SAR with the SAPCAR tool using the
following command:
Note
If you have already installed SAP systems on other servers, we recommend that you
use the same group ID (GID) for all sapsys or R3GROUP groups in the system
landscape. To do this, enter your landscape system gid into <gid> on the above
command. If you want the SAPHOSTCONTROL installation to generate a new group
ID, enter the command saphostexec –install instead.
6. Leave the PASE interactive terminal session using function key F3.
Note
If it did not already exist, R3GROUP was created during the installation. Even though
the SAPHOSTAGENT does not require special authorities, we recommend that you
grant the required authorities for system API’s that need to be authorized for user
profile R3GROUP for your SAP system now. For more information, see SAP Note
175852.
End of the note.
Result
You have installed and started the following units on your host:
Note
The installed programs are automatically started when the host is booted. On
Microsoft Windows hosts, this is done by the services SAPHostControl and
SAPHostExec. On UNIX hosts the automatic start is ensured by the startup script
sapinit, which starts the required executables. On IBM i, the programs are started
by the auto start job SAPINIT in subsystem QUSRWRK, which is configured during
the installation.
Upgrade
If you want to perform an upgrade manually for the host agent, proceed as follows:
The archive contains the saphostexec program. Perform the upgrade by switching to
this temporary directory and running the command saphostexec -upgrade there.
After the upgrade, you can delete the temporary directory again.
Switch to the root user and perform the upgrade by switching to this temporary
directory and running the command saphostexec -upgrade there.
After the upgrade, you can delete the temporary directory again.
Log on with user profile QSECOFR or a user profile with equivalent special authorities
and start a PASE interactive terminal session by entering the command CALL
PGM(QP2TERM).
Switch to the temporary directory used for extracting SAPHOSTAGENT.SAR and run
the command saphostexec -upgrade.
After the upgrade, you can delete the temporary directory again.
Uninstallation
If you want to uninstall the host agent, use the following command:
saphostexec -uninstall
This stops the above executables and services and deletes the working directory of the host
agent.