Installation under Windows

A WinCC OA installation installs the different components of WinCC OA such as database, UI runtime and others based on what installation components you have chosen. For installing WinCC OA under Windows the user must have administrator rights.

In order to use WinCC OA under Windows, minimum hardware and software requirements must be met (see chapter Hardware and software requirements for WinCC OA).

Installation instruction

1. Insert the WinCC OA DVD in your DVD drive. If autorun is active under Windows, the setup program will be started automatically. Continue with step 5.

2. On the task bar, right-click on Start and select the Explorer entry.

3. In the left panel, click on the letter for the DVD drive.

4. In the right panel of the Windows Explorer, double-click on the setup program icon to start the installation.

5. The installation progress has started (see below).

Caution

Administrative rights are necessary for the installation of WinCC OA!

For the installation of WinCC OA under Windows 7 & Windows 8 the setup must be started with administrative permissions (Right-click > "Run as administrator").

Windows 32-bit and 64-bit

If the WinCC OA installation is started by calling "setup.exe", then the installation program will install WinCC OA according to the current operating system (32-bit or 64-bit). It is, however, also possible to manually select the 32-bit / 64-bit setup by calling "setup32.exe" or "setup64.exe" respectively.

note

We recommend that you install the WinCC OA 64-bit on 64-bit Windows. However, a WinCC OA 32-bit installation is also feasible on 64-bit Windows .

note

On 32-bit Windows a 64-bit WinCC OA cannot be installed. When trying to do so an error message will be generated.

Installation language

If you start the WinCC OA installation through "setup.exe", the installation language depends on the regional options of the user (Start > Control panel) and not on the language of the operating system. If you start the installation through  "WinCC OA 3.10.msi", the installation language is English.

Note that if the installation has been executed in German, you have to uninstall WinCC OA to execute the installation in English.

Caution

If the error "Error 1324. The path Datenpunkttypen_f?_Symbolkatalog contains an invalid character." occurs during the installation of WinCC OA, the settings for programs that do not support Unicode must be changed. Under Control Panel > Regional and Language Options > Advanced the option "Select a language to match the language version of the non-Unicode programs you want to use" must be set to either German or English.

Installation progress

The WinCC OA setup process is taken place in an InstallShield Wizard. The setup program displays the version number during the installation. Before the components (features) of the WinCC OA Installation can be installed the following setup steps have to be passed through:

1. License Agreement - accept the terms in the license agreement (End User License Agreement) to continue with "Next".

2. Customer Information - enter your user name and the organization. Click on "Next" to continue.

3. Custom Setup - select the installation options meeting your requirements. For available features see below.

By default all features that are needed for a standard installation of WinCC OA are already selected. If you want to install additional features like ETool, addOns, etc., you can select them here. Once a standard installation exists, individual features can also be installed later. Note that for the most features an own license is required (see Licensing).

TIP

If you want to install several addOns at once, use the option "This feature, and all subfeatures, will be installed on local hard drive." from the feature context menu. The first option "This feature will be installed on local hard drive" can be used to install individual features.

The installation path of the selected feature is shown below the tree view of the features. A new installation path can be specified using the "Change" button. Most features have the same installation path. Therefore, if you change the path for the feature "Information Server", you also change the path for the features "Base (Development & Runtime)", "API" and others. Only the applications whose installation path is C:\WinCC_OA_Proj\  have an installation path that can be set individually. Optionally, change the installation path - note that the path must not contain blanks! If you specify an directory for the installation, where an WinCC OA installation already exists, only files that were not changed since the first installation will be overwritten. Files that were already modified will not be overwritten. Specify a new directory for a completely new installation of WinCC OA.

note

Please note that the path must not contain any spaces.

If you specify a directory in which a WinCC OA installation already exists, then only files that have not yet been changed since the first installation will be overwritten. Any file that has been changed will not be overwritten!

Please use different directory to completely re-install WinCC OA.

note

WinCC OA cannot be installed on a network drive.

Please click on "next" to continue.

4. Ready to Install the Program - click on "Install" to install WinCC OA with the selected components (feature).

If a WinCC OA version has already been installed, an update installation is executed. You can select between

• Modify - allows to install additional features or to uninstall already installed features. Already installed features are preselected. If you deselect such a preselected feature, this will be uninstalled.

• Repair - Repairs the installed program, for example, corrupt files, registry entries. This option is a MSI feature.

• Remove: Removes WinCC OA from your computer (see also Uninstall).

Note

It may happen that the MSI uninstall routine does not remove WinCC OA correctly from the system and, for example, former versions cannot be installed since a newer installation is already installed. In this case use Windows Installer CleanUp Utility to remove the old installation.

Features of the Custom Setup

Base Products

• Base (Development & Runtime) - base installation with Online Help and WinCC OA Service.

