SAP Java Topology by HTTP Job

This job is based on parsing data from the XML queried HTTP URLs. URLs can differ slightly depending on the system configuration where the application server (instance) resides. There are two main types of configurations that are used by this job:

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Pure/standalone Java system configuration, which has the following type of query:

http(s)://<address>:<port>/sap/monitoring/SystemInfoServlet (used to query information about the entire system)

Double Stack (DS) configuration, which has the following type of query:

http(s)://<address>:<port>/monitoring/SystemInfoServlet (used to query information about the entire system)

Discovery Flow

The discovery flow for the SAP Java Topology by HTTP Job is as follows:

Get available SAP JMX credentials for this destination.

Note Even if the port in specified in the credentials is different from destination port, such credential are also used.
For each credential, this job attempts to perform an HTTP query using the SystemInfoServlet URLs mentioned above. Successful output is XML that is parsed to get the following SAP system details:
- system ID (from the XML: /SAP_J2EE/SID/@value)
- system installation type (from the XML: /SAP_J2EE/INSTALLATION_TYPE/@value)
- version, which is composed of:
  - /SAP_J2EE/REL/@value
  - /SAP_J2EE/PATCH_LEVEL/@value
- database information (from the XML: /SAP_J2EE/DB_INSTANCE)
- SCS (from the XML: /SAP_J2EE/SCS_INSTANCE)
  
  Note SCS data is not complete because it contains only port and host information, while the instance number is missing. Therefore, this job computes the instance number from the port. Several port patterns considered, such as 3xNN, 81NN (http), 444NN (https), where NN stands for instance number.
- dialog instances (from the XML: /SAP_J2EE/DIALOG_INSTANCE)
  
  Note /SAP_J2EE/DIALOG_INSTANCE/INSTANCE_DIR and /SAP_J2EE/DIALOG_INSTANCE/NAME are intentionally skipped from the discovery algorithm as they may contain invalid data.
- central instance (from the XML: /SAP_J2EE/CENTRAL_INSTANCE)
  
  Reporting dialog and central instances contains some additional logic for instance name resolving. To get the instance name, this job collects information on all workers (or servers) and a dispatcher to get runtime properties such as application.home, com.sap.jvmdir, java.home, rdbms.driverLocation, and user.dir. This job attempts to find a path with the corresponding SID and with a valid instance name from the paths that have been discovered thus far. Usually application.home contains such information.
- software components (from the XML: /SAP_J2EE/SOFTWARE_COMPONENTS/COMPONENT)