Docs.bmc.com brief outage

This site, docs.bmc.com, will undergo a brief outage of less than ten minutes starting at 5 PM CDT June 12/3:30 AM IST June 13.

Network port schematics for App Visibility


Network ports used in an App Visibility Manager deployment

The following figure illustrates a typical high-level logical architecture for an App Visibility Manager deployment, including the general communication between the server components and the agents. The direction of the arrows indicate the connection requests.

All communication is over HTTPS.

Ports used by App Visibility components for network communication

appvis_networkports.png

 

Network ports used by the App Visibility components

The following figures illustrate the default ports on which communication is made with the App Visibility portal. The direction of the arrows indicate the connection requests except for the component communication, which is illustrated in a previous diagram.

All communication is over HTTPS.

Ports used by the App Visibility portal for network communication

appvis_networkports_portal.png


Ports used by the App Visibility collector for network communication

appvis_networkports_collector.png


Ports used by the App Visibility proxy for network communication

appvis_networkports_proxy.png


Network ports for App Visibility Manager

Notes

  • Ensure that you open ports in your firewall to enable communication between the components.
  • If a network port is occupied, the App Visibility server component stops, as reflected in the component log, but the log message does not give the reason.

The following properties apply to all App Visibility Manager ports:

  • Flow is inbound
  • Default state is enabled

You can configure most port numbers during installation. You can configure all port numbers postinstallation:

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*