Instance configuration
The instance configuration supports five different configuration types:
![*](chapterTOC_bullet.png)
General properties contained in files
rtbs.config,
zookeeper.properties,
server.properties![*](chapterTOC_bullet.png)
Keystore Configuration (
rtbs.properties)
![*](chapterTOC_bullet.png)
Truststore Configuration (
rtbs.properties)
![*](chapterTOC_bullet.png)
Ports (
rtbs.properties,
zookeeper.properties,
server.properties)
![*](chapterTOC_bullet.png)
Other: Cluster Configuration (
rtbs.properties,
zookeeper.properties,
server.properties)
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 | RTBS Core Properties | <RTBS_ROOT>/conf/rtbs.properties | EDA Configuration ![*](chapterTOC_bullet.png) EventTypeStore location (com.softwareag.event.routing. eventtypestore.location) DES Configuration ![*](chapterTOC_bullet.png) TypeRepository location (com.softwareag.events.repository. location) ![*](chapterTOC_bullet.png) License location (com.softwareag.events.license. location) ![*](chapterTOC_bullet.png) Routing Configuration (com.softwareag.events.routing. configuration.directory) It is not recommended to make other changes to the configuration file. All other settings in the configuration file can be configured using the configuration types listed in this table. |
General Properties | HA-Store | <RTBS_ROOT>/ha-store/conf/server.properties | Persistence settings for high availability ![*](chapterTOC_bullet.png) Retention time (log.retention.hours, time in hours before buffered data becomes eligible for deletion). Defaults to 168 hours (7 days) ![*](chapterTOC_bullet.png) Retention size (log.retention.bytes, maximum size of buffered data, per buffer). Defaults to infinity, i.e., the size is only bound by retention time) It is not recommended to make 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 to make any manual changes to the file. All relevant aspects can be configured using the configuration types listed in this table. |
Keystores | | <RTBS_ROOT>/conf/rtbs.properties | Keystore location, alias, type, location, password |
Other | | | Cluster configuration: ![*](chapterTOC_bullet.png) Replication Factor: determines how many replicas of persisted data (for high availability) will be created. The number must be >= 1 and <= the number of RTBS instances in the cluster. The number must be >= 2 to achieve any fault tolerance. As a rule of thumb: the higher the number of replicas the more RTBS node failures can be tolerated. However, the amount of storage required on the RTBS machines increases linearly with the number of replicas. 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. ![*](chapterTOC_bullet.png) Zookeeper-URLs ![*](chapterTOC_bullet.png) Format: hostname:port, for example, machine1.mycompany.com: 12181![*](chapterTOC_bullet.png) To form a cluster, Zookeeper URLs must contain a comma-separated list of all machines that should be part of the cluster. To form a cluster of the machines machine1, machine2, and machine3, enter: machine1: 12181,machine2:12181, machine3:12181 ![*](chapterTOC_bullet.png) Instance ID ![*](chapterTOC_bullet.png) The instance ID must be a number between 1 and 255 and must be unique among all cluster members. It is used to identify cluster members. The ID is internally used to configure RTBS Core's rtbs.id, Zookeeper's ID (myid), and HA-Store's broker.id. |
Ports | | | Port configuration for RTBS (non-TLS/TLS), Zookeeper, HA-Store |
Truststores | | <RTBS_ROOT>/conf/rtbs.properties | Truststore location, alias, type, location, password, and period. The truststore is required to validate (JWT) tokens that MashZone 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). |
<RTBS_ROOT> usually is <INSTALL_ROOT>/MashZoneNG/rtbs