Network ports for App Visibility Manager

The following table lists the default configurations of protocols and ports for different components and services used by BMC TrueSight App Visibility Manager.

Related topics

Network ports

App Visibility Manager high-availability deployment

Network port schematics for App Visibility

Performing the App Visibility server installation

Setting up and managing the App Visibility components and databases

Basic deployment options for TrueSight Operations Management

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:

  • Protocol is TCP
  • 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 App Visibility proxy settings
  • Changing settings of the App Visibility agent for Java
  • Changing settings of the App Visibility agent for .NET

ComponentServiceDefault port numberFunction

App Visibility portal

App Visibility portalHTTPS8100

Communication to an App Visibility portal from the following components:

  • App Visibility collectors
  • App Visibility proxies
  • App Visibility agents for Java and .NET
  • TEA Agents
  • TrueSight Presentation Server
App Visibility portal supportabilityHTTPS8101Communication to an App Visibility portal supportability console by BMC Customer Support, accessed via a browser
App Visibility portal control portHTTPS8102Communication with the paired portal node for HA
App Visibility portal databaseHTTPS8800

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 collectorHTTPS8200

Communication to an App Visibility collector from the following components:

  • App Visibility portal
  • App Visibility proxy
  • App Visibility agents for Java and .NET
  • TEA Agents
App Visibility collector supportabilityHTTPS8201

Communication to an App Visibility collector supportability console by BMC Customer Support, accessed via a browser

App Visibility collector control portHTTPS8202Communication with the paired collector node for HA
App Visibility collector databaseHTTPS8800

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 proxyHTTPS8300Communication to an App Visibility proxy from an App Visibility portal
App Visibility proxy supportabilityHTTPS8301Communication to an App Visibility proxy for supportability
Beacon receiver, HTTPHTTP880For HTTP pages, receives beacons from the end-user's browsers
Beacon receiver, HTTPSHTTPS8444For HTTPS pages, receives beacons from the end-user's browsers

App Visibility agent for Java

App Visibility agent for Java supportabilityHTTPS50000-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 .NETNot applicableNot applicableNot applicable

Synthetic TEA Agent

Synthetic Transaction Execution Adapter (TEA) AgentNot applicableNot applicableNot applicable

Was this page helpful? Yes No Submitting... Thank you

Comments