P2000 Enterprise Configuration

24-10685-68 Revision BMarch, 2016

enterprise

configuration

P2000Security Management System

version 3.12

Copyright 2016Johnson Controls, Inc.

All Rights Reserved

No part of this document may be reproduced without the prior permission of Johnson Controls, Inc.

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.

Other Manufacturers’ Documentation

Johnson Controls does not duplicate documentation of other equipment manufacturers. When necessary, Johnson Controls provides documentation that supplements that of other manufacturers. When unpacking your equipment, keep all original manufacturer documentation for future reference.

Technical Support

For factory technical support, Johnson Controls authorized field technicians or authorized dealer representatives can contact Global Security Solutions Technical Support by phone at (866) 893-0423 or (414) 524-1214, or by email at [email protected]. They can also call the Field Support Center at (800) 524-1330 or (414) 524-5000 and use options 6, 1, 7.

End users and customers should contact their local Johnson Controls branch or authorized dealer for any of their support needs (technical support, maintenance contracts, on-site field support, P2000 Software Service Agreements, Service Partnerships, and so on). Visit http://www.johnsoncontrols.com/location-finder to find your local Johnson Controls office.

For material returns contact the branch if the material was purchased through a Johnson Controls branch or through the Product Sales Operations Team, if ordered through the Advanced Order Management System (AOMS) and follow the RMA process; or contact the authorized dealer representative where the material was purchased directly.

Acknowledgment

Metasys® and Johnson Controls® are trademarks of Johnson Controls, Inc. All other company and product names are trademarks or registered trademarks of their respective owners.

mailto:[email protected]

http://www.johnsoncontrols.com/location-finder

Enterprise Configuration Table of Contents24-10685-68 Rev. B

TABLE OF CONTENTS

Chapter 1: Introduction

Manual Summary 1-1

About the P2000 Enterprise Configuration 1-2

Key Terms 1-2

Implementation Notes 1-3

P2000 Publications 1-4

Central Site Settings 1-5

Regional Site Settings 1-6

Basic SQL Procedures 1-7

Chapter 2: Configuring P2000 Central Server

Creating Windows Login Account for SQL Server 2-1

Editing “sa” Login Properties 2-8

Changing the Login Account for SQL Services 2-9

Creating Shared Directories 2-10

Configuring Publisher and Distributor 2-11

Establishing an Enterprise System 2-15

Populating the Enterprise Settings 2-16

Setting Up P2000 Publications 2-18

Generating Snapshots 2-18

Setting Up the Replication Identity Range 2-20

Chapter 3: Merging Data Between Sites

Rules for Data Merging 3-1

Merging Data Between Sites 3-2

Live System Upgrade (Additional Hardware) 3-3

Live System Upgrade (No Additional Hardware) 3-10

i

Enterprise Configuration Table of Contents24-10685-68 Rev. B

Chapter 4: Configuring P2000 Regional Server

Preparing for Configuration 4-1

Editing “sa” Login Properties 4-2

Changing the Login Account for SQL Services 4-2

Establishing Subscriptions 4-2

Replication Set Identity Range 4-15

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

ii

Enterprise Configuration Introduction24-10685-68 Rev. B

1. INTRODUCTION

This document is a supplement to the P2000 documentation. It provides information on how to configure your P2000 servers to constitute an enterprise system, where multiple sites share cardholder and badge information.

IMPORTANT: Installers and users of the P2000 Enterprise Configuration System must complete appropriate training and obtain certification before installing and using this advanced feature.

MANUAL SUMMARY

This document is divided into the following chapters and appendices:

Chapter 1: Introduction defines the key terms and provides introduction to the P2000 Enterprise system.

Chapter 2: Configuring P2000 Central Server contains instructions on setting up the P2000 Central Site.

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.

Chapter A: Publications identifies publications and their corresponding articles (database tables).

Chapter B: Important Notes provides reference information useful for troubleshooting.

1-1


ABOUT THE P2000 ENTERPRISE CONFIGURATION

The P2000 Enterprise Configuration advanced feature allows multiple P2000 sites to share cardholder and 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 (also called “central site” or “central server”). All other P2000 systems within the enterprise become P2000 Regional Sites (also called “regional sites” or “regional servers”). Each regional site synchronizes its data with the central site. Database replication is implemented through the use of Microsoft ® SQL Server™ database technologies.

NOTE: You can deploy the P2000 Version 3.12 system in a distributed mode, where the P2000 server is hosted on two separate machines. All the P2000 services run on one machine (P2000 application server), while the P2000 databases are hosted on another machine (P2000 database server). Refer to the Separating the P2000 Application Server from the Database Server document for more information.

Key Terms

The following section provides a quick translation between the SQL Server and P2000 terminologies. Key terms include:

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.

1-2


Figure 1-1: P2000 Enterprise Configuration

Implementation Notes

Throughout this document, the terms Pegasys and P2000 are used interchangeably.

WAN

Central Site

“CENTRAL”

P2000 Regional Site 1

“ORANGE”


“BLUE”


“GREEN”

1-3


We recommend that all P2000 servers in the P2000 Enterprise Configuration system use the same version of the Microsoft SQL Server.

Screen captures and examples provided in this document (including network paths, logins, passwords, and server names) reflect the factory settings. The information on your system may be different and will reflect your custom settings.

New installations of P2000 software version 3.12 create a “P2000” folder, while upgrades from previous versions may use the “Cardkey P2000” folder.

Procedures and screens may vary slightly depending on the software version. However, you can still follow the general outline.

P2000 Publications

The following publications are established in P2000:

The main reason to establish 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 include:

Publication Name Description

Enterprise Contains site and subscription information. This publication is mandatory for all enterprise sites.

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.

1-4


• 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 SQL Server Database Replication over using 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.When network connection disruption is prolonged, the message buffer in the P2000 Remote Message Server may not be sufficient to buffer all messages generated by the local system.

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.

CENTRAL SITE SETTINGS

Use the following table for reference during system configuration.

Table 1-1: Central Site Settings

Item Factory Settings Customer Settings

P2000 Server name1,2 CENTRAL

Windows account name3 psqlserver

Windows password Master1

SQL server name1 CENTRAL

SQL administrator account3 sa

1-5


REGIONAL SITE SETTINGS

Use the following tables for reference during system configuration.

SQL administrator account password Master1

SQL “built-in” administrator account BUILTIN\Administrators

Replication Set Identity Range4 10,000,000 to 19,999,999

