Andover Continuum web.client Planning and Installation Guide for Version 1.92

(1)

Planning and Installation Guide

for Version 1.92

(2)

No part of this publication may be reproduced, read or stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Schneider Electric.

This document is produced in the United States of America. Andover Plain EnglishTM is a trademark of Schneider Electric. Andover InfinetTM is a trademark of Schneider Electric.

All other trademarks are the property of their respective owners. Title: Andover Continuum web.Client Planning and Installation Guide web.Client Version 1.92

Date: December, 2010

Schneider Electric part number: 30-3001-835

The information in this document is furnished for informational purposes only, is subject to change without notice, and should not be construed as a commitment by Schneider Elec-tric. Schneider Electric assumes no liability for any errors or inaccuracies that may appear in this document.

On October 1st, 2009, TAC became the Buildings Business of its parent company Schneider Electric. This document reflects the visual identity of Schneider Electric. However, there remain references to TAC as a corporate brand throughout the Andover Continuum soft-ware. In those instances, the documentation text still refers to TAC — only to portray the

(3)

December, 2010

Planning and Installation Guide

30-3001-835 Version 1.92

(4)

(5)

About this Manual ...

9

What’s in this Manual ... 9

Revision History ... 10

Chapter 1 Introduction to web.Client ...

13

Overview ... 14

web.Client Overview ... 14

web.Client User Documentation ... 15

A Typical System before web.Client ... 16

A Typical System Implementing web.Client ... 17

Differences between web.Client and CyberStation ... 19

Chapter 2 System and Pre-Installation Requirements ...

21

web.Client Setup Configurations ... 22

Hardware and Software Requirements for LAN System ... 23

Hardware and Software Requirements for a Standalone System 27 Pre-Installation Microsoft Tasks ... 31

Installing System Software ... 32

.NET Framework 2.0 ... 32

Installing IIS on Windows Server 2008 ... 32

Installing IIS on Windows XP and Windows Server 2003 43 Registering File Extensions for Windows Server 2003 .... 45

Configuring IIS for Windows Vista ... 45

Registering File Extensions for Windows Server 2008 and Windows Vista ... 46

(6)

Changing the Default TCP Web Port Number for the

IIS PC ... 48

Disabling WinSock Proxy Client on Standalone System . 48 Ensuring a Domain Membership Is Selected ... 49

Avoiding Invalid Characters in a Server Name ... 49

Disabling Windows Firewall ... 49

Disabling Automatic Windows Updates ... 50

Chapter 3 Installing and Configuring web.Client on the IIS PC ...

51

Overview ... 52

Installing web.Client on the IIS PC ... 53

Creating and Initializing the Database on a Standalone IIS PC ... 59

Adding web.Client to an Existing Standalone Database . 66 Initializing the Database on a LAN IIS PC ... 68

web.Client Video System Upgrades ... 71

Routing Alarms to the IIS PC on a LAN System ... 73

Configuring Access Permissions for web.Client Users .... 74

Configuring Your Video Servers ... 75

Configuring Graphics Folders for web.Client: Windows XP and Windows Server 2003 ... 76

Specifying a Local Folder as a Web Address ... 76

Specifying a Network Folder as a Web Address ... 77

Verifying Anonymous Access to Virtual Folders ... 80

Configuring Graphics Folders for web.Client: Windows Vista . 81 Setting Up an Application for Graphics on Windows Vista 81 Giving Everyone Access to Graphics Files on Windows Vista ... 82

Establishing Pinpoint Folders ... 84

(7)

Changing the Default TCP Port Number ... 98

Chapter 4 Testing and Installing web.Client on a Client PC ...

99

Overview ... 100

Testing Access to and Installing web.Client on a Client PC ... 100

Before Getting Started ... 101

Launching Internet Explorer in Windows Vista ... 102

Installing the web.Client Utilities Control ... 102

Installing Microsoft .NET Framework 2.0 ... 104

Installing web.Client Pinpoint ... 105

If your IIS PC Uses IIS 6.0 and Windows Server 2003 106 Installing the Video Layout Control and .NET Framework 3.5 ... 106

Setting Browser “Zone” Permissions for .NET Framework 108 Download and Install .NET Framework SDK 2.0 ... 108

Run the Microsoft Code Access Security Policy Tool . 109 Server Proxy Applications ... 110

Logging Out of web.Client ... 111

Chapter 5 Using web.Client to Set Up Your Organization ...

113

Overview ... 114

Example: Building a Security Management System ... 114

web.Client Security Basics ... 115

Testing web.Client Security ... 117

Scenario 1: A Single-Building Company ... 118

How Is the Company Physically Divided? ... 118

Who Are the Users? ... 119

What Are the Security Levels? ... 120

Setting Up web.Client in CyberStation ... 120

Scenario 2: A Global Company ... 121

What Are the Company Personnel Groups? ... 121

Where Are the Company Facilities Located? ... 122

Who Are the Users? ... 122

What Are the Security Levels? ... 123

(8)

Appendix A

web.Client Security and Troubleshooting Tips ...

125

Tips ... 126

Tip 1 - Ensuring Full System Access for at Least One User ... 126

Tip 2 - Placing PIM Files in a Single Folder ... 126

Tip 3 - Applying Security to non-web.Client Folders 127 Tip 4 - Verifying DCOM Is Enabled ... 128

Tip 5 - Enabling the Default Document ... 128

Tip 6 - Understanding Security Ramifications for IIS Applications ... 129

Tip 7 - Be Sure that IIS Is Installed before .NET Framework ... 130

Tip 8 - Changing IIS / Windows Server 2003 Resource Recycle Time ... 130

Appendix B

web.Client Applications that Are Installed ...

133

Installed Applications ... 134

Appendix C

Guidelines for Upgrading to Version 1.92 ...

135

Upgrade Guidelines ... 136

