Database Tools Commissioning Guide - Johnson Controls

Database Tools Commissioning GuideCode No. LIT-12012254Software Release 9.0Issued August 2017

Document Introduction.............................................................................................................2Summary of Changes................................................................................................................2Attribute Name to ID Conversion Tool Overview....................................................................2

Attribute Name to ID Conversion Tool Workflow.............................................................................2Launching Attribute Name to ID Conversion Tool...........................................................................4Attribute Name to ID Conversion Wizard..........................................................................................5Convert Attribute Names to IDs in the Historian Database Dialog Box.........................................6

Data Precision Enhancement Tool Overview..........................................................................7Data Precision Enhancement Tool Workflow...................................................................................7Launching the Data Precision Enhancement Tool..........................................................................8Data Precision Enhancement Dialog Box.........................................................................................9Data Precision Enhancement Dialog Box Status...........................................................................10Data Precision Enhancement Dialog Box after Conversion.........................................................11

Detailed Procedures: Attribute Name to ID Conversion Tool..............................................12Attribute Name to ID Conversion Tool Requirements...................................................................12Manually Launching the Attribute Name to ID Conversion Tool..................................................13Resolving Point Names for Known Languages.............................................................................15Resolving Point Names for Unknown Languages.........................................................................16Resolving Point Names if More Than One Point ID Exists for an Attribute................................17Resolving Point Names with the Same Attribute...........................................................................18Verifying the Database Update........................................................................................................19Exiting without Updating the Database..........................................................................................20

Detailed Procedures: Data Precision Enhancement Tool....................................................20Data Precision Enhancement Tool Requirements and Restrictions............................................20Running the Data Precision Enhancement Tool............................................................................21

Troubleshooting: Attribute Name to ID Conversion Tool.....................................................23Troubleshooting: Data Precision Enhancement Tool...........................................................24Related Documentation...........................................................................................................25

1Database Tools Commissioning Guide

Document IntroductionThis document describes how to execute the Metasys® Post Installation (MPI) Database tool after installing theMetasys Server Application Data Server (ADS)/Extended Application Data Server (ADX) or Open Data Server (ODS)software if the installation notifies you that the database conversion failed.

The MPI Database tool is a Microsoft® Windows® application that is used to launch two plug-ins for resolvingdatabase problems that require user input:• Attribute Name to ID Conversion tool: converts the attribute name to the attribute ID in the existing JCIHistorian

database to match the new language independent data storage method at Metasys Server Release 8.0 andlater.

• The Data Precision Enhancement tool: converts the data type in the ADS, ADX, and ODS JCIHistorian databasefrom real to float.

This document does not describe how to prepare, install, or upgrade your computer with theMetasys Server software.Also, this document does not describe how to build, download, or manage a database.

If you are converting point names in the existing JCIHistorian database, see Attribute Name to ID Conversion ToolOverview and Detailed Procedures: Attribute Name to ID Conversion Tool. If you are converting a data type in theJCIHistorian database from real to float, see Data Precision Enhancement Tool Overview and Detailed Procedures:Data Precision Enhancement Tool.

Summary of ChangesNo technical changes were made to this document for Metasys Release 9.0.

Attribute Name to ID Conversion Tool OverviewThe Attribute Name to ID Conversion tool converts the attribute name to the attribute ID in the existing JCIHistoriandatabase to match the new language independent data storage method at Metasys Server Release 8.0 and later.The tool migrates trend samples that were collected at the earlier Metasys release for use with Release 8.0 or later.

Prior to Metasys Server Release 8.0, the Fully Qualified Attribute Reference (FQAR) of database trend sampleswere stored as language dependent text. In cases where the system default language was changed, the FQAR andthe trend samples associated with it were no longer accessible. As a result, the tool migrates trend samples thatwere collected at the earlier Metasys releases for use with Metasys Release 8.0 and later.

Metasys Server Release 8.0 and later stores trend samples using attribute identification numbers to provide forFQAR language independence. This modification requires the conversion of all point names in the existing JCIHistoriandatabase to include attribute numbers.

The Attribute Name to ID Conversion tool runs during theMetasys Server software installation to determine all FQARentities in the JCIHistorian database that belong to the same field point or attribute. After identifying the FQARentities, the tool changes the references in the trend sample objects to refer to this now unique point name. Theresulting attribute name is the numerical value for the attribute preceded with a # sign. The tool removes the unusedFQAR entities from the database after conversion.

