Wonderware InTouch 8.0 ReadMe. New Features of InTouch 8.0. ArchestrA Application Server Integration. New Security Models

Transcription

1 Wonderware InTouch 8.0 ReadMe Last revision: 12/05/02 This document contains important information about WonderwareÒ InTouchÔ 8.0. Please carefully review this document for known issues in this version and changes to the InTouch documentation included on this CD. New Features of InTouch 8.0 InTouch Documentation System Requirements Installation Information Known Restrictions for Limited Users InTouch 8.0 Known Issues InTouch 8.0 Known Issues - InTouch 8.0 Documentation New Features of InTouch 8.0 Wonderware InTouch 8.0 is comprised of several components that provide: visualization design and presentation data access extensibility to external components/systems event handling alarm logging history, reporting and analysis tools Wonderware InTouch has set the standard for ease of development to allow users to create complex and powerful operator interface displays quickly and easily. Some of the new features in this release are: ArchestrA Application Server Integration InTouch 8.0 is the first ArchestrA-enabled version of InTouch, which integrates with Wonderware s new Application Server. Using the same familiar development and runtime environment, it is now possible to browse the ArchestrA namespace and to design and deploy a fully integrated and extensible ArchestrA-based graphics application. New Security Models InTouch 8.0 adds two security models; operating system (OS)-based security and ArchestrA-based security. With a single click, an application can be configured to use OS-configured users and groups or ArchestrA users and roles. A number of new functions are introduced to enable authentication to be simply configured and controlled within an application. These new models are in addition to the current InTouch based security, which is maintained for compatibility. Improved Support for FDA 21 CFR Part 11 Requirements In conjunction with the new security and authentication functions, new system tags enable the visibility of full names of operators, and OS group and ArchestrA role membership. Using these features improves productivity and flexibility when designing and configuring an application, which must be validated to conform to the above standard. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 1/15

2 Upgraded Distributed Alarm Subsystem With easy configuration and improved alarm handling performance, the Distributed Alarm Subsystem of InTouch 8.0 builds on the changes introduced for InTouch 7.11 and adds ArchestrA support, FDA alarm features and performance enhancements. Alarm Toolkit The InTouch 8.0 Alarm Toolkit enables systems integrators and end-users to enhance their InTouch system by writing custom Alarm Providers and Alarm Consumers. Providers and consumers will be capable of being fully integrated with both 7.11 and 8.0 alarm systems. Alarm Display A new Alarm Display, the Alarm Viewer, is introduced. This display uses ActiveX technology for full script control and versatility. It provides a superset of the familiar distributed alarm object (DAO), which is maintained. The Alarm Viewer is designed to present a similar look and feel to the Alarm DB View control. Alarm DB View Updates The Alarm DB View control is used to visualize historical alarm information from the alarm database. InTouch 8.0 updates this control to add new features and flexibility, including a Duration column, more flexible alarm comments, configurable date and time formats and a new drag-and-drop query filter designer. New Alarm Fields New alarm fields are introduced for the FDA related information, including the full name of the operator associated with an alarm action. Enhanced Alarm Database InTouch 8.0 adds full support for Microsoft SQL Server 2000 and MSDE Enhancements to the database views have been made to improve performance on retrieval of larger data sets. Log Viewer The Log Viewer is introduced as a system service that records information from ArchestrA-enabled components regarding the activities occurring on your computer. The Log Viewer is part of the System Management Console (SMC) suite of utilities you can use to manage InTouch and the ArchestrA environment. The Log Viewer is a replacement for the Wonderware Logger (WWLogger). InTouchView InTouchView is designed as a visualization and interface product specifically for use in an ArchestrA Application Server environment. Using InTouchView, ArchestrA-enabled applications can be developed which provides operators with the ability to perform tasks when connected to an ArchestrA Application Server system. InTouchView applications do not have the ability to connect to I/O sources other than an ArchestrA Application Server Galaxy. InTouchView applications do not generate alarms, but can display and acknowledge alarms from other alarm providers. InTouchView applications use the ArchestrA security model. Change Network Account Utility Use the Change Network Account utility to change the Domain or Local Machine Name, User Name and/or Password. To use this utility, click Start, point to Programs, then point to Wonderware, Common and click Change Network Account. Top of document file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 2/15

