Starting and stopping the AppWatcher process

The AppWatcher process manages the other data collection processes, restarting them if they are not running.

If the capturing of monitoring data is enabled, the AppWatcher process is automatically started when the engine system is started. If you implemented a method of starting the AppWatcher process for a release of InfoSphere® Information Server before Version 11.3, it is no longer needed.

The AppWatcher process creates log files in the /InformationServer/Server/DSODB/logs directory. All AppWatcher start and stop requests are recorded in the AppWatcher_Cmd.log file.

When AppWatcher is started a log file called AppWatcher_Svc-YYYYMMDDHHMMSS.log is created, where YYYYMMDDHHMMSS is the date and time when the AppWatcher instance was started. This file is used to log any issues for that instance of AppWatcher.

Starting the AppWatcher process

You can use these commands to start the AppWatcher process.

Start the AppWatcher process.

Option Description

UNIX and Linux

Option	Description
UNIX and Linux	Issue this command from the /InformationServer/Server/DSODB/bin directory: `DSAppWatcher.sh –start` This command must be run as dsadm or an equivalent user. The AppWatcher process is run in the background so the command returns as soon as it has finished starting the other processes. The command does not wait for the other processes to enter the RUNNING state. Add this command to the same place as the `uvadmin –start` command in the InfoSphere Information Server engine startup scripts.
Windows	Issue these commands to start the Windows service: `net start "DataStage AppWatcher Service"` If the command fails, the following service specific return codes might be shown in the failure message: 1 The AppWatcher service was already running. 3 The AppWatcher service was not started because the collection of monitoring data is not enabled in the configuration file. 21 The request to start the AppWatcher process timed out You can set the AppWatcher service to start when the system is rebooted by setting its Startup Type to Automatic on the Windows Services dialog.

Issue this command from the /InformationServer/Server/DSODB/bin directory:

DSAppWatcher.sh –start

This command must be run as dsadm or an equivalent user. The AppWatcher process is run in the background so the command returns as soon as it has finished starting the other processes. The command does not wait for the other processes to enter the RUNNING state.

Add this command to the same place as the uvadmin –start command in the InfoSphere Information Server engine startup scripts.

Windows

Issue these commands to start the Windows service:

net start "DataStage AppWatcher Service"

If the command fails, the following service specific return codes might be shown in the failure message:

1: The AppWatcher service was already running.
3: The AppWatcher service was not started because the collection of monitoring data is not enabled in the configuration file.
21: The request to start the AppWatcher process timed out

You can set the AppWatcher service to start when the system is rebooted by setting its Startup Type to Automatic on the Windows Services dialog.

Stopping the AppWatcher process

You can use these commands to stop the AppWatcher process.

Stop the AppWatcher process.

Option	Description
UNIX and Linux	Issue this command from the /InformationServer/Server/DSODB/bin directory: `DSAppWatcher.sh –stop` The command stops the AppWatcher process and all the data collection processes that it manages.
Windows	Issue these commands to stop the Windows service: `net stop "DataStage AppWatcher Service"` The command stops the AppWatcher process and all the data collection processes that it manages.