Starting and stopping the TrueSight Operations Management components

Use the following sections to understand services and scripts used for starting and stopping the TrueSight Operations Management components.

Additionally, find out how these services or scripts are integrated in the operating system.

Related topics

Starting or stopping the Remedy SSO service

Installing

Upgrading

Starting and stopping the Presentation Server

Starting and stopping the Presentation Server on Windows

The following service can be used to start and stop the core server, Index server, and the database server from services.msc.

You can also start and stop this service by running the tssh server command.

For more information, see Presentation Server tssh commands.

Starting and stopping Presentation Server on Linux

The BMCTSPSSvc script located at /etc/init.d starts and stops the Presentation Server on Linux.

TrueSight Presentation Server can be installed by a non-root user only. Therefore, the installer does not have sufficient permissions to automatically create the BMCTSPSSvc script used for starting the Presentation Server.

You need to run the tssh service command to register the service which in turn performs the following actions:

  • Creates the BMCTSPSSvc script in the /etc/init.d directory.

  • Creates the following soft links located at /etc/<RunLevel>.

You can start or stop the Presentation Server by running the following commands:


Starting and stopping Infrastructure Management components

Starting and stopping Infrastructure Management on Windows

You can start and stop the Infrastructure Management server in the following ways:

The following table lists the services available for the various Infrastructure Management components. These services can be started or stopped from services.msc.

Starting and stopping Infrastructure Management on Linux

The BMCTrueSight script located at /etc/init.d can be used to start and stop Infrastructure Management on Linux.

If you have installed Infrastructure Management as a root user, the installer automatically creates the BMCTrueSight script in the /etc/init.d directory and also creates the following soft links located at /etc/<RunLevel>:

The BMCTrueSight script automatically starts the Infrastructure Management server on machine restart.

If you installed Infrastructure Management as a non-root user, you need to enable the creation of the BMCTrueSight script. To do this, run the create_startup_script script located at pw/scripts with root user permissions.

You can also start or stop Infrastructure Management by running the pw sys command. To do this, access the pw CLI and run the pw sys start command or the pw sys stop command.

Starting and stopping the Integration Service on Windows

The following service can be used to start and stop the Integration Service from services.msc.

For more information about starting or stopping the service, see Verifying-that-the-Integration-Service-is-running-on-Microsoft-Windows.

Starting and stopping Integration Service on Linux

The S81pronto.0.<instance number> script located at /etc/rc2.d/ can be used to start and stop the Integration Service on Linux.

The installer creates the following scripts that start and stop the pronet_agent process corresponding to the Integration Service. These scripts are located at <IntegrationService-InstallationDirectory>/pw/pronto/bin.

When you restart the computer hosting an Integration Service, the S81pronto.0.<instance number> script runs the startremotepw script to start the Integration Service.

Note: The S81pronto.0.<instance number> script is created if you install the Integration Service as a root user. As a non-root user, you need to ask your adminstrator (or super user) to manually copy the s81pronto.xxxx file from <installationDirectory>/pw/pronto/bin to all the etc/rc.d/rc<runLevel>/.d files.

For more information about starting or stopping the service, see Verifying-that-the-Integration-Service-is-running-on-Linux.

Starting and stopping the remote cell on Windows

The following service can be used to start and stop the Integration Service from services.msc.

Starting and stopping the remote cell on Linux

The mc_<CellName> script located at etc/init.d can be used to start and stop the remote cell process on Linux.

The installer creates the following soft links located at /etc/<RunLevel>.

The following commands can help you start, stop, and view the status of the remote cell process:

Starting and stopping the App Visibility server

To start and stop the App Visibility server services in 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 start and stop the App Visibility server services in Linux

On the computers where the App Visibility server components are installed, 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 start and stop the App Visibility server services in 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:

Component

Start command

Stop command

App Visibility portal

systemctl start adop_portal.service

systemctl stop adop_portal.service

App Visibility collector

systemctl start adop_collector.service

systemctl stop adop_collector.service

App Visibility database

systemctl start av_pgsql.service

systemctl stop av_pgsql.service

App Visibility proxy

systemctl start adop_apm_proxy.service

systemctl stop adop_apm_proxy.service

Starting and stopping a synthetic TEA Agent as a process

To start the synthetic TEA Agent as a process

  1. On the TEA Agent computer, navigate to the installationDirectory\TEAAgent directory, for example, C:\Program Files (x86)\BMC Software\BMCTEAAgent\TEAAgent directory.
  2. Right-click the start_agent.bat file, and select Run as administrator.

A command prompt opens and displays the status of the TEA Agent.

To stop the synthetic TEA Agent process

To stop the TEA Agent process, press Ctrl+C to terminate the batch file in the command window.

Starting and stopping the Real User Analyzer or Collector

To start the Real User Analyzer or Collector service

  1. Log in to the virtual machine with the Real User Analyzer or Collector installation as root.
  2. Run the required command in a command prompt:

    • service euem_analyzer start
    • service euem_collector start

If the Real User Analyzer or Collector component service is working after the start command, you will see the Real User Analyzer or Collector Console in a supported browser.

To stop the Real User Analyzer or Collector service

  1. Log in to the virtual machine with the Real User Analyzer or Collector installation as root.
  2. Run the required command in a command prompt:

    • service euem_analyzer stop
    • service euem_collector stop
Warning

If you use a kill command to stop the Real User Analyzer or Collector component, the component service continues to operate. The component and the database stops working but the operating system maintains the component as a continuing service.

Starting and stopping the Real User Cloud Probe

To start or stop the Cloud Probe in Linux

  1. Log in to the virtual machine with the Real User Cloud Probe installation as root.
  2. Run the required command in a command prompt:
    • service cloud-probe start
    • service cloud-probe stop

To start or stop the Cloud Probe in Windows

  1. Run the services.msc command.
  2. In the list of services, right-click on the BMC Real User Cloud Probe service and use the following options accordingly:

    • Start
    • Stop
    • Restart


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*