3 InTouch Documentation The InTouch documentation set includes the following guides: Wonderware FactorySuite InTouch User s Guide. InTouch Reference Guide. Provides an in-depth reference to the InTouch QuickScript language and functions, system tagnames, and tagname dotfields. SPCPro User s Guide. Provides complete information on the InTouch SPCPro add-on program. Recipe Manager User s Guide. Provides complete information on the Recipe Manager addon program. SQL Access Manager User s Guide. Provides complete information on the SQL Access Manager add-on program. Wonderware FactorySuite Protocols Guide. This guide provides background information on the main protocols used between components of Wonderware products. All of these guides are provided in PDF form and can be printed. Also, information included in these guides is provided in browser-based online Help. You need to install Adobe Acrobat reader in order to view the PDF user s guides. Click here to Download Acrobat Reader. Top of document System Requirements To run InTouch, we recommend as a minimum the following hardware and software configurations: Any IBM compatible PC with a Pentium II processor or higher (minimum: 400MHz on a single node system, recommended: 1.2GHz or higher). At least 2GB of free hard disk space. At least 256MB of random-access memory (RAM), 512MB of RAM is recommended. We recommend 5MB of RAM per 5K tagnames. For example, 32MB of RAM for 32K tagname support and 128MB of RAM for 60K tagname support. SVGA display adapter (2MB RAM recommended). We recommend you view WindowMaker in 800x600 resolution or higher to ensure full visibility of all dialog boxes. Pointing device. For example, mouse, trackball, touch screen. The Microsoft Windows 2000 Professional operating system with Service Pack 3 or higher or the Microsoft Windows XP Professional operating system with Service Pack 1 or higher. For InTouch Terminal Services, the Microsoft Windows 2000 Server(s) operating system(s) with Service Pack 3 or higher and with Windows Terminal Services enabled only in the Application Server mode. For the Windows 2000 operating system to implement the distributed functionality of InTouch, Wonderware NetDDE must be installed and operational. Wonderware InTouch Version 8.0 (or later) does not support the Microsoft Windows 3.x, the Microsoft Windows for Workgroups, the Microsoft Windows 9x or the Microsoft Windows NT operating systems. Top of document file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 3/15

4 Installation Information InTouch 8.0 Installation Detailed installation instructions are included in the InTouch Installation Guide. It is recommended that you read the InTouch Installation Guide prior to beginning the installation process. To read the installation guide, click here. The Microsoft SQL Server key is required in order to install the MS SQL Server. When installing the MS SQL Server, you will be asked to enter the 25 digit key number. The Microsoft SQL Server key number is GJDD4-GMYXW-GQR4C-KT4P9-QDQGB. If Microsoft SQL Server 2000 is installed on the same system on which InTouch is being installed, the InTouch setup program may require you to reboot the system during the installation procedure. The reboot is required because Microsoft SQL Server 2000 installs MDAC version 2.6, but InTouch requires MDAC version 2.6 Service Pack level 2 (SP2). The InTouch setup program will install this Service Pack during installation. Once the system has been rebooted, InTouch installation will resume automatically. Due to this reboot, the off node communication account User Name and Password that were entered before this reboot must be re-entered after InTouch installation is resumed. This applies only if you are installing InTouch on Microsoft Windows 2000 operating system(s). If Microsoft SQL Server 2000 SP2, which installs MDAC version 2.6 SP2, is installed on your system prior to InTouch installation or if Microsoft SQL Server 2000 is not installed on your system, the InTouch setup program will not require a reboot during installation. If InTouch 7.11 is installed on your system and you have Alarm DB Logger set to run as a service, you must change the mode to manual before you uninstall InTouch and reboot your system. If you uninstall InTouch 7.11 with Alarm DB Logger in automatic mode, InTouch 8.0 installation will not complete properly. Top of document Known Restrictions for Limited Users InTouch 8.0 Although InTouch 8.0 can be run by Limited Users, certain features and operations will not be supported for Limited Users. We recommend that users who configure InTouch applications have Power User privileges. The following operations are not supported for Limited Users: Installing or uninstalling Wizards and ActiveX controls. Configuring node properties (Limited Users will not be permitted to access Node Properties in the Application Manager). Converting 16 bit applications created in InTouch 5.6a. Opening applications created by other users. Using the license utility. Using SPCPro features. Using the Alarm Purge-Archive utility. Using the Alarm DB Restore utility. Using the AlarmSuite History Migration utility. Changing the Alarm DB Logger settings. Top of document Known Issues InTouch 8.0 file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 4/15

