PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
Go to start of metadata

On this page:


The scripts to start and stop the Controller and other AppDynamics platform processes are located in the <controller_home>/bin directory. Using the scripts, you can start the processes that comprise the platform individually or all at once. 

Starting or stopping individually allows you to turn off data collection (by shutting down just the app server, for instance) while performing database operations. The startController script starts both the database and app server with one command. Similarly, the stopController scripts turn off both the Glassfish application server and the database.

To avoid the possibility of data corruption errors, be sure to stop the application server and database gracefully (that is, by using the stop scripts described on this page) before shutting off or rebooting the machine on which the Controller is running.

Start and Stop the Controller

On Linux

To start the Controller on Linux, run this script from the Controller home:

bin/startController.sh

To stop the Controller on Linux: 

bin/stopController.sh
On Windows

For Windows, note that the Controller processes are automatically installed as a service. To start the services, run this script from the Controller home:

bin\startControllerSvcs.bat

To stop the Controller services:

bin\stopControllerSvcs.bat 

If you have uninstalled the Controller as a Windows service for any reason, use these scripts to stop and start the Controller: startController.bat and stopController.bat from an elevated command prompt (run as administrator).

Never stop the Controller or its individual services (the AppDynamics Application service or AppDynamics Database services) from the task manager. To stop and restart the AppDynamics processes, open an elevated command prompt (run as administrator) and run the scripts for starting and stopping the service.  

Start and Stop the Controller App Server

On Linux

Start the app server by running this script from the Controller home:

bin/controller.sh start-appserver

Stop the app server using this command: 

bin/controller.sh stop-appserver
On Windows

Run the following command in an elevated command prompt from the Controller home:

bin\controller.bat start-appserver

Stop the app server using this command:

bin\controller.bat stop-appserver

Start and Stop the Controller Database

On Linux

Start the database by running this command from the Controller home:

bin/controller.sh start-db

Stop the database by running this command: 

bin/controller.sh stop-db
On Windows

Stop the database by running the following command in an elevated command prompt:

bin\controller.bat start-db

Stop the database by running this command:

bin\controller.bat stop-db

Start and Stop the Events Service

The events service is an internal data storage engine used by the Database Monitoring module.

The events service is off by default. To use Database Monitoring, you need to start the events service. 

On Linux

Start the events service on Linux by running this command from the Controller home:

bin/controller.sh start-events-service

Stop the events service by running this command: 

bin/controller.sh stop-events-service
On Windows

Start the events service on Windows by running this command from the Controller home:

bin\controller.bat start-events-service

Stop the events service by running this command:

bin\controller.bat stop-events-service

Additional Commands

If you run the controller script with no arguments, the command prints all options it accepts. These include commands, for example, for starting and stopping the events service or reporting service, logging in to the database, and stopping HTTP listeners.

In general, you should use these additional operations only as specifically instructed by the AppDynamics documentation or by AppDynamics support.

 

  • No labels