Web Client Configuration Guide (for Microsoft IIS Web Server)

Citect Pty. Limited 3 Fitzsimons Lane PO Box 174 Pymble NSW 2073 Australia Telephone: 61 2 9496 7300 Fax: 61 2 9496 7399

DISCLAIMER Citect Corporation makes no representations or warranties with respect to this manual and, to the maximum extent permitted by law, expressly limits its liability for breach of any warranty that may be implied to the replacement of this manual with another. Further, Citect Corporation reserves the right to revise this publication at any time without incurring an obligation to notify any person of the revision. COPYRIGHT Copyright 2005 Citect Corporation. All rights reserved. TRADEMARKS Citect Pty. Limited has made every effort to supply trademark information about company names, products and services mentioned in this manual. Trademarks shown below were derived from various sources. Citect, CitectHMI, and CitectSCADA are registered trademarks of Citect Corporation. IBM, IBM PC and IBM PC AT are registered trademarks of International Business Machines Corporation. MS-DOS, Windows, Windows 95, Windows NT, Windows 98, Windows 2000, Windows for Workgroups, LAN Manager, Microsoft Windows XP, Excel and MSMAIL are trademarks of Microsoft Corporation. DigiBoard, PC/Xi and Com/Xi are trademarks of DigiBoard. Novell, Netware and Netware Lite are registered trademarks of Novell Inc. dBASE is a trademark of Borland Inc. GENERAL NOTICE Some product names used in this manual are used for identification purposes only and may be trademarks of their respective companies. December 2005 edition for CitectSCADA Version 6.1 Manual Revision Version 6.1. Printed in Australia.

Contents
CitectSCADA Web Client
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 System architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Setting up your Web Server using Microsoft IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Selecting an appropriate PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Whats been installed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 The IIS virtual directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Web Client user account types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Setting up security using IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Client type access rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Configuring client account user groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Preparing the Web Server folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Setting up access rights for client accounts . . . . . . . . . . . . . . . . . . . . . . . . . 18 Deleting a user account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Testing the Web Server security settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Logging on to the Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Preparing a CitectSCADA Project for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Functionality limitations of the Web Client platform. . . . . . . . . . . . . . . . . . . . 21 Feature limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Cicode Function Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Preparing a projects user files for delivery . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Running the Web Deployment Preparation tool . . . . . . . . . . . . . . . . . . . . . . 24 Configuring a deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Creating a new deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Deploying a project from within CitectSCADA. . . . . . . . . . . . . . . . . . . . . . . . 28 Displaying a deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Editing an existing deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Updating a deployment to reflect project changes . . . . . . . . . . . . . . . . . . . . 32 Deleting a deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Implementing Multiple Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 How default languages are implemented . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Using a language different to the current system locale setting . . . . . . . . . . 36 Implementing a non-default language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Web Client Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

iv

Contents Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Windows 2003 Server-related issues . . . . . . . . . . . . . . . . . . . . . . . . 40 General issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

CitectSCADA Web Client

Introduction
TheCitectSCADAWebClientallowsyoutoviewaliveCitectSCADAproject withinaWebbrowser.ItprovideseasyaccesstoCitectSCADARuntimefor LANconnectedusersrequiringread/writeaccesstocurrentproduction information. Forexample,aseniormanagercouldmonitorafacilityandaccesscurrent productioninformationfromanycomputerontheLANwithouttheneedfor extensivedownloadsorsoftwareinstallation. See Also Systemarchitecture TodisplayaliveCitectSCADAprojectinanInternetbrowser,youmustcombine thecontentoftheprojectpagesandthecurrentdatathesepagespresentusing standard,Webbasedcommunicationprotocols.Tounderstandthe communicationarchitecturefortheCitectSCADAWebClient,itseasiestto considertheroleeachofthefollowingcomponentsplayinachievingthis outcome: CitectSCADAWebServerPerformstheserversidefunctionalityofthe system.Aswellasfacilitatingcommunication,itdirectsaclienttothe graphicalandfunctionalcontentofaCitectSCADAprojectandthelocation oftheruntimeservers.ThisinformationisstoredontheWebServerwhena CitectSCADAprojectisconfiguredasadeployment.ACitectSCADA WebServercancontainmultipledeployments. CitectSCADARuntimeServers(includingtheI/OServer,AlarmsServer, TrendsServerandReportServer)Monitorthephysicalproductionfacility andcontainthelivevariabletagdata,alarmsandtrendsthattheWebClient willdisplay. WebClientprovidestheplatformtomergeadeployedprojectspagesand contentwiththerawdatadrawnfromtheruntimeservers.Again,standard Webtechnologiesarerequired,sotheclientusesMicrosoftInternet Explorer. Thefollowingdiagramshowshowthesecomponentsinteract.

System architecture

CitectSCADA Web Client

CitectSCADA Web Client communications architecture.

OncetheWebClienthasconnectedtotheRuntimeservers,steps2and3become anongoingprocess,withtherequiredcontentbeingcalleduponastheuser navigatestheprojectpages. Notethatthisdiagramhasthesystemcomponentssetupondifferent computerspurelyforthesakeofexplainingthecommunicationsmodel.In reality,theflexibilityofthearchitectureallowsthesecomponentstobe distributedinanyrequiredarrangement;theycanevenshareacommon location.

Getting Started
TheCitectSCADAWebClientHelpisdesignedtoguideyouthroughthesteps requiredtosuccessfullysetupaWebClientsystem. Toensureasuccessfulinstallation,firstfamiliarizeyourselfwiththeSystem architecture,andthenworkthroughthefollowingstepsintheorderprovided. Notes WebClientversion6.1cannotrunaCitectSCADAversion6.0project deployment,norcanitcommunicatewiththe6.0versionofthe CitectSCADAruntimeenvironment.Theconversealsoapplies:WebClient version6.0cannotrunaCitectSCADAversion6.1projectdeployment,nor communicatewiththeCitectSCADAversion6.1runtimeenvironment.If youveupgradedtoversion6.1oftheWebClient,youcanstillviewyour legacydeployments(thatis,deploymentscreatedwithversion6.0)by followingtheproceduresdescribedinWebClientUpgradeIssues. ThisdocumentpresumesyouintendtouseMicrosoftsInternetInformation Server(IIS)astheplatformforyourWebServer.Youalsohavetheoptionto usetheApacheTomcatWebServer.Ifyouareunsureaboutwhichtouse, seethetopicChoosingwhichWebServertechnologytouseintheCitectSCADA onlinehelpbeforeyouproceed. 1 SettingupyourWebServerusingMicrosoftIIScoversthehardwareand softwarerequirmentsfortheWebServer,andprovidesinstructionsfor installingandconfiguringtherequiredsoftware. SettingupsecurityusingIISdescribeshowsecurityisimplementedonthe WebServerandthedifferenttypesofclientaccountsused.Italsoexplains howtosetupandmanagetheseaccounts. PreparingaCitectSCADAProjectforDeploymentexplainsthe adjustmentsthatneedtobemadetoaCitectSCADAprojectpriorto deploymentontheWebServer. ConfiguringadeploymentdescribeshowtodeployaprojectontheWeb Server,byidentifyingitssourcelocationandassociatedservers.Italso explainshowtomanageprojectsoncedeployed. ImplementingMultipleLanguageSupportifrequired,thereareseveral languageoptionsyoucanimplementontheWebServerinterface.

Ifyouhaveperformedtheproceduresoutlinedaboveandhaveproblems,see FrequentlyAskedQuestionstohelpresolveissuesyoumightexperience.

Setting up your Web Server using Microsoft IIS

ThistopicdescribeshowtoprepareyourWebServerforcommunicationwith LANconnectedclientsusingMicrosoftInternetInformationServices(IIS)asthe serverplatform. Selecting an appropriate PC BeforedecidingonwhichcomputertouseasyourWebServer,youshould consideryoursystemarchitectureandwhetherornottheWebServerhas appropriateaccesstotheCitectSCADAruntimeserver(s). IftheCitectSCADAWebServerandCitectSCADAruntimeserveraresetupon differentmachines,anditisnotpossibletoestablishatrustrelationshipbetweenthem, thetwomachinesmustbeonthesamedomainsothattheWebservercanaccess thedirectoryontheCitectSCADAserverthatshostingthewebdeployment files.If,conversely,atrustrelationshipcanbeestablishedbetweentheWeb ServerandtheCitectSCADAserver,theycanbeondifferentdomainsaslongas theWebserverhasreadaccesstotheprojectfolderontheCitectSCADAserver. See Also Requirements Installation Whatsbeeninstalled? ThecomputeryoudecidetouseasyourWebServermustmeetthefollowing hardwareandsoftwarerequirements. Hardwarerequirements Minimum:PentiumII500MHz,256MBRAM,25MBHD(free) Recommended:PentiumIV1GHz,512MBRAM,1GBHD(free) Note:MemoryrequirementsdependonhowmanysimultaneousWebClient connectionsareexpected. Softwarerequirements Windows2000Pro,XPPro,2000Server,or2003Server MicrosoftInternetInformationServices(IIS)(Version5orlater) MicrosoftInternetExplorer(Version6.0orlater) NTFSfilesystem Note: ThetargetdrivefortheWebServersoftwaremustuseanNTFSfilesystem, otherwiseyouwonthavefullaccesstotherequiredWindowssecurity settings(thatis,theFolderPropertiesdialogwillnothaveaSecuritytab).If youarecurrentlyusingaFAT/FAT32system,ensureyouconvertthedriveto NTFSbeforeinstallingtheWebServersoftware.

