Difference between revisions of "Remote Program Call Server"

From PresenceWiki
Jump to: navigation, search
(Summary)
 
Line 1: Line 1:
 +
==== Key Facts ====
 +
 
{{ComponentQuickFacts|Launches executables, batch files, etc by request|Background Process|Windows Service (typical)|No license required.}}
 
{{ComponentQuickFacts|Launches executables, batch files, etc by request|Background Process|Windows Service (typical)|No license required.}}
  

Latest revision as of 06:15, 30 June 2010

Key Facts

Cog.png
Purpose: Launches executables, batch files, etc by request
Type: Background Process
Started By: Windows Service (typical)

Summary

The Remote Program Call Server (RPC) is a server component that runs on every machine within the Presence Domain (with the exception of client-only machines).

It is responsible for launching executable files on demand, which is required under the following circumstances:

Permissions

In a typical Windows installation the RPC will run as a Windows Service, named "Presence RPC Server". Since all it is responsible for launching the Presence Server and Database Server it is important to ensure that the RPC Server has the permissions required to access any files or resources that the Presence Server will need to access. For this reason it is often a good idea to create a Windows account that the service can run as.



Architecture > Presence Components > Remote Program Call Server

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