Note: The Attribute Name to ID Conversion tool launches automatically during the Metasys Server installation orupgrade. You can also manually launch the tool at any time in cases where attribute names are identified inthe database.

Attribute Name to ID Conversion Tool WorkflowFigure 1 details the typical workflow for the Attribute Name to ID Conversion tool when upgrading an ADS, ADX, orODS to Metasys Server Release 8.0 and later.


Figure 1: Attribute Name to ID Conversion Tool Process


Launching Attribute Name to ID Conversion ToolThe Attribute Name to ID Conversion tool is designed to run during theMetasys Server installation or upgrade withoutuser interaction. You only need to launch the tool if the database conversion is unable to automatically process theconversion without user interaction.

Figure 2: JCIHistorian Database Exception Error

If the database conversion fails during the Metasys Server installation, you need to launch the tool manually. Thetool is located in the Tools folder of the MetasysIII installation folder(C:\Program Files (x86)\Johnson Controls\MetasysIII\Tools). The folder contains the Convert Attribute Namesto IDs for Trend link. Double-click this link to launch the Attribute Names to ID Conversion Wizard, which allowsyou to manually complete the conversion process. See Manually Launching the Attribute Name to ID ConversionTool for more information on how to launch the tool.

Figure 3: Convert Attribute Names to IDs for Trend Link Location


Attribute Name to ID Conversion WizardThe Attribute Name to ID Conversion Wizard resolves and merges all point names in the trend database. The wizardis activated when you select the Convert Attribute Names to IDs for Trend link in the MetasysIII installation folderpreviously discussed in Launching Attribute Name to ID Conversion Tool.

The wizard automatically resolves all point names with attribute names in US English. The tool also manually resolvesand merges point names with non-English attribute names.

Figure 4 shows an example of the Attribute Name to ID Conversion Wizard when it has been launched. The buttonoptions are described in detail in Table 1.

Note: In order to prevent you from accidentally closing the tool and leaving the database in an incomplete state,the wizard has no exit or minimize button. You cannot close the wizard unless you complete the databaseconversion or click the Cancel and Exit (Lose Changes) button.

Figure 4: Attribute Name to ID Conversion Wizard

Table 1: Attribute Name to ID Conversion Wizard CalloutDescriptionCalloutShows available conversion languages.1

Resolves the points for all attributes with the language selected in the drop-down box immediately above it. Thiscan be used when you know the language the trend samples are stored in. You need to select a language fromthe drop-down box before you click the button.

2

Exits the wizard to continue the conversion process with the Convert Attribute Names to IDs in the HistorianDatabase dialog box. Use this when you are unsure which language the trend samples are stored in, or thenumber of point names requiring resolution indicated is greater than 0.

3


Table 1: Attribute Name to ID Conversion Wizard CalloutDescriptionCalloutWrites any changes back to the database.

Note: The wizard only writes changes back to the database if you clickUpdate Database and Exit. The wizarddoes not automatically write these changes back during the process.

4

Cancels any changes and closes the wizard.5

Opens the log file.6

Convert Attribute Names to IDs in the Historian Database Dialog BoxThe Convert Attribute Names to IDs in the Historian Database dialog box allows you to interact directly with the pointnames when you are unsure which language the trend samples are stored in, or if the number of point namesrequiring resolution indicated in the Attribute Name to ID Conversion Wizard is greater than 0 after attempting toresolve all points.

Figure 5 shows an example of the Attribute Name to ID Conversion Dialog after you have left the Attribute Name toID Conversion Wizard. The buttons and features of the dialog are described in detail in Table 2.

Figure 5: Convert Attribute Names to IDs in the Historian Database Dialog Box

Table 2: Convert Attribute Names to IDs in the Historian Database Dialog Box CalloutDescriptionCalloutTable from which to choose attribute IDs (if necessary).1

Resolves an individual point with the same attribute name.2

Resolves all points with the same attribute name.3

Updates the JCIHistorian database.4

Closes the dialog box without saving.5


Table 2: Convert Attribute Names to IDs in the Historian Database Dialog Box CalloutDescriptionCalloutReverses all changes and rereads the current contents of the JCIHistorian database.6

Indicates how much of the process is completed.7

Table showing the point names and attribute of the JCIHistorian database.8

Opens the log file.9

Data Precision Enhancement Tool OverviewThe Data Precision Enhancement tool increases the precision of the stored values in the ADS, ADX, and ODSJCIHistorian database.