Requirements

6 Bydefault,CitectSCADAusesNetBIOStofacilitatecommunicationsovera network.TousetheWebServer,youmustswitchyoursystemovertoTCP/ IP.Fordetails,seeUsingTCP/IPfornetworkcommunicationsinthe CitectSCADAonlinehelp. See Also Installation InstallingtheCitectSCADAWebServeronanIISbasedInternetserverinvolves: InstallingCitectSCADAWebServer InstallingInternetInformationServices(IIS) InstallingCitectSCADAWebServer TheWebServersoftwareisinstalledofftheCitectSCADAInstallationCD1. 1 2 3 4 LaunchtheCitectSCADAinstaller(CD1)onthehostcomputer. SelectWebServerforIISfromtheinstallationoptionspanel.(SeeInstalling InternetInformationServices(IIS)belowifanerrormessageappears.) Selectthedestinationfolderfortheinstallation.Bydefault,thisis C:\Program Files\Citect\CitectSCADA\WebServer. TheinstallerallowsyoutochooseaCompleteorCustominstallation. ChooseCustomifyouwanttoinstallspecificcomponentsoftheWebServer system,forexample,justtheWebClientcomponent. ClickInstalltoruntheinstallation.

Installation

InstallingInternetInformationServices(IIS) IfyouselectWebServerforIISfromtheinstallationoptionspanel,theinstaller automaticallydeterminesifIISisinstalled.Ifthisisnotthecase,thefollowing errormessagewillappear:

Ifthismessageappears,youmustinstallIISasaWindowsComponent. 1 2 3 4 LaunchtheWindowsControlPanel(Start|ControlPanel). SelectAddOrRemovePrograms. SelecttheAdd/RemoveWindowsComponentsoption.TheWindows ComponentsWizardappears. LocateInternetInformationServices(IIS)inthelistofcomponents,and makesuretheboxnexttoitischecked.

7 5 See Also ClickNext,thenclickFinish.

YourcomputerisreadytoinstallCitectSCADAWebServerforIIS. Whatsbeeninstalled? OnceyouveinstalledCitectSCADAWebServerforIIS,youwillfindthe followingdirectoriesinthespecifieddestinationfolder.

Whats been installed?

TheWebServerdirectoryprimarilyhoststheadministrativepagesthatare displayedbyaWebServer. Thecgibinandimagesdirectoriescontainthecontentrequiredtodisplay thesepages. Theclientfoldercontainstheclientcomponents(.cabfiles)thatare deliveredtoaremotecomputertorunadeployment.Anysubdirectories includesthecomponentsassociatedwithaparticularrelease(inthiscase, Version6.00). TheDeployfolderincludesthefilesassociatedwithanydeployments (CitectSCADAprojects)configuredontheWebServer. The#DisplayClientfolder(locatedintheDeployfolder)playsakeyrolein theWebServersecurity,asthepermissionsdefinedforthisfolderdetermine theaccessrightsforeachuser. Thelocalesfoldercontainsthefilesrequiredtosupportdifferentlanguages fortheclientinterface.SeealsoImplementingMultipleLanguageSupport. Note:IfyoureupgradingyourversionoftheWebClienttoversion6.1,your installationlooksalittledifferent,sinceyoullalsonowhavea601folderinyour clientfolder.Fordetails,seeWebClientUpgradeIssues.

8 The IIS virtual directory TheinstallationprocessalsoaddsavirtualdirectorycalledCitectSCADAto WindowsIIS(InternetInformationServices).Thisvirtualdirectoryestablishes theWebServerasavaliddestinationforclientapplications.However,italso playsanimportantroleinmanagingwhichusershaveaccesstothesite. YoucanviewevidenceofthisvirtualdirectoryintheIISmanagementconsole, whichislaunchedbyselectingInternetInformationServices(orInternet ServicesManageronWindows2000)fromWindowsAdministrationTools menu.TheCitectSCADAvirtualdirectoryshouldappearunderthelistof defaultwebsites.

YoucanviewthepropertiesforthedirectorybyselectingPropertiesfromthe rightclickmenu. TheVirtualDirectoryinheritsallsecuritysettingsfromthecomputersdefault website,withthefollowingexceptions: DirectoryBrowsingisenabled ScriptSourceAccessisdisabled Thedefaultdocumentissettodefault.htmonly Anonymousaccessisdisabled IntegratedAuthenticationisdisabled BasicAuthenticationisenabled Thesesecuritysettings,includingintegratedauthentication,anonymousaccess andSSLEncryption,canbecustomizedbythelocaladministrator.However, properconfigurationrequiresexperiencewithIISandanunderstandingofthe implicationsofadjustingitssettings.

9 See Also SettingupsecurityusingIIS

10

Security
SecurityontheWebServerisbasedontheimplementationofuseraccounts. InthecaseofanIISbasedWebserver,securityistightlyintegratedwith Windowsuserauthentication.WithanApacheTomcatWebServer,theaccess rightsforeachusertypeisdefinedthroughthecreationofroles. BothsystemssupportthesameuseraccounttypesonaWebClient. Web Client user account types TheWebClienthasthreetypesofuseraccount.
Client type Administrator Display Client Manager Client Description User is permitted to remotely view, add, update and delete deployments. User can view project pages and make adjustments to writable values. User can only view the project pages.

TheWebServerteststheaccessrightsforeachuserwhentheyloginandthen displaysorhidestheappropriatebuttonsonthehomepageaccordingly. Note:AlthoughtheWebClientsecurityarchitecturecontrolsaccesstoyour projectsontheWebServer,notethattheCitectSCADAsystemsecurity (privilege/areasettings)stillmanagesprotectionofthecontrolsystem, maintainingaprimarylevelofsecurity.

12

Setting up security using IIS

SettingupsecurityonanIISbasedWebServerprimarilyinvolvescreatingthree Windowsusergroups,eachrepresentingoneoftheWebClientuseraccount types.Individualuserscanthenbeassignedtotherelevantusergroup,and automaticallyinheritappropriateaccessrightsbasedontheWindowssecurity settingsdefinedforthegroup. Client type access rights Thefollowingtabledefinestheaccessrightsthateachtypeofuserhastothe WebServersinstalleddirectories,asdefinedbythepropertiesforeach. Inthetable,readmeansRead&Execute,ListFolderContentsandReaduser permissionsareallowed;readandwritemeansFullControlisallowed,and accessdeniedmeansFullControlisdenied.
Installed directory WebServer WebServer \ cgi-bin WebServer \ client WebServer \ deploy WebServer \ deploy \ #DisplayClient WebServer \ images ADMINISTRATOR read read read read and write read read DISPLAY read read read read read read MANAGER read read read read access denied read

Forexample,anadministratorclientneedstobeabletoreadalltheinstalled folderstofullyaccessthecomponentsofthehomepage.Additionally,theyneed writeaccesstotheDeploysubdirectorytocreatenewdeployments. Bycomparison,amanagerclientmustbedeniedaccesstothe#DisplayClient foldertopreventtheabilitytowritebacktoaCitectSCADAproject. Therefore,whensettingupsecurityontheWebServer,youneedtomakesure thatyouruseraccountsalignappropriatelywiththepermissionsoutlinedinthe tableabove. ToimplementtheWebServerssecuritystrategysuccessfully,youshouldfollow theprocedurebelowthatwillprotectyoursystemandsimplifymanagingclient accounts. Settingupsecurityinvolvesthefollowingsteps: 1 2 3 4 Configuringclientaccountusergroups PreparingtheWebServerfolder Settingupaccessrightsforclientaccounts TestingtheWebServersecuritysettings

TheongoingmanagementofyourWebServersecurityshouldtheninvolve addingandremovingindividualaccountsasrequired.

14 Notes TheinstallationandinitialconfigurationoftheWebServermustbe performedbyaWindowsuserwithlocaladministratorpermissions;thatis, theymustbeabletoaddandeditWindowsUseraccounts,andmodifyfile/ folderprotection.ThiscapabilityisrequiredtosetupWebClientuser accountsandmanagesecuritysettings. Itisimportanttounderstandthedistinctionbetweentheroleofthe WindowsLocalAdministrator,andtheWebClientsAdministratorusers: WindowsAdministratorconfiguressecurityontheWebServerand setsupclientaccounts. WebClientAdministratoranendusercapableofmodifyingand managingprojectsdeployedontheWebServer. ThetworolesparallelaCitectconfigurationengineerandaruntime operator.

Configuring client account user groups

CreatingausergroupassociatedwitheachtypeofWebClientaccountonyour WebServerallowsyoutomanagesecuritywithouthavingtodealwith individualusers.Userscanbeaddedtoagroupandinheritthesecuritystatus setforthegroup. TocreateaUserGroupontheWebServercomputer,youmustloginto WindowswithLocalAdministratorpermissions. Tocreatetheclientaccountusergroups: 1 GototheComputerManagementtool,whichislaunchedfromtheWin dowsStartmenuorControlPanel.

15 2 LocateLocalUsersandGroupsinthedirectorytree.Thisiswheretheusers andgroupsforthelocalmachineareconfiguredandmanaged.

3 4 5

RightclicktheGroupsfolderandselectNewGroup.ThiscallsuptheNew Groupdialog. IntheGroupName,typeWebClientAdministrator(orsomething appropriate),anddescribethegroupspurpose. ClickCreate. Thegroupyouhavejustcreatedshouldappearinthelistofgroups presentedintheComputerManagementconsole.

6 7

