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

  • as of WIN10
  • as of Windows Server 2012

Linux

  • CentOS as of V7
  • Oracle Linux as of V7
  • Debian as of v8 (Jessie)
  • others on request


Software requirements

The basic software for operation is:

Softwaremin. versionmax. version
Wildfly1318
DB: mariadb5.510.4
DB alternative: mysql5.58.0
Java (Oracle, openJDK, Zulu, corretto, etc.)JDK 8JDK 11 (on request)
Web browser (Chrome, Edge, Firefox)optional


Hardware requirements

We recommend complying with 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 for these - depending on whether they access PTC Creo or not:


ReleaseEngine Daemons (without Creo)

Operating systems

Windows

  • as of WIN10
  • as of Windows Server 2012

Linux

  • CentOS as of V7
  • Oracle Linux as of V7
  • Debian as of v8 (Jessie)
  • others on request


Hardware

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


Software

The basic software for 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 cannot be used by PTC for Creo.


Hardware

Hardware required by PTC for the respective Creo version.

The graphics card may deviate from PTC's recommendations, as 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 with licenseCreo3Creo9

When installing Creo, JLINK must also be installed. JLINK is required by the ReleaseEngine for communication with Creo.

Example with Creo 7:

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


Optional software (depending on version)

Softwaremin. versionmax. versionManufacturer license required
SAP GUIothers on requested

GraphicsMagick 1.3.291.3.36
Ghostscript9.109.53
TiffStamper

(tick)
MS Office20102016(tick)
Open Officeothers on requestedothers on requested


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 the ReleaseEngine is used in conjunction with SAP systems, the following requirements 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

  • a 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.