1. The name must be unique within the Enterprise system.2. If you are using a custom database instance, use the format: “database_server\named_instance” for the

P2000 database.3. Custom settings may affect the setup of your server. We recommend that you use the factory settings or

contact Technical Support for assistance.4. Each ID range should be unique within the Enterprise system and cannot be re-used. If you need to reassign

the server’s ID range, use a new range.

Table 1-2: Regional Site Settings


P2000 Server name1,2

1. The name must be unique within the Enterprise system.2. If you are using a custom database instance, use the format: “database_server\named_instance” for the

P2000 database.

ORANGE

Windows account name3

(the same as for the central server)

3. Custom settings may affect the setup of your server. We recommend that you use the factory settings orcontact Technical Support for assistance.

psqlserver

Windows password(the same as for the central server)

Master1

SQL server name1 ORANGE

SQL administrator account(the same as for the central server)3

sa

SQL administrator account password(the same as for the central server)

Master1

SQL “built-in” administrator account(the same as for the central server)

BUILTIN\Administrators

Replication Set Identity Range4

4. Each ID range should be unique within the Enterprise system and cannot be re-used. If you need to reas-sign the server’s ID range, use a new range.

20,000,000 to 29,999,999

Table 1-1: Central Site Settings


1-6


BASIC SQL PROCEDURES

This section describes basic procedures such as opening the Microsoft SQL Server Management Studio and executing scripts. These steps are frequently required during the configuration of the regional and central server and are not repeated in detail each time. You can use the procedures in this section for reference.

Procedures and windows depicted in this section may vary slightly depending on the version of SQL Server. However, you can follow the general outline.

The following procedures were performed on SQL Server 2008 R2.

To start Microsoft SQL Server Management Studio:

1. Log on as the system administrator.

2. Go to Start > Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio.

3. In the Connect to Server window, select the server and click Connect.

NOTE: If you are using a custom database instance, enter Server name in the format: “database_server\named_instance.”

4. The SQL Server Management Studio opens.

1-7


To switch between Registered Servers and Object Explorer views:

1. In the SQL Server Management Studio, click the Registered Servers or Object Explorer tab to select required view.

To execute a script:

1. In the SQL Server Management Studio, go to File > Open > File and browse for the script. Unless noted otherwise, the scripts are in the following directory:

C:\Program Files\Johnson Controls\P2000\sql

2. Select the script and click Open.

3. A script opens in the right window pane.

Registered Server and Object Explorer view tabs

1-8


In the example below, the Create sp_Pub_XXX_2005.sql script is selected for execution on the CENTRAL server.

4. When you need to edit the script, follow the instructions provided.

5. Verify that the right database is selected.

The script (may require manual edits)

Selected database

1-9


6. Click the Parse Query button to check the integrity of the script.

7. Wait for the text “Command(s) completed successfully” to appear in the lower window pane under Messages.

8. Click the Execute button.

9. Verify that the following message appears at the bottom of the window: “Query executed successfully.”

Click to parse query

Click to execute query

1-10


10. Close the query window by clicking the X button in the top right corner.

11. If you receive a message asking whether to save changes to the query, click No.

To start SQL Server Configuration Manager:

1. Go to Start > Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager.

2. The SQL Server Configuration Manager window opens.

To manage SQL Server services:

1. Go to Start > Programs > Administrative Tools > Services.

2. In the Services window, you can verify service status, view or change settings, and control service activity.

3. Close the Services window.

Click to close query

1-11


1-12

Enterprise Configuration Configuring P2000 Central Server24-10685-68 Rev. B

2. CONFIGURING P2000 CENTRAL SERVER

To configure a computer as a central server in the P2000 Enterprise system, you must start with a clean P2000 installation. The P2000 Enterprise Configuration cannot be set up properly through an upgrade from earlier versions of P2000 software.

Before you follow the procedures in this chapter:

• Install the P2000 prerequisites and software

• Back up the databases


CREATING WINDOWS LOGIN ACCOUNT FOR SQL SERVER

During replication, SQL Server and SQL Server Agent cannot run as local system, but require a separate account on all participating servers. In this example, the user name for this account is “psqlserver.”

On every Enterprise server, central or regional, you need to create a Windows account dedicated to SQL components. The account user name and password for this account must be the same across the system.

You also need to create a “built-in” SQL administrator account.

See the Central Site Settings table for reference.

• We recommend that you disable password expiration.

• The account should be a member of Users (Domain Users when applicable) and Administrators.

The steps for creating and configuring the new account vary depending on whether or not the P2000 server is on the domain.

If your P2000 server is not on the domain, follow the steps below. Otherwise, go to page 2-6.

2-1


To create a local “psqlserver” user account (no domain):

1. Go to Start > Administrative Tools > Computer Management (this path may vary depending on your operating system).

2. In the Computer Management window, go to Computer Management (Local) > System Tools > Local Users and Groups, right-click Users, and select New User...

3. In the New User window, make the following selections, click Create, and close the window:

Field Value

User name psqlserver

Full name Any (for example, “SQL Server Service”)

Description Any (for example, “P2000 SQL server user account”)

Password Master 1

Confirm Password Master 1

User must change password at next logon Clear

User cannot change password Select

Password never expires Select

2-2


4. In the right pane of the Computer Management window, double-click psqlserver.

5. In the Properties window, on the Member Of tab, click Add...

6. In the Select Groups window, click the Advanced…

7. In the expanded window, click Find Now.

8. In the search results, double-click Administrators, and click OK.

9. In the Properties window, under Member Of tab verify that psqlserver is now a member of Administrators and Users; click OK.

10. Close the Computer Management window.

To create “BUILTIN\Administrators” user account:

1. Open the Microsoft SQL Server Management Studio.

2. Expand the entry for the server and the Security folder.

3. Right-click Logins and select New Login.

In the Login - New window, create an account with the following settings (if not specified below, leave the default value). Do not close this window yet.

Field Value

Login name BUILTIN\Administrators

Default database master

2-3


4. In the left window pane, click Server Roles.

In addition to public check box, which is selected by default, select sysadmin.

2-4


5. In the left window pane, click User Mapping. Make the following selections and click OK.

6. Exit SQL Server Management Studio.

NOTE: From now on, use the “psqlserver” account every time you log on to establish or configure the Enterprise system.

Go to “Editing “sa” Login Properties” on page 2-8.

Field Value

Users mapped to this login Select BadgeImages and Pegasys

Database role membership for: BadgeImages Select db_owner and public

Database role membership for: Pegasys Select db_owner and public

2-5


