Difference between revisions of "Database Server"
From PresenceWiki
(→Database Server) |
(→Database Server) |
||
| Line 7: | Line 7: | ||
Presence uses IBM Pointbase (TM) to store all internal data and state. The Database Server is installed as part of a Presence full installation, or can be installed separately. | Presence uses IBM Pointbase (TM) to store all internal data and state. The Database Server is installed as part of a Presence full installation, or can be installed separately. | ||
| − | In order for the [[Administration Client]] and [[ | + | In order for the [[Administration Client]] and [[Presence Server]] to function correctly they must be able to communicate with the Database Server. |
{{ArchitectureLinks|Server Components}} | {{ArchitectureLinks|Server Components}} | ||
Revision as of 11:33, 29 June 2010
| ||
| Purpose: | Internal state / data storage, logging | |
| Type: | Background Process | |
| Started By: | Heartbeat Server via Remote Program Call Server |
Database Server
Presence uses IBM Pointbase (TM) to store all internal data and state. The Database Server is installed as part of a Presence full installation, or can be installed separately.
In order for the Administration Client and Presence Server to function correctly they must be able to communicate with the Database Server.
Architecture > Server Components > Database Server
| Heartbeat Server | Database Server | Presence Server | HTTP Server | Remote Program Call Server |
| Administration Client | Heartbeat Client |
