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 RTCP
Registered Intercepts table, from the Configurable table,
or both. The supported types of RTCP Registered Intercepts are:
- CICS® DPL
- CICS TG
- 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.