Appendix D

SQL Express Installation Error Messages ...

139

Overview ... 140

(9)

What’s in this Manual

z Introduction to web.Client

z System and Pre-Installation Requirements

z Installing and Configuring web.Client on the IIS PC z Testing and Installing web.Client on a Client PC z Using web.Client to Set Up Your Organization z web.Client Security and Troubleshooting Tips z web.Client Applications that Are Installed z Guidelines for Upgrading to Version 1.92 z SQL Express Installation Error Messages

(10)

About this Manual

Revision History

This manual documents web.Client, Version 1.92..

Symbols Used

The Notes, Cautions, Warnings, and Hazards in this manual are defined, as follows.

Note: Notes contain additional information of interest to the user.

CAUTION Type of hazard How to avoid hazard.

Failure to observe this precaution can result in injury or equipment damage.

WARNING Type of hazard How to avoid hazard.

Failure to observe this precaution can result in severe injury.

DANGER

ELECTRIC SHOCK HAZARD How to avoid hazard.

Failure to observe these instructions will result in death or serious injury.

(12)

(13)

Chapter 1

Introduction to web.Client

This chapter contains the following topics:

z web.Client Overview

z web.Client User Documentation z A Typical System before web.Client

z A Typical System Implementing web.Client z Differences between web.Client and CyberStation

(14)

Chapter 1: Introduction to web.Client

Overview

This manual provides you, the system administrator, with general information for planning, installing, and configuring your Andover Continuum web.Client system, version 1.92.

web.Client Overview

web.Client is an application that provides you with web-enabled access everywhere, all the time. By using a standard browser, your authorized personnel can access the Continuum facility management system in real time across your site’s local area network (LAN) or across your

CAUTION

This manual is for system administrators.

To use the installation and setup procedures in this manual you must be a system administrator with experience in setting up a web server. You must also have experience using Microsoft system software and understand that there are graphical user-interface differences between the different Windows platforms. For detailed information about Microsoft software, please see your Microsoft Windows online help and visit www.microsoft.com and other Microsoft web sites.

Failure to observe this precaution can result in incorrect system configuration.

Note: The procedures in this manual presume you and your users are installing or upgrading to web.Client version 1.92. You must meet the software and hardware requirements compatible with version 1.92. Refer to Chapter 2,

(15)

z View and generate reports of all access events, including area access events, access events by persons, and distribution-event transactions via the Access Distribution View

z Edit and view schedules and calendars.

z Change a password.

With the advanced web.Client Pro option, your users have all the features of the basic web.Client Personnel Manager option as well as the following additional features:

z Create, run, and view graphical reports (class object Report), including bar charts, pie charts, trend charts, text reports, and so on.

z List and view graphics and groups

z View live system alarms and live events

z View live video, as well as search for and view recorded video, via the class object, VideoLayout.

z Search for web.Client objects by exploring a folder tree hierarchy or a network/device tree hierarchy, or by using a text search engine

z Edit and view Loops and TrendLogs.

For complete information about any of these features, please see the web.Client online help.

web.Client User Documentation

Extensive online help is available within the web.Client application browser window. Click the question mark button. This button appears at the top of every web.Client screen. The online help covers all of the major features in the web.Client user interface.

(16)

Chapter 1: Introduction to web.Client

A Typical System before web.Client

The following illustration shows how your Continuum system is used before web.Client.

A Continuum system without web.Client consists of a database server and high powered, dedicated workstations. Also note that all

administration must be performed at one of the dedicated workstations.

The following illustration shows the administration of the typical system would entail. In this security example, a single administrator is responsible for assigning all security privileges for engineering and manufacturing personnel.

(17)

A Typical System Implementing web.Client

Illustrations on the next page show how your system is utilized when web.Client is added to a Continuum system. As shown in the second illustration, a web.Client local area network (LAN) system consists of:

z A database server

z Dedicated workstations for configuration z A dedicated web.Client application server

z PCs running Internet Explorer 7.0 or 8.0 connecting web.Client

You can delegate security tasks to authorized personnel who then assign security privileges for their departments (in this case, engineering and manufacturing personnel).

You use the dedicated workstation, and the authorized personnel use web.Client on their own computers.

In the administration of a web.Client system, for example, you would be responsible for assigning privileges to engineering and

manufacturing designees, who in turn are responsible for assigning all security privileges for engineering and manufacturing personnel. Similarly, you could grant access rights to:

z An employee to adjust the temperature after viewing current

conditions

z A coordinator to schedule a conference room and activate the

lighting

z A technician to take control of an air handler during service

z A manager to search video for an incident

z A facilities manager to graphically monitor and adjust building

conditions and monitor alarms

Note: You will be installing either a web.Client for a LAN system or a standalone with web.Client. A LAN system has two servers: a database server and a web.Client application server. In a standalone system, the database and web.Client application reside on one server. Chapter 2, System and Pre-Installation Requirements, provides detailed requirements for both systems.

(18)

(19)

Differences between web.Client and CyberStation

web.Client is an extension of CyberStation. Through the convenience of a web browser, you can view, monitor, and in some cases modify objects and their values. (These include BACnet® objects, since CyberStation and web.Client support the BACnet ANSI/ASHRAE standard.)

However, there are some differences between what your users can do in web.Client vs. CyberStation. You generally use web.Client to view and monitor objects that were defined in CyberStation. The following table lists the levels of support offered with each major web.Client feature. For information on web.Client features, see the web.Client online help.

web.Client Levels of Support LEVELS OF web.Client SUPPORT

Feature View Modify Delete Create

Personnel X X X X

Schedules and Calendars X X X

Events within schedules only Events within schedules only Reports X X X Areas X Groups X Loops X X Graphics X Alarms X X Events X Distribution Events X X X

Points and objects X X X

Except: BACnet objects cannot be deleted.

