You can install SAP Host Agent manually by executing the saphostexec executable with option -install from the extracted SAPHOSTAGENT<SP-version>.SAR archive.
|Windows||You have installed the specified Microsoft security patch in accordance with the instructions in SAP Note 1375494 . You also need to install the latest version of the Microsoft Runtime used by SAP as described in SAP Note 684106 .|
|IBM i||Option 33 of the operating system must be installed. Use menu GO LICPGM to check whether the option is installed and install it if required.|
|IBM i||The system startup program (specified in system value QSTRUPPGM) must contain the STRSBS command to start subsystem QSYS/QUSRWRK. This is needed because SAPHOSTAGENT will be started as an auto-start job in subsystem QSYS/QUSRWRK|
|Windows||As a member of the local Administrators group|
|UNIX||As a user with root authorization|
|IBM i||As a user profile with special authorities
example as user profile
If user profile R3GROUP does not exist on your server, it will be created during the installation of SAP Host Agent. 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 system 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.
|UNIX, IBM i||/tmp/hostagent|
Take SAP Note 212876 into account when doing so. Use the following command for extraction, and execute them in the directory of the archive:
|Windows||<path to SAPCAR> sapcar.exe -xvf SAPHOSTAGENT<SP-version>.SAR|
|UNIX||<path to SAPCAR> sapcar -xvf SAPHOSTAGENT<SP-version>.SAR|
|IBM i||<path to SAPCAR> SAPCAR -xvf SAPHOSTAGENT<SP-version>.SAR|
If user sapadm does not yet exist, it is automatically created as a local user and you are prompted to enter a password for this user to be created.
In some cases it might be useful to configure sapadm as a domain user instead of a local user, for example if you have multiple Windows hosts in your system landscape each of which has SAP Host Agent. Enter the following command to install saphostexec while specifying sapadm as the domain user:
saphostexec.exe -install -user <domain>\sapadm
The administrator user sapadm of the SAP Host Agent is created automatically during the installation, but it does not get assigned a password.
Note You can set the password in one of the following ways:
|IBM i||./saphostexec -install -gid
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 user profile R3GROUP already exists, or if you want the saphostcontrol installation to automatically generate a new group ID, enter the command saphostexec -install without the addition -gid <gid> .
|UNIX, IBM i||/usr/sap/hostctrl/exe/saphostexec -status|
After the installation has finished successfully, SAP Host Agent is up and running.
|UNIX, IBM i||/tmp/hostagent|
IBM i only: If it did not already exist, R3GROUP was created during the installation. Even though SAP Host Agent 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 .