Johnson Controls P2000 Quick guide

P2000
Security Management System
Version 3.10 and higher, June, 2010
24-10515-21 Revision –
Enterprise Configuration

Security Solutions
[phone]
www.johnsoncontrols.com
P2000
Security Management System
Enterprise Configuration
Version 3.10 and higher, June, 2010
24-10515-21 Revision –

Copyright 2010
Johnson Controls, Inc.
All Rights Reserved
No part of this document may be reproduced without the prior permission of Johnson Controls, Inc.

Acknowledgment
Cardkey P2000, BadgeMaster, and Metasys are trademarks of Johnson Controls, Inc.
All other company and product names are trademarks or registered trademarks of their
respective owners.
If this document is translated from the original English version by Johnson Controls, Inc., all
reasonable endeavors will be used to ensure the accuracy of translation. Johnson Controls, Inc.
shall not be liable for any translation errors contained herein or for incidental or consequential
damages in connection with the furnishing or use of this translated material.
Due to continuous development of our products, the information in this document is subject to
change without notice. Johnson Controls, Inc. shall not be liable for errors contained herein or
for incidental or consequential damages in connection with furnishing or use of this material.
Contents of this publication may be preliminary and/or may be changed at any time without any
obligation to notify anyone of such revision or change, and shall not be regarded as a warranty.
Declaration of Conformity
This product complies with the requirements of the European Council Electromagnetic
Compatibility Directive 2004/108/EEC and the Low Voltage Directive 2006/95/EEC.
This equipment must not be modified for any reason and it must be installed as stated in the
Manufacturer’s instruction.
If this shipment (or any part thereof) is supplied as second-hand equipment, equipment for sale
outside the European Economic Area or as spare parts for either a single unit or system, it is not
covered by the Directives.

TABLE OF CONTENTS
24-10515-21 Rev. – v
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
Chapter 1: Introduction
About This Manual................................................................................................................................... 1-1
Manual Summary..................................................................................................................................... 1-1
Technical Support ............................................................................................................................ 1-2
Qualification for Installation and Use................................................................................................ 1-2
Note on Other Manufacturer’s Documentation................................................................................. 1-2
Manual Conventions ........................................................................................................................ 1-2
About the P2000 Enterprise Configuration .............................................................................................. 1-3
Key Terms........................................................................................................................................ 1-4
P2000 Publications .......................................................................................................................... 1-5
Chapter 2: Configuring P2000 Central Server
SQL Server Login Account ...................................................................................................................... 2-2
Creating the “psqlserver” Account.................................................................................................... 2-2
Logging into the “psqlserver” Account.............................................................................................. 2-8
Connecting to the SQL Server ................................................................................................................. 2-8
Establishing Shared Directories............................................................................................................. 2-11
Configuring Publisher and Distributor .................................................................................................... 2-14
Generating P2000 Stored Procedures........................................................................................... 2-19
Establishing an Enterprise System ........................................................................................................ 2-20
Populating the Enterprise Settings......................................................................................................... 2-21
Setting Up P2000 Publications .............................................................................................................. 2-22
Snapshots.............................................................................................................................................. 2-25
Replication Set Identity Range............................................................................................................... 2-26
Chapter 3: Merging Data Between Sites
Merging Data Between Sites ................................................................................................................... 3-1
Live System Upgrade to Enterprise Configuration Using Additional Hardware ............................... 3-2
Live System Upgrade to Enterprise Configuration Without Additional Hardware .......................... 3-12
Rules for Data Merging .......................................................................................................................... 3-17
Chapter 4: Configuring P2000 Regional Server
Preparing for Configuration...................................................................................................................... 4-1
Changing the Login Account.................................................................................................................... 4-1
Connecting to the SQL Server ................................................................................................................. 4-4
Establishing Subscriptions ....................................................................................................................... 4-4
Replication Set Identity Range............................................................................................................... 4-17

Table of Contents Enterprise Configuration
vi 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
Appendix A: Publications
Appendix B: Important Notes
Initialization ......................................................................................................................................B-1
Deadlocks and Retries .....................................................................................................................B-1
Identity Columns ..............................................................................................................................B-1
Primary Key Violation.......................................................................................................................B-1
Calling sp_adjustpublisheridentityrange...........................................................................................B-2
Connectivity Loss .............................................................................................................................B-2

