Difference between revisions of "Presence Server"

From PresenceWiki
Jump to: navigation, search
(Key Facts)
(Summary)
Line 15: Line 15:
  
 
==== Summary ====
 
==== Summary ====
The Presence Work Server (also known as just the Presence Server) is the main Presence execution server. It's primary job is to [[Presence Tasks]], and it does so in the following manners:
+
The Presence Work Server (also known as just the Presence Server) is the main Presence execution server. It's primary job is to run [[Presence Tasks]]. Task execution can be triggered in one of four ways:
  
* Scheduled Task Execution
+
* Scheduled
* On Demand Task Execution
+
* On Demand
* Task Debugging
+
* Debug
* SOAP-invoked Task Execution
+
* SOAP invocation
 +
 
 +
You can install one or more Presence Servers, on different machines or across different virtual machines. If multiple servers are installed they will take it in turns to execute Tasks, which shares the workload across the network. This enables users to scale up their installation as their usage grows, and provides an extra level of redundancy.
  
 
== Load Balancing ==
 
== Load Balancing ==

Revision as of 05:09, 29 June 2010

Presence Work Server

Key Facts

Purpose: Task execution (debug, schedule, on demand, SOAP)
Type: Background Process
Started By: Heartbeat Server via Remote Program Call Server
License Type: One license per server


Summary

The Presence Work Server (also known as just the Presence Server) is the main Presence execution server. It's primary job is to run Presence Tasks. Task execution can be triggered in one of four ways:

  • Scheduled
  • On Demand
  • Debug
  • SOAP invocation

You can install one or more Presence Servers, on different machines or across different virtual machines. If multiple servers are installed they will take it in turns to execute Tasks, which shares the workload across the network. This enables users to scale up their installation as their usage grows, and provides an extra level of redundancy.

Load Balancing

One or more Presence Servers can be installed on different machines (or Virtual Machines) to form a load balanced network. This allows you to scale up your Presence installation as your requirements grow.

In a typical installation the Work Server is launched by the Heartbeat Server, and can be stopped and started by the Heartbeat Client.

Port Usage

The Presence Server uses a number of TCP/IP ports for internal communication. These are documented in the Server Ports page.

Task Execution

When multiple Work Servers are in place Tasks will be executed on an appropriate server based on Load Balancing settings.