Technical Requirements: FNZ Studio 2025

The FNZ Studio Platform is a J2EE web application which can be run on an on-premise infrastructure, on a Cloud infrastructure, or in containers.

  • On the server side, the Platform requires the Java Development Kit (JDK) and a Java application server or servlet engine.
  • On the client side, only a web browser is required to access FNZ Studio Composition (development interface) or FNZ Studio Runtime (end-user interface).

Hosting Options

On-Premise Hosting

The Platform is easily hosted on on-premise infrastructure. It requires only a JDK and a compatible Application Server.

A number of options for hosting the Cluster Storage are available, such as the File system (NFS), Relational Databases, Apache Cassandra, and Cloud Native options.

See the Supported Software Versions section below for a detailed overview of supported JDKs, Application Servers, and Cluster Storage options for your version of the Platform.

Cloud Hosting

Thanks to its architecture, the Platform is not restricted to running on on-premise infrastructure, but can also be run on Cloud infrastructure. The following Cloud environments are supported:

  • Amazon Web Services (AWS)
  • MS Azure (ISV Partnership)
  • Oracle Cloud (ISV Partnership)

Starting from Appway 9, the Cluster Storage can also be located in the Cloud when running the Platform on AWS or MS Azure, using AWS S3 or MS Azure Block Blobs respectively.

See the Supported Software Versions section below for a detailed overview of supported JDKs, Application Servers, and Cluster Storage options for your version of the Platform.

Container Hosting

The Platform supports container technologies such as Docker. Since containers provide virtualization on the level of the server’s operating system, they are fully transparent to the Platform.

To operate the Platform in containers, configure each container to run an Application Server and then run the Platform on top of it, in exactly the same way as you would install an Application Server and the Platform directly on a server. When running a cluster, operate one container per cluster node.

See the System Installation Using Containers article for more information, and the Supported Software Versions section below for details on supported Application Servers for your version of the Platform.

Platform releases are consistently tested to ensure they are stable and fully functional when operated in containers – tests are performed using Docker containers.

Supported Software Versions

Our Platform is a Java-based application which requires additional software to run. This section outlines compatible software versions in the following categories:

  • Browser (FNZ Studio Composition)
  • Browser (FNZ Studio Runtime)
  • Java
  • Application Servers
  • Servlet Specification
  • Cluster Storage (Cloud Native / Other)

The supported product versions listed below have been tested and approved for the according Platform version. Minor point releases above the product versions listed are fully supported.

FNZ Studio 2025

The information reported here refers to the latest FNZ Studio 2025.x.x release (see Products card).

  • Browser (Studio Composition) Desktop:

    • Latest version of Safari (macOS only), Chrome, and Firefox
    • Latest version of Microsoft Edge

    Mobiles and tablets:

    • Not supported

  • Browser (Studio Runtime) Desktop:

    • Latest version of Safari (macOS only), Chrome, and Firefox
    • Latest version of Microsoft Edge

    Mobiles and tablets:

    • Latest version of Safari (on iOS) and Chrome (on Android)
Important! Microsoft has announced the official end of support for Internet Explorer 11 desktop application starting from June 15, 2022. IE11 is therefore no longer supported in Appway 2022.1 and higher. See more information.

  • Java

    • Oracle JDK 21 (latest patch version)
    • OpenJDK 21 (latest patch version) (1)

  • Application Servers

    • Apache Tomcat 9.0.82 or greater (recommended) (2)
    • IBM WebSphere Liberty 23.0.0.10 or greater (3)

  • Servlet Specification

    • 3.1

  • Cluster Storage

    • File system (e.g. NFS)
    • Apache Cassandra
    • Relational Databases (4)
    • Amazon S3
    • Microsoft Azure Blobs

  • Blob Storage

    • File system (e.g. NFS)
    • Relational Databases (4)
    • Amazon S3
    • Microsoft Azure Blobs

Notes:

  • (1) Supported OpenJDK 21 distributions: Eclipse Temurin 21, Amazon Corretto 21, Azul Zulu OpenJDK 21, and Red Hat OpenJDK 21. For more information, see OpenJDK Support .
  • (2) Apache Tomcat 10 is not supported.
  • (3) Web Profile 7 or 8 preferred. Web Profile 9 or greater and Jakarta EE 9 or greater are not supported.
  • (4) See the compatibility matrix available in the Supported Databases section for more information on the supported databases (check the row on the Relational DB Hazelcast Store extension).

