ADX Commissioning

ADS/ADX Commissioning GuideLIT-1201645MS-ADSxxx-x MS-ADXxxx-x

Software Release 6.0Issued January 30, 2013Supersedes May 13, 2011

Refer to the QuickLIT website for the most up-to-date version of this document.

Document Introduction.............................................................................................................4Related Documentation.............................................................................................................4Commissioning the ADS Overview..........................................................................................4

Application and Data Server (ADS)...................................................................................................4ADS Device Object..............................................................................................................................5Site Director.........................................................................................................................................6Repositories........................................................................................................................................6Trend Repository Database..................................................................................................................7Audit Repository Database...................................................................................................................7Event Repository Database..................................................................................................................8Annotation Repository Database..........................................................................................................9Metasys Reporting Repository Database.............................................................................................9System Security for the ADS/ADX.....................................................................................................9Time Zone, Date, and Time Management........................................................................................10Email, Pager, SNMP Trap, and Printer Agents...............................................................................10Email DDA...........................................................................................................................................10Pager DDA..........................................................................................................................................10SNMP Trap DDA.................................................................................................................................11Printer DDA.........................................................................................................................................11Antivirus Software............................................................................................................................11Printing Information Displayed on the User Interface...................................................................11Receiving Data from Remote NAEs/NCEs or NIEs........................................................................11Additional Configuration Notes.......................................................................................................11An ADS and ADX on the Same Site...................................................................................................12Dial Out to a Remote NAE/NIE Device...............................................................................................12Uninterruptible Power Supply.............................................................................................................12

Detailed Procedures................................................................................................................13Configuring an ADS/ADX as Site Director......................................................................................13Configuring an ADS/ADX as Site Director with One ADS/ADX..........................................................13Configuring One ADS/ADX as Site Director with Multiple ADS/ADX Devices....................................13Configuring an ADS/ADX as Site Director if You Delete the Current Site Director.............................13Configuring ADS/ADX Repositories................................................................................................13Setting the Time Zone, Date, and Time on an ADS/ADX...............................................................14Setting up a Local or Network Printer on an ADS/ADX for Windows 7 OS, Windows Server 2008R2 OS, or Windows Server 2008 OS...............................................................................................14Setting up a Local or Network Printer on an ADS/ADX for Windows XP Professional OS........18Setting up a Local or Network Printer for Scheduled Reports Output................................................19Configuring an ADS/ADX to Accept Dial-Up Connections...........................................................20Configuring Dial-Up Connections for Windows 7 OS,Windows Server 2008 R2 OS, or Windows Server2008 OS..............................................................................................................................................20Configuring Dial-Up Connections for Windows XP Professional OS..................................................21Using the IIS Lockdown Wizard, Version 2.1..................................................................................22Removing User Accounts from a Demoted Site Director.............................................................26Changing the Site Director..................................................................................................................26

1ADS/ADX Commissioning Guide

http://cgproducts.johnsoncontrols.com/default.aspx

Moving the Security Database and Clearing It from the Demoted Site Director.................................26Configuring Metasys System Settings...........................................................................................26Changing Metasys Log on Screen Background..................................................................................26Changing the Action Queue Timeout..................................................................................................27Creating Audit Entries for Discard Events...........................................................................................27Configuring Metasys Advanced Reporting System Settings.......................................................27Refreshing the Metasys Advanced Reporting System Data Manually...............................................28Changing Metasys Advanced Reporting System Settings for IIS 7.5.................................................28Changing Metasys Advanced Reporting System Settings for IIS 7.0.................................................29Changing the Archive Database Used by the Metasys Advanced Reporting System (ADX Only).....30

Troubleshooting.......................................................................................................................32Split ADX Troubleshooting...............................................................................................................32Backup and Restoration of the SQL Server Databases................................................................32Using Communication Log Files.....................................................................................................32Windows Log File Cleanup..............................................................................................................33ADS/ADX and SCT Temporary File Cleanup..................................................................................34ADS/ADX Startup Failures...............................................................................................................34Folders in the Windows Event Viewer on the ADS/ADX...............................................................35Anti-Spyware Software on the ADS/ADX Computer......................................................................35

Technical Specifications.........................................................................................................36Application and Data Server (ADS) System Requirements .........................................................36Application and Data Server-Lite System Requirements .............................................................37Extended Application and Data Server System Requirements (Unified ADX) ...........................38Extended Application and Data Server System Requirements (Split ADX)................................39Extended Application and Data Server System Requirements (Unified 50 User ADX) .............41

Appendix: Time Zone, Date, and Time Management............................................................43Time Zone, Date, and Time Management Introduction..................................................................43Overview of Time Synchronization.................................................................................................43ADS/ADX Site Director with NAEs/NIEs.............................................................................................43NIE and Child Devices........................................................................................................................44Time Synchronization Methods.......................................................................................................44Windows Time Synchronization..........................................................................................................44Multicast Time Synchronization..........................................................................................................44BACnet Time Synchronization............................................................................................................45Example Network..............................................................................................................................45Time Zone..........................................................................................................................................45Site Time Server................................................................................................................................46Time in Device Object and UI Status Bar........................................................................................46Steps for Successful Time Management........................................................................................46Verifying the Site Director Defined for an Engine/Server....................................................................47Setting the Time Synchronization Method..........................................................................................47NAE/NIE Is the Site Director...............................................................................................................48ADS/ADX Is the Site Director..............................................................................................................50Configuring Additional Multicast Time Synchronization Settings........................................................53

Appendix: Changing the Name and the Computer Name....................................................55Changing the ADS/ADX Name and the Computer Name on an ADS and Unified ADXIntroduction.......................................................................................................................................55Overview of Changing the ADS/ADX Name and the Computer Name...............................................55Preparing the Computer......................................................................................................................55Using an Existing Archive or Creating a New Archive........................................................................57Uninstalling and SCT Software...........................................................................................................57

Renaming the Computer.....................................................................................................................58Verifying SQL Server Software and Reporting Services.....................................................................59Reinstalling Metasys Software............................................................................................................59Downloading the ADS/ADX................................................................................................................59Finalizing ADS/ADX Settings..............................................................................................................60Uploading ADS/ADX Name Changes to the SCT...............................................................................60

Appendix: Configuring and Maintaining Preferences..........................................................62Configuring and Maintaining Preferences Introduction................................................................62Preferences Concepts......................................................................................................................62System and User Preferences............................................................................................................62Managing Preferences........................................................................................................................64Detailed Procedures.........................................................................................................................65Configuring Preferences.....................................................................................................................65Restoring Default System Preferences...............................................................................................65Copying Preferences between Devices..............................................................................................65Restoring Default User Preferences...................................................................................................65Removing User Preference Files........................................................................................................65Copying User Preferences to Another User........................................................................................66Preserving Preferences in an Upgrade...............................................................................................66

Appendix: Microsoft® Windows® Operating System (OS) and SQL Server™ SoftwareLicense Requirements.............................................................................................................67Windows OS License Requirements......................................................................................67

Operating System CALs...................................................................................................................67Licensing Modes and CAL Examples.............................................................................................69

SQL Server Licensing Requirements.....................................................................................69ADS Requirements..................................................................................................................70Purchasing and Designating CALs........................................................................................70Appendix: Moving Historical Data From Existing ADS/ADX Installation...........................72

Important Considerations................................................................................................................72Moving Historical Data From Existing ADS/ADX Installation Introduction.................................72Preparing the New ADS/ADX Computer.........................................................................................73Preparing the Old ADS/ADX Computer...........................................................................................73Restoring the System to the New ADS/ADX Computer.................................................................75

Document IntroductionThis document describes how to commission the Application Data Server (ADS) or the Extended Application andData Server (ADX) as part of the Metasys® system. Use this document to configure the ADS/ADX the first time orto change the configuration of the ADS/ADX on an existing site. Also covered is the procedure for moving theADS/ADX application and databases to a different computer.

Note: In this document, the term ADS includes ADS-Lite except where noted. The term NAE includes the NAE45-Liteexcept where noted. These products are available only to specific markets. Contact your Johnson Controls®representative for details.

Related DocumentationTable 1: ADS/ADX Commissioning Related Documentation

LIT or Part NumberSee DocumentFor Information On

LIT-12017931Metasys system HelpSite Object Configuration and the MetasysSystem User Interface (UI)

LIT-1201525Application and Data Server (ADS/ADX) ProductBulletin

ADS/ADX Features and Benefits

LIT-12011521ADS, ADX, and SCT Installation and UpgradeInstructions Wizard2

Installation and Upgrade of ADS/ADXSoftware

LIT-12011688ADS-Lite Installation and Upgrade InstructionsWizard2

Installation and Upgrade of ADS-LiteSoftware

Part No. 24-10067-1Metasys System Extended Architecture LicenseInformation

License Information

LIT-1201527Metasys System Extended Architecture OverviewTechnical Bulletin

Metasys System (General)

LIT-1201534SCT Technical BulletinSystem Configuration Tool (SCT) Software

LIT-1201528Security Administrator System Technical BulletinMetasys System Security and Permissions

LIT-1201519NAE Commissioning GuideNetwork Automation Engine (NAE)

LIT-120113421Ready Access Portal HelpReady Access Portal UI

LIT-12011523Ready Access Portal Software InstallationInstructions

Ready Access Portal Software Installationand Administrator Tasks

LIT-1201639Metasys System Extended Architecture DirectConnection and Dial-Up Connection ApplicationNote

Direct Connections or Dial-up Connections

LIT-1201654Software License Activator Technical BulletinHow to License the ADS/ADX

1 This LIT number represents a print-friendly version of the Help.2 Use the wizard to generate instructions specific to your system.

Commissioning the ADS OverviewThe importance of commissioning the ADS/ADX relates to the Microsoft® Licensing requirements. Refer tohttp://www.microsoft.com and see Appendix: Microsoft® Windows® Operating System (OS) and SQL Server™Software License Requirements for details on licensing.

The ADS/ADX software contains features and configurations that are not set up by the installation. This documentdescribes how to set up and modify the configuration of the ADS/ADX to better suit the needs of your facility.

Application and Data Server (ADS)The ADS is a scalable platform that serves multiple users and provides database software options for archivinghistorical data using the Microsoft SQL Server 2008 Express software database.


http://www.microsoft.com

The extended version of the Application and Data Server, the ADX, serves a larger number of users and providesmore extensive historical data storage using the SQL Server 2008 software database. The ADX may also beconfigured in a split configuration, where the web/application components of the ADX reside on a dedicatedweb/application server and the historical databases of the ADX reside on a dedicated database server.

For ADS/ADX hardware and software requirements, refer to the Metasys System Extended Architecture OverviewTechnical Bulletin (LIT-1201527).

Note: We recommend that you do not install or run additional software on the ADS/ADX computer such as wordprocessors, games, Computer Aided Drafting (CAD) software. Only install and run the software listed in theADS, ADX, and SCT Installation and Upgrade Instructions Wizard Content (LIT-12011331) or the ADS-LiteInstallation and Upgrade InstructionsWizard Content (LIT-12011689), including ADS/ADX, SCT, and antivirussoftware.

ADS Device ObjectThe user interface organizes the ADS device object attributes (Figure 1) in the UI tabs described in Table 2. TheObject Type and Model Name of an ADX are both shown as ADS in the Focus window for the ADS device object.

Figure 1: ADS Device Object


Table 2: UI Tabs of the ADS Device ObjectOnline/SCT1PurposeTab

Both2Description of device including information related to site. The tab alsoincludes general information about the ADS Repository, particularly ifhistorical data needs to be forwarded to other ADS Repositories.

Focus/Configuration

OnlineName, value, status, and description for Trend Study or User Graphicitems in the ADS

Summary

OnlineHTTP messaging information for diagnostic purposesDiagnostic

BothE-mail configuration and destination informationEmail

BothPager configuration and destination informationPager

BothSimple Network Management Protocol (SNMP) configuration anddestination information

SNMP

BothAlarm printer configuration and destination informationPrinter

1 Online refers to the tabs you see when looking at the ADS/ADX UI. SCT refers to the tabs you see when looking at an archivedatabase in the SCT.

2 The Focus tab appears online and the Configuration tab appears in the SCT.

Site DirectorThe Site Director provides all users a uniform point of entry to the system and the ability to view all network componentsincluding the information defined in the site object. The Site Director supports functions such as user login, useradministration, and time synchronization. On a Metasys site, only one ADS/ADX server can be configured as theSite Director.

All User Views created for a site need to reside on the ADS/ADX configured as the Site Director. Typically, the usergraphics created for a site also reside on the Site Director ADS/ADX.

RepositoriesImportant: To store historical data successfully, you must enter values for two system attributes. First, the Default

ADS Repository attribute in the Site object defines where historical data is stored. Second, the ADSRepository attribute in the engine/server determines where the device sends historical information. Bydefault, these attributes are blank. Be sure to enter the address/name of your repository device (typicallythe Site Director) in these attributes to ensure you do not lose historical data. For the Site Director itself,leave the ADS Repository attribute blank if the Site Director also serves as the repository.

A repository provides long-term storage for historical data. Typically, the ADS/ADX configured as the Site Directoralso provides the individual repositories for trend data, event messages, audit messages, annotations, and reporting.Individual repositories may reside in the SQL Server 2008 software database and/or the SQL Server 2008 Expresssoftware database. For a split ADX, the repositories are on the database server computer where the SQL Serversoftware is installed.

If necessary, when you are not using an ADS-Lite, you can optimize the performance of the trend, event, audit,annotation, and reporting repositories by installing multiple ADS/ADX servers on a site and configuring each ADS/ADXas a repository for a limited number of NAE, Network Control Engine (NCE), or Network Integration Engine (NIE)devices. Alternatively, you can also install a split ADX where the database server computer stores all historical data.

Note: The ADS-Lite cannot be a Site Director for other ADSs of any kind.

Table 3 lists the ADS/ADX repositories, the corresponding online Metasys system Help (LIT-1201793) topic, andthe corresponding file name. The next sections describe the repositories in more detail and suggest ways to optimizethe repositories.


Table 3: ADS/ADX RepositoriesDatabase File Name on the ADS/ADXComputer

Metasys System Help (LIT-1201793)Topic

Repository

JCIHistorianDBTrend ExtensionTrends

JCIAuditTrailsAudit TrailAudits

JCIEventsAlarm and Event ManagementEvents

JCIItemAnnotationEvent Message AnnotationsAnnotation

MetasysReportingAdvanced ReportingReporting

Trend Repository DatabaseOverviewThe Trend repository database resides on the ADS within the SQL Server 2008 Express software database and onan ADX within the SQL Server 2008 software database. The folder location of the database files that store trenddata is determined during the ADS/ADX installation.

If you are using Microsoft Windows 7 OS, Windows Server® 2008 R2 OS, or Windows Server 2008 OS, the defaultdirectory location is:

C:\ProgramData\Johnson Controls\MetasysIII\SQLData

If you are using Microsoft Windows XP® Professional OS, the default directory location is:

C:\Documents and Settings\All Users\Application Data\Johnson Controls\MetasysIII\SQLData

Note: The installation program places the Trend repository on the same computer where the ADX software resides.For a split ADX, the directory location is on the database server computer on the same drive where the SQLServer software is installed. During installation, you can change where the databases are loaded (Drive:\path).

The ADS/ADX performance degrades as the number of trend samples coming in to the ADS/ADX Trend repositoryincreases, and the frequency of the trend samples to be stored in the Trend repository increases, depending on thehardware resources used for the ADS/ADX computer.

Trend Repository OptimizationOptimize the required storage size of the ADS/ADX Trend repository using the following methods:

• configure larger sample intervals on individual trends• determine which trends to store long-term and configure only those trends to transfer their samples• define the Trend extension to sample on Change-of-Value (COV) with a larger COV increment for noncritical

point objects

In addition, optimize the network communication performance for transferring trend samples from NAE/NCE or NIEdevices to the ADS/ADX repository using the following methods:

• configure the Transfer Setpoint on individual trends so they transfer their samples at different intervals than othertrends

• use the ADS Delivery Time of the NAE/NCE or NIE device to transfer the samples at the time when user accessto the system is minimal

Refer to the Trend Extensions topic in the Metasys system Help (LIT-1201793) for more information.

Audit Repository DatabaseAudit Repository Database OverviewThe Audit Repository resides on the ADS within the SQL Server 2008 Express software database and on an ADXwithin the SQL Server 2008 software database. During the ADS/ADX installation, you can determine the folderlocation of the database files that store Audit messages.


If you are using Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS, the default directorylocation is:


If you are using Windows XP Professional OS, the default directory location is:


The installation program places the Audit repository on the same computer where the ADX software resides. For asplit ADX, the directory location is on the database server computer on the same drive where the SQL Server softwareis installed. During installation, you can change where the databases are loaded (Drive:\path).

The ADS/ADX performance degrades as the number of audit samples coming in to the ADS/ADX Audit repositoryincreases and the frequency of the audit samples to be stored in the Audit repository increases, depending on thehardware resources used for the ADS/ADX computer.

Audit Repository OptimizationOptimize the required storage size of the ADS/ADX Audit repository by specifying the Audit level (1 through 4) forthe audit messages that need to be reported and archived.

In addition, optimize the network communication performance for transferring audit messages from NAE/NCE orNIE devices to the ADS/ADX Event repository by optimizing the Audit repository size in the device object of eachNAE/NCE or NIE.

Audit Level 1 provides the minimum information. Audit Level 4 provides the most information. Audit Level 2 is thedefault setting. Refer to the Audit Trail topic in the Metasys system Help (LIT-1201793) for more information.

Event Repository DatabaseEvent Repository OverviewThe Event repository resides on the ADS within the SQL Server 2008 Express software database and on an ADXwithin the SQL Server 2008 software database. You may view and acknowledge ADS/ADX alarms and events inthe event repository. The newest and highest priority alarm or event that requires acknowledgement appears in theAlarms window. Use the Event Viewer to see all the events in a device repository. When the device repositoryreceives an acknowledgement either from the UI or through a Web service, the original source device of the alarmis notified.

During the ADS/ADX installation, you can determine the folder location of the database files that store event messages.





The installation program places the Audit repository on the same computer where the ADX software resides. For asplit ADX, the directory location is on the database server computer on the same drive where the SQL Server softwareis installed. During installation, you can change where the databases are loaded (Drive:\path).