Before Metasys Server Release 8.0, the data was stored as a real data type in the database. For Metasys versions8.0 and later, data is stored as float data type to increase precision. The tool converts the data type from Metasysversions 7.0 and earlier in the database from real to float to allow users continued access to existing data atMetasysServer Release 8.0 and later.

Notes:• You do not always need to run the Data Precision Enhancement tool. This tool should only be executed if the

value precision is not satisfying current customer requirements.• If you need to execute the tool, we recommend that you start the conversion process immediately after the

Metasys Server installation or upgrade is complete.

Data Precision Enhancement Tool WorkflowFigure 6 details the typical workflow for the Data Precision Enhancement tool when converting the data type in theADS, ADX, and ODS JCIHistorian database from real to float.


Figure 6: Data Precision Enhancement Tool Process

Launching the Data Precision Enhancement ToolThe Data Precision Enhancement tool runs after you complete the Metasys Server installation or upgrade process.

The Data Precision Enhancement tool is located in the Tools folder of the MetasysIII installation folder(C:\Program Files (x86)\Johnson Controls\MetasysIII\Tools). The folder contains the Enhance Analog Precisionlink. Double-click this link to launch the Data Precision Enhancement Main Page, which converts the data type inthe database from real to float. See Detailed Procedures: Data Precision Enhancement Tool for more informationon how to launch the tool.


Figure 7: Enhance Analog Precision Link Location

Data Precision Enhancement Dialog BoxUse the Data Precision Enhancement dialog box to convert the data type in the database from real to float. Figure8 and Table 3 describe the layout of the MPI Tool for the Data Precision Enhancement dialog box.

Figure 8: Data Precision Enhancement Dialog Box


Table 3: Data Precision Enhancement Dialog Box CalloutsDescriptionCalloutSQL server version, level, and edition information.1

Free disk space available for the database drive and the drive letter.

Notes:

• If the .mdf and .ldf files exist on different drives, information for both drives is shown.• This field is not shown if the tool was started with a database that has already been converted.

2

Terminates the tool.3

Progress for the prerequisites check and each converted table.4

Status, warnings, and error messages pertaining to the process.5

Starts the conversion.

Note: The button is disabled if:• the tool is started with a database that has already been converted.• there is not enough free disk space available.• an error has been detected.

6

MPI.log file with conversion details.7

Required conversion time estimate.8

Number of analog rows.9

State of the data type throughout the process. For example, this field may contain SQL real or SQL float.10

Database .ldf file size in MB.11

Database .mdf file size in MB.12

Database name from the connection string.13

SQL server name from the database connection string.14

Data Precision Enhancement Dialog Box StatusThe status on the Data Precision Enhancement dialog box populates with a variety of messages throughout thedatabase conversion process. These include general messages, warnings, and error messages. Figure 9, Table 4,Table 5, and Table 6 describe the messages that can display in the status of the dialog box.

Figure 9: Status

Table 4: General Status MessagesDescriptionMessageThe conversion is still active.Active

The conversion has finished successfully.Done

The database is already converted.Data type float already exists in databaseanalog tables


Table 5: WarningsDescriptionMessageThe database drive does not contain enough free disk space for the conversion.Not enough free disk space on drive X.

Temporarily about X or more are required !

The tool needs permission to read the free disk space information.Warning: No free disk space informationfound via sql

The database size is too big for the conversion.SQL express database too big forconversion. Maximum supported size formdf: < 5 GB

Table 6: Error MessagesDescriptionMessageAn error occurred and can be reviewed by clicking Show Log.Error, see details in Log

An open database error occurred after the tool started. Click Show Log to showerror details.

Error during open database JCIHistorianDB

Data Precision Enhancement Dialog Box after ConversionThe layout of the Data Precision Enhancement dialog box changes after the database conversion is complete. Figure10 and Table 7 describe the layout of the Data Precision Enhancement dialog box after the conversion occurs.

Figure 10: Data Precision Enhancement Dialog Box after Conversion


Table 7: Data Precision Enhancement Dialog Box after Conversion CalloutsDescriptionCalloutSQL server version, level, and edition information1

Displays the actual value2

Terminates the tool3

Displays progress in green4

Done5

Disabled6

MPI.log file with conversion details7

SQL float8



Database name from the connection string11

SQL server name from the database connection string.12

Detailed Procedures: Attribute Name to ID Conversion Tool

Attribute Name to ID Conversion Tool RequirementsYou need a computer installed with the Metasys Server Release 8.0 or later software to run the Attribute Name toID Conversion tool.

Important: When merging a number of trend samples, the process can take over one hour. Before you begin,ensure that your computer is plugged in and is not set to automatically log out or reboot.