5 Alarm Database Migration Please backup your alarm database before performing any actions in InTouch 8.0. Once the database has been migrated to the InTouch 8.0 format, it will not be accessible from InTouch The InTouch 7.11 alarms database will be automatically migrated to the InTouch 8.0 format upon pressing Start in the InTouch 8.0 AlarmDBLogger utility. For successful migration, the user should be logged on as "sa. Data integrity will be maintained during the migration process. Once the migration is complete, the alarm data may be viewed using the tools included in InTouch 8.0. Viewing Alarms from the Application Server Use the Alarm Viewer ActiveX control to view alarms generated by the Application Server. Do not use the Distributed Alarm Object. InTouch Security It is recommended to start InTouch with ArchestrA-based security selected only if you have a platform deployed. Using IsAssignedRole in Animations Known Issue: When using the "IsAssignedRole" script function in animations, the screen may not refresh properly. Work-Around: Place the "IsAssignedRole" script in a Data Change Script that triggers off of a change to $Operator. Set memory discrete tags for each role to be tested and use the memory tags for animation. L : To run View or the Alarm DB Logger as service, reboot your computer after installing InTouch. L : Alarm DB View Control In the Events tab, the validation for the Script name is done for only 32 characters. If more than 32 characters are entered, only 32 characters will be retained upon validation. L : Security Changing passwords: InTouch Local security password changes function correctly. InTouch OS security - If the user logged on to the computer is a domain user who is a local administrator, that user can change the local user password in InTouch. Local administrators can change the passwords of all users who are not administrators. InTouch ArchestrA mode ArchestrA in Galaxy password changes function correctly. ArchestrA in OS mode Only a user logged on to InTouch as an administrator can change passwords. Currently, ArchestrA does not allow local non-administrator passwords to be changed. L : The Productivity Pack is no longer available on the InTouch CD-ROM as a separate product. However, the Symbol Factory and 16 Pen Trend components of Productivity Pack are available as an option to install during InTouch installation. The remaining components of Productivity Pack will be available on the Knowledge Base CD (KBCD). L : The following Alarm DB View Control properties have been retained from InTouch 7.11 and can be scripted only (they will not appear in the Properties dialog box): file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 5/15