TrendLogs X X

Video X 1

1. Video can be modified, but not saved. For example, you can change cameras, show/hide time, change focus, zoom, but you will lose these changes if the page is refreshed or you open another editor.

Doors X X

(20)

(21)

Chapter 2

System and Pre-Installation

Requirements

This chapter contains the following topics:

z web.Client Setup Configurations

z Hardware and Software Requirements for LAN System

z Hardware and Software Requirements for a Standalone System z Pre-Installation Microsoft Tasks

Note: Before installing or upgrading to web.Client version 1.92, be sure the requirements outlined in this chapter are satisfied.

(22)

Chapter 2: System and Pre-Installation Requirements

web.Client Setup Configurations

Depending on your web.Client version 1.92 package and configuration, you are setting up either:

z web.Client local area network (LAN) system z A standalone “single user” system with web.Client

LAN system: The web.Client LAN system comprises a Continuum/

SQL database server and an Internet Information Services (IIS) server dedicated to running the web.Client application. On a LAN system, the IIS server can be a Windows XP Professional workstation, Windows Server 2003, or Windows Vista, but each supports a different number of user connections. See the table below.

Standalone system: The standalone “single user” system with

web.Client comprises one PC on which the Continuum/SQL Express database, IIS, and the web.Client application all reside. A standalone system PC may also run Windows XP Professional workstation, Windows Server 2003, or Windows Vista.

The following table lists the maximum number of web.Client version 1.92 users per server, as well as the maximum number of

CyberStations and IIS servers, for each type of setup:

Maximum Number of web.Client 1.92 Users Per Server

Maximum Number of web.Client Users Per Server

Number When IIS Is

Installed on

When IIS Is Installed on

(23)

Hardware and Software Requirements for LAN System

A web.Client LAN system has two server types:

z Continuum/SQL database server z IIS server (one for every 25 users)

If your system has no more than 25 users, select one server as the web.Client IIS server. This IIS server should be dedicated to running the web.Client application. For a larger LAN system (at least for any system having more than 25 users) your site must have more than one IIS server.

Depending on your particular LAN installation, the IIS server can be:

z Windows XP Professional workstation (maximum of two users) z Windows Server 2003 (maximum of 25 users per IIS server) z Windows Vista (maximum of two users per IIS server)

The IIS server must be on a network that can connect to the Continuum/SQL database server. The browser PCs must be on a network that can connect to the IIS server.

web.Client version 1.92 will upgrade any previous version on IIS server. web.Client 1.92 includes CyberStation 1.92, and installing it upgrades the IIS machine to 1.92. Workstations not at version 1.92 must be upgraded before installing web.Client.

(24)

Hardware and Software Requirements for a

Standalone System

On a single-user standalone system with web.Client, the Continuum SQL Express database, IIS, and the web.Client application are all installed on one Windows XP Professional workstation, one Windows Server 2003, or one Windows Vista machine.

web.Client version 1.92 will upgrade any previous version’s IIS server. web.Client 1.92 includes Cyberstation 1.92, and installing it upgrades the IIS machine to 1.92. Workstations other than the IIS server that are not at version 1.92 must be upgraded before installing web.Client.

Browser PCs for Users on a LAN System

Tested & Supported Browser PCs for Users on a LAN System

Hardware Software

The video feature requires network access to a digital video recorder. This may require you to open port 18772 or establish a Virtual Private Network (VPN) connection if there is a firewall.

The client browser PC on a LAN system can be running one of the following:

z Windows XP Professional (SP3)

z Windows Server 2003 (SP2) or Windows Server 2003 R2 (SP2)

z Windows Vista Business (SP2), Vista Ultimate (SP2), or Vista Home Premium SP2)

For Windows XP, Windows Server 2003, or Windows Vista:

Internet Explorer 7.0 OR Internet Explorer 8.0

Verify IE defaults are enabled for: Cookies and JavaScript

Note: The standalone system can accommodate two user connections (browser PCs). If you require more than two users, then you must upgrade to a LAN system with Windows Server 2003 (maximum 25 users).

(28)

(Refer to the Andover Continuum CyberStation Installation Guide, 30-3001-720, for upgrade procedures.)

Pre-Installation Microsoft Tasks

Before installing web.Client, perform the following tasks.

Browser PCs for Users on a Standalone System

Tested & Supported Browser PCs for Users on a Standalone System

Hardware Software

The video feature requires network access to a digital video recorder. This may require you to open port 18772 or establish a Virtual Private Network (VPN) connection if there is a firewall.

The client browser PC on a standalone system can be running one of the following:

z Windows XP Professional (SP3)

z Windows Server 2003 (SP2) or Windows Server 2003 R2 (SP2)

z Windows Vista Business (SP2), Vista Ultimate (SP2), or Vista Home Premium SP2)

For Windows XP and Server 2003: Internet Explorer 7.0 or Internet Explorer 8.0

For Windows Vista Home Premium: Internet Explorer 7.0

Verify IE defaults are enabled for Cookies and JavaScript

CAUTION

Microsoft system experience required.

To perform this standard Microsoft procedure, you must have administrative experience using Microsoft system software and understand that there are differences in the graphical user interfaces between different Windows platforms. User interface illustrations are not provided. Please see your Microsoft Windows online help and visit www.microsoft.com and other Microsoft web sites.

(32)

Installing System Software

Install the operating system, TCP/IP, and PC system software that meet the requirements specified earlier in this chapter.

.NET Framework 2.0

To avoid this problem, be sure that IIS has been installed on the server before Microsoft .NET Framework 2.0 is installed.

If Microsoft Windows already comes with .NET Framework 2.0, or you have downloaded .NET Framework 2.0 separately during a Windows upgrade before IIS is installed, run the following command:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

Installing IIS on Windows Server 2008

