A full Presence installation can consist of several processes.
Firstly there are 2 services.
An RPC (Remote Program Call) Service, which is used to enable Presence installations running on different machines to communicate with each other.
All machines that are running a Presence Server should be running the RPC service as this lets the Heartbeat talk to the Presence Server.
The RPC service runs the prpc.exe.
The Heartbeat Service controls the main Presence apps and should be running on the same machine that the Presence Database is installed on. Even in a multi server environment there should be only one Heartbeat Service running. This controls the Database Server, the Presence Servers and the Httpservers.
The Heartbeat Service Runs the hbserver.exe
Starting the Heartbeat Client (on any machine) will let you identify which Programs are running (and on which machines).
When you start the Heartbeat Client it will ask you which machine you want to connect to. This should be the machine that is running the Heartbeat Server and Presence Database.
You can tell which Presence processes are running on a given machine through the Task Manager.
If you wish to kill a process be sure to right click and select 'End Process Tree' as this will kill the exe and the associated java.exe process.
List of Exes:-
channelman.exe - The Channel Manager, used to manage message channels. dbserv.exe - runs the internal presence Database Server (Only one machine should be running this). hbserver.exe - runs the Heartbeat Server (Only one machine should be running this). httpstart.exe - The HTTP Server, used to respond to dynamic requests. presadmin.exe - The Administration Client, used to create, edit and manage Presence tasks. Connects to the Presence Database. presenceserver.exe - The Presence Server runs the Presence tasks. Several machines can run this utilising the load balancing. prpc.exe - The Remote Program Call Server program. As stated above this is used to by a Presence Server to communicate with the Heartbeat.