Repeatsteps3to5tocreateDisplayClientandManagerClientusergroups. Toeventuallytestyoursecuritysettings,youshouldaddatleastoneuserto eachgroup.

YouarenowreadytostartPreparingtheWebServerfolder.

Preparing the Web Server folder

YouneedtoadjustthesecuritysettingsfortheWebServerfolderanditssub directories,asthiswilldeterminetheaccessgrantedtoeachtypeofclient account. TopreparetheWebServerfolder: 1 LogontotheWebServercomputerasaWindowsAdministrator.

16 2 LaunchWindowsExplorerandbrowsetotheWebServerfolder. TheWebServerfolderislocatedintheinstallationdirectory.Bydefault,this isC:\Program Files\Citect\CitectSCADA\WebServer. 3 4 RightclicktheWebServerfolderandselectProperties. FromthePropertiesdialog,selecttheSecuritytabtodisplaytheusers currentlyconfiguredforthefolder.

Therewillprobablybeseveralgroupsalreadydefinedinthisfolder.Thetwo youneedtopayattentiontoaretheAdministratorsgroupandthe Everyonegroup. TheAdministratorsgrouprepresentsalltheWindowsusersrecognized bytheWebServercomputerwithLocalAdministratorrights.This grouphasFullControlpermissionsonthefolder,facilitatingtheability toadjusttheWebServersecuritysettings.Ifthisisthecase,thereshould benoreasontomodifythisgroup.

17 TheEveryonegrouprepresentsallotherusersrecognizedbythelocal machine.YoushouldgivethisgroupreadaccesstotheWebServer folder;thatis,allowRead&Execute,ListFoldersContents,andRead permissions.ThisprovideslocalusersontheWebServermachinewith theequivalentofDisplayClientpermissions. IfthereareothergroupsdefinedfortheWebServerfolder,forexample PowerUsers,youmightwanttoremovethesegroupstosimplify managingyourWebClientaccounts. 6 ToaddthethreegroupsyouhavecreatedtotheWebServerfolder,gotothe SecuritytaboftheWebServerfolderproperties,andselectAdd.Usingthe dialogthatappears,locatetheusergroupsyoucreatedonthelocalmachine. TheAdvancedbuttonallowsyoutosearchfordefinedgroups.

Note:TheSelectUsersorGroupsdialogappearsdifferentlyinWindows 2000totheWindowsXPversionpicturedabove.InWindows2000,youcan simplyselectauserorgroupfromthelistofthoseavailableandclickAdd. 7 Confirmthesecuritysettingsforthethreenewlycreatedgroups.Each shouldhavethesamereadaccessastheEveryonegroup:Read&Execute, ListFoldersContents,andReadpermissions. EnsureallthesubdirectoriesinheritthepermissionssetfortheWebServer folder.Thisensuresconsistentsecuritysettingsacrossalltheinstalled directories. Todothis,clickthefolderpropertiesAdvancedbutton,andselectReplace permissionentriesonallchildobjects,thenclickOK. Note:WithWindows2000,thisoptionreadsResetpermissionsonallchild objectsandenablepropagation.

18 ASecuritydialogmightappearwarningthatthiswillremoveexplicitly definedpermissionsonchildobjects.ClickYestocontinue. TheWebServersinstalleddirectoriesshouldnowhaveconsistentsecurity settingsforalltherequiredusergroups. Next,youmustmodifythesecuritysettingfortwospecificfolderstoimplement therequiredpermissionsforthedifferentclientaccounttypes. See Also Settingupaccessrightsforclientaccounts. ThethreeclientaccounttypessupportedbytheWebClientaredefinedbythe securitysettingsforeachwithintheinstalleddirectoriesontheWebServer machine. Thedifferences,outlinedinthetableinClienttypeaccessrights,requirespecific securitysettingsfortheAdministratorClientandManagerClienttypes.An AdministratorneedswriteaccesstotheDeploysubdirectory,andtheManager needstobedeniedaccesstothe#DisplayClientsubdirectory. TheDisplayClientgroupneedsnoadditionalconfiguration,asitusesthe settingsoutlinedinPreparingtheWebServerfolder. ToconfiguresecuritysettingfortheAdministratorClientgroup: TheAdministratorClientrequiresfullaccesstotheDeploysubdirectoryto enablethecreationandmodificationofdeployments. 1 2 3 4 LocatetheDeploysubdirectoryintheWebServerfolder.Bydefault,thisis C:\Program Files\Citect\CitectSCADA\WebServer\Deploy. RightclickthefolderandselectPropertiestodisplaytheDeployfolder properties. ClicktheSecuritytabandlocatetheWebClientAdministratorgroupyou createdinthelistofusersandgroups. EditthepermissionssetforthegrouptoAllowFullControl.

Setting up access rights for client accounts

ToconfigurethesecuritysettingsfortheManagerClientgroup: TheManagerClientmustbedeniedaccesstothe#DisplayClientsubdirectory topreventwritechangesbeingmadetoadeployedCitectSCADAproject. 1 Locatethe#DisplayClientsubdirectoryintheWebServerfolder.Bydefault, thisisC:\Program Files\Citect\CitectSCADA\WebServer\Deploy\#DisplayClient. RightclickthefolderandselectPropertiestodisplaythefolderproperties. ClicktheSecuritytabandlocatetheWebClientManagergroupyoucreated inthelistofusersandgroups.

2 3

19 4 Editthepermissionssetforthegroup,whichyoushouldchangetoDeny FullControl. ASecuritydialogappearswarningDenyentriestakepriorityoverall Allowentries.ClickYestocontinue. YouhavenowconfiguredthesecuritysettingsfortheclientgroupsontheWeb Server.Next,youshouldcommenceTestingtheWebServersecuritysettings. See Also Deletingauseraccount YoucandenyauseraccesstotheWebServerbyremovingthemfromthegroups thathavepermissionssetfortheWebServerfolder. However,ifsecurityisaconcern,youshoulddenytheuseraccesstotheWeb Serverfolderbeforeyoudeletethem.Thisavoidsaknownproblemwherethe operatingsystemdoesntimmediatelyacknowledgethatauseraccounthasbeen deleted,creatingashortperiodwhereadeletedusercanstilllogon. Tosecurelydeleteauseraccount 1 2 3 AddtheuserasanindividualtotheWebServerfolder. SettheiraccessrightstoDenyFullControl. RemovetheuserfromthegroupsthathavepermissionssetfortheWeb Serverfolder.

Deleting a user account

Withallaccessdenied,theycannotdoanythingeveniftheygainaccess.

Testing the Web Server security settings

TotestthesecuritysettingsforyourWebServerclientgroups: 1 2 3 LaunchInternetExplorerontheWebServermachine. CalluptheWebClienthomepagebytypinginthefollowingaddress:

http://localhost/CitectSCADA

Tryloggingintothehomepageusingausernameandpasswordthatsbeen addedtotheAdministratorClientgroup. Ifsuccessful,theSystemMessagesdialogshouldreadLOGINADMIN Admin(UserName)loggedin. IfthemessagestartswithLOGINDC(forDisplayClient)orLOGINMC(for ManagerClient),thereisaproblemwithyourconfiguration.Confirmthat youareusingthecorrectusernameforthegroupyouaretesting.Ifthe problemstilloccurs,revisittheprocessinSettingupsecurityusingIISto ensureanerrorhasntbeenmade.

RepeatthisprocesswithaDisplayClientandManagerClientuser.

OnceyouhaveconfirmedthatsecurityiscorrectlysetupontheWebServer,you cannowprepareyourCitectSCADAprojectfordeployment.Formore informationseeConfiguringadeployment.

20

Logging on to the Web Server

Aftersettingupyourclientaccounts,youmustprovidethefollowingdetailsto eachendusersotheycanlogontotheWebServer: AddressoftheWebServer ThisistheaddressusershavetotypeintotheirWebbrowsertogainaccess totheCitectSCADAWebServer. Iftheyaredoingthisremotely,theaddressis:

http://<machine name>/CitectSCADA

or
http://<machine IP address>/CitectSCADA

IftheyareloggingontotheWebServercomputer,theaddressis:
http://localhost/CitectSCADA

Usernameandpassword OncethebrowserhasarrivedattheWebServer,theenduserisaskedto provideausernameandpassword.Typically,youjustneedtotellthemthat theirWindowsusernameandpasswordwillprovideappropriateaccess.If youhadtocreateanewuserprofileforsomeone,youmustprovidethem withthedetails.

Preparing a CitectSCADA Project for Deployment

BeforedeployingaprojectonaWebServer,youwillprobablyneedtoadjustthe CitectSCADAconfigurationenvironmenttoensureitisreadyforWebbased delivery.Youneedtoconsiderthefollowingissues: FunctionalitylimitationsoftheWebClientplatform Preparingaprojectsuserfilesfordelivery RunningtheWebDeploymentPreparationtool Note:Bydefault,CitectSCADAusesNetBIOStofacilitatecommunicationsover anetwork.TousetheWebClient,youmustswitchyoursystemovertoTCP/IP byadjustingtwospecific[LAN]parametersandmappingyourserverTCP/IP addresses.Forexample:
[LAN] tcpip=1 netbios=0 [DNS] <SCADA I/O server name>=<IP address> <alarm server name>Alarm=<IP address> <report server name>Report=<IP address> <trend server name>Trend=<IP address>

Note:Iftheprojectissetupforredundancy,bothserversmustappearinthe [DNS]sectionofthecitect.inifile. RefertothetopicUsingTCP/IPfornetworkcommunicationsinthe CitectSCADAUserGuidefordetailsonsettingyourDNSparameters.

