Hi Adr,
have a look at the manual
Using System Health -> Chapter 6: Managing BSM Processes
..
The following table displays the processes that run on the BSM servers:
..
It lists all processes BSM consists of.
You might need to get the real name as reported on the system, for example
dbloader Runs the component on the server which loads the data into the database.
Process name: mercury_db_loader
but on Windows the real process name (which you might need to monitor it) is "hpbsm_db_loader.exe".
C:\HPBSM\AppServer\resources>tasklist | findstr hpbsm
hpbsm_RTSM.exe 11592 Services 0 673,844 K
hpbsm_pmanager.exe 11080 Services 0 174,440 K
hpbsm_marble_loader.exe 4104 Services 0 202,828 K
hpbsm_analytics_loader.ex 8148 Services 0 353,384 K
hpbsm_db_loader.exe 12928 Services 0 216,832 K
hpbsm_marble_worker_1.exe 5948 Services 0 353,216 K
hpbsm_marble_matcher.exe 2064 Services 0 136,736 K
hpbsm_wde.exe 9188 Services 0 447,832 K
hpbsm_marble_supervisor.e 336 Services 0 250,328 K
hpbsm_offline_engine.exe 14464 Services 0 279,896 K
hpbsm_basel_engine.exe 11224 Services 0 188,632 K
hpbsm_opr-scripting-host. 7672 Services 0 240,420 K
hpbsm_pi_engine.exe 11008 Services 0 241,540 K
hpbsm_opr-backend.exe 11920 Services 0 617,180 K
hpbsm_bizImpact.exe 7296 Services 0 112,512 K
plus Nanny, HortnetQ and the webserver
Depending on the Server Deployment and installation type (typical, GW or DPS) you might need to customize the list of processes you monitor.
While BSM can live and will continue to run with some processes being down (for example Partition Manager),
all processes have to be up and running, so every process failing is bad.
Greetings
Siggi
P.S.: Below you'll find a screenshot from Process Explorer showing the usual process of a small single server deplyoment