Important Information on JBoss EAP

JBoss EAP is currently not supported.

JBoss EAP 7.4 does not support Java 21 and FNZ Studio 2025 is not compatible with JBoss EAP 8.0. As a result, there is currently no supported configuration for FNZ Studio 2025 on JBoss EAP. While we keep supporting JBoss EAP and IBM WebSphere Liberty with future versions of FNZ Studio, we strongly recommend new installations to host FNZ Studio on Apache Tomcat. Many add-ons like the OIDC Authenticator or Session Manager are available exclusively for Apache Tomcat. Apache Tomcat is the application server of choice for all of FNZ’s own cloud and on-prem installations. Important! We cannot provide a guarantee regarding issues occurring on customized or extended instances of the above mentioned application server versions (for example application servers using security-related wrappers, custom JAAS modules, or any other type of configuration deviating from the standard application server configuration).

Supported Databases

A number of Platform capabilities are based on database technology and require the use of a compatible database.

Supported Databases for FNZ Studio 2025

The database compatibility matrix available in this section covers the following FNZ Studio 2025 capabilities:

The information reported here refers to the latest FNZ Studio 2025 release (see Products card.
For information on DataStore, ProcessAuditTrail, and OfflineWorklistClient. capabilities, contact Support.

The Platform supports databases accessible either directly using a JDBC driver connection created in the Platform itself or through JNDI data sources configured on the application server.

The following table provides a compatibility matrix of the databases that can be used with FNZ Studio 2025.x.x capabilities mentioned above (see the full list of tested configurations below the table):

Extension/Database Release PostgreSQL 17.2 PostgreSQL 16.2 PostgreSQL 15.2 Oracle 23c Oracle 21c Oracle 19c MS SQL Server 2022 MS SQL Server 2022 MS SQL Server 2017
BusinessDataStorage Yes Yes Yes Yes Yes Yes Yes Yes Yes
BAM Yes Yes Yes Yes Yes Yes Yes Yes Yes
RelationalDbBlobStorage Yes Yes Yes Yes Yes Yes Yes Yes Yes
RelationalDbHazelcastStore Yes Yes Yes Yes Yes Yes Yes Yes Yes

 

Following is the complete list of tested configurations:

  • PostgreSQL 17.2
    • DB Version: 17.2
    • Driver version: PostgreSQL driver 42.7.4
  • PostgreSQL 16.2
    • DB Version: 16.2
    • Driver version: PostgreSQL driver 42.7.1
  • PostgreSQL 15.2
    • DB Version: 15.2
    • Driver version: PostgreSQL driver 42.5.4
  • Oracle 23c
    • DB Version: 23.3.0.23.9
    • Driver version: Oracle driver 23.5.0.24.07, OJDBC11 (1)
  • Oracle 21c
    • DB Version: 21.0.0.0
    • Driver version: Oracle driver 23.5.0.24.07, OJDBC11
  • Oracle 19c
    • DB Version: 19.3.0.0
    • Driver version: Oracle driver 23.5.0.24.07, OJDBC11
  • MS SQL Server 2022
    • DB Version: 16.0
    • Driver version: Microsoft JDBC Driver 12.6
  • MS SQL Server 2019
    • DB Version: 15.0
    • Driver version: Microsoft JDBC Driver 12.6
  • MS SQL Server 2017
    • DB Version: 14.0
    • Driver version: Microsoft JDBC Driver 12.6

Notes:

  • (1) In the Data Source configuration (Connection Properties field), set the property oracle.jdbc.sendBooleanAsNativeBoolean=false.

Supported JMS Providers

Currently supported JMS providers for all Platform versions (Appway 7 and higher) are:

  • Apache ActiveMQ 5.10.2 (through the IntegrationLinkComponents Extension)
See IntegrationLinkComponents Extension documentation.

Infrastructure Requirements

Infrastructure requirements vary greatly from one Platform installation to another, depending on the particularities of the Solution running on it. Among other factors, the number of "active Process Instances" and of "concurrent users" determines the amount of memory and type of infrastructure necessary:

  • Concurrent users represent the number of active users who are simultaneously accessing the server from within Studio Composition or Studio Runtime.
  • An active Process Instance occurs when a Process built in Studio Composition is started in Studio Runtime. As long as any task in a particular Process has not yet been completed by the Solution's end users, that Process Instance remains active.

Example Requirements for Common Installation Types

The table below outlines example requirements for several typical usage scenarios. These figures are based on performance tests for several types of Solutions, ranging from a small demo environment with 1 user to a large enterprise solution handling 2'000 users working simultaneously. Important! These figures are to be understood as examples only – complex Solutions can require a more powerful infrastructure for optimal performance.

  1. Development environment: 20 concurrent users / 200 active Process Instances
  2. Production (small) environment: 200 concurrent users / 4000 active Process Instances
  3. Production (large) environment: 2000 concurrent users / 200'000 active Process Instances Some of the example scenarios below require a cluster of servers with a load balancer.
  Development Production (small) Production (large)
Server nodes 1 (1) 2 (3) 6 (3)
Memory 4 GB 8 GB per node (16 GB in total) 8 GB per node (48 GB in total)
CPU 2 CPU with 4 cores each 2 CPUs with 4 cores each per node( 16 cores in total) 2 CPUs with 4 cores each per node (48 cores in total)
Disk space (non-shared) 4 GB 16 GB per node (32 GB in total) 16 GB per node (96 GB in total)
Shared disk space (2) - 40 GB 120 GB
Network speed between server nodes - 5 MB/s = 40 Mbit/s 20 MB/s = 160 Mbit/s

Notes:

  • (1) It is recommended to set up a development environment with multiple nodes (at least two) if you plan to run the final application on multiple nodes in the production environment. This is to ensure that the Solution under development is compatible with a multi-node setup.
  • (2) In an installation with several server nodes, shared disk space is the Cluster Storage directory, while non-shared disk space hosts the datahome directory. There are a number of options for implementing shared disk space, see the section below on Supported Software Environments for your Platform version for details on supported Cluster Storage options.
  • (3) For multi-node installations, a very stable and fast network connection between the cluster nodes is required:
    • (almost) no network interruptions
    • latencies of 5 milliseconds or less
    • at least 1Gbit/s

Due to these requirements, we strongly recommend that you locate all cluster nodes in the same data center, as geographically dispersed cluster setups usually do not fulfill the above criteria.

Estimating Minimum Infrastructure Requirements

The following rules of thumb are intended to help you estimate the memory and type of infrastructure necessary for a particular Platform installation.

Important! These formulas are to be understood as guidance only – complex Solutions may require a more powerful infrastructure for optimal performance.

In the case of installations with multiple server nodes, these rules of thumb refer to the total values for all nodes.

  • Number of CPU cores = # Concurrent Users / 75 + # Nodes + 20% For example: 2000 Concurrent Users / 75 + 6 Nodes + 20% = 39.2 Cores

  • Memory in MB = # Process Instances / 10 + # Business Objects + # Process Messages / 10 For example: 200'000 Process Instances / 10 + 5000 Business Objects + 100'000 Process Messages / 10 = 35'000 MB

  • Non-shared disk space in a multi-node installation = 16 GB

  • Shared disk space = Total Memory * 3 For example: 35'000 * 3 = 105'000 MB

  • Network speed between server nodes (in MB/s) = # Concurrent Users / # Nodes / 20 For example: 2000 concurrent users / 6 nodes / 20 = 17 MB/s = 136 Mbit/s

Disclaimer

Because third-party products frequently ship fixes, updates and new releases, we are not able to test every possible configuration. Likewise, certain configurations of third-party software may not be compatible with FNZ Studio. We recommend that you confirm support for all component versions of your configuration with any vendors who have provided those components.

If you experience a problem with the Platform and a product version listed in this document (or a point release above), please let our Support Team know.

All support for products or versions that differ from those listed in this document are best-effort only. If an unsupported third-party product is determined to be the cause of any problem, you will have to move to a supported product or contact the third-party product provider for help. We may provide limited support for some environments to help customers evaluate our products and develop applications, but we do not recommend or support their use in production environments.