P2000 Publications - Johnson Controls P2000 Configuration

Enterprise Configuration

P2000 Publications

The following publications are established in P2000:
Enterprise - mandatory for all enterprise sites; contains site and subscription

information.
Configuration - contains cardholder, badge and other configuration

information.
FDA - contains all secondary tables for FDA compliance (when applicable)

that are in the P2000 database.
Alarms - contains alarm information.

Transaction - contains transaction history information.

Audit - contains audit information.

BadgeImages - contains cardholder fingerprints, portraits and signatures.

BadgeImages FDA - contains all secondary tables for FDA compliance from

the BadgeImages database.
The main reason for establishing multiple publications is to logically separate the
different components of the Pegasys and BadgeImages database. You can establish
and use either all of these publications or a subset of them.
Do not establish a publication unless you want a regional server to receive this
information through database replication. The main publications are Configuration
and BadgeImages. Typical subscriptions that you might not want to establish are:
FDA - the only reason to replicate them to the central server would be to have

a remote storage location for them.
Alarms - rather than be replicated, they can be sent to another system using

P2000 Remote Message Server to become instantly available for Alarm
Monitors.
Transaction - like Alarms, they can be sent to another system using P2000

Remote Message Server and would then be displayed in the P2000 Real Time
List, whereas replication only adds them to the database for reporting
purposes, (also achieved by the P2000 Remote Message Server).
Audit - as Transaction.

BadgeImages FDA - the only reason to replicate them to the central server

would be to have a remote storage location for them.
The main advantage of the MS SQL Server Database Replication versus the P2000
Remote Message Server is that when using replication, the audit and transaction
messages are transferred to the P2000 Central Server even after the network
connection has been disrupted and restored. In case of lasting network connection
disruption, the message buffer within the P2000 Remote Message Server may not be
sufficient to buffer all messages generated by the local system.
24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
Introduction
1-5