Difference between revisions of "Presence Server"
(→Port Usage) |
(→Task Execution) |
||
| Line 26: | Line 26: | ||
The Presence Server uses a number of TCP/IP ports for internal communication. These are documented in the [[Server Ports]] page. | The Presence Server uses a number of TCP/IP ports for internal communication. These are documented in the [[Server Ports]] page. | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 10:18, 29 June 2010
Presence Work Server
Key Facts
| Purpose: | Task execution (Debug, Scheduled, 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:
Users 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. The frequency with which individual servers execute Tasks is controlled by the Load Balancing settings.
Port Usage
The Presence Server uses a number of TCP/IP ports for internal communication. These are documented in the Server Ports page.
