alert 3.60 installation & upgrade guide · 2019. 6. 11. · alert™ 3.60 installation &...

ALERT Installation & Upgrade Guide

Version 3.60

ExpertALERT™ StandardALERT™

ViewALERT™

Information in this document is subject to change without notice and does not represent a commitment on the part of Azima DLI. No part of this manual may be reproduced or transmitted in any form, or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser's personal use, without the express written permission of Azima DLI.

Copyright 2012 by Azima DLI All Rights Reserved

Printed in the United States of America

All product names mentioned in this document are trademarked or copyrighted by their manufacturers.

No part of this document may be reproduced or transmitted in any form without the prior written permission of Azima DLI.

Copyright ©2012 by Azima DLI – All Rights Reserved. Contact Azima DLI at [email protected] for further information. This manual explains how to install and upgrade to ALERT 3.60 for commercial software installations on a desktop PC / server.

Product Number: 80004780 Version: 3.60 Date: November 2012

ExpertALERT, StandardALERT, ViewALERT, ALERT, DCX, DCA-60, TRIO, Technology You Can’t Ignore, Sprite, SpriteMAX, Sprite Roamer, WATCHMAN, WATCHMAN Analysis, WATCHMAN Remote, WATCHMAN Onsite, WATCHMAN Reliability Portal, WATCHMAN Intensive Care, Reliability as a Service, Raas, and Knowing What’s Ahead are trademarks of Azima DLI.

mailto:[email protected]

ALERT™ 3.60 Installation & Upgrade Guide iii

Contents WELCOME! ...................................................................................................... 1 Getting Help ............................................................................................................................. 2

ABOUT THE ALERT SYSTEM ......................................................................... 3 Minimum System Requirements .............................................................................................. 3

Standalone vs. Client-Server ................................................................................................... 3

Using Multiple Databases ........................................................................................................ 4

Replication ....................................................................................................................... 4

Data Collector Compatibility .................................................................................................... 5

Version 3.50 Data Collectors ............................................................................................ 5

Version 3.40 Data Collectors ............................................................................................ 5

INSTALLING THE ALERT 3.60 SYSTEM ........................................................ 6 Installing Sybase SQL Adaptive Server Anywhere 12 ............................................................. 7

Installing ALERT 3.60 .............................................................................................................. 8

Logging in to ALERT 3.60 ...................................................................................................... 14

User Documentation....................................................................................................... 15

Registering Your Software ..................................................................................................... 16

Requesting Software Keys from Azima DLI ................................................................... 16

UPGRADING FROM ALERT 3.50 .................................................................. 17 Replicating Post Upgrade from ALERT 3.50 ......................................................................... 18

UPGRADING FROM ALERT 3.40 .................................................................. 19 Updating Non-Replicating 3.40 Databases ............................................................................ 20

Using the Database Update Wizard ............................................................................... 20

Updating Replicating 3.40 Databases .................................................................................... 23

Updating a Master Database with the Replication Wizard .............................................. 24

USING A SERVED DATABASE ..................................................................... 27

REGISTERING A DATABASE WITH ODBC .................................................. 34 Troubleshooting the ODBC Administrator .............................................................................. 39

iv Azima DLI

ALERT™ 3.60 Installation & Upgrade Guide 1

Welcome! Thank you for purchasing ALERT™ 3.60 software!

This document contains installation instructions for both new customers and for those who are upgrading from ALERT 3.40 or ALERT 3.50.

How you install or upgrade your ALERT 3.60 software is the same for ExpertALERT™, StandardALERT™, and ViewALERT™. This document refers to all three generically as the ALERT software.

Much of the information in this guide is relevant to all users. We recommend you read the entire guide before starting the installation or upgrade process.

Depending on your situation, certain sections will be most relevant to you:

NEW Customers See “Installing the ALERT 3.60 System” on page 6.

Commercial Software UPRADES

If you are upgrading from ALERT 3.50, see page 17.

If you are upgrading from ALERT 3.40, see page 19.

If you are upgrading from a version of ALERT that is earlier than Version 3.40, contact Azima DLI Technical Support.

2 Azima DLI

Getting Help If you run into any issues that you cannot solve with the information found in this document, you can reach Azima DLI Technical Support in any of the following ways:

• E-mail [email protected]. Be sure to include a detailed description of the issue, including what lead up to the trouble and any error messages you encountered.

• Launch a Chat Session with an Azima DLI support expert. Visit www.AzimaDLI.com. From the Training + Resources menu, choose Customer Support and then click the live chat icon.

• Call the Azima DLI Technical Support Hotline. Dial 800-654-2844 for live Technical Support between 8am and 7pm Eastern Time, Monday through Friday. Users outside the continental United States must call 206-842-7656. If you need help outside of these hours, leave a detailed message and a support member will return your call at the first opportunity.

Azima DLI 300 Trade Center

Suite 4610 Woburn, Massachusetts 01801

781-938-0707


http://www.azimadli.com/


About the ALERT System The ALERT system is made up of three components:

• Sybase SQL Adaptive Server Anywhere 12. This is the database engine required by ALERT 3.60. It can be installed on your local computer or on a network. If you are installing your database on a network and “serving” it to other users, Sybase 12 must be on the database server with the database and on EVERY client running ALERT 3.60.

• ALERT 3.60. This software must be installed on every computer from which a user will access ALERT.

• Database. At least one database must be installed and registered with the Open Database Connectivity Administrator (ODBC) before you can launch and use the ALERT 3.60 software. This database can be installed on your local computer or “served” over a network.

All of the collected and processed data is housed in a database and provided to the software via the database engine (Sybase 12). For example, when an analyst wants to view a spectrum, the software sends a query (a request for specific information) to the database engine. The database engine searches the database for the information and then passes it back to the ALERT software to display to the analyst.

Minimum System Requirements The following are the minimum system requirements for the ALERT system:

• PC with a Pentium* II, 500 MHz microprocessor (Pentium* 4, 2.0 GHz or better microprocessor is recommended).

• Hard disk with 500 megabytes of free space, 1+ GB is recommended.

• 512 MB of random access memory (RAM), 1024 MB or more is recommended.

• Microsoft® Windows® XP (SP3), Windows Vista, or Windows 7 operating system.

If you are running Windows 95, 98, ME, NT, or 2000 do not proceed with the installation or upgrade and contact Azima DLI.

Standalone vs. Client-Server Before you begin installing or upgrading software, you must have a clear plan for where each component will be installed.

If you are the only person using the system, then all three components can be installed on your local computer.

However, if others will be accessing the ALERT data, we recommend you set up the system using a client-server configuration.

To do this, install both the database engine (Sybase 12) and the database on a network computer or server that is accessible by all users. Install the ALERT 3.60 software and Sybase 12 on each user’s desktop, laptop, or tablet PC.

4 Azima DLI

This type of client-server setup works well because the engine's searching of the database is more efficient and only the results of the query are passed back across the network to the ALERT software on your local machine.

Note: If you believe that you may need to use a different database engine (instead of Sybase SQL Adaptive Server Anywhere 12), or you think you may want additional licenses, contact Azima DLI (or your sales representative) and your internal computer/network support staff before you proceed with the installation.

If you use a client-server setup, you must “serve” the database from the database engine. This is done by configuring a service via Sybase Central, which is installed with Sybase 12. For more information about “serving” a database, see “Using a Served Database” on page 27.

Using Multiple Databases A single database can handle multiple plants and multiple, simultaneous users.

However, in some cases you may prefer to use more than one database.

For example, a power company with multiple power stations may install a different database at each station. Doing this makes accessing data at each location easier for those at that plant since the database is on a local server.

Doing this does not mean the data is ONLY accessible by local users. Users at other plants need only to register the database at the other plant(s) and have access to their local servers. Performance may be a little slower when accessing a remote plant, but data is easily accessible.

Replication There is another way to achieve this goal through a method called replication. Using this method, a single database containing ALL data from ALL plants is installed at each power station. The replication process synchronizes the databases so that changes made at different plants are reflected in all of the databases. If you are interested in setting up replication, refer to the ALERT 3.60 Replication Guide.


Data Collector Compatibility TRIO CX7, TRIO CA6, DCX, or DCA-60 data collectors that replicate to ExpertALERT or StandardALERT installed on a workstation, server, or laptop computer must be running a minimum of Version 3.50 to be compatible with the ALERT 3.60 software.

Once the computer hosting (or serving) the master database is upgraded to ALERT 3.60, replicating data collectors running Version 3.40 and earlier will NOT be able to replicate with the master ALERT 3.60 database.

• If you have a data collector running Version 3.50, see “Version 3.50 Data Collectors.”

• If you have a data collector running Version 3.40, see “Version 3.40 Data Collectors.”

• If you have a data collector that is earlier than Version 3.40, contact Azima DLI before you install or upgrade to ALERT 3.60 on your computer.

Version 3.50 Data Collectors Version 3.50 data collectors are fully compatible with commercial ALERT 3.60 software.

Once the workstation, server, or laptop hosting (or serving) the master database is upgraded from ALERT 3.50 to ALERT 3.60, replication will continue to work seamlessly with Version 3.50 TRIO, DCX, or DCA-60 units.

Before you upgrade your commercial software to Version 3.60, make sure the master database has all current changes from the data collectors. To do this, replicate all of your data collectors and then replicate the master database.

Once ALERT 3.60 is installed, open the master database and wait a few moments while a SQL script adjusts the database structure from Version 3.50 to Version 3.60. This occurs automatically, without user prompt, and only the first time you open the database. The next time you replicate, these changes are applied to the subscription databases on the data collectors.

The command (.bat) file used to run replication does NOT need to be updated or modified to replicate the databases. However, if Replication Wizard 3.50 is installed on the remote data collector, it must be upgraded to Version 3.60. If you need to do this, you must uninstall Replication Wizard 3.50 before you install the new version. For information about installing Replication Wizard 3.60, see the ALERT 3.60 Replication Guide.

Version 3.40 Data Collectors Version 3.40 data collectors are NOT compatible with commercial ALERT 3.60 software.

If you are installing or upgrading to ALERT 3.60 on your workstation, server, or laptop, you must upgrade your replicating TRIO, DCX, or DCA-60 units to Version 3.50.

Keep in mind that once you upgrade the commercial software hosting the master database from ALERT 3.40 to ALERT 3.60, you must use the Replication Wizard to update the master database to Version 3.60, extract new V3.60 subscription files, and create new command (.bat) files for your replicating data collectors

These subscriptions must be installed on your data collectors after the units have been upgraded to Version 3.50. See the ALERT 3.50 Installation & Upgrade Guide for help upgrading your data collector to Version 3.50.

For help generating new replication subscriptions and command files, refer to the ALERT 3.60 Replication Guide.

6 Azima DLI

Installing the ALERT 3.60 System Use the following checklist as a guide when installing ALERT 3.60 for the first time. Each task is explained in detail in this document.

This checklist applies to new installations of ExpertALERT 3.60, StandardALERT 3.60, and ViewALERT 3.60 on a workstation PC, server, or laptop.

If you are upgrading, see either “Upgrading from ALERT 3.50” on page 17 or “Upgrading from ALERT 3.40” on page 19, depending on the version from which you are upgrading. If you have ALERT software that is earlier than Version 3.40, contact Azima DLI Technical Support.

TASK 1: Ensure Minimum System Requirements are Met The minimum system requirements for ALERT 3.60 are listed on page 3.

TASK 2: Install Sybase SQL Adaptive Server Anywhere 12 How to install Sybase 12 is explained on page 7.

TASK 3: Install ALERT 3.60 How to install the ALERT 3.60 software is explained on page 8.

TASK 4: Log In How to log in for the first time is explained on page 14.

TASK 5: “Unlock” Your Software How to request the unlock keys needed to register your software is explained on page 16. If you do not unlock the software, it will only operate for 30 days.


Installing Sybase SQL Adaptive Server Anywhere 12 SQL Adaptive Server Anywhere 12 must be installed with new installations of ALERT 3.60 and with upgrades from ALERT 3.40. If you are upgrading from ALERT 3.50, you do not need to install Sybase 12 – it is already installed.

Azima DLI provides installation files for Sybase 12 on the ALERT 3.60 installation CD. If you are upgrading, you will have either received a CD or have been directed to a download page to access the needed files.

Important! Do NOT remove older versions of Sybase before installing Sybase 12. This is especially important if you are upgrading from ALERT 3.40. Existing databases cannot be updated to work with ALERT 3.60 if the older instance of Sybase is removed. Also, if you are using any DCA-50 data collectors, they require Sybase 7 to function properly.

Sybase 12 must be installed on every computer from which you plan to run ALERT. If you are setting up the ALERT system in a client-server configuration, Sybase 12 must also be installed on the network computer or server from which the database will be “served.”

The provided Sybase 12 installation places only the features required for ALERT software products and for replication between ALERT databases. The installation creates shortcuts to Interactive SQL, Sybase Central, the ODBC Data Source Administrator, and to the Network Server and Personal Server applications.

To install Sybase SQL Adaptive Server Anywhere 12 1. Ensure you are logged in as an Administrator on the

computer on which you plan to install Sybase 12.

2. Access the installation files. If you have a CD, browse to the Sybase 12.0.1 B8 folder. If you are referred to a download page, locate the download.

3. Right-click Sybase12.0.1.B8.Install.vbs and select Run as Administrator to start the installation. If you are prompted for permission to launch the file, click Yes. (If your operating system is Microsoft® Windows XP, you can just double-click the file to start the installation.)

4. Wait while Sybase 12 is installed. This may take several minutes.

5. When the Installation Complete message appears, click OK.

IMPORTANT!

Be sure to launch the CORRECT Sybase 12 installation file.

The file name is:

Sybase12.0.1.B8.Install.vbs

DO NOT install the file that ends in .msi.

8 Azima DLI

Installing ALERT 3.60 These instructions are the same for Version 3.60 of ExpertALERT, StandardALERT, and ViewALERT. In the steps below, the images presented are from ExpertALERT.

Use these instructions for new installs and for upgrades on a workstation PC, server, or laptop computer.

To install ALERT 3.60 1. Be sure the computer on which you plan to install ALERT 3.60 meets the minimum system

requirements detailed here.

2. Log in as an Administrator on the computer on which you plan to install ALERT 3.60.

3. Launch the executable file for the installation. If your operating system is Microsoft® Visa or Microsoft® Windows 7, you may need to right-click the executable and select Run as Administrator. Where the executable is located depends on whether this is a new install or an upgrade.

− New customers: Insert the ALERT installation CD and locate the executable file (.exe) for the ALERT software (for example, ExpertALERT.3.60.0.72.B1.Install.exe). The name of the file may vary slightly depending on the ALERT product you are installing.

− Upgrades: If you have been sent a CD, do the same as a new customer (above). If you were directed to a download page, access it and locate the executable file (.exe) for the ALERT software installation.

Tip! If you are prompted to allow the program to run, allow it.

4. On the Welcome dialog box, click Next.


5. On the License Agreement dialog box, review the license agreement and decide whether you accept the terms.

− If you do, select I accept the terms of the license agreement, then click Next.

− If you do not, select I do not accept the terms of the license agreement. If you do not accept the terms, the Next button is disabled and the installation cannot proceed. Click Cancel to exit the installation.

Note: If you want a copy of the License Agreement for your files, click the Print button. The license agreement will automatically be sent to your default printer.

10 Azima DLI

6. On the Setup Type dialog box, decide whether you want to install the software and the demo database provided with it or just the software, then click Next.

− Select Program Files and Database if you want to install the demo database (EADB.db). This is the default option. We strongly recommend you install the demo database and use it to practice using the ALERT software and as a base to build your own custom database. This database is automatically registered with the ODBC Data Source Administrator on your computer and is ready for use once the installation is complete. You can have more than one database, so installing it does not mean you cannot create or install another database at a later time.

− Select Program Files Only if you only want to install the ALERT software. If you choose this option, you will not be able to open the ALERT software until a database is registered with the ODBC Data Source Administrator on your computer. (If you are upgrading from ALERT 3.50, your existing databases are already registered and will work with ALERT 3.60. If you are upgrading from ALERT 3.40, you will need to update your existing databases and register them with ODBC.)


7. On the Choose Destination Location dialog box, specify where you want the software installed, then click Next. You can accept the default destination (C:\Program Files\Azima DLI\ALERT 3.60) or you can click Browse and navigate to a different location.

8. If you opted to install the demo database in Step 5, the Choose Database Location dialog

box opens. Specify where you want the demo database (EADB.db) installed, then click Next. You can accept the default location (C:\EA360DATA) or click Browse to navigate to a different folder.

Note: If you are not installing the demo database, the Choose Database Location dialog box does not open. Continue with Step 9.

12 Azima DLI

9. On the Ready to Install the Program dialog box, click Install if you are happy with the settings you have specified thus far. If you want to change any of your earlier selections, click the Back button to make changes.

10. Wait while the ALERT software and demo database (if selected) are installed.


11. On the InstallShield Wizard Complete dialog box, click Finish. The ALERT software is now installed.

What you do next depends on whether you installed the demo database (EADB.db) with the ALERT 3.60 software and, if you are upgrading, whether you have existing databases you want to use.

• If you installed the demo database and plan to use it (new installs and upgrades), you can launch the software and practice using ALERT or start building a custom database using the demo database as a base. When installed, the demo database is automatically registered with the ODBC Data Source Administrator on your computer. This means that it has been given a data source name (EA360DB), which appears on the login dialog box when you launch ALERT 3.60. Continue with “Logging in to ALERT 3.60” on page 14.

• If you are upgrading from ALERT 3.50, you can launch the ALERT 3.60 software and open any database you previously used with ALERT 3.50. This is because your existing ALERT 3.50 databases are already registered with the ODBC Data Source Administrator and are configured for use with Sybase 12. When the database opens, a SQL script window opens for a few moments as the database is adjusted for use with the ALERT 3.60 software. This will only happen the first time you open each of your ALERT 3.50 databases with ALERT 3.60. If you installed the demo database during the upgrade, it can also be opened since it was registered automatically with the ODBC Data Source Administrator during the upgrade process. Continue with “Logging in to ALERT 3.60” on page 14.

• If you did NOT install the demo database and this is a new installation or if you are upgrading from ALERT 3.40, you will not be able to launch the ALERT 3.60 software because no ALERT databases are registered with the ODBC Data Source Administrator for use with Sybase 12. The ALERT 3.60 login dialog box will not list any databases. Before you can launch the software, you must register a database with the ODBC Data Source Administrator on your computer so its DSN will be recognized by the software and Sybase 12. If you did not install the demo database because you are upgrading and want to use your existing ALERT 3.40 databases, you must update each database for use with ALERT 3.60. How to update non-replicating databases is explained on page 20. How to update a replicating network is explained on page 23. If you need help registering a database with the ODBC Data Source Administrator, see page 34.

14 Azima DLI

Logging in to ALERT 3.60 Once you have installed Sybase 12 and ALERT 3.60 and at least one database is registered with the ODBC Data Source Administrator on your computer, you can log into the ALERT 3.60 software.

Before you log in, make sure you know the data source name (DSN) of the database you plan to use. If you installed the demo database with the ALERT software, this database is automatically registered with ODBC and is ready for use. The DSN for the demo database for ExpertALERT, StandardALERT, and ViewALERT is EA360DB.

Note: If you are upgrading from ALERT 3.40 and want to use an existing database, you must first update it for use with ALERT 3.60 and Sybase 12. How to do this is explained on page 20 for non-replicating databases and on page 23 for replicating databases. (If you are upgrading from ALERT 3.50, this is not necessary; continue with the steps below to launch the software.)

To launch the ALERT 3.60 software How you log in is the same for commercial software installations of ExpertALERT, StandardALERT, and ViewALERT.

1. Launch the software using either of the following methods:

− From the Start menu, choose All Programs>Azima DLI>ALERT3.60>ExpertALERT 3.60. Depending on your operating system, this path may vary slightly. If you have StandardALERT or ViewALERT, its name will be used in place of ExpertALERT.

− Double-click the ALERT 3.60 icon on your desktop. The icon will bear the name of your ALERT product (ExpertALERT, StandardALERT, ViewALERT).

2. On the log in screen, do the following and then click OK.

− In the User name box, enter the user name provided by your Administrator or Azima DLI.

− In the Password box, enter the password provided by your Administrator or Azima DLI.

− From the Data source drop-down list, select the name of your database. Only ALERT databases that have been registered with the ODBC Data Source Administrator on this computer are listed. If you installed the demo database, it was automatically registered and its DSN appears in the list (EA360DB).

Tip! If you are the only person to use your computer, and/or you are not concerned if other people access your ALERT system, consider selecting the Save password check box. Selecting this check box eliminates the need to enter your credentials every time you launch the software.

If this is the first time you are logging in to the software, you are prompted to register it (as explained on page 16).


User Documentation Once logged in to ALERT, refer to its online help for detailed user instructions. To access the online help, chose Help>Contents.

In addition to the online help, there are other pieces of end-user documentation available once ALERT is installed.

• A PDF user manual can be accessed by choosing Start>All Programs>Azima DLI>ALERT3.60>ALERT Users Guide. This manual contains the same information as the online help.

• A Vibration Analysis Guide in online format provides a tutorial on the basics of machine vibration analysis. It is not specific to the ALERT software, but provides novice users solid machine vibration information. This tutorial may be accessed by choosing Start>All Programs>Azima DLI>ALERT3.60>Vibration Analysis Guide.

16 Azima DLI

Registering Your Software The first time you run ALERT after an initial installation or upgrade, you are prompted to register the software. All commercial software installations of ExpertALERT, StandardALERT, and ViewALERT on a computer initially operate as a 30-day trial and must be registered to “unlock” the full, licensed version.

To register, you must contact Azima DLI Technical Support. You can click Register later and use the software temporarily, but it will cease to operate if you do not register it within the trial period.

Requesting Software Keys from Azima DLI You must contact Azima DLI to get the two registration keys that will unlock the software. If you are upgrading from an older version, your warranty must be current in order to request new software keys.

1. Ensure you have the serial number of your software. It will either be on your installation CD packaging or, if you downloaded the software, in the email sent to you by Azima DLI with the download link.

2. Launch your ALERT software.

3. Choose Help>Register now to open the Software Registration dialog box.

4. Provide the Code Entry Number and Computer ID (located on the License details tab) to Azima DLI Technical Support via email ([email protected]) or over the telephone (during regular business hours) at 800-654-2844.

5. A support tech will provide you with two keys. Enter your serial number and these keys on the License details tab:

a. In the Software Serial Number box, enter the serial number provided with your installation.

b. In the Key 1 and Key 2 boxes, enter the keys provided by Azima DLI

6. Click the Register button.



Upgrading from ALERT 3.50 Upgrading from ALERT 3.50 is a simple, straightforward process.

You do NOT need to install Sybase 12 since it is already installed with ALERT 3.50.

Unlike upgrades from earlier versions of ALERT, your existing ALERT 3.50 databases do not need to be updated with the Database Update Wizard before use with ALERT 3.60. This is because they are already registered with the ODBC Data Source Administrator and Sybase 12. When you first open an ALERT 3.50 database with ALERT 3.60, a SQL script runs automatically and makes the database structure changes needed for ALERT 3.60—you do not need to do anything manually.

If your ALERT software replicates to a remote site (such as an Azima DLI data collector), you do NOT need to update the master database, generate new subscriptions, or create new command (.bat) files after upgrading to Version 3.60. However, if your remote computer or data collector has Replication Wizard 3.50 installed on it, you must uninstall it and install Replication Wizard 3.60. See “Data Collector Compatibility” on page 5 for more information about replicating to a data collector.

Use the following checklist if you are upgrading from a commercial software installation of ExpertALERT 3.50, StandardALERT 3.50, or ViewALERT 3.50 that is installed on a workstation PC, server, or laptop.

If you are upgrading from Version 3.40, see “Upgrading from ALERT 3.40” on page 19. If ALERT is set up in a client-server configuration, see page 27.

TASK 1: Ensure Your Warranty is Current Upgrading to a new version of the ALERT software requires a new “unlock” code be obtained from Azima DLI. Without the code, the software will only run for 30 days. Only those with current warranties can obtain a new unlock code. If you are unsure about your warranty status or you want to get back into warranty, contact Azima DLI.

TASK 2: Backup Existing Databases Backup your existing ALERT 3.50 databases before upgrading. Once the new software is installed and you open your existing databases, they are automatically adjusted to work with ALERT 3.60. Having a backup of your 3.50 databases is recommended.

TASK 3: Uninstall ALERT 3.50 Uninstall ALERT 3.50 prior to upgrading to ALERT 3.60.


TASK 7: Log In How to log in to ALERT 3.60 is explained on page 14. If you select the data source of an existing 3.50 database when you log in, a SQL script launches and automatically adjusts it for use with ALERT 3.60. This script only deploys the first time you open each of your ALERT 3.50 databases with ALERT 3.60.


18 Azima DLI

Replicating Post Upgrade from ALERT 3.50 If you were successfully replicating to remote sites with ALERT 3.50, the replication process should continue to operate as expected once you upgrade the computer hosting (or serving) the master database to ALERT 3.60.

Note the following:

• You do NOT need to use the Replication Wizard to update the master database, generate new subscriptions, or create new command (.bat) files.

• Once the computer hosting (or serving) the master database is upgraded to ALERT 3.60, open the ALERT 3.50 master database with ALERT 3.60. A SQL script launches automatically, without user prompt, and adjusts the database to the 3.60 structure. These structure changes will propagate to the subscription database the next time the master database replicates.

• If any of your remote sites have Replication Wizard 3.50 installed, it must be uninstalled and replaced with Replication Wizard 3.60.

• If you plan to use Replication Wizard 3.60 (for example, to extract a new subscription for a new data collector), you must make sure the master database has been opened with ALERT 3.60 at least once before using the Wizard. The master database must be adjusted for the ALERT 3.60 database structure prior to running Replication Wizard 3.60.


Upgrading from ALERT 3.40 Upgrading from ALERT 3.40 requires many of the same steps as a new installation. However, you must perform the additional step of updating your existing databases for use with the new version.

Important! If you are running a version of ALERT that is prior to V3.40, you must contact Azima DLI Technical Support. These instructions do NOT apply to upgrades from versions earlier than 3.40.

Use the following checklist if you are upgrading ExpertALERT 3.40, StandardALERT 3.40, or ViewALERT 3.40 software that is installed on a workstation PC, server, or laptop

If you are upgrading from Version 3.50, see “Upgrading from ALERT 3.50” on page 17. If ALERT is set up in a client-server configuration, see page 27.

TASK 1: Ensure Your Warranty is Current Upgrading to a new version of the ALERT software requires a new “unlock” code be obtained from Azima DLI. Without the code, the software will only run for 30 days. Only those with current warranties can obtain a new unlock code. If you are unsure about your warranty status or you want to get back into warranty, contact Azima DLI.

TASK 2: Backup Existing Databases During the upgrade process, you will update your Version 3.40 databases to work with ALERT 3.60. Once this is done, they will not open with earlier versions of ALERT. We strongly suggest you backup your existing databases before starting the upgrade.

TASK 3: Uninstall ALERT 3.40 Uninstall ALERT 3.40 prior to upgrading to ALERT 3.60.

TASK 4: Install Sybase SQL Adaptive Server Anywhere 12 ALERT 3.40 uses an earlier version of Sybase. You should NOT remove the earlier version of Sybase before installing Sybase 12. If you are using ALERT in a client-server configuration, you must also configure a service using Sybase 12. Databases that were “served” using ALERT 3.40 and Sybase 7 do not have their configurations automatically updated in Sybase 12. How to install Sybase 12 is explained on page 7. How to configure a service to serve a 3.60 database is explained on page 27.


TASK 6: Update Existing ALERT Databases to Version 3.60 All ALERT 3.40 databases must be updated to the ALERT 3.60 format and converted to Sybase 12 prior to use with the new software. How to update non-replicating databases is explained on page 20; instructions for updating replicating databases begin on page 23.

TASK 7: Log In How to log in to ALERT 3.60 is explained on page 14.


20 Azima DLI

Updating Non-Replicating 3.40 Databases Any existing, non-replicating ALERT 3.40 database that you plan to use with ALERT 3.60 must be updated to the ALERT 3.60 format and converted to Sybase 12.

This is done with the Database Update Wizard, a utility installed with ALERT 3.60

Note the following:

• If you are upgrading from ALERT 3.50, your existing database do not need to be updated.

• If you are using an ALERT database that is earlier than 3.40, contact Azima DLI Technical Support.

Important! If you use replicating databases, the update process is different. Do not perform the steps in this section and instead refer to “Updating Replicating 3.40 Databases” on page 23.

Using the Database Update Wizard Perform the following steps for each non-replicating ALERT 3.40 database you plan to use with ALERT 3.60.

Note: Once the following process is complete, the database will be ready for use with ALERT 3.60. You do not have to register the updated database with the ODBC Data Source Administrator on the computer—this is done for you automatically during the update process.

1. Ensure the database you plan to update is backed up. Once a database is updated for use with ALERT 3.60, it will no longer work with ALERT 3.40.

2. Create a working directory on the hard drive of your computer. This directory will be used during the update process and should have at least 3x the free space as the .db and its associated .log file combined for the database you plan to update. (You can delete this folder once your databases are updated.)

3. Launch the Database Update Wizard. How you access it may vary slightly depending on your operating system.

For Windows XP:

Choose Start>All Programs>Azima DLI>ALERT3.60>Database Update Wizard.

4. When the Database Update Wizard opens, click Next.


5. From the Data source drop-down list, select the data source name (DSN) of the database you want to update, then click Next.

Tip! If your firewall notifies you about blocking the Adaptive Server Anywhere Database Engine, unblock it.

6. Specify the working folder you created in Step 2, then click Next. You can type the path to the folder or click Browse to navigate to it.

22 Azima DLI

7. On the Completing the Update Wizard dialog box, verify the path to the database to be updated and then click Next.

8. Wait while the database is updated. This could take some time to complete, depending on

the size of the database. Several windows will open and track the status of the update.


9. On the Success dialog box, click Finish. The database is updated and ready to use with ALERT 3.60.

Note: The database’s DSN is updated for Sybase 12. It will no longer work with older versions of Sybase.

Updating Replicating 3.40 Databases If you use replicating databases and are upgrading from ALERT 3.40, you must update the master database to work with ALERT 3.60 and Sybase 12 and then generate new subscriptions and command (.bat) files for all of your remote sites using the ALERT 3.60 Replication Wizard.

Important! Before upgrading from ALERT 3.40, make sure all sites replicate to the master so that recent changes and newly collected data are not lost. During the update process you must cease all data collection activity on the replicating network. If you have an online system, stop it.

The update process is different depending on whether the master database is located on the same computer as ALERT or whether it is served over a network (that is, the master database resides on a separate database server).

• If the master database is on the same computer as ALERT, continue with the next section, “Updating a Master Database with the Replication Wizard.”

• If the master database is on a separate database server, you must “un-serve” the database before you update it. Once the database on the database server is updated using the Replication Wizard (as described below), you must serve it again, but this time using Sybase 12. See “Using a Served Database” on page 27 for more information about serving a database.

Tip! We recommend you have the ALERT 3.60 Replication Guide on hand. It explains how to install the ALERT 3.60 Replication Wizard, shows you how to extract a subscription database from a master database, and details the steps needed to run the replication batch file.

24 Azima DLI

Updating a Master Database with the Replication Wizard These instructions are for a replicating network in which the master database is NOT served via a separate database server. This means that the master database and ALERT 3.60 reside on the same computer.

1. Make sure the master database has all current changes from the remote sites:

a. Replicate all remote sites.

b. Replicate the master database.

2. If not done already, install ALERT 3.60 on the computer on which the master database resides. How to install ALERT is explained on page 8.

3. Install the ALERT 3.60 Replication Wizard on the computer on which the master database resides and on all remote sites (DCX/DCA-60 units). The installation files for the Replication Wizard are included on the ALERT 3.60 installation CD and are accessible on the Azima DLI download page (for those who are upgrading). How to install the Replication Wizard is explained in the ALERT 3.60 Replication Guide, which is provided with its installation files.

4. Update the master database to ALERT 3.60 using the Replication Wizard.

a. On the computer on which the master database resides, double-click the Replication Wizard 3.60 icon on the desktop or choose Start>All Programs>Azima DLI>Replication Wizard 3.60> Replication Wizard 3.60. (This path may be slightly different depending on your operating system.)

b. When the Wizard opens, click Next.


c. From the Data source drop-down list, select the DSN of the master database you want to update, then click Next.

d. Specify the path to the folder you want to use as a “working” folder and then click Next.

You can type the path or click the Browse button to navigate to it. If you specify a folder that does not exist, the installation can create it for you (after you are prompted to approve its creation).

Tip! This folder should be located on the drive with the most available free space. The available disk space should be at least 3x the size of the database. This is important if you have an unusually large database.

26 Azima DLI

e. Select the All remote sites have replicated check box to confirm that all remote sites are up-to-date, and then click Next. (You should have replicated the master and all remote sites in Step 1.)

f. Wait while the database is updated to ALERT 3.60 and Sybase 12. This may take

several minutes, depending on the size of the database.

g. On the Success dialog box, click Finish. The replicating database has been updated for use with ALERT 3.60 and Sybase 12. It will no longer work with ALERT 3.40 and Sybase 7.

5. The existing subscriptions at your remote sites will no longer work now that the master has been updated to ALERT 3.60. To work with ALERT 3.60, existing subscriptions must be re-extracted from the master via the Replication Wizard and copied to the remote sites. Refer to the ALERT 3.60 Replication Guide for instructions on how to create a subscription and transfer it to a remote site.

Important! Before you generate the subscriptions, make sure all of the logins needed for all of your remote sites are established in the master database.


Using a Served Database If you plan to allow a database to be “served” to more than one user, you must set up the ALERT 3.60 system using a client-server configuration.

To do this, install both Sybase 12 and the database on a network computer or server that is accessible by all users. Install the ALERT 3.60 software and Sybase 12 on each user’s desktop, laptop, or tablet PC. You must then “serve” the database from the network computer by configuring a service via Sybase Central.

Important! If you plan to “serve” an ALERT database concurrently to multiple users, you must purchase a license from Azima DLI for each connection. Once your server is set up, Azima DLI Technical Support can issue the Sybase keys needed for each seat.

Note: If you believe that you may need to use a different database engine (instead of SQL Anywhere), or you think you may want additional licenses, contact Azima DLI (or your sales representative) and your internal computer/network support staff.

28 Azima DLI

To “serve” a database from a network computer The following steps are performed on the network computer after Sybase 12 and the database you plan to serve are installed on it.

Note: If you are upgrading from Version 3.50 and were successfully serving your database(s) with that version, you do not have to perform the following steps for Version 3.60. Your existing databases should continue to work as before.

1. On the network computer, start Sybase Central. How to do this varies slightly depending on your operating system. For Windows 7: Choose Start>All Programs>SQL Anywhere 12>Administration Tools>Sybase Central.

2. In the right pane, double-click SQL Anywhere 12.

3. Select the Services tab, then right-click in the right pane and select New>Service from the

shortcut menu to open the Create Service Wizard.


4. On the Welcome dialog box, enter a name for the service. In the image below, we have named the service ALERT360, but you can enter any name you want. The name you enter here will be used by the ODBC Data Source Administrator on each PC that will access the database on the server. It will be used as the Server name when you register with ODBC. (To see where you enter this, see Step 5E of “Registering a Database with ODBC” on page 37.)

5. On the Select a Type dialog box, select Network Database Server, then click Next.

30 Azima DLI

6. On the Specify an Executable dialog box, enter the path to the Sybase 12 database server executable, then click Next. The Wizard should find the executable and populate the path automatically (for example, C:\Program Files\SQL Anywhere 12\Bin32\dbsrv12.exe), so you most likely do not need to enter anything.


7. On the Specify Parameters dialog box, enter the following, but replace ALERT360 with the name of your service (as entered in Step 4) and replace “D:\EA360DATA\EADB.db” with the path to the database on your network computer. Click Next when you are done.

-p 4096 -x TCPIP -n ALERT360 “D:\EA360DATA\EADB.db”

When registering this database with the ODBC Data Source Administrator (as explained on page 34), you would enter EADB (without the .db extension) in the Database name box and ALERT360 in the Server name box.

Note: If you have more than one database with the same filename, use an –n switch to assign a unique name to each so they can be individually registered with the ODBC Data Source Administrator. For example, you may have created two databases from the EADB.db demo database—one for Plant A and one for Plant B—with each bearing the same EADB.db file name. In this case, use an –n switch to identify each one. In the example above, replace the last line with two lines to represent the two databases:

-p 4096 -x TCPIP -n ALERT360 “D:\EA360DATA\PlantA\EADB.db” –n PlantA “D:\EA360DATA\PlantB\EADB.db” –n PlantB

In this case, you would not enter EADB as the Database name when registering these databases with the ODBC Data Source Administrator. Instead, you would enter PlantA or PlantB depending on which database you are registering.

32 Azima DLI

8. On the Select an Account dialog box, select the Local system account option button and ensure the Allow service to interact with desktop check box is selected, then click Next.

9. On the Select a Startup Type dialog box, select the Automatic option button to have the

service start automatically, then click Next.


10. On the Start the Service dialog box, select the Start the service now check box, then click Finish. The service is created and starts running.

11. Register the database with the ODBC Administrator on every desktop computer, server,

laptop, or TRIO/DCX/DCA-60 tablet PC that will access it. How to do this is explained on page 34.

34 Azima DLI

Registering a Database with ODBC Any database you plan to use with ALERT 3.60 must be registered with the ODBC Data Source Administrator on the computer from which ALERT is run.

This must be done manually, EXCEPT in the following cases:

• If you install the demo database during the installation of ALERT 3.60, it is automatically registered with ODBC on your computer and has the DSN of EA360DB.

• If you are upgrading from ALERT 3.50, your databases do not need to be updated. They will automatically work with ALERT 3.60 using their current DSNs (which are already registered for use with Sybase 12).

• If you are upgrading from ALERT 3.40 and you update your existing database using the steps provided in this document, those databases are automatically registered with ODBC during the update.

If you are using any other database, it must be registered with the ODBC Data Source Administrator on each computer from which ALERT will be run.

Registering a database lets you specify its data source name (DSN). This name will appear in the drop-down list when you log into any of the ALERT products, including the data collectors, so we suggest you use something intuitive.

To register a database with the ODBC Data Source Administrator 1. Open the ODBC Data Source Administrator on the computer, laptop, or tablet PC. How you

access it may vary slightly depending on the operating system of the computer.

a. Choose Start>Control Panel. b. Double-click Administrative Tools.

c. Double-click Data Sources (ODBC) to open the ODBC Data Source Administrator.


2. Select the System DSN tab and click Add to set up a new data source.

Important! Make sure you do not select the User DSN tab. If you do, only the currently logged in user will be able to access the database.

3. On the Create New Data Source dialog box, select SQL Anywhere 12 and click Finish to

open the ODBC Configuration for SQL Anywhere dialog box. You may have to scroll down the list to locate SQL Anywhere 12.

36 Azima DLI

4. On the ODBC tab, enter a name for the data source in the Data source name box. Make the name intuitive, as it is what you will need to select to open this database in ALERT.


5. On the Login tab, do the following:

a. From the Authentication drop-down list, ensure Database is selected.

b. In the User ID and Password boxes, enter the login needed to access this database. You can use any valid login from the database.

c. From the Action drop-down list, select the following depending on where the database is installed and whether it is “served.”

− If the database is on this computer and is NOT being served to other users, select Start and connect to a database on this computer.

− If the database is served from a different computer on your network, select Connect to a running database on another computer. (Because it is served, the database is already started, so you only need to connect to it.)

− If the database is served to other users AND is installed on this computer, select Connect to a running database on this computer. (Because it is served, the database is already running so you only need to connect to it.)

d. In the Database file box, type the path to the database file or click Browse to navigate to it.

e. For “served” databases only: Enter the database name in the Database name box and the database service name in the Server name box. This information is specified when you configure a Sybase 12 service to “serve” the database. For more information, see “Using a Served Database” on page 27.

38 Azima DLI

6. Return to the ODBC tab and click the Test Connection button to find out if the database can be successfully accessed.

7. If the connection works, a success message appears. Click OK to dismiss it. If the

connection fails, review what you entered on the Login tab. For example, make sure the login you entered is valid and typed correctly. If you still cannot connect, see “Troubleshooting the ODBC Administrator” on page 39.

8. Click OK on the ODBC Configuration for SQL Anywhere dialog box.

9. Click OK on the ODBC Data Source Administrator dialog box.

The database now has a data source name and is registered with the ODBC Data Source Administrator on the computer. To verify this, launch ALERT and locate the data source name from the Data source drop-down list on the login dialog box.


Troubleshooting the ODBC Administrator We recommend you involve your IT Department before troubleshooting the ODBC Data Source Administrator.

Sometimes the problem is a simple one to fix. Review the following suggestions to see if any resolve the problem. If not, try the other solutions suggested below.

• Check the login. The login you enter must be a valid login for the database. Make sure you typed both the user name and password correctly in Step 5b above.

• Make sure the correct action is selected. In Step 5c above, make sure you selected the Start and connect to a database on this computer option if the database is on this computer; the Connect to a running database on another computer option if the database is “served” from another computer on your network; or the Connect to a running database on this computer option if the database is served to other users, but is installed on this computer. There are other options that are similar, so you may have inadvertently selected the wrong one.

Issue: I clicked the Test Connection button and I got the following error message:

Try this: Confirm that the main executable file is working properly.

Choose Start>Run and in the Open box, type DBENG12 and click OK.

If the following dialog box appears, the main executable is working and you should turn your attention to verifying access to the database. Make sure you have entered a valid login for the database.

If the above dialog box does not open, the main executable is NOT working properly. The problem lies with the path to this file.

Check the Environmental Variables to ensure the path to the executable is correct.

The following instructions are for Windows XP:

1. From the Start button, right-click My Computer and select Properties.

2. On the Advanced tab, click the Environmental Variables button.

3. Locate the PATH variable and ensure following is included in its value: C:\Program Files\Sybase\Shared\Sybase Central 4.0\java;C:\Program Files\SQL Anywhere 12\bin32

40 Azima DLI


Try this: Open the ODBC Data Source Administrator and edit the data source.

On the Login tab, make sure Database is selected from the Authentication drop-down list.

If it is, then verify that the correct option is selected from the Action drop-down list:

• If the database is on this computer and is NOT being served to other users, select Start and connect to a database on this computer.

• If the database is served from a different computer on your network, select Connect to a running database on another computer.

• If the database is served to other users AND is installed on this computer, select Connect to a running database on this computer.


Try this: Open the ODBC Data Source Administrator and make sure the path to the database is correct on the Login tab.

alert 3.60 installation & upgrade guide · 2019. 6. 11. · alert™ 3.60 installation &...

Documents