24-10515-21 Rev. – 1-1
Chapter 1
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
INTRODUCTION
The P2000 Enterprise Configuration advanced feature allows customers with multiple sites
to communicate with each other to share Cardholder/Badge information. Cardholders can be
granted access to doors at all assigned sites within the Enterprise system.
In the P2000 Enterprise Configuration, one P2000 site becomes the P2000 Central Site and
all other P2000 systems within the enterprise become P2000 Regional Sites. Each regional
site synchronizes its data with the central site. Database replication is implemented through
the use of Microsoft SQL Server database technologies.
ABOUT THIS MANUAL
This document is to be used as a supplement to the P2000 documentation. It details the
information concerning the P2000 Enterprise Configuration:
Configuring the P2000 Central Site
Moving data from existing P2000 Regional Sites to the P2000 Central Site
Configuring a P2000 Regional Site
NOTE
Throughout this manual, the terms Pegasys and P2000 are used
interchangeably.
NOTE
The screen captures shown in this manual may differ slightly, depending
on the firmware version you are using.
MANUAL SUMMARY
Chapter 1: Introduction, defines the key terms and conventions used throughout the
manual, as well as provides introduction to the P2000 Enterprise system.
Chapter 2: Configuring P2000 Central Server, contains instructions on setting up
the P2000 central server for Enterprise Configuration.

Introduction Enterprise Configuration
1-2 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
Chapter 3: Merging Data Between Sites, describes how to move P2000 Enterprise
Regional Site data to the P2000 Enterprise Central Site.
Chapter 4: Configuring P2000 Regional Server, provides instructions for
establishing P2000 regional server as a Database Subscriber.
Appendix A: Publications, identifies publications and their corresponding articles
(database tables).
Appendix B: Important Notes,provides reference information useful for
troubleshooting.
Technical Support
Technical assistance is provided to Johnson Controls authorized dealer
representatives from 5 a.m. PT (Pacific Time) to 5 p.m. PT Monday through Friday.
System users can get answers to operator questions by calling the local Johnson
Controls Inc. sales/service office.
The authorized dealer representatives can also provide you with information on the
maintenance contracts and the on-site field service.
Qualification for Installation and Use
Installers and users of the P2000 Enterprise Configuration System must complete
appropriate training and obtain certification prior to installing and using this
advanced feature.
Note on Other Manufacturer’s Documentation
Johnson Controls does not duplicate documentation of other equipment
manufacturers. When necessary, as in some installation procedures, we will provide
documentation that supplements other manufacturer’s documentation. When
unpacking your equipment, keep all original manufacturer documentation for
future reference.
Manual Conventions
The following items are used throughout this manual to indicate special
circumstances, exceptions, important points regarding the equipment or personal
safety, or to emphasize a particular point.
NOTE
Notes indicate important points or exceptions to the information provided in
the main text.

!
CAUTION
Cautions remind you that certain actions, if not performed exactly as
stated, can cause damage to equipment, security problems, or cause the
system to operate incorrectly due to errors in system setup or
programming.
WA R N IN G
Warnings indicate that the possibility of personal injury exists if an
action or actions are not performed exactly as stated.
Enterprise Configuration Introduction
24-10515-21 Rev. – 1-3
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
ABOUT THE P2000 ENTERPRISE CONFIGURATION
To implement the P2000 Enterprise Configuration, P2000 utilizes MS SQL Server's
Database Replication.
Data replication for the P2000 Enterprise Configuration is implemented with a Publisher and
Distributor together on one P2000 Central Site, and multiple Subscribers on P2000 Regional
Sites.
In the P2000 Enterprise Configuration, one P2000 site becomes the P2000 Central Site, also
called “central site” or “central server” throughout this manual.
All other P2000 systems within the enterprise become P2000 Regional Sites, also called
“regional sites” or “regional servers” throughout this manual.
Each regional site synchronizes its data with the central site. It receives data updates from the
central site and/or regional sites.
In order for the MS SQL Server Database Replication to operate correctly, the central and
regional sites need to be properly configured. This manual contains information necessary to
perform P2000 Enterprise Configuration.
NOTE
It is strongly recommended that all P2000 servers in the P2000 Enterprise
Configuration system use the same version of the Microsoft SQL Server.

CK720 CK720 CK720
P2000 Regional
Site 3
“GREEN”
CK720 CK720 CK720
Central Site
“CENTRAL”
CK720 CK720 CK720
P2000 Regional
Site 2
“BLUE”
CK720 CK720 CK720
P2000 Regional
Site 1
“ORANGE”
WAN
Introduction Enterprise Configuration
1-4 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
Key Terms
The following section aims to provide a quick translation between the SQL Server
and P2000 terminologies:
Articles – Database tables. An article contains data from a table.
Publication – A set of database tables (for example, Cardholder/Badge) that is made
available for a subscriber by a publisher/distributor.
Publisher/Distributor – The server of the P2000 Central Site
Subscriber – The server of the P2000 Regional Site

Enterprise Configuration Introduction
24-10515-21 Rev. – 1-5
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
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.

Introduction Enterprise Configuration
1-6 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
Ensure proper network connectivity and name resolution. All Regional Servers must
not only successfully ping the Central Server, but also be able to register the Central
Server by name in the SQL Enterprise Manager. The Central Server must be able to
register and open all registered servers in SQL Enterprise Manager.