Manually Launching the Attribute Name to ID Conversion ToolNote: The Attribute Name to ID Conversion tool runs during the Metasys Server installation or upgrade process

without interaction from the user. You only need to launch the tool if the database conversion is unable toautomatically process the conversion without user interaction.

Figure 11: JCIHistorian Database Exception Error

Click View log for more details for more information regarding the conversion failure. The Editor dialog boxappears.

Figure 12: Editor Dialog Box

The following procedure outlines how to manually launch the tool when the Metasys Server installation or upgradeprocess fails.

1. Launch the Attribute Name to ID Conversion tool using Windows File Explorer. Browse toC:\Program Files (x86)\Johnson Controls\MetasysIII\Tools.

2. Double-click the Convert Attribute Names to IDs for Trend executable file. The MPI dialog box for resolvingpoint trends appears. The tool performs a short analysis of the current trend database.


Figure 13: MPI Dialog Box for Resolving Point Trends

3. Click Yes to bring up the Attribute Name to ID Conversion Wizard's main window.

Note: If no update is necessary, a second MPI dialog box appears to confirm that no updates are required.Click OK. Restart the Metasys system if it stopped before launching the MPI tool.

Figure 14: MPI Dialog Box for Confirming No Updates Required

Figure 15: The Attribute Name to ID Conversion Wizard Window

Note: The Attribute Name to ID Conversion Wizard window shows the number of point trends with namedattributes in US English that resolved automatically.


4. Click Update Database and Exit if the remaining number of point trends that need resolving is 0. Changes arethen written back to the database.

Figure 16: No Remaining Point Trends to Resolve

5. If additional point names require resolution and you know the language configured for the Metasys network, goto Resolving Point Names for Known Languages. If you do not know the language, go to Resolving Point Namesfor Unknown Languages.

Resolving Point Names for Known Languages1. Select the language from the drop-down list.

Figure 17: Attribute Name to ID Conversion Wizard Language Selection

2. Click Resolve all points for all attributes with the current language.


Figure 18: Attribute Name to ID Conversion Wizard Language Selected

3. Click Update Database and Exit if the number of point names requiring resolution is now 0. The SuccessfulUpdate dialog box appears.

4. Click OK.5. If additional point trends require resolution, points with other unknown languages exist. Go to Resolving Point

Names for Unknown Languages.

Resolving Point Names for Unknown Languages1. Click Skip this step and proceed or proceed with the changes already made in the Attribute Name to ID

Conversion Wizard. The Convert Attribute Names to IDs in the Historian Database dialog box appears.


Figure 19: Convert Attribute Names to IDs in the Historian Database Dialog Box

2. If you need to resolve point names because more than one point ID exists for an attribute, go to Resolving PointNames if More Than One Point ID Exists for an Attribute. If you need to resolve point names with the sameattribute, go to Resolving Point Names with the Same Attribute.

Resolving Point Names if More Than One Point ID Exists for an Attribute1. Select a point in the left grid of the Convert Attribute Names to IDs in the Historian Database dialog box that

needs updating. The possible attribute IDs for the point you selected in the grid appear on the right of the dialogbox.


Figure 20: Resolving Point Names if More Than One Point ID Exists for the Same Attribute Name

2. Select the appropriate attribute ID from the grid on the right of the dialog box.

Note: Some points may not have matching attribute names in any of the known languages. If this occurs, thegrid on the right of the dialog box will list all possible attributes sorted by ID. Select the attribute that isdefined for the trend extension of this point. Select ID: 85 if the trend extension for the point is not available.

3. Click Resolve selected Point: X Trend Attribute: X with Attribute ID: XXX.

Note: If additional points require resolution, repeat Step 1 through Step 3 until all points are resolved.4. Click Update Database and Exit to write your changes back to the database. The Successful Update dialog

box appears.5. Click OK.

Note: You need to manually restart your computer to complete the Metasys Server installation or upgradeprocess.

Resolving Point Names with the Same Attribute1. Select a point in the left grid of the Convert Attribute names to IDs in the Historian Database dialog box.


Figure 21: Resolving Point Names with the Same Attribute

2. Click Resolve All (X) Point Trend(s) with the Attribute Name: (X) with Attribute ID:.

Note: If additional points require resolution, repeat Step 1 and Step 2 until all points are resolved.3. Click Update Database and Exit to write your changes back to the database. The Successful Update dialog

box appears.4. Click OK.

Note: You need to manually restart your computer to complete the Metasys Server installation or upgradeprocess.