• Web Client - client for visualization and controlling of WinCC OA panels in all common web browsers on personal computers or selective mobile end devices (notebooks, netbooks).

• UI Runtime (client only) - minimal variant. Requires access to a WinCC OA server system.

Online Help

WinCC OA Online Help in English and German. Available as compiled chm file or as plain HTML. If a "Restart" dialog appears while installing the Online Help, confirm the dialog with "NO". After finishing the WinCC OA installation, you can restart the computer.

AddOns

• Advanced Maintenance Suite - tool for efficient planning, management, execution and control of maintenance work and breakdown remedy.

• Communication Center - provides alert information via SMS or e-mail.

• Ultralight Client - thin web client for remote controlling and maintaining.

• Disaster Recovery System - addOn for coupling / data synchronization of two hot-standby systems, obtaining a double redundant warm-standby system

• Standard Object Library - Base framework for branch specific WinCC OA object libraries. (the Online Helps on the object libraries are located in the corresponding /help directories)

• S7 AdvancedLib - sector-independent base library for automation WinCC OA + S7

• BACnet - BACnet building automation package (driver, object library and HMI)

• S7 BaseLib - WinCC OA basic objects and S7 library for combined WinCC OA/S7 projects.

• Video -  video management system for operating, visualization and control of complex facilities (e.g. traffic requirements).

• Report (Excel)- WinCC OA Reporting system for Microsoft Excel. Microsoft Excel program files are not included.

Applications

• Demo Application - sample application 'DemoApplication' introducing the possibilities of WinCC OA. Bilingual graphical user interface and database (English/German).
  
  A demo project is installed through the "Typical" installation. It is a sample project that is created with   the installation. The name of the demo project contains the version number, for example, the demo project of version 3.10 is called "Demo_3.10". Therefore, it is possible to execute the setup program by more than one version and by each version there will be one demo project.
  A demo project is only available under Windows.

• GettingStarted-Application - sample application 'GettingStarted' for building a WinCC OA project step by step. Bilingual graphical user interface and database (English/German).

Note

The DemoApplication and GettingStarted-Application are not uninstalled automatically when uninstalling a WinCC OA version and must be uninstalled using the WinCC OA Project Administration, if desired.

Special Functions

• API  - WinCC OA application programming interface (API). The environment variable API_ROOT is mapped to the directory in which the API has been installed. The installation directory is <wincc_oa_path>/api.

• Information Server - GUI based database connection to relational database systems via ADO.

• OleDB Provider Client only - installs all essential files for accessing historical WinCC OA data via OLE DB. Requires access to a WinCC OA server system.

• Old Version Support - old version database definition files and binaries. These are required to update old WinCC OA applications to the current version.

• Recipes - Recipe management system for configurable recipe types and unlimited number of recipes. Value acquisition from current process values, Excel (CSV) import / export.

Third Party Software

• GMS Instrumentation ActiveX Library - ActiveX Library

• Wibu-Key - license management software

NOTE

If the computer on which WIBU-KEY is installed is member of a domain but, however, is currently not in the network, the installation of WIBU-KEY can not be completed, as the domain server can not be found. In this case add the computer to a working group.

NOTE

The option ADO 2.6 is not available as an extra option anymore. The Microsoft Sub installation MDAC 2.7 (that is a superset of ADO) will be executed instead if it is required for the use of a feature and is not installed yet. You have to install the database drivers for the desired database (for example, MS Excel, MSAccess, Oracle Client) before you use the ADO functionality. The End User License Agreement is located in file ADO_EULA.txt.

You can launch WinCC OA immediately after installation. As a rule, it is not necessary to modify environment variables.

Note

Use the WinCC OA functions intended for backup in order to backup the WinCC OA data (online backup, backup of the alarm archives, backup of the HDB directories). For details, see the chapter System Management, Database and the corresponding sub chapters. Access to WinCC OA data by external programs (virus detection programs, backup programs) must be prevented in order to avoid access conflicts.

Caution

It is recommended to disable the user account control (UAC) when using Windows 7 / Server 2008! If the user account control is not deactivated, e.g. the project administration must be started as administrator (right click > "Run as administrator").

Chapter

Contents

Installation under Windows

Explains system requirements, Install components, custom WinCC OA installation and links to the topics.

Custom installation

Possibility of custom installation for WinCC OA versions < 3.6.

Licensing

How to obtain a valid license code, the entries of the shield file, keywords for the modules that need a license (also valid under Linux)

Uninstall

Describes the complete uninstallation of WinCC OA versions.

Unattended Setup

Running the installation in unattended mode.

System settings

Preventing and avoiding crashes under Windows.

WinCC OA as service

WinCC OA running under Windows with no user logged in.

Configuration of the service

Configuration in order to start WinCC OA as service.

Branding WinCC OA MSI Installation

Instructions how to customize the texts and the layout of the WinCC OA installation progress to own needs.