Starting and stopping the App Visibility server services

This topic provides the Windows and Linux commands to stop and start the services for the App Visibility server components, and to verify that the services are running.

The App Visibility server comprises services for the following components:

App Visibility portal
App Visibility collector
App Visibility database (installed with the portal and collector)
App Visibility proxy

After you manually change configuration files for these components, you must restart the component service.

This topic presents the following sections:

Linux commands to start and stop services

To start and stop the services on Linux

Run the required command to start or stop a service:

Component	Start command	Stop command
App Visibility portal	`service adop_portal start`	`service adop_portal stop`
App Visibility collector	`service adop_collector start`	`service adop_collector stop`
App Visibility database	`service av_pgsql start`	`service av_pgsql stop`
App Visibility proxy	`service adop_apm_proxy start`	`service adop_apm_proxy stop`

To verify that the services are running on 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
service av_pgsql status

Windows commands to start and stop services

To start and stop the services on Windows

Use the Windows services manager (services.msc) to stop and start the App Visibility server components.

The following services are listed for their respective installed components:

BMC App Visibility Collector
BMC App Visibility Portal
BMC App Visibility PostgreSQL
BMC App Visibility Proxy

Note

Start the BMC App Visibility PostgreSQL service before you start the portal and collector services.

Stop the BMC App Visibility PostgreSQL service after you stop the portal and collector services.

To verify that the services are running on Windows

Run services.msc and verify that the services are running.

Page tree