24-10515-21 Rev. – 2-1
Chapter 2
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
CONFIGURING P2000 CENTRAL SERVER
Prior to configuring the central server, install the P2000 prerequisites and software (see the
P2000 Server/Workstation Software Installation Manual for details) and backup the
databases.
The steps within this section will tell you how to:
Assign a new Microsoft®Windows account to the MS SQL Services
Configure the central site’s database server as Distributor and Publisher
Establish the P2000 Publications
Create snapshots for all P2000 Publications
Use the following tables for reference during P2000 Central and Regional Sites
configuration:
Table 2-1: Central Site Settings
Item Factory Settings Customer Settings
P2000 Server name* CENTRAL
Windows account name** psqlserver
Windows password Master1
SQL server name* CENTRAL
SQL administrator account** sa
SQL administrator account password Master1
Replication Set Identity Range*** 10,000,000 to
20,000,000
* The name has to be unique within the Enterprise system.
** Choosing different settings may impact the setup of your server. It is recommended that you use the factory
settings, or contact Technical Support for assistance.
***Each ID range should be unique within the Enterprise system and cannot be re-used. If you need to re-assign
the server’s ID range, use a new range.

Table 2-2: Regional Site Settings
Item Factory Settings Customer Settings
P2000 Server name* ORANGE
Windows account name**
(the same as for the central server)
psqlserver
Windows password
(the same as for the central server)
Master1
SQL server name* ORANGE
SQL administrator account** 
(the same as for the central server)
sa
SQL administrator account password
(the same as for the central server)
Master1
Replication Set Identity Range*** 20,000,000 to
30,000,000
* The name has to be unique within the Enterprise system.
** Choosing different settings may impact the setup of your server. It is recommended that you use the factory
settings, or contact Technical Support for assistance.
***Each ID range should be unique within the Enterprise system and cannot be re-used. If you need to re-assign
te server’s ID range, use a new range.
Configuring P2000 Central Server Enterprise Configuration
2-2 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
NOTE
The procedures described in this chapter are to be performed starting with
a clean P2000 installation. The P2000 Enterprise Configuration cannot be
set up properly through an upgrade from earlier versions of P2000
software.
SQL SERVER LOGIN ACCOUNT
During replication, SQL Server and SQL Server Agent cannot run as “local system,” but
require a separate account on all participating servers. To create it, follow the steps below.
Creating the “psqlserver” Account
The steps for creating and configuring the “psqlserver” account vary depending on
whether or not the P2000 server is on the domain.
If your P2000 server is noton the domain, follow the steps below. For instructions to
be used on a P2000 server that is on the domain, see page 2-5.

Enterprise Configuration Configuring P2000 Central Server
24-10515-21 Rev. – 2-3
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
To create a local service user account for the SQL Server:
1. Go to Start>Programs>Administrative Tools>Computer Management.
2. In the Computer management window, under Computer Management
(Local) expand the Local Users and Groups folder.
3. Right-click the Users icon and select New User.
4. In the New User window, fill out the following fields:
User name: psqlserver
Full name: SQL Server Service
Description: P2000 SQL service user account
Enter and confirm password (Master1).
Un-select the User must change password at next logon check box.
Select the following check boxes: User cannot change password and
Password never expires. Click Create.
5. Click Close.
6. You are now back to the Computer Management window. In the right window
pane, double-click the psqlserver icon.

Configuring P2000 Central Server Enterprise Configuration
2-4 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
7. The psqlserver Properties window opens. Click the Member Of tab and the
Add... button.
8. In the Select Groups window, click the Advanced… button.
9. In the expanded window, click the Find Now button.
10. From the search results window, double click on Administrators, and then
click OK.
11. You are back to the psqlserver Properties window; verify that psqlserver is
now a member of Administrators. Click OK.

Enterprise Configuration Configuring P2000 Central Server
24-10515-21 Rev. – 2-5
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
12. Close the Computer Management window. Go to “Logging into the
“psqlserver” Account” on page 2-8.
To create a domain user account for the SQL server:
1. At the domain controller, log on to the domain as the system administrator.
2. Go to Start>Programs>Administrative Tools>Active Directory Users and
Computers.
3. In the Active Directory Users and Computers window, under the
CDOMAIN.com icon, right-click Users, and go to New>User.
4. In the New Object-User window, fill out the following fields:
First name: SQL
Last name: Server
User logon name: psqlserver
User logon name (pre-Windows 2000): psqlserver
(for example: CDOMAIN\psqlserver)
Click Next.

Configuring P2000 Central Server Enterprise Configuration
2-6 24-10515-21 Rev. –
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
5. Specify and confirm the password (Master1). Un-select the User must
change password at next logon check-box, then select the following check
boxes: User cannot change password and Password never expires.
Click Next.
6. Verify the settings and click Finish.
7. You are now back to the Active Directory Users and Computers window.
Double-click the Users icon.
8. In the right window panel, double-click the SQL Server icon.
9. The SQL Server Properties window opens. Click the Member Of tab and the
Add... button.
10. In the Select Groups window, click the Advanced… button.
11. In the expanded window, click the Find Now button.
12. Highlight Administrators and click OK.