There are multiple databases for Presence Server They
can be installed on the same server as Presence Server,
or they can be installed on different servers.
The following table describes the databases that are used with
Presence ServerNote: Some
databases are optional, based on your configuration.
Table 1. Presence Server databasesDatabase name |
Description |
PSDB |
Stores the Presence Server tables
and is the main application database. |
PSURDB |
Stores usage records. |
PSCIDB |
Used to store content indirection documents.
Optionally, the tables and records for this database could be placed
in the PSDB database instead. |
PSSIBUS |
Optional; required only if you are using the
Data store option for JMS messaging, instead of File store. |
During the installation process, an XML file is used to capture
your specific configuration information. The configuration information
is then written to the Presence Server database,
where it can be shared by all servers in the cluster.
The
Presence Server database
contains the following tables:
Table 2. Presence Server databaseTable |
Description |
CONFIG |
Stores configuration information |
PUBLISH |
Stores raw presence documents |
FULLDOC |
Stores combined presence documents |
MANAGING_SERVERS |
Stores information about the managing servers
for subscriptions |
WATCHERS |
Stores pending subscription requests for watcher
information |
PRESENCE_AUTH_RULES |
Stores presence rules documents |
Table 3. Content indirection databaseTable |
Description |
CONTENT_INDIRECTION |
Stores content indirection document information |
Tip: Optional: The CONTENT_INDIRECTION table could
also be located in the Presence Server database.
Table 4. Usage records databaseTable |
Description |
USAGERECORDS |
Stores usage record information |
The SiBus database contains multiple tables created by WebSphere® Application Server for
the SIBus function.