Description:
In an out of the box Service Desk Manager, pdm_status and slstat are used to verify the status of Service Desk Manager processes. However, sometimes it is useful to verify the list of processes via the Windows Task Manager, or the Windows tasklist command.
Solution:
Before checking that the task list does include the expected set of processes, you may first want to check Windows Services to confirm whether the server is a primary Service Desk server or a secondary Service Desk server. For this, please review Figure 1 and Figure 2 below.
To view the running Windows process, you can either start the Task Manager or run the tasklist command.
The following list is a set of possible Service Desk processes that may be returned when you run "tasklist" on the primary Service Desk server. Note that, in this case, the database management system is SQL Server; this is indicated by the presence of sql_agent_nxd.exe.
animator_nxd.exe arcpur_srvr.exe bpebr_nxd.exe bpeid_nxd.exe bpnotify_nxd.exe bpvirtdb_srvr.exe boplgin.exe bu_daemon.exe dbmonitor_nxd.exe domsrvr.exe domsrvr.exe ehc_nxd.exe ehm_nxd.exe java.exe javaw.exe keit_daemon.exe kpi_daemon.exe krc_daemon.exe kt_daemon.exe ldap_virtdb.exe lexagent_nxd.exe licService.exe license_nxd.exe mdb_registration_nxd.exe pcrpt_nxd.exe pdm_d_mgr.exe pdm_export_mgr.exe pdm_global_nxd.exe pdm_mail_nxd.exe pdm_maileater_nxd.exe pdm_proctor_nxd.exe pdm_text_nxd.exe pdm_tomcat_nxd.exe pdm_ver_nxd.exe rep_daemon.exe spel_srvr.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_agent_nxd.exe sql_prov_nxd.exe sslump_nxd.exe ttv_nxd.exe webengine.exe webengine.exe
The following list is a set of possible Service Desk processes that may be returned when you run "tasklist" on a secondary Service Desk server:
domsrvr.exe javaw.exe javaw.exe pdm_proctor_nxd.exe pdm_tomcat_nxd.exe spel_srvr.exe webengine.exe
Keep in mind, that it is possible to configure the Service Desk Manager primary and secondary servers differently than the out-of-the-box configuration. For example, you may have offloaded the boplogin process from the primary server to a secondary server. In that case, the task list would show boplogin.exe running on the secondary machine and not on the primary machine.
So, even though, on the secondary server, this command:
tasklist /FI SERVICES eq pdm_daemon_proctor
returns only:
pdm_proctor_nxd.exe 4052 Services 0 1,640 K
there are actually other processes running that are associated with Service Desk and these processes have been started through the proctor by the daemon manager on the primary Service Desk server. After the primary Service Desk server is stopped, pdm_proctor_nxd.exe is the only process that should still be running.
If, after stopping Service Desk Manager service on the primary server and then stopping the service on each secondary server, you find that some of the processes are still running, then there may be a problem restarting Service Desk Manager if the remaining processes are not cleaned up beforehand.
Figure 1. Windows Services : primary Service Desk Manager Server
<Please see attached file for image>
Figure 2. Windows Services : secondary Service Desk Manager Server
<Please see attached file for image>