6 1. UnAckAlmForeColor - Get: returns UnAckAlmForeColorRange1 Set : sets UnAckAlmForeColorRange1 through UnAckAlmForeColorRange4 2. UnAckAlmBackColor - Get: returns UnAckAlmBackColorRange1 Set: sets UnAckAlmBackColorRange1 through UnAckAlmBackColorRange4 3. AckAlmForeColor - Get: returns AckAlmForeColorRange1 Set: sets AckAlmForeColorRange1 through AckAlmForeColorRange4 4. AckAlmBackColor - Get: returns AckAlmBackColorRange1 Set: sets AckAlmBackColorRange1 through AckAlmBackColorRange4 5. AckRtnForeColor - Get: returns AlmRtnForeColor Set: sets AlmRtnForeColor 6. AckRtnBackColor - Get: returns AlmRtnBackColor Set: sets AlmRtnBackColor 7. UnAckRtnForeColor - Get: returns AlmRtnForeColor Set: sets AlmRtnForeColor 8. UnAckRtnBackColor - Get: returns AlmRtnBackColor Set: sets AlmRtnBackColor Wonderware recommends that users of InTouch 8.0 use the new InTouch 8.0 properties instead of the InTouch 7.11 properties. L : The following InTouch 7.11 Alarm DB View Control properties are supported in InTouch 8.0: ProviderName ProviderExactMatch GroupName GroupExactMatch FromPriority ToPriority When these properties are set and Refresh/Requery is performed, these properties will take precedence while querying for the data from the database. If filters are defined they will be ignored when these properties are set, but if a filter favorite is applied later, filters will take effect. L : While querying a Hot Backup Pair from the client node, the behavior in the following scenarios is as described: Scenario 1. With both the primary and secondary nodes running, close WindowViewer for the primary node, but leave WindowMaker open. Alarm Manager does not switch to the secondary node. Scenario 2.With only the secondary node running, close WindowViewer for the secondary node, but leave WindowMaker open. The Distributed Alarm Object still shows the secondary alarms. The behavior observed in both scenarios is as expected. As long as Alarm Manager is running on the primary or secondary node, the client has a valid connection. InTouch 8.0 starts Alarm Manager when WindowMaker or WindowViewer is opened. If WindowMaker is running, Alarm Manager is also running and the client has valid connection. Note : The client connection will be reset when Alarm Manager is closed. If both WindowMaker and WindowViewer are open, you must close both WindowMaker and WindowViewer to close Alarm Manager. L : The TagType column in the AlarmMaster table contains R for ROC alarms on Integer Tags. This is because, for an ROC alarm, the Value and Limit field values can be real even if the tag is of type integer. Therefore, the consumer receives the type as Real and that value is logged into the database. L : file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 6/15

7 In the InTouch security mode, the value of the first event is set to "InTouch\operator" in order to ensure that a change occurs in cases of both success and failure (with short operator name and "" values respectively) and a concluding event is generated. L : If an incorrect xml file is selected for Query Favorites in the Alarm Viewer ActiveX Control or for Filter Favorites in the Alarm DB View ActiveX Control, the controls recognize that the file format is incorrect. When you click Query Favorites in Alarm Viewer or Filter Favorites in the Alarm DB View Control, an error message is displayed informing you that the file format is incorrect. Click OK to reformat the file or click Cancel if you do not want to reformat the file, then enter an xml file with the correct format for Query Favorites or Filter Favorites. L : Security, $PasswordEntered tag: When a user is logged off, the $PasswordEntered tag is set to a special character (alert bell character) instead of being set to null. L : The Symbol Factory default directory is C:\InTouch. L : When using ArchestrA-based security, the system sets the proper domain name if a user logs in using a fully-qualified username (DomainName\UserName) and leaves the Domain Name field blank. L : Password changes have been tested to be working under the following scenarios: 1..InTouch Local security password changes are functional. 2. InTouch OS security - If the logged on user to machine is a domain user that is a local administrator, the user can change the local user s password in InTouch. Local administrator users can change non-administrator passwords. 3. InTouch ArchestrA mode 3.a. ArchestrA in Galaxy mode password changes are functional. 3.b. ArchestrA in OS mode Only a user logged on to InTouch as an administrator can change a password. L : If you have created an application using InTouch 7.11 and the Event Trend, SQL Grid or Doc Viewer Productivity Pack Utilities, you must do the following to open the application in InTouch 8.0: 1) Event Trend Copy the wcchart.dll and wcchart.wdo files into the InTouch folder (C:\Program Files\Wonderware\InTouch). 2) SQL Grid - Copy the Sqlgrid.dll,sqlgrid.wdo, ivsql08.dll, ivgui08.dll, ivqry08.dll and ivutl08.dll files into the InTouch folder (C:\Program Files\Wonderware\InTouch). 3) Doc Viewer - Copy the Docview.dll and Docview.wdo files into the InTouch folder (C:\Program Files\Wonderware\InTouch) and copy the View32W.dll file into the ArchestrA folder (C:\Program Files\Common Files\ArchestrA). Note: It is not necessary to copy any files for WizGen Generator. L : file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 7/15

