Metasys Web Access System Overview

Transcription

1 Technical Bulletin Issue Date February 18, 2003 Metasys Web Access System Overview Metasys Web Access System Overview...2 Introduction... 2 Key Concepts... 3 Related Information... 3 Hardware and Software Requirements... 4 Features... 4 MWA User Types... 5 Microsoft Windows License Requirements... 6 User Type Limitations... 7 Windows 2000 Terminal Services Limitations... 8 Startup... 9 Shut Down...10 MWA Architecture Using MWA for Tenant Applications Johnson Controls, Inc. Code No. LIT Release 5.1

2 2 Metasys Web Access System Overview Technical Bulletin Metasys Web Access System Overview Introduction Metasys Web Access (MWA) provides M5 Workstation capabilities from a Windows 2000 Server/Windows 2000 Advanced Server computer with Terminal Services enabled to multiple remote users via Microsoft Internet Eplorer Web browser. When you access the MWA computer remotely through a Web browser, MWA uses the same user interface presentation as an M5 Workstation and uses the M5 screen manager to organize the screen space layout. By applying Microsoft Terminal Services, each user connected to the MWA computer essentially acts as a separate M5 Workstation and can use the M-Series applications to access data on integrated N1 and N30 networks. This document describes: related information M-Series features available with MWA MWA user types Microsoft Windows license requirements MWA user type limitations Windows 2000 Terminal Services limitations MWA startup MWA shut down MWA architecture using MWA for tenant applications

3 Metasys Web Access System Overview Technical Bulletin 3 Key Concepts Related Information Table 1 lists the literature related to MWA. Table 1: Related Information For Information On Refer to Metasys Web Access Installing and Commissioning Metasys Web Access Technical Bulletin (LIT ) Metasys Web Access User s Guide M5 Workstation M5 Workstation User s Guide Metasys Operator Workstation (OWS) M-Trend M-Graphics M-Authorize M-Eplorer M-Command M-View M-Inspector M-Schedule, M-Calendar M-Alarm M-Password N30 Objects N1 OLE for Process Controls (OPC) Data Access Server N1 OPC Alarm and Event (AE) Server BACnet OPC Alarm Server N1 Trend Collector M-Collector N30 Supervisory Controller M-Alarm Multimedia Site Book Metasys Data Visualization (MDV) Metasys Historical Data Visualization (MHDV) Operator Workstation User s Guide Operator Workstation Technical Bulletin (LIT ) M-Trend User s Manual M-Graphics User s Manual Using M-Authorize Technical Bulletin (LIT ) M-Eplorer User s Guide M-Schedule/M-Calendar User s Guide M-Alarm User s Guide M-Password Technical Bulletin (LIT ) M-Password Application Actions Technical Bulletin (LIT ) Object Dictionary Appendi A: N1 OPC Data Access Server Technical Bulletin (LIT ), Appendi B: N1 OPC Data Access Server Advanced Concepts Technical Bulletin (LIT ) M-Alarm User s Guide: Using M-Alarm with the N1 OPC Alarm and Event Server (LIT ) M-Alarm User s Guide: Using M-Alarm with the BACnet OPC AE Server (LIT ) N1 Trend Collector (LIT ) chapter of the M5 Workstation User s Guide Using M-Collector Technical Bulletin (LIT ) N30 Supervisory Controller User s Guide M-Alarm Multimedia User s Guide Site Book User s Guide (LIT ) Analog Profile Product Bulletin (LIT ), Comfort Chart Product Bulletin (LIT ), Starfield Display Product Bulletin (LIT ) Metasys Historical Data Visualization Installation Bulletin (LIT )

