Network port schematics for App Visibility
Consult the following schematics for information about the various ports used by App Visibility. The port numbers provided in this topic are based on a default implementation.
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
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
Ports used by the App Visibility collector for network communication
Ports used by the App Visibility proxy for network communication
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:
-
Changing App Visibility portal settings
-
Changing App Visibility collector settings
-
Changing settings of the App Visibility agent for Java
-
Changing settings of the App Visibility agent for .NET
| Component | Protocol | Default port number | Function |
|---|---|---|---|
App Visibility portal | |||
| App Visibility portal | HTTPS | 8100 | Communication to an App Visibility portal from the following components:
|
| App Visibility portal supportability | HTTPS | 8101 | Communication to an App Visibility portal supportability console by BMC Customer Support, accessed via a browser |
| App Visibility portal node synchronization port | HTTPS | 5701 | Communication with the paired portal node for HA |
| App Visibility portal database | HTTPS | 8800 | Communication to the database from the App Visibility portal Communication is local; you do not need to open a firewall for external communication. |
App Visibility collector | |||
| App Visibility collector | HTTPS | 8200 | Communication to an App Visibility collector from the following components:
|
| App Visibility collector supportability | HTTPS | 8201 | Communication to an App Visibility collector supportability console by BMC Customer Support, accessed via a browser |
| App Visibility collector node synchronization port | HTTPS | 5702 | Communication with the paired collector node for HA |
| App Visibility collector database | HTTPS | 8800 | Communication to the database from the App Visibility collector Communication is local; you do not need to open a firewall for external communication. |
App Visibility proxy | |||
| App Visibility proxy | HTTPS | 8300 | Communication to an App Visibility proxy from an App Visibility portal |
| App Visibility proxy supportability | HTTPS | 8301 | Communication to an App Visibility proxy for supportability |
| Beacon receiver, HTTP | HTTP | 8304 | For HTTP pages, receives beacons from the end-user's browsers |
| Beacon receiver, HTTPS | HTTPS | 8305 | For HTTPS pages, receives beacons from the end-user's browsers |
| Storage HTTP | HTTP | 8302 | Communication to the storage engine from the App Visibility proxy Communication is local; you do not need to open a firewall for external communication. |
| Storage TCP | TCP | 8303 | Communication between App Visibility proxy storage engine nodes in a cluster Communication between the nodes is secured using SSL/TLS. |
App Visibility agent for Java | |||
| App Visibility agent for Java supportability | HTTPS | 50000-50100 | Communication to an App Visibility agent for Java supportability console by BMC Customer Support, accessed via a browser |
App Visibility agent for .NET | |||
| App Visibility agent for .NET | Not applicable | Not applicable | Not applicable |
Synthetic TEA Agent | |||
| Synthetic Transaction Execution Adapter (TEA) Agent | Not applicable | Not applicable | Not applicable |
Comments
Log in or register to comment.