For Windows Server 2008, install Internet Information Services (IIS) on the designated web.Client application server (LAN systems) or the standalone CyberStation/web.Client workstation (standalone system). The LAN web.Client application server and standalone CyberStation/ web.Client workstation are generically called IIS PC in this manual for both systems.

1. Start the Server Manager by clicking in the Administrative

Tools menu.

Note: If IIS is installed after .NET Framework, you will experience problems opening web.Client Pinpoint graphics and some web.Client editors.

(33)

(34)

(35)

4. In the Select Server Roles page, check the Application Server checkbox to install .Net Framework 3 as a prerequisite.

(36)

5. Click Add Required Features.

(37)

7. In the Application Server page, click Next.

.

8. In the Select Server Roles page, check the following checkboxes:

Web Server (IIS) Support, HTTP Activation, and Message Queuing Activation.

(38)

An Add role services/features required dialog displays for each of your role service selections.

9. Click the Add Required Role Services or Add Required

Features button to install additional features for Web Server (IIS) Support, HTTP Activation, and Message Queuing Activation.

(39)

(40)

(41)

12. In the Select Role Services page, check the IIS 6 Management

Compatibility checkbox.

13. Click Next.

14. In the Confirm Installation Selections page, click Install to verify your selections.

(42)

An Installation Progress page displays with information on the roles, role services, or features being installed.

(43)

Installing IIS on Windows XP and Windows Server 2003

For Windows XP and Windows Server 2003, install IIS on the designated web.Client application server (LAN systems) or the standalone CyberStation/web.Client workstation (standalone system). The LAN web.Client application server and standalone CyberStation/ web.Client workstation are generically called IIS PC in this manual for both systems.

For Windows XP: Follow this procedure to install IIS 5.0:

1. From the Control Panel, open Add/Remove Programs. The

Add/Remove Programs dialog appears.

2. Select Add/Remove Windows Components. The Windows

Components Wizard (Windows Components) screen appears. 3. Check the Internet Information Services (IIS) checkbox, and

click Next to install.

(44)

4. After the Wizard completes the component-configuration process, which may take several minutes, click Finish.

For Windows Server 2003: Follow this procedure to install IIS 6.0: 1. From the Control Panel, open Add/Remove Programs. The

Add/Remove Programs dialog appears.

2. Select Add/Remove Windows Components. The Windows

Components Wizard (Windows Components screen) appears. 3. Check the Application Server checkbox.

4. Select and highlight Application Server, and click the Details button. The Application Server dialog appears.

5. Check the following checkboxes: ASP.NET, Application Server

Console, Enable network COM+ access, and Internet Information Services (IIS).

6. In the Application Server dialog, select and highlight Internet

Information Services (IIS) and click the Details button. The Internet Information Services (IIS) dialog appears.

7. Check the following checkboxes: Common Files, Internet

Information Services Manager, and World Wide Web Service.

8. In the Internet Information Services (IIS) dialog, select and highlight World Wide Web Service, and click the Details button. The World Wide Web Service dialog appears.

9. Check the following checkboxes: Active Server Pages, Internet

(45)

Registering File Extensions for Windows Server 2003

If you have Windows Server 2003, you must also register the .PIN and .EMF file extensions in the IIS MIME Types (for web.Client Pinpoint graphics).

After IIS installation on Server 2003, follow this procedure:

1. From the Control Panel, double click and open Administrative

Tools. The Administrative Tools dialog appears.

2. Double click and open Internet Information Services (IIS)

Manager. The Internet Information Services (IIS) Manager

dialog appears.

3. In the tree, right click on the machine name, and select Properties from the popup menu. The Properties dialog appears.

4. Click the MIME Types button. The MIME Types dialog appears. 5. Click the NEW button. The MIME Type dialog appears.

6. In the Extension field, enter .pin and in the MIME type field, enter pinfiles/plain.

7. Click OK and repeat steps 5 and 6, but in the Extension field, enter .emf and in the MIME type field, enter image/emf. 8. Click OK three times back through the dialogs.

9. Restart your machine, follow the other pre-installation tasks, and follow the installation procedures in Installing and Configuring web.Client on the IIS PC and Testing and Installing web.Client on a Client PC.

Configuring IIS for Windows Vista

If you are installing web.Client on Windows Vista, you must configure IIS settings, as follows.

1. From the Control Panel, open Programs and Features.

(46)

3. In the Windows Features (Turn Windows features on or off) dialog, in the tree, expand Internet Information Services. 4. Under Internet Information Services, expand Web

Management Tools, then expand IIS 6 Management Compatibility.

5. Check only the following checkboxes: IIS 6 Management

Console, IIS Metabase and IIS 6 configuration

compatibility, and IIS Management Console. Other checkboxes

must be cleared.

6. Under Internet Information Services, expand World Wide

Web Services, then expand Application Development

Features, Common Http Features, Health and Diagnostics, Performance Features, and Security.

7. Check only the following checkboxes: .NET Extensibility,

ASP.NET, ISAPI Extensions, ISAPI Filters, Default Document, Directory Browsing, HTTP Errors, Static Content, HTTP Logging, Request Monitor, Static Content Compression, Request Filtering, and Windows

Authentication. Other checkboxes must be cleared. 8. Click OK.

Restart your machine, follow the other pre-installation tasks, and follow the installation procedures in Installing and Configuring web.Client on the IIS PC and Testing and Installing web.Client on a Client PC.

(47)

2. In the Connections tree, select the machine name.

3. In the right-hand content pane, under IIS, double click MIME

Types. The Add MIME Type dialog appears. 4. Under Actions, click Add.

5. In the File name extension field, enter .pin. 6. In the MIME type field, enter pinfiles/plain.

7. Click OK and repeat Steps 4, 5, and 6, but in the File name

extension field, enter .emf and in the MIME type field, enter image/emf.

8. Click OK.

