Table Of Contents
Installing the AlarmTracker Client
Installation of the AlarmTracker Client software involves running the installation files and starting the Client.
The AlarmTracker Client uses DCOM to communicate with the LGMapper Server. The code handles the details of this communication for you.
AlarmTracker uses the SQL Server OLE DB provider to gain direct access to the LGMapper Alarms Database in order to perform queries and refresh AlarmTracker displays. The SQL Server OLE DB provider is part of the Microsoft Data Access Components (MDAC) re distributable component. The AlarmTracker installation verifies that MDAC 2.1 SP2 or higher is present on the system before proceeding. If MDAC 2.1 SP2 or higher is not present, an error message is generated and the installation halts (see MDAC Requirement).
As with the LGMapper, the AlarmTracker Client uses the SQL Server OLE DB provider to access the LGMapper SQL Server Alarms Database. This provider must be on the system in order for the installation to proceed.
When you start the installation script (see Installing the AlarmTracker Client), it verifies the SQL Server OLE DB provider is present. MDAC 2.1 SP2 must be present in order for the AlarmTracker Client installation to proceed. If it is not, an error message is shown and the installation aborts. If this occurs, refer to Installing the MDAC Components.
Installing the MDAC Components
The self-installing MDAC 2.1 component in the file mdac_typ.exe has been provided. This file is on the installation disk (or available along with the self-installing installation file).
Note MDAC 2.1 SP2 will not install, and is not necessary, on Windows 2000 systems.
To install MDAC 2.1
Step 1 Copy mdac_type.exe from the release media to a writable temporary directory.
Step 2 Execute mdac_type.exe from the temporary directory.
Note This must be done due to an installer limitation (MDAC can not be properly installed directly from the CD or from read-only media).
Once the installation is complete (reboot if directed to do so), proceed with the AlarmTracker Client installation (Installing the AlarmTracker Client).
Installing the AlarmTracker Client
Step 1 Run Setup.exe from the AlarmTracker Client directory of the Operations Support CD-ROM.
The AlarmTracker Client Installation Wizard starts (Figure 8-1).
Figure 8-1 Welcome to the InstallShield Wizard for AlarmTracker Version 2.0
Figure 8-2 InstallShield Wizard - Information Window
Figure 8-3 InstallShield Wizard - Choose Destination Location Window
Step 4 Select the destination location for the AlarmTracker Client files.
Accept the default location, navigate to another existing location, or create a new location. Throughout the remainder of this chapter, the selected location will be referred to as the installation folder.
Figure 8-4 InstallShield Wizard - Setup Status Window
When the installation is complete, the COM component registration is finished and the InstallShield Wizard Complete window (Figure 8-5) appears.
Figure 8-5 InstallShield Wizard Complete Window
Step 6 Click Finish to exit the InstallShield Wizard (Figure 8-5).
Note A system reboot may be required for the registration to take effect. Reboot the system if directed.
Starting the AlarmTracker Client
Once installation is complete, start the AlarmTracker Client.
Step 1 Select Start>Programs>AlarmTracker2 (Figure 8-6).
Figure 8-6 Start>Programs>AlarmTracker2
When the AlarmTracker Client starts, it shows the Connect to Servers dialog (Figure 8-7).
Figure 8-7 Connect to LGMapper Servers Dialog Box
This dialog allows you to specify one or two LGMapper Server locations to connect to.
Step 2 Enter the machine name of, or browse to, the desired LGMapper Server1 and/or LGMapper Server2 name(s). (Refer to Figure 8-8.)
Figure 8-8 Connecting to the LGMapper Server(s)
Step 3 Click Connect (Figure 8-8), the process of connecting to the LGMapper Server begins.
The process of connecting and initializing may take a few minutes. The dialog box expands vertically (Figure 8-9) as various progress messages appear during the initialization.
Figure 8-9 Connect to Servers Dialog Box Indicating Connection Progress
During the initialization phase:
•The code creates an instance of the SvrMgrObj on the LGMapper Server which manages the communication between the LGMapper Server and the AlarmTracker Client
•If this is the first AlarmTracker Client connecting to the LGMapper Server, the LGMapper Server:
–initializes its connection with the Listener process
–initializes its Configuration Database by taking an in-memory snapshot of its contents and building a local object hierarchy
–preprocess any Alarm objects remaining from the previous invocation of LGMapper
–reads the Listener Base Records
–builds Alarm objects
–updates the object hierarchy
•LGMapper Server takes a snapshot of the full object hierarchy and serializes it across the wire to the AlarmTracker Client
•AlarmTracker serializes the object hierarchy from LGMapper Server into its local object hierarchy
•AlarmTracker Client initializes its displays and begins processing
If the AlarmTracker Client is in a different domain than that of the LGMapper Server, and there is not a two-way trust relationship between these domains, the following error message may appear:
Failed to open DataSource LGMapper_geonv
Client unable to establish connection
[DBNMPNTW] ConnectionOpen (CreateFile()).
If this occurs, issue a net use command using the following syntax:
> net use \\lgmapperhost password /user:domain\username
•lgmapperhost is the name of the machine you are trying to connect to (the LGMapper Server machine)
•domain\username is the name of a valid account in the domain of the LGMapper Server machine
•password is the corresponding password for this account
Note To auto-connect to the LGMapper Server(s) upon starting the AlarmTracker Client, click Auto-Connect to Servers on Startup (Figure 8-10).
Figure 8-10 Automatically Connecting to the LGMapper Server(s) at AlarmTracker Client Startup