Limitations of topology discovery

You must be aware of certain limitations in Topology discovery.

Security credentials are not observed

Topology discovery does not typically capture security credentials. Resources created from observations might require editing to add such credentials before you use them in recording, tests, or stubs. The exception is WebSphere MQ, where credentials are populated when a new physical resource is modeled for a queue manager, based on the values from the observation point.

SIB provider endpoint might be inaccurate

When creating resources from Service Integration Bus (SIB) observations, the provider endpoint configured in the created physical resource might need to be edited. This update is required if the port is not the default port (7276) or if the server has multiple host names.

JMS topology discovery does not observe any invocations that use the referenced connection factories and destinations

If you record or stub JMS by using the Java agent in WebSphere Application Server or another application server and the application code uses @Resource or @MessageDriven annotations to reference JMS connection factories and destinations, JMS topology discovery does not observe any invocations that use the referenced factories or destinations.

Feedback