4 4 Metasys Web Access System Overview Technical Bulletin Hardware and Software Requirements Refer to the Metasys Installation and Platform Requirements Technical Bulletin (LIT-12012) for information on MWA hardware and software requirements. Features MWA features include: remote access to M-Series workstation applications through Microsoft Internet Eplorer Web browser ability to monitor and control objects for integrated Metasys N1 and N30 networks dynamic color graphics with animation capabilities (M-Graphics) personalized graphical interface for each user network navigation (M-Eplorer) and online object inspection (M-Inspector) alarm management (M-Alarm) versatile trend collection, storage, and analysis, plus graphical viewing of trend data (M-Trend) graphical scheduling for integrated N1 and N30 Networks consistent interface to integrated systems custom configurable screen layout using Screen Manager component support for Metasys Data Visualization (MDV) and Metasys Historical Data Visualization (MHDV) for integrated N1 and N30 objects Note: M-Alarm Multimedia (MMX) should not be installed on an MWA Server machine. The MMX load on the Alarm and Event server may cause serious performance issues for remote MWA users. We recommend loading MMX on a separate M5 Workstation.

5 Metasys Web Access System Overview Technical Bulletin 5 MWA User Types MWA functionality considers two types of users, the remote user and the local user. The type of user determines the etent of user restriction. The supported number of concurrently connected MWA users (5 or 10) may be connected either as an MWA local user or as an MWA remote user. If an operator is connected to MWA as an MWA local user, only up to 4 (for the 5 concurrent MWA product option) or 9 (for the 10 concurrent MWA product option) additional MWA remote users can connect to M-Graphics or to M-Alarm on MWA. Remote User The remote user performs the day-to-day Building Automation System (BAS) operational tasks and activities typically done through M-Series workstation component features. The remote user accesses the BAS with Internet Eplorer Web browser from a computer that does not have MWA installed on it. This user can only access M-Series components available through MWA and the Web browser. Windows Terminal Services limits client sessions to 256 colors. This color limitation will affect M-Components (for eample, M-Graphics and M-Alarm) configurations set higher than 256 colors. Windows 2000 Operating System (OS) finds the closest color match to graphics (for eample, bitmaps) set higher than 256 colors. To get the best color representation, create all new graphics using 256 colors. For eisting graphics set higher than 256 colors, open the graphics in a graphics program, load a 256-color palette, choose dither color (not match), and resave the graphics. See M-Series Components in Accessing MWA as a Remote User (LIT ) for details regarding remote user functionality. Local User The local user accesses the BAS system on the computer where MWA software is installed. A local user potentially has full access to all applications installed on the MWA computer. Applications specific to the local user include Metasys Person-Machine Interface (PMI) software and other software tools needed to configure the OPC servers and trend collectors for the integrated networks. When Metasys PMI is on a separate computer from MWA, you must use the IP address of the computer with Metasys PMI to configure the N1 OPC Data Access, AE Servers, and N1 Schedule.

6 6 Metasys Web Access System Overview Technical Bulletin Microsoft Windows License Requirements There are two types of licenses needed, the Windows 2000 Server Client Access License (CAL) and the Windows 2000 Terminal Services Client Access License (TS CAL). The MWA computer must have Per Server Windows 2000 Server CALs for the number of concurrently connected users. CALs are loaded with the Windows 2000 server OS. The number of CALs controls the number of users allowed to connect concurrently. Remote users can connect from any device, but only up to the number of Windows 2000 Server standard CALs. For eample, assume that you have installed the Windows 2000 Server OS with five Windows 2000 Server CALs but you have twelve users that may need to access the MWA, then all twelve users can access the MWA server, but only five can connect concurrently. Note: If the MWA computer was not properly configured for Per Server configuration during Windows 2000 OS installation, you can change it using Windows Licensing (Start menu > Programs > Administrative Tools > Licensing). In addition to the standard CALs for the Windows 2000 Server OS, each device (computer) that connects to the MWA server is required to have a TS CAL. TS CALs are loaded onto the Windows 2000 Server Terminal Services machine (MWA server). When a new device connects to this server, one of these TS CALs is issued. Accounting for issued TS CALs differs with the operating system of the connecting device: Every device with a Windows 98 OS, Windows NT OS, or Windows XP Home Edition OS uses one of the allocated TS CALs. Devices with a Windows 2000 Professional OS or Windows XP Professional OS do not get counted as using a TS CAL. The appropriate number of CAL and TS CAL licenses for the customer s site must be purchased from the Microsoft Corporation. Once you have purchased the Terminal Server License from the Microsoft Corporation, follow the instructions in this document to activate the server license and install the client licenses.