9. Restart your machine, follow the other pre-installation tasks, and follow the installation procedures in Installing and Configuring web.Client on the IIS PC and Testing and Installing web.Client on a Client PC.

SSL Considerations for the IIS PC

The tasks described below are not necessarily pre-installation tasks, but they are related to establishing support for SSL on the IIS PC. For detailed instructions, please use the reference links below.

Setting Up SSL on the IIS PC -- web.Client version 1.74 (and higher)

fully supports Secure Sockets Layer (SSL) technology, whereby a web.Client user can access confidential, secure information over the Internet. As a system administrator, you must ensure that an SSL Certificate, acquired by an authorized SSL provider, resides on the IIS PC. You can set up SSL before or after web.Client installation. For instructions, please see Establishing SSL Support for Confidential Information in Chapter 3.

Enabling SSL for web.Client -- After you have set up an SSL

Certificate for the IIS PC, you must enable SSL for web.Client via web.Client Properties in Internet Information Services. For instructions, please see Enabling SSL for web.Client in Chapter 3.

(48)

SSL and web.Client Pinpoint Graphics -- The graphics package,

web.Client Pinpoint, can be used with an SSL installation. However, you must perform a few tasks to ensure compatibility with Pinpoint and ensure access to graphics files that have been set up in the

Pinpoint graphics folders. This is not a pre-installation task. You must first establish Pinpoint graphics folders (Chapter 3) and set up an SSL Certificate on the IIS PC. For instructions, please see Setting Up SSL for web.Client Pinpoint in Chapter 3.

Changing IE Internet Security Options to Accommodate SSL --

After you have set up an SSL Certificate for the IIS PC, you must modify Internet Explorer Internet Options to disable superfluous warning messages that users would otherwise see while using certain web.Client features with SSL. This is not a pre-installation task. For instructions, please see Changing IE Security Internet Options to Accommodate SSL in Chapter 3.

Changing the Default TCP Web Port Number for the IIS PC

Normally, the IIS PC defaults to Internet TCP port 80. Some Internet-access providers do not use port 80. You can change this port number from 80 to another port number. This can be done before or after web.Client installation. For more information, please see Changing the Default TCP Port Number in Chapter 3

Disabling WinSock Proxy Client on Standalone System

To improve performance on a single-user standalone system, disable the Microsoft WinSock Proxy Client. Follow this procedure:

(49)

Ensuring a Domain Membership Is Selected

To improve performance (if your site has more than one web.Client user), be sure each PC (computer name) is designated as a member of a domain, rather than a workgroup, via the Microsoft Windows system properties network identification.

Avoiding Invalid Characters in a Server Name

When specifying a name for the web.Client IIS server, be sure the server name does not contain an underscore character (_). If the web.Client IIS server has an underscorehttp://www.boston.com/

yourtown/news/malden/2010/05/planning_board_gives_green_lig.html, it will not be able to set cookies.

Disabling Windows Firewall

If your IIS server is a Windows XP (SP3), Windows Server 2003 (SP2) or Windows Vista machine, you must disable the Windows firewall as follows:

1. From the Control Panel, open Windows Firewall. The

Windows Firewall dialog appears.

2. Select the Off (not recommended) radio button, and click OK. Note: After installing web.Client, be sure you configure Distributed COM (DCOM) default security settings and disable HTTP keep-alives. For those Microsoft procedures, see Chapter 3, Installing and Configuring web.Client on the IIS PC. See also Appendix A, web.Client Security and Troubleshooting Tips for troubleshooting tips.

(50)

Disabling Automatic Windows Updates

When running web.Client, you must disable Automatic Updates in Windows by following these instructions:

In Windows XP:

1. From the Control Panel, open Automatic Updates. The

Automatic Updates dialog appears.

2. Select the Turn off Automatic Updates radio button. 3. Click OK.

In Windows Vista:

1. From the Control Panel, open Windows Update. The Windows

Update with Windows Ultimate Extras page appears.

2. Click Change Settings on the right-side of the page. The Choose

how Windows can install updates page displays.

3. In the Important Updates drop-down menu, click the Never

check for updates (not recommended) menu item. 4. Click OK

(51)

Chapter 3

Installing and Configuring

web.Client on the IIS PC

This chapter contains the following topics

z Overview

z Installing web.Client on the IIS PC z web.Client Video System Upgrades z Configuring Your Video Servers

z Configuring Graphics Folders for web.Client: Windows XP and

Windows Server 2003

z Configuring Graphics Folders for web.Client: Windows Vista z Establishing Pinpoint Folders

z Configuring DCOM Default Security Settings z Disabling HTTP Keep-Alives

z Resetting Timeout and Live Events Via web.config File z Establishing SSL Support for Confidential Information z Changing the Default TCP Port Number

(52)

Chapter 3: Installing and Configuring web.Client on the IIS PC

Overview

This chapter provides instructions for installing and configuring web.Client version 1.92 on the IIS PC, defined as follows:

z The IIS PC on a LAN system is the IIS server with Windows Server

2003, Windows XP Professional workstation, or Windows Vista.

z The IIS PC on a standalone system with web.Client is the single

machine (Windows XP Professional workstation, Windows Server 2003, or Windows Vista) on which both IIS and Continuum database reside.

The procedures in this chapter are for a first-time installation. If you are upgrading to web.Client version 1.92, refer to Appendix C, Guidelines for Upgrading to Version 1.92, which presents some guidelines for this upgrade. See also the Andover Continuum CyberStation Installation Guide, 30-3001-720.

CAUTION

Microsoft system experience required.

To perform this standard Microsoft procedure, you must have administrative experience using Microsoft system software and understand that there are differences in the graphical user interfaces between different Windows platforms. User-interface illustrations are not provided. Please see your Microsoft Windows online help and visit www.microsoft.com and other Microsoft web sites.

