A full Presence installation can consist of several processes.
Firstly there are 2 services.
The 'Presence RPC Server' service runs the Remote Program Call Server.
This is used to enable Presence installations running on different machines to communicate with each other.
The Remote Program Call Server runs the prpc.exe.
The 'Presence Viii Heart Beat Server' service runs the Heartbeat Server.
Even in a multi server environment there should be only one Heartbeat Server running on just one machine only.
The Heartbeat Server 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.
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 also 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 Database Server. 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. Used to by a Presence Server to communicate with the Heartbeat.
To view an uptodate list of TCP/IP ports used by Presence processes, please view the Server Ports page.