Introduction
SAP Host Agent Outside Discovery is an SLD/LMDB data supplier which reports Computer System, Database, SDA, SAP Host Agent and other data.
It is available as of SAP Host Agent 721 PL37.
| FRUN | SolMan 7.2 SP06 | < SolMan 7.2 SP06 |
|---|---|---|
SAP Host Agent Outside Discovery is mandatory. | Outside Discovery can be configured to be performed by SMD Agent or SAP Host Agent. (Note 2556432) Recommendation is to use SAP Host Agent Outside Discovery | SMD Agent Outside Discovery is mandatory |
It is not recommended to use SAP Host Agent Outside Discovery and SMD Agent Outside Discovery together.
Differences between SMD Agent Outside Discovery and SAP Host Agent Outside Discovery
| SAP Host Agent | SMD Agent | |
|---|---|---|
Computer System Outside Discovery | SAP Host Agent Outside Discovery will detect and register all configured IPs and their corresponding hostnames to LMDB/SLD. It does not matter if the hostname is used by an SAP Instance or a Database. | SMD Agent Outside Discovery reports only the IPs and hostnames, which are used by a SAP Instance or an SMD Agent (Agent-On-The-Fly Concept). |
Database Outside Discovery | SAP Host Agent Outside Discovery will detect and register all databases on the host. Also, if the database offers more connect addresses, SAP Host Agent Outside Discovery will report additional database objects based on the connect addresses. | SMD Agent Outside Discovery reports only the databases, which are used by a SAP System. |
FRUN Outside Discovery Documentation
Solution Manager 7.2 Outside Discovery Documentation
https://launchpad.support.sap.com/#/notes/2556432
Displaying the Outside Discovery Configuration
The Outside Discovery Configuration can be displayed by using the GetCIMObject Webservice.
- Method: GetInstance
- Class: SAPHostAgent_OutsideDiscovery or SAPHostAgent/OutsideDiscovery
the SAPHostAgent_OutsideDiscovery instance will display
- the current scheduled Outside Discovery settings
- all registered XMLs (ConfigureOutsideDiscoveryPath)
- all discovered SLD/LMDB Destinations
Example
C:\Program Files\SAP\hostctrl\exe>saphostctrl.exe -function GetCIMObject -getinstance SAPHostAgent/OutsideDiscovery ********************************************************* CreationClassName , String , SAPHostAgent_OutsideDiscovery ********************************************************* ComputerSystem , string , Enabled Databases , string , Enabled SimpleDiagnosticAgent , string , Enabled SAPHostAgent , string , Enabled Microsoft IIS , string , Enabled SLDRegistration , string , Enabled Cleanup , string , Enabled CreationClassName , string , OutsideDiscoverySettings NextExecution , string , 2021/03/09 00:02:37 ExecutionFrequencyMinutes , uint64 , 720 ********************************************************* CreationClassName , string , OutsideDiscoveryDestinations localhost_1128 , string , C:\Program Files\SAP\hostctrl\exe\config.d\slddest_localhost_1128.cfg
Outside Discovery Webservices
SAP Host Agent provides webservices to configure and execute Outside Discovery.
Both can be used with saphostctrl commandline client or any other Webservice Client.
ConfigureOutsideDiscovery
ConfigureOutsideDiscovery
Usage: saphostctrl [generic option]... -function <Webmethod> [argument]...
saphostctrl -help [<Webmethod>]
Generic options:
-host <hostname>
-user <username> <password>
-prot tcp|pipe [Force to use TCP only or PIPE connection only]
-https|-sso
-format [flat|tree|cimobject] where supported.
-sotimeout <connect[,recv,send]> set socket timeout in second
negative values = INFINITE
Supported Webmethods:
ConfigureOutsideDiscovery
Configure the Outside Discovery Job which runs periodically
These Options control the Outside Discovery Job.
If frequency is not provided, it will run every 12 hours.
If execution options are not provided the default will be used (detect everything and try to register it).
-enable
[-frequency <X> Run frequency in minutes]
[-jobtimeout <X> Wait X seconds for the Outside Discovery Job which was started with the enable option and return the results]
Outside Discovery Execution Options:
[-sldreg Run SLD registration after Outside Discovery]
[-computersystem Discover only the Host ComputerSystem]
[-database Discover only the Database(s) on this host]
[-smdagent Discover the Solution Manager Diagnostic Instance(s) and Host ComputerSystem]
[-saphostagent Discover the SAPHostAgent]
[-msiis Discover only the Microsoft Internet Information Service]
[-xmlfromconfig Register XML(s) configured with the ConfigureOutsideDiscoveryPath webservice]
[-cleanup Delete the generated sldreg XML input files after the discovery]
-disable
-auto
detect Outside Discovery settings automatically
Outside Discovery Destination
*****************************
With the following parameters, a SLDREG destination can be configured.
-sldhost <SLD Hostname>
-sldport <Portnumber of SLD>
-sldusername <SLD user>
-sldpassword <SLD user password> Use "-" for hidden input.
SLDREG SSL/SSO configuration parameters (optional):
[-sldusessl Enable SSL communication encryption]
[-sldpsepath <path> Set a specific PSE path to be used by SLDREG]
[-sldusecertauth Enable SSO Certificate Authentication for SLDREG; Username and Password will be ignored.]
ConfigureOutsideDiscovery Example
/usr/sap/hostctrl/exe/saphostctrl.exe -function ConfigureOutsideDiscovery -enable -sldhost sld.my.domain -sldport 1234 -sldusername MYUSER -sldpassword SECRET
ConfigureOutsideDiscovery with SSO example
/usr/sap/hostctrl/exe/saphostctrl.exe -function ConfigureOutsideDiscovery -enable -sldhost sld.my.domain -sldport 1234 -sldusessl -sldusecertauth -sldpsepath /usr/sap/hostctrl/exe/sec/MYPSE.pse
ConfigureOutsideDiscoveryPath
This function takes XML files with LMDB/SLD payload and stores the path to the files in the OutsideDiscovery configuration file <HostAgentPath>config.d/OutsideDiscovery.config.
ConfigureOutsideDiscoveryPath Configure a file or directory to OutsideDiscovery configuration for sld registration. Only XML file will be taken into consideration. -register <file/directory> Add a file to OutsideDiscovery configuration for sld registration -unregister <file/directory> Remove a file from OutsideDiscovery configuration for sld registration
After successful Execution of ConfigureOutsideDiscoveryPath, the configured files will be sent to LMDB/SLD via sldreg during the next automatic Outside Discovery execution (default every 12 hours).
To explicitly send the configured files via sldreg to the configured LMDB/SLD destination, use "ExecuteOutsideDiscovery -xmlfromconfig -sldreg".
ExecuteOutsideDiscovery
ExecuteOutsideDiscovery
Usage: saphostctrl [generic option]... -function <Webmethod> [argument]...
saphostctrl -help [<Webmethod>]
Generic options:
-host <hostname>
-user <username> <password>
-prot tcp|pipe [Force to use TCP only or PIPE connection only]
-https|-sso
-format [flat|tree|cimobject] where supported.
-sotimeout <connect[,recv,send]> set socket timeout in second
negative values = INFINITE
Supported Webmethods:
ExecuteOutsideDiscovery
[-sldreg Run SLD registration after Outside Discovery]
[-computersystem Discover only the Host ComputerSystem]
[-database Discover only the Database(s) on this host]
[-smdagent Discover the Solution Manager Diagnostic Instance(s) and Host ComputerSystem]
[-saphostagent Discover the SAPHostAgent]
[-msiis Discover only the Microsoft Internet Information Service]
[-xmlfromconfig Register XML(s) configured with the ConfigureOutsideDiscoveryPath webservice]
[-cleanup Delete the generated sldreg XML input files after the discovery]
Note: The ExecuteOutsideDiscovery call without parameters will run all of the parameters above except the SLD registration.
Database System Outside Discovery
As of SAP Host Agent 722 PL 55, Outside Discovery supports the detection of Database Systems, meaning clustered / replicated databases.
This feature can be activated via a setting in the Host Agent configuration file http.server.settings.
<Host Agent exe dir>/config.d/http.server.settings
OutsideDiscovery {
DatabaseDiscoveryMethod : databasesystem
}
The default setting for database outside discovery is to detect local databases only.