7 Metasys Web Access System Overview Technical Bulletin 7 User Type Limitations The functionality of M-Series components with MWA depends on the user type: local versus remote. A local user can access the complete functionality of the M-Series components. MWA restricts the use of some components by remote users. Table 2 lists software features and details the functionality available for each user type. Table 2: Software Feature Functionality by User Type Component Local User Remote User M-Graphics M-Eplorer for N30 network navigation N30 Object inspection with: M-Inspector tab Command M-Inspector tab View M-Inspector tab Schedule M-Inspector tab Calendar M-Eplorer for N1 network navigation N1 Object inspection with: M-Inspector tab Command M-Inspector tab Focus M-Inspector tab Schedule M-Inspector tab Point History M-Alarm M-Password Login M-Password Configuration Screen Manager M-Trend M-Authorization View Only MDV View Only MHDV View Only N1 OPC Data Access Server/Alarm and Event Configurators N1 Schedule Configurator Site Book M-Alarm Logger Configurator M-Collector N1 Trend Collector Metasys PMI (on MWA server) System Shutdown/Reset

8 8 Metasys Web Access System Overview Technical Bulletin Windows 2000 Terminal Services Limitations Windows 2000 Terminal Services imposes the following limitations on MWA. No support for 16-bit software applications, for eample Metasys Person-Machine Interface (PMI), to remote users Windows 2000 Terminal Services restricts 16-bit software applications to one instance. MWA does not support remote access to Metasys PMI features based on 16-bit technology. MWA does not support access to the traditional Metasys PMI features, including Network Map, Focus Windows, and online database generation. MWA does not support the OWS Eec functions for launching PMI tasks within an M-Graphics display. No support for software applications that do not support Windows 2000 Server OS Windows 2000 Terminal Services only supports software applications running on Windows 2000 Server OS. AspenTech InfoPlus.21 M-Historian option does not support Windows 2000 OS and is not supported by MWA. The Access Historian option is supported by MWA. No support for Netscape Navigator Web browser Windows 2000 Terminal Services supports only Microsoft Internet Eplorer Version 5.5 or later. Due to limited functionality of ActiveX controls on Netscape browsers, the Netscape browser is unable to run Terminal Services clients. Limits remote users to 256 colors Windows 2000 Terminal Services supports only 256 colors in graphics displays. Consider the following when using M-Graphics: Be careful using bitmaps. M-Graphics checks imported bitmaps for the number of colors used. If imported bitmaps contain more than 256 colors (8 bits), M-Graphics provides the option to reduce the number of colors to 256 for the imported bitmaps. Do not use multiple bitmaps within an M-Graphics display to avoid color palette switching. Avoid gradients in MWA M-Graphics displays. Verify that the number of colors used within all the embedded ActiveX controls in an M-Graphics display is less than 256 colors. This Terminal Services limitation may also impact any other M-Series Component features that provide displays with more than 256 colors.

9 Metasys Web Access System Overview Technical Bulletin 9 May impose network security issues when communicating through the Internet If the MWA application requires communication through firewalls, the Microsoft Windows 2000 Terminal Services software requires port 3389 to be open in the customer s firewall. Port 3389 provides support for the Remote Desktop Protocol. In addition, MWA communication to integrated N30 networks and third party BACnet devices requires opening port Firewalls enforce special rules to restrict the communication among computers, and usually restrict Web server and Internet communication to port 80. For details, refer to Installing and Commissioning Metasys Web Access Technical Bulletin (LIT ). Startup MWA startup for a Local User When a local user logs on, MWA: checks for MWA software authorization launches MWA screen manager (if configured) launches Metasys OWS (if installed on MWA computer) in the background integrates Metasys PMI launches GenTray application launches OPC Data Access and AE servers launches configured trend collectors MWA startup for a Remote User When a remote user connects to MWA, the computer: downloads the Remote Desktop Web Connection (RDP) ActiveX control to the remote user s computer (on first connection only) verifies the remote user s Windows 2000 Server/Advanced Server authentication When the remote user logs on to the computer, MWA: checks for MWA software authorization launches GenTray application launches MWA screen manager establishes a connection to OPC servers running locally on the MWA computer