8 When using workgroups, the workgroup name cannot be substituted for the domain name in the Log On dialog box. The Log On dialog box must have the local machine name, which is the true authenticator in the case of a workgroup. If the domain name is left as null, InTouchView will log on to the local machine by default. L : When using workgroups, the workgroup name cannot be substituted for the domain name in the AddPermission (or any other) script function. Instead, the local computer name, which is the true authenticator in case of a workgroup, must be used as the domain name. L : To improve the performance of the Alarm DB Logger, data can be stored to the SQL Server on a separate node. L : The installation procedure no longer installs the WWLogger (Wonderware Logger). The new logging system is called "Log Viewer" and is part of the System Management Console (SMC), which is installed during InTouch installation. The System Management Console, which contains Log Viewer, can be launched via the Start/Programs menu under "Wonderware." Log Viewer will no longer be launched automatically when InTouch is started. L : All users of OS-based security should use non-null passwords. This applies only if $PasswordEntered is used to Logon and is not an issue if GUI or scripts are used to log on. L : The accelerator key for browsing to the next animation link in the object properties dialog box in WindowMaker is ALT + K. Using ALT + N will cause WindowMaker to freeze. L : InTouch 8.0 requires, as a prerequisite, MDAC 2.6 to be installed on Windows 2000, and MDAC 2.7 to be installed on Windows XP Professional operating systems. InTouch installation procedure will detect if MDAC 2.6 is not installed on your Windows 2000 system and will give you a chance to install it automatically. MDAC 2.7 is already installed as part of Windows XP Professional operating system. L : When the path is not specified in the Query Favorites field in the AlarmViewerCtrl Properties Query tab or in the Filter Favorites File Name field in AlarmDbViewCtrl Properties Query Filter tab, the XML file for Query Favorites or for Filter Favorites is created in the %ALLUSERSPROFILE%\Application Data\Wonderware\InTouch directory by default. L : In the Alarm Viewer ActiveX Control, sorting by the Limit and Value columns is not supported. In the secondary sort dialog these columns will not be displayed. L : The following conditions apply when you are using the AttemptInvisibleLogon() script function to log on to InTouch: If the ArchestrA-based security mode is selected, the Domain Name can be left blank only if the Galaxy security mode is selected or a fully qualified user name is entered in the username field (in the case of OS User or OS Group-based security mode). file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 8/15

9 If the InTouch security mode is selected, there is no domain so the Domain Name can be left blank. If the operating system-based security mode is selected and the Domain Name is left blank, the system considers the local computer name to be the domain name. L : Security The maximum number of characters for usernames for users logging on to InTouch varies depending on which security mode is in use. The differences by mode are as follows: 1) ArchestrA-based security mode ArchestrA-based security is selected in InTouch and ArchestrA has the following settings: Galaxy usernames can have a maximum of 255 characters.. InTouch login restricts the allowed user name length to 68 characters. Galaxy users with usernames consisting of more than 68 characters will not be able to log on to InTouch applications using the ArchestrA-based security mode. 2) InTouch-based security mode: InTouch usernames can have a maximum of 16 characters. The logon dialog box restricts the number of characters in the username to 16. 3) Operating System-based security mode For operating system-based security modes (i.e. InTouch operating system user-based, ArchestrA operating system user-based and ArchestrA operating system group-based modes), usernames can have a maximum of 20 characters due to operating system restrictions. The logon dialog box restricts the number of characters in the username to 20. For the operator full name: In InTouch-based security mode, the full name is the same as the username. In all other security modes, the operator full name is restricted to 131 characters. Galaxy usernames can have a maximum of 255 characters and operating system-based security usernames can have a maximum of 256 characters. For these users, InTouch truncates the full name at 131 characters and uses that as the operator full name. L : $InactivityTimeout does not set the logged on operator name to None in all security modes. For the InTouch security mode, $InactivityTimeout sets $OperatorName to None and $OperatorDomain to InTouch. For the operating system-based security mode, $InactivityTimeout sets $OperatorName to None and $OperatorDomain to the previously logged on user s domain (these values should be null).for the ArchestrA-based security mode, $InactivityTimeout sets $OperatorName to None and $OperatorDomain to the previously logged on user s domain (these values should be null). For ArchestrA Galaxy-based security, $InactivityTimeout sets $OperatorDomain to ArchestrA, but does not set $OperatorName to null. L : In regions that normally use the 24-hour time format, users must set up the AM and PM symbols in Windows/Control Panel/Regional Settings/Time tab in order to display the AM/PM time formats correctly in the Alarm Viewer control and the Alarm DB View control. L : In the Alarm Viewer ActiveX Control, the Value and Limit sorting options appear in the Query tab, but the use of these sorting options is not supported. L : If your system has a Windows 2000 operating system, you must set the TCB privilege to file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 9/15

