ECT Installation Wizard User Manual
ECT Installation Wizard User Manual
Table of Contents
Table of Contents................................................................................................................ 2
Glossary ......................................................................................................................... 3
General Information............................................................................................................ 4
Glossary
CT Control Terminal
OPC OLE for Process Control, a sever which contains ControlIT datapoints and
events.
General Information
Technical Support Address
Note: throughout this document the 3 terminologies namely, ECT Installation Wizard, Installation
Wizard or Wizard indicate the same terminology i.e. ECT Installation Wizard Tool.
Chapter 2 - Installation
2.1. Installation Wizard Setup
The Installation Wizard does not have any installation program and it can be directly
started from a CD or a disk drive. However, Installation Wizard requires the Microsoft
.NET framework 3.5. If this framework is not already installed on your PC, by starting the
Installation Wizard, one of the following error messages is output:
Or:
NOTE: by installing .NET framework you will get the following dialog from Microsoft
which runs very slowly and the progress bar indication is somewhat confusing but it
installs correctly!! Please have also some patience since the installation may take up to 10
minutes or longer.
IMPORTANT NOTE: After the installation the PC must be rebooted in order the WiBu
key driver to be effective, otherwise, by starting the Control Terminal, an error message
regarding that the key is missing may be output.
At the top statusbar, the version(1.0.0) of the Installation Wizard configuration file is
displayed. There is also a field at the top of the screen marked as “UNITROL >>”. This
field is only informative and shows the selection path. As you will see in the next chapter,
the Installation Wizard is built up in hierarchical form. On the main screen, the various
installations of the Control Terminal are also listed. At the bottom left, under the ABB logo,
the version of the Installation Wizard tool is shown.
When the Installation Wizard is started, it reads through the wizard configuration XML file
and builds up the installation wizard structure. If the configuration file includes any syntax
error, then the wizard will not start and an error message is output. Note, that the
configuration file is read only during the wizard start up. This means if you make any
changes to the configuration file during the wizard operation, this will not have any effect.
In order for your changes to be effective, you have to restart the wizard!
The user selects the version of the control terminal package which he wishes to install.
The wizard lists all the software components(such OPC server, WiBu key, ECT) which are
needed to be installed for the requested installation. If the wizard detects that another
version of the requested installation already exists, it outputs a conflicting sign and lists
the conflicting installations. The user can decide whether to continue with the installation
process by clicking on the “Install” button or manually remove the already existing
installations.
Note that for OPCServer and the WiBu key, it does not output conflicting sign since these
components have only one version. The wizard checks whether these components
already installed on the PC, in this case it will not install them again otherwise, installs
them. This is the reason why the installation process may take different length of time
depending upon which components already exists.
UNITROL
Installation Wizard
CTMS ECT
V1.3.32 V2.3.32
Single Single
Channel Channel
Local Local
• specify the location of the installers for the specified installation packages
• specify the CT application files
• specify any files to be delivered such as OPC server definition files
<Configuration>
<DocFiles> All the documents are listed here.
<FileSets> All files to be delivered(OPC file)
<Installers> All installers are listed here.
<ApplicationConfigurations> All ECT config files are listed here.
<Options> The tree structure of each installation
is defined here.
</Configuration>
In order to create this configuration file, it is important to consider that this file is virtually
divided into 2 parts, namely Global and iterative as shown below:
?Global:
DocFiles
FileSets
Installers
ApplicationConfigurations
?Iterative:
Options
In the global part, all the documents, files, installers and application configuration files are
declared together with their paths where they reside. In the iterative part, the hierarchy of
Example:
Assume we wish to create an installation wizard for installing 2 packages namely ECT
and CTMS. The ECT package has 2 further versions namely, Ver1.0 and Ver2.0. Each
version has a user manual. ECT has one config file for each version. There is also an
OPC server common for ECT and CTMS. The OPC server definition files must be also
delivered with this wizard.
Here is the high level design of the wizard configuration file. Note: the syntax used in the
following example is not precise(correct)!!!
<Configuration>
<DocFiles>
UserMan_ECT_Ver_1.0 path: Doc\ect user manual v1.0.pdf
UserMan_ECT_Ver_2.0 path: Doc\ ect user manual v2.0.pdf
UserMan_CTMS_Ver_1.0 path: Doc\ctms user manual v1.0.pdf
<SetFiles >
Opc_Files_V1.3.32 path source: OPC File\1.3.32 path target: “OPCServer”
“OPCServer” this path is defined in registry. To find out, start registry by clicking
on Stat/Run then enter RegEdit. Select the following path in the registry structure:
SOFTWARE/ABB/OPCServer/5.0.2/Installation/FilePaths/WorkingFolder
<Installers>
Ect_ver1.0_installer path: CT/ECT/ect installer verion 1.0.msi
Ect_ver2.0_installer path: CT/ECT/ect installer verion 2.0.msi
CTMS_installer path: CT/CTMS/ctms installer verion 1.0.msi
Opc_server_installer path: CT/OPCServer/setup.exe
<ApplicationConfigurations>
ECT_1.0_UN6800_1.2.21_config path: 1.2.21/npf-configuration.xml
ECT_2.0_UN6800_2.2.32_config. path: 2.2.32/npf-configuration.xml
<Options >
Root : UNITROL
<SupportingInstallers>
Opc_server_installer
<ChildOption>
ECT
<ChildOption>
V1.0
<SupportingInstallers>
Ect_ver1.0_installer
The software version of the ECT Installation Wizard can be viewed in the main screen
under the ABB logo.
Assuming that we wish to install the ABB CT Management Studio. To install this package,
follow these:
• Select the required version of this package and click on the Next button:
The following screen will appear:
The above screen has 3 tabs, namely, Description, Documentation Files and Installers.
The description tab includes a short text about the installation package. The
Documentation Files tab lists all the available documents for the current installation.
Each document can be opened by clicking on the symbol located on the very right
hand side of the document as illustrated below:
The Installers tab lists all the installers required for the current installation package. In
this case, the required installers are CT Management Studio V1.0.13 and the Firebird
Database Driver.
By clicking on the OK button, the main screen of the Installation Wizard appears where
the user can select the next installation package.
During the installation operation, if the wizard detects that one or more version of the
package to be installed already exists, the wizard outputs a conflicting tab marked in red
color. In this tab all the conflicting packages are listed. The user can then decide whether
to continue with the installation or uninstall them. To uninstall a package, it should be
selected first then the Uninstall… button be clicked.
Startup error
The ECT Installation Wizard requires .NET framework 3.5 and if this software is not
already installed then the following error message is output:
The above error message indicates that there is a syntax error in the wizard configuration
XML file. The line number of the error location is also shown.
Exception error
The following error message may be output, if the wizard configuration XML file includes
an invalid path.
Please select the installlation path, e.g. C:\Program Files\ABB\CT\CT Panel Edition\CT
Panel Edition for ECT
A wizard configuration does not keep everything that belongs to a given installation together
(e.g. installers, documentation, database files etc.), but declares all files that can be
copied/installed/displayed on the root level. This greatly simplifies keeping the overview
of the individual configurations that follow. Basically, this configuration file consists
of four root sections:
<FileSets>
<!--
Sets of arbitrary files to be copied to any location, paths relative to "Files" root folder.
The target location can be an absolute path (e.g. C:\abb-files) or relative to one of these folders:
- Desktop
- Installers (this is where the CT installer is being installed to).
- ApplicationConfigurations (CTs sub folder in the "My Data" special folder)
- OpcServerFiles (the path of the ABB OPC server - needs to be installed of course)
-->
<!-- a file set groups a number of files and copies them to a given location -->
<FileSet Id="FS:Set1" Name="Set1">
<TargetDirectoryRoot>ApplicationFolder</TargetDirectoryRoot>
<DeleteFolderContentsBeforeCopying>false</DeleteFolderContentsBeforeCopying>
<TargetDirectoryPath>SubFolder</TargetDirectoryPath>
<!--
A "FilePath" indicates the source location and can be one of two things:
- a file that is being copied to the target directory
- a folder whose *content* is being copied.
-->
<File FilePath="File0.txt" />
<File FilePath="File1.txt" />
<File FilePath="File2.txt" />
</FileSet>
<FileSet Id="FS:Set2" Name="Set2">
<!-- another file set -->
<File FilePath="File0.txt" />
<File FilePath="File1.txt" />
</FileSet>
</FileSets>
<Installers>
<Installer Id="INST:Installer A" Name="Installer A">
<!-- registry value to be checked in order to determine whether software is already installed -->
<RegistryCheck RegistryPath="HKEY/USERS/" FieldName="Version" FieldValue="1.0.1">
<InstallStrategy>IfUnavailable</InstallStrategy>
<!--
This is the hierarchy of target systems - basically, these are nested "Item"
elements that allow us to follow a hierarchical selection, e.g.
UNITROL 6080 >> UNITROL SW VERSION X >> ECT VERSION Y >> ECT CONFIGURATION Z
While following the hierarchy, all configured data is merged. This means that
a child item automatically derives the configuratino of its parent, e.g. by merging
files to be copied.
<ApplicationInstaller>
<!-- The installer(s) are referenced here -->
<ItemReference>INST:ECT Demo System</ItemReference>
</ApplicationInstaller>
<!-- UNINSTALL PATTERN search in registry for uninstall of products in case of conflict detection-->
<SuggestedUninstallPattern>wibu</SuggestedUninstallPattern>
<DocumentationFiles>
<!-- We already include CT manuals on the root level - the user always gets these... -->
<!-- The reference for DOC Files are inserted using "ItemReference"-->
<ItemReference>DOC:Manual C</ItemReference>
</DocumentationFiles>
</Option>
<Option Id="OPT:Child2" Name="Child2">
<Description>
This is the second child of the root item.
This is a longer text, which we need to wrap,
which means, continue on a new line so we can read everything...
</Description>
<!-- ChildOptions are used for building a hirachy / tree structure -->
<!-- NOTE: a child elemnt inherits all features of the parent. This means if you define an installer or DocFiles -->
<!-- by parent, you don't need to define it again by the child element. Only once is enough -->
<ChildOptions>
<Option Id="OPT:Child3" Name="Child3">
<ChildOptions />
<FileSets>
<!-- The reference for FileSets are inserted using "ItemReference"-->
<ItemReference>FS:Set2</ItemReference>
</FileSets>
</Option>
<Option Id="OPT:Child4" Name="Child4" />
<Option Id="OPT:Child5" Name="Child5" />
</ChildOptions>
<FileSets>
<ItemReference>FS:Set1</ItemReference>
</FileSets>
</Option>
</ChildOptions>
<DocumentationFiles>
<ItemReference>DOC:Manual A</ItemReference>
<ItemReference>DOC:Manual B</ItemReference>
</DocumentationFiles>
<SupportingInstallers>
<ItemReference>INST:Installer A</ItemReference>
</SupportingInstallers>
<FileSets>
<ItemReference>FS:Set1</ItemReference>
</FileSets>
</Option>
</Configuration>