(53)

Installing web.Client on the IIS PC

Follow this procedure to install web.Client on the IIS PC.

1. Insert the web.Client CD. The Install web.Client screen displays. Click Install web.Client to begin.

2. If you do not have the Microsoft VS 2008 C++ Redistributable installed, an InstallShield Wizard appears and indicates that this application is required before the CyberStation installation begins. Click Install.

Continuum then checks to ensure that Microsoft .NET Framework 3.5 is also installed. If not, the following message displays:

(54)

Continuum then checks to ensure that Microsoft .NET Framework 3.5 is also installed. If not, the following message displays:

Follow these instructions, discontinue this CyberStation installation, and install the .NET Framework 3.5 from the Continuum release CD.

Once these requirements are installed, return to this installation and when the initial Install web.Client screen displays once more, click Install web.Client.

3. When the web.Client Installation dialog appears, click Next to continue.

Note: If you do not have the correct Microsoft service pack installed, you will receive a warning message, asking you to install the correct software. See Chapter 2 for software requirements.

(55)

If your key is not enabled for web.Client, you will receive a warning message. You may continue with the installation or cancel.

4. The License Information dialog appears. Read and accept the license agreement, and click Next to continue.

5. The RegisterUser dialog appears. Enter your User Name and

Company Name.

Later, after web.Client is installed, you can right-click on the Continuum icon in your tool tray and select About to display the

About Continuum dialog, which lists the information from the RegisterUser dialog.

6. An Alias Information screen appears explaining what happens next in the installation.

(56)

After reading this screen, click Yes to continue.

The Enter Text screen asks you to provide the web.Client Virtual Directory Alias. Keep the default alias (WebClient) or provide your own alias. Click Next to continue.

(57)

The Setup Status screen appears as the files are installed.

Once the progress bar disappears, the Create IIS Application window appears and informs you that the IIS application is being created.

Then, you are asked if you would like to read the latest web.Client release notes. Click Yes or No.

(58)

Finally, you are asked if you would like to run the Database Initialization program now. Click Yes or No.

web.Client is now installed on the IIS PC. Depending on your system, follow one of the next three procedures, covered in the following subsections:

z Creating and Initializing the Database on a Standalone IIS PC z Adding web.Client to an Existing Standalone Database

(59)

Creating and Initializing the Database on a Standalone IIS PC

A first-time database installation on a standalone system happens in two steps via the Database Initialization dialog:

Step 1: Installing the SQL Express database engine. Step 2: Creating a new Continuum database.

Installing SQL Express Via Database Initialization Dialog

Follow this procedure:

1. From the Start menu, select Programs > Continuum >

Database Initialization.

2. Select Stand Alone from the Continuum Database

Initialization dialog.

Note: After successful installation, the Continuum Database Initialization dialog automatically appears.

CAUTION

Close all applications on your computer before installation.

After SQL Express is installed, your PC restarts immediately. You cannot restart your computer later. Be sure to close all open applications on your computer.

(60)

(61)

Note that Microsoft SQL Server is shown in the DBMS Name field dropdown menu.

4. Ensure that Continuum (default setting) appears in the Data

Source Name field.

5. Ensure that (Workstation Name)\SQLEXPRESS appears in the

Server Name field. For example, QUALPC217 is the workstation

name used in the previous dialog.

6. Leave the Database Name at its default, ContinuumDB. 7. Enter your login ID, Andover97, in the User Login ID field. 8. Enter your user password in the User Password field.

9. Re-enter your password (Pyramid97 if you are upgrading to 1.92 from the previous version default) in the Confirm Password field. 10. DB File Location: If you leave DB File Location at its default

path, then you must leave SQL Express at its default path when it is installed. If you browse a different path for DB File Location, then you must browse SQL Express to the same file path when it is installed.

11. Leave the Database Size at its default setting.

12. Enter a system administrator password of your choice into the Sa

Password field.

This password must meet Microsoft SQL Server rules for the composition of a password:

The password must be at least eight characters long.

The password must not contain all or part of the user’s account name

(three or more alphanumeric characters).

The password must not contain the following characters: comma (,),