The following procedure should only be performed on servers on the domain. We recommend use of local accounts so that the P2000 service does not depend on the domain.

To create a domain “psqlserver” user account:

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 (this path may vary depending on your operating system).

3. In the Active Directory Users and Computers window, under the icon for the domain, right-click Users, and go to New > User.

4. In the New Object-User window, enter the following information, and click Next.

Field Value

First name SQL

Last name Server

User logon name psqlserver (@domain_name.com)

2-6


5. In the New Object - User window, make the following selections, and Next.

6. Verify the settings and click Finish.

7. In the Active Directory Users and Computers window, double-click Users.

8. In the right window panel, double-click SQL Server.

9. In the SQL Server Properties window, on the Member Of tab, click Add...

10. In the Select Groups window, click Advanced…


Field Value

Password Master 1

Confirm Password Master 1

User must change password at next logon Clear

User cannot change password Select

Password never expires Select

Account is disabled Clear

2-7



13. In the SQL Server Properties window, under the Member Of tab, verify that the SQL Server is now a member of Administrators and Domain Users.

14. Click OK to close the SQL Service Properties window.

15. Close the Active Directory Users and Computers window.

From now on, use the “psqlserver” account every time you log on to establish or configure the Enterprise system.

EDITING “SA” LOGIN PROPERTIES

The number of servers is limited by the SQL Server license.

The “sa” login is a SQL Server login that is a member of the “sysadmin” fixed server role. This account cannot be deleted. For Enterprise configuration purposes you must configure this account to not enforce password policy.

To disable password enforcement for the “sa” account:

1. In the SQL Server Management Studio window, click the Object Explorer view tab and expand the navigation tree for the central server. Under Security > Logins, double-click the sa item.

2. In the Login Properties - sa window, clear Enforce password policy and click OK.

Clear the Enforce password policy

2-8


3. Close the window.

CHANGING THE LOGIN ACCOUNT FOR SQL SERVICES

The SQL Server Agent (MSSQLSERVER) account and the SQL Server (MSSQLSERVER) account must be configured as follows:

• Use “psqlserver” account instead of the local account

• Use Automatic startup mode

After configuring MSSQLSERVER, start up the service.

NOTE: “MSSQLSERVER” is the default database instance name. If you are using a custom database instance, use the name of that instance.

To modify the SQL Server Agent (MSSQLSERVER) service:

1. Go to Start > Programs > Administrative Tools > Services.