Functionality limitations of the Web Client platform

DuetothearchitecturerequiredtosupportWebbasedexecutionof CitectSCADAprojects,theWebClientcannotofferthefullfunctionalityofa standardCitectSCADAsystem. YoushouldconsiderthefollowinglistofunsupportedfeaturesandCicode functionstoassessifthiswillbedetrimentaltotheperformanceofyourproject. Someadjustmentsmightberequired. Feature limitations Thefollowingfeaturesarenotsupported: CicodeDebugger. Remoteshutdown. FuzzyLogic. Clusterfunctionality. Kernelwindows.

22 KeyboardshortcutsthatclashwithInternetExplorerskeyboardshortcuts. WebClientisunabletoactasaCitectSCADAServer. PagesbasedonthedefaultMenuPagetemplatewillonlyshowbuttonsfor pagespreviouslyvisited. ThePageSelectbuttononthedefaultNormaltemplateonlylistspages previouslyvisited. TheCSV_IncludeprojectsUpdatePageListmenuitemwillnotwork. Note:IfyourprojectisbasedontheCSV_Includetemplate,youmustcreate acustomizedmenutoaccesspagesfromthemenubar. Cicode Function Limitations SeveralCicodefunctionsareunavailablewiththeWebClient,orlimitedintheir capabilities:
Cluster Functions DebugBreak DelayShutdown FTP Functions Fuzzy Logic Functions KerCmd ProjectRestartGet ProjectRestartSet ProjectSet Shutdown ShutdownForm SwitchConfig TraceMsg UserCreate UserCreateForm UserDelete UserEditForm UserPassword UserPasswordForm GetWinTitle WinFree WinMode WinMove WinPos WinSize WinTitle Cluster functionality not supported Cicode debugger not supported Programmatic Shutdown not supported All FTP functions are not supported Removed from control due to size Kernel windows not supported Programmatic Shutdown not supported Configuration environment not available Kernel windows not supported Changes to user profiles must be made on the machine where the project is compiled and auto-deployed. Windows other than the main window only

23
WndShow WndViewer Invokes multimedia applications Feature not supported

See Also

Preparingaprojectsuserfilesfordelivery IfthecontentofyourCitectSCADAprojectincorporatesusercreatedfiles,such asDBFfiles,HTMLfiles,orCSVfiles,youmustmanuallyplacetheseintoa specialzipfilecalledMisc.zipfordeliverytotheWebServer.Similarly,ifa projectcontainsActiveXobjects,thesealsomustbeincludedinazipfilecalled ActiveX.zip. Toprepareanyusercreatedfilesfordeployment: 1 Identifyalltheusercreatedfilesthatareassociatedwiththeprojectyou wanttodeploy. ThesefilescouldincludeCSVorDBFfilesassociatedwithtablespresented onprojectpages,orHTMLcontent. 2 3 Useacompressiontooltozipthesefilesupintoasinglefilecalled Misc.zip. PlaceMisc.zipinthemainfolderfortheproject.Forexample,inthecaseof theCSV_Exampleproject,thiswouldbe:
C:\Program Files\Citect\CitectSCADA\User\CSV_Example

Preparing a projects user files for delivery

Note:IfyourprojecthasincludedprojectsthatuseActiveXobjects,ensure thesearealsozippedupinanActivex.zipfileintheincludedprojects directory. ThefilesarenowreadyfordeploymentontheWebServer. ToprepareanyincludedActiveXobjectsfordeployment: 1 2 3 IdentifyalltheActiveXobjectsassociatedwiththeprojectyouwantto deploy. Useacompressiontooltozipthesefilesupintoasinglefilecalled ActiveX.zip. PlaceActiveX.zipinthemainfolderfortheproject.Forexample,inthe caseoftheCSV_Includeproject,thiswouldbe:
C:\Program Files\Citect\CitectSCADA\User\CSV_Include

Note:IfanActiveXobjecthasanassociateddatasource,ensurethedatasource canbelocatedbythecomputerhostingtheWebClient.SeethetopicManaging associateddatasourcesunderthesectiononActiveXobjectsinthe CitectSCADAUserGuideHelp. See Also RunningtheWebDeploymentPreparationtool

24

Running the Web Deployment Preparation tool

Thefinalstepinpreparingaprojectfordeploymentinvolvesrunningitthrough theWebDeploymentPreparationtool.Thistakesafreshlycompiledprojectand createstherequiredfilesanddirectoriesforWebbaseddelivery. TorunaprojectthroughtheWebDeploymentPreparationtool: 1 Ensuretheprojectyouwanttodeployhasallitsassociateduserfilesand ActiveXobjectszippedupfordelivery(seePreparingaprojectsuserfiles fordelivery). LocatetheprojectyouwanttodeployinCitectExploreranddoafresh compile. GototheCitectExplorerToolsmenuandselectWebDeployment Preparation(orclickthefollowingiconontheExplorertoolbar):

2 3

Aprogressindicatorappears.Thesizeoftheprojectsignificantlyaffects howlongthisprocesstakes;alargeprojectwithmanyfilescantakeoverten minutestoprocess,dependingonyourhardware.(Youcanabortthe deploymentpreparationifyouwant.) Whencomplete,adialogappearsstatingthepreparationwassuccessful. ClickOK. TheprojectisnowreadyfordeploymentontheWebServer.Ifyouchangea project,youmustdoafreshcompileandruntheWebDeployment Preparationtoolagain.

Hint:YoucanruntheWebDeploymentPreparationtoolautomaticallywhen youcompileaproject.Todothis,gototheCitectProjectEditorToolsmenuand selectOptions.SelectthePrepareforWebDeploymentoptionandclickOK. Notethatthisincreasesthetimetakenforeachcompile,particularlyforlarge projects.

Configuring a deployment
AdeploymentrepresentstheimplementationofaCitectSCADAprojectonthe WebServer.Itincorporatesthefilesandcomponentsrequiredtodisplaya project,andthenstoresthelocationoftheserverswhereCitectSCADARuntime dataisgenerated. ThedeploymentsconfiguredonaWebServerarelistedontheWebClienthome page,whichisthepagethatappearswhenyouinitiallylogin.Theconfiguration detailsforadeploymentcanbedisplayedbyclickingthesmallplus(+)iconto theleftofthedeploymentname.

Thetypesofactionyoucanimplementforadeploymentdependonthe permissionsgrantedbyyourlogin.Forexample,ifyouloginasaManager Client,youcanonlyviewadeployment.Ifyouareanadministrator,youcan editdeploymentsandcreatenewones. Thefollowinglistdescribesthefunctionalityassociatedwitheachoftheicons presentedonthehomepage.:

Add New Deployment - takes you to the Deployment Configuration page where you can create a new deployment (Administrator Clients only). Help - launches a PDF file explaining how to configure and use the Web Client. Edit Deployment - takes you to the Deployment Configuration page and allows you to edit the selected deployment (Administrator Clients only). Delete Deployment - Deletes the selected deployment (Administrator Clients only).

26
Start Display Client - Displays the selected deployment with Display Client permissions (Display Client and Administrator Client only) Start Manager Client - Displays the selected deployment with Manager Client permissions

Additionally,theSystemMessagespanelprovidesnotificationofeventsthat impactthecurrentstatusoftheWebServer. See Also PreparingaCitectSCADAProjectforDeployment Creatinganewdeployment DeployingaprojectfromwithinCitectSCADA Displayingadeployment Editinganexistingdeployment Updatingadeploymenttoreflectprojectchanges Deletingadeployment ToconfigureadeploymentofaCitectSCADAprojectonaWebServer,youmust loginwithAdministratorClientpermissions.Thiswillprovideyouwithaccess tothefullfunctionalityofthehomepage. Toaddanewdeployment 1 ClicktheAddNewDeploymenticon.

Creating a new deployment

ThistakesyoutotheDeploymentConfigurationpage.

TypeinanameintheDeploymenttextbox,andincludeaDescriptionif required.Adeploymentnamecannotcontainanyofthefollowing characters:\ * ? | . , / " ' : ; < > # & Note:IfyouveupgradedyourversionoftheWebClient,youcanstillview yourlegacydeploymentsthatyoucreatedusingversion6.0oftheWeb Client.Fordetails,seeWebClientUpgradeIssues.

27 3 IdentifythesourceoftheCitectSCADAprojectscontentintheProjectPath field.Youneedtoconsiderthelocationoftheprojectfilesinrelationtothe WebServer,asitwilldeterminehowyoudefinetheprojectpath. IftheprojectislocatedlocallyontheWebServer,youcanuseanormalpath address.ThepathmustpointdirectlytotheprojectwithintheCitectSCADA Userdirectory.Forexample,thelocationoftheExampleprojectwouldbe:

C:\Program Files\Citect\CitectSCADA\User\Example

Note:IfyouareremotelyadministeringtheWebServerandusealocalpath address,makesurethepathrepresentsthelocationoftheprojectontheWeb Servercomputer,notthecomputeryouarecurrentlyusing. IftheprojectisnotlocatedontheWebServer,youneedtouseaUNC addressthatidentifiesthehostnetworkcomputerandthedirectoryitcanbe foundin.Forexample,

\\ComputerName\Program Files\Citect\CitectSCADA\User\Example

Note:YoumustsharethedirectoryaprojectresidesintoallowtheWeb Serveraccesstoit.Ideally,youshouldcreateasharefromthedirectory (calledWebShare,forexample)andthenusethefollowingprojectpath:

