Requirements

Basic requirements that are necessary for using the WinCC OA Product Packaging.

  • A valid OEM agreement with ETM professional control GmbH. (This is required for the replacing and adding of files within the msi packages. It is not required for the creation of a custom bootstraper with chosen msi packages.)
  • WiX Toolset Version v3.11.2.
    Note: The environment variable WIX must be set. It is set by the WiX Toolset Installer.
  • Windows PowerShell
  • .Net-Runtime 6.0 or newer must be available.

Optional Recommendations

Following tools are recommended for creating a custom product package as many of the included automations are based on their usage and not using them will require additional configuration steps as well as extended understanding on the covered configuration topics.

The following tools are only needed if you create the msi packages yourself and want to sign them:

  • A valid certificate in .pfx format for signing the product binaries. This certificate must have a password.
  • SignTool - Used to sign the product binaries with a valid certificate. This can either be acquired by downloading the Windows SDK or by using Visual Studio.
    Note: The path to the signtool executable must be added to the PATH environment variable.

install-buildprerequisites.

The PowerShell script PackageData/automation/install-buildprerequisites. within the WinCC_OA_3.19.0_branding_base.zip package can be used to automatically install all necessary tools.

Note: This does not include the installation of Windows SDK for signing.