2. In the Services window, right-click SQL Server Agent (MSSQLSERVER and select Properties.

3. In the Properties window, on the Log On tab:

• Select This account and browse for the “psqlserver” account.

• Specify and confirm the password (Master1).

• Click OK.

4. Verify that Automatic startup mode is selected.

5. Restart the service.

The next procedure is very similar, but this time you will modify the SQL Server (MSSQLSERVER) account.

To modify the SQL Server (MSSQLSERVER) account:

1. In the Services window, right-click SQL Server (MSSQLSERVER) and select Properties.

2. In the Properties window, on the Log On tab:

• Select This account and browse for the “psqlserver” account.

2-9


• Specify and confirm password (Master1).

• Click OK.

3. Verify that Automatic startup mode is selected.

4. Restart the service.

CREATING SHARED DIRECTORIES

The REPLDATA folder will be used to store the snapshot, and will be available to all SQL Servers in the Enterprise system.

Establish a shared REPLDATA directory with Full Control rights assigned to Administrator.

(CENTRAL SERVER) To establish a shared directory:

1. In the Windows Explorer, go to:

C:\Program Files\Microsoft SQL Server\ MSSQL.10.MSSQLSERVER\MSSQL

2. Right-click the repldata folder and select Share with > Advanced sharing...

3. In the Properties window, under Sharing tab, click Advanced Sharing...

4. In the Advanced Sharing window, select Share this folder and click Permissions.

5. In the Permissions window, click Add...

6. In the Select Users or Groups window, click Advanced...



9. In the Select Users or Groups window, click OK.

10. In the Permissions window, verify that Administrators is highlighted in the upper window pane. In the lower window pane select Full Control in the Allow column. Click OK.

2-10


11. In the Properties window for the server, click OK.

CONFIGURING PUBLISHER AND DISTRIBUTOR

The Publisher and distributor are configured on a central server.

(CENTRAL SERVER) To configure publication and distribution:

1. Start SQL Server Management Studio, and connect to the central server using the psqlserver account.

2. Under the central server’s icon, right-click the Replication folder and select Configure Distribution...

3. The Configure Distribution Wizard starts. click Next.

Central server

2-11


4. Verify that the central server is selected as Distributor, and click Next.

5. In the Snapshot Folder window, enter the location of the “repldata” folder to be used for snapshots. Use the following format, where CENTRAL is the name of the central server:

\\CENTRAL\REPLDATA

Click Next.

6. Accept the default settings by clicking Next.

2-12


NOTE: “MSSQLSERVER” is the default database instance name. If you are using a custom database instance, select a folder corresponding to that instance.

7. In the Publishers window, verify that the central server is selected in the Publisher column, and click Next.

8. In the Wizard Actions window, verify that Configure distribution is selected, and click Next.

9. In Complete the Wizard window, view the settings and click Finish.

2-13


10. Verify that the configuration has been successful and no errors appear, and click Close.

11. Keep the Microsoft SQL Server Management Studio window open.

(CENTRAL SERVER) To configure Publisher properties:

1. In the Microsoft SQL Server Management Studio window, right-click Replication and select Publisher Properties.

2. In the left window pane of the Publisher Properties window, click Publication Databases.

3. In the right pane of the Publisher Properties window, select the BadgeImages and Pegasys check boxes in the Merge column. Click OK.

Keep the Microsoft SQL Server Management Studio window open.

(CENTRAL SERVER) To generate P2000 stored procedures for Publisher/Distributor:

1. In the Microsoft SQL Server Management Studio window, go toFile > Open > File.

2. Browse for the Create sp_Pub_XXX_2005.sql file located in the following directory:


Select it and click Open.

NOTE: On 64-bit Microsoft Windows operating systems supported by P2000, the Johnson Controls directory is located in Program Files (x86).

3. Right-click the central server and click Connect.

4. Parse the query to check the integrity of the script, and then and execute the query.

5. Close the Microsoft SQL Server Management Studio window.

2-14


ESTABLISHING AN ENTERPRISE SYSTEM

To establish an enterprise configuration, Enterprise Time Zones and Access Groups must be defined. For instructions on defining Time Zones and Access Groups, refer to the P2000 Software User Manual. You can define them now or later.

On the central server, the local site is automatically defined as the Enterprise Site. However, the enterprise parameters must be set manually, as described in the procedure below.

(CENTRAL SERVER) To identify the P2000 server as the Enterprise site:

1. Log on to P2000.

2. From the main menu, select Config > System.

3. In the System Configuration window, right-click Enterprise Parameters, and select Edit.

4. In the Enterprise Parameters Edit window, from the Enterprise Site drop-down list, select the name of this site as defined during the P2000 software installation. Click OK.

5. The site is now listed in the System Configuration window under Enterprise Parameters>Enterprise Sites. Keep the System Configuration window open.

2-15


POPULATING THE ENTERPRISE SETTINGS

Before any subscriptions can be created, the initial site tables must be populated. This is done on the Central Site in the Enterprise Site Edit screen of P2000.

CENTRAL SERVER: To add regional sites:

Add the sites that have already been established. More sites can be added at a later time.

1. In the System Configuration window for P2000, under Enterprise Parameters, right-click the Enterprise Sites icon and select Add.

2. The Enterprise Site Edit window opens where you can add a new site. Each site added so far is listed.

2-16


3. Specify the Name and Database Server of the regional site.

For Subscription Sites, select the sites for which you want the data to be available on this regional server. Selecting All sites subscribes this server to data from the entire Enterprise system. Click OK.

4. Repeat steps 1 through 3 for each regional site.

5. Verify that the added sites appear in the System Configuration window. Close this window.

2-17


SETTING UP P2000 PUBLICATIONS

The SQL Server Agent (MSSQLSERVER) must be running.

(CENTRAL SERVER) To create a publication:

1. Stop all P2000 Services on the central site and quit their monitoring.

2. In SQL Server Management Studio, browse for the Create All Publications.sql file located in the following directory:

C:\Program Files (x86)\Johnson Controls\P2000\sql

Select it and click Open.

3. Remove the entire “EXEC” statement line for all such publications that you do not want to create. See P2000 Publications on page 1-4 for more information on how to decide which publications to create.


5. We recommend that you scroll review error messages on the Messages tab. Resolve any reported problems.

6. Exit without saving the script file. Keep the Microsoft SQL Server Management Studio window open.

GENERATING SNAPSHOTS

Once the publications are created, you need to generate snapshots for each publication. Snapshots contain initial data from the Publisher, schema (database structure) information, and initialization parameters for tables with identity columns.

NOTE: We recommend that you run each snapshot separately to avoid deadlocks and corruption of control tables.

(CENTRAL SERVER) To run a snapshot:

1. In the Microsoft SQL Server Management Studio window, expand the navigation tree, and go to Replication > Local Publications folder.

2-18


2. Right-click a publication, and select View Snapshot Agent Status.

3. In View Snapshot Agent Status window, click Start.

4. Click Close.

5. The status will change from “The agent has never been run” to “Starting Agent” and to “100%.”

Wait for the snapshot to complete (as indicated by the “100%” status). The process may take several minutes.

6. For each publication, run the associated snapshot agent as described in steps 2 to 5. Run the snapshots one at a time.

Completed snapshot

2-19


The number of snapshots depends on the number of previously established publications. Some snapshots may take several minutes to complete.

7. When all snapshots are completed, we recommend that you back up the databases.

SETTING UP THE REPLICATION IDENTITY RANGE

An identity range is set up by executing a script. See To execute a script: on page 1-8 for detailed instructions.

See the Central Site Settings table for reference.

To set up an identity range:

1. In the Microsoft SQL Server Management Studio window:

• Right-click the central server and click Connect.

• Select Pegasys from the drop-down list.

2. In the Microsoft SQL Server Management Studio window, open the following script:

P2000EntityConfig_spP2000ReplicationSetAllTablesIDRange.sql.


Select Pegasys database

2-20


4. We recommend that you review error messages on the Messages tab. Resolve any reported problems.

To specify an identity range:

1. In Microsoft SQL Server Management Studio, click the New Query button.

2. Verify that the Pegasys database is selected.

3. Type the following command, where XX is the beginning of the ID range, and YY is the end of the ID range”

exec dbo.spP2000ReplicationSetAllTablesIDRange XX, YY

See Table 1-1 and Table 1-2 for reference.


5. We recommend that you scroll review error messages on the Messages tab. Resolve any reported problems.


Congratulations! You have successfully defined the required publications for your P2000 Enterprise Solution.

2-21


2-22

Enterprise Configuration Merging Data Between Sites24-10685-68 Rev. B

3. MERGING DATA BETWEEN SITES

To establish the subscription of a P2000 regional server to a P2000 central server, you must back up the data currently stored in the P2000 regional server databases and incorporate it into the P2000 central server.

To synchronize the central and regional servers, all data in the regional server will be deleted and partially re-initialized with the contents of the central server.

You will also restore the database backup from regional server as the PegasysBackup database on both the regional and the central servers. This way, you can run standard P2000 reports against this database if needed.

The data recorded in tables associated with the following publications will not be maintained:

• FDA

• BadgeImages FDA

• Xaction

• Audit

• Alarms

RULES FOR DATA MERGING

When merging the data from the P2000 regional server into the P2000 central server, the following rules are applied:

• Records that already exist in the P2000 central server will not be modified, as they are currently active within the existing P2000 Enterprise.

• Only records that are explicitly designated to be merged will be merged into the central database.

• If a badge number is already assigned to another cardholder), the conflict is resolved by assuming that the P2000 central server has the correct information.

Because of the above rules, we recommend that you check the cardholder/badge security settings before the subscription is established, or before a new P2000 regional server becomes the active P2000 server for the regional system.

In addition, you must re-enter any configuration changes that were made after backing up the P2000 regional server and completing the data subscription.

3-1


MERGING DATA BETWEEN SITES

This section outlines the steps required to merge data between the P2000 regional server and the P2000 central server. It requires knowledge of basic procedures as described in the P2000 Software User Manual and P2000 Software Installation. Details of these procedures are not repeated in this section.

There are two scenarios for establishing a live P2000 site version 3.12 as a part of an Enterprise system. In the first scenario, additional server hardware takes on the P2000 server functions during the transition. In the second scenario, no additional hardware is necessary.

Refer to the following sections:

• Live System Upgrade (Additional Hardware) on page 3-3

• Live System Upgrade (No Additional Hardware) on page 3-10

When installing a clean site, follow the instructions for Live System Upgrade (No Additional Hardware) on page 3-10.

