EFTA01225578.pdf

SOFTWARE HOUSE From Tyco Security Products C•CURE 9000 Version 2.50 Enterprise Architecture Guide REVISION HO um-252 HO EFTA01225578 C•CURE and Software House are registered trademarks of Tyco Security Products. The trademarks, logos, and service marks displayed on this document are registered in the United States [or other countries]. Any misuse of the trademarks is strictly prohibited and Tyco Security Products will aggressively enforce its intellectual property rights to the fullest extent of the law, including pursuit of criminal prosecution wherever necessary. MI trademarks not owned by Tyco Security Products are the property of their respective owners, and are used with permission or allowed under applicable laws. Product offerings and specifications are subject to change without notice. Actual products may vary from photos. Not all products include all features. Availability varies by region; contact your regional sales manager. Software version: 2.50 Document Number: UM-252 Revision Number: HO Release Date: December 2015 This manual is proprietary information of Software House. Unauthorized reproduction of any portion of this manual is prohibited. The material in this manual is for information purposes only. It is subject to change without notice. Software House assumes no responsibility for incorrect information this manual may contain. © 2015 Tyco Security Products. MI rights reserved. EFTA01225579  Table of Contents Preface 9 How to Use this Manual 10 Finding More Information 12 Conventions 13 Software House Customer Support Center 14 Chapter 1 - Application Server Overview 15 Introduction 16 Understanding The Enterprise Environment 18 Multi-version Support 19 Multi-version Server Synchronization 21 Multi-version Client Support 21 Multi-version Impact on Integrations 25 Using the Administration Client from the MAS 26 Setting the Application Server Interactive 29 Navigation Pane 30 Templates for Object Creation 30 Hardware Tree and Video Trees 30 Advanced Query Tab 31 Using the Administration Client from a SAS 31 Enterprise Architecture Capabilities Summary 32 Licensing 36 ML M2, M3, M4, M5 License Versions 36 Satellite Application Servers (SAS) 36 Validation 37 Chapter 2 - Application Server Architecture 41 Architecture Overview 42 Objects in the Enterprise Architecture 43 Typical Configuration 44 Editing Objects that Reside on a Different Server 45 Editing a SAS Local Object from the MAS 45 C•CURE 9000 Enterprise Architecture Guide 3 EFTA01225580  Server Synchronization 47 Synchronization Results 49 Chapter 3 - Configuring an Enterprise Architecture 51 Setting Up an Enterprise Architecture .52 Privileges in Enterprise Architecture 53 System All Global Privilege 53 Access to Global Common Objects 54 Access to Common Objects 54 Client Access Privileges 56 Operators In Enterprise Architecture 58 Privilege Schedules for Operators 58 Operator Application Server Tab 58 Operator Configuration 60 Accessing the Operator Editor 60 Client Configuration 62 Primary Connection to the MAS 62 Primary Connection to a SAS 63 Dynamic Views in Enterprise Architecture 64 Dynamic View Restrictions 64 Holidays in Enterprise Architecture 66 Chapter 4 - Application Server Editor 67 Application Server Dynamic View 68 Viewing a List of Application Servers 70 Application Server Context Menu 72 Application Server Synchronization Conflicts View 74 Synchronization Conflict View from the MAS 74 Synchronization Conflicts View from a SAS 75 Synchronization Conflicts View Definitions 76 Using the Synchronization Conflicts View 77 Synchronization Conflicts Definitions 79 Application Server Editor 87 Application Server Tasks 87 Accessing The Application Server Editor 87 Using the Application Server Editor 88 Application Server General Tab 89 General Tab Definitions 89 Application Server Groups Tab 91 Adding an Application Server to a Group 91 Application Server Synchronization Tab 92 4 C•CURE 9000 Enterprise Architecture Guide EFTA01225581  Audit Log Synchronization 92 Journal Synchronization 92 Synchronization Tab Tasks 92 Application Server Triggers Tab 94 Application Server State Images Tab 97 State Images Tab Definitions 97 Viewing a List of Application Servers 97 Application Server Context Menu 99 Chapter 5 - Partitions in Enterprise Architecture 101 Partition Overview 102 Types of Partitions 102 Objects and Partitioning 104 Moving Objects to Another Partition 104 Global Only Objects 105 Group Objects 106 Optionally Global Objects 107 Non-Global Objects 109 System Defined Non-Global Objects 110 Editable Intrinsic Local Objects 111 Non-editable Intrinsic Local Objects 112 Non-global MAS Objects 112 Chapter 6 - Personnel in Enterprise Architecture 113 Personnel Overview 114 Configuring Personnel in Enterprise Architecture 115 Global Personnel 117 Global Clearances 119 Assigning Clearances to Personnel from a Dynamic View 119 Global Custom Clearances 120 Custom Clearances and Door/Elevator Groups 120 Removing Expired Custom Clearances from a Personnel Record 120 Disabling Credentials for Inactivity in Enterprise Architecture 121 Editing User-defined Fields in Enterprise Architecture 122 Editing Customer Tab Field Labels 123 Editing C•CURE ID Objects in Enterprise Architecture 124 CHUIDs in an Enterprise 125 Applying CHUID Formats 125 CHUID Templates 125 Handling Credential CHUID Uniqueness Conflicts 125 Query to find Duplicate CHUIDs 126 C•CURE 9000 Enterprise Architecture Guide 5 EFTA01225582  Running a Query for Duplicate CHUIDs in Credentials 127 Personnel Type in Enterprise Architecture 128 Images in Enterprise Architecture 129 Chapter 7 - Hardware in Enterprise Architecture 131 Configuring Hardware in Enterprise Architecture 132 apC Support on a SAS System 134 ISC Controllers are Not Supported on SAS or MAS 134 Chapter 8 - Video in Enterprise Architecture 135 Configuring Video in Enterprise Architecture 136 Chapter 9 - System Variables in Enterprise Architecture 139 System Variables Overview 140 System Variables Dynamic View 141 Personnel Related System Variables 143 Auto Increment Card Number System Variables 143 Disable by Inactivity Enabled and Disable by Inactivity Scan Time System Variables 143 Maximum Clearances Per Person System Variable 143 Maximum Custom Clearances Per Person System Variable 144 PIN Length System Variable 144 Audit/Journal Synchronization System Variables 146 Audit Synchronization System Variable 146 Journal Synchronization System Variable 146 Restarting Drivers When Changing System Variables 147 Chapter 10 - Journal/Audit In Enterprise Architecture 149 Using Journal and Audit Logs in Application Server 150 Synchronizing Log Files 150 Audit Logs 150 Log Management 151 Using System Variables for Synchronization 151 Using an Event to Manually Synchronize Log Files 151 Journal Messages 153 Journal Triggers in an Enterprise 153 Chapter 11 - Central Reporting in Enterprise Architecture 155 Central Reporting 156 Retrieving Enterprise Data 156 Pre-configured Reports 156 Operator Privileges 157 The Reports Dynamic View 157 8 C•CURE 9000 Enterprise Architecture Guide EFTA01225583  Chapter 12 - Central Management in Enterprise Architecture 159 Central Management Overview 160 Central Administration 161 Features: 161 Capabilities: 161 Master Database 161 Application Layouts 162 Default Server 162 Creating Views for Central Monitoring Operators 162 Action Constraints 163 Setting Application Servers Interactive 164 Setting a Server Interactive from the Administration Station 164 Setting a Server Interactive from the Monitoring Station 165 Central Monitoring Station 166 Central Monitoring Overview 166 Features 166 Operator Privileges 166 Master Database 166 Application Layouts 166 Capabilities 167 Receiving Activity Messages 167 Receiving Event Messages 167 Viewing Swipe and Show Activity 167 Central Monitoring Explorer Bar 168 Selecting Objects 169 Components 169 Central Monitoring and Privileges 170 Operator Access 170 Central Monitoring and Actions 171 Using Context Menu Actions 171 Central Monitoring - Performing Manual Actions 171 Chapter 13 - Enterprise Architecture Backup and Restore 173 Back Up and Restore for C•CURE 9000 in an Enterprise System 174 How Synchronization Interacts with Backup and Restore 174 Re-Synchronizing Servers after a Database Restore from Backup 175 Chapter 14 - Import and Export in an Enterprise 177 Importing Data in Enterprise Architecture 178 Import Watcher in the Enterprise Architecture 178 Exporting Data in Enterprise Architecture 178 C•CURE 9000 Enterprise Architecture Guide 7 EFTA01225584  Appendix A - Enterprise Architecture FAQ 179 Enterprise Architecture FAQ 180 Index 187 8 C•CURE 9000 Enterprise Architecture Guide EFTA01225585  Preface The C•CURE 9000 Enterprise Architecture Guide is for new and experienced security system users who want to learn to use this product for the C•CURE 9000 Security Management System. In this preface How to Use this Manual 10 Finding More Information 12 Conventions 13 Software House Customer Support Center 14 C•CURE 9000 Enterprise Architecture Guide Preface 9 EFTA01225586 How to Use this Manual How to Use this Manual This manual contains chapters that provide the following information about C•CURE Application Server. Chapter 1: Application Server Overview This chapter introduces the Enterprise Architecture option, explaining its concept, structure, features, and capabilities. Chapter 2: Application Server Architecture This chapter outlines the Enterprise Architecture configurations and the concept of synchronization. Chapter 3: Configuring an Enterprise Architecture This chapter explains how to configure the Enterprise Architecture. Chapter 4: Application Server Editor This chapter describes the Application Server editor. Chapter 5: Partitions in Enterprise Architecture This chapter describes the use of Partitions in a Enterprise Architecture. Chapter 6: Personnel in Enterprise Architecture This chapter explains how Personnel is managed in Enterprise Architecture. Chapter 7: Hardware in Enterprise Architecture This chapter explains how access control hardware is configured and managed in an Enterprise environment. Chapter 8: Video in Enterprise Architecture This chapter explains how video security hardware is configured and managed in an Enterprise environment. Chapter 9: System Variables in Enterprise Architecture This chapter outlines the use of system variables in an Enterprise Architecture. 10 Preface C•CURE 9000 Enterprise Architecture Guide EFTA01225587 How to Use this Manual Chapter 10: Journal/Audit In Enterprise Architecture This chapter explains the Journal and Audit capabilities in the Enterprise Architecture. Chapter 11: Central Reporting in Enterprise Architecture This chapter describes the central reporting capability of the Enterprise Architecture. Chapter 12: Central Management in Enterprise Architecture This chapter explains how to perform central monitoring in an Enterprise Architecture. Chapter 13: Enterprise Architecture Backup and Restore This chapter describes the backup and restore capabilities of Enterprise Architecture. Chapter 14: Import and Export in an Enterprise 'Ibis chapter describes the Import and Export capabilities of Enterprise Architecture. Appendix A: Enterprise Architecture FAQ This appendix provides questions and answers about the Enterprise Architecture. C•CURE 9000 Enterprise Architecture Guide Preface 11 EFTA01225588 Finding More Information Finding More Information You can access C•CURE 9000 manuals and online Help for more information about C•CURE 9000. Manuals C•CURE 9000 software manuals are available in Adobe PDF format on the C•CURE 9000 DVD. You can access the manuals if you copy the appropriate PDF files from the C•CURE 9000 Installation DVD English \ Manuals folder. The available C•CURE 9000 and Software House manuals are listed in the C• CURE 9000 Installation and Upgrade Guide, and appear as hyperlinks in the online.pdf file on the C•CURE 9000 DVD English \ Manuals folder. These manuals are also available from the Software House Member Center website Online Help You can access C•CURE 9000 Help by pressing Fl or clicking Help from the menu bar in the Administration/Monitoring Station applications. 12 Preface C•CURE 9000 Enterprise Architecture Guide EFTA01225589 Conventions Conventions This manual uses the f >Bowing text formats and symbols. Convention Meaning Bold This font indicates screen elements, and also indicateswhen you should take a direct action in a procedure. Bold font describes one of the following items: • A command or character to type, or • A button or option on the screen to press, or • A key on the keyboard to press • A screen element or name blue color text Indicates a hyper link to a URL. or a cross-reference to a hgure. table. or section in this guide. Regularitak !oaf Indicates a new term. <text> Indicates a variable. The following items are used to indicate important information. Indicates a note. Notes call attention to any item of information that may be of special importance. NOTE Indicates an alternate method of performing a task. TIP 0 Indicates a caution. A caution contains information essential to avoid damage to the system. A caution can pertain to hardware or software. Indicates a warning. A warning contains information that advises users that failure to avoid a specific action could result in physical harm to the user or to the hardware. STOP Indicates a danger. A danger contains information that users must know to avoid death or serious injury. C•CURE 9000 Enterprise Architecture Guide Preface 13 EFTA01225590 Software House Customer Support Center Software House Customer Support Center Telephone Technical Support During the period of the Agreement, the following guidelines apply: • Software House accepts service calls only from employees of the Systems integrator of Record for the installation associated with the support inquiry. Before Calling Ensure that you: • Are the Dealer of record for this account. • Are certified by Software House for this product. • Have a valid license and current Software Support Agreement (SSA) for the system. • Have your system serial number available. • Have your certification number available. Hours Normal Support Hours Monday through Friday. 8O0IMI. to 8:00 . EST. Except holidays. Emergency Support Hours 24 hours/day, seven days a week. 365 days/year. Requires Enhanced SW? x2r Standby Telephone Support (emergency) provided to Certified Technicians. For allother customers. billable on time and materials basis. Minimum charges appty- See MSRP. Phone For telephone support contact numbers for all regions. see 14 Preface C•CURE 9000 Enterprise Architecture Guide EFTA01225591  Application Server Overview This chapter introduces the Enterprise Architecture option and explains how C•CURE 9000 servers operate in an enterprise environment. In this chapter Introduction 16 Understanding The Enterprise Environment 18 Multi-version Support 19 Using the Administration Client from the MAS 26 Licensing 36 C•CURE 9000 Enterprise Architecture Guide Chapter1 15 EFTA01225592 Introduction Introduction The C•CURE 9000 Enterprise Architecture is a licensable option that allows you to configure multiple C•CURE 9000 servers to communicate with a Master Application Server. The Master Application Server (MAS) provide a platform for global management of the Personnel, Video, and access security objects on two or more Satellite Application Servers (SAS) in an enterprise. Figure 1: Basic Configuration: One MAS and Two SAS Systems CCURE 9000 Mow Am:so:won Server thiAS) For Control Monitoring Central Reporting Global Managemerl tin PC (MAS) Satellite APPItcation Szietite Apprication Server 1 Server 2 Client PC -SAS Client PC -31152 O STAR Video Video Ccradlet Server S•ne( The Enterprise Architecture works by synchronizing each SAS system's database with the MAS database. The Master (MAS) contains the global data that is used across every server, such as global Personnel records, global clearance, and global Operators. The global data is synchronized to each SAS so that it can be used to implement enterprise- wide security. The MAS itself does not have any directly connected controllers or video servers, but it can be used to remotely monitor and manage controllers and video servers attached to SAS's in the enterprise. See Typical Configuration on Page 44 for more information. The MAS provide the capability for Central Monitoring of the entire enterprise, using the C•CURE 9000 Monitoring Station application. From a central Monitoring Station connected to the MAS, you can view Events, Activities, and status on every SAS in the enterprise. Alternatively, you can connect to a particular SAS to monitor that system and its connected hardware. See Central Monitoring Station on Page 166 for more information. In addition, the MAS provide a Central Reporting capability, because its database include information about all objects that are replicated from the satellite servers. See Central Reporting on Page 156 for more information. Each Satellite (SAS) server contains database records for the video and access security hardware connected to it, as well as local personnel, clearance, privilege, and other data. Each SAS synchronize with the Master so that SAS local data is replicated to the MAS for central management and monitoring. 16 Chapter1 C•CURE 9000 Enterprise Architecture Guide EFTA01225593 Introduction MI data is synchronized immediately when saved (or queued if a server is offline), except for Journal and Audit data, which is synchronized on a configurable schedule. Network latency and load on the MAS and SAS databases can effect synchronization performance. Operator Privileges are used to provide system users with exactly the information they need, and deny access to information they do not need or should not be able to view. These capabilities let you deploy multiple C•CURE 9000 servers in an enterprise environment, solving scalability and wide area network issues and providing a platform for central monitoring, global management, and central reporting. Starting with a baseline of version 2.40 Service Pack 2, the MAS and each SAS in an Enterprise can be NOTE running different versions of C•CURE 9000, as long as the MAS installed version is equal to or later than the SAS version on each server. If the MAS uses version 2.50, then each SAS must use either version 2.40 Service Pack 2 or version 2.50. C•CURE 9000 Enterprise Architecture Guide Chapter 1 17 EFTA01225594 Understanding The Enterprise Environment Understanding The Enterprise Environment The Enterprise Architecture provides an administrator with the ability to view and manage all aspects of access control and video security from one application - the Administration Workstation attached to the MAS. From this vantage point, you can: • View and edit all Personnel, Credentials, and Clearances. • Configure and manage all access control hardware. • Configure and manage all video security hardware. • Create Queries and Reports that can summarize data from every server in the Enterprise, or from a limited subset of data based on a Query you construct. (Status values are not synchronized from SAS to MAS, so reports on the MAS cannot provide the latest status values.) Using the Administration Client from the MAS on Page 26 explains how a client application attached to the MAS provides the ability to choose whether to view and manage the entire enterprise or to view and manage a specific SAS system from a central location. Using the Administration Client from a SAS on Page 31 explains how a client application attached to a SAS differs in scope but provides the ability to configure Global and local objects from the SAS. The Enterprise Architecture also provides the ability to perform Central Monitoring from a Monitoring Station client application attached to the MAS. See Central Monitoring Station on Page 166. You can create and run Centralized Reports from a client application attached to the MAS. See Central Reporting on Page 156 18 Chapter 1 C•CURE 9000 Enterprise Architecture Guide EFTA01225595 Multi-ver SC 71 Support Multi-version Support For an established Enterprise consisting of a MAS and one or more SAS systems, upgrading to a new version of C•CURE 9000 is a large and potentially formidable task. Previously, the MAS needed to be upgraded first, and then each SAS would be upgraded one-by-one, without any ability to connect to the MAS previous to their upgrade. For a large Enterprise this could mean that some SAS systems would be out of contact with the MAS for a considerable time. To overcome this problem, C•CURE 9000 is providing Multi-version support - the ability for SAS systems not yet upgraded to the version the MAS is running to connect to the MAS, synchronize records, identify conflicts, and attach clients to the MAS to configure and monitor the Enterprise. From the MAS perspective, a Global Operator has the ability to attach to both upgraded and non-upgraded SAS systems, with some limitations due to the version differences. The Multi-version process begins with an Enterprise where the MAS and every SAS is currently at the same version, and the MAS is upgraded. Therefore, only two versions of C•CURE 9000 can be involved: ■ The new version to which the MAS has been upgraded ■ The previous version at which all SAS systems were operating. If an Enterprise currently has a MAS at one version and SAS systems with differing versions, it is necessary to update all SAS systems to be at the same version as the MAS to establish a common baseline, prior to beginning to upgrade the MAS to take advantage of Multi-version support. The intention still is to proceed with upgrading every SAS to match the new MAS version. The difference is that until that point, all the SAS systems can participate in the Enterprise, within version-specific limitations. To enable upgraded clients to communicate with previous version SAS systems, during the upgrade a copy is made of the C•CURE 9000 client applications from the previous version so that these applications can be launched when needed if the upgraded client detects it is running in a Multi-version Enterprise. Example: If a Global Operator on the MAS opens the Monitoring Station, and that Operator is currently interactive with SAS systems that have been upgraded and some SAS systems that have not been upgraded, separate Monitoring Station windows open: ■ The current upgraded version of the Monitoring Stations is opened for upgraded SAS systems that are interactive. ■ The previous version of the Monitoring Station is opened for SAS systems that have not been upgraded and are interactive. C•CURE 9000 Enterprise Architecture Guide Chapter 1 19 EFTA01225596 Alulleverson Support Figure 2: Multi-version Client Example C•CURE 9000 Master Aophcauco Server (MAS) Satellite Appica:o-, Server 2 VIOUS SION Previous Version Monitoring Station See the C•CURE 9000 Release Notes for the upgrade version to determine the previous versions that are supported for Multi-version in a given release. The following table summarizes the capabilities provided by Multi-version support. 20 Chapter! C•CURE 9000 Enterprise Architecture Guide EFTA01225597 Multi-version Support Table 1: Multi-version Support Capabilities Summary Category Effects Multi-version Server Synchronization occurs between the upgraded MAS and alprevious version SAS systems, but data differences Synchronization resulting from the upgrade are not synchronized. When a SAS is upgraded, the MAS and SAS re-synchronize to take care of any data not previously synchronized. See Multi-version Server Synchronization on Page 21. See Table 2 on Page 22 for detals on the supported connections and limitations. Mutti-verson Client Client applications that are upgraded can attach to upgraded MAS and SAS, but have limftations in communicating Support with previous version SAS systems. Client applications that are not upgraded are limited to connecting to previous version SAS systems, with limitations. See Mutti-version Client Support on Page 21. Mutti-verson Integration A previous version Integration that Is not enterprise-aware wilcontinue to operate with a previous version SAS, but Impact not with an upgraded MAS or SAS. An upgraded Integration wal only work correctly with an upgraded SAS, because the Integration's instaler wilnot retain the previous version of the integration to launch when communicating with a previous version SAS. See Multi-version Impact on Integrations on Page 25. Mufti-version Server Synchronization Multi-version Support changes the way that data is synchronized between the MAS and each SAS in two respects: ■ Synchronization is allowed to occur if the SAS version of C•CURE 9000 is different from the MAS version. However data differences resulting from the MAS upgrade are not synchronized (these differences are flagged in the database, however, so that they can be synchronized at a later time). ■ When the SAS is upgraded to match the MAS version, the MAS and SAS re-synchronize to take care of any data not previously included in the Multi-version synchronization. The status of Multi-version synchronization for an Enterprise is summarized on the Application Server Dynamic View on Page 68, so that you can readily determine the Multi-version synchronization status between a SAS and the MAS, or between the MAS and all SAS systems. Multi-version Client Support The way a client application behaves in the Multi-version Enterprise depends upon the server(s) to which the client application connects. When you launch a client application in a Multi-version environment, a message box is displayed to tell you how the client is affected by operating in that Multi-version environment. Example: You launch an upgraded Monitoring Station client that connects to the MAS. The following message appears to let you know you are operating in a Multi-version Enterprise: You are running this dient while your Enterprise is in the process of upgrading. The dientfimdionality is limited to performing tasks on objects owned by servers that match your version of the client. As a result, the 'Default Server' and C•CURE 9000 Enterprise Architecture Guide Chapter! 21 EFTA01225598 Mufti-version Support 'Read Data from' server lists only contain servers that are compatible with your dient. Where applicable, Right-click menus are disabled for objects owned by incompatible servers. When running the Monitoring Station (MS), the upgraded MS automatically starts the previous version of the MS so that you can monitor newly both upgraded servers and ones that haven't been upgraded yet. Each version of the MS is limited to loading Application layouts that reference compatible servers. If your Monitoring Station client was configured to be interactive with both upgraded and previous version SAS systems, your upgraded Monitoring Station client displays information from the upgraded SAS systems, and launches a previous version of the Monitoring Station to display information from any interactive previous version SAS systems. Table 2 on Page 22 below applies to remote clients - a client application on one system connecting to a C•CURE 9000 server on a different system. A local client residing on a server is assumed to be connecting to its local server using the same version between client and server. Table 2: Client Support ha Multl-Version Environment Client Connect to: Supported? Details Previous Previous Supported Connected to a previous version SAS. the user cannot edit Global ohpects. with the exception version version SAS with of adding and removing PersonnelClearances. tvlonrtoring (with restrictions If the user attemptstodouble-chckon a Global °Died the following status message isdisplayed Station Upgraded asa bubble from the Administration client ton in the Notification area (lower right corner) of Client MAS in the the display: Enterprise) You aro running in a Multi-Version environment and the object that you have selected is incompatible with this version of the client. Previous Previous Supported Connected to a previous version SAS. the user cannot edit Global objects. with the exception version version SAS with of adding and removing Personnel Clearances. Admin (with restrictions The previous version Admin client limits the user to selecting partitions owned by the SAS Client Upgraded server in the 'New Object' drop down list. NIAS in the Enterprise) This restriction results in the 'right-click' context menu being disabled for all Global objects except Personnel obscts and then by further restricting the supported commands to Assign Clearances and Remove Clearances . If the user attempts to double-click on a Global ObjeCt the following status message isdisplayed asa bubble from the Administration client ton in the Notification area (lower right corner) of the display: You aro running in a Multi-Version environment and the object that you have selected is incompatible with this version of the dent. 22 Chapter 1 C•CURE 9000 Enterprise Architecture Guide EFTA01225599 Multi-version Support Table 2: Client Support in a Mufti-Version Environment (continued) Client Connect to: Supported? Details Previous Upgraded Supported The Monitoring Station only loads Application Layouts belonging to servers that match its version MAS (with with version. Monitoring Multi-version restrictions If a Monitoring Station hasApplication Layouts that can be interactive with both upgraded and Station SAS systems in previous version servers, the layouts are onty interactive with compatible (previous version) the Enterprise) SefVers. The Monitoring Station does not allow the user to select an incompatible (upgraded) server in the Read Data fromdrop-down list. The drop-down list will onty show compatible servers. The Monitoring Station only shows Events and Activities associated with objects that belong to servers that haven't been upgraded. If the user selects a Global object in a Dynamic View, the following message is displayed as a bubble from the Administration client icon in the Notification area (lower right corner) of the displa