System requirements
The following are the minimum requirements for a Striim server. Additional memory and disk space will be required depending on the size and number of events stored in memory and persisted to disk by your applications.
CPU cores
at least 8, or more depending on application requirements
Memory
at least 32 GB, or more depending on application requirements (see Changing the amount of memory available to a Striim server)
Free disk space
for evaluation and development: minimum 10 GB, 20 GB recommended
for production: 100 GB or more depending on application requirements
free disk space must never drop below 10% on any server
The following will increase disk space requirements:
BigQuery Writer when Streaming Upload is False
event tables persisted to Elasticsearch (see CREATE EVENTTABLE)
exception stores persisted to Elasticsearch (see CREATE EXCEPTIONSTORE)
Kafka streams (see Persisting a stream to Kafka)
the metadata repository if hosted on the internal Derby instance (see Configuring Striim's metadata repository)
MSSQL Reader when Transaction Buffer Type is Disk (see MS SQL Reader properties)
Oracle Reader when Transaction Buffer Type is Disk (see Oracle Reader properties)
server log files (see Changing log file retention settings)
WActionStores persisted to Elasticsearch (see CREATE WACTIONSTORE)
See also Configuring low disk space monitoring.
Certified operating systems
64-bit CentOS 7.9
64-bit Red Hat Enterprise Linux (RHEL) 7.6, 7.9, 8.7, 8.8, and 9.1
64-bit Ubuntu 18.04 LTS, 20.04 LTS, and 22.04 LTS
64-bit Windows Server 2019 and 2022
Mac OS X 13.1 (for evaluation and development purposes only)
64-bit Windows 11 (for evaluation and development purposes only)
If you need to run Striim on another operating system or a different version, please Contact Striim support.
Supported Java environments
All servers and Forwarding Agents in a Striim cluster must run the same version.
recommended: 64-bit Oracle SE Development Kit 8 (required to use HTTPReader or SNMPParser or Kerberos authentication for Oracle or PostgreSQL); for a license, contact Oracle License Management Service
also supported: 64-bit OpenJDK 8
Firewall / open ports
The following ports must be open inbound (and, as noted, outbound) for communication among servers and Forwarding Agents in the cluster.
on servers where you want remote access, port 22 for SSH and/or SCP
on the server running the Derby metadata repository, port 1527 for TCP*
on servers running the web UI, port 9080 (http) and/or 9081 (https) for TCP (or see Changing the web UI ports)
on all servers*
port 5701 for TCP for Hazelcast (if you wish to use Hazelcast Enterprise, Contact Striim support) plus one additional port per server and Forwarding Agent in the 5702-5799 range. For example, with three servers and two Forwarding Agents, 5701-5705.
port 9300 for TCP (Elasticsearch)
ports 49152-65535 both inbound and outbound for ZeroMQ (see Narrowing the ZeroMQ port range)
port 54327 for multicast UDP on an IP address in the 239 range chosen based on the cluster name (to ensure that each cluster uses a different address). To find that address, install Striim on the first server and look in
striim-node.log(see Logging) for a message such as "Using Multicast to discover the cluster members on group 239.189.210.200 port 54327." (If you do not wish to use multicast UDP, see Using TCP/IP instead of multicast UDP.)
*Not required if you have only one server and no Forwarding Agents.
See also Striim Forwarding Agent system requirements).
Supported web browser
The web client has been tested on Chrome. Other web browsers may work, but if you encounter bugs, try Chrome. Some ad-blocking plugins may prevent the UI from loading.