3-2


Live System Upgrade (Additional Hardware)

The starting point is a P2000 system version 3.12. This system will become a regional site in the P2000 Enterprise Configuration and will reside on new hardware.

Figure 3-1: Live System Upgrade: Starting Point

(REGIONAL SERVER) To establish a site as part of Enterprise Configuration:

1. On the additional server hardware, install P2000 version 3.12.

NOTE: The new server must have the same computer name, P2000 server name, and P2000 site name as the old system.

2. Register the P2000 software and the options used by your system, including the Enterprise Configuration option.

P2000 Serverversion 3.12

Hub

Panels and P2000 Workstationsversion 3.12

WAN

CENTRAL SITE

P2000 Server version 3.12Enterprise Configuration

3-3


Figure 3-2: Live System Upgrade: Installing Additional Server


Hub


WAN

CENTRAL SITE


Additional P2000 Server version 3.12, with the Enterprise Configuration advanced feature

3-4


3. Back up the regional server’s Pegasys and BadgeImages databases using the P2000 Backup utility (append or overwrite Backup Data and Backup Images).

4. Back up the Badge Layouts and application files located in the following directories, including all subdirectories:

N:\Bmaster

C:\Program Files (x86)\Johnson Controls\P2000\Badgemaster

Older systems may use the following directory:

C:\Program Files\Johnson Controls\CARDKEY P2000\ Badgemaster

5. On the newly established P2000 regional server, restore the Pegasys and BadgeImages databases as archives using the P2000 Backup utility. During the process, in the P2000 Backup window, select Restore to archive, but clear Convert to Current Version After Restore.

6. On the newly established P2000 regional server, restore the Badge Layout and application files as archives.

IMPORTANT: Do not restart the server until instructed to do so on page 3-10.

7. Establish subscriptions between the newly installed P2000 server and the central site. For detailed steps, refer to Chapter 4: Configuring P2000 Regional Server.

The panels and workstations are still communicating with the previous P2000 server.

3-5


Figure 3-3: Live System Upgrade: Configuring Additional Server

8. Suspend subscriptions from this region.

9. Verify that the SQL Server and SQL Server Agent services are running.


Hub


WAN

CENTRAL SITE


Est

ab

lish

sub

scri

ptio

n

Additional P2000 Server version 3.12, becomes a regional server within the Enterprise Configuration

3-6


10. In SQL Server Management Studio, run the P2000_mergedata script to merge the archived databases. The script is located in the following directory:

C:\Program Files (x86)\Johnson Controls\P2000\sql

Figure 3-4: Live System Upgrade: Restoring Databases


Hub


WAN

CENTRAL SITE


Est

ab

lish

su

bsc

rip

tion

Archived database

“Empty” database

Me

rge

REGIONAL SITE


3-7


11. Verify database integrity following these steps:

• In the SQL Server Management Studio window, click the New Query button.

• Type the following commands:

use pegasysdbcc checkdbgouse badgeimagesdbcc checkdbgo

• Parse and execute the script.

• Scroll down in the lower window pane and find the line:

“CHECKDB found 0 allocation errors and 0 consistency errors in database ‘Pegasys’.”

• Scroll down further and find the line:

“CHECKDB found 0 allocation errors and 0 consistency errors in database ‘BadgeImages’.”

12. On systems with FDA tracking option is enabled, re-establish FDA signatures using the P2000 Database Maintenance utility. To do so, run Calculate Digital Signature and then Validate Digital Signature for all signatures.

13. Activate each replication job and manually start the replication cycle (one at a time).

14. Manually add modifications that were made to the old database since the backup time.

15. Verify that the P2000 regional server is fully operational.

To switch the panels and workstations to communicate with the new regional server:

1. Configure the P2000 workstations to communicate with the new server’s computer name.

2. Configure the panels to communicate with the new server’s IP address.

3-8


3. Perform a download to all panels.

Figure 3-5: Live System Upgrade: Connecting Panels and P2000 Workstations


Hub


WAN

CENTRAL SITE


Est

ab

lish

sub

scri

ptio

n

REGIONAL SITE


3-9


(REGIONAL SERVER) To complete the configuration:

1. Restart P2000 regional server.

2. Launch P2000 on the P2000 regional server.

3. Back up the P2000 regional server database, overwriting the initial backup.

4. Verify the data on the P2000 regional server.

5. In System Configuration, define the P2000 regional site as an Enterprise Site.


7. In P2000 Site Parameters, configure the smart download delay for all sites as two times longer than replication time, plus one minute.

Live System Upgrade (No Additional Hardware)

The P2000 prerequisites and software must be installed before proceeding. During the following procedures, you will need information about the P2000 central server configuration.

(REGIONAL SERVER) To upgrade a site to become a part of an Enterprise Configuration:

1. Back up the regional server’s Pegasys and BadgeImages databases using the P2000 Backup utility (append or overwrite Backup Data and Backup Images).

2. Make note of the P2000 Installation Key and Registration/Option Keys.

3. Restore the Pegasys and BadgeImages databases as archives using the P2000 Backup utility. During the process, in the P2000 Backup window, select Restore to archive, but clear Convert to Current Version After Restore.

3-10


4. Back up the Badge Layouts and application files located in the following directories, including all subdirectories:

N:\Bmaster

C:\Program Files (x86)\Johnson Controls\P2000\Badgemaster

Older systems may use the following directory:

C:\Program Files\Johnson Controls\CARDKEY P2000\ Badgemaster

NOTE: If this is a clean installation, skip steps 5-7.

5. Using the Add/Remove programs utility, uninstall the P2000 software, but do not uninstall the P2000 database, badge layout files, or user groups.

6. Manually remove the Pegasys and BadgeImages databases as follows. Do not remove the archive.

• Start SQL Server Management Studio.

• In the left window pane, under the icon for the regional (local) server, click the Databases folder. A list of available databases appears.

• In the right window pane, right-click the Pegasys database icon and select Delete.

3-11


• In the Delete Object window, click OK.

• In the Microsoft SQL Server Management Studio window, right-click the BadgeImages database icon and select Delete.

• In the Delete Object window, click OK.

• Close the Microsoft SQL Server Management Studio window.

7. Perform a clean installation of the P2000 version 3.12 software.

8. Register the P2000 software and the options used by your system, including the Enterprise Configuration option.

9. After the system restarts, stop the P2000 services, applications, and service monitoring.

10. Verify that the SQL Server and SQL Server Agent services are running.

IMPORTANT: Do not restart the server.

