Difference between revisions of "Presence Server"

From PresenceWiki
Jump to: navigation, search
m (Work Server moved to Presence Server: I don't know why we called it the work server...)
(Troubleshooting)
 
(23 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Work Server ==
+
==== Key Facts ====
  
The Presence Work Server (also known as just the Presence Server) contains the execution engine for running [[Presence Tasks]]. It also contains the On Demand Server and Web Service engine.
+
{{ComponentQuickFacts|Task execution ([[Debug]], [[Scheduled]], [[On Demand]], [[SOAP]])|Background Process|[[Heartbeat Server]] via [[Remote Program Call Server]]|One license per server}}
  
In a typical installation the Work Server is launched by the [[Heartbeat Server]], and can be stopped and started by the [[Heartbeat Client]].
+
==== 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:
  
== Port Usage ==
+
* [[Debug]]
 +
* [[Scheduled]]
 +
* [[On Demand]]
 +
* [[SOAP]] invocation
 +
 
 +
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.
 
The Presence Server uses a number of TCP/IP ports for internal communication. These are documented in the [[Server Ports]] page.
  
== Task Execution ==
+
==== Troubleshooting ====
 +
 
 +
'''Presence will not start, or exits immediately'''
 +
 
 +
* Ensure the [[Database Server]] is running
 +
* Check that the user owning the process "presenceserver.exe" has read/write permissions to the Presence installation directory
 +
* Check the [[Server Ports]] page to verify there are no port conflicts
 +
* Check to make sure you have a valid Licence file for the server.
 +
 
 +
==== Logging ====
 +
 
 +
At present the Presence server logs can be found the following locations:
 +
 
 +
* "presoutput" folder in installation user's "documents and settings" folder
 +
* "res/logs/server" directory
 +
 
 +
We are currently working on consolidating the log output of each of the Presence processes to a single location.
  
When multiple Work Servers are in place Tasks will be executed on an appropriate server based on [[Load Balancing]] settings.
+
{{ArchitectureLinks|Server Components}}

Latest revision as of 10:55, 19 August 2015

Key Facts

Cog.png
Purpose: Task execution (Debug, Scheduled, On Demand, SOAP)
Type: Background Process
Started By: Heartbeat Server via Remote Program Call 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.

Troubleshooting

Presence will not start, or exits immediately

  • Ensure the Database Server is running
  • Check that the user owning the process "presenceserver.exe" has read/write permissions to the Presence installation directory
  • Check the Server Ports page to verify there are no port conflicts
  • Check to make sure you have a valid Licence file for the server.

Logging

At present the Presence server logs can be found the following locations:

  • "presoutput" folder in installation user's "documents and settings" folder
  • "res/logs/server" directory

We are currently working on consolidating the log output of each of the Presence processes to a single location.


Architecture > Server Components > Presence Server

Heartbeat Server | Database Server | Presence Server | HTTP Server | Remote Program Call Server
Administration Client | Heartbeat Client