SAP Java Topology by SAP JMX Job

This job uses the SAP Java client to access the MBean server of an application server via the P4 port (5xx04).

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)`

Note The P4 port is usually closed and starting from Java application server version 7.x it is recommended to use the SAP Java Topology by WebServices and/or SAP Java Topology by HTTP jobs.

Prerequisites

Set up credentials.

To set up credentials to be used by the Java client discovery, you must provide separate credentials called SAP JMX. The SAP JMX credentials enable connection to a machine and verification of whether a SAP system is installed on it.
Add java client (jar files) to DataFlowProbe machine.

Note If you create version folders under the \j2ee\sap directory on the Data Flow Probe machine, you can connect to several SAP versions by adding .jar files to each folder. For example, to connect to versions SAP 6.4 and 7.0, in the SAP folder create two sub-folders called 6.x and 7.x and place the relevant .jar files in these folders.
1. Add the following .jar files to the <DataFlowProbe_root>\runtime\probeManager\discoveryResources\j2ee\sap directory on the Data Flow Probe machine:
  - sapj2eeclient.jar
  - logging.jar
  - exception.jar
  - sapxmltoolkit.jar
  The files reside in the \usr\sap\<SID>\<instance name>\j2ee\j2eeclient directory on one of the SAP instance machines.
2. Add the com_sap_pj_jmx.jar file to the <DataFlowProbe_root>\runtime\probeManager\discoveryResources\j2ee\sap directory on the Data Flow Probe machine.
  
  The file resides in the \usr\sap\<SID>\<instance name>\j2ee\admin\lib directory on one of the SAP instance machines.

Discovery Flow

Get available credentials for this destination and filter them so that only credentials that do not have a port or with a port that belongs to the list of ports opened on a destination are used.
For each credential, this job attempts to establish a connection to the destination.
Once the connection is established, this job sends the query SAP_J2EECluster to get cluster details. This query returns the following information:
- Name. This attribute contains the name of the cluster/system.
- InstanceNames. This attribute contains the names of the Java application servers available in this system.
After this query initial topology is reported.
To get more details about each instance, this job repeats the SAP_J2EEClusterquery to the same MBean but with the additional attribute AllInstanceInfos. The hostname and instance number are determined based on the Name value.
If the parameter reportComponentsAsConfigFile is set to true, this job discovers Development Components. The following MBeans are used to query interfaces, libraries, and services respectively:
- ```
SAP_J2EEInterfacePerNode
```
- ```
SAP_J2EELibraryPerNode
```
- ```
SAP_J2EEServicePerNode
```
This job discovers SCS (Central Services) application servers using the query SAP_J2EEInstance with name set to SCS.
This job discovers information about one or more workers and a dispatcher using the query SAP_J2EEClusterNode.
This job attempts to discover databases using the query SAP_ITSAMJ2eeCluster. However, this works only for the new MBean model (starting from version 7.1).