11. Establish subscriptions between the newly installed P2000 server and the central site. For detailed steps, refer to Chapter 4: Configuring P2000 Regional Server.

12. Suspend replication jobs (disable subscription jobs).

13. In SQL Server Management Studio, run the P2000_mergedata script to merge the archived databases. The script is located in the following directory:

14. Verify database integrity following these steps:

• In the SQL Server Management Studio window, click the New Query button.

• Type the following commands:

use pegasysdbcc checkdbgouse badgeimagesdbcc checkdbgo

3-12


• Parse and execute the script.

• Scroll down in the lower window pane and find the line:

“CHECKDB found 0 allocation errors and 0 consistency errors in database ‘Pegasys’.”

• Scroll down further and find the line:

“CHECKDB found 0 allocation errors and 0 consistency errors in database ‘BadgeImages’.”

15. On systems with FDA tracking option is enabled, re-establish FDA signatures using the P2000 Database Maintenance utility. To do so, run Calculate Digital Signature and then Validate Digital Signature for all signatures.

16. Reactivate replication jobs and manually start replication cycles one at a time.

(REGIONAL SERVER) To complete the configuration:

1. Restart P2000 regional server.

2. Launch P2000 on the P2000 regional server.

3. Back up the P2000 regional server database, overwriting the initial backup.

4. Verify the data on the P2000 regional server.

5. In System Configuration, define the P2000 regional site as an Enterprise Site.


7. In P2000 Site Parameters, configure the smart download delay for all sites as two times longer than replication time, plus one minute.

3-13


3-14

Enterprise Configuration Configuring P2000 Regional Server24-10685-68 Rev. B

4. CONFIGURING P2000 REGIONAL SERVER

Follow instructions in this chapter to establish a P2000 regional server as a Database Subscriber.

Perform procedures described here only after you have been directed to do so from Chapter 3: Merging Data Between Sites.

NOTE: Procedures and screens may vary slightly depending on the version of SQL Server. However, you can still follow the general outline.


PREPARING FOR CONFIGURATION

Begin by creating a new Windows account with administrator rights on the P2000 regional server, using the same Windows account name and password as used on the P2000 central server (see Table 1-1 for reference). You will:

• Create a “psqlserver” Windows account with administrator rights

• Create a “BUILTIN\Administrators” account on the SQL server and assign it server roles and user mappings

Afterwards, always log on to the server using the “psqlserver” account.

The procedures for the two tasks listed above are the same as for the central server. For detailed instructions, see Creating Windows Login Account for SQL Server on page 2-1 (until you get to section Editing “sa” Login Properties on page 2-8). After completing the procedures, continue with Changing the Login Account for SQL Services below.

Go to “Editing “sa” Login Properties” on page 4-2.

4-1


EDITING “SA” LOGIN PROPERTIES

The number of servers is limited by the SQL Server license.

Refer to Editing “sa” Login Properties on page 2-8 for instructions.

CHANGING THE LOGIN ACCOUNT FOR SQL SERVICES

Refer to Changing the Login Account for SQL Services on page 2-9 for instructions.

ESTABLISHING SUBSCRIPTIONS

From each regional site, establish the subscriptions to the central server’s publications. Establish only one Subscriber at a time.

IMPORTANT: Stop all P2000 Services on the regional site and quit their monitoring.

(REGIONAL SERVER) To clean the database tables:

1. Start SQL Server Management Studio.

2. In the Connect to Server window, select the regional server’s Windows authentication. Click Connect.

3. In the SQL Server Management Studio window, go to File > Open > File.

4. Browse for and open the Clean (publication name).sql file located in the following directory:


5. Parse and execute the query.

6. Repeat steps 3 to 5 for all Clean (publication name).sql files.

7. Keep the Microsoft SQL Server Management Studio window open.

4-2


(REGIONAL SERVER) To establish a subscription for a publication:

1. In the Microsoft SQL Server Management Studio window, expand the entry for the regional server. Under Replication, right-click the Local Subscriptions folder and select New Subscriptions...

2. The New Subscription Wizard opens. Click Next.

3. In the Publisher drop-down list, select <Find SQL Server Publisher...>.

4-3


4. Select the central server and click Connect.

5. Expand the navigation tree to display all available subscriptions. The list of available subscriptions depends on the number of previously established publications.

Subscriptions should be established in the following order:

• Enterprise

• Configuration

• FDA

• BadgeImages

• BadgeImages FDA

• Audit

• XAction

• Alarms

Select a subscription and click Next.

6. Verify Run each agent at its Subscriber (pull subscriptions) is selected. Click Next.

4-4


7. Verify that the regional server is selected as subscriber; click Next.

NOTE: For BagdeImages and BagdeImages FDA subscriptions, the “BadgeImages” database should be selected.

4-5


8. Click the button indicated below to open the Merge Agent Security window.

Click to open Merge Agent Security window

4-6


9. In the Merge Agent Security window, select Run Under SQL Server Agent service account (This is not recommended security best practice), and click OK.

4-7


10. Click Next.

11. In the Agent Schedule drop-down menu, select <Define schedule...>.

4-8


12. You can adjust subscription’s schedule to fit the needs of the Enterprise system. In the New Job Schedule window, set up the schedule of a subscription, and click OK. (Each subscription’s schedule must be adjusted separately). See Table 4-1 for recommendations.

Table 4-1: Recommended Replication Schedule

Publication Recommended Replication

Enterprise, Configuration, BadgeImages

Every five minutes

FDA, Alarms, Audit, BadgeImages FDA, XAction

Every hour (for instant availability in Alarm Monitors, use Remote Message Service rather than more frequent replication).

4-9


Staggered the replication cycle to ensure that only one subscriber attempts to re-synchronize with the central server at a time.

We recommend that you use prime numbers for the time between replication cycles (for example: 5 minutes at Site 1, 7 minutes at Site 2, 11 minutes at site 3, and so on).

13. View the new schedule settings, and click Next.

4-10


14. Verify that Immediately is selected in the Initialize When drop-down list, and click Next.

15. Set the Subscription Type to Client, and click Next.

4-11


16. Verify that Create the Subscriptions check box is selected, and click Next.

17. Click Finish.

4-12


18. Wait while the subscription is created.

NOTE: Applying a snapshot through a wide area network can take considerable time. SQL Server offers the option to apply the snapshot to a local hard drive. Refer to the SQL Server help for further details about this option.

19. Verify that the subscription was created successfully, and click Close.

20. Repeat steps 1 through 19 for each publication you want to subscribe to.