period (.), hyphen (-), underscore (_), or number sign (#).

The password must contain characters from three of the following four

categories:

Uppercase letters (A...Z)

Note: If you are upgrading to Version 1.92, and you accepted the pre-1.92 default password, Pyramid97, you must enter Pyramid97 here. If you are installing web.client for the first time, use a password of your choice.

(62)

Lowercase letters (a...z) Digits 0...9

Non-alphanumeric characters, such as exclamation (!) and dollar ($)

Otherwise you will receive this warning:

13. In the Windows User Name field, enter your Microsoft Windows system user name here. This is necessary with SQL Express. You must have administrative access in order to run the automated scripts that are part of the database initialization process.

14. Enter your Microsoft Windows system password and confirm that password in the Windows Password and Confirm Password fields, respectively.

15. Check the checkboxes as follows:

CAUTION

The password you enter here is required to execute scheduled SQL Server tasks. Should you later change your Windows password, these scheduled tasks will no longer execute. To correct this, access the Scheduled Tasks in Windows and change their password with the Set Password button in their Properties dialog

(63)

b. Create System List Views - Check this box to import and create

list-views (from the ASCII dump file, List.dmp) for system information other than object class defaults (for example, all events).

c. Create System Alarm Enrollments - Check this box to import

con-figured system AlarmEnrollment objects (from the ASCII dump file, SystemAlarms.dmp). These define the basic conditions under which CyberStation points go into alarm.

d. Create/Update Graphical Report Settings - Check this box to

import graphical report templates. CyberStation supplies many Report templates that include bar-chart templates, pie-chart tem-plates, and trend temtem-plates, giving Reports a certain default “look and feel.” If you do not check this box, then these report templates will not be available. For more information on Reports, see the Continuum CyberStation online help.

e. Enhanced Alarm Logging - Check this box to activate an enhanced

method that automatically speeds up the process of logging alarms with workstations. Without enhanced alarm logging, configuration of workstation recipients in EventNotification objects becomes more cumbersome.

f. Enhanced Alarm Delivery - This checkbox is intended for a system

with multiple workstations. Check this box only if you intend to add more workstations to the system. If more workstations will not be added, then leave it unchecked.

Checking this checkbox guarantees the delivery of alarms to all recipient workstations regardless of their status at the time of the alarm generation.

This selection activates special background applications and processes (already installed) that establish an ongoing connection between workstations and the database server, where new alarms are written. Enhanced alarm delivery guarantees alarm delivery even when connections are lost. The alarms are delivered when the connection is restored.

Enhanced alarm delivery provides a suite of diagnostic and

troubleshooting tools that allow you, for example, to monitor the status of alarm messages and background alarm delivery processes as well as

Note: If the Enhanced Alarm Logging checkbox is not checked, the Enhanced

Alarm Delivery checkbox becomes unselectable.

Note: This setting has no effect on BACnet alarms, which can be guaranteed through the configuration of BACnet alarm notifications.

(64)

ping a particular workstation to deliver an alarm message that, for some reason, could not be delivered. For instructions on how to activate these diagnostic tools, please contact product support services.

g. Extended Logging Backwards Compatibility - If you want to use

pre-Version 1.7 “old” extended logging, in addition to “new” extended logging, be sure this checkbox is checked.

For more information about extended logs, please see the Continuum CyberStation online help.

16. Click the Continue button.

The Is SQL Express Installed dialog appears.

Note: Before version 1.7, you created Plain English programs for extended logs. These programs facilitated extended log tables in the database, one table per controller. In version 1.7 or higher, you must check the Extended Logging

Backwards Compatibility box to retain the older method for creating

(65)

During SQL Express installation, the software checks your computer for certain problems that could complicate SQL installation and/or the creation or update of the Continuum database. There are several different scenarios. For example, third-party software may generate license-agreement issues. For a detailed description of these issues, how CyberStation resolves them, and a list of error messages, please see Appendix D, SQL Express Installation Error Messages.

If there are no problems, the Select Folder dialog appears.

18. Accept the default path, or use the browse button to select a directory in which to install SQL Express, and click OK.

19. The Extracting Files progress window appears. The unpacking takes approximately 1 to 5 minutes. Next, the Microsoft SQL

Server 2005 Setup progress window appears. This also can take

several minutes. After the installation has completed, the reboot dialog appears, which may take up to 60 seconds. Do not proceed

until this dialogue appears. Click OK and reboot your computer.

20. After rebooting, a screen telling you that SQL script is running then appears. This screen closes automatically after a few minutes. Note: If you left DB File Location at its default path, then you MUST leave SQL

Express at its default path when it is installed. If you browsed a different path

for DB File Location, then you must browse SQL Express to the same file path

Note: Be sure that the drive you have selected has a minimum of 2 GB of free space available.

(66)

21. After your PC finishes rebooting, verify MSSQL server is running. Double click the SQL Server Service Manager icon in the system tool tray.

The SQL Server Service Manager dialog appears.

The status bar at the bottom of the dialog should read:

Running - \\WorkstationName\SQLEXPRESS - MSSQLServer

Note: If the SQL Server Service Manager icon is not present in the system tool tray, try running it from the Windows Start menu. Click Start, select

Programs and Startup. The SQL Server Service Manager icon should be

there. If this does not work, contact the Schneider Electric Technical Support department for further instructions.

(67)

2. Select Stand Alone.

The Database Initialization dialog, shown on the next page, appears.

3. Select the Update Existing Database radio button. 4. Click the Continue button.

Upon completion, you receive this message: Database successfully updated

5. Click OK.

The Continuum Database Initialization window reappears. 6. Click Close.

(68)

Initializing the Database on a LAN IIS PC

Prior to using your web.Client LAN system IIS PC, perform the following procedure to initialize the database. The detailed procedure for CyberStation is presented in the Andover Continuum CyberStation Installation Guide, 30-3001-720, but the web.Client specific steps are

(69)

Select the Workstation tab to set the workstation parameters. Set the Workstation Name, Folder Name, Device Node ID and

Network ID for the workstation. See the Andover Continuum

(70)

3. Select the Database tab, shown on the next page.

4. Fill in the fields as shown below if you are adding a new server to a LAN system. If this is a server upgrade, they will be populated automatically. The Server Name field should be set to the name of your Continuum database server.

5. Click OK to activate the workstation, then click Close on the

Continuum Database Initialization window to complete the

database initialization.

Note: The Andover Continuum CyberStation Installation Guide, 30-3001-720, provides important guidelines for entering information in the Workstation

(71)

web.Client Video System Upgrades

If you are upgrading from a pre-1.92 version of web.Client, the Learn

All Video Servers dialog appears at the completion of the database

initialization process. You must learn your video servers in order to see cameras.

For more information on configuring video servers, see Configuring Your Video Servers. For more information on upgrading web.Client, see Appendix C, Guidelines for Upgrading to Version 1.92.

1. Click Yes to learn all servers and cameras now, or No to learn them later in CyberStation’s Video Administrator.

It is recommended that you learn video servers and cameras now since it is more efficient to learn them all at once rather than learning them individually later.

If you click Yes, the Learn All Video Servers - Status dialog, shown on the next page, displays. It shows a count of the servers and cameras as they are learned.

2. Click Close to stop the learn process at any time.

The video servers and cameras will then be in a partially-learned state- with only those servers and cameras that have been learned to that point displaying in the Learn All Video Servers - Status dialog.

Note: Should you choose not to learn servers and cameras now, you will need to learn them later in Video Administrator. For more information on learning cameras , see the Video Administrator Settings tab in the CyberStation online help.

(72)

Note: If your video system is unstable, you may receive an ERROR:SERVERNAME message during the learn process. Should this occur, ensure that your system is stable and then perform a single Learn Cameras operation for that server. For more information, see the Video Server Editor - General Tab in the CyberStation online help.

(73)

Routing Alarms to the IIS PC on a LAN System

On a LAN system, perform the following procedure from another CyberStation to route alarms to the IIS PC:

1. For every EventNotification object, add the IIS PC’s workstation to the list of alarm recipients to be notified. To do so, open the

EventNotification editor and select the Delivery tab.

2. In the Delivery tab, click the Add Recipient button. The

Recipients Configuration dialog, shown on the next page,

appears.

3. Use the Recipient field’s browse button and the browse dialog to search for and select the workstation that is on the IIS PC. 4. Configure these settings appropriately for your system. There are

several ways to configure recipients, according to your needs. Refer to the Continuum CyberStation online help, for information on the configuration of event notifications.

(74)

Configuring Access Permissions for web.Client Users

Perform the following CyberStation procedure to grant or deny security access permissions for web.Client users.

1. From the system tray in the lower right corner of your screen, right-click on the Continuum icon, and select Security from the Note: For additional enhanced alarm delivery, ensure that the Enhanced Alarm

Delivery checkbox is checked via the Database Initialization dialog. For

detailed information on the checkboxes in the Database Initialization dialog, please see the Andover Continuum CyberStation Installation Guide, 30-3001-720.

(75)

For complete Continuum security configuration procedures, see the Andover Continuum CyberStation Access Control Essentials Guide, 31-3001-405, or the Continuum CyberStation online help.

Configuring Your Video Servers

For your users to access the web.Client video surveillance monitor (also known as a “video layout”) and assign one or more cameras to a video layout camera matrix, at least one video server must have been configured via Continuum’s VideoServer object editor, so that its cameras are available to the video layout.

For more information on configuring a video server (and the VideoServer object) please see VideoServer in the Continuum CyberStation online help. For more information on configuring video layouts, please see Video in the web.Client online help.

5. For each user group, edit each web.Client action to grant or deny permission to access the web.Client feature. To grant access, click to display a key, as shown above. To deny access, leave the lock, or if unlocked, click to display a lock.

Note: VideoServer and VideoLayout objects are created on CyberStation. Though you may modify a VideoLayout in web.Client, you cannot save your modifications in web.Client; only on CyberStation.

(76)

Configuring Graphics Folders for web.Client: Windows

XP and Windows Server 2003

If you have Windows XP or Windows Server 2003, perform the following procedures. If you have Windows Vista, see Configuring Graphics Folders for web.Client: Windows Vista.

Your users must access web.Client Pinpoint graphics file folders as URL web-address locations on the Internet. This section presents the

following procedures:

z Specifying a Local Folder as a Web Address

z Specifying a Network Folder as a Web Address

z Verifying Anonymous Access to Virtual Folders

Specifying a Local Folder as a Web Address

Use the following procedure to specify local folders as web addresses: 1. Using your Windows Explorer, search for and select the folder that

you wish to access as a URL web address. For example, suppose the folder name is NewGraphicsFiles.

Note: If you are using SSL (and an SSL Certificate) to facilitate exchanges of encrypted, confidential information, then you must also set up web.Client Pinpoint to be compatible with SSL. For instructions, please see Setting Up SSL for web.Client Pinpoint later in this chapter.

Andover Continuum web.client Planning and Installation Guide for Version 1.92

Planning and Installation Guide

for Version 1.92

Planning and Installation Guide

About this Manual ...

9

Chapter 1

Introduction to web.Client ...

13

Chapter 2

System and Pre-Installation Requirements ...

21

Chapter 3

Installing and Configuring web.Client on the IIS PC ...

51

Chapter 4

Testing and Installing web.Client on a Client PC ...

99

Chapter 5

Using web.Client to Set Up Your Organization ...

113

Appendix A

web.Client Security and Troubleshooting Tips ...

125

Appendix B

web.Client Applications that Are Installed ...

133

Appendix C

Guidelines for Upgrading to Version 1.92 ...

135

Appendix D

SQL Express Installation Error Messages ...

139

What’s in this Manual

Revision History

Related Documentation

Symbols Used

Chapter 1

Introduction to web.Client

Overview

web.Client Overview

web.Client User Documentation

A Typical System before web.Client

A Typical System Implementing web.Client

Differences between web.Client and CyberStation

Chapter 2

System and Pre-Installation

Requirements

web.Client Setup Configurations

Hardware and Software Requirements for LAN System

Hardware and Software Requirements for a

Standalone System

Pre-Installation Microsoft Tasks

Installing System Software

.NET Framework 2.0

Installing IIS on Windows Server 2008

Installing IIS on Windows XP and Windows Server 2003

Registering File Extensions for Windows Server 2003

Configuring IIS for Windows Vista

SSL Considerations for the IIS PC

Changing the Default TCP Web Port Number for the IIS PC

Disabling WinSock Proxy Client on Standalone System

Ensuring a Domain Membership Is Selected

Avoiding Invalid Characters in a Server Name

Disabling Windows Firewall

Disabling Automatic Windows Updates

Chapter 3

Installing and Configuring

web.Client on the IIS PC

Overview

Installing web.Client on the IIS PC

Creating and Initializing the Database on a Standalone IIS PC

Installing SQL Express Via Database Initialization Dialog

Initializing the Database on a LAN IIS PC

web.Client Video System Upgrades

Routing Alarms to the IIS PC on a LAN System

Configuring Access Permissions for web.Client Users

Configuring Your Video Servers

Configuring Graphics Folders for web.Client: Windows

XP and Windows Server 2003