understanding System Monitor's processes
The Fleetwatch system runs as a mix of processes and services. The system runs under a dedicated local Admin account, and no processes should run under any other account.
Processes: System Monitor, Messaging Manager, System Monitor’s Monitor
Services: Apache, CommServer
While connecting to the server is okay, no other Users or Administrators should start additional instances of the Fleetwatch processes. If you are unsure if System Monitor is running under another account, check Task Manager before launching System Monitor.
Click on Show processes from all users. System Monitor and other Fleetwatch programs should only be running in the Fleetwatch local admin run account. Reach out to Fleetwatch support if there are questions about the programs and accounts.
Here’s an example of Task Manager showing processes running under fwadmin. These shouldn’t be running under any other account.
Processes running only in the Fleetwatch local admin account:
• Fuel Island Monitor software (System Monitor.exe), one instance only.
• Interface control class module for the RIH3000 series interface set, SQL Version (fwRIHSQLControlClass35.exe), one for each of the Fleetwatch fuel lane and/or maintenance bay RIH units at the transit agency.
• Watchdog Interface Control (FW_Watchdog 3.exe), one instance only.
• Messaging Manager 3.exe *32, aka Database Synchronization Manager for Fleetwatch Databases, one instance only.
If Users log on as the Fleetwatch local admin User via Remote Desktop (RDP) session, please instruct users to not log off of the account when they’re done. Instead, Users should lock the Windows session and disconnect from the RDP session. If users do log out of the run account, the service lanes will run on standalone mode, fueling operations can continue, but data won’t be pushed to the server until System Monitor is again running under the run account.