The Java based armonitor starts the BMC Remedy AR System server, BMC Remedy AR System plug-in server, Distributed Server Option (DSO) server, and processes specified in the armonitor.conf (armonitor.cfg) file. The armonitor provides capability to:
- stop a process
- start a process that was stopped earlier by using the stop signal or that failed to start
- restart a process
- monitor the armonitor.conf file for changes made to individual processes
On Windows, armonitor automatically runs as a service called BMC Remedy Action Request System Server.
On UNIX, the arsystem script usually controls armonitor. For more information, see arsystem.
Each file name is listed by its UNIX name. If a Windows equivalent exists, it appears in parentheses after the UNIX name.
If a process terminates, armonitor restarts the process. But if the process terminates for more than four times in 30 seconds, armonitor does not restart that process. The following exception might occur when the AR System server ports are not free and the armonitor tries to start the AR System server:
Some of the ports on this machine are not free. Make sure all the ports required for running server as per documentation are available.
You must perform the following steps to free the ports for Microsoft Windows:
- Open Task Manager > Process tab.
- Click View > Select Column.
- Select the PID (Process Identifier) checkbox and Image Name in the Select Process Page column.
The Image Name helps in identifying the processes that points to a particular process under the AR Installation directory.
- Identify all the processes related to the AR System server.
- End these processes.
- Restart the AR System server when the processes are not displayed in the task list.
The armonitor process maintains the following lists for the processes specified in the armonitor.conf (armonitor.cfg) file.
|STARTED_PROCESSES_LIST||Lists the processes that are currently running|
|FAILED_TO_START_PROCESSES_LIST||Lists the processes which fail to start successfully|
|STOPPED_PROCESSES_LIST||Lists the processes stopped by the user by using the |
Starting from BMC Remedy AR System 9.1, following enhancements are provided to armonitor file:
The ARMonitor.properties file consists of following properties to manage the BMC Remedy AR System processes:
The RMI Port is used by the ARMonitor_Admin to give instructions to armonitor. The property is configured by the ARMonitor.properties file, when the process is started or restarted.
Allows the armonitor process to detect the changes made to the armonitor.conf (armonitor.cfg) file without affecting other BMC Remedy AR System processes.
Default value: False
This property can be set to true or false through the ARMonitor_Admin functions - enablefilemonitor & disablefilemonitor
|Determines the maximum number of attempts that are made to enable the file-monitor|
Timeout value in seconds, for which armonitor will wait for receiving the startup signal from server.
If no signal received from server during this time, the server will not be considered as started and the server process, if running, will be stopped.
|Determines the maximum number of attempts until a server is started before terminating the process.|
|Determines the maximum number of attempts until a non-server process is started before terminating the process.|
ARMonitor_Admin.sh or ARMonitor_Admin.bat
The ARMonitor_Admin.sh (ARMonitor_Admin.bat) is an interface to communicate with the armonitor file using the arguments provided below.
Before you use the ARMonitor_Admin.sh (ARMonitor_Admin.bat) file, ensure that the value of JAVA_HOME is set correctly.
The examples are provided for Microsoft Windows. From Windows Command Prompt, change to the AR System installation directory and enter the following commands:
Checks if the armonitor.conf (armonitor.cfg) file is running
Stops all the processes specified in the armonitor.conf (armonitor.cfg) file and stops armonitor process.
Lists all processes that are currently running
Lists all processes sorted according to whether the process is successfully started, whether it failed to start, or whether the user has stopped the process with ARMONITOR_ADMIN calls
Stops the specific process if the process is currently running
Starts a process if the process is not currently running
Restarts a process using the process name assigned to the process
Refreshes the process with a new process definition read from the armonitor.conf (armonitor.cfg) file.
Provides the process command assigned to the process.
Provides the process details for all the processes specified in the armonitor.conf (armonitor.cfg) file
Returns TRUE or FALSE based on whether the FILE_MONITOR option is enabled or disabled
Enables the FILE_MONITOR feature for armonitor and also updates the
Disables the FILE_MONITOR feature for armonitor and also updates the
If you add a new parameter to an already running process, the armonitor considers this as a new process and starts the process again. This creates two instances of the same process running in armonitor which results in to an error. Ensure that you stop the running process by using
stopprocess argument before editing the process.
Starting from BMC Remedy AR System 9.1 a new FILE_MONITOR feature is added to armonitor to monitor the armonitor.conf (armonitor.cfg) file for changes. The
disablefilemonitor arguments are used to enable or disable the FILE_MONITOR feature.
The FILE_MONITOR provides following features when you modify the armonitor.conf (armonitor.cfg) file:
- If a new process is modified, the process is started automatically without affecting other processes running in the armonitor.conf (armonitor.cfg) file.
- If any numeric parameters of a process are modified, the same process is restarted by the armonitor with the new parameter values.
The armonitor.cgf file has the following new entries:
- External-Windows-Service: process-type = BMC:EmailEngine, service-name="BMC Remedy Email Engine - 1"
- External-Windows-Service: process-type = BMC:FlashBoardServer, service-name="BMC Remedy Flashboards Server -
These entries are used to start and stop the Flashboard and Email engine services when you apply a patch that is provided as a binary payload.