10 10 Metasys Web Access System Overview Technical Bulletin Shut Down MWA Shut Down for a Local User When a local user shuts down, the local user: notifies remote users to log off releases connections eits screen manager shuts down the computer from the Windows Start menu MWA Shutdown for a Remote User The remote user cannot shut down the MWA computer. The remote user chooses log off or disconnect from the Windows Start menu of the MWA session. Note: If a remote user does not log off correctly (for eample, if the user closes the Web browser before logging off from the MWA session), the session stays active on the MWA computer. You can configure the automatic log off feature to end the session if the user does not log off from the MWA session correctly. Please refer to Configuring the Automatic Log Off Feature in the Installing and Commissioning Metasys Web Access Technical Bulletin (LIT ). MWA Architecture Figure 1 describes MWA system architecture with Metasys PMI on the same computer. MWA can communicate with a separate computer on an N1 network running Metasys PMI. In this case, the MWA computer does not require a local user to be logged in. Figure 2 describes the system architecture if Metasys PMI is on a separate computer. This configuration does not apply to N30 networks. If Metasys PMI is on a separate computer and the network contains multiple Operator Workstations (OWSs) on multiple N1 networks; the N1 OPC server, the N1 AE server, and the N1 Schedule server used by MWA must be configured to have only one path to any N1 network. Figure 3 describes how to configure MWA to communicate with multiple OWSs. Note: If MWA accesses Metasys PMI on a separate computer, the Metasys PMI computer has increased minimum requirements for processor speed and RAM.