The ADS/ADX performance degrades as the number of event samples coming in to the ADS/ADX Event repositoryincreases and the frequency of the event samples to be stored in the Event repository increases, depending on thehardware resources used for the ADS/ADX computer.

Event Repository OptimizationOptimize the required storage size of the ADS/ADX Event repository by only defining alarm extensions for pointobjects for which event messages need to be processed and archived.


In addition, optimize the network communication performance for transferring event messages from NAE/NCE orNIE devices to the ADS/ADX Event repository by optimizing the Alarm repository size in the device object of eachNAE/NCE or NIE.

Refer to the Alarm and Event Management section in the Metasys system Help (LIT-1201793) for more information.

Annotation Repository DatabaseThe Annotation repository resides on the ADS within the SQL Server 2008 Express software database and on anADX within the SQL Server 2008 software database. The Annotation repository contains all optional annotationsentered manually for items in the All Items tree.

During the ADS/ADX installation, you can determine the folder location of the database files that store annotations.





The installation program places the Annotation repository on the same computer where the ADX software resides.For a split ADX, the directory location is on the database server computer on the same drive where the SQL Serversoftware is installed. During installation, you can change where the databases are loaded (Drive:\path).

The ADS/ADX performance degrades as the number of annotations coming in to the ADS/ADX Annotation repositoryincreases and the frequency of the annotation samples to be stored in the Annotation repository increases, dependingon the hardware resources used for the ADS/ADX computer. The Annotation repository requires no special optimizationbecause the repository only grows in size as the number of annotations increases.

Metasys Reporting Repository DatabaseThe Metasys Reporting repository database resides on an ADX within the SQL Server 2008 software database. TheMetasys Reporting repository contains Metasys Advanced Reporting System information and Metasys EnergyEssentials configuration information.

The folder location of the database files that store reporting information is determined during the ADS/ADX installation.The default directory location is:


Note: The installation program places the Metasys Reporting repository on the same computer where the ADXsoftware resides. For a split ADX, the directory location is on the database server computer on the samedrive where the SQL Server software is installed. During installation, you can change where the databasesare loaded (Drive:\path).

System Security for the ADS/ADXThe Security Administration System protects access to the ADS/ADX and requires users to enter a user ID andcomplex password when logging on to the ADS/ADX. For greater security, change the default password for theMetasysSysAgent user immediately after you install or upgrade the ADS/ADX software. For details, refer to theSecurity Administrator System Technical Bulletin (LIT-1201528) or the Change Password topic in Metasys Help(LIT-1201793).

Metasys system passwords must meet the following complexity requirements, in which the password must includeat least:

• six characters• one upper case letter• one number


A user with the Administrator Role can edit the security database by adding users, modifying user IDs and passwords,and assigning object category-based privileges and system access privileges.

When the ADS/ADX is the Site Director, its Security Administration System function controls access to the entiresite. The assigned object category-based privileges and system access privileges affect the permissions grantedfor the user logged on to the Site Director.

The ADS/ADX also allows you to log on using the Microsoft Active Directory® directory service. For details, refer tothe Security Administrator System Technical Bulletin (LIT-1201528).

When the ADS/ADX is not the Site Director (used only as a repository for data storage), its local Security AdministrationSystem function is used for user authentication for direct access to this ADS/ADX. The assigned system accessprivileges affect the permissions granted for the user who is directly logged on to this ADS/ADX. The Site Director,where users normally log on to the system, provides the effective Security Administration System function for site-wideaccess. On sites with multiple ADS/ADX devices, the Site Director security database must be copied to all of theother ADS/ADX devices to support the latest alarm and event features. For information on backing up and copyingsecurity databases, refer to the Metasys system Help (LIT-1201793).

Note: The ADS-Lite cannot be Site Director for other ADS devices of any kind.

The Security database can only be viewed and modified in the online system at the Site Director by a user with theAdministrator Role. If you want to maintain the same Security database for all ADS/ADX devices, back up the archivedatabase (which includes the Security database) of the Site Director with the SCT and then copy this Securitydatabase to all ADS/ADX devices on the site.

For more information on System Security, including setting up roles and users, refer to the Security AdministratorSystem Technical Bulletin (LIT-1201528).

We recommend that you implement Secure Sockets Layer (SSL) security for improved protection of user passwordswhen using the Metasys Advanced Reporting System. Refer to theNetwork and IT Guidance for the BAS ProfessionalTechnical Bulletin (LIT-12011279) for details on how to implement SSL security.

Time Zone, Date, and Time ManagementSee Setting the Time Zone, Date, and Time on an ADS/ADX for information on time zone, date, and timemanagementon your network.

Email, Pager, SNMP Trap, and Printer AgentsThe ADS/ADX uses an agent called the Destination Delivery Agent (DDA) to route event messages to other mediaand devices, like e-mail or a pager. The ADS/ADX supports the DDAs in this section.

Note: For more information on how to configure the DDA, refer to the Metasys system Help (LIT-1201793).

Email DDAThe Email DDA supports the standard Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP), andInternet Message Access Protocol (IMAP) for sending event messages to an e-mail account. For details on how toconfigure the Email DDA, refer to the Metasys system Help (LIT-1201793).

The Email DDA maintains a log file of recent communication. For more information, see Using Communication LogFiles in Troubleshooting.

Pager DDAThe Pager DDA supports the standard Telocator Alphanumeric Protocol (TAP) for sending event messages to apager. For details on how to configure the Pager DDA, refer to the Metasys system Help (LIT-1201793).

The ADS/ADX does not support modems on the serial port.

The Pager DDA maintains a log file of recent communication. For more information, see Using Communication LogFiles in Troubleshooting.


SNMP Trap DDASimple Network Management Protocol (SNMP) is a protocol governing network management and the monitoring ofnetwork devices and their functions. It is not necessarily limited to Transmission Control Protocol/Internet Protocol(TCP/IP) networks. SNMP monitoring is typically used for large Building Automation System (BAS) networks withmany network devices. Alarm and event notifications are sent to and stored on an SNMP management computerthat monitors all devices on the network.

The ADS/ADX uses SNMP protocol to deliver network device status and conditions to a designated SNMPmanagement computer. SNMP monitoring must be set up at the network level, and an SNMP management devicemust be assigned on the network. If you are applying a Metasys system to an existing network, consult with thenetwork administrator or IT department that administers the network to determine if SNMP monitoring is availableon the network. Configure custom SNMP messages and specify the SNMP message destinations in the SNMP tabof the Metasys UI.

Release 3.0 and later provide enhanced SNMP functionality on Metasys systems, including a Metasys systemManagement Information Base (MIB) file for configuring third-party SNMP translation applications to request, receive,and translate specified SNMP trap messages generated by the Metasys SNMP DDA.

Printer DDAThe Printer DDA is only available on the ADS/ADX for sending event messages to printers. The Printer DDA supportsany printer type supported by the Windows® operating system on which the ADS/ADX is installed. The Printer DDAalso supports IP based network printers (but not Novell® NetWare printers) and printers that are connected to theADS/ADX by parallel or USB port. The ADS/ADX supports printing to multiple printers at one time.

Antivirus SoftwareFrequent virus scans of the computer running the ADS/ADX are necessary to maintain the integrity of your system.We recommend one of the following antivirus software programs:

• Symantec® Endpoint Protection software Corporate Edition Version 11.0 or later• McAfee® Active VirusScan® software Version 8.5 or later

For details on how to install and configure Symantec Endpoint Protection software for use on an ADS/ADX, refer tothe ADS, ADX, and SCT Installation and Upgrade Instructions Wizard (LIT-12011521).

Printing Information Displayed on the User InterfaceAny printer supported by the computer's operating system can be used to print the content of any panel displayedon the Metasys system UI. The supported printers include IP network printers and printers connected using a USBor parallel port. Printing through Novell NetWare services is not supported.

Receiving Data from Remote NAEs/NCEs or NIEsAn ADS/ADX may be configured to receive (via a dial-up connection) and store trend, alarm, and audit data fromindividual, remote NAEs/NCEs/NIEs that are not on the same site as the ADS/ADX.

Each remote NAE/NCE/NIE must have its own modem, and each NAE/NCE/NIE must be configured to dial theADS/ADX. Refer toConfiguring an NAE to Dial Out to an ADS/ADX in theNAE Commissioning Guide (LIT-1201519)for information on setting up an NAE/NIE to dial an ADS.

To use a Multi Tech® MT5634ZBA-USB 56k, V.90 external USB modem in Metasys system networks requires the8.27L Version or higher of the Multi Tech modem firmware installed on the modem.

The ADS/ADX does not support modems on the serial port.

The ADS/ADX must also be configured to accept incoming dial-up connections. See Configuring an ADS/ADX toAccept Dial-Up Connections. Refer to the Metasys System Extended Architecture Direct Connection and Dial-UpConnection Application Note (LIT-1201639) for details on how to set up a computer to connect directly or via a dial-upconnection to an NAE/NCE/NIE device.

Additional Configuration NotesWhen configuring your Metasys system site, consider the notes in this section.


An ADS and ADX on the Same SiteWhile it is possible to install both an ADS and an ADX on the same site (with the restriction that an ADS-Lite cannotbe the Site Director for ADSs of any kind), historical data cannot be shared between the two computers. The repositoryfiles only exist on one ADS/ADX computer or on the database server computer in the split ADX. The NAE/NCE/NIEcan send historical records to only one repository computer.

Dial Out to a Remote NAE/NIE DeviceUse a computer that runs on Windows XP Professional operating system for setting up a dial-in or direct connectionto an NAE/NCE/NIE device. For more detailed information on configuring direct and dial-up connection, refer to theMetasys System Extended Architecture Direct Connection and Dial-Up Connection Application Note (LIT-1201639).

Uninterruptible Power SupplyWe recommend connecting the ADS/ADX to a reliable Uninterruptible Power Supply (UPS) to avoid data loss in theevent of a power outage. Contact your Johnson Controls representative or see the computer price list for UPSrecommendations.


Detailed ProceduresConfiguring an ADS/ADX as Site DirectorThe ADS/ADX installation process defaults each ADS/ADX to be its own Site Director. When addingmultiple ADS/ADXdevices to a site for providing additional repositories, only one ADS/ADX can be configured as the Site Director.

Note: The ADS-Lite cannot be Site Director for another ADS of any kind.

Note: If an ADS/ADX is already designated as the Site Director, you must first remove the Site Director designationfrom that ADS/ADX. Use this procedure for the current Site Director and clear Site Director in Step 3. Thenrepeat as directed for the new Site Director.

1. From the ADS/ADX UI, open the Site Object.2. Click Edit.3. In the Site Director drop-down list, select the correct Site Director.4. Click Save.

Configuring an ADS/ADX as Site Director with One ADS/ADXBy default, a single ADS/ADX on the site is the Site Director.

Configuring One ADS/ADX as Site Director with Multiple ADS/ADX DevicesTo configure one ADS/ADX as Site Director with multiple ADS/ADX devices, use the System Configuration Tool(SCT) and define all ADS device objects and the Site objects. The first Metasys server (ADS/ADX) inserted into theSCT archive database automatically becomes the Site Director. If you define multiple Metasys servers (ADS/ADXdevices), the top Metasys server shown in the All Items navigation tree of the SCT archive database automaticallybecomes the Site Director.


Note: After completing the system configuration, perform a download to all ADS/ADX servers with the SCT toensure that only the ADS/ADX defined in the Site object is configured as the Site Director and all otherADS/ADX servers are configured as repositories.

If necessary, change the Site Director in the Site object. See Configuring an ADS/ADX as Site Director.

Configuring an ADS/ADX as Site Director if You Delete the Current Site DirectorIf you define multiple Metasys Servers (ADS/ADX devices) and you delete the ADS/ADX that is defined as the SiteDirector, the top Metasys server shown in the All Items navigation tree of the SCT archive database automaticallybecomes the Site Director.


If necessary, change the Site Director in the Site object. See Configuring an ADS/ADX as Site Director.

Note: After completing the system configuration, perform a download to all ADS/ADX devices with the SCT toensure that only the ADS/ADX defined in the Site object is configured as the Site Director and all otherADS/ADX servers are configured as repositories.

Configuring ADS/ADX RepositoriesThe ADS/ADX installation process allows the user to define the folder locations of the database files for ADSrepositories. There are three typical configurations:

• The ADS/ADX is the Site Director and the ADS repository.• The ADS/ADX is the Site Director and a different ADS is the ADS repository.• The ADX is split so the web/application server computer is the site director and the database server computer

is the repository.


Note: Even though the database server computer hosts the Repository, each NAE/NCE/NIE is configured to haveits repository entry directed to the ADX web/application server computer. The ADX web/application serveraccepts the data from the NAE/NCE/NIE and then writes the data to the repository on the database servercomputer. There is never any direct communication between an NAE/NCE/NIE and the database servercomputer.

1. Open the ADS object.2. Set the objects and devices according to Table 4.

Note: Each ADS/ADX that is configured as a repository has the capability to forward the historical data (trendsamples and alarm/event messages) received from an NAE/NCE/NIE device to other ADS/ADX repositoriesas defined in the Repository Storage (list) in its device object. The ADS/ADX does not forward Audit Trails.

Table 4: Configuring ADS RepositoriesEnter This ValueIn This FieldDevice or ObjectConditionIts own computer nameLocal Site DirectorOn the ADS/ADX (Site Director)If the ADS/ADX Is Both the

Site Director and the ADSRepository Not used - leave blankADS Repositories

The computer name of the SiteDirector

Local Site DirectorOn an NAE


ADS Repository

Its own computer nameLocal Site DirectorOn the ADS/ADX (Site Director)If an ADS/ADX Is the SiteDirector and a Different ADSIs the ADS Repository The computer name of the ADS

RepositoryADS Repositories


Local Site DirectorOn the ADS/ADX (ADSRepository)1

Not usedADS Repositories


Local Site DirectorOn an NAE or Any Other ADS

The computer name of the ADSRepository

ADS Repository(ies)

Its own computer nameLocal Site DirectorOn the ADS/ADX (Site Director)If the ADX Is Split and theWeb/Application ServerComputer Is the Site Directorand the Database ServerComputer Is the Repository

Not used - leave blankADS Repositories


Local Site DirectorOn the NAE or Any Other ADS

The computer name of theweb/application servercomputer2

ADS Repository(ies)

1 If an ADS/ADX is the repository for all NAE/NIE devices, verify that its computer name is entered as Default ADS Repositoryin the Site object and also as Default ADS Repository in all NAE/NIE device objects. If this ADS/ADX is the repository only forparticular NAE/NIE devices, verify that its computer is entered as ADS Repository only for these NAE/NIE device objects.

2 The ADX web/application server actually accepts the data from the NAE/NIE and then writes the data to the repository on thedatabase server computer.

Setting the Time Zone, Date, and Time on an ADS/ADXSee Appendix: Time Zone, Date, and Time Management for information on setting the time zone, date, and timemanagement on your network.

Setting up a Local or Network Printer on an ADS/ADX for Windows 7 OS,Windows Server 2008 R2 OS, or Windows Server 2008 OSNote: This procedure sets the printer as the destination for the Printer DDA.

1. Make sure the printer power is on and is connected to the computer or building network.


2. Click Start, then click Control Panel > Hardware and Sound.3. Select Add a Printer under the Printers or Devices and Printers section. TheChoose a local or network printer

screen appears (Figure 2). For Windows 7 OS, this screen has the same content but is labeledWhat type ofprinter do you want to install?

Figure 2: Choose a Printer Port Screen

4. Select theAdd a local printer option (even if the printer is a network printer). TheChoose a printer port screenappears (Figure 3).

Figure 3: Choose a Printer Port Screen

5. For a network printer, select Create a new port and select Standard TCP/IP Port from the drop-down list. Goto Step 6.

For a local printer, select Use an existing port and select the appropriate port from the list. Go to Step 8.


6. Click Next. The Type a printer hostname or IP address screen appears (Figure 4).

Figure 4: Type a Printer Hostname or IP Address Screen

7. Enter the host name or IP address of the printer. The Port name field autofills while you type the host name orIP address. Keep the Query the printer check box selected (the default).

Note: If you are uncertain about the proper printer host name to use, print a test page from the printer and lookfor the Printer name line in the test printout. Copy the name and syntax exactly. You may otherwisespecify the IP address of the printer in the Hostname or IP address field.

8. Click Next. If the printer driver cannot be retrieved from the printer, the Install the printer driver screen appears(Figure 5).

Figure 5: Install the Printer Driver Screen


9. Select the printer manufacturer and locate the model number in the Printers list box. If the printer model is notlisted, click Have Disk and select the appropriate printer driver on a network drive, local hard drive, or othermedia.

10. Click Next to continue. The Type a printer name screen appears (Figure 6).

Figure 6: Type a Printer Name Screen

11. Accept the default printer name or type a name to identify the printer. Set this printer as the default printer if theoption is available.

12. Click Next to continue. If you are using Windows 7 OS, a Printer Sharing screen appears. Select the Do notshare this printer option. Click Next.

The printer driver installation begins. When it is finished, the final Add Printer screen appears (Figure 7).

Figure 7: Final Add Printer Screen

13. If you want to test the printer, click Print a test page.14. Click Finish to complete the printer installation.


Setting up a Local or Network Printer on an ADS/ADX for Windows XPProfessional OSNote: This procedure sets up the printer as the destination for the Printer DDA.

1. Make sure the printer power is on and is connected to the computer or building network.2. From the Start menu, select Settings > Printers and Faxes. Click the Add Printer icon. The Add Printer Wizard

appears.3. Click Next. The Local or Network Printer screen appears (Figure 8).4. Click Local printer attached to this computer (even if the printer is a network printer).5. Clear the Automatically detect and install my Plug and Play printer check box (Figure 8).

Figure 8: Local or Network Printer Screen

6. Click Next. The Select a Printer Port screen appears (Figure 9).

Figure 9: Select a Printer Port Screen

7. For a network printer, click Create a new port. From the Type drop-down list, select Standard TCP/IP Port.The Add Standard TCP/IP Printer Port Wizard appears. Go to Step 8.

For a local printer, click Use the following port. From the list, select the appropriate port. Go to Step 10.8. Click Next. The Add Port screen appears (Figure 10).


Figure 10: Add Port Screen

9. Enter the name or IP Address of the printer. The Port name field autofills while you type the host name or IPaddress.