21. Verify that all subscriptions are successfully established.

Keep the Microsoft SQL Server Management Studio window open.

When the subscriptions are established, the Merge Agent runs the data merge based on the schedule and initialization time configured in this procedure. The following steps let you verify that the merge is complete.

4-13


(REGIONAL SERVER) To verify completion of the Merge Agent activity:

1. In the Microsoft SQL Server Management Studio, in the tree in the left window pane, expand the regional server, expand SQL Server Agent, expand Jobs, and then double-click Job Activity Monitor.

2. In the right window pane, the Agent Job Activity column displays established subscriptions (the list may vary depending on your system). Notice the subscription in progress.

“Executing” status indicates subscription in progress

4-14


3. Wait until all subscriptions are complete, as indicated by the “Succeeded” and “Idle” messages, and close the window.

REPLICATION SET IDENTITY RANGE

(REGIONAL SERVER) To set up an identity range:

1. In the Microsoft SQL Server Management Studio, go to File > Open > File.

2. In the Open File window, navigate to the following directory:


Select and open the file:

P2000EntityConfig_spP2000ReplicationSetAllTablesIDRange.sql

NOTE: On 64-bit Microsoft Windows operating systems supported by P2000, the Johnson Controls directory is located in Program Files (x86).

3. In the Connect to Server window, select the regional server, and click Connect.

NOTE: If you are using a custom database instance, use the format: regional_server\named_instance.

4. In the Microsoft SQL Server Management Studio window, verify that Pegasys is selected in the drop down list.

4-15



6. In the lower window pane, verify that the commands were completed successfully. Resolve any reported problems.

7. Open a new query and type the following commands:

Pegasys must be selected

4-16


exec dbo.spP2000ReplicationSetAllTablesIDRange XX, YY

Where XX is the beginning of the ID range, and YY is the end of the ID range. See Table 1-2 for reference.

8. Verify that Pegasys is selected in the drop-down list.

9. Parse and execute the query.


4-17


4-18

Document Title Publications24-10685-68 Rev. B

A. PUBLICATIONS

The following list identifies publications and their corresponding articles (database tables).

Alarms

alarms_hist

Audit

audit

Configuration

access_group_details

accgroup

accgrpelevator

accgrpterm

accgrptermgrp

acctpl

actioninterlock

alarmcategory

alarmcolors

alarmoptions

alarmresptext

alrminst

applicationpreferences

area_configuration

area_details

area_layout

area_layout_data

assaabloy

assaabloy_badgeformat

autobadge

auto_cardholder_id

auto_cardholder_status

AVChannel

avdrycontact

AVMonitor

AVPreset

A

AVSite

bacnetsource

badge

badgefields

badgeformats

badgelayout

badgemagformula

badgepurpose

badgesetup

badgesite

badgestatus

BadgeStatusSave

cardevent

cardholder

cardholdersite

CCTVAlarm

CCTVAuxiliaryCamera

CCTVAuxiliarySystem

CCTVCamera

CCTVMacros

CCTVMonitor

CCTVPattern

CCTVPreset

CCTVSequence

CCTVServer

CCTVSwitch

CCTVTour

company

counter

counter_p900

dataimport_fields

dataimport_mapping

dept

-1


dnld_req_rule

dnld_req_timed

drycontact_status

elevator

elevatordetails

elevatordetails_mercuty

enable_code

event

event_action

event_action_decode

event_trigger

event_trigger_decode

externalip

facility

facility_hid

facility_group

facilitystatus

fascn_ccc

firealarm_entity

firealarm_status

flag_p900

floorgrp

floorgrpdata

floormask

floormaskdata

floorname

GenericText

HIDAgTzPanelRef

holiday

hoursonsiteterminals

hoursonsitezones

icon_image

icon_image_set

icon_overlay

idbadge

igdata

imagerecallfilter

input

input_ck

A

input_hid

input_p900

input_s321ip

input_status

Input2CamInfo

inputgrp

intercom_exchange

intercom_station

intercom_station_status

IntegrationComponent

IntegrationComponent_assaabloy_dsr

IntegrationComponent_intercom

IntegrationComponentStatus

intrusion_entity

intrusion_entity_mercury

intrusion_status

journal

journal_attachments

loopconfig

map

mapimage

messagefilter

mifareencode

mfg_item

mseagraphic

msgfiltergroup

koneip_cntrl_defn

koneip_cntrl_grp

koneip_cntrl_grp_floor

mercuryinput

mercuryoutput

mercury_cardformat

mercury_action

mercury_connections

mercury_facility

mercury_input_calibration

mercury_procedure

mercury_trigger

MusterDefinition

-2


MusterPrinters

MusterReaders

ogdata

output

output_ck

output_p900

output_s321ip

output_status

outputgrp

otis_compass_mode

otis_compass_status

P900sysparameters

panel

panel_ck

panel_hid

panel_mercury

panel_osi

panel_p900

panel_s321ip

panelholiday

panelstatus

paneltz

partition

pin_number

portconfig

privgrp

privgrpdata

p2kadxmap

reason

redundancy_cfg

redundancy_isolation_ip

remoteserver

report

reportdata

requestapprovers

requestapprovers_details

requestconfig

requiredfields

SecLevelRanges

A

service_stat

siadevice

site

sitepartmap

softalarm

softwareupdate

station

station_stat

svr_startup_cnfg

term_pin_number

termgrp

termgrpterm

terminal

terminal_assaabloy

terminal_ck

terminal_hid

terminal_isonas

terminal_mercury

terminal_osi

terminal_p900

terminal_s321ip

terminalstatus

timezone

tour_configuration

tour_note

tour_station_configuration

trigger_event_p900

trigger_link_p900

udfboolean

udfdate

udfgen

udfnum

udfselection

udfselectionchoices

udftext

uniquebadge_id

userpartition

userprivgrp

userremotepartitions

-3


users

usersite

user_concealed_udf

webaccessconfig

webaccessctrl

Enterprise

enterprise_parameters

ent_site

esp_parameters

FDA

access_group_details_save

accgroup_save

accgrpelevator_save

accgrpterm_save

accgrptermgrp_save

acctpl_save

actioninterlock_save

alarmcolors_save

alarmfw_save

alarmresptext_save

alrminst_save

area_configuration_save

area_details_save

area_layout_data_save

area_layout_save

assaabloy_save

auto_cardholder_id_save

AVChannel_save

avdrycontact_save

AVMonitor_save

AVPreset_save

AVSite_save

badge_save

