The following table lists the default configurations of protocols and ports for different components and services used by BMC TrueSight App Visibility Manager.
Notes The following properties apply to all App Visibility Manager ports: You can configure most port numbers during installation. You can configure all port numbers postinstallation: Communication to an App Visibility portal from the following components: Communication to the database from the App Visibility portal Communication is local; you do not need to open a firewall for external communication. Communication to an App Visibility collector from the following components: Communication to an App Visibility collector supportability console by BMC Customer Support, accessed via a browser Communication to the database from the App Visibility collector Communication is local; you do not need to open a firewall for external communication.
Component Service Default port number Function App Visibility portal
App Visibility portal HTTPS 8100
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 control port HTTPS 8102 Communication with the paired portal node for HA App Visibility portal database HTTPS 8800 App Visibility collector
App Visibility collector HTTPS 8200
App Visibility collector supportability HTTPS 8201 App Visibility collector control port HTTPS 8202 Communication with the paired collector node for HA App Visibility collector database HTTPS 8800 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 880 For HTTP pages, receives beacons from the end-user's browsers Beacon receiver, HTTPS HTTPS 8444 For HTTPS pages, receives beacons from the end-user's browsers 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
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
1 Comment
Nikhil Shetty
Hello Team, do we need 2-way communication from App vis agent for java to the App viss portal and collector on port 8100 and 8200 respectively.