11 Metasys Web Access System Overview Technical Bulletin 11 Internet access to MWA requires that Metasys PMI be on a separate computer. Refer to Installing and Commissioning Metasys Web Access Technical Bulletin (LIT ) for details about Internet access to MWA. Note: Do not install M3 or M5 Workstation software on the hardware platform that runs MWA software. M3 and M5 Workstation software do not support the Windows 2000 Server/Advanced Server operating system. Make sure that you have a separate M3 Workstation connected to the N30 network, or a separate M5 Workstation connected to the N1 or N30 network for performing any network configuration activities.` MWA Restrictions for Communicating to N1 Dial Networks and N1 Direct Networks Metasys Web Access (MWA) communication to N1 Dial and Network Controller (NC) Direct networks require that the network connection is performed through the Metasys PMI. MWA communication to all N1 Dial and NC Direct networks needs to have the capability for all available networks to be connected online concurrently. All Metasys networks must be concurrently accessible (have the capability to be online and connected) when the MWA server is in use. If all N1 Dial networks or NC Direct networks cannot be online concurrently, MWA remote users will not be able to communicate with these N1 Dial networks or NC Direct networks. When a single MWA server accesses multiple Metasys N1 Dial or NC Direct networks, all of the N1 Dial and NC Direct networks must be accessible (have the capability to be online and connected) at the same time that the MWA server is in use. This solution is required for any application where different MWA remote users may want to work with different N1 networks at the same time. MWA support for Metasys dial-up and NC Direct networks is limited to two networks by the number of RS-232 ports on the Metasys Operator Workstation (OWS) to which the MWA server is connected. As a result of this restriction, N1 network connections for a single MWA server are limited to one of the following: two NC Direct networks two N1 Dial networks (with two configured modems) one NC Direct network and one N1 Dial network All N1 Direct network connections must be configured to be online at the same time.

12 12 Metasys Web Access System Overview Technical Bulletin When accessing N1 Dial network data through M-Eplorer the very first time after the MWA server has been started, it takes time for MWA to get the data from the network, even though the PMI has already established communication to the N1 Dial network. The larger the N1 Dial network, the longer it takes, and it may take several minutes. During this time, the computer may alert you with a message saying, Server Busy- Retry or Switch To. Please wait. The computer returns to normal operation once the data has been collected by M-Eplorer. This delay only occurs the first time after the MWA application has been started or restarted. To minimize the likelihood of receiving this message, verify that the Permanent Object List (POL) database for the N1OPC data access server is up to date, see Generating POLs for Offline Browsing in Appendi A: N1 OPC Data Access Server Technical Bulletin (LIT ).

13 Metasys Web Access System Overview Technical Bulletin 13 User 1 User 2 User 3 User 10 Microsoft Internet Eplorer Web Browser 5.5 or later Microsoft Internet Eplorer Web Browser 5.5 or later Microsoft Internet Eplorer Web Browser 5.5 or later Microsoft Internet Eplorer Web Browser 5.5 or later Internet OR Intranet Windows 2000 Server/ Advanced Server OS (TSRVR) M-Series Components OPC Servers MWA Optionally: Analog Profile Starfield Display Comfort Chart Color Spectrum M-SAT M-Tools N1 Alarm and Event N1 Data Access NCM Comm Metasys 32-bit Communications N30 Alarm and Event N30 Data Access N30 Comm N30 Communications Metasys PMI UDP UDP RK Serial Comm IP Ethernet v2 PPP IP Ethernet v2 Net 1 Net 2 Net n Enterprise LAN or WAN NCM Devices N2 Bus N2 Devices N2 Bus N2 Devices N30 Controllers MWA1b Figure 1: MWA for Integrated N1 and N30 Networks (with Metasys PMI on the Same Computer)

14 14 Metasys Web Access System Overview Technical Bulletin User 1 User 2 User 3 User 10 Microsoft Internet Eplorer Web Browser 5.5 or later Microsoft Internet Eplorer Web Browser 5.5 or later Microsoft Internet Eplorer Web Browser 5.5 or later Microsoft Internet Eplorer Web Browser 5.5 or later Internet OR Intranet Windows 2000 Server/ Advanced Server OS (TSRVR) OPC Servers MWA Optionally: Analog Profile Starfield Display Comfort Chart Color Spectrum M-SAT M-Tools N1 Alarm and Event N1 Data Access R Windows 98/Windows NT /2000 Professional Metasys PMI NCM Comm Metasys 32-bit Communications Metasys UDP Metasys N1 Trend Collector RK Serial Comm IP Ethernet v2 Enterprise LAN or WAN Net 1 Net 2 Net N NCM Devices N2 Bus N2 Devices N2 Bus N2 Devices MWA2b Figure 2: MWA for Integrated N1 Networks (with Metasys PMI on a Separate Computer)

15 Metasys Web Access System Overview Technical Bulletin 15 N1OPC Configurator Site Name IP address OWS N1 AE Configurator Site Name IP address OWS N1Schedule Configurator IP address MWA OWS-201 MetaHost (MRS) IP MultiNet with connections to: NetA NetB NetC N1 Name: NetA UDP: Other N1 devices OWS-214 MetaHost (MRS) IP Single Net N1 Name: NetB UDP: Other N1 devices OWS-222 MetaHost (MRS) IP Single Net N1 Name: NetC UDP: Other N1 devices Figure 3: Multiple N1 Networks Connecting

16 16 Metasys Web Access System Overview Technical Bulletin Using MWA for Tenant Applications Although MWA is designed to provide a full day-to-day operator user interface, MWA can also be configured to provide a restricted user interface for tenant users. Tenants usually just want to control their own environment, such as the conditions in their offices. To set up this configuration, assign individual passwords for users to access just the M-Graphics that represent and include the conditions of their personal environment. For more details on how to define the network connection and user access for this group of users, please refer to the Installing and Commissioning Metasys Web Access Technical Bulletin (LIT ). Controls Group 507 E. Michigan Street P.O. Bo 423 Milwaukee, WI Published in U.S.A.