Installing Configuration Server
Configuration Server is an optional Streaming Integration Platform component that serves two main purposes:
- Generation and distribution of TLS certificates for other components (ISAM Agent, JSON Agent, SQL Agent).
- Central configuration management via custom configuration UI.
Configuration Server is a .NET 10 ASP.NET application and can be installed on a suitable Windows or Linux system.
Normally you would download the Configuration Server installer from the Synergex Resource Center but to simplify the workshop a copy of the installer is already present on your Linux server:
~/installers/sip-config-server-1.0.0-1.el9.x86_64.rpm
It's finally time to install the first Streaming Integration Platform component:
Install the Configuration Server
sudo dnf install -y ~/installers/sip-config-server-1.0.0-1.el9.x86_64.rpm
sip install config
As the installation proceeds you will see messages like this:
===============================================================================
Streaming Integration Platform: CONFIGURATION SERVER
===============================================================================
By installing this product you accept the terms of the Synergex Product License
agreement (PLA) which can be viewed at:
https://www.synergex.com/wp-content/uploads/2022/08/SDE_PLA_CURRENT-1.pdf
Using configuration data from /etc/sysconfig/sip.conf
- Service name : sip-config-server
- User account : sip-service
- User group : sip-service
- Dflt profile : default
- HTTPS port : 5121
Installing : sip-config-server-1.0.0-1.el9.x86_64 1/1
Running scriptlet: sip-config-server-1.0.0-1.el9.x86_64 1/1
Starting service
Checking for Configuration Server CA certificate
Found CA certificate: /etc/synergex/sip/config-server/config-server-ca-sipws.crt
Copying CA certificate to /etc/pki/ca-trust/source/anchors.
Refreshing system CA trust.
CA trust update completed.
===============================================================================
Installation complete.
===============================================================================
Configuration Server runs as a systemd service called sip-config-server. Some
useful commands for managing and monitoring the service can be found below:
View server log: sudo journalctl -u sip-config-server -f
Server status: sudo systemctl status sip-config-server
Stop service: sudo systemctl stop sip-config-server
Start service: sudo systemctl start sip-config-server
Restart service: sudo systemctl restart sip-config-server
Disable service: sudo systemctl disable sip-config-server
Enable service: sudo systemctl enable sip-config-server
Uninstall service: sudo systemctl remove sip-config-server
In addition to service-related information being recorded in syslog, a service
log file may also be created if ISAMAgent.LogToDisk is set to true in the
Master configuration file (MasterConfig.json), and the location of the server
log file is determined by the value of ISAMAgent.LogToDisk.
Verifying : sip-config-server-1.0.0-1.el9.x86_64 1/1
Installed:
sip-config-server-1.0.0-1.el9.x86_64
Complete!
Verifying Configuration Server is Running
Before proceeding, check that Configuration Server is running:
Execute this command
systemctl status sip-config-server
sip status config
Either way, you should see something like this:
● sip-config-server.service - Streaming Integration Platform Configuration Server
Loaded: loaded (/usr/lib/systemd/system/sip-config-server.service; enabled; preset: disabled)
Drop-In: /etc/systemd/system/sip-config-server.service.d
└─override.conf
Active: active (running) since Tue 2026-09-22 14:53:03 PDT; 1min 56s ago
Main PID: 5621 (ConfigServer)
Tasks: 24 (limit: 100396)
Memory: 43.7M (peak: 44.4M)
CPU: 552ms
CGroup: /system.slice/sip-config-server.service
└─5621 /usr/lib/synergex/sip/config-server/ConfigServer --config-profile default --port 5121
Sep 22 14:53:04 sipws bash[5621]: WARNING: Failed to establish CA trust: Failed to copy CA to anchors (install). Ensure you run as root or have passwordless sudo. (sudo may require NOPASSWD or run the app as root)
Sep 22 14:53:04 sipws bash[5621]: ExitCode: 1
Sep 22 14:53:04 sipws bash[5621]: STDERR:
Sep 22 14:53:04 sipws bash[5621]: 20260922-145304 Failed to establish CA trust: Failed to copy CA to anchors (install). Ensure you run as root or have passwordless sudo. (sudo may require NOPASSWD or run the app as root)
Sep 22 14:53:04 sipws bash[5621]: ExitCode: 1
Sep 22 14:53:04 sipws bash[5621]: STDERR:
Sep 22 14:53:04 sipws bash[5621]: 20260922-145304 No XML encryptor configured. Key {2c2db685-7a89-41ed-9d0a-e701e161380b} may be persisted to storage in unencrypted form.
Sep 22 14:53:04 sipws bash[5621]: 20260922-145304 Server certificate created
Sep 22 14:53:04 sipws bash[5621]: 20260922-145304 Created local database /etc/synergex/sip/config-server/config-server.db
Sep 22 14:53:04 sipws bash[5621]: 20260922-145304 Enabled Swagger UI at /swagger
Is it running?
- Look for Active: active (running) which, depending on your terminal software, may be displayed in green.
- If it is not running, seek assistance from a workshop facilitator.