The instance configuration supports five different configuration types:
The following table gives an overview of the supported configuration types, their location, and which configuration aspects they cover.
Configuration type |
Configuration instance |
Location |
Description |
General Properties |
Event Service Core Properties |
<EventService_ROOT>/conf/rtbs.properties |
EDA Configuration
|
General Properties |
HA-Store |
<EventService_ROOT>/ha-store/conf/server.properties |
Persistence settings for high availability
It is not recommended making other changes to the configuration file. Especially broker.id should only be changed using the Other configuration type (cluster configuration, see below). Port settings should be changed using the ports configuration type (see below). |
General Properties |
Zookeeper |
|
Apache Zookeeper configuration. It is not recommended making any manual changes to the file. All relevant aspects can be configured using the configuration types listed in this table. |
Keystores |
|
<EventService_ROOT>/conf/rtbs.properties |
Keystore location, alias, type, location, password |
Other |
|
|
Cluster configuration:
Note: The replication factor setting only affects buffers that are created after the replication factor was changed, that is, changing the replication factor does not affect existing buffers.
|
Ports |
|
|
Port configuration for Event Service (non-TLS/TLS), Zookeeper, HA-Store |
Truststores |
|
<EventService_ROOT>/conf/rtbs.properties |
Truststore location, alias, type, location, password, and period. The truststore is required to validate (JWT) tokens that MashZone NextGenMashZone NextGen uses to authenticate against MashZone NextGen Event Service. Make sure to use a truststore that contains a public key matching the private key used in MashZone NextGen (see section Protect MashZone NextGen Event Service access). |
<EventService_ROOT> usually is <INSTALL_ROOT>/MashZoneNG/rtbs