\\ComputerName\WebShare

Rememberthatifyouaretryingtoaccesstheprojectdirectoryfroma remotecomputer,alocaladministratorloginwillnotprovideyouwith appropriateaccessonadifferentcomputer.Youshoulduseanetworkuser profilethatwillberecognizedbyothercomputersonthesamedomain. 4 IdentifytheCitectSCADAserversassociatedwiththedeployment.Youcan typeanameintheServerfield(asdefinedinyourCitectSCADAproject), theIPAddressoftheserver,andthePortnumber. Thereare,however,twoscenariosyouneedtoconsiderhere: HavetheIPaddressesfortheprojectserversalreadybeenidentifiedin the[DNS]sectionofthecitect.inifile?Ifyouhavealreadydonethis whensettingupTCP/IP,youdontneedtoidentifyanyserversastheIP addressescanberetrievedfromthecitect.inifile.SeeUsingTCP/IP fornetworkcommunicationsintheCitectSCADAUserGuideHelpfor detailsonusing[DNS]parameters. Note:IfyouincludedanIPaddressforaserverwhenconfiguringyour deployment,ittakesprecedenceoveradifferentaddressidentifiedfor thesameserverinthe[DNS]sectionofyourcitect.inifile. AreyourCitectSCADAserversprotectedbehindafirewall?Ifso,with eachservernameyoumustprovidethepublicaddressandportnumber foryourfirewall.Thefirewallshouldbeconfiguredtohandlethe mappingtoprivateIPaddressandportnumberforeachCitectserver.

28 5 AddanyadditionalserverstoyourdeploymentbyclickingAddNew Server,andrepeatingstep4foreachserver.