badgefields_save

badgeformats_save

badgelayout_save

badgemagformula_save

A

badgepurpose_save

badgesetup_save

badgesite_save

cardevent_save

cardholder_save

cardholdersite_save

CCTVAlarm_save

CCTVAuxiliaryCamera_save

CCTVAuxiliarySystem_save

CCTVCamera_save

CCTVMacros_save

CCTVMonitor_save

CCTVPattern_save

CCTVPreset_save

CCTVSequence_save

CCTVServer_save

CCTVSwitch_save

CCTVTour_save

company_save

counter_p900_save

counter_save

dataimport_fields_save

dataimport_mapping_save

dept_save

elevatordetails_mercury_save

elevatordetails_save

enable_code_save

ent_site_save

enterprise_parameters_save

event_action_save

event_save

event_trigger_save

externalip_save

facility_save

facility_group_save

facility_hid_save

fascn_ccc_save

firealarm_entity_save

flag_p900_save

-4


floorgrp_save

floorgrpdata_save

floormask_save

floormaskdata_save

floorname_save

GenericText_save

holiday_save

hoursonsiteterminals_save

hoursonsitezones_save

icon_image_save

icon_image_set_save

icon_overlay_save

idbadge_save

IDSequences_save

igdata_save

imagerecallfilter_save

input_ck_save

input_hid_save

input_p900_save

input_s321ip_save

input_save

Input2CamInfo_save

inputgrp_save

IntegrationComponent_assaaboy_dsr_save

IntegrationComponent_intercom_save

IntegrationComponent_save

intercom_exchange_save

intercom_station_save

intrusion_entity_mercury_save

intrusion_entity_save

journal_attachments_save

journal_save

koneip_cntrl_defn_save

koneip_cntrl_grp_floor_save

koneip_cntrl_grp_save

localsite_save

loopconfig_save

A

map_save

mapimage_save

mercuryinput_save

mercuryoutput_save

mercury_action_save

mercury_connections_save

mercury_facility_save

mercury_input_calibration_save

mercury_procedure_save

mercury_trigger_save

output_s321ip_save

panel_hid_save

panel_mercury_save

panle_osi_save

panel_s321ip_save

messagefilter_save

mfg_item_save

msgfiltergroup_save

MusterDefinition_save

MusterPrinters_save

MusterReaders_save

ogdata_save

output_ck_save

output_p900_save

output_save

outputgrp_save

otis_composs_mode_save

P900sysparameters_save

panel_ck_save

panel_p900_save

panel_save

panelholiday_save

paneltz_save

partition_save

pin_number_save

portconfig_save

privgrp_save

privgrpdata_save

reason_save

-5


redundancy_cfg_save

redundancy_isolation_ip_save

remoteserver_save

report_save

reportdata_save

requiredfields_save

requestapprovers_ave

requestapprovers_details_save

requestconfig_save

SecLevelRanges_save

siadevice_save

site_save

softalarm_save

softwareupdate_save

station_save

svr_startup_cnfg_save

term_pin_number_save

termgrp_save

termgrpterm_save

terminal_assaabloy_save

terminal_ck_save

terminal_hid_save

terminal_isonas_save

terminal_mercury_save

terminal_p900_save

terminal_s321ip_save

terminal_save

timezone_save

tour_configuration_save

tour_station_configuration_save

trigger_event_p900_save

trigger_link_p900_save

udfboolean_save

udfdate_save

udfgen_save

udfnum_save

udfselection_save

udfselectionchoices_save

udftext_save

A

user_concealed_udf_save

userpartition_save

userprivgrp_save

userremotepartitions_save

users_save

usersite_save

XAction

redn_xaction

request_queue_hist

xaction

BadgeImages

fingerprint

portrait

signature

BadgeImages FDA

fingerprint_save

portrait_save

signature_save

-6

Document Title Important Notes24-10685-68 Rev. B

B. IMPORTANT NOTES

INITIALIZATION

Execution of the snapshot agent places exclusive locks on the target tables and in some of the system tables used to manage the replication process. When multiple snapshots run simultaneously against the same database, a deadlock can cause a snapshot not to generate. Snapshots are configured not to start immediately. Instead, each snapshot agent must be started by an operator.

DEADLOCKS AND RETRIES

When a deadlock occurs, one process or job is cancelled, and all changes are supposed to be rolled back. Frequently, not all the changes are reversed. This problem applies both to the initial snapshot generation and to the Subscriber initialization where the snapshot is applied. However, the Subscriber initialization is far more sensitive and prone to problems. In particular, the Subscriber table holding replication identity ranges and the replication identity constraint on some merged tables are not cleaned up.

IDENTITY COLUMNS

Identity columns are managed by assigning value ranges to each Subscriber. When a value range is used up, a new one is assigned. The available range values available for each article (published table) are kept in the distribution database in the MSrepl_identity_range table on the Publisher. The MSrepl_identity_range table in the subscribing database contains current range assignments for that database.

PRIMARY KEY VIOLATION

The primary key in the MSrepl_identity_range table (in the subscribing database) is an object ID assigned to specific articles. If a process cancels unexpectedly, this table may not be cleared. Subsequent attempts by the merge agent to initialize will generate a Primary Key Violation for this table. In this case, we recommend that you drop the subscription and re-create it.

B-1

Document Title Important Notes24-10685-68 Rev. B

CALLING SP_ADJUSTPUBLISHERIDENTITYRANGE

The replication identity constraint is applied to a subscribing table during merge initialization and whenever a new range has been assigned. Old constraints are not always removed when subscription initialization is canceled and retried. This problem means that multiple, disjointed ranges may be assigned to an identity column in a table. When a table insert is attempted, the user receives a SQL Server message that a range is exhausted, advising they run a sp_adjustpublisheridentityrange procedure on the Publisher. However, running this stored procedure will not help. Either the extra constraints on the table must be removed, or the database must be dropped and re-created.

CONNECTIVITY LOSS

With two Subscribers and multiple panel simulators running, one subscribing machine consistently loses contact with the Publisher. Merge operations fail on the subscribing machine and are not updated on the Publisher’s replication monitor. Attempts to connect to SQL Server with the Enterprise manager and the Query Analyzer fail. However, if you exit the P2000 user interface, connectivity is restored and the merge jobs succeed. You can then run P2000 again.

B-2

We welcome your comments at [email protected].

Security Solutions(805) 522-5555

www.johnsoncontrols.com

P2000 Enterprise Configuration

Documents

Transcript of P2000 Enterprise Configuration