If you know that the application flow map should be showing a specific backend and you are not seeing it, you can modify the configuration to detect backends. You can:

• Edit the default backend discovery rules.
• Create new custom backend discovery rules.
• Create new custom exit points to provide visibility for backend types that are not automatically discovered.
• Disable automatic discovery of backends that are not of interest.
• Disable correlation for the backend.

In many cases, you can achieve the level of customization that you need by editing the default rules rather than creating new rules.

To edit a rule, in the Backend Detection tab, select the application and Use Custom Configuration for this Tier, and click Edit Automatic Discovery.

For certain backend types—particularly those named by URL—the name of the discovered backend instances include a port number. If the app agent is unable to discover the port number for some reason, the port number is displayed in the UI as "-1". This can happen, for example, when a port is not a public port or the API for discovering the port is not available on the application environment (often the case for an RMI backend type). Despite having an unknown port number, the backends are nonetheless uniquely identified.