Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- SAP Java Discovery
- Overview
- Supported Versions
- Topology
- How to Discover Full SAP Java-related Topology
- SAP Java Topology by HTTP Job
- SAP Java Topology by SAP JMX Job
- SAP Java Topology by WebServices Job
- SAP J2EE Topology by HTTP Adapter
- SAP J2EE Topology by JMX Adapter
- Troubleshooting and Limitations – SAP Java Discovery
SAP Java Topology by WebServices Job
This job is based on the same MBean model as the job SAP Java Topology by SAP JMX, but uses the SAP WebServices transport. This job also shares the same code base as the SAP Java Topology by SAP JMX job, and slightly differs in the discovery flow due to a deserialization limitation.
ID: SAP_Dis_J2EE_Site
This job is triggered on IPs that are part of the host with endpoint sap_http.
- remoteJVMArgs. The JVM parameters that should be passed to the remote process.
- reportComponentsAsConfigFile. If true, this job reports Java system components as a registry (configuration file). If false, this job reports separate CIs per component. The default value is true.
-
runInSeparateProcess. This parameter indicates whether the pattern runs in a separate thread. The default value is true.
-
Set up credentials
The WebServices client uses the same credentials that are used for the SAP Java Topology by SAP JMX job.
-
Libraries installation on the probe
There is no need to install external libraries. All required dependencies come with a Probe installation.
The flow for this job is very similar to the flow of the SAP Java Topology by SAP JMX job, but there are some differences when discovering whole system information.
Note Due to the deserialization limitation some discovered instances are reported without instance_name, as this information is not available.
The discovery flow for the SAP Java Topology by WebServices job is as follows:
-
Gets available credentials for this destination and filter them so that only credentials that do not have a port or have 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 using WebServices.
-
Once the connection is established, this job discovers all application servers by their names by sending 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.
Note At this point, this job misses discovery of the instance details due to the deserialization limitations of the WebServices client.
-
-
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).
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: