Installing IGSS32



Conversion of IGSS32 v2 Configurations to v3 Format

Introduction

This document describes the conversion procedure necessary for running configurations created in v2 in the new IGSS32 v3 system.

We strongly recommend that you follow the procedural steps in the exact order listed below.

Please note that you will not be able to run your old v2 configuration successfully under v3, until you have converted the configuration itself and imported the v2 driver settings into the v3 Driver Setup program.

Conversion procedure

The following procedure is divided into six main steps corresponding to the various IGSS32 v3 programs and utilities you must use to successfully convert the v2 configuration.

To complete this procedure, it is assumed that both v2 and v3 are installed. However, you can do without a full v2 installation as long as the v2 driver settings in the Windows Registry are intact. In the “Convert driver settings from v2 to v3” procedure below, these settings are exported to a v3 compatible format.

STEP 1: Convert the v2 configuration

(c2to3.exe)

We recommended that you back up the v2 configuration before converting it to v3.

|Step |Action |

|1. |Open Windows Explorer and double-click the c2to3.exe program located in the \Gss subfolder of |

| |your v3 installation path. The program window appears. |

|2. |Select File ( Open and select the v2 configuration file (.elm) you want to convert. |

| |[pic] |

|3. |Click Open. The v2 configuration is now converted to the new v3 format. |

| |The program window shows you a detailed status of the conversion. Notice that the three core |

| |files of the v2 configuration are backed up: .elm, .dsc and |

| |.mdb. |

| |The status information displayed below is saved in the file, c2to3.log, located in the \Gss |

| |subfolder of your v3 installation path. |

| |Towards the end of the conversion process, you are asked whether you want to reuse the alarm |

| |and log files from v2. |

| |[pic] |

|4. |Click Yes to reuse your v2 alarm and log files. The Browse for Folder dialogue appears. |

| |[pic] |

|5. |Select the report folder where the v2 alarm and log files are located and click OK. |

| |A message appears telling you how to integrate the above files when you install the converted |

| |configuration. |

| |[pic] |

| |Refer to STEP 4, sub-step 3 later on in this document to view the Installation Options |

| |dialogue where these settings are located. |

|6. |Click OK. A message appears telling you that you need to convert your v2 driver settings to |

| |the v3 format. Refer to “STEP 3: Convert driver settings from v2 to v3 (Driver Setup)” below. |

| |[pic] |

|7. |Click OK and close the c2to3.exe program. |

STEP 2: Convert the v2 .BCL files

in a Command Prompt

In order to be able to use the .BCL files generated in v2 in subsequent versions of IGSS, these files must be subjected to a special conversion routine. This is done to assure that these files contain the structure compatible with the IGSS ODBC server software, which is the interface used to implement functionality in later versions of the IGSS software package like the Object Historian, the embedded graph feature and the ERW report module.

|Step |Action |

|1. |Locate the folder where the .BCL files for v2 are stored. |

|2. |Open a Command Prompt and find the utility bcl2to3.exe, which is normally found in the [IGSS |

| |install path]\gss subfolder. |

|3. |Run the utility from its location with a path to the location of the .BCL files. Here’s an |

| |example with an IGSS configuration called PlantAlpha and where the report subfolder is called |

| |PlantAlpha.r: |

| |[IGSS install path]\gss bcl2to3 C:\PlantAlpha\PlantAlpha.r |

| |The converted .BCL files will be placed in the PlantAlpha.r sub-folder. |

|4. |Inspect the resulting file names after running the utility. New .BCL files have been generated|

| |with the normal .BCL file name extension together with a copy of the original file with a |

| |renamed extension name called .BC2. |

| |Not all of the original v2 .BCL files may have been converted. This is due to the fact that |

| |only a limited number actually need to be converted, i.e. those that did not complete |

| |generating records due to a halt in the IGSS data collection engine during the period of |

| |operation of the v2 configuration. |

| |After conversion, all files within a given .BCL class will have the same size or vary only |

| |slightly (one byte). |

STEP 3: Make the converted configuration active

(Setup)

|Step |Action |

|1. |Open the IGSS32 Setup program. |

|2. |On the Folders tab, do the following: |

| |Under Configuration file, type the path to the converted configuration file, .elm or|

| |click Browse to find it. |

| |Under Report folder, type the path to the configuration’s report folder or click Browse to |

| |find it. |

| |Under Symbol file, type the path to the configuration’s symbol file or click Browse to find |

| |it. |

|3. |Click OK to close the program. |

STEP 4: Convert driver settings from v2 to v3

(Driver Setup)

In v2, driver settings were stored in the Windows Registry. Therefore, these settings must first be exported from the Registry to a v3 file format. Then they are imported into a v3 driver profile whose settings are now saved in the configuration’s database, .mdb.

|Step |Action |

|1. |Open the v2 Driver Setup program and verify that the v2 driver profile associated with the |

| |converted v2 configuration is set active. |

| |This step is necessary, because the v3 Driver Setup program exports the active driver profile |

| |from v2. |

| |If you need to copy the v2 driver profile to another PC, refer to the help file for v2 Driver |

| |Setup. Search for “managing driver profiles”. The procedure is described towards the end of |

| |the topic. |

|2. |Open the v3 Driver Setup program. |

| |At this point, there is no driver profile associated with the converted configuration. |

| |Therefore, this message appears. |

| |[pic] |

|3. |Click OK. The Save Profile As dialogue appears. |

| |[pic] |

|4. |Type the name of the new v3 driver profile. Typically, this will be the same name as you gave |

| |the configuration. Click OK. By default, the new driver profile is set active. |

| |The main window of Driver Setup appears. Make sure that the title bar shows the path and name |

| |of the converted v2 configuration and the name of the driver profile you’ve just created. In |

| |this example, Carlsberg is the name of the active driver profile. |

| |[pic] |

|5. |Select Tools ( Export IGSS32 V2 Driver Settings. The Save As dialogue appears. |

| |Driver Setup will now export the driver settings from the v2 driver profile you set active in |

| |step 1. |

| |Type a descriptive name for the export file and we recommend that you save it in the root |

| |folder for the v3 configuration and click Save. |

| |[pic] |

|6. |Select Tools ( Import IGSS32 Driver Settings. The Open dialogue appears. |

| |Choose the export file created in step 5 and click Open. |

| |[pic] |

|7. |The following message appears. If you are importing the v2 settings into an empty v3 driver |

| |profile, you can ignore this message. |

| |But if you’re importing into a v3 driver profile with existing station names and drivers, |

| |please read the message carefully. |

| |[pic] |

| |Click Yes to continue or click No to go back and make changes. |

|8. |The Driver Import dialogue appears. Type the exact station name as you assigned to this |

| |station in v2 Setup (Station name field on the Type tab). |

| |Station names are case sensitive. |

| |[pic] |

| |Click OK to continue. The driver settings are now imported into the v3 driver profile. |

|9. |Click on the station name defined in the previous step. Under Station type, make sure that the|

| |correct station type is selected. For an IGSS server, select Server or single user. |

| |[pic] |

|10. |Review the imported driver settings. If satisfactory, select File ( Save and exit the program.|

STEP 5: Install the converted configuration

(Definition)

|Step |Action |

|1. |Open the Definition program. The converted configuration will appear, because we chose it as |

| |the active configuration in Setup. |

|2. |Select File ( Install Configuration. If there are unsaved changes, the following message |

| |appears. Click Yes to save changes. |

| |[pic] |

|3. |The Installation Options dialogue appears. Change the settings as required and click OK. |

| |Under Keep, make sure that the Alarm files and Log files check boxes are selected, if you |

| |chose to reuse the v2 alarm and log files. |

| |[pic] |

|4. |If the installation is successful, a message similar to the one below appears. |

| |[pic] |

| |If the installation is not successful, review the error report and make the required changes |

| |to the configuration. Click the Help button in the Installation Options dialogue for further |

| |details. |

|5. |When the installation is complete, close the Definition program. |

STEP 6: Start the converted configuration

(IGSS32 Starter)

|Step |Action |

|1. |Open the IGSS32 Starter program. |

|2. |Click Start IGSS. |

|3. |Click Supervise to start the Supervise and Alarm programs. |

|4. |Review the converted configuration. |

The conversion process is now complete.

(0210 revision 1)

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download