Update or patch project

Requirements

• A project must be registered, otherwise it cannot be updated.
• Only executable projects can be updated. It is not necessary to update sub-projects (without an executable database).
• Before a project can be updated, the WinCC OA standard libraries in the project directory and in project-specific sub projects must be synchronized with the current libraries or removed temporarily.
• If the project contains custom CtrlExtensions that have not been compiled before the upgrade, they must be commented out in the config file before upgrading.
• The config entry paramLang = "language" must be commented out or deleted before updating.
  Note: Each project that is updated, must contain a "log" directory.

Upgrade Project

To update an existing project, proceed as follows:

1. Start the project administration of the new version.
2. Open the panel for displaying the projects with an older version.

   

3. Select the desired project from the project list - see the figure above.
4. Click the Upgrade project button - see the figure above. Confirm the license warning dialog.
   Note: The disk space is checked:

   

   If there is not enough space, the following message is displayed:

   

   or a message that the disk space will not be sufficient. A message that the disk space has not been checked is shown if an error occurs during the evaluation of the memory. Make sure that you free up additional disk space.
5. Check the displayed settings/information:

   

6. Click the OK button to apply the settings and to update the project - see figure above.

The project that should be updated is shown in the text field Project. The path of the current WinCC OA version is shown below the text field.

If the check box Save project before upgrading is enabled, the whole project is backed up before it is updated. The update is saved in the directory where the project is located with the name <ProjectName>.bak. If several backups are made, the .bak files are saved using ascending numbers (.bak, .bak1, .bak2).

The PMON port for the updated project can also be changed via the Pmon port field. If the port is not changed the standard PMON port (4999) is used.

If the check box CTRL syntax check before upgrading is enabled, the CTRL syntax is checked. The CTRL scripts and libraries of the project and the sub-projects are checked as well as the panels of the project. In a new version, variable names may no longer be allowed due to newly defined keywords (see Reserved keywords).

The syntax check is performed before upgrading the database. If one or more syntax errors are detected, a dialog will be opened asking whether to cancel or continue the project upgrade. The project can also be updated if the syntax of the project files is incorrect. The output of the syntax check is stored in the PVSS_II.log file of the project.

An older project can be converted to an SQLite project including an NGA database. For more information see chapter Automatic Migration of RAIMA → SQLite (+NGA).

Click OK to start the update - see figure above. When the update is started, the Log Viewer is opened automatically and the convertDb.log file is shown. This allows you to follow the update process. Error messages are shown in case of errors.

After the project is successfully updated, it will be displayed in the list of projects in the Project Administrator panel with the current version. When closing the panel with the list of projects of an older version, the project list is automatically updated.

Patch Update

Patch Update in a Single Server System:

1. Stop the project
2. Install the patch.
3. Start the project.
4. Check the functionality of the system.

Patch update in a redundant system:

1. Stop the project at the passive host (e.g.: host2).
2. Install the patch on this host.
3. Start the project on the passive host.
4. Wait until the start up of the project is finished.
5. Check if the recovery was successful and the redundant hosts are connected.
6. Perform a redundancy switchover.
7. Repeat steps 1-5 for the second host.
8. Check the functionality of the system.

WinCC OA Upgrade in a redundant system

The upgrade of the WinCC OA version in a redundant project is possible with the following steps. These steps are only necessary if a simultaneous stop of the projects on both redundant computers is not possible.

The following instructions take into account the use of UI machines or remote WinCC OA installations, e.g. for drivers or CTRL Managers. The upgrade order Server 1 → Server 2 or Server 2 → Server 1 can be chosen arbitrarily.

1. Stop the WinCC OA project on server1 --> the system on server2 is now active.
2. Change the port numbers of the Data Manager, Event Manager, Redu Manager and the Split Manager in the config file of the WinCC OA project on the Server 1
3. Execute an upgrade to the actual WinCC OA version on server1 (eventually incl. upgrade to the current Oracle schema version, if RDB is used).
4. Start the WinCC OA project on server1. Once the start up has been finished, both computers are active, but the system on server1 has no connection to the UI clients / remote machines.
5. For the UI clients/remote WinCC OA machines, run the upgrade to the latest WinCC OA version. The upgrade includes the installation of the new version and modification of the config/progs file (reference to the new version and, if necessary, adjusted executable and WinCC OA manager names).
6. Adjust the port numbers of the Data Manager and Event Manager of the UI clients / remote machines according to the configuration of server1.
7. Start the WinCC OA processes on the UI clients/remote WinCC OA-machines
8. Stop the WinCC OA project on server2.
9. Execute an upgrade to the actual WinCC OA version on server2.
10. Adjust the port numbers of the Data Manager, Event Manager, Redu Manager and Split Manager in the config file of the WinCC OA project according to the configuration of server1.
11. Start the WinCC OA project on server2 --> the server2 executes a recovery and the project start up.