Verifying the App Visibility server component installations

To verify that the App Visibility server installation was successful

1. Access the adopserver_install_log file that is located in the %temp% directory (Windows) or /tmp folder (Linux).
2. Check for warnings or errors.
   If no error messages are present, the installation was successful.
3. According to what you installed, verify that the App Visibility server components are running:
   • (Windows) Run services.msc and verify that services are running:
     • BMC App Visibility Collector
     • BMC App Visibility Portal
     • BMC App Visibility PostgreSQL
     • BMC App Visibility Proxy

   • (Linux) Run the following commands to verify that the processes are running:

     ps -ea|grep adop_collectord
     ps -ea|grep adop_portald
     ps -ea|grep adop_apm_proxyd
     ps -ea|grep av_pgsqld

4. Check for errors reported in the App Visibility log files in the following locations:

   • Windows
     
     • server_installationDirectory\collector\logs\collector.log
     • server_installationDirectory\portal\logs\portal.log
     • server_installationDirectory\apm-proxy\logs\apm-proxy.log
   • Linux
     
     • server_installationDirectory/collector/logs/collector.log
     • server_installationDirectory/portal/logs/portal.log
     • server_installationDirectory/apm-proxy/logs/apm-proxy.log

   
   

   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.

5. After you add App Visibility to the TrueSight console, see the Components page of the TrueSight console to confirm that the portal is connected.

Where to go from here

Installing-an-App-Visibility-agent-for-Java

Installing-an-App-Visibility-agent-for-NET

Installing-a-Transaction-Execution-Adapter-Agent (TEA Agent)