Maintenance outage for upgrade on Sunday, September 22

This site, docs.bmc.com, will be inaccessible for two hours starting at 8 AM CDT, Sunday, September 22, for a platform upgrade.

    Page tree
    Skip to end of metadata
    Go to start of metadata

    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:

    Windows commands to start, stop, and verify services

    To start and stop the services on Windows

    On the computers where the App Visibility server components are installed, 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

    If you need to restart the PostgreSQL service, use the following order:

    • Stop the BMC App Visibility PostgreSQL service after you stop the portal and collector services.
    • Start the BMC App Visibility PostgreSQL service before you start the portal and collector services.

    To verify that the services are running on Windows

    On the computers where the App Visibility server components are installed, run services.msc and verify that the services are running.

    Linux commands to start, stop, and verify services

    To start and stop the services on Linux

    On the computers where the App Visibility server components are installed, run the required command to start or stop a service:

    ComponentStart commandStop command
    App Visibility portalservice adop_portal startservice adop_portal stop
    App Visibility collector

    service adop_collector start

    service adop_collector stop
    App Visibility databaseservice av_pgsql startservice av_pgsql stop
    App Visibility proxy

    service adop_apm_proxy start

    service adop_apm_proxy stop

    To start and stop the services on SUSE Linux Enterprise 12

    If the App Visibility server components are installed on SUSE Linux Enterprise 12, run the required command to start or stop a service:

    ComponentStart commandStop command
    App Visibility portalsystemctl start adop_portal.service
    systemctl stop adop_portal.service
    App Visibility collector

    systemctl start adop_collector.service

    systemctl stop adop_collector.service
    App Visibility databasesystemctl start av_pgsql.service
    systemctl stop av_pgsql.service
    App Visibility proxy

    systemctl start adop_apm_proxy.service

    systemctl stop adop_apm_proxy.service

    To verify that the services are running on Linux

    On the computers where the App Visibility server components are installed, 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

    Related topics

    Setting up and managing the App Visibility components and databases

    Importing a KeyStore file or replacing the certificate for the App Visibility proxy

    Starting and stopping services

    Starting and stopping a synthetic TEA Agent as a process