Comment on page
SAP Host Agent
1. In the IT-Conductor main menu, navigate to Dashboards > Administrator.
Figure 1: IT-Conductor Dashboards Menu
2. Scroll down, locate SAP Host Agents, and click 
to create a new system.
Figure 2: SAP Host Agents Section
3. Fill in the necessary configuration information and click .
Figure 3: Create a new SAP Host Agent
4. A dialog pop-up confirming the entry has been created will appear. Click OK.
Figure 4: SAP Host Agent Creation Confirmation
5. The next page is to associate a monitoring account that the host agent allows connecting services. Once the privileges are set, enter the username and password. Click .
Note: Please refer to the Setting Up Accounts for SAP Host Agent Monitoring for the privileges required for the host agent to work properly.
Figure 5-a: Association of the Host Agent to the Application
6. A pop-up message will confirm that the account has been created. Click OK to complete the process.
Figure 5-b: Association Confirmation
This will add the configuration for monitoring the host agent.
On Microsoft Windows, we recommend using a single domain user for all host agents.
The user account(s) must be a member of:
- On Linux/Unix: sapsys group
- On Windows: SAP_LocalAdmin group
IT-Conductor uses web services provided by the SAP host agent, which are protected and can only be used by an authenticated caller (see SAP Note 927637). To authorize users to access SAP host agent services, the following need to be performed for all hosts to be monitored, after ensuring the executable <DIR_EXECUTABLE>/sapuxuserchk has 4750 permission (on Linux/Unix).
Note: Only needed if not using adm; we recommend sapadm or daaadm.
- 1.Open the file:
Linux/Unix
Windows
/usr/sap/hostctrl/exe/host_profile
C:\Program Files\SAP\hostctrl\exe\host_profile
2. Add the "service/admin_users" parameter with the following values (separated by a blank space):
Linux/Unix
Windows
service/admin_users = <user1> <user2>
service/admin_users = [<domain>]\<user1> [<domain>]\<user2>
3. Restart SAP Host Agent with:
Linux/Unix
Windows
/usr/sap/hostctrl/exe/saphostexec -restart
C:\Program Files\SAP\hostctrl\exe\saphostexec.exe -restart
4. Log on with the OS user to be checked and execute:
sapcontrol -prot GSOAP_HTTP -nr -user "<User Name>" "<User Password>" -function AccessCheck <function>
where "Functions" in IT-Conductor include:
- GetAccessPointList
- GetProcessList
- GetEnvironment
- GetInstanceProperties
- ABAPGetWPTable
- GetSystemInstanceList
- GetQueueStatistic
- GetAlertTree
- GetAlerts
- EnqGetStatistic
- EnqGetLockTable
- ICMGetProxyConnectionList
- ICMGetCacheEntries
- ICMGetThreadList
- WebDispGetServerList
- WebDispGetGroupList
- WebDispGetVirtHostList
1. Open the SAP instance profile "<DIR_INSTALL>/profile/DEFAULT.PFL"
2. Add the following parameters:
service/admin_users = <sid>adm daaadm sapadm service/protectedwebmethods = -GetAccessPointList -GetProcessList -GetEnvironment -GetInstanceProperties -ABAPGetWPTable -GetSystemInstanceList -GetQueueStatistic -GetAlertTree -GetAlerts -EnqGetStatistic -EnqGetLockTable -ICMGetThreadList -ICMGetConnectionList -ICMGetProxyConnectionList -ICMGetCacheEntries -WebDispGetServerList -WebDispGetVirtHostList -J2EEGetProcessList -J2EEGetProcessList2 -J2EEGetThreadList -J2EEGetThreadList2 -J2EEGetCacheStatistic -J2EEGetCacheStatistic2 -J2EEGetWebSessionList - J2EEGetWebSessionList2 -J2EEGetEJBSessionList -J2EEGetRemoteObjectList -J2EEGetSharedTableInfo -J2EEGetVMHeapInfo
3. On Unix: As root user - restart the relevant "sapstartsrv" process for the sap instance using: "systemctl restart sapinit", which requires an SAP downtime, so make sure to do it during maintenance.
Last modified 1mo ago