Typically,aCitectSCADAprojectincorporatesanI/Oserver,alarmsserver, trendsserverandreportserver.Youmustidentifyeachoftheservers associatedwiththeproject. 6 UsetheClientControltextboxtospecifytheuseofaparticularversionof theWebClientcomponentwhenthedeploymentisdisplayed. ThemenulistsallthedifferentversionsoftheWebClientcontrolcurrently installedontheWebServer.Typically,youshouldchoosetheversionofthe controlthatmatchestheversionofCitectSCADAyourprojectwascompiled on. 7 ClickApplyChanges.(Thisisimportant,asyoullloseyourchangesifyou jumpstraightbacktothehomepage.

Alltheprojectfilesareretrievedfromthepathindicated,andcopiedtothe WebServerreadyforaccessbytheWebClients. Oncecomplete,informationaboutthesizeoftheprojectappearsintheFile PathsbannerabovetheProjectPathfield.Thenumbertotheleftindicates howmanyfilesareincludedintheproject;thenumbertotherightindicates thetotalsizeoftheproject. Thedeploymentissaved.WhenyoureturntotheWebClienthomepage,by clickingthehomeicon,yournewdeploymentislisted. See Also DeployingaprojectfromwithinCitectSCADA Displayingadeployment TheWebClientarchitectureletsyoudeployaprojectfromwithinthe CitectSCADAconfigurationenvironment,avoidingtheneedtousetheWeb Clientinterfacetosetupasystem. ThisprocessrequiresyoutoadjusttwoparametersintheCitect.inifile,
[WebServer]WebClientCaband[WebServer]DeployRoot.Theseparameters

Deploying a project from within CitectSCADA

identifytheclientcomponentusedwiththeprojectandthelocationofthe deploymentrootdirectory.Whentheprojectiscompiledandpreparedfor deployment,itisplaceddirectlyontheWebServer.

29 Notes IfyouveupgradedyourWebClienttoversion6.1,youcanstillviewyour legacydeployments.Fordetails,seeWebClientUpgradeIssues. Whenimplementingthisoption,payattentiontoyourcitect.inifile configuration,asanyerrorswiththeseparametersaredifficulttodiagnose. Toavoidinputerrors,usetheWebDeploymentToolontheCitectExplorer toolbarwiththeWebServersWebDeploymentGUI. IftheprojectnamecontainsnonEnglishcharacters,deployingfromwithin CitectSCADAmightfail.Underthesecircumstances,usetheWebServer interfacetocreatethedeployment. TodeployaprojectfromwithinCitectSCADA: 1 ConfirmthatyourCitectSCADAsystemisconfiguredtouseTCP/IPby adjustingthefollowingcitect.iniparameters:
[LAN] tcpip=1 netbios=0

ConfirmthatyourCitectSCADAserversarecorrectlymappedtotheirIP addresseswithinthe[DNS]sectionofthecitect.inifile.(Refertothetopic UsingTCP/IPfornetworkcommunicationsintheCitectSCADAUserGuide formoreinformation.) Forexample:

[DNS] <SCADA I/O server name>=<IP address> <alarm server name>Alarm=<IP address> <report server name>Report=<IP address> <trend server name>Trend=<IP address>

Note:NetBIOSautomaticallyidentifiesaserversrolebyappendingthe suffixAlarm,TrendorReporttotheendoftheproposedservername whenitisinitiallycreatedbytheComputerSetupWizard.Toidentifya serverforTCP/IP,youmustaddthissuffixyourselfintheDNS identificationsettings. Iftheprojectissetupforredundancy,bothserversmustappearinthe

citect.inifile.

Adjustthe[WebServer]DeployRootand[WebServer]WebClientCab parameterswithinthecitect.inifile. TheDeployRootparameterrepresentsthedirectorywherethedeployment willbelocatedontheWebServer. IfyouhavesetupanIISbasedWebServer,thedefaultlocationwillbethe Deploydirectorywithintheinstalleddirectories.Forexample:

30
[webserver] DeployRoot="C:\Program Files\Citect\CitectSCADA\WebServer\deploy"

IfyouareusinganApacheTomcatWebServer,thiswillbe:
[webserver] DeployRoot="C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\CitectSCADA\deploy"

Note: Whensettingthe[WebServer]DeployRootiniparameter,thepathmust containdeployasthelastsubfoldername,otherwisethedeployment willfail. UseamappeddriveinsteadofaUNCaddressifdeployingtoanetwork destinationfromaWindows2000system.Thisavoidspotential deploymentfailures.Donotmapadrivedirectlytothedeployment location,asthepathmustfinishwithadeploysubfolder. 4 TheWebClientCabparameterrepresentsthedirectorypathandclient componenttousewhenadeploymentisrun,inrelationtotheinstalled Clientdirectory.Forexample:
[webserver] WebClientCab=600/CitectSCADAWebClient_6_0_176.cab

Notetheuseofaforwardslashinthedefinedpath. 5 Compileyourprojectandthenprepareitfordeployment.GototheCitect ExplorerToolsmenuandselectWebDeploymentPreparationorselectthe followingiconontheExplorertoolbar.

Note:YoucanruntheWebDeploymentPreparationprocessautomatically whenyoucompileaproject.Todothis,gototheCitectProjectEditorTools menuandchooseOptions.SelectthePrepareforWebDeploymentoption andclickOK.Beaware,however,thatthismightincreasethetimerequired foraprojecttocompile. YourprojectshouldnowappearasadeploymentwithintheWebClienthome pagenexttimeyoulogin. See Also Displayingadeployment Whenyoudisplayadeployment,itdownloadstherequiredWebClient componentfilefromtheWebServer,enablingyoutoruntheassociated CitectSCADAprojectinyourWebbrowser.

Displaying a deployment

31 Todisplayadeployment: 1 2 Locatethedeploymentyouwanttodisplayinthelistofavailabledeploy ments. Clicktherelevanticon(StartDisplayClientorStartManagerClient)to displaythedeployment.

Thedisplayoptionsavailabletoyoudependonyourloginpermissions.If youselecttheManagerClienticon(theonewiththegoldlock),youcanonly readthecurrentvaluesfortheCitectSCADAproject. Oncetherequiredprojectfilesandcomponentshavebeendownloaded,the CitectSCADAprojectappears.Youcannownavigatetheprojectpagesas required. Note:Anerrormessagemightappearifthecurrentuserontheclientmachine doesnothaveWindowsadministratorrightswhenaneworupdated componentfile(.cabfile)isdownloaded.EnsurethecurrentWindowsuserhas administratorrightsifanewdeploymentisrunoranupdated.cabfileneedsto bedownloaded. See Also Editinganexistingdeployment Ifrequired,youcaneditthesettingsforadeployment.Forexample,youcan changethenameofthedeploymentorspecifyanewaddressforaruntime server. Toeditadeploymentssettings,youmustbeloggedinasanAdministrator Client. Toeditanexistingdeployment 1 2 Selectthedeploymentyouwanttoeditinthelistofavailabledeployments. ClicktheEditDeploymenticon.

Editing an existing deployment

ThistakesyoutotheDeploymentConfigurationpage. Changethefieldsasrequired.Forfielddescriptions,seeCreatinganew deployment. Note:IfyougiveadeploymentanewName,itisduplicatedinsteadbeing updatedandoverwritten.Thisallowsyoutoeasilycopyanexisting deployment;however,youmustdeletetheoriginaldeploymentwiththeold nameifitsnolongerrequired.

32 3 ClickApplyChanges.(Thisisimportant,asyoullloseyourchangesifyou jumpstraightbacktothehomepage.)

TheWebServerretrievesafreshsetofpagesandcomponentsforthe CitectSCADAproject,whichwillincludeanyrecentchanges. See Also Updatingadeploymenttoreflectprojectchanges IfyouchangeasourceCitectSCADAproject,youmustupdateitsassociated deploymenttoensurethechangesarereflectedontheWebServer. Updatingadeploymentensuresthelatestprojectpagesandcomponentsare retrievedbytheWebServerandavailablefordistribution.Thisisimportantas discrepanciesmightoccurbetweentheprojectpagesandthedatabeingpulled fromtheruntimeserversifthecontentisnotuptodate. Toupdateadeployment: 1 Ensurethattheprojectyouwanttoupdatehasbeencompiledandpro cessedwithintheCitectSCADAbytheWebDeploymentPreparationtool. SeeRunningtheWebDeploymentPreparationtool. Selectthedeploymentyouwanttoupdate. ClicktheEditDeploymenticon.

Updating a deployment to reflect project changes

2 3

ThistakesyoutotheDeploymentConfigurationpage. 4 ClickApplyChanges.

TheWebServerretrievesafreshsetofpagesandcomponentsforthe CitectSCADAproject,whichwillincludeanyrecentchanges. See Also Editinganexistingdeployment Deletingadeployment TodeleteadeploymentfromaWebServer,youmustloginasanAdministrator Client. TodeleteadeploymentfromtheWebServer: 1 Selectthedeploymentyouwanttodeletefromthelistofavailabledeploy ments.

Deleting a deployment

33 2 ClickDeleteDeployment.

Adialogasksyoutoconfirmthatyouwanttodeletethedeployment.Click OK. See Also Configuringadeployment

34

Implementing Multiple Language Support

TheWebClientdeploymentconfigurationinterfacecanbedisplayedusing languagesotherthanEnglish.Thefollowinglanguagesaresupportedby default: French German Spanish Chinese Japanese Korean Youcanalsoimplementotherlanguagesbytranslatingtheresourcemessagefile thatdefinesthetextdisplayed.Inthecaseofthelanguageslistedabove,thisfile hasalreadybeentranslatedwithaversionforeachlanguagestoredinthe installedlocalesfolder. See Also Howdefaultlanguagesareimplemented Usingalanguagedifferenttothecurrentsystemlocalesetting Implementinganondefaultlanguage WhenyouconnectaclientcomputertotheWebServer,thescriptontheweb pageautomaticallydetectsthelanguagecodecurrentlydefinedasthedefault forthebrowser.Thiscodeisdrawnfromthesystemlocalesettingdefinedin ControlPanel|RegionalOptionsontheclientmachine. Oncethebrowserslanguagecodehasbeendetermined,thescriptattemptsto matchitwiththoseavailableontheWebServer.Ifamatchismade,the associatedlanguageisautomaticallyusedfortheWebClientdeployment configurationinterface.Ifamatchcannotbemade,itdefaultstoEnglish. Forexample,ifyourWindowsLocalesettingisChinese(PRC),thelanguage codesetforyourbrowserwouldbezhcn.Thisiscomparedtothecurrentlist oflanguagecodesontheWebServer,whichbydefaultisthefollowing:
Language English French German Spanish Simplified Chinese Japanese Korean Windows Language Code en fr de es zh ja ko

How default languages are implemented

36 Havingfailedtomatchzhcn,thescripttriestoloadSimplifiedChinese language,zh,asamatch.TheinterfacewillautomaticallydisplayinChinese. See Also Usingalanguagedifferenttothecurrentsystemlocalesetting YoucandisplaythecontentoftheWebClientsdeploymentconfigurationpages usingalanguagethatsdifferenttothecurrentsystemlocalesettingforthe computer.Todothis,useaURLquerystringintheaddressfieldofyour browser. Toswitchtoalanguageotherthanthedefault: 1 Decidewhichlanguageyouwanttouseanddetermineitsassociatedlan guagecode.(SeeHowdefaultlanguagesareimplementedforalistofthe codesforthedefaultlanguagessupportedbytheWebServer). Forexample,ifyouwanttouseChinese,thecoderequiredwouldbezh. Note:Ifthelanguageyouwanttouseisnotoneofthesupportedlanguages, youmustcreateandtranslateyourownmessagefile.SeeImplementinga nondefaultlanguage. 2 UseaURLquerytoindicatethelanguageyouwanttousefortheWebClient deploymentpages.Forexample,iftheaddressfieldonyourbrowser currentlyreads:
http://localhost/CitectSCADA

Using a language different to the current system locale setting

adda/?lang="querytotheendoftheaddress.Forexample,Chinese wouldbe:
http://localhost/CitectSCADA/?lang=zh

Note:Ifyouuseacodethatrepresentsaregionalvariationofoneofthe defaultlanguagesandthatspecificcodecannotbematched,theWebServer canonlyimplementtheavailabledefaultversionofthelanguage.For example,usingthelanguagecodeforChinese(PRC),zhcn,resultsinthe SimplifiedChinesebeingused,zh. YourWebbrowsernowdisplaystheWebClientsdeploymentconfiguration pagesusingtheappropriatelanguage. See Also Implementinganondefaultlanguage IfyouneedtousealanguageontheWebClientsdeploymentconfiguration interfaceotherthanoneofthedefaultlanguagessupportedbytheWebserver, youcanimplementyourowntranslationofthemessagesfilethatdefinesthe textthatappears.

Implementing a nondefault language

37 Todisplayalanguageotherthanthosesupportedbydefault: 1 Usingatexteditorthatsupportsthelanguageyouwanttoedit,openoneof theexistingmessagefileslocatedintheWebServerslocalesdirectory;the defaultpathis:

C:\Program Files\Citect\CitectSCADA\Web Server\locales

Thefileyouopenshouldincludethelanguagethatwillbeeasiestto translate.Thelanguagecodeatthestartofeachfilenamecanbeusedto identifythelanguageeachfilerepresents;forexample,theEnglishlanguage fileiscalledenmsg.xml. 2 Savethefilebacktothelocalesdirectory,usingtheappropriatelanguage codeinthename. Tonamethefilecorrectly,checkthelistofWindowsLanguageCodesforthe appropriatecode.Thiswillallowyourtranslatedresourcefile(XXmsg.xml) tobeautomaticallyloadedwhentheWebClienthomepageislaunched, provideditmatchesthecurrentsystemlocalesetting. Forexample,toimplementHebrewontheWebClientsconfigurationpages, youwouldnameyourfilehemsg.xml.TousetheTaiwanesevariationof Chinese,youwouldcallthefilezhtwmsg.xml. 3 Nowchangethefilecontent.Firstly,setthecorrectencodingformat. Theencodingformatisdefinedinthetoplineofthefile,whichappearsas follows:
<?xml version="1.0" encoding="iso-8859-1" ?>

IfthelanguageusesEnglishcharacters,theformatyouwoulduseisANSI, whichisdefinedasiso88591(seeexampleabove). IfthelanguageusesnonEnglishcharacters,youwoulduseUnicode,which isdefinedasUTF8(seeexamplebelow).

<?xml version="1.0" encoding="UTF-8" ?>

NowtranslatethetextthatappearsontheWebClientinterface. Thecontentthatneedstobetranslatedisdividedacrosstwosectionswithin thefile:labelsandmessages.Thelabelssectionincludesthecontent usedtodescribeandidentifytheelementsoftheinterface;themessages sectionincludesthenotificationsthatappearinthesystemmessagespanel. Totranslatethesesections,alterthetextbetweentheenclosingXMLtags.Do notalterthetagsthemselves. Note:Makesureyoumaintainany%characters,astheseareusedto insertsysteminformation. Forexample,theEnglishfile:

38
<!-- Labels --> <span id="TITLE">CitectSCADA Web Client Deployment</span> <span id="SYSMSG">System Messages</span> <span id="DEP">Deployment</span> <span id="DESC">Description</span> <span id="ACTION">Action</span> <!-- Messages --> <sysmsg id="DELOK">% deleted.</sysmsg> <sysmsg id="DELCAN">% will NOT be deleted.</sysmsg> <sysmsg id="DEPNULL">You can't % an empty deployment.</sysmsg> ...

wouldappearasfollowsinSpanish:
<!-- Labels --> <span id="TITLE">Despliegue del Cliente Web CitectSCADA</span> <span id="SYSMSG">Mensajes del Sistema</span> <span id="DEP">Despliegue</span> <span id="DESC">Descripcin</span> <span id="ACTION">Accin</span> <!-- Messages --> <sysmsg id="DELOK">% eliminado.</sysmsg> <sysmsg id="DELCAN">% NO ser eliminado.</sysmsg> <sysmsg id="DEPNULL">No puede % un despliegue vaco.</sysmsg>

Onceyouhavetranslatedthefileandsaveditwiththeappropriatenametothe localesfolder,yourWebServerwillbeabletosupportthelanguage. Note:Whenyousaveyourfile,makesurethetexteditoryouusedsavesthefile intheappropriateformat,i.e.ANSIorUnicode(UTF8).

Web Client Upgrade Issues

IfyouveupgradedyourWebClientfromversion6.0toversion6.1,readthe followingsectionsaboutinstallationandhowtousetheupgradedWebClient toolwithexistingdeployments. Installation UpgradingtothenewversionoftheWebClientaddsanewfoldernamed610to theclientfolder,circledhere:

IfyoureplanningoninstallingWebClientversion6.1butwanttoviewlegacy (thatis,preversion6.1)deployments,beforeinstallingthenewversion,backup yourolddeploymentstoasafelocation.Then,afterinstallingthenewversion, copyyourolddeployment(s)backtothedeployfolder(seeabove),andthe legacy.cabfile(s)tothecorrespondingfolderintheclientfolder;thiswill makeyourolddeploymentsavailableforuse. Creatingnewdeployments Whencreatinganewdeployment,notethatthe.cabfileyouuse(Client Control)forthedeploymentmustcorrespondtothecorrectversionofthe projectyouwanttoaccess.Forexample,tocreateadeploymentbasedona version6.0CitectSCADAproject,fromtheClientControlmenuchoose600/ filename.cab. DeployingaprojectfromwithinCitectSCADA IfyouaredeployingaprojectfromwithinCitectSCADA,editthe[webserver] sectioninyourcitect.inifiletospecifythecorrectcabfilefortheversionof theWebClientyoureusing.Forexample,foraversion6.1deployment,specify a.cabfilelocatedinthe610folder;fora6.0version,specifythe600folder.

36

Frequently Asked Questions

ThissectionanswersfrequentlyaskedquestionsconcerningtheWebClient.One sectionisdedicatedtoissuespertainingtoWindows2003Server,andtheother togeneralissues. Windows 2003 Server-related issues ThissectiondescribesissuesrelatingtotheWindows2003serverproduct. Q.MyWebClientDeploymentPagedisplaysincorrectlyonWindows2003 Server:ShowServerDetailsismissingandtheiconsforStartDisplayClient, DeleteDeployment,andEditDeploymentarealsomissing.HowdoIfixthis? A:Therearetwoproblemsthatcouldbeoccuringhere: WhenIIS6.0isinstalled,itdefaultstoasecurelockedmode,meaningit canserveuponlystaticcontent.ASP,ASP.NET,andFrontPageServer Extensionsarealldisabledandmustbeexplicitlyandseparatelyenabled. TheCitectSCADAWebServerneedsASPenabledontheIIS. ToenableASPforIIS6onWindows2003Server: 1 2 3 4 5 6 ChooseStart|ControlPanel,thendoubleclickAddorRemovePrograms. IntheAddorRemoveProgramsdialogbox,clickAdd/RemoveWindows Components. IntheWindowsComponentsWizarddialogbox,selectApplicationServer, andthenclickDetails. IntheApplicationServerdialogbox,selectInternetInformationServices (IIS)andclickDetails. IntheInternetInformationServices(IIS)dialogbox,selectWorldWideWeb ServiceandclickDetails. IntheWorldWideWebServicedialogbox,makesureActiveServerPageis selected. OnWindows2003Server,thedefaultsettingistohavealltheweblocations exceptlocalhostasanuntrustedsite.Consequentlyyoumustmodifyyour browserssecuritysettings. ToupdateyourTrustedSitessettingsforWindows2003Server: 1 2 3 ChooseTools|InternetOptions. ClicktheSecuritytabandthenTrustedSites|Sites. InAddthisWebsitetothezonefield,addthewebserversIPaddressas follows:
http://<ip address>

37 Note:IfyouhaveotherproblemsonyourWebClientpages,youshouldverify yoursecuritysettingsevenifyouarenotrunningWindows2003Server. Q:WhenItrytostarttheWebClient,IgettheerrormessageStartingCitect WebClientFailed:Cannotinitializecitectsystem,andthentheWebClient fails.HowdoIcorrectthis? A:Firstcheckthatyouhaventaccidentallydeletedthe#DisplayClientfolder fromtheinstalledWebServerdirectory,asthiswillcausethiserror.Bydefault, thisdirectoryislocatedat:

C:\Program Files\Citect\CitectSCADA\WebServer\Deploy\#DisplayClient

Ifthisisnotthecase,thisissueisduetoaMIMEconfigurationproblem:the initializationfilesarenotbeingrecognizedinWindows2003asregisteredfile extensions.Tocorrectthis,addthecorrectMIMEtypeextensionbydoingthe following: 1 2 3 4 5 6 RuntheIISmanagerandgotoWebSites|DefaultWebSite|Cit ectSCADA|deploy. ChoosePropertiesfromthefoldersrightclickmenu. GotoHTTPHeaders|MIMEtypes. IntheExtensionfield,enter.*. IntheMIMEtypefield,enterall. RestartyourWebserverandclient.

General issues ThissectiondescribesgeneralissuesrelatingtotheWebClientproduct. Q.WhenItrytorunadeploymentinInternetExplorer,Igetthefollowing error:Problemswiththispagemightpreventitfrombeingdisplayed properly....Whatistheproblem? A.Thecauseofthisproblemstemsfromdownloadingtheclientcomponent(the .cabfile)associatedwiththedeployment.Ifthecurrentuserontheclient computerdoesnothaveWindowslocaladministratorrightswhenthe downloadtakesplace,thiserrormessageappears. Thesolutionistoensurethatthepersonwhorunsadeploymentforthefirst timeisaWindowslocaladministratorontheclientmachine.Oncethe componentshavebeendownloaded,theproblemwillnotreoccurandanyuser canaccessthedeployment;unlessthe.cabfileisupdatedandanewerversion mustbedownloaded. Q.IdeployedaprojectfromwithinCitectSCADAusingtheappropriate citect.ini[WebServer]parameters,buttheprojectdoesnotappearinthelistof

38 deploymentsontheWebServer.Adialoginformedmethatthedeployment wassuccessful.Whathashappened? A.Thisproblemcanoccurifyoumakeanerrorwiththesyntaxforthe [WebServer]DeployRootparameter.If,forexample,youuseacurlybracket insteadofasquarebracket,(forexample,[WebServer}DeployRoot),the compilercannotreadtheparameteranddeploymentfilesaresenttothe CitectSCADAprojectdirectoryinstead:

C:\Program Files\Citect\CitectSCADA\User\<Project Name>

Thedeploymentisflaggedassuccessful,butitcannotbelocatedbytheWeb Server. Youshouldcheckthelocationaboveforevidenceofthisproblem,asasubfolder calledWebDeploywillhaveappeared.Ifthisisthecase,youshouldreview thesyntaxusedinyourcitect.inifile. Q.IdeletedauserfromthelistofusersconfiguredforaccesstotheWeb Server,buttheycanstilllogin.HowdoIdenythemaccess? A.SometimesausercanconnecttotheWebServerevenaftertheiruseraccount hasbeendeleted.Thisisduetotheoperatingsystemfailingtoacknowledge,for aperiodofaroundhalfanhour,thatauserhasbeendeleted. Thesolutionistodenyfullaccesstotheuserbeforedeletingthem.Thatway, theycannotgainaccess.SeethetopicDeletingauseraccount. Q.WhenItrytoruntheWebClientcomponentforthefirsttime,Igeta SystemSettingsChangemessageinstructingmetorestartmycomputer. WhatshouldIdo? A.Thisisaknownproblemaffectingcomputersthatcontainoldversionsof somesystemfilesrequiredbytheWebClientControl.Ifthesefilesareusedby anotherapplicationduringinstallation,thisSystemSettingsChangemessage appears.ClickOKtorestartyourmachinetoallowthenewerversionsofthe requiredfilestobeinstalledduringsystemreboot.Theproblemwilldisappear. Q.OneoftheActiveXObjectsincludedinmyprojectcannotlocateits associateddatasource.Whereisit? A.IfanActiveXobjecthasanassociateddatasource,youneedtoensurethe datasourcecanbelocatedbythecomputerhostingtheWebClient.Seethetopic Managingassociateddatasourcesfordetails. Q.WhydoesapopupsayingClientcontrol (CitectSCADAWebClient_6_0_xxx.cab)isnotintheoptionlist!whenItryto editmydeploymentfromtheWebClientDeploymentConfigurationPage?

39 Therearetwopossiblereasonsforthisdialog: 1 Youmighthavesetthe[WebServer]parameterWebClientControlincor rectly.TheWebpagemightnotrecognizethenameorversionofthe.cabfile. Youshouldalsocheckthatyouveusedaforwardslashinfrontofthecab filename,asthisisrequiredfortheWebServertolocatethecorrectfile. Ausermighthavedeletedtherequired.cabfilefromC:\Program Files\Citect\CitectSCADA\WebServer\client\600(orthespecified location).Therefore,theWebpagecannotfindit. Q.TheProcessAnalystinterfacenormallydisplaysinaforeignlanguageasI translatedthelanguageresourceDLL,butitdisplaysinEnglishontheWeb Clientplatform.HowdoIcorrectthis? A.AProcessAnalystcontrolrunninginsideaCitectSCADAWebClient supportsruntimelanguageswitching,butyoumustconfigurewhichlanguages theWebClientwilldownloadtotheclientmachine. Toconfigurethelanguagestodownload: 1 2 CreateazipfileintheCitectSCADA\binfoldercalledbin.zip. AddtothezipfileallthelanguageresourceDLLfilesthatyouwantthe clienttodownloadanduse.(Youcanfindthesefilesinyour\Program Files\Common Files\Citectfolder.) Note:Thebin.zipfileanditscontentsarenotversionchecked.Thismeans youmustmanuallyremovethebin.zipfromtheWebClientmachinesif yourservercontainsamorerecentbin.zipfile.Todothis: 1 1 1 FindtheinstallationdirectoryoftheAnalyst.dllfileonyourWebClient machinesandlookforafilecalledbin.zipinthisdirectory. Deletethisfile. ReconnecttotheWebservertodownloadthelatestbin.zipfile.

Q.IhavekeyboardshortcutsconfiguredinmyCitectSCADAproject,butthey donotworkproperlywhentheprojectisdeployedintheWebClient.Whats wrong? A.KeyboardshortcutsconfiguredforInternetExplorer(IE)takeprecedence overkeyboardshortcutsconfiguredwithinyourCitectSCADAprojects.For example,theCSV_ExampleprojecthasF11assignedtocallupHelpona selectedanimationpointonagraphicspage.IftheprojectisrunasaWebClient deployment,F11willtoggletheviewtofullscreen,asisthecasenormallywith IE. ThisisalimitationofusingInternetExplorertohostCitectSCADAprojects.The easiestsolutionistoreturntotheCitectSCADAconfigurationenvironmentand assignyourshortcutssothatnoclashesoccur.SeetheInternetExplorerHelpfor detailsofpreconfiguredkeyboardshortcuts.

40 Q.IcantprintfromtheWebClient.Whynot? A.YoucanprintfromtheWebClient,butnotbyusingyourbrowsersFile| Printcommand.Instead,inyourCitectSCADAproject,createaPrintcontrol thatusestheCicodeWinPrint()functiontoprintthepageyouwant. Q.ThenewpagethatIaddedtomyCitectSCADAprojectdoesnotappearin thePageSelectlistorthedefaultmenupageintheWebClient.HowcanI correctthis? A:IfthepageyouaddedtoyourCitectSCADAprojectdoesnotappearinWeb Client,youcanmanuallytypeinthepagenameinthePageSelectlisttoview thisnewpage.InthisversionoftheWebClient,thenewpageisnotaddedtothe defaultmenupage. Q.HowdoestheWebClientdealwithActiveXcontrols(forexample, CiMeterX.ocx)anduserfiles(Recipes.dbf,forexample)thatarerequiredbya userproject? A.Ifyouruserprojectrequiresfilessuchasthese,youneedtocreatespecialzip filestocontainthem.CreateanActiveX.zipfiletocontaintheActiveXfiles requiredbyyourproject,andaMisc.zipfiletocontainotherfilesthatyour projectneeds;forexample,recipes.dbf,Chinese.dbf,Japan.dbf,andsoon. Addthesefilesunderthemainprojectpath(forexample,C:\Program Files\Citect\CitectSCADA\User\Example). Note:Youcanhavesubfolderswithinthezipfiles,butyourprojectmustbe configuredtousethesamerelativepathstructure. Duringcompilation,anyzipfilesthatcontainsupportingfilesrequiredbya CitectSCADAprojectarecopiedtotheWebdeploysubfolder.Duringstartup, theWebClientwillcheckthetimestampofanyzipfilestodetermineifthezip fileshavebeenupdated;ifthefileshavebeenupdated,thezipfileswillbe downloaded. Q.MyprojectwascreatedusingCitectFacilitiesandincorporatestheCitect TimeScheduler.TheTimeSchedulerisnotworkingwhenIruntheprojecton theWebClient.Whatswrong? A.IfyouwanttoruntheTimeScheduleronaCitectSCADAWebClient,you mustensurethattheuserprofileyouloginwithhasappropriatenetworkaccess totheconfigurationtool,andthelocationoftheconfigurationfiles.Theuser mustbeabletoexecutetheconfigurationtool,andwritetotheconfiguration files. Q.TheWebClientDeploymentPagedisplaysincorrectlyonWindows2000 AdvancedServer.ShowServerDetailsismissing,andtheiconsforStart

41 DisplayClient,DeleteDeploymentandEditDeploymentarealsomissing. Whatiswrong? A.ThisappearstobecausedbyWindowsAutomaticUpdateinstallingseveral componentsatthesametimeafterafreshinstalloftheoperatingsystem.Even thoughInternetExplorermighthavebeenupgradedtothelatestversion(for example,6.0.2800.1106)itmightstillbehaveasaversion5browser;forexample, itofferslimitedsupportforiframes.IfyoucallupAboutInternetExplorer fromtheHelpmenu,andaVersion5styledialogappearswithaversion6 releasenumber,thenyourcomputerisaffectedinthisway. Acompleteuninstall/reinstallofInternetExplorerwillcorrecttheproblem.

42

Appendix A: Windows Language Codes

code af sq ar-sa ar-iq ar-eg ar-ly ar-dz ar-ma ar-tn ar-om ar-ye ar-sy ar-jo ar-lb ar-kw ar-ae ar-bh ar-qa eu bg be ca zh-tw zh-cn zh-hk zh-sg hr cs da nl nl-be en en-us en-gb Windows locale setting Afrikaans Albanian Arabic (Saudi Arabia) Arabic (Iraq) Arabic (Egypt) Arabic (Libya) Arabic (Algeria) Arabic (Morocco) Arabic (Tunisia) Arabic (Oman) Arabic (Yemen) Arabic (Syria) Arabic (Jordan) Arabic (Lebanon) Arabic (Kuwait) Arabic (U.A.E.) Arabic (Bahrain) Arabic (Qatar) Basque Bulgarian Belarusian Catalan Chinese (Taiwan) Chinese (PRC) Chinese (Hong Kong SAR) Chinese (Singapore) Croatian Czech Danish Dutch (Standard) Dutch (Belgium) English Englsih (United States) English (United Kingdom) code hu is id it it-ch ja ko ko lv lt mk ms mt no no pl pt-br pt rm ro ro-mo ru sz sr sr sk sl sb es es-mx es-gt es-cr es-pa es-do Windows locale setting Hungarian Icelandic Indonesian Italian (Standard) Italian (Switzerland) Japanese Korean Korean (Johab) Latvian Lithuanian FYRO Macedonian Malaysian Maltese Norwegian (Bokmal) Norwegian (Nynorsk) Polish Portuguese (Brazil) Portuguese (Portugal) Rhaeto-Romanic Romanian Romanian (Moldavia) Russian Sami (Lappish) Serbian (Cyrillic) Serbian (Latin) Slovak Slovenian Sorbian Spanish (Traditional) Spanish (Mexico) Spanish (Guatemala) Spanish (Costa Rica) Spanish (Panama) Spanish (Dominican Republic)

48

Appendix A: Windows Language Codes

code en-au en-ca en-nz en-ie en-za en-jm en en-bz en-tt et fo fa fi fr fr-be fr-ca fr-ch fr-lu gd gd-ie de de-ch de-at de-lu de-li el he hi Windows locale setting English (Australian) English (Canada) English (New Zealand) English (Ireland) English (South Africa) English (Jamaica) English (Caribbean) English (Belize) English (Trinidad) Estonian Faeroese Farsi Finnish French (Standard) French (Belgium) French (Canada) French (Switzerland) French (Luxembourg) Gaelic (Scotland) Gaelic (Ireland) German (Standard) German (Switzerland) German (Austria) German (Luxembourg) German (Liechtenstein) Greek Hebrew Hindi code es-ve es-co es-pe es-ar es-ec es-cl es-uy es-bo es-sv es-hn es-ni es-pr sx sv sv-fi th ts tn tr uk ur vg ve vi xh ji zu Windows locale setting Spanish (Venezuela) Spanish (Colombia) Spanish (Peru) Spanish (Argentina) Spanish (Ecuador) Spanish (Chile) Spanish (Uruguay) Spanish (Bolivia) Spanish (El Salvador) Spanish (Honduras) Spanish (Nicaragua) Spanish (Puerto Rico) Sutu Swedish Swedish (Finland) Thai Tsonga Tswana Turkish Ukrainian Urdu Valley Girl Venda Vietnamese Xhosa Yiddish Zulu

Index
A
ActiveX.zip,23 Administrator WebClient,11

M
ManagerClient WebClient,11 Misc.zipfile,23 multiplelanguagesupportforWebClient,35 nondefaultlanguages,36

P
preparingaprojectforWebClientdeployment,21

C
configuring WebClientdeployment,25 creating WebClientdeployment,26

R
requirements WebServer,5

D
defaultlanguagesforWebClient,35 deploymentforWebClient configuring,25 creating,26 deleting,32 displaying,30 editing,31 fromCitectSCADA,28 updating,32 DisplayClient WebClient,11

S
security configuringWebClientusergroups,14 deletingWebClientusers,19 preparingtheWebServerfolder,15 setttingupWebClientaccounts,18 testingWebClientsettings,19 WebClient,11 WebClientsetup,13

U
unsupportedfunctionality,21 users WebClient,11

F
FAQs WebClient,40 frequentlyaskedquestions WebClient,40 functionalitylimitations,21

W
WebClient,1 ActiveX.zipfile,23 Administrator,11 clientaccountaccessrights,18 configuringadeployment,25 configuringclientaccountusergroups,14 creatingadeployment,26 defaultlanguages,35 deletingadeployment,32 deletingauseraccount,19 Deployfolder,7 deployingaprojectfromCitectSCADA,28 DisplayClient,11

L
languages WebClient,35 limitations Cicodefunctions,21 functionality,21 loggingontoWebServer,20

50

Index DisplayClientfolder,7 displayingadeployment,30 editingadeployment,31 frequentlyaskedquestions,40 functionalitylimitations,21 gettingstarted,3 implementingnondefaultlangauges,36 installeddirectories,7 introduction,1 loggingontoWebServer,20 ManagerClient,11 Misc.zipfile,23 multiplelanguagesupport,35 preparingaprojectfordeployment,21 preparingtheWebServerfolder,15 preparinguserfilesfordelivery,23 security,11 settingupasystem,3 settingupaccessrights,18 settingupsecurity,13 systemarchitecture,1 testingsecurity,19 updatingadeployment,32 useraccounttypes,11 usingadifferentlanguagetothelocalesetting,36 WebDeploymentPreparationtool,24 WebServeraddress,20 WebDeploymentPreparationtool,24 WebServer address,20 requirements,5