Discovery > Discovery Modules > Enterprise Applications > SAP Discovery > SAP Java Discovery > SAP Java Topology by WebServices Job

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.

ClosedAdapter

ID: SAP_Dis_J2EE_Site

ClosedTrigger TQL

This job is triggered on IPs that are part of the host with endpoint sap_http.

ClosedParameters
  • 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.

ClosedPrerequisites

  1. Set up credentials

    The WebServices client uses the same credentials that are used for the SAP Java Topology by SAP JMX job.

  2. Libraries installation on the probe

    There is no need to install external libraries. All required dependencies come with a Probe installation.

ClosedDiscovery Flow

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:

  1. 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.

  2. For each credential, this job attempts to establish a connection to the destination using WebServices.

  3. 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.

  4. 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

  5. This job discovers SCS (Central Services) application servers using the query SAP_J2EEInstance with name set to SCS.

  6. This job discovers information about one or more workers and a dispatcher using the query SAP_J2EEClusterNode.

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