Skip to main content
Skip table of contents

Important system requirements


ReleaseEngine Cockpit

The ReleaseEngine Cockpit runs on Wildfly.


System requirements

The following operating systems are supported here:

Windows

  • WIN10
  • Windows Server 2012
  • Windows Server 2016
  • Windows Server 2019

Linux

  • CentOS from V7
  • Oracle Linux from V7
  • Debian from v8 (Jessie)
  • others on demand


Software requirements

The basic software for operation is:

Softwaremin. Versionmax. Version
Wildfly1318
DB: mariadb5.510.4
DB alternativ: mysql5.58.0
Java (Oracle, openJDK, Zulu, corretto, etc.)JDK 8JDK 11 (on demand)
Web-Browser (Chrome, Edge, Firefox)optional


Hardware requirements

We recommend that you adhere to the following minimum hardware requirements:

Hardwaremin.recommended
CPU1>=2
RAM4GB>=8GB
HDD30GBDepending on use (Vault, etc.)
Network interface card11


ReleaseEngine Daemons

The actual RE processing is done with daemons. The following requirements apply to these - depending on whether they access PTC Creo or not:


ReleaseEngine Daemons (without Creo)

Operating systems

Windows

  • WIN10
  • Windows Server 2012
  • Windows Server 2016
  • Windows Server 2019

Linux

  • CentOS from V7
  • Oracle Linux from V7
  • Debian from v8 (Jessie)
  • others on demand


Hardware

Hardwaremin.recommended
CPU1>=2
RAM2GB>=4GB
HDD30GBDepending on use (Vault, etc.)
Network interface card11


Software

The basic software for the operation is:

Softwaremin. versionmax. version
Java (Oracle, openJDK, Zulu, corretto, etc.)JRE 11JRE 11


Release Engine Daemon (with Creo)

Operating systems

Windows

The operating systems required by PTC for the respective Creo version are supported:

See:

Linux

Linux is not usable for Creo on the part of PTC. 


Hardware

Hardware required as specified by PTC for the respective Creo version.

For the graphics card, it is possible to deviate from the recommendations on the part of PTC, since the requirements of the daemon with regard to shading/rendering etc. are lower.


Software

Basic software for operation.

Softwaremin. versionmax. version
Java (Oracle, openJDK, Zulu, corretto, etc.)JRE 11JRE 11
Creo Installation (requires PTC LicenseCreo3Creo9

JLINK has to be installed during the Creo installation. JLINK is used by the Release Engine for the communication with Creo.

Example with Creo 7:

The file pfcasync.jar has to be available in the directory <Creo Dir>\Common Files\text\java after the installation.


Optionale Software (depending on the requirements)

Softwaremin. Versionmax. VersionVendor license required
SAP GUIprovided on request

GraphicsMagick 1.3.291.3.36
Ghostscript9.109.53
TiffStamper

(tick)
MS Office20102016(tick)
Open Officeprovided on requestprovided on request


General hardware sizing

The sizing of the RE strongly depends on the scenario that is mapped with the RE. Influencing factors are, for example, the size of the files, the number of installed parts, the complexity of the components, etc.

For a detailed sizing, an exact knowledge of the respective scenario is important and thus requires preparatory project work.

INNOFACE is happy to support you in this preparatory project work and will be happy to assist you on request.


Daemons with access to SAP systems

If ReleaseEngine is used in interaction with SAP systems, the following prerequisites must be observed:

When using SAP ERP:

  • SAP BASIS >= 6.40 

When using SAP S/4 HANA (no premise or cloud):

  • Version >= SAP S/4 1610


License requirements

  • one CREO Parametric license for each instance of the ReleaseEngine (if the RE accesses CREO, e.g. to trigger a conversion).
  • one Windchill Base license per instance of the ReleaseEngine (if the RE accesses Windchill).


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.