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

Related ports
For detailed information about all the network ports required for BMC TrueSight Operations Management components, see Network ports.

Tip

Press F to view the table in full-screen mode. 

Note

Ensure that you open ports in your firewall to enable communication between the components.


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

Note

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.

ComponentServiceDefault port numberProtocolFlowFunctionDefault statePort configurable

App Visibility portal

App Visibility portalHTTPS8100TCPInboundCommunication to an App Visibility portal from an App Visibility collector, proxy, and agent, and the TrueSight Presentation Server
EnabledYes
App Visibility portal supportabilityHTTPS8101TCPInboundCommunication to an App Visibility portal for supportabilityEnabledYes
App Visibility portal control portHTTPS8102TCPInboundCommunication with the paired portal node for HAEnabledYes

App Visibility collector

App Visibility collectorHTTPS8200TCPInboundCommunication to an App Visibility collector from an App Visibility portal, proxy, and agentEnabledYes
App Visibility collector supportabilityHTTPS8201TCPInboundCommunication to an App Visibility collector for supportabilityEnabledYes
App Visibility collector control portHTTPS8202TCPInboundCommunication with the paired collector node for HAEnabledYes

App Visibility proxy

App Visibility proxyHTTPS8300TCPInboundCommunication to an App Visibility proxy from an App Visibility portal
EnabledYes
App Visibility proxy supportabilityHTTPS8301TCPInboundCommunication to an App Visibility proxy for supportabilityEnabledYes
Beacon receiver, HTTPHTTP880

TCP

InboundFor HTTP pages, receives beacons from the end-user's browsersEnabledYes
Beacon receiver, HTTPSHTTPS8444TCPInboundFor HTTPS pages, receives beacons from the end-user's browsersEnabledYes

App Visibility database

App Visibility databaseHTTPS8800TCPInboundCommunication to the App Visibility database from an App Visibility portal and collectorEnabledYes

App Visibility agent for Java supportability

App Visibility agent for Java supportabilityHTTPS50000-50100 TCPInboundCommunication to an App Visibility agent for supportabilityEnabledYes

App Visibility agent for .NET

App Visibility agent for .NETNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicable

Synthetic TEA Agent

Synthetic Transaction Execution Adapter (TEA) AgentNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicable

Related topics

Network ports

App Visibility Manager high-availability deployment

Performing the App Visibility server installation

Setting up and managing the App Visibility components and databases

Basic deployment options for TrueSight Operations Management

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

4 Comments

  1. Hi

    This table is really difficult to get an overview of. Can you please provide a picture like there is for this component: https://docs.bmc.com/docs/display/public/tsim10/Network+ports

    Thank you.

    1. Hi Karmo,

      Thank you for commenting on the documentation.

      I added your suggestion to our documentation backlog and will address it as soon as possible.

      Regards,

      Sara

  2.  

    1.  

© Copyright 2013-2016 BMC Software, Inc.
© Copyright 2013-2016 BladeLogic, Inc.
Legal notices