Windows installation
Install through WSL2
Configure Kafka
Steps for Linux and WSL2
Validate the installation
Check the Kafka setup
Troubleshooting
Fix Kafka connection problems
CompatibilityUse Kafka with GermainUX 2024.2 or later. Earlier GermainUX releases use Apache ActiveMQ.
Prerequisites
Before installing Kafka, confirm that:Windows installation
Kafka runs on Windows through Windows Subsystem for Linux 2 (WSL2).1 Install WSL2
Open PowerShell as an administrator:2 Install JDK 17
Run the following commands in Ubuntu:3 Download and install Kafka
The example below uses Kafka 3.7.1. Use the version approved for your GermainUX release.Linux installation
1 Install JDK 17
The following example applies to Ubuntu and other Debian-based distributions:2 Download and install Kafka
Configure Kafka
The following configuration steps apply to both Linux and WSL2 installations.1. Configure the data directory
Open the KRaft server configuration:2. Configure advertised listeners
Kafka returns the address configured inadvertised.listeners to its clients. The address must therefore be resolvable and reachable from Germain Enterprise and every Germain node.
For a local, single-host deployment:
localhost with the Kafka server’s DNS name or reachable IP address:
localhost when GermainUX components connect from other hosts. Remote clients would interpret it as their own local machine.
If needed, also verify the listener binding:
Initialize Kafka storage
Kafka storage must be formatted once before the broker starts for the first time. Generate a cluster ID:Start Kafka
Start Kafka in the foreground:Validate the installation
Confirm that Kafka is listening
Test connectivity from each GermainUX host
<kafka-host> with the hostname configured in advertised.listeners.
Test Kafka operations
Create a temporary topic:Start GermainUX
Use the following startup order:1
Start Kafka and wait until it is ready to accept connections
2
Start Germain Enterprise
3
Start the Germain nodes
4
Confirm that the GermainUX components connect to Kafka without errors
Production considerations
The preceding procedure uses an unencryptedPLAINTEXT listener and a single Kafka broker. Before using this configuration in production, consider:
- TLS encryption
- Client authentication and authorization
- Multiple brokers and replication
- Disk-capacity monitoring
- Topic retention policies
- JVM and operating-system monitoring
Show all 10
Show all 10
- Automated startup and restart
- Configuration and data backups
- Firewall restrictions
- Log rotation
Troubleshooting
If GermainUX cannot connect to Kafka, verify:- Kafka is running.
- Port
9092is listening and accessible. advertised.listenerscontains a hostname reachable by every GermainUX host.- DNS resolves the advertised hostname correctly.
- No firewall blocks the connection.
- Kafka and GermainUX use compatible security settings.
- The Kafka data directory is writable and has sufficient space.
- Kafka started before Germain Enterprise and the nodes.
- Install JDK
- Install Kafka
Get Help
Contact GermainUX Support
The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE.

