Semarchy xDI System requirements
Before installing Semarchy xDI, review the system requirements for each component you need to ensure that the software will run properly.
Common requirements
Java virtual machine
Semarchy xDI software requires a Java virtual machine (JVM), either as a runtime environment (JRE) or development kit (JDK). We recommend using a 64-bit JVM on a 64-bit operating system for best performance.
Semarchy xDI supports the following Oracle and OpenJDK Java versions:
-
Java 17 LTS
-
Java 21 LTS
Designer requirements
Hardware
xDI Designer can be run on computers with at least 8 GB RAM, and at least 600 MB free disk space. More space may be needed for extra components.
Operating system
Designer supports the following operating systems:
-
Windows 10 and 11, 64-bit.
-
Linux 64-bit, with an X server and GTK+ 3.20.0 or higher.
-
macOS 11 (Big Sur), 12 (Monterey), 13 (Ventura), 14 (Sonoma).
We provide separate Designer builds for Intel and Apple (M1 and newer) processors.
The Wayland display server is unsupported on Linux and may result in unexpected behavior. |
Database servers
Designer can connect to a wide range of database technologies. For more information, refer to the documentation for the relevant Designer components.
Runtime requirements
Hardware
xDI Runtime needs at least 80 MB of free disk space to install, and at least 1 GB of database storage. Memory, hard disk space and CPU requirements depend on your integration flows.
Operating system
The Runtime can be installed on any operating system with a supported Java Virtual Machine.
Certified database servers
The Runtime stores its logs and scheduler configuration in a database. The default is a built-in HSQL quick-start database, but you can use a certified relational database as well. At least 1 GB of database storage is required.
The built-in HSQL database is only accessible from the runtime by default, and is not recommended for production use. For more information, see Built-in HSQL database. |
The following database engines are certified for use with Runtime:
Oracle Database
Software versions |
|
Editions |
|
Supported platforms |
|
PostgreSQL
Software versions |
|
Supported platforms |
|
Third-party providers |
|
Microsoft SQL Server
Software versions |
|
Editions |
|
Supported platforms |
|
Microsoft Azure SQL Database
Software versions |
|
Analytics requirements
Hardware
xDI Analytics needs at least 500 MB of free disk space for itself and an application server, and at least 1 GB of database storage. Memory, hard disk space and CPU requirements depend on the application server, and on other installed xDI products.
Operating system
Analytics can be installed on any operating system with a supported Java Virtual Machine.
Supported application servers
The Analytics server runs as a Java application in a supported application server. It is certified to run on the following Apache Tomcat application servers:
-
Apache Tomcat 9.0.x
Analytics can also be installed as a JEE web application in the following application servers:
-
Eclipse Jetty 10.x
-
Wildfly 15.x to 26.x
Certified database servers
Analytics stores its data in a relational database. It requires at least 1 GB of database storage, although this number may increase depending on how many packages and how much version history you store.
The following database engines are certified for use with Analytics:
Oracle Database
Software versions |
|
Editions |
|
Supported platforms |
|
PostgreSQL
Software versions |
|
Supported platforms |
|
Third-party providers |
|
Microsoft SQL Server
Software versions |
|
Editions |
|
Supported platforms |
|
Microsoft Azure SQL Database
Software versions |
|
Web browsers
The Analytics web user interface supports the following web browsers:
-
Google Chrome 68 and newer (desktop and mobile)
-
Firefox 61 and newer
-
Microsoft Edge 42 and newer
-
Safari 11 and later (macOS and iOS)
Web browsers tend to be updated frequently. Semarchy xDI tries to stay compatible with reasonably recent versions. Please review the Analytics release notes for an updated list of known browser issues. |