10 Act as a part of the operating system before logging on to InTouch using operating systembased security. This is not required for the Windows XP Professional operating system. To set the TCB privilege: 1. On the Start menu, point to Programs, then point to Administrative Tools and click Local Security Policies. 2. Open the Local Policies folder and double-click the User Rights Assignments folder. 3. Double click Act as a part of operating system. 4. Add the user and click OK. 5. Log on to the computer again before using the TCB privilege. L : If you log on to an ArchestrA-Galaxy mode using the PostLogOnDialog or the Security Logon feature on the Special menu and have a user name with 68 or more characters, the proper $OperatorName will not be displayed. Under these conditions, only the last four characters of user name will be displayed. If you log on to an ArchestrA-Galaxy mode using $*Entered tags or scripts, the proper $OperatorName will be displayed. L : InTouch Terminal Services using Windows Terminal Services Advanced Client (TSAC) The ActiveX control for TSAC, which is installed currently on your Windows 2000 server with Terminal Services enabled, may not work properly if you have an older version of this control installed. Attempting to open this ActiveX control in an Internet Explorer browser may cause a blank page to be displayed. To resolve this issue, click the link below to install the latest TSAC ActiveX control from Microsoft. In this web page, click the Remote Desktop Web Connection ActiveX control link to install the latest TSAC ActiveX control on your Windows 2000 server with Terminal Services enabled. This issue is ONLY applicable if you are using TSAC in connection with running InTouch 8.0 Terminal Services. L : Attempting to write to an Application Server tag using an indirect tag will produce false messages in the log when the attempt fails due to security. The following messages will appear in the log: 1) Failed to Poke - This message is correct. 2) Failed to advise This message appears in the log twice and is incorrect. L : The Operator Full Name and Operator Domain are not populated for ACK records if the acknowledgement is done from the Distributed Alarm Object (DAO). CFR 21 Part 11-compliant applications should be developed using the AlarmViewer ActiveX Control and not the Distributed Alarm Object. L : When a user password for operating system-based security expires, the user cannot change the password from within InTouch. The user must log off from the Terminal Session, log on again with the current username and change the password. Then, the user must start the InTouch application and log on to InTouch using the new password. The password in the operating system can be changed within InTouch by using the ChangePassword script only if the user is logged on to a valid session of InTouch. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 10/15

