Stages is a web application, so a recent web browser is required on the clients.

Note: The browser must have cookies and JavaScript enabled.

*1) Due to low rendering speed, Internet Explorer may react slowly when many elements are located on the same hierarchical level. Therefore the number of elements to be displayed is limited when using this browser. The default limit is 200 elements, which can be adjusted via the “list.limit.ie” config property. A progress bar is displayed after one second to raise user awareness. For process usability reasons, we recommend to place elements into folders to avoid this situation from happening and for maximizing process user experience.
*2) Due to poor SVG support, the Zoom and Scroll tool for process visualizations is not supported for IE 11 and older Edge versions (< 79.0).

Stages is a Java application and is executed on a Tomcat application server. The application server is automatically installed together with Stages.

The application server also acts as a web server. Thus, no additional web server (i.e. Apache or IIS) is required. If you do deploy Stages behind a web server (i.e. Apache or IIS), please ensure that:

• the https and wss (web socket) protocol URLs are forwarded for /stages and below.
• the https protocol URLs are forwarded for /reporting and below.
• the https protocol URLs are forwarded for /pkit and below, if you want the V6 Stages bookmarks to be redirected to their V7 counterparts.

Running Stages with a permanent license requires the Stages server machine to have a fixed IP address.

If the Stages user database should be synchronized with a Windows Active Directory Server via LDAP, a read-only user account on the ActiveDirectory server is required.

Stages is approved to run on virtualized environments, if sufficient resource isolation is assured (e.g. that intense CPU usage on another VM cannot degrade the Stages application VM performance).

• Oracle
• MySQL

Criteria

• max 25 parallel active users
• max 100 open user sessions
• max 5000 users synchronized via LDAP
• max 10 CM project sandboxes

Server Recommendations

• RAM: 8 GB minimum
• CPU: 4 Cores
• Storage: 6 GB (system, not including project sandboxes)

Database Recommendations

• Shared Oracle or MySQL server
• Connection 1 GBit
• Latency < 1 ms (Ping) required

Criteria

• max 100 parallel active users
• max 500 open user sessions
• max 15000 users synchronized via LDAP
• max 100 CM project sandboxes

Server Recommendations

• RAM: 12 GB minimum
• CPU: 8 Cores
• Storage: 12 GB (system, not including project sandboxes)

Database Recommendations

• Oracle or MySQL server
• CPU: 4 Cores
• Connection 10 GBit
• Latency < 1 ms (Ping) required

Criteria

• max 500 parallel active users
• max 2000 open user sessions
• max 50000 users synchronized via LDAP
• over 100 CM project sandboxes

Server Recommendations

• RAM: 16 GB minimum
• CPU: 16 Cores
• Storage: 24 GB (system, not including project sandboxes)

Database Recommendations

• Oracle server
• CPU: 8 Cores
• Connection 10 GBit
• Latency < 1 ms (Ping) required