Note: If you are uncertain about the proper printer name to use in the Add Port screen, print a test page fromthe printer and look for the Printer name line in the test printout. Copy the name and syntax exactly. Youmay otherwise specify the IP Address of the printer.

10. Click Next. The Additional Port Information Required screen appears (Figure 11).

Figure 11: Additional Port Information Required Screen

11. If the printer has multiple ports, select the correct printer port. Click Next to continue.12. Follow the instructions on the screen to complete the printer setup.

Setting up a Local or Network Printer for Scheduled Reports OutputThe Scheduled Reports feature allows you to send report output directly to a printer connected to or accessible withthe Site Director ADS/ADX. Follow the steps in this section.

1. On the ADS/ADX computer, create a new Windows OS user using the standard procedure specific to yourparticular Windows OS.

2. Restart the computer and log on as the new user you created in Step 1.


3. If you are using Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS, follow the stepsin Setting up a Local or Network Printer on an ADS/ADX for Windows 7 OS, Windows Server 2008 R2 OS, orWindows Server 2008 OS.

If you are using Windows XP Professional OS, follow the steps in Setting up a Local or Network Printer on anADS/ADX for Windows XP Professional OS.

4. If a restart is required, log on as the new user you created in Step 1.5. Set the printer you added in Step 3 as the default printer for the new user.6. Print a test page to verify that printing works for the new user.7. If the new user account has Administrator privileges, go to Step 8.

If the new user account does not have Administrator privileges, log off and then log on with a user account thathas Administrator privileges. This action enables you to perform the remaining steps in this section.

8. Open Control Panel on the ADS/ADX computer and select Administrative Tools > Services.

If you are using Windows 7 OS or Windows Server 2008 R2 OS, select Control Panel > System and Security> Administrative Tools > Services. Click Yes to continue if the User Account Control prompt appears.

If you are using Windows Server 2008 OS, select Control Panel > System and Maintenance > AdministrativeTools > Services. Click Continue if the User Account Control prompt appears.

9. In the Services window, right-click Metasys III Action Queue and select Properties.10. On the Log On tab, click This account.11. Enter the new user’s name in the This account field and the new user’s password in the Password andConfirm

password fields.12. Click OK.13. In the Services window, right-click Metasys III Action Queue and select Restart.14. Test the printer by creating a scheduled report in the ADS/ADX that is configured to go to that printer. Refer to

the Metasys system Help (LIT-1201793) for details on the Scheduled Reports feature.

Configuring an ADS/ADX to Accept Dial-Up ConnectionsFor an ADS/ADX to receive data via a dial-up connection from NAEs/NCEs/NIEs, each remote NAE/NCE/NIE musthave its own modem and phone line connection, and each NAE/NCE/NIE and modem must be configured to dialthe ADS/ADX. Refer to theConfiguring an NAE to Dial Out to an ADS/ADX section in theNAECommissioning Guide(LIT-1201519) for information on setting up an NAE/NIE to dial an ADS/ADX.

Note: The ADS/ADX does not support modems on the serial port.

• For Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS, see Configuring Dial-UpConnections for Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS.

• For Windows XP Professional OS, see Configuring Dial-Up Connections for Windows XP Professional OS.

Configuring Dial-Up Connections for Windows 7 OS, Windows Server 2008 R2 OS, orWindows Server 2008 OS1. Install the modem on the computer running the ADS/ADX, following the modem manufacturer instructions.2. Click the Start menu or button and select Control Panel > Network and Internet > Network and Sharing Center.3. If you have Windows 7 OS or Windows Server 2008 R2 OS, click Change adapter settings in the left pane.

A screen showing existing network connections appears.

If you have Windows Server 2008 OS, click Manage network connections in the left pane under Tasks.4. If the Menu bar is not shown, press the Alt key. A row of menu options appear on the screen.5. Select File > New Incoming Connection. Click Continue or Yes if prompted by the User Account Control dialog.

The Allow connections to this computer screen appears.6. Select an existing user account or click Add someone to add a new user.7. Click Next.


8. Select the correct modem to accept the incoming connections and click Next.9. Select Internet Protocol Version 4 (TCP/IPv4) only. It does not matter if you are not able to clear other options.10. Click Properties.11. Clear Allow callers to access my local area network.12. Select Specify TCP/IP addresses and type in the addresses:

• If the NAEs using this connection are configured for Dynamic Host Configuration Protocol (DHCP), but noDHCP server exists on the network, the recommended range is from 192.168.77.44 to 192.168.77.47.

• In other scenarios, the recommended range is from 169.254.77.44 to 169.254.77.47.

Note: The recommended IP range allows up to three simultaneous dialing connections to the ADS/ADX.Increasing the suggested range increases the number of simultaneous connections available. The IPrange is not necessarily a limit on the number of modems, only the number of modems with a connectedcall in to the ADS/ADX.

Configure the ADS Repository attribute of the NAEs/NCEs/NIEs that dials this ADS/ADX as the first IPAddress in the range of addresses chosen in this step (that is, either 192.168.77.44 or 169.254.77.44).

13. Click OK to return to the wizard.14. Click Allow access.15. Click Close on the screen that confirms the connection has been configured.

Configuring Dial-Up Connections for Windows XP Professional OS1. Install the modem on the computer running the ADS/ADX, following the modem manufacturer instructions.2. Open Control Panel and double-click Network Connections. The Network Connections window appears.3. Click New Connection Wizard. The New Connection Wizard appears. Click Next.4. Select Set up an advanced connection and click Next.5. Select Accept Incoming Connections and click Next.6. Select the correct modem to accept the incoming connections and click Next.7. Select Do not allow virtual private connections and click Next.8. Select an existing user or click Add to add a new user.9. Click Next.

Note: The user name and password must match the NAE Internet Service Provider (ISP) user name andpassword.

10. Select Internet Protocol (TCP/IP) only. It does not matter if you are not able to clear other options.11. Click Properties.12. Clear Allow callers to access my local area network.13. Select Specify TCP/IP addresses and type in the addresses:

• If the NAEs using this connection are configured for Dynamic Host Configuration Protocol (DHCP), but noDHCP server exists on the network, the recommended range is from 192.168.77.44 to 192.168.77.47.

• In other scenarios, the recommended range is from 169.254.77.44 to 169.254.77.47.

Note: The recommended IP range allows up to three simultaneous dialing connections to the ADS/ADX.Increasing the suggested range increases the number of simultaneous connections available. The IPrange is not necessarily a limit on the number of modems, only the number of modems with a connectedcall in to the ADS/ADX.

Configure the ADS Repository attribute of the NAEs/NCEs/NIEs that dials this ADS/ADX as the first IPAddress in the range of addresses chosen in this step (that is, either 192.168.77.44 or 169.254.77.44).

14. Click OK to return to the wizard.15. Click Next.16. Click Finish.


Using the IIS Lockdown Wizard, Version 2.1Note: This section applies only to Windows XP Professional OS. Skip this section if you have Windows 7 OS,

Windows Server 2008 R2 OS, or Windows Server 2008 OS.

IIS Lockdown Wizard is a security tool, available from the Microsoft Corporation, designed to address securityconfiguration problems within the Internet Information Server (IIS). The IIS Lockdown Wizard functions by providingtemplates to turn off unnecessary features of the IIS, therefore reducing the attack surface available to hackers. Thistool is not a substitute for good security practices or applying critical system updates on a regular basis.

Note: Perform these instructions only after the ADS/ADX software is installed on the computer.

1. Navigate to http://download.microsoft.com/download/iis50/Utility/2.1/NT45XP/EN-US/iislockd.exe and clickOpen. The Welcome to the Internet Information Services Lockdown Wizard screen appears (Figure 12).

Note: You can also click Save and save the file (iislockd.exe) to your computer.

Figure 12: Welcome to the Internet Information Services Lockdown Wizard Screen

2. Click Next. The license agreement screen appears (Figure 13).


http://download.microsoft.com/download/iis50/Utility/2.1/NT45XP/EN-US/iislockd.exe

Figure 13: License Agreement Screen

3. If you agree to the license agreement, click I agree and click Next. The Select Server Template screen appears(Figure 14).

Figure 14: Select Server Template Screen

4. Select theDynamicWeb server (ASP enabled) template and clickNext. The URLScan screen appears (Figure15).


Figure 15: URLScan Screen

5. Verify that Install URLScan filter on the server is selected and click Next. The Ready to Apply Settings screenappears (Figure 16).

Figure 16: Ready to Apply Settings Screen

6. Click Next. The Applying Security Settings screen appears (Figure 17), and the Status field shows the progressof the wizard.


Figure 17: Applying Security Settings Screen

7. Click Next. The Completing the Internet Information Services Lockdown Wizard screen appears (Figure 18).

Figure 18: Completing the Internet Information Services Lockdown Wizard Screen

8. Click Finish.9. Using Windows Explorer, locate and open

...\SYSTEM32\INETSRV\urlscan\urlscan.ini using Notepad.10. Change AllowDotInPath=0 to AllowDotInPath=1.


11. Close and save urlscan.ini.12. Restart the computer.

You can undo the settings by executing iislockd.exe again. The program indicates that IIS lockdown has alreadybeen run and gives you the option to undo the changes. Any changes you make after the initial execution ofthe IIS Lockdown Wizard are lost. Refer to Microsoft software documentation for detailed information. TheURLScan application can only be removed using Add/Remove Programs.

Removing User Accounts from a Demoted Site DirectorIf you demote a supervisory controller or ADS/ADX from a Site Director to a child device on the site, all user accountsthat you added to the device while it was a Site Director remain in the security database. If you determine that useraccounts on the demoted site should be removed after the demotion has occurred, use the SCT to perform thefollowing steps to prepare a clean security database with all user-defined accounts deleted. This clean databasecan then be downloaded to the demoted device.

Changing the Site DirectorNote: If you have already changed the Site Director and downloaded the site, go to Moving the Security Database

and Clearing It from the Demoted Site Director.

1. Start the SCT, open the archive database for the site, and choose the new Site Director in the Site object.2. Download the Site so that every device knows the new Site Director.

Moving the Security Database and Clearing It from the Demoted Site Director1. Upload the archive database of the demoted device using the Manage Archive Wizard in SCT, which also backs

up the Security database of the device. This step is necessary only if you are using the same set of users on thenew or an existing Site Director.

2. Upload the archive database of one of the devices (NAE/NCE/NIE/ADS/ADX) on the site that has never been aSite Director and has never had a Site Director’s Security database copied to it (and, therefore, has a cleanSecurity database with only the default user accounts).

3. Copy the Security database that you created in Step 2 to the device that was demoted from the Site Directorusing the Security Copy Wizard in SCT.

4. If you are using the Security database of the demoted device on the new Site Director, copy the Security databasethat you backed up in Step 1 to the new or existing Site Director.

5. Create a backup of the Security database from the device that was demoted and restored with a clean databasein Step 3.

Note: This step ensures that the device Security database in the SCT matches the clean Security databaseyou copied to the device in Step 3.

Configuring Metasys System SettingsThe Metasys system administrator can modify default settings manually if needed.

The settings in this section reset to their default values when you upgrade the system. Reconfigure the settings asdesired.

Changing Metasys Log on Screen BackgroundYou can replace the standard Johnson Controls splash screen with a custom image. For example, a customer'sname, logo, or a photo of their facility can be shown as the Site Management Portal is loading. When choosing theimage, follow these recommendations:

• Use digital image files of type jpg or png. Avoid bitmap files, which are not compressed and often have a verylarge file size.

• For best results, configure the image dimensions for 800 x 600 pixels, the resolution as 96 dpi, and the colordepth as 24 bit. Limit the file size to 100 KB or less. Use any photo editor, such as Microsoft Paint, to resize orreconfigure the image.

• If you use an image with a light background, you may need to change the text color for the User Name andPassword fields. The default color of these fields is white and may be almost invisible over a light background.


1. Prepare the image to meet the recommendations provided at the beginning of this section.2. Copy the image to this folder on the ADS/ADX computer:

C:\inetpub\wwwroot3. Open a text editor such as Notepad, selecting the Run as Administrator option. (Highlight the text editor from

the Programs list, right-click and select Run as Administrator. Specify the Administrator's password if the operatingsystem prompts you.) Some computers require administrator access to make changes to system files.

4. Open the FrameworkProperties.properties file on the ADS/ADX computer located here:

C:\inetpub\wwwroot\MetasysIII\UI\com\jci\framework5. In the log on screen background section at the end of the properties file, specify the file name of the splash

screen in the loginPaneBitmapURL parameter. Example:

loginPaneBitmapURL= /<splashscreen.jpg>6. If necessary, change the text color for the User Name and Password fields by setting the loginPaneTextColor

parameter to a hexadecimal color code. Possible hex codes include: #FF0000 (red), #000000 (black), #0000FF(blue), #FFFFFF (white). The following is an example of setting the screen text color to gray:

loginPaneTextColor=#8080807. Save the FrameworkProperties.properties file.8. Launch the Site Management Portal UI from the Launcher. Verify the new background and text color appear.

Note: If the image file you specified is not found, the background defaults to solid blue. If the text is not visible,specify a different color using the loginPaneTextColor parameter.

Note: You may also change the splash screen for SCT. Follow these same instructions, but edit theFrameworkProperties.properties file on the SCT computer located here:C:\inetpub\wwwroot\MetasysIII\toolUI\com\jci\framework

Changing the Action Queue TimeoutYou may need to change this setting if you download a large number of user views or graphics that reside on adifferent subnet than the SCT. In this situation, the Action Queue may time out before the download is complete.The default value for the Action Queue timeout is 30 seconds.

This setting is handled in the SCT. Refer to the SCT Technical Bulletin (LIT-1201534) for details on changing thissetting.

Creating Audit Entries for Discard EventsBy default, the ADS/ADX does not create an audit entry when you discard an event that originates on the ADS/ADX.

Note: Engines do not create an audit entry when you discard events that originate on the engine. For details onchanging this setting, refer to the NAE Commissioning Guide (LIT-1201519) .

1. On the ADS/ADX computer, open Notepad.2. Using Notepad, open the following file:

C:\Inetpub\wwwroot\MetasysIII\WS\web.config3. Find the line forWriteAuditAckDiscard:

<add key="EventRepository.WriteAuditAckDiscard" value="false"/>

4. Change the value from false to true.5. Save the file and close all windows.

Configuring Metasys Advanced Reporting System SettingsThe administrator of the reporting system ADX can manually refresh data and modify default settings on the ADXsuch as changing the timeout period and the default number of rows allowed in a report.

The settings in this section reset to their default values when you upgrade or uninstall/reinstall the ADX software.Reconfigure the settings as desired.


Refreshing the Metasys Advanced Reporting System Data ManuallyWhen you make changes to the SCT archive referenced by the Metasys Advanced Reporting System, the data doesnot refresh in the reporting system until 3:15 A.M. the following morning.

Note: Any users logged on to the reporting system at the time of the refresh are automatically logged off from thesystem. Perform manual refreshes at times when it is likely the system is not in use.

1. Exit the Metasys Advanced Reporting System UI.2. Select Start > All Programs > Accessories > Command Prompt.When you select Command Prompt, use the

right mouse key and select Run as Administrator. Click Continue or Yes if prompted by the User AccessControl dialog.

3. Type net stop metasysreportcacherefresh and press Enter.4. Type net start metasysreportcacherefresh and press Enter.

Note: The refresh process may take several minutes to complete. The ADX event log includes an entry whenthe refresh process completes, or indicates any errors.

5. Type exit and press Enter.6. Open the Metasys Advanced Reporting System UI, and the data reflects the changes you made to the SCT

archive.

Changing Metasys Advanced Reporting System Settings for IIS 7.5Note: Follow these steps if you are using Windows Server 2008 R2 OS, which uses IIS 7.5.

1. Open the Control Panel of the reporting system ADX and select System and Security > Administrative Tools >Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager windows appears.

2. In the navigation tree on the left, expand the name of the local computer, Sites, and Default Web Site. Theconfigured websites appear under the expanded Default Web Site.

3. Select the MetasysReports website.4. In the middle pane of the screen, double-click Application Settings under the ASP.NET section. Make sure the

Features View is selected. The Application Settings window appears.5. See Table 6 to change the desired setting.6. To edit a setting, double-click its name on the Application Settings window. Specify a new value and click OK.

Table 5: Summary of Reporting System ChangesDetailsPossible EditsApplication SettingThe default time and frequency to refreshreporting system data is 3:15 A.M. andonce every 24 hours. The minimumfrequency is 1 hour, but is not arecommended value because any userslogged on to the reporting system at thetime of the refresh are automaticallylogged off from the system. Configureautomatic refreshes to occur at timeswhen it is likely the reporting system isnot in use, and do not set frequentintervals.

Edit both of the following:

• EditCacheRefreshBaseTime to thedesired refresh time.

• Edit CacheRefreshInterval to thedesired number of hours betweenrefreshes.

Automatic Refresh

The Metasys Advanced ReportingSystem UI timeout period defaults to 15minutes (900 seconds). The MetasysAdvanced Reporting System UI timeoutperiod applies to every user who logs onto the reporting system.

EditWebServiceDBTimeout to thedesired value, in seconds.

Reporting System UI Timeout


Table 5: Summary of Reporting System ChangesDetailsPossible EditsApplication SettingThe Metasys Advanced ReportingSystem limit for the maximum number ofrows in a report is 10,000. If the reportreaches or exceeds this limit, the systemnotifies you that the limit has beenreached and the report is not generated.Increase this number to enable reportsto return more than 10,000 rows of data.

Edit RowsLimit to the desired value.Report Default Row Limit

This setting determines whether MeanKinetic Temperature is selected in theOther Filters panel. The default settingis for Mean Kinetic Temperature to beselected.

Edit MKTChecked to one of thefollowing:

• false if you would like the MeanKinetic Temperature check box to becleared by default.

• true if you would like the MeanKinetic Temperature check box to beselected by default.

Default for Other Filters Panel

7. When complete, close the Internet Information Services (IIS) Manager window.

Note: You also can modify this setting in the appsettings.config file located in theC:\Inetpub\wwwroot\MetasysReports directory.

Changing Metasys Advanced Reporting System Settings for IIS 7.0Note: Follow these steps if you are using Windows Server 2008 OS, which uses IIS 7.0.

1. Open Control Panel on the reporting system ADX and select System and Maintenance > Administrative Tools> Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager windows appears.

2. In the navigation tree on the left, expand the name of the local computer, Sites, and Default Web Site. Theconfigured websites appear under the expanded Default Web Site.

3. Select the MetasysReports website.4. In the middle pane of the screen, double-click Application Settings under the ASP.NET section. Make sure the

Features View is selected. The Application Settings window appears.5. See Table 6 to change the desired setting.6. To edit a setting, double-click its name on the Application Settings window. Specify a new value and click OK.


Table 6: Summary of Reporting System ChangesDetailsPossible EditsApplication SettingThe default time and frequency to refreshreporting system data is 3:15 A.M. andonce every 24 hours. The minimumfrequency is 1 hour, but is not arecommended value because any userslogged on to the reporting system at thetime of the refresh are automaticallylogged off from the system. Configureautomatic refreshes to occur at timeswhen it is likely the reporting system isnot in use, and do not set frequentintervals.

Edit both of the following:

• EditCacheRefreshBaseTime to thedesired refresh time.

• Edit CacheRefreshInterval to thedesired number of hours betweenrefreshes.

Automatic Refresh

The Metasys Advanced ReportingSystem UI timeout period defaults to 15minutes (900 seconds). The MetasysAdvanced Reporting System UI timeoutperiod applies to every user who logs onto the reporting system.

EditWebServiceDBTimeout to thedesired value, in seconds.

Reporting System UI Timeout

The Metasys Advanced ReportingSystem limit for the maximum number ofrows in a report is 10,000. If the reportreaches or exceeds this limit, the systemnotifies you that the limit has beenreached and the report is not generated.Increase this number to enable reportsto return more than 10,000 rows of data.

Edit RowsLimit to the desired value.Report Default Row Limit

This setting determines whether MeanKinetic Temperature is selected in theOther Filters panel. The default settingis for Mean Kinetic Temperature to beselected.

Edit MKTChecked to one of thefollowing:

• false if you would like the MeanKinetic Temperature check box to becleared by default.

• true if you would like the MeanKinetic Temperature check box to beselected by default.

Default for Other Filters Panel

7. When complete, close the Internet Information Services (IIS) Manager window.

Note: You also can modify this setting in the appsettings.config file located in theC:\Inetpub\wwwroot\MetasysReports directory.

Changing the Archive Database Used by the Metasys Advanced Reporting System (ADXOnly)Note: To perform this task, youmust have SQL ServerCREATE PROCEDURE permission on the archive database

(to create stored procedures) andUPDATE permission on theMetasys Reporting database. As a SQL Serversoftware administrator, you should have these permissions by default.

Note: To perform this task, you also must have Administrator rights for the Windows OS.

This procedure is required only if you meet one of the following requirements:

• You have the Metasys Advanced Reporting system installed on your ADX and would like to change the archivedatabase referenced by the reporting system without uninstalling and re-installing the ADX software.

• You have an ADX Turnkey and would like to have the reporting system refer to an archive other than MyArchive1(the default reporting system archive database on an ADX Turnkey).

You must repeat this procedure every time you import a new database.


1. If you would like to rename your ADX computer, do so now. For a non-Turnkey system, see Appendix: Changingthe Name and the Computer Name. For a Turnkey system, refer to the ADS/ADX Turnkey User's Guide(LIT-12011177).

2. Make sure the archive database you are going to associate with the reporting system is at the same releaseas the reporting system SCT and ADX.

3. Import the alternate archive into SCT.

Refer to the Metasys system Help (LIT-1201793) for details on importing archive databases into the SCT.4. Select Start > All Programs > Accessories > Command Prompt.When you select Command Prompt, use

the right mouse key and select Run as Administrator. Click Continue or Yes if prompted by the User AccessControl dialog.

5. Type the following at the command prompt:

CD C:\\ProgramData\Johnson Controls\MetasysIII\SQLData\SCTArchive\ARSDBFix

6. Press Enter.7. At the prompt, type the following:

ARSDBFix.bat “database name”

where “database name” is the name of the alternate archive. If the name contains spaces, enclose the entirename in double quotes as in Step 5. If the name has no spaces, quotes are not required.

8. Press Enter. If errors occur during execution, they appear in the command window.

Note: For more information on the execution, type ADRDBFix.bat /? at the prompt and press Enter.9. At the command prompt, type the following:

ReloadCache.bat10. Press Enter. If errors occur during execution, they appear in the command window.When the prompt reappears,

the procedure is complete.11. Type Exit.12. Press Enter twice.


TroubleshootingSplit ADX TroubleshootingIf the web/application server computer needs to be restarted during runtime, you can restart the computer withoutany special considerations.

If the database server computer needs to be restarted, you must restart both the database server computer and theweb/application server computer. The database server computer must be restarted before the web/application servercomputer. If you do not restart the computers in this order, the ADX application detects that the database is unavailableand enters the Warm Start sequence.

If this happens, do the following:

1. Shut down the database server computer.2. Shut down the web/application server computer.3. Start the database server computer.4. Wait until the database server computer and SQL Server software are running.5. Start the web/application server computer.

Backup and Restoration of the SQL Server DatabasesFrequent backups of the SQL Server databases are necessary to maintain the integrity of your system. Examineyour business needs to determine if daily, weekly, or monthly backups are necessary. The Metasys DatabaseManager software packaged with Metasys software provides a convenient method for database backup and restore.For details, refer to Metasys Database Manager Help (LIT-12011202).

You can also perform database functions with the Microsoft SQL Server Management Studio tool. This software isincluded with the full editions of SQL Server software and available for the Express editions from the MicrosoftDownload Center website. Contact your Johnson Controls support representative for more information on how touse third-party applications to perform backups of individual databases.

Refer to Network and IT Guidance for the BAS Professional Technical Bulletin (LIT-12011279) for more generalSQL Server database recommendations.

To avoid system problems, exclude the following files and folders from any backup procedure:

• C:\Inetpub\wwwroot\MetasysIII• C:\Inetpub\wwwroot\MetasysIII\WEB.CONFIG• C:\Inetpub\wwwroot\MetasysIII\BIN• C:\<WINNT or Windows>\Microsoft.NET\Framework\v1.1.4332\CONFIG• C:\<WINNT or Windows>\Microsoft.NET\Framework\v2.0.50727\CONFIG• C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config• C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG• C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config• C:\Inetpub\wwwroot\MetasysIII\GLOBAL.ASAX

Using Communication Log FilesThe Email DDA and the Pager DDA provide text-only log files to help you troubleshoot communications betweenthe ADS/ADX and the paging terminal. The Communication Log files contain the most recent successful andunsuccessful messages sent by the DDA. If the message was unsuccessful, the log file contains a message indicatingthe error (for example, a pager message may have been unsuccessful due to lack of dial tone or a busy signal).

Once the log file reaches its size limit, the ADS/ADX saves the log file as a backup (.bak) file and starts with anempty log file. Once that log file reaches its size limit, the ADS/ADX again saves the log file as a backup file, thistime overwriting the previous backup file.

You can open and view the log files using a text editor such as Microsoft Notepad.


Table 7 describes the Email DDA and Pager DDA Communication Log files in the ADS/ADX. Table 8 describes theerror messages that appear in the Pager DDA log file.

Table 7: ADS/ADX Communication Log FilesSize LimitLocation of the FileDescriptionLog File50 KBFor Windows XP Professional OS:

C:\Documents and Settings\All Users\ApplicationData\Johnson Controls\MetasysIII

Displays the most recentcommunications between theADS/ADX and the emailrecipient.

EmailLog.txt

EmailLog.bak

For Windows 7 OS, Windows 2008 Server R2 OS, orWindows 2008 Server OS:

C:\ProgramData\Johnson Controls\MetasysIII

50 KBFor Windows XP Professional OS:

C:\Documents and Settings\All Users\ApplicationData\Johnson Controls\MetasysIII

Displays the most recentcommunications between theADS/ADX and the pagerrecipient.

PagerLog.txt

PagerLog.bak

For Windows 7 OS, Windows 2008 Server R2 OS, orWindows 2008 Server OS:

C:\ProgramData\Johnson Controls\MetasysIII

Table 8: Error Messages in the Pager Log FileSolutionDescriptionErrorTry sending page again.Line is busy.BUSY

Try sending page again.Paging terminal is not answering.NO ANSWER

Try sending page again.Paging terminal is not answering.NO CARRIER

Check the telephone cord jack.There is no dial tone heard on the phone.NO DIALTONE

Enter a valid pager ID.Pager ID is incorrect.Invalid ID

Close the other application.1. Another application is using COM port.Failure to Initialize TAPI

Reset the NAE.2. COM port was not closed properly.

Reset the NAE.3. COM port is busy.

Change the Extra Initialization commandfield in the Internal Modem section of theCommunications tab to M0.

4. NAE Internal modem Initialization string isincorrect.

Windows Log File CleanupAll computers, including the ADS/ADX, generate log files related to Windows OS functions such as IIS. These filescan accumulate and eventually cause poor computer performance as the amount of available hard disk space isreduced.

For example, IIS logs every message it receives in the following location, depending on your OS:

• Windows XP OS:

c:\WINDOWS\system32\LogFiles\W3SVC1• Windows 7 OS, Windows Server 2008 R2 OS, and Windows Server 2008 OS:

c:\inetpubs\logs\logfiles\w3svc1

After consulting with your IT department, you may delete or move all IIS log files from the ADS/ADX computer toconserve hard disk space. As a precaution, you may want to retain the log files created over the past week.

In addition, several third-party tools are available to maintain your Windows OS log files and address log file storageproblems. Seek out tools that meet your needs and satisfy IT security standards on your site. Two examples of thesetools are WinDirStat and CCleaner.


ADS/ADX and SCT Temporary File CleanupComputers with ADS/ADX and SCT software generate temporary and transient files related to the operation of theADS/ADX and SCT. These files can accumulate and reduce the available hard disk space. You can delete or movethese files offline to help save on hard disk space.

The Metasys system folders whose contents are candidates for clean up are under the MetasysIII folder as follows:

• Windows XP OS:

C:\Documents and Settings\All Users\Application Data\Johnson Controls\MetasysIII• Windows 7 OS, Windows Server 2008 R2 OS, and Windows Server 2008 OS:

C:\Users\All Users\Johnson Controls\MetasysIII

The particular subfolders that contain temporary or transient content are:

• \Diagnostics• \download• \FileTransfer• \SecurityFiles• \temp• \upload

When you delete or move the files under these folders, do not delete or move the folders themselves, just thesubfolders and any files under the subfolders. Also, do not disturb any other MetasysIII folders that are not listedhere.

ADS/ADX Startup FailuresSee Folders in the Windows Event Viewer on the ADS/ADX for information about how these failures are logged.

If the ADS/ADX encounters an error during startup, it logs the error to the ADSADX Log, then enters into a WarmStart retry sequence. This sequence is the ADS/ADX trying to restart. It continues to try restarting until it is successfulor until the user stops the Metasys III Device Manager service.

If you try to stop the Metasys III Device Manager Service while it is in this Warm Start sequence, it could take up to5 minutes to stop. To work around this:

1. Resolve any issue that may be causing the Startup of the ADS/ADX to fail. For example, the SQL Server softwaremay be offline. If the issue cannot be resolved, to prevent the ADS/ADX from continually restarting, the user cando the following:a. Open Control Panel on the ADS/ADX computer and select Administrative Tools > Services.

If you are using Windows 7 OS or Windows Server 2008 R2 OS, select Control Panel > System and Security> Administrative Tools > Services.

If you are using Windows Server 2008 OS, select Control Panel > System and Maintenance > AdministrativeTools > Services.

b. In the Services window, right-click Metasys III Device Manager and select Stop.c. Click OK and close all windows.d. In the Control Panel, click Administrative Tools > Event Viewer.

If you are using Windows 7 OS or Windows Server 2008 R2 OS, select Control Panel > System and Security> Administrative Tools > Event Viewer.

If you are using Windows Server 2008 OS, select Control Panel > System and Maintenance > AdministrativeTools > Event Viewer.

Service Stopped messages in the Application folder for the MIIIDM source indicate that the Metasys IIIDevice Manager stopped.


Note: If the Metasys III Device Manager is not stopped, in the Administrative Tools > Services window,right-click Metasys III Device Manager and select Properties. Set startup type to Manual and restartthe computer. The Device Manager does not start up.

e. The ADS/ADX does not start on computer restart. You must start the Metasys III Device Manager servicemanually when necessary.

2. Restart the ADS/ADX computer.

Folders in the Windows Event Viewer on the ADS/ADXThe ADSADX Log and Metasys Report Server folders in the Windows Event Viewer on the ADS/ADX containinformation related to specific ADS/ADX software failures.

Note: In a split ADX, these folders exist on the web/application server computer.

Note: Error messages appear in English only.

The following events appear in the ADSADX Log folder:

• The ADS/ADX software has a failure initializing any subsystem during startup.• The ADS/ADX software has a failure during runtime when it tries to write to the SQL Server database.

The ADSADX Log folder defaults to Overwrite as Necessary. If you would like to save all events or have a certainEvent Log folder size, right-click the folder in the Windows Event Log and change this property.

Note: A display problem occurs when viewing the properties of the ADSADX Log in the Windows Event Viewer.Even though the folder defaults to Overwrite as Necessary when the folder is created during the first startupof the ADS/ADX, it appears in the Windows Event Viewer as Overwrite Events Older Than. In reality, the fileis Overwrite as Necessary.

The Metasys Report Server folder records errors specific to the Metasys Advanced Reporting System such as:

• when a report was run• who ran a specific report• the destination of a report

Additional errors write to theWindows Event Viewer Application folder. Any event in this folder is a result of informationgenerated by or an error in the Metasys III Device Manager service (MIIIDM source). Errors found in the Applicationfolder include a connection loss between the client and server or a connection loss between the web/applicationserver computer and database server computer in a split ADX.

The Windows Event Viewer is located in Control Panel > Administrative Tools > Event Viewer.

If you are using Windows 7 OS or Windows Server 2008 R2 OS, select Control Panel > System and Security >Administrative Tools > Event Viewer.

If you are usingWindows Server 2008OS, access Event Viewer by selecting Control Panel > System andMaintenance> Administrative Tools > Event Viewer.

Anti-Spyware Software on the ADS/ADX ComputerAnti-spyware software may not allow the ADS/ADX to write to the Windows OS Hosts file. Some anti-spywaresoftware may prompt you to accept or reject the change; other software does not allow the change to occur at all.

If the anti-spyware software is blocking the ADS/ADX from editing the Hosts file, you can still log on to the ADS/ADX;however, you may not be able to navigate to NAEs/NCEs/NIEs or ADS/ADX devices through the ADS/ADX (SiteDirector) using the Metasys system User Interface.

If you are using anti-spyware software, accept changes to the Hosts file that write Metasys Device Names/IP pairsto the file if you are prompted. If the software automatically denies Hosts file changes, configure the anti-spywaresoftware to allow the IIS Admin Service to edit the Hosts file.

Configure and verify that the anti-spyware software allows the Metasys Device Manager and Metasys ActionQueue services to run on the ADS/ADX computer.


Technical SpecificationsApplication and Data Server (ADS) System RequirementsTable 9: Application and Data Server (ADS) System Requirements (5 Users)

2.8 GHz Intel Core 2 Duo processor

2 x 320 GB hard disk (RAID 1)2 with 40 GB free space after installation of allprerequisite software and before installation of ADS software. Configure RAID 1(mirroring) with disk write-caching turned on.

DVD driveNote: Prerequisite software includes the supported OS, database software, .NET

Framework, and any other software or service packs required for your ADSconfiguration.

Recommended Computer Platform1

Graphics card (1 GB RAM, ATI® Technologies or NVIDIA® Corporation, 64-bitcompatible [for 64-bit OS], Small Form Factor [SFF] if required)3

4 GB RAM (32-bit systems)Recommended Memory4

8 to 16 GB RAM (64-bit systems)

Windows® 7 OS Professional, Enterprise, and Ultimate Editionswith SP1 (32-bitor 64-bit)

(Includes Microsoft IIS Version 7.5)

Supports Microsoft SQL Server™ 2008 R2 Express software with SP2 (32-bit or64-bit) or SQL Server 2008 Express software with SP3 (32-bit)

Supported Operating Systems5 andDatabase Software

Windows XP® OS Professional Edition with SP3 (32-bit)


Supports Microsoft SQL Server 2008 R2 Express software with SP2 (32-bit) or SQLServer 2008 Express software with SP3 (32-bit)

Windows Internet Explorer® Version 8.0 or 9.0

(Other browsers, such as Google Chrome and Mozilla Firefox®, may also be usedbut are not fully supported.)

Note: You use the web browser to download the Launcher application. After youinstall the Launcher application, you use the Launcher, not the web browser,to log on to the Metasys UI.

Required Web Browser Software forMetasys Client Computers

Ethernet network interface card (100 or 1000 Mbps)Note: The ADS supports only one network interface card.

Network Communication

Launcher softwareCCT softwareAdditional Software Included with theADS Microsoft SQL Server 2008 R2 Express

software with SP2 (32-bit and 64-bit)Export Utility software

Microsoft SQL Server 2008 Expresssoftware with SP3

Metasys Database Manager software

Microsoft .NET Framework Version 3.5SP1

Ready Access Portal software

SCT Manager softwareSCT software


Table 9: Application and Data Server (ADS) System Requirements (5 Users)Any network or local printer supported by the qualified Windows operating systemOptional Hardware

Energy Essentials

Graphic Generation Tool

Optional Software

1 Our computer platform and memory recommendations are not meant to imply that older or slower machines are not usable.Refer to theNetwork and IT Guidance for the BAS Professional Technical Bulletin (LIT-12011279) for more information regardingcomputer/server recommendations.

2 For best performance, use Serial Attached SCSI (SAS) hard drives, not Small Computer System Interface (SCSI) hard drives.3 For improved performance in configurations where ADS and Ready Access Portal share the same computer.4 For best performance, use the maximum amount of memory that the computer allows.5 Refer to theNetwork and IT Guidance for the BAS Professional Technical Bulletin (LIT-1201279) for specific Microsoft WindowsOS settings that may be required for your Metasys system configuration.

Application and Data Server-Lite System RequirementsTable 10: Application and Data Server-Lite System Requirements

2.8 GHz Intel Core 2 Duo processor

2 x 320 GB hard disk (RAID 1)2 with 40 GB free space after installation of all prerequisitesoftware and before installation of ADS-Lite software. Configure RAID 1 (mirroring) withdisk write-caching turned on.

DVD driveNote: Prerequisite software includes the supported OS, database software, .NET

Framework, and any other software or service packs required for your ADSconfiguration.

Graphics adapter (Graphics adapter (1 Gb RAM, ATI® Technologies or NVIDIA®Corporation, 64-bit compatible (for 64-bit OS), Small Form Factor (SFF) if required)3

Recommended ComputerPlatform 1

4 GB RAM minimum (32-bit systems)

8 GB RAM minimum (64-bit systems)

Recommended Memory

Windows® 7 OS Professional, Enterprise, and Ultimate Editions with SP1 (32-bit or64-bit)

(Includes Microsoft® IIS Version 7.5)

Supports Microsoft SQL Server™ 2008 R2 Express software with SP2 (32-bit or 64-bit) orSQL Server 2008 Express software with SP3 (32-bit)

Supported Operating Systems4and Database Software

Windows XP® OS Professional Edition with SP3 (32-bit)


Supports Microsoft SQL Server 2008 R2 Express software with SP2 (32-bit) or SQL Server2008 Express software with SP3 (32-bit)


(Other browsers, such as Google® Chrome and Mozilla Firefox, may also be used but arenot fully supported.)

Note: You use the web browser to download the Launcher application. After you installthe Launcher application, you use the Launcher, not the web browser, to log on tothe Metasys UI.

Required Web Browser forMetasys Client Computers

Ethernet network interface card (100 or 1000 Mbps)Note: The ADS supports only one network interface card.



Table 10: Application and Data Server-Lite System RequirementsLauncher softwareCCT softwareAdditional Software Includedwith

the ADS-Lite Microsoft SQL Server 2008 R2 Expresssoftware with SP2 (32-bit and 64-bit)

Export Utility software

Microsoft SQL Server 2008 Express softwarewith SP3


Microsoft .NET Framework Version 3.5 SP1Ready Access Portal software


Any network or local printer supported by the qualified Windows operating systemOptional Hardware

Graphic Generation ToolOptional Software


2 For best performance, use Serial Attached SCSI (SAS) hard drives, not Small Computer System Interface (SCSI) hard drives.3 For improved performance only when ADS and Ready Access Portal share the same computer.4 Refer to theNetwork and IT Guidance for the BAS Professional Technical Bulletin (LIT-12011279) for specific Microsoft WindowsOS settings that may be required for your Metasys system configuration.

Extended Application and Data Server System Requirements (Unified ADX)Table 11: Extended Application and Data Server System Requirements (Unified ADX Systems, 10 or 25Users)

2.4 GHz Intel Xeon® single processor

2 x 600 GB hard disk (RAID 1)2 with 40 GB free space after installation of all prerequisitesoftware and before installation of ADS software. Configure RAID 1 (mirroring) with diskwrite-caching turned on.

DVD driveNote: ADX prerequisite software includes theWindowsOS, SQLServer software,Windows

.NET Framework, and any other software or SPs required by your ADX configuration.

Recommended Server Platform1

16 GB RAM (10 or 25 user ADX)Recommended Memory3

Windows Server 2008 R2 OS (64-bit) with SP1


Supports Microsoft SQL Server™ 2008 R2 Standard and Enterprise software with SP2(64-bit)

or Microsoft SQL Server 2008 Standard and Enterprise software with SP3 (64-bit)

Supported Operating Systems4

and Database Software 5

Windows Server 2008 OS (32-bit) with SP2


Supports Microsoft SQL Server 2008 R2 Standard and Enterprise software with SP2 (32-bit)

or SQL Server™ 2008 Standard and Enterprise software with SP3 (32-bit)

Note: A 32-bit OS only supports a maximum of 4 GB memory. For best performance, usea 64-bit OS.


(Other browsers, such as Google Chrome and Mozilla Firefox, may also be used but arenot fully supported.)


Required Web Browser Softwarefor Metasys Client Computers

Ethernet network interface card (100 or 1000 Mbps)Note: The ADX supports only one network interface card.



Table 11: Extended Application and Data Server System Requirements (Unified ADX Systems, 10 or 25Users)

Launcher softwareCCT softwareAdditional Software Includedwiththe ADX Microsoft SQL Server 2008 R2 Express






Note: The Metasys Advanced Reporting System requires an ADX. The SCT computermust be online and accessible to the ADX at all times.

Any network or local printer supported by the qualified Windows operating systemOptional Hardware

Energy Essentials software

Graphic Generation Tool software

Optional Software


2 For best performance, use SAS hard drives, not SATA hard drives.3 For best performance, use the maximum amount of memory. An ADX with 16 GB RAM has much greater performance thanan ADX with only 4 GB RAM. A 32-bit OS does not support more than 4GB of RAM.

4 Refer to theNetwork and IT Guidance for the BAS Professional Technical Bulletin (LIT-12011279) for specific Microsoft WindowsOS settings that may be required for your Metasys system configuration.

5 You must purchase a SQL Server software license for each individual processor you have. You do not need to purchase multiplelicenses if you have a single processor divided into multiple cores. For example, if you have a single processor with dual cores,purchase one license for SQL Server software.

Extended Application and Data Server System Requirements (Split ADX)Table 12: Extended Application and Data Server System Requirements (Split ADX Systems, 10 or 25 Users,50 Users Not Supported)

Web/Application Server


2 x 600 GB hard disk (RAID 1)2 with 40 GB free space after installation of all prerequisitesoftware4 and before installation of ADS software. Configure RAID 1 (mirroring) with diskwrite-caching turned on.

DVD drive


Database Server


2 x 600 GB hard disk (RAID 1) with 40 GB free space after installation of all prerequisitesoftware4 and before installation of ADS software. Configure RAID 1 (mirroring) with diskwrite-caching turned on.

DVD drive

SCT Computer

In a split configuration, you cannot install SCT software on either the web/application servercomputer or the database server computer. Refer to the System Configuration Tool CatalogPage (LIT-1900198) for current SCT computer requirements.

16 GB RAM (web/application server and database server for 10 or 25 user ADX)Recommended Memory3


Table 12: Extended Application and Data Server System Requirements (Split ADX Systems, 10 or 25 Users,50 Users Not Supported)



Supports Microsoft SQL Server™ 2008 R2 Standard and Enterprise software with SP1(64-bit) or Microsoft SQL Server 2008 Standard or Enterprise software with SP3 (64-bit)

Supported Operating Systems5 ,6with Supported DatabaseSoftware 7



Supports Microsoft SQL Server 2008 R2 Standard and Enterprise software with SP1 (32-bit)or SQL Server™ 2008 Standard and Enterprise software with SP3 (32-bit)






Ethernet network interface card (100 or 1000 Mbps)

Note: The ADX supports only one network interface card.









Any network or local printer supported by the qualified Windows operating system.Optional Hardware



Optional Software


2 For best performance, use SAS hard drives, not SATA hard drives.3 For best performance, use the maximum amount of memory. An ADX with 16 GB RAM has much greater performance thanan ADX with only 4 GB RAM. Also, a 32-bit OS only supports a maximum of 4 GB of RAM.

4 ADX prerequisite software includes the Windows OS and SQL Server software, Windows .NET Framework, and any othersoftware or service packs required for your ADX configuration.

5 The web/application and database servers must have the same OS installed.6 Refer to theNetwork and IT Guidance for the BAS Professional Technical Bulletin (LIT-12011279) for specific Microsoft WindowsOS settings that may be required for your Metasys system configuration.



Extended Application and Data Server SystemRequirements (Unified 50 UserADX)Table 13: Extended Application and Data Server System Requirements (Unified ADX Systems, 50 Users)


6 x 300 GB hard disk (RAID 5)2 with 50 GB free space after installation of all prerequisitesoftware and before installation of ADS software. Configure RAID 5 with disk write-cachingturned on.

DVD driveNote: ADX prerequisite software includes theWindowsOS, SQLServer software,Windows

.NET Framework, and any other software or SPs required by your ADX configuration.


32 GB RAMRecommended Memory



Supports Microsoft SQL Server™ 2008 R2 Standard and Enterprise software with SP2(64-bit)

or Microsoft SQL Server 2008 Standard and Enterprise software with SP3 (64-bit)

Supported Operating Systems3

and Database Software 4



Supports Microsoft SQL Server 2008 R2 Standard and Enterprise software with SP2 (32-bit)

or SQL Server™ 2008 Standard and Enterprise software with SP3 (32-bit)






Ethernet network interface card (1000 Mbps)Note: The ADX supports only one network interface card.










Table 13: Extended Application and Data Server System Requirements (Unified ADX Systems, 50 Users)Any network or local printer supported by the qualified Windows operating system.Optional Hardware



Optional Software


2 For best performance, use SAS hard drives, not SATA hard drives.3 Refer to theNetwork and IT Guidance for the BAS Professional Technical Bulletin (LIT-12011279) for specific Microsoft WindowsOS settings that may be required for your Metasys system configuration.



Appendix: Time Zone, Date, and Time ManagementTime Zone, Date, and Time Management IntroductionThe time zone, date, and time used by all devices connected to a Metasys site are synchronized automatically,preventing errors from manual time entry and clocks that become inaccurate over time. Network-wide timemanagement ensures that scheduling, trending, audit trailing, data collecting, time-stamping of alarms, and otherfunctions that require accurate time management use the same time zone, date, and time consistently for all systemoperations.

Time synchronization occurs on the Metasys network when an engine or server sends an IAmLive message to theSite Director. If the IAmLive message fails, the engine or server sends another message to retrieve the time fromthe Site Director. When the time is synchronized between the devices, a second IAmLive message is successful.

For network-wide time synchronization, the NAE/NIE/ADS/ADX designated as Site Director is the device time serverbecause it provides the time zone, date, and time for all other engines/servers on the site. All other devices areconsidered time clients because they receive the time zone, date, and time from the Site Director.

To set the date and time in the Site Director (and therefore the entire site), you can set the time manually or selecta time server for the Site Director. The time server for the Site Director is referred to as the site time server andshould be a reliable source not on the Metasys network. Regardless of how you set the date and time, you must setthe time zone in the Site Director.

Important: Edit the Device Time Servers attribute or Time Sync Period attribute in the Site object only.

Note: To ensure that the correct time appears on the Site Management Portal UI accessed from a client computer,apply the most recent Daylight Saving Time (DST) patch for the operating system on all clients that accessthe Site Director. The DST patch is available from Microsoft Corporation.

Overview of Time SynchronizationThis section contains a summary of how time synchronizes on a site with various system components. Table 14summarizes the time sources for various system items. All time is Universal Time Coordinated (UTC) and all systemdevices handle DST.

Table 14: Time SourcesTime SourceItemNAE/NIENAE/NIE Trend Data

NAE/NIENAE/NIE Events

NAE/NIENAE/NIE Commands

ADS/ADXAnnotations

ADS/ADXEvent Acknowledgements

ADS/ADX Site Director with NAEs/NIEsOn a site with an ADS/ADX Site Director and NAEs/NIEs, the following time synchronization steps occur:

1. ADS/ADX Site Director comes online.2. NAEs/NIEs come online and check in with the Site Director.3. Every 15 seconds, the NAEs/NIEs check for ADS/ADX online/offline conditions. If the ADS/ADX is offline, the

NAEs/NIEs send an IAmLive message to the ADS/ADX every 20 seconds.4. When the ADS/ADX receives the IAmLive message, it attempts to validate the security credentials of the

NAEs/NIEs. If the time in the NAEs/NIEs is different than the time in the ADS/ADX by 5 or more minutes, theengine security credentials are invalidated.

5. When the NAE receives back an invalidated credential, the NAEs/NIEs request the current time from the ADS/ADXand update the engine time to match.


Note: Time between an ADS/ADX and NAEs/NIEs synchronizes only if the time differs between the ADS/ADXand NAEs/NIEs by 5 or more minutes. In the worst case scenario, one NAE could be 4 minutes and 59seconds ahead of the ADS/ADX, and another NAE could be 4 minutes and 59 seconds behind theADS/ADX.

6. After time is synchronized and the ADS/ADX is online, the NAEs/NIEs send IAmLivemessages to the ADS/ADXevery 5 minutes (instead of every 20 seconds).

NIE and Child DevicesImportant: We recommend that time be synchronized carefully between the NIE and the N1 network, preferably

using a common external time server. All N1 network data collected by the NIE is time stamped at theNIE (no N1 network time stamps persist in the data collected by the NIE).

While the NIE can push time to the NCM, the preferred method of synchronization for the NIE and N1network is to have both synchronize with an external time server.

On a site with an NIE and child devices (NCMs, for example), the following time synchronization steps occur:

1. The NIE comes online and is mapped to NCMs.2. When the time changes in the NIE (as a result of synchronization with an ADS/ADX, for example), the NIE pushes

the time change down to the NCM. This time push requires that the Synchronize Time attribute of the NIE N1Integration object is enabled.

Time Synchronization MethodsThree methods for network time synchronization are available in the Metasys system, including Microsoft Windows®Simple Network Time Protocol (SNTP) time synchronization, Multicast, and BACnet® time synchronization.

You can use the Microsoft Windows and Multicast methods when an SNTP master time server is available. If theSite Director has no access to SNTP time servers, you can use the BACnet synchronization method.

To enable a time synchronization method, modify the Time Sync Method attribute for the Site. See the Steps forSuccessful Time Management and Setting the Time Synchronization Method sections.

Windows Time SynchronizationThe Windows time synchronization is Microsoft Corporation’s implementation of the standard Windows SNTPw32time. This method is also referred to as unicast synchronization. With this form of time synchronization, all routerscan route User Datagram Protocol (UDP) traffic. Windows time synchronization may have a larger time interval inwhich devices are out of sync with the SNTP master time server due to skewing and convergence.

If you use Windows time synchronization, you must define a device time server in the Site Director using the DeviceTime Servers attribute.

Note: If you implement an intentional time change for your site, in less than 5 minutes, all other devices on the siteupdate with the new time with Windows time synchronization.

Multicast Time SynchronizationTheMulticast time synchronization is the Johnson Controls implementation of SNTPw32time with Multicast capabilitiesand RFC-2030 compliance. This method delivers the same features as the Windows method, but also providesMulticast functionality. The Multicast method provides improved Metasys time synchronization between the SiteDirector and supervisory devices. A time domain server provides the master time to the Site Director, and the SiteDirector in turn multicasts the time to all supervisory devices on the Metasys network.

When a supervisory device first signs up with the Site Director, it polls the Site Director for the current time andmatches its time with the Site Director time. By default, every 5 minutes the Site Director broadcasts the current timeto all supervisory devices. If a particular device time differs 1.5 seconds or more from the Site Director time, thedevice adjusts its time to match. Additionally, if the Site Director time changes by more than 1 to 1.5 seconds, itsends out a Multicast time message to all devices within 2 seconds of the change.


This form of time synchronization requires that all routers on the site support Multicast routing (Internet GroupMulticast Protocol [IGMP]) because the Multicast time message crosses routers. The Johnson Controls SNTP timesynchronization reduces the time interval in which devices are out of sync with the SNTP master time server.

Note: All devices synchronized with Multicast time synchronization must be at Release 3.1 or later. For example,if you have an ADS at Release 3.1 and NAEs at Release 2.2, you cannot sync these devices using Multicasttime synchronization.

Note: If you implement an intentional time change for your site, within a few seconds, all other devices on the siteupdate with the new time with Multicast time synchronization.

BACnet Time SynchronizationBACnet time synchronization uses BACnet protocol to synchronize with BACnet devices such as the NAE. Use thismethod when the Site Director has access to a BACnet time server. This method is not available on the ADS/ADX.

Example NetworkStep 1 shows an example system with a common time zone, date, and time management setup. This example isrepresentative of the Multicast and Windows time synchronization methods.

The Site Director (in this case, an ADS) is configured to receive the date and time from an intranet time server. Thedate and time originates at an Internet time server (such as the Naval atomic clock). Using Simple Network TimeProtocol (SNTP), the intranet time server requests the time from the Internet time server. The Site Director requeststhe time from the intranet time server. Then, using the Metasys system automatic time synchronization, and themanually configured time zone, the Site Director automatically provides the time zone, date, and time to the otherengines/server on the Metasys network.

Figure 19: Time Management Sample System

Time ZoneThe time zone of the Site Director defaults to (GMT-06:00) Central Time (US & Canada). If your site is not in theCentral time zone, set the time zone for your location. When you set the time zone in the Site Director, it propagatesthe current time to all the engines/servers on the site. You must set the time zone in the Site Director even if youselect a site time server. In addition, set the time zone in all ADS/ADX devices, even though none of them are theSite Director.

When a non-Site Director NAE is downloaded in a different time zone than Central Standard Time (CST), the NAEmight revert to CST. This problem indicates that domain name resolution is not working properly. Consequently, theNAE cannot reach the ADX Site Director after download. You can solve this problem in one of two ways:

• Add the ADX name and IP address to the NAE host file. The NAE communicates to the Site Director as long asboth have the same date based on their time zones. Communication fails if the two machines are set to differenttime zones such that one has passed into the next day but the other has not. An example of this would be if the


Site Director is set to Japan Standard Time and the device is set to CST, and the time in Osaka has passedmidnight while the device is just after 10 A.M. the previous day.

• Set the NAE to the Site Director time zone and write the NAE Local Site Director attribute to the ADX IP address;then, upload the NAE. After that step, each download of the device is given the Site Director IP address andcorrect time zone.

Site Time ServerAs an alternative to setting date and time manually for a device, you can select a site time server. A site time serversets the date and time in the Site Director. If you have a split ADX, select the same site time server for both theweb/application server computer and the database server computer. Site time servers can be on your intranet, suchas a Domain Controller/Server; or on the Internet, such as the U.S. Naval Observatory Master Clock.

For a list of Navy master clocks, go to http://tycho.usno.navy.mil/.

See the Selecting a Site Time Server for the Site Director NAE/NIE or Selecting a Site Time Server for the SiteDirector ADS/ADX (Windows Method Only) sections.

Time in Device Object and UI Status BarThe time zone, date, and time in the Status Bar of the UI and the time zone, date, and time in the device object ofthe device to which you are browsing are the same time; however, there may sometimes seem to be a discrepancyor delay between the two.

In the Site Director, the time zone, date, and time in the device object of the device are set by you or by the designatedsite time server. In a non-Site Director NAE, the time zone, date, and time in the device object come from the SiteDirector. In a non-Site Director ADS/ADX, the time zone in the device object comes from your manual setting, butthe date and time come from the Site Director.

The Device object then passes the time zone, date, and time along to the Status Bar for display. If the device isbusy, it may take a few minutes for the time zone, date, and time to update correctly in the Status Bar.

Steps for Successful Time ManagementFor successful time management, do the following:

1. Verify that each non-supervisory engine/server on the Metasys network has the correct Site Director defined.

See the Verifying the Site Director Defined for an Engine/Server section.2. Set the time synchronization method for the site.

See the Setting the Time Synchronization Method section.3. Set the time zone and then set the date and time or select a site time server for the site.

See the NAE/NIE Is the Site Director or ADS/ADX Is the Site Director section.

If you have an NAE/NIE as the Site Director, the time zone, date, and time are set in the UI of the Site DirectorNAE/NIE. See the NAE/NIE Is the Site Director section. If you have non-Site Director ADSs/ADXs on the site,you must set the time zone for these servers.

If you have an ADS/ADX as the Site Director, the time zone, date, and time are set in the Windows OS of thecomputer where the ADS/ADX resides. See the ADS/ADX Is the Site Director section. If you have non-SiteDirector ADS/ADX devices on the site, you must set the time zone for these servers.

4. For Multicast time synchronization only, configure the SNTP Multicast attributes for the site.

See the Configuring Additional Multicast Time Synchronization Settings section.5. If a P2000 Security Management System (SMS) is integrated to the ADS/ADX server, both the P2000 and

ADS/ADX servers should reference the same network time server. If the two systems use different time servers,the P2000 and ADS/ADX servers are not clock synchronized, which results in intermittent or no communicationsbetween the two systems.


http://tycho.usno.navy.mil/

Verifying the Site Director Defined for an Engine/ServerFor time synchronization to work properly, all engines/servers on a site must have the correct name for the SiteDirector in the Local Site Director attribute. If an engine/server has the wrong device defined as Site Director, timesynchronization may not work properly on your Metasys site.

1. Log on to engine/server.2. Drag and drop the engine/server object to the Display frame.3. Select Advanced.4. Scroll to the Site section and verify the Local Site Director attribute contains the correct device (Figure 20). In

this example, the Site Director is an NAE (NAE-THREE).

Note: The Local Site Director may be entered as an IP address or host name. If entered as a host name, thename is case sensitive (for example, NAE-THREE is not the same as nae-three).

Figure 20: Site Director Field

Note: If the Site Director field contains the wrong device or is empty, click Edit. Edit the Site Director entry andclick Save.

5. Go to Setting the Time Synchronization Method.

Setting the Time Synchronization MethodSee the Time Synchronization Methods section for descriptions of the methods.

1. Log on to Site Director engine/server.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. Select Advanced.5. In the Time section, in the Time Sync Method drop-down box, select the desired time synchronization method

(Windows or Multicast).

Figure 21: Time Sync Method Field

6. If you select Windows time, enter a device time server in the Device Time Servers attribute. A device time serveris required for Windows time synchronization.

7. Click Save.


Important: When the Time Sync Method is set to Multicast and the ADS/ADX computer is synchronized witha time source other than itself, the Site Time Server must be an SNTP Time Server to allow theADS/ADX to perform time synchronization. Time synchronization occurs when a change is detectedin the ADS/ADX computer local clock, or at the Site configured Time Sync Period.

Enabling Multicast time synchronization terminates the Windows win32time service, but changingthe Time Sync Method back to Windows does not re-enable the service. If you change the TimeSync Method back to Windows, you must manually start the win32time service, or restart the SiteDirector.

8. Go to NAE/NIE Is the Site Director or ADS/ADX Is the Site Director.

NAE/NIE Is the Site DirectorIf an NAE/NIE is the Site Director, you must set the time zone first, then either set the date and time or select a timeserver for the Site Director NAE/NIE.

Note: See the Verifying the Site Director Defined for an Engine/Server and Setting the Time Synchronization Methodsections before following the steps in this section.

Setting the Time Zone in the Site Director NAE/NIE1. Log on to the Site Director NAE/NIE.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. In the Time section, in the Time Zone drop-down box, select the correct time zone for the device (Figure 22).

Figure 22: Time Zone in the Site Object

5. Click Save.

If you are also manually setting the date and time in the Site Director NAE/NIE, go to the Setting the Date andTime in the Site Director NAE/NIE section.

If you are selecting a time server for the Site Director NAE/NIE, go to the Selecting a Site Time Server for theSite Director NAE/NIE section.

Setting the Date and Time in the Site Director NAE/NIEBefore manually setting the date and time in the Site Director NAE/NIE, follow the steps in the Setting the Time Zonein the Site Director NAE/NIE section.

1. In the navigation tree, right-click the Site object and select Commands. The Commands dialog box appears.2. Click Set Time and enter a value in the text box (Figure 23).


Figure 23: Time in a Site Director NAE/NIE

3. Click Send.

Note: If you have a site time server selected, do not attempt to set the time manually. If you have one or moresite time servers defined, sending this command generates an error.

4. In the navigation tree, right-click the Site object and select Commands. The Commands dialog box appears.5. Click Set Date and select a date from the calendar (Figure 24).

Figure 24: Date in a Site Director NAE/NIE

6. Click Send.

Note: If you have one or more site time servers defined, sending this command produces an error. If you havea site time server defined, do not attempt to set the time manually.

The Site Director time zone, date, and time are now set and propagate to all other engines on the site.


Selecting a Site Time Server for the Site Director NAE/NIEBefore selecting a site time server for the Site Director NAE/NIE, follow the steps in the Setting the Time Zone inthe Site Director NAE/NIE section.

1. Reset the NAE/NIE for the time zone change to take effect.2. Log on to the NAE/NIE.3. Drag and drop the Site object to the Display frame.4. Click Edit.5. In the Time section, in the Site Time Servers field, click the browse button.

Note: The Device Time Servers field should be blank unless you are using Windows time synchronization. Donot change the value for the Time Sync Period attribute.

Figure 25: Site Time Servers in the Site Object

6. In the screen that appears, click Add (Figure 25).7. Enter the IP address of the SNTP server from which the Site Director receives its time (Figure 26).

Note: Specify a host name only if a DNS server is available to the Site Director.

Note: If you add more than one address, the Site Director NAE55/NIE55 tries to contact the first address. Ifthat fails, the NAE55/NIE55 contacts the second one, and so on. The NAE35/NAE45 engines use onlythe first address in the list.

Figure 26: Add Site Time Server

8. Click OK.9. Click Save. The Site Director now requests the date and time from the selected time server and propagates it

to all other engines on the site.10. Go to Configuring Additional Multicast Time Synchronization Settings if needed.

ADS/ADX Is the Site DirectorSet the time zone first, then either set the date and time or select a time server for the Site Director ADS/ADX.

Note: See the Verifying the Site Director Defined for an Engine/Server and Setting the Time Synchronization Methodsections before following the steps in this section.

Note: If you select a site time server for your Site Director ADS/ADX, and you also set the time manually in theADS/ADX, the manual time is overridden at the end of the time specified in the Time Sync Period attribute(default is 1 hour).


Setting the Time Zone in the Site Director ADS/ADX1. In the lower right corner of the ADS/ADX computer screen, double-click the time. If you are using Windows 7

OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS, single-click the time. The Date and TimeProperties box appears (Figure 27). The appearance of this screen varies depending on the OS.

Figure 27: Time and Date on a Site Director ADS/ADX - Windows XP Professional OS

2. If you have Windows XP Professional OS, click the Time Zone tab (Figure 28). If you have Windows 7 OS,Windows Server 2008 R2 OS, or Windows Server 2008 OS, select the Change date and time settings optionand click Change time zone.

Figure 28: Time Zone on a Site Director ADS/ADX

3. Select a time zone from the drop-down list box.4. Select Automatically adjust clock for daylight saving changes, if present.5. If you have non-Site Director ADS/ADX devices on your site, set the time zone in those servers following the

instructions in this section.

If you are also manually setting the date and time in the Site Director ADS/ADX, go to the Setting the Date andTime in the Site Director ADS/ADX section.


If you are selecting a time server for the Site Director ADS/ADX, click OK and go to the Selecting a Site TimeServer for the Site Director ADS/ADX (Windows Method Only) or Selecting a Site Time Server for the Site DirectorADS/ADX (Multicast Method Only) section.

Setting the Date and Time in the Site Director ADS/ADXBefore manually setting the date and time in the Site Director ADS/ADX, follow the steps in the Setting the TimeZone in the Site Director ADS/ADX section.

1. In the Date and Time Properties box, click the Date & Time tab. If you have Windows 7 OS, Windows Server2008 R2 OS, or Windows Server 2008 OS, click the time in the lower right corner of the screen. Select theChange date and time settings option and click Change date and time.

2. Set the time and date.3. Click OK.

The Site Director time zone, date, and time are now set and propagate to all other engines/servers on the site.

Selecting a Site Time Server for the Site Director ADS/ADX (Windows Method Only)If you set up a site time server for your Site Director, you can set the date and time manually in the ADS/ADX, butthe manual settings are overridden at the end of the Time Sync Period.

Before selecting a site time server for the Site Director ADS/ADX, follow the steps in the Setting the Time Zone inthe Site Director ADS/ADX section.

1. On the Windows Start menu of the ADS/ADX computer, select Run. The Run dialog box appears (Figure 29). Ifyou have Windows 7 OS, click the Start icon and select All Programs > Accessories > Run.

Figure 29: Run Dialog Box

2. TypeNet time /setsntp:"10.10.16.1 10.10.16.2 ...", where 10.10.16.1 and 10.10.16.2 are example IP addressesof time servers.

Note: The IT department should provide the address of a suitable time server.

Be sure that the quotation marks are included (especially when listing multiple time servers).3. Click OK.

The Site Director now requests the date and time from the selected time server and propagates it to all otherengines/servers on the site.

Selecting a Site Time Server for the Site Director ADS/ADX (Multicast Method Only)Before selecting a site time server for the Site Director ADS/ADX, follow the steps in the Setting the Time Zone inthe Site Director ADS/ADX section.

1. Log on to ADS/ADX.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. In the Time section, in the Site Time Servers field, click the browse button.

Note: Leave the Device Time Servers field blank. Do not change the value for the Time Sync Period attribute.


Figure 30: Site Time Servers in the Site Object

5. In the screen that appears, click Add (Figure 30).6. Enter the IP address of the SNTP server from which the Site Director receives its time (Figure 31).

Note: Specify a host name only if a DNS server is available to the Site Director. Leave the Device Time Serversfield blank.

For Multicast time synchronization, if you add more than one address, the Site Director ADS/ADX triesto contact only the first address.

7. Click OK.

Figure 31: Add Site Time Server

8. Click Save. The Site Director now requests the date and time from the selected time server and propagates itto all other engines/servers on the site.

9. Go to Configuring Additional Multicast Time Synchronization Settings.

Configuring Additional Multicast Time Synchronization SettingsIn addition to selecting the Multicast time synchronization method (Setting the Time Synchronization Method), youmust define other Multicast attributes.

To configure additional Multicast time synchronization settings:

1. Log on to Site Director engine/server.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. Select Advanced.5. In the Time section, modify the attributes listed in Table 15 (Figure 32).


Figure 32: Multicast Time Synchronization Fields

Table 15: Multicast Time Synchronization FieldsDescriptionAttributeSpecifies the IP address used to multicast the SNTP message. This address identifies thegroup of devices to receive the SNTP message. The RFC-2030 defined standard addressis 224.0.1.1. The address is configurable to allow site specific use.

Multicast Group Address

Specifies the UDP port on which Multicast time synchronization polls and listens formessages. The RFC-2030 defined standard port is 123.The UDP port defined here mustmatch the Time Server’s UDP port for successful polling to occur.

Multicast UDP Port

Specifies the Time-to-Live (TTL) for a Multicast message. The value indicates the numberof router hops (number of routers to pass through) allowed before the message is not sent.Routers must be configured to pass Multicast messages to allow the time sync message topass.

Note: A default value of 1 typically stops the Multicast message from leaving the IP subnetof the Site Director. Most routers decrease the existing TTL upon arrival of a packet,and drop the packet instead of rerouting it when the TTL reaches 0.

Multicast TTL

Specifies the number of minutes between forcing a Multicast time synchronization messagefrom the Site Director to participating devices.

Multicast Heartbeat Interval

6. Click Save.


Appendix: Changing the Name and the Computer NameChanging the ADS/ADXName and the Computer Name on anADS andUnifiedADX IntroductionFollow the steps in this section to change the name of an ADS/ADX. The ADS/ADX name and the computer namemust match for proper functionality.

Important: After you follow these procedures for a Site Director, the fully qualified item references in historical datado not match the fully qualified item references in historical data, because the references have the newADS/ADX name. Note this detail when using tools that can access historical data, such as the MetasysExport Utility, which retrieves data representing the old item references.

Important: Do not follow these instructions for an ADS/ADX Turnkey computer. To rename an ADS/ADXTurnkey computer, refer to Appendix A: Changing the ADS/ADX Name and the Computer Name of theADS/ADX Turnkey User’s Guide (LIT-12011177).

Overview of Changing the ADS/ADX Name and the Computer NameThis section provides an overview of the steps to change the ADS/ADX name and the computer name. You mustperform all the steps referenced in this section in the correct sequence to ensure success.

1. Prepare the computer. See Preparing the Computer.2. Prepare the archive. See Using an Existing Archive or Creating a New Archive.3. Uninstall the ADS/ADX and SCT software. See Uninstalling and SCT Software.4. Rename the computer. See Renaming the Computer.5. Verify SQL Server software and Reporting Services functionality. See Verifying SQL Server Software and

Reporting Services.6. Reinstall the software. See Reinstalling Metasys Software.7. Download the ADS/ADX. See Downloading the ADS/ADX.8. Test the ADS/ADX. See Finalizing ADS/ADX Settings.9. Upload your changes to the SCT. See Uploading ADS/ADX Name Changes to the SCT.

Preparing the Computer1. If the computer has been running for several days, restart the computer and leave it connected to the network

so that it can use its current IP address. If this is a new computer, connect it to a hub or switch before startingso that the computer can obtain a valid IP address. Type ipconfig in a command window to verify an IP addresshas been assigned.

Important: If you do not obtain a valid IP address in Step 1, the computer rename process may fail.2. Log on to the ADS/ADX Site Management Portal to verify the ADS/ADX is running.3. Exit the ADS/ADX Site Management Portal.4. Make sure the SCT and all other applications are closed.5. If the Ready Access Portal software if installed, remove it now by using the steps in the Ready Access Portal

Software Installation Instructions (LIT-12011523). Make sure you do not remove Ready Access Portal databases.You reinstall the software after the rename procedure.

6. Click or double-click the clock in the lower right-hand corner of the desktop to verify that the time zone and timefor the computer are correct.

7. Write down the new name you want to assign to the ADS/ADX computer. Note the case of each letter becausethe name is case sensitive. The new ADS/ADX name must:

• begin with a letter• contain a maximum of 15 characters• contain only letters A-Z (upper or lower case), numbers 0-9, and hyphens

8. Change the computer name label stamped on the ADS/ADX computer to the new name in Step 7.


9. Open the System Properties window (Figure 33).

If you are using Windows 7 OS or Windows Server 2008 R2 OS, open Control Panel and select System andSecurity > System. The System window appears.

If you are using Windows Server 2008 OS, open Control Panel and select System and Maintenance > System.The System window appears.

If you are using Windows XP Professional OS, open Control Panel and select System. The System Propertieswindow appears. Select the Computer Name tab.

Figure 33: System Properties or System Window - Windows 7 OS and Windows Server 2008 OSExamples

10. Write down the original ADS/ADX name as it appears in the Full computer name field. Be sure to note if thecomputer contains a domain name or a workgroup is specified. You need to reconfigure the computer with thisinformation after the rename. Also note the case of each letter as the computer name is case sensitive.

11. Close all windows.12. Log on to the ADS/ADX Site Management Portal to verify that the ADS/ADX is running.

Note: Ignore the label for the ADS/ADX that appears in the Navigation Tree.


Note: If you see a screen asking for you to choose an Internet Service Provider, re-enable the networkconnection and go back to Step 2.

13. Exit the ADS/ADX Site Management Portal.14. Go to Using an Existing Archive or Creating a New Archive.

Using an Existing Archive or Creating a New Archive1. Log on to the SCT.2. If you are using an existing archive with an ADS/ADX, open the archive and go to Step 8.

If you are creating a new archive, select Item > New Archive.3. Enter a unique name for the new archive. When you are asked to create a new site, click Yes.4. Follow the Insert Site Wizard instructions to create a new site.

The order of the time zones in the Metasys software does not match the order in which they are presented inthe Windows OS. Use care to select the correct time zone from the list, expanding the time zone display ifneeded to view the exact time zone name.

5. Finish the rest of the steps in the Insert Site Wizard.6. When the Create Device box appears, select Metasys server from the drop-down selection box. Click OK.7. Follow the Insert Site Wizard instructions to create the Metasys server. On the Identifier screen, enter the original

ADS/ADX computer name from Step 10 of Preparing the Computer. Finish the rest of the steps in the wizard.

When you are finished creating the new device, the name of the Metasys Server shown in the navigation treeshould match the original ADS/ADX name.

8. Select the Metasys server in the navigation tree.9. On the Tools menu, click Load Archive.10. On the Load Type screen, under Type, click Upload from Device.11. Click Next on each Load Wizard screen until you reach the Site Login screen.12. On the Site Login screen, click Test Login. If the name you entered for the ADS/ADX matches the computer’s

name, the log on process should succeed.13. Click Next on each of the remaining Load Wizard screens to start the upload process.

Note: If the upload is not successful, restart the computer and go to Step 1 in this section.14. When upload Completion Status reports OK, right-click the Metasys server in the navigation tree, and click

Rename. The Rename box appears.15. In the New Name field, enter the new ADS/ADX name from Step 7 of Preparing the Computer.16. Click OK.17. If you have existing user views, open each user view in Edit mode in the SCT, use the Find/Replace function

to change the name, and save the user view. The Site Director portion of the reference updates to match thenew Site Director name.

Note: Do not download or make other name changes in the SCT.18. Using SCT, back up the archive database by selecting Database > Create Backup.19. Go to Uninstalling and SCT Software.

Uninstalling and SCT Software1. Start Windows Explorer. If you are using Windows XP Professional OS, navigate to:

C:\Documents and Settings\All Users\Application Data\JohnsonControls\MetasysIII\SQLData\SSRSsync

If you are using Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS, navigate to:C:\ProgramData\Johnson Controls\MetasysIII\SQLData\SSRSsync


2. Rename the SSRSsync folder to SSRSsync1. This action relocates the contents of this folder before you uninstallthe ADS/ADX software in Step 3. The folder contains a batch file that you need in Step 11 of Renaming theComputer.

3. Uninstall the Metasys ADS/ADX software. Make sure you do not delete the databases, currently scheduledactions, or license keys. Restart the computer and log on.

4. Uninstall the Metasys SCT software, making sure you do not remove scheduled actions from the SCT. Restartthe computer and log on.

5. Go to Renaming the Computer.

Renaming the ComputerImportant: Be sure to complete the steps in Preparing the Computer, Using an Existing Archive or Creating a New

Archive, and Uninstalling and SCT Software before following the steps in this section. Renaming thecomputer is only one step in the process of changing the name of the ADS/ADX.

Note: Make sure you do not skip Step 9 through Step 11; otherwise, the Metasys Database Manager displays theincorrect name for the SQL Server database.

1. If you are using Windows 7 OS or Windows Server 2008 R2 OS, click the Start button and select Control Panel> System and Security > System. The System window appears (Figure 33). Click Change settings. Click Yesif prompted by the User Access Control dialog.

If you are using Windows XP Professional OS, select Start > Settings > Control Panel > System. Select theComputer Name tab.

If you are using Windows Server 2008 OS, select Start > Control Panel > System and Maintenance > System.The System window appears (Figure 33). Click Change settings. Click Continue if prompted by the User AccessControl dialog.

2. Click Change.3. In the Computer name field, enter the new ADS/ADX name from Step 7 of Preparing the Computer. If this

computer is a member of a domain, specify the name in the Domain field. If the computer name included a DNSsuffix, enter the DNS suffix.

Note: If you join the computer to a domain, the DNS suffix appears automatically. If you join the computer toa workgroup, the DNS suffix is optional.

4. Click OK.5. Click OK when you are prompted to restart the computer.6. Close all windows.7. Restart the computer, then log on.8. Wait five minutes to ensure that all Windows services are fully started.9. If you are using Windows 7 OS, or Windows Server 2008 R2 OS, or Windows Server 2008 OS, select Start >

All Programs > Accessories. Then right-click Command Prompt and select Run as Administrator. ClickContinue or Yes if prompted by the User Access Control dialog. If you are using Windows XP Professional OS,select Start > Run. Type cmd and press Enter to open a command window.

10. If you are using Windows 7 OS, or Windows Server 2008 R2 OS, or Windows Server 2008 OS, type thiscommand and press Enter:

cd C:\ProgramData\Johnson Controls\MetasysIII\SQLData\SSRSsync

If you are using Windows XP Professional OS, type this command and press Enter:

cd C:\Documents and Settings\All Users\Application Data\JohnsonControls\MetasysIII\SQLData\SSRSsync1

11. Type SQLRename.bat and press Enter. If you need SA user access rights to SQL Server, type SQLRename.bat<SA user name> <password> and press Enter. A script runs in the command window.

12. When the script is finished, close the Command Prompt window.


13. Restart the computer, then log on.14. Go to Reinstalling Metasys Software.

Verifying SQL Server Software and Reporting Services1. Start SQL Server Configuration Manager and verify that both SQL Server and SQL Server Reporting Services

are running. If either of these instances is not running, right-click its instance name and click Start.2. Start the Reporting Services Configuration Manager.3. In the left pane, click Web Service URL. In the right pane, click the link for the Report Server Web Service URL.

Verify the Web pages displays properly.4. In the left pane, click Report Manager URL. In the right pane, click the link for the Report Manager Site Identification

URL. Verify the Web page displays properly.

Note: This page may take up to 30 seconds to appear.

If Reporting Services is not working properly, wait several minutes and attempt this procedure again. If failurespersist, refer to the Metasys Advanced Reporting System Troubleshooting section in the ADS, ADX, and SCTInstallation and Upgrade Instructions Wizard Content (LIT-12011331).

Reinstalling Metasys Software1. Insert the SCT media and run the installation file (setup.exe). Follow the Install Wizard steps to install the SCT

software. Refer to Installing the SCT Software in the ADS, ADX, and SCT Installation and Upgrade InstructionsWizard Content (LIT-12011331).

2. Log on to the newly installed SCT and restore the database backup you created in Step 18 of the Using anExisting Archive or Creating a New Archive section.

3. Insert the ADS/ADX media and run the installation file (setup.exe). Follow the Install Wizard steps to install theADS/ADX software. Refer to Installing/Upgrading the ADS/ADX Software in the ADS, ADX, and SCT Installationand Upgrade Instructions Wizard Content (LIT-12011331).

4. Insert the Ready Access Portal media and run the installation file (setup.exe) if you previously removed thesoftware. Refer to the Ready Access Portal Installation Instructions (LIT-12011523).

5. Go to Downloading the ADS/ADX.

Downloading the ADS/ADX1. If you are using Windows 7 OS, select Start > Control Panel > System. Click Change settings. The System

window appears (Figure 33).

If you are using Windows Server 2008 R2 OS, select Start > Control Panel > System and Security > System.Click Change settings. The System window appears (Figure 33).

If you are using Windows XP Professional OS, select Start > Settings > Control Panel > System. The SystemProperties window appears. Select the Computer Name tab (Figure 33).

If you are using Windows Server 2008 OS, select Start > Control Panel > System and Maintenance > System.Click Change settings. The System window appears (Figure 33).

2. In the Full computer name field, verify that the computer name matches the new ADS/ADX name from Step7 of Preparing the Computer.

3. Close the System Properties window.

Note: Do not log on to the ADS/ADX at this time. It may be in an invalid state. Continue with the steps.4. Verify the name in SQL Server ConfigurationManager matches the new ADS/ADX name fromStep 7 ofPreparing

the Computer. For SQL Server 2008, select Start > Programs or All Programs > Microsoft SQL Server 2008 >Configuration Tools > SQL Server Configuration Manager. For SQL Server 2008 R2, select Start > Programsor All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager.

5. In the tree in the left pane, click SQL Server Services. In the right pane, double-click SQL Server(instancename), where instancename is the name of your SQL Server instance. In the SQL Server(instancename) Properties box, click the Service tab. Verify that the name in the Host Name field matches thenew ADS/ADX name.


Note: It is normal for the name to appear in upper case letters in the SQL Server Configuration Manager.6. Close all windows.7. Log on to the SCT.8. If you have any user views, open each user view in Edit mode in the SCT, use the Find/Replace function to

change the name to the new name, and save the user view. The Site Director portion of the reference updatesto match the new Site Director name.

9. Click the Metasys server in the navigation tree.

Note: At this time, it is normal for the site name to be the same as the original ADS/ADX name. Do not attemptto change the site name at this time.

10. On the Tools menu, click Load Archive.11. In the Type drop-down list box, select Download to Device.12. Follow the wizard instructions to download the Metasys server. Be sure to do the following:

a. On the Site Login screen, click Test Login to verify you can communicate with the server.b. On the Device Change screen:

• Do not select Use this option to rename a device via download.• Do not select Use this option to change a device address via download.

13. Click Next and continue with the wizard to start the download process.14. When the completion status reports OK, exit the SCT. The status may also report Server requires a manual

reset (571). This message is normal.15. Restart the ADS/ADX computer, then log on.16. Go to Finalizing ADS/ADX Settings.

Finalizing ADS/ADX SettingsTo finalize ADS/ADX settings:

1. Log on to the ADS/ADX Site Management Portal.2. Verify no user views are currently open.3. On the View menu, click Extended Labels.4. Double-click the Metasys site in the navigation tree.5. Click Edit in the Display pane.6. In the Name and Default ADS Repository attributes, enter the new ADS/ADX name. Note the case of each

letter because the name is case sensitive.7. In the Time Zone attribute, set the time zone to the correct zone.8. Click Save.9. On the Action menu, click Refresh All Tabs. The site and ADS/ADX name now match.10. Exit the ADS/ADX Site Management Portal.11. Restart the computer.12. Go to Uploading ADS/ADX Name Changes to the SCT.

Uploading ADS/ADX Name Changes to the SCT1. Log on to the SCT.2. Click the Metasys server in the navigation tree.3. On the Tools menu, click Manage Archive. The Manage Archive Wizard appears.4. In the Type drop-down list box, click Upload From Device.5. On the Select Devices screen, select the Metasys server in the navigation tree.6. Click Next on each Load Wizard screen until you reach the Site Login screen.7. On the Site Login screen, click Test Login.


Note: If this fails, go back to Changing the ADS/ADX Name and the Computer Name on an ADS and UnifiedADX Introduction and start the rename procedure over again.

8. Click Next on each of the remaining Load Wizard screens to finish the upload process.

When upload Completion Status reports OK, the upload is complete. The site and server names now match.9. Exit the SCT.10. Restart the ADS/ADX computer, then log on.11. If you are not using the Metasys Advanced Reporting System, the verification and rename processes are

complete. Go to Step 12.

If you are using the Metasys Advanced Reporting System, go to Verifying SQL Server Software and ReportingServices.

12. If you uninstalled the Ready Access Portal software at the beginning of the rename process, reinstall it by usingthe steps in the Ready Access Portal Software Installation Instructions (LIT-12011523). The verification andrename processes are complete.


Appendix: Configuring and Maintaining PreferencesConfiguring and Maintaining Preferences IntroductionTheMetasys system provides customized preferences for the UI. The preferences allow authorized users to configurehow the UI behaves, including the sounds and colors, the startup view, and the ability to add links to externalapplications that can be accessed from within the UI of the ADS/ADX/SCT/NAE device.

Important: Preferences do not persist after an upgrade unless you take manual steps to save the settings beforeyou begin a system upgrade. See Preserving Preferences in an Upgrade.

Some steps in the following sections involve certain file operations, such as copying files and navigating to specificfolders. The tool used for these operations is either Windows Explorer (ADS, ADX, SCT, NAE55, NIE55, NxE85) orInternet Explorer Web browser (NAE35, NAE45, or NCE25). For an NAE55/NIE55, log on to the device remotelyusing the NxE Information and Configuration Tool (NCT), then use the Remote Desktop function of NCT. Typeexplorer at the command prompt. For an NAE35/NAE45/NCE25, use the NAE Configuration Tool (NCT) and startthe FTP server. Access the NAE contents with Internet Explorer and type ftp://<NAE IP Address> in the Addressline. For information on the NCT, refer to theNxE Information and Configuration Tool Technical Bulletin (LIT-1201990).

Preferences ConceptsSystem and User PreferencesPreferences are divided into two categories: System Preferences and User Preferences.

System PreferencesSystem preferences apply to all users who log on to the site or device. System preferences affect the performanceand operation of the system. Only the MetasysSysAgent user and the BasicSysAgent user have authorization toconfigure system preferences. An audible alarm notification change is an example of a system preference. The SCTsupports a subset of system preferences. If the SCT is installed on an ADS/ADX, the preferences are shared by theUI and the SCT.

Before you make system preference changes, the preferences are read from the DefaultSystemPreferences.xmlfile. Once you make system preference changes, a new file called SystemPreferences.xml is created (Figure 34).Both of these files are located in the directory on the Metasys system device as indicated in Table 16.

Table 16: Location of Preferences FilesFile LocationMetasys System

Device

C:\Documents and Settings\All Users\Application Data\Johnson Controls\MetasysIII\Preferences1ADS/ADX

C:\ProgramData\Johnson Controls\MetasysIII\Preferences2

NAE55/NIE55 C:\Documents and Settings\All Users\Application Data\Johnson Controls\MetasysIII\Preferences

C:\ProgramData\Johnson Controls\MetasysIII\PreferencesNAE85/NIE85

\Storage\Metasys\PreferencesNAE35/NAE45/NCE25

1 This location applies if you have Windows XP Professional OS.2 This location applies if you have Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS.

The procedure to synchronize system preferences within a site or to reuse the system preferences on another siteis a manual copy and paste process. Use the process to copy system preferences to other devices on the site or toother sites. See Copying Preferences between Devices.


Figure 34: System Preference Files

As highlighted in Figure 34:

• DefaultSystemPreferences.xml: This is the default system preferences file. It is installed as part of the standardinstallation for all Metasys system devices.

• SystemPreferences.xml: This file stores the configured system preferences. If you have not yet configuredsystem preferences, this file does not appear in the directory.

User PreferencesUser preferences apply to a specific Metasys system user. User preferences define how the information is displayedin the UI and do not affect the operation of the system. The colors and marker styles of a trend display are examplesof user preferences. Each user is authorized to view and edit their own user preferences.

The system automatically assigns a numbered user preference file name for each user calledUserPreferences-userID.xml, where userID is the identification number of the user. Using an identification number,rather than using the actual user name, serves two purposes. First, it avoids any conflicts that might arise if the username contains special characters. Second, it allows the user to be renamed without breaking the connection to theuser preferences file.

To view user identification numbers, open the Security Administrator screen and select User Preference File Namesunder the View menu (this option is available only to the MetasysSysAgent user). The user preference file namesappear in the Roles and Users pane (Figure 35) and correspond to files on the Metasys device in the directory asindicated in Table 16. As shown by two callouts in Figure 35:

• 1: User preference file name as seen in the Security Administration in the UI.• 2: User preference file as seen when accessing an NAE using Remote Desktop in the NCT.

The procedure to synchronize user preferences within a site or to reuse the user preferences on another site is amanual copy and paste process. Use the manual process to copy user preferences to other devices on the site orto other sites. See Copying Preferences between Devices.


Figure 35: User Preference File

Managing PreferencesPreferences are not archived on the SCT and they are not part of the upload/download process. Additionally,Preferences are not saved during a security backup when you upgrade. Preferences must be managed manually.

For information on managing preferences for each preference type, see the following sections:

• System Preferences• User Preferences


Detailed ProceduresConfiguring PreferencesNote: To configure the preferences of a specific user, you must log on as that user or as a user with Administrator

rights.

1. On the Tools menu of the UI, click Configure Preferences. The Metasys Preferences dialog box appears.2. Set the preferences according to the Preferences section of the Metasys system Help.

If you specified Level 1-4 Sound Files on the Alarm Settings tab, place the alarm sound files into the audio folderon the Metasys system device. The audio folder is located in the following directory:

For ADS/ADX/NAE55/NIE55/NAE85/NIE85:

C:\Inetpub\wwwroot\MetasysIII\UI\audio

For NAE35/NAE45/NCE25:

\Storage\Metasys\wwwroot\metasysIII\UI\audio

Note: If a sound file is missing from the folder, the Metasys system uses the default system beep for that alarmpriority.

Restoring Default System Preferences1. Access the Metasys system device on which you want to restore the default system preferences. (For example,

if this is an NAE55, use the Remote Desktop option available with NCT.2. Navigate to the Preferences directory for the device as shown in Table 16.3. Delete the SystemPreferences.xml file.

Copying Preferences between Devices1. Access the source Metasys system device; that is, the one that contains the preferences you want to copy. (For

example, if this is an NAE55, use the Remote Desktop option available with NCT. The local hard drive of yourcomputer is automatically mapped to the NAE through remote desktop.)

2. Navigate to the Preferences directory for the device as shown in Table 16.3. Copy SystemPreferences.xml (system preference) or UserPreferences-userID.xml (user preference), where

userID is the identification number that appears in the Security Administration tool.4. Paste the file onto the desktop of your computer.5. If you are accessing the Metasys system device remotely, log off.6. Access the destination Metasys system device (where you want to copy the preferences) with the

MetasysSysAgent user and navigate to the Preferences directory for the device as shown in Table 16.7. Paste the SystemPreferences.xml file or UserPreferences-userID.xml file that you copied to your computer

desktop with Step 4.

Restoring Default User Preferences1. Log on to the Metasys UI as the MetasysSysAgent user.2. On the Tools menu of the UI, select Administrator. The Security Administration tool appears.3. On the View menu, select User Preference File Names. The user preference file names appear in the Roles and

Users pane of the Security Administration tool.4. Record the file name of the user whose preferences you want to restore.

Note: If the user has been removed from the system, there is no record of the user preference file name in theSecurity Administration tool. In this case, remove user preference files from the Metasys device that donot have a corresponding user preference file name in the Security Administration tool.

5. Close the Security Administration tool and continue with Removing User Preference Files.

Removing User Preference Files1. Access the Metasys device from which you want to remove the user preference files and navigate to the

Preferences directory for the device as shown in Table 16.


2. Delete files named UserPreferences-userID.xml, where userID is the identification number that appears in theSecurity Administration tool.

Note: Do not delete DefaultUserPreferences.xml.

Copying User Preferences to Another User1. Log on to the Metasys UI as the MetasysSysAgent user.2. On the Tools menu of the UI, select Administrator. The Security Administration tool appears.3. On the View menu, select User Preference File Names. The user preference file names appear in the Roles and

Users pane of the Security Administration tool.4. Record the file name of the user whose preferences you want to copy (Source User) and the file name of the

user whom you want to share those preferences (Destination User).5. Close the Security Administration tool.6. Access the Metasys device and navigate to the Preferences directory for the device as shown in Table 16.7. Delete the preference file (if it exists) of the Destination User that you recorded in Step 4.8. Copy and paste the user preference file of the Source User you recorded in Step 4. If using Windows Explorer,

the file appears in the folder with Copy of appended to the front of the file name.9. Rename the copied file to the original name of the Destination User preference file name.

Preserving Preferences in an UpgradePreferences do not persist after an upgrade unless you take manual steps to save the settings before you begin asystem upgrade.

1. Before you begin the upgrade process, access the source Metasys system device that contains the preferencesyou want to copy. (For example, if this is an NAE55, use the Remote Desktop option available with NCT. Thelocal hard drive of your computer is automatically mapped to the NAE through remote desktop.)

2. Navigate to the Preferences directory for the device as shown in Table 16.3. Copy SystemPreferences.xml (system preference) or UserPreferences-userID.xml (user preference), where

userID is the identification number for each specific user with customized preferences. If you are saving preferencesfor multiple users, be sure to copy all files.

4. Paste these files in a safe location on your computer or network drive, or store them on other media.5. Upgrade your system according to the ADS, ADX, and SCT Installation and Upgrade Instructions Wizard

(LIT-12011521) and other appropriate documentation.6. Copy the files from the safe location in Step 4 back to the directory in Step 1.


Appendix: Microsoft® Windows® Operating System (OS) and SQLServer™ Software License RequirementsWindows OS License RequirementsThe Microsoft operating system software used by the ADX requires licenses called Client Access Licenses (CALs).A CAL is a license that gives you the right to access the services of the server. Two types of Microsoft operatingsystem CALs are available: a device-based CAL and a user-based CAL. These Microsoft CALs are purchasedseparately from the ADX software as described in Purchasing and Designating CALs.

Note: The ADS does not require purchased OS CALs.

Operating System CALsEvery site requires a combination of both device and user CALs.

Operating System - Device CALs: A device CAL is required for every device that accesses the ADX server,regardless of the number of users who access the ADX. A device CAL is the best choice if your organization hasusers who access the Metasys network by sharing the same computer during their work shifts. Each NAE requiresone device CAL. For example, if 15 NAEs are connected to the ADX, a total of 15 device CALs are required. Or, if100 NAEs are connected to the ADX, a total of 100 device CALs are required.

Operating System - User CALs: A user CAL is required for every user who accesses the ADX server, regardlessof the number of computers they use for that access. A user CAL is the best choice if your organization has Metasysusers who need roaming access to the Metasys network using multiple computers. For example, if two users log into the ADX from different locations, two user CALs are required. Or, if 50 users log in to the ADX, 50 user CALs arerequired.

Another example is a security guard station. Security guards during different shifts often use a single workstation,requiring the use of only one device CAL. However, if the security guards use multiple workstations throughout thefacility, one user CAL per guard is required. In this example, a single user CAL is more cost-effective, because asingle ADX connection requires only one user CAL.

Total Number of CALs: The total number of device and user CALs required equals the total number of devices andusers connected to the ADX.

Example One: If you have 100 NAEs and 10 users who use different workstations to log in, you need 110 CALs(100 device CALs and 10 user CALs).

Example Two: If you have 100 NAEs and 10 users who use the same workstation to log in, you need 101 deviceCALs (100 device CALs for NAEs and 1 device CAL for workstation).

Table 17 lists the ADX software components and examples of what CAL combinations are required. Refer to theMetasys System Extended Architecture Overview Technical Bulletin (LIT-1201527) for the number of devices anADX supports.


Table 17: ADX OS License and CAL ExamplesWindows OS CAL ExamplesRecommended

Number of CALs toPurchase

Optional MVEOffering

ADX Offering

5 CALs = 2 user CALs + 3 device CALs5MVE5

(up to 5 users)

ADX10

(up to 10 users) 5 CALs = 3 user CALs + 2 device CALs




(up to 25 users)

ADXSWO



(up to 50 users)

ADX50


If you purchase Metasys system software separately from the hardware, use Table 17 to determine how many CALsyou need to purchase from Microsoft. If you purchase Metasys system software as part of an ADS/ADX Turnkey orADS/ADX Ready product, the appropriate number of CALs is included in the purchase. For more details, seePurchasing and Designating CALs.


Licensing Modes and CAL ExamplesFigure 36 illustrates the use of CALs in a Metasys network.

Figure 36: Example Network in Per Device or Per User OS Licensing Mode

SQL Server Licensing RequirementsThe SQL Server software editions used by the ADX product, including SQL Server 2008 R2 Standard or Enterpriseand SQL Server 2008 Standard or Enterprise, require CALs. However, the SQL Server software editions used bythe ADS product, including SQL Server 2008 Express R2 and SQL Server 2008 Express, do not require CALs.

If your ADX computer has a single processor, we recommend you purchase one Processor License to allow anunlimited number of users, NAE/NIE/NCE devices, and ADS/ADX computers to access the SQL Server databaseon that computer. If your ADX computer running SQL Server software has multiple processors, purchase ProcessorLicenses for all of the processors on that computer. Licensing is based on the number of physical CPUs in thecomputer, not the number of core processors. For example, if the computer has a single quad-core processor, onlyone processor license is required.


For a split ADX, SQL Server software is installed on the database server computer. You must purchase a singleprocessor license for the database server computer if the computer has a single processor. If the database servercomputer has more than one processor, you must purchase one SQL Server processor license for each processor.

For a split ADX with the Metasys Advanced Reporting System, the database engine component of SQL Serversoftware is present on the database server computer, and the reporting services component of SQL Server softwareis installed on the web/application server computer. You must purchase a single processor license for both thedatabase server computer and the web/application server computer.

Table 18 lists the ADS/ADX software components and the OS license types that they require.

Table 18: SQL Server License RequirementsSQL Server ProcessorLicense

SQL Server Software CurrentlySupported

OptionalMVEOfferingADX Offering

1 Processor LicenseSQL Server 2008 R2 Software

OR

SQL Server 2008 Software

MVE5 (up to 5 users)ADX10 (up to 10 users)

MVE10 (up to 10 users)

MVE25 (up to 25 users)ADXSWO (up to 25 users)

MVE50 (up to 50 users)ADX50 (up to 50 users)

ADS RequirementsThe ADS and ADS-Lite software that runs on Windows XP Professional OS or Windows 7 OS do not come with,and do not require, device or user CALs. Also, the ADS uses the free version of SQL Server Express software, soyou do not need to purchase SQL Server CALs.

To avoid ADS connection and network communication performance issues, the number of users and the numberof NAE/NIE/NCE devices and ADS/ADX computers that transfer trend data, event messages, and audit messagesshould not exceed 10. If a Metasys site with a single ADS configured as the Site Director and default repositoryexceeds that number of connections, consider one of the following options:

• Configure one ADS to be the Site Director. Install and configure another ADS (or more) to provide the ADSrepository function. When you install a separate ADS to provide the repository function, it allows you to dedicatefive connections on the alternate ADS for system users and another five connections on the alternate ADS toNAE/NIE/NCE devices and ADS/ADX computers for transferring trend data, event messages, or audit messages.

Note: The ADS-Lite cannot be the Site Director for another ADS of any type.

• Upgrade to an ADX. Configure the Windows Server OS of the ADX computer with the number of CALs equal tothe total number of users and devices accessing the ADX. In addition, configure the SQL Server database withone SQL Server Processor license.

Refer to the Metasys System Extended Architecture Overview Technical Bulletin (LIT-1201527) for performanceguidelines and limitations.

Purchasing and Designating CALsYou need to purchase one additional device CAL for every NAE added to your Metasys system. You may also needto purchase additional user CALs as you expand the number of authorized Metasys system users. If you currentlyhave an ADS and you expand your system to require more than 10 connections, upgrade to an ADX.

For CAL purchasing information, log in to the Johnson Controls employee portal website, go to the Tools & Applicationspage, then click the Computer Price List (ADS/ADX Turnkey Info) link in the Procurement/Purchasing section.The Computer Price List page appears. Review this page to learn how to access the Insight/JCI website(http://www.insight.com/jci) that contains information about purchasing CALs.

When you purchase CALs, you receive a paper certificate fromMicrosoft. There is no method in the operating systemto designate or configure the number of device or user CALs. So make sure you keep the Microsoft CALs certificatein safekeeping at the customer site in case of an audit. You may be subject to a fine if a security audit reveals thatyour system is not correctly licensed.


http://www.insight.com/jci

If Metasys system software is purchased separately, the customer is responsible for purchasing the correct numberof CALs and for properly designating each CAL. A device CAL cannot be transferred to a user CAL, or vice versa.If a Metasys Ready or Turnkey computer is purchased, the proper number of CALs come with the purchase, so noadditional CALs are required. Ultimately, the customer must determine how to split the total number of CALs betweendevice and user.

For additional information on CALs, licensing, and downgrading OS CALs, refer tohttp://www.microsoft.com/licensing/about-licensing/client-access-license.aspx.


http://www.microsoft.com/licensing/about-licensing/client-access-license.aspx

Appendix: Moving Historical Data From Existing ADS/ADXInstallationImportant ConsiderationsImportant considerations include the following:

• The steps covered in this section only apply if the operating systems and SQL Server versions of the twocomputers are the same. If the OS and the SQL Server versions do not match, make changes to match the twosystems before continuing.

• This procedure can take several hours to complete, depending on the size of the archive databases and yourlevel of experience with SQL Server software. Be sure to allow enough time to finish all the steps.

• You must use an account with full Administrator rights on the ADS/ADX computer to complete the databasetransfer procedure.

• The name of the new ADS/ADX computer must match exactly the name of the old ADS/ADX computer, becausethe ADS/ADX computer name is within every object reference name. To avoid possible network issues, do notallow two computers with the same name to be on the same network at the same time.

• We highly recommend that you configure the new ADS/ADX computer with the same static IP address as theold ADS/ADX computer, because this address could be defined in some NAEs as the ADS/ADX repository.

• If you do not want to lose any historical data while the system is down, make sure the buffers on the supervisoryengines are large enough to hold trend, event, and audit data. During the procedure, the ADS/ADX is offline forseveral hours and is unavailable to archive data until the new ADS/ADX comes online.

• Microsoft SQL Server Management Studio is required for some SQL operations. Be sure to use the edition ofSQL Server Management Studio that matches your edition of SQL Server software. A version of SQL ServerManagement Studio Express software is available on the Metasys software media. For information on how touse this third-party application, contact your Johnson Controls support representative.

• Metasys DatabaseManager is required for database backup and restore functions. Refer to theMetasys DatabaseManager Installation Instructions (LIT-12011553) and Metasys Database Manager Help (LIT-12011202).

• The JCIItemAnnotation database does not exist for ADS/ADX installations before Release 3.1. TheMetasysReporting database exists for ADX installations only (not ADS) to support the Metasys AdvancedReporting System and Metasys Energy Essentials.

• If you need more details on installing the OS, SQL Server software, and Metasys software, refer to the ADS,ADX, and SCT Installation and Upgrade Instructions Wizard Content (LIT-12011331).

Moving Historical Data From Existing ADS/ADX Installation IntroductionFollow the steps in this section to move the Metasys historical and security databases from an existing ADS/ADXcomputer to a different ADS/ADX computer. Typically, this procedure is required if you need to transfer the ADS/ADXapplication from a testing server to a production server. The historical databases that are moved include audit(JCIAuditTrails), alarm (JCIEvents), trend (JCIHistorianDB), annotation (JCIItemAnnotation), and reporting(MetasysReporting). The security databases that are moved are located under the SecurityDB and SecurityFilesfolders. The locations of the files you transfer depend on the operating system. See Table 19.


Table 19: File Locations on ADS/ADX ComputerWindows 7 OS

Windows Server 2008 R2 OS

Windows Server 2008 OS

Windows XP Professional OSFile

C:\ProgramData\JohnsonControls\MetasysIII\DatabaseFiles

C:\Documents and Settings\All Users\ApplicationData\Johnson Controls\MetasysIII\DatabaseFiles

Archive Database File

C:\ProgramData\JohnsonControls\MetasysIII\SQLData

C:\Documents and Settings\All Users\ApplicationData\Johnson Controls\MetasysIII\SQLData

Historical DatabaseFiles

C:\ProgramData\JohnsonControls\MetasysIII\SecurityDB

AND

C:\ProgramData\JohnsonControls\MetasysIII\SecurityFiles

C:\Documents and Settings\All Users\ApplicationData\Johnson Controls\MetasysIII\SecurityDB

AND

C:\Documents and Settings\All Users\ApplicationData\Johnson Controls\MetasysIII\SecurityFiles

Security Files

Note: C:\ in Table 19 represents the drive where the OS is installed.

Preparing the New ADS/ADX ComputerTo prepare the new ADS/ADX computer:

1. Install the same Windows operating system on the new ADS/ADX computer as the old ADS/ADX computer,assigning exactly the same computer name as the old computer. Make sure you format the hard drive as partof installing the OS, and perform the OS installation off the network.

2. Configure the new ADS/ADX computer with exactly the same IP address, subnet mask, default gateway, andDNS server configuration as the old ADS/ADX computer, but do not connect the new computer to the networkuntil told to do so. If this is a split ADX, use the same address information from the old Application Web servercomputer and the old Database server computer.

3. Install the same edition of Microsoft SQL Server software on the new ADS/ADX computer as the old ADS/ADXcomputer. At the end of installation, make sure you perform surface area configuration for SQL Server software.

4. Install any other prerequisite software components on the new ADS/ADX computer as required for ADS, ADX,and SCT software.

5. Install SCT. Refer to Installing the SCT Software in the ADS, ADX, and SCT Installation and Upgrade InstructionsWizard Content (LIT-12011331).

6. Install the Metasys Database Manager. Refer to the Metasys Database Manager Installation Instructions(LIT-12011553).

7. Go to the next section, Preparing the Old ADS/ADX Computer.

Preparing the Old ADS/ADX ComputerTo prepare the old ADS/ADX computer:

1. Verify that the old ADS/ADX computer has the Metasys Database Manager for the current release installed. Ifnot, install the Metasys Database Manager, referring to theMetasys Database Manager Installation Instructions(LIT-12011553).

2. Log in to the Site Management Portal UI of the old ADS/ADX computer.3. Forward audit messages from all supervisory engines to the ADS/ADX repository by following these steps for

each engine:

a. Select a supervisory engine in the Navigation tree.b. Select View > Audit Viewer. The Audit Viewer for that engine appears.c. Click Forward Messages. The messages are forwarded to the ADS/ADX repository.

4. Route archived trend data from all supervisory engines to the ADS/ADX by following these steps for each engine:


a. Select a supervisory engine in the Navigation tree.b. Select Action > Commands. A list of available commands appears.c. Select Archive, then click Send. The archived trend data is sent to the ADS/ADX.

5. Log in to the SCT and perform the following steps to upload the database of the ADS/ADX and each supervisorydevice:

a. Select Tools > Manage Archive.b. Select Upload from Device as the Load Type. Click Next.c. Select an ADS/ADX or supervisory engine to upload. Click Next.d. Follow the remaining steps in the Manage Archive Wizard to initiate the upload procedure.

6. Using SCT, back up the archive database by selecting Tools > Database > Create Backup. At Release 6.0,backing up the archive database also backs up the security database.

7. Make a copy of the archive database backup file onto a CD, DVD, or other removable media, so that you canmove it to the new ADS/ADX computer later. (For the default file location, see Table 19.)

8. Close the SCT.9. On the Control Panel, select Administrative Tools > Services. If you have Windows 7 OS, Windows Server 2008

R2 OS, or Windows Server 2008 OS, on the Control Panel select System and Security > Administrative Tools> Services.

10. In the Services window, double-click Metasys III Device Manager. The Metasys III Device Manager Propertieswindow appears.

11. Change the Startup type to Manual. Click Stop. This prevents the collection of any new audits, alarms, trends,and annotations from the supervisory engines to the ADS/ADXwhile you move the databases. Click OK to closethe Metasys III Device Manager Properties window.

12. Close all windows.13. Start the Metasys Database Manager and perform a full backup the following databases: JCIAuditTrails,

JCIEvents, JCIHistorianDB, JCIItemAnnotation, and MetasysReporting (Figure 37). (For details, refer to MetasysDatabase ManagerHelp [LIT-12011202]). If this is a split ADX, back up these databases on the database servercomputer.

Figure 37: Metasys Databases to Backup


14. Make a copy of the JCIAuditTrails, JCIEvents, JCIHistorianDB, JCIItemAnnotation, and MetasysReportingdatabase backup files onto a CD, DVD, or other removable media, so that you can move them to the newADS/ADX computer later. (For the default file location, see Table 19.)

15. Disconnect the old ADS/ADX computer from the network. If this is a split ADX, disconnect both the web/applicationserver computer and database server computer from the network.

16. Use the ipconfig command at a command prompt to verify that no connection to the network is active.17. Keep the old ADS/ADX computer on hand for several days in case a problem occurs during the transfer procedure.18. Go to Restoring the System to the New ADS/ADX Computer.

Restoring the System to the New ADS/ADX ComputerTo restore the system to the new ADS/ADX computer:

1. Connect the new ADS/ADX computer to the building network. If this is a split ADX, connect both the web/applicationserver computer and database server computer to the network.

2. Copy the backup files of the JCIAuditTrails, JCIEvents, JCIHistorianDB, JCIItemAnnotation, andMetasysReportingdatabases taken from the old ADS/ADX computer onto the hard drive of the new ADS/ADX computer. (For thedefault file location, see Table 19.) If this is a split ADX, copy these files to the database server.

3. Copy the archive database file from the old ADS/ADX computer onto the hard drive of the new ADS/ADX computer.(For the default file location, see Table 19.) If this is a split ADX, copy these files to the database server.

4. Start the Metasys Database Manager in Expert mode and separately restore the JCIAuditTrails, JCIEvents,JCIHistorianDB, JCIItemAnnotation, and MetasysReporting databases you copied in Step 2 (Figure 38). If thisis a split ADX, perform this step at the database server computer.

Figure 38: Metasys Database Restore Screen

5. Start SCT and restore the archive database that you copied in Step 3.6. Install ADS/ADX software. (Refer to Installing/Upgrading the ADS/ADX Software in the ADS, ADX, and SCT

Installation and Upgrade Instructions Wizard Content [LIT-12011331]). If this is an ADX and you are installingthe Metasys Advanced Reporting System, specify the archive database you restored in the previous step whenchecking the SQL Server connection.

7. Restart the new ADS/ADX computer.8. Start SCT and download the ADS/ADX archive database.9. Log in to the ADS/ADX and verify the supervisory controllers are online and properly communicating.


Building Efficiency507 E. Michigan Street, Milwaukee, WI 53202

Metasys® and Johnson Controls® are registered trademarks of Johnson Controls, Inc.All other marks herein are the marks of their respective owners. © 2013 Johnson Controls, Inc.

www.johnsoncontrols.comPublished in U.S.A.


ADX Commissioning

Documents

Transcript of ADX Commissioning