Verifying the Database Update1. Launch the Attribute Name to ID Conversion tool using Windows File Explorer. Browse to

C:\Program Files (x86)\Johnson Controls\MetasysIII\Tools.2. Double-click the Convert Attribute Names to IDs for Trend executable. The No Updates Required dialog box

appears.

Figure 22: No Updates Required Dialog

Note: If the Continue with a wizard dialog box appears, points still require resolution. Go toManually Launchingthe Attribute Name to ID Conversion Tool to repeat the conversion process.


3. Click OK.

Exiting without Updating the DatabaseNotes:• You can exit the Attribute Name to ID Conversion tool through either the Attribute Name to ID Conversion Wizard

or Convert Attribute Names to IDs in the Historian Database dialog box. The process discussed in this sectionapplies to either window.

• All changes made automatically by the tool or manually are lost if you exit the database without updating.

1. Click Cancel and Exit (lose changes). The Continue With Exit dialog box appears.

Figure 23: Continue With Exit Dialog Box

2. Click Yes.

Detailed Procedures: Data Precision Enhancement Tool

Data Precision Enhancement Tool Requirements and RestrictionsNotes:• You do not always need to run the Data Precision Enhancement tool. This tool should only be executed if the

value precision is not satisfying current customer requirements.• If you need to execute the tool, we recommend that you start the conversion process immediately after the

Metasys Server installation or upgrade is complete.

To run the Data Precision Enhancement tool, you need the following:

• A computer installed with Metasys Server Release 8.0 or later software.• A computer installed with an edition of Microsoft SQL Server or SQL Server Express that is supported forMetasys

Release 8.0 or later.• A maximum database size of no more than 5 GB if you use SQL Server Express.

Note: The JCIHistorian database size doubles when you run the Data Precision Enhancement tool. The databasesize cannot pass the 10 GB limit during this process. Use theMetasysDatabaseManager tool to determinethe size of the JCIHistorian database.

• An adequate amount of free disk space to prevent problems with a full SQL Transaction log.


Important: Create a backup of the JCIHistorian database or manually ensure that there is enough disk spaceavailable before you begin the database conversion process. The conversion process could damagethe database if there is not enough free disk space.

Running the Data Precision Enhancement Tool1. Browse to C:\Program Files (x86)\Johnson Controls\MetasysIII\Tools using Windows Explorer.

Figure 24: Enhance Analog Precision Link Location

2. Double-click the Enhance Analog Precision link to launch the Data Precision Enhancement dialog box.

Figure 25: The Data Precision Enhancement Dialog Box


3. Ensure that the Free disk space section of the Data Precision Enhancement dialog box is green. The greenbackground means that there is sufficient disk space available to convert the database.

Figure 26: Free Disk Space

4. Click Convert to float to begin the data conversion from real to float. The fields update automatically when theconversion is complete.

Figure 27: The Data Precision Enhancement Dialog Box after Conversion

Notes:• The database conversion can take up to 4 hours to complete. See the Conversion time estimate and Progress

sections of the Data Precision Enhancement dialog box (Figure 25) for the anticipated length and status ofthe conversion process.

• You cannot exit the tool once the conversion process is underway.5. Match the field of the Data Precision Enhancement dialog box on your computer to the fields listed in Data

Precision Enhancement Dialog Box after Conversion.

6. Click Exit.


Troubleshooting: Attribute Name to ID Conversion ToolSolutionError or Error MessageThere is a problem with the contents of the JCIHistoriandatabase that prevented the tool from upgrading the databaseautomatically.

The problem is caused by one of three issues:• Trend samples stored with different attribute names for the

same attribute of a field point cannot be merged.• An attribute name cannot be translated.• There is more than one attribute possible for the same

attribute.

Follow the steps in theManually Launching the Attribute Nameto ID Conversion Tool section to resolve any or all of theseissues.

You receive a JCIHistorian Database Exception windowafter you complete the Metasys Server installation orupgrade.Figure 28: JCIHistorian Database Exception Error Window

An error was reported from the operating system. There aremany possible errors that can occur.

Review the following information provided by the two methodsto determine the error:1. Locate the MPI.LOG file in the

C:\Users\tasw\AppData\Local\Temp folder.2. Click the View log for more details link on the Database

conversion fail screen. The Editor dialog box appears withdetails regarding the error.

Figure 29: Editor Dialog Box

TheMetasys Server installation or upgrade ended with thefollowing error code:

<error number>

<error text>

The ADS sent new trend samples for points that are beingconverted. Exit the tool and manually launch it again.

If the issue persists, copy the MPI.* files from theC:\Users\tasw\AppData\Local\Temp folder and contact yourlocal Johnson Controls® field support representative for moreinformation.

You receive a Duplicate Key window after launching thetool manually.


Troubleshooting: Data Precision Enhancement ToolSolutionError or Error MessageThe following scenarios could cause the Convert to float button to disable:

The tool was started with a database that is already converted: If the databaseis already converted, you do not need to run the tool. Click Exit to exit the tool.

There is not enough free disk space available: The conversion process coulddamage the database if there is not enough free disk space. Click Exit to exit thetool. Using Windows Explorer, manually ensure there is enough disk spaceavailable. Once you determine there is enough disk space to proceed with thedatabase conversion, start the process in Running the Data PrecisionEnhancement Tool again.

An error has been detected: Click Show log to show error details and resolvethe error. Once you have resolved the error, you may continue with the databaseconversion.

The Convert to float button is disabled.

There is not enough free disk space to convert the database. The Status fieldlists the estimated value for the assumed required disk space. Click Exit to exitthe tool. Using Windows Explorer, manually ensure there is enough disk spaceavailable. Once you determine there is enough disk space to proceed with thedatabase conversion, start the process in Running the Data PrecisionEnhancement Tool again.

The Status field is red and displays thefollowing message:

Not enough free disk space...

The database you are converting is too large. You must change the databasefrom SQL Express to SQL Server and detach the database from SQL Expressand attach it to the SQL Server.

The Status field is red and displays thefollowing message:

SQL Express database too big forconversion. Maximum supported sizefor mdf: < 5 GB


SolutionError or Error MessageThe tool requires permission to read the free disk space information.

To resolve this problem:

1. Click Change credentials. The Change Credential window appears.Figure 31: Change Credential Window

2. Select the Use Windows credentials for authentication check box if youwant to use Windows® credentials to read the free disk space information.

Do not select the Use Windows credentials for authentication check boxif you want to use the SQL Server authentication with user id and password.

3. Enter an applicable user name and password based on Step 3 in the ChangeCredential window.

4. Click Read free disk space. The database conversion continues if there isenough free disk space to continue.Note: We strongly recommend that you not click Convert to float on the

MPI - Warning/Hint dialog box. Performing the database conversionwithout the necessary free disk space could damage the database.

You receive a MPI - Warning/Hint dialogbox after you attempt to convert thedatabase.Figure 30: MPI - Warning/Hint Dialog Box

The database is already converted. You do not need to run the tool. Click Exit toexit the tool.

The Status field is green and displays thefollowing message:

Data Type float already exists indatabase analog tables

Related DocumentationTable 8 contains literature related to the database tools.

Table 8: Database Tools Related DocumentationSee DocumentFor Information OnMetasys® Server Installation and Upgrade Instructions Wizard(LIT-12012162)

Metasys® Server Lite Installation and Upgrade InstructionsWizard (LIT-12012258)

Installing or Upgrading the ADS or ADX

SCT Installation and Upgrade Instructions (LIT-12012067)Installing or Upgrading SCT

ODS Installation and Upgrade Instructions Wizard(LIT-12011945)

Installing or Upgrading the ODS

Open Data Server Help (LIT-12011942)How to Use the Metasys ODS Software

Metasys® Database Manager Help (LIT-12011202)Interacting with and Monitoring the Databases on the ADS,ADX, or ODS

Metasys® SMP Help (LIT-1201793)Working with Trends, Alarms (Events), Audits, andAnnotations


Table 8: Database Tools Related DocumentationSee DocumentFor Information OnMetasys® SCT Help (LIT-12011964)Creating, Editing, and Loading Archive Databases with the

SCT

Language Installation Program Installation Instructions(LIT-12011793)

Installing the Johnson Controls® Language InstallationProgram (LIP) Tool

Language Installation Program Help (LIT-12011349)How to use the LIP Tool

Network and IT Guidance Technical Bulletin (LIT-12011279)Network and IT Considerations

Building Technologies & Solutions507 E. Michigan Street, Milwaukee, WI 53202

Metasys® and Johnson Controls® are registered trademarks of Johnson Controls.All other marks herein are the marks of their respective owners.© 2017 Johnson Controls

www.johnsoncontrols.comPublished in U.S.A.


Database Tools Commissioning Guide - Johnson Controls

Documents

Transcript of Database Tools Commissioning Guide - Johnson Controls