11 L : Creation of WWALMDB database / Recreation of tables (with the Recreate Tables option selected) can be performed by sa only. Restoring of Alarm Records (as used in Restore Utility) can be performed by sa only. Migration of Alarm Records (as used in Alarm Suite History Migration) can be performed by "sa, "wwadmin" and "wwpower. Viewing of Alarm Records (as used in the Alarm DB View Control) can be performed by sa, wwadmin, wwpower, and wwuser. Purging Alarm Records (as used in Purge / Archive Utility) can be performed by sa and wwadmin. L : Since events for Domain, Operator Name and Operator are generated before the actual field value has changed, the field for that particular value will display the information for the previous user. L : When using InTouch in combination with the Application Server, the RTN Implies Ack option in the Alarm Properties dialog box does not apply to alarms generated from the Application Server. Therefore, if an Application Server alarm is active and unacknowledged, then returns to normal, it will not be acknowledged and will continue to be displayed. L : To change a user log on, aaadminuser.exe, which is accessed from the Start menu, should be used instead of wwuser.exe. L : If your system has a Microsoft Windows XP operating system, you will not be able to log on to InTouch with operating system-based security using a blank password. Wonderware recommends that users avoid using blank passwords for InTouch when any security mode other than None is selected. Top of document Known Issues InTouch 8.0 Documentation The following table describes changes to the documentation. Item Location of Change Existing Documentation Change 1 InTouchUG.pdf, System Requirements, p InTouchUG.pdf, Customizing Your Development Environment, p InTouchUG.pdf, Setting WindowViewer s General Properties, p InTouchUG.pdf, Using the Security System Tagnames, p File: Using the Microsoft Windows 2000 Professional with Service Pack 1 or Windows XP Professional with Service Pack 3 operating systems. WindowMaker Properties screenshot shows Start Wonderware Logger as a checkbox option. WindowViewer Properties screenshot shows Start Wonderware Logger as a checkbox option. Whenever the $PasswordEntered tag changes, a log on is attempted internally without any GUI being displayed. Microsoft Windows 2000 Professional with Service Pack 3 or Windows XP Professional with Service Pack 1 operating systems. Start Wonderware Logger is not an option in WindowMaker Properties. Start Wonderware Logger is not an option in WindowViewer Properties. Whenever the $PasswordEntered tag changes, a log on is attempted internally without any GUI being displayed. The log on attempt file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 11/15

12 Security System Tagnames. 5 InTouchUG.pdf, $VerifiedUserName, p InTouchUG.pdf, Tagname Dictionary Special Features, p WindowMaker Help File: Tagname Dictionary Special Features. The log on attempt uses the $*Entered tags as input user name and the string value of $OperatorDomainEntered as the domain name (used only if the current mode is operating system-based security). If the security mode is not operating system-based, this tag is ignored. Contains the verified user's full name if the call to InvisibleVerifyCredentials() is successful and if the security mode is set to operating system-based or ArchestrA AppServer-based security. Extended Tagname Support InTouch can support up to 61,405 tagnames in its Tagname Dictionary. (The number of tagnames that your system supports is determined by your software license.) uses the $*Entered tags as input user name and the string value of $OperatorDomainEntered as the domain name (used only if the current mode is operating system or ArchestrA-based security). This tag can be ignored if the security mode is: 1. the InTouch-based security mode. 2. the operating system-based security mode and the user is logged on to a local computer. 3. the ArchestrA-based security mode or the operating systembased (user or group) mode if $OperatorEntered has the fullyqualified username 4. the ArchestrA Galaxy mode. Contains the verified user's full name if the call to InvisibleVerifyCredentials() is successful and if the security mode is set to any security mode except for the None mode. Extended Tagname Support InTouch can support up to 61,402 tagnames in its Tagname Dictionary. (The number of tagnames that your system supports is determined by your software license.) 7 InTouchUG.pdf, Timestamps in the Distributed Alarm System, p File: Timestamps in the Distributed Alarm System. 8 InTouchUG.pdf, AlarmCounter Database Stored Procedure, p File: AlarmCounter Database Stored Procedure. Timestamps in the Distributed Alarm System The present Alarm Record for the Distributed Alarm system has five timestamps: Table shown The column names in the table are documented as: TagName Nchar, Name of the object that generated the alarms such as TIC101 Area Nchar, Name of the area or group for the alarm Type Nchar, Type of alarm such as Hi, HiHi, ROC, PV, Remove section and table. The column names in the table should be documented as: TagName Nchar, Name of the object that generated the alarms such as TIC101 GroupName Nchar, Name of the area or group for the alarm AlarmType Nchar, Type of alarm such as Hi, HiHi, ROC, file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 12/15

13 9 InTouchUG.pdf, Column Details Button, p File: Column Details Button. 10 InTouchUG.pdf, Column Details Button, p File: Column Details Button. Alarm Viewer Help File: Column Details Button. 11 InTouchUG.pdf, Colors Page, p File: Colors Page. 12 InTouchUG.pdf, Colors Page, pp File: Colors Page. HiAlarm. Category Nchar, Alarm class or alarm category such, as Value, Process, Batch, etc. AlarmCount Integer, Number of onsets of the alarm during the time range. If alarm existed prior to entering the selected time range, do not count that one. Priority Integer, Alarm priority. Provider Nchar, Provider of alarm, such as node/intouch, or GalaxyName. Comment - Nchar Comment - Displays the tagname s comments. These comments were typed in the Alarm Comment box when the tagname s alarm was defined in the database. These comments are also updated when ACK comments are given. The property descriptions list the incorrect default colors for several properties. PV, HiAlarm. AlarmClass Nchar, Alarm class or alarm category such, as Value, Process, Batch, etc. AlarmCount Integer, Number of onsets of the alarm during the time range. If alarm existed prior to entering the selected time range, do not count that one. Priority Integer, Alarm priority. Provider Nchar, Provider of alarm, such as node/intouch, or GalaxyName. Comment - Nchar Description - Displays the tagname s comments. These comments were typed in the Alarm Comment box when the tagname s alarm was defined in the database. These comments are also updated when ACK comments are given. UTC Time - Displays the date and time of the alarm or event, in coordinated universal time (UTC). Duration Displays the UNACK duration or the alarm duration, depending on what has been selected by the user. AckOrAlarmDuration The duration column is populated with either UNACK Duration or Alarm Duration. FALSE (0) is UNACK Duration and TRUE (1) is Alarm Duration. The following list notes the corrections required for property color defaults: AlmRtnForeColor - The default color is blue. AlmRtnBackColor - The default color is white. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 13/15

14 EventForeColor - The default color is red. 13 InTouchUG.pdf, About the Filters Pane, p WindowMaker Help File: About the Filters Pane. Alarm DB View Control Help File: About the Filters Pane. 14 InTouchUG.pdf, About the Filters Pane, p WindowMaker Help File: About the Filters Pane. Alarm DB View Control Help File: About the Filters Pane. Duration Filters query by UNACK duration % - any string of zero or more characters. _ - any single character. [ ] - Any single character not within the specified range ([^a-f]) or set ([^abcdef]). [^ ] - Any single character not within the specified range ([^a-f]) or set EventBackColor - The default color is white. UnAckAlmBackColorRange1 - The default color is white. UnAckAlmBackColorRange2 The default color is white. UnAckAlmBackColorRange3 - The default color is white. UnAckAlmBackColorRange4 - The default color is white. AckAlmBackColorRange1 - The default color is white. AckAlmBackColorRange2 - The default color is white. AckAlmBackColorRange3 - The default color is white. AckAlmBackColorRange4 - The default color is white. AckAlmForeColorRange1 - The default color is black. AckAlmForeColorRange2 - The default color is black. AckAlmForeColorRange3 - The default color is black. AckAlmForeColorRange4 - The default color is black. Duration Filters query by UNACK and alarm duration. A duration column set as equal to zero will not produce records with a null value in the query. % - any string of zero or more characters. _ - any single character. [ ] - Any single character within the specified range ([a-f]) or set ([abcdef]). [^ ] - Any single character within the specified range ([^af]) or set ([^abcdef]). file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 14/15

15 15 InTouchUG.pdf, New Alarm DB Logger Features, p File: New Alarm DB Logger Features. Top of document ([^abcdef]). InTouch and its related applications will not launch the Alarm DB Logger in the event that it is not already running. InTouch and its related applications will not launch the Log Viewer, automatically. The Log Viewer must be launched manually. To launch the Log Viewer: 1. On the Start menu, point to Programs, then click Wonderware. 2. Click System Management Console, then click Log Viewer. 3. Click Default Group, then click Local. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/readme80.html 15/15