Starting the topology discovery process

Starting the topology discovery process involves selecting the observation points to be used and exercising the system under test.

About this task

You must select at least one observation point to begin the discovery process. You can choose observation points from the Registered Intercepts table, from the Configurable table, or both. The supported types of Registered Intercepts are:
  • HTTP
  • Java Agent
  • JDBC
  • SIB
  • TCP

Most of the observation points are named after the types of resources they can observe. For example, use the HTTP observation point to observe HTTP traffic. The exceptions are TCP and the Java agent.

Use the TCP intercept to observe resources that were invoked by using any of the following protocols:
  • TCP
  • IPIC (protocol for communication between IBM® TXSeries® for Multiplatforms and mainframes that use TCP/IP)
  • IMS™
  • MQTT
  • FIX
The Java agent observes Java applications that have been configured to use the Java virtualization agent. See Java virtualization agent. You can use the Java agent intercept to capture the following observations:
  • HTTP observations when an application makes HTTP requests by using either the standard JSE API or the Apache HTTP client APIs (version 3 or 4).
  • JMS observations when an application makes JMS requests by using the standard JMS API.
    Note: The new JMS 2.0 APIs are not supported for discovery, recording or stubbing.

You can capture credentials when you observe JMS requests. To enable this feature, set the capture property to on in the registration.xml file for the Java agent; see Modifying the configuration settings of the Java virtualization agent. When you subsequently model resources based on these observations, identities are created based on the captured data, and the most commonly used identity is associated with the generated transport.


  1. In the Architecture School perspective, select the Topology Discovery view. To select one or more observation points from the list of available HCL Quality Server intercepts, click Registered Intercepts in the Observation Points pane and select the intercepts to use as observation points. The Registered Intercepts table displays the types of intercepts that support observations. For each intercept type, the number of currently registered intercepts is also displayed. HCL Quality Server must be running at the time you use the intercept observation points. Click Refresh to update this information. You do not need to provide any additional configuration information to use these observation points.
  2. To select an observation point for WebSphere® MQ, click Configurable. For information about configuring this observation point, see Configuring a WebSphere MQ observation point.
  3. After you select your observation points, click the Start discovery icon.
    The Start discovery icon is shown.
  4. Exercise the system under test. Topology discovery is similar to using the recording studio, in that you are observing processes in action. As the specified observation points observe resources, those resources are displayed in the Observed Resources pane. The resources are grouped by observation point. If a model of a resource already exists on your system, the line for that resource is highlighted in orange. This color can be changed in the project preferences. Right-click the line for the option to open the modeled resource within the project.
    The HTTP server on the local host was observed.
  5. Click a discovered resource for more information. A summary of the invocations of the resource is displayed in the Observed Resource Invocations Summary pane.
    An HTTP web service request is shown.
  6. To stop the discovery process, click the Stop discovery icon. Although you can model observed resources while the discovery process is running, stopping the process can free up resources and reduce the amount of work that is performed by the observation points within the system under test.
    The Stop discovery icon is shown.

What to do next

Review the observed resources. Where needed, you can add discovered resources to your model of the system under test. For more information, see Modeling components from discovered resources.