FlowX Events Gateway setup
This guide will walk you through the process of setting up the events-gateway service.
Infrastructure prerequisites
Before proceeding with the setup, ensure that the following components have been set up:
- Redis - version 6.0 or higher
- Kafka - version 2.8 or higher
Configuration
Configuring Kafka
Set the following Kafka-related configurations using environment variables:
SPRING_KAFKA_BOOTSTRAPSERVERS- the address of the Kafka server, it should be in the format “host:port”
Groupd IDs
The configuration parameters “KAFKA_CONSUMER_GROUPID_*” are used to set the consumer group name for Kafka consumers that consume messages from topics. Consumer groups in Kafka allow for parallel message processing by distributing the workload among multiple consumer instances. By configuring the consumer group ID, you can specify the logical grouping of consumers that work together to process messages from the same topic, enabling scalable and fault-tolerant message consumption in your Kafka application.
| Configuration Parameter | Default value | Description |
|---|---|---|
KAFKA_CONSUMER_GROUPID_PROCESSENGINECOMMANDS_MESSAGE | engine-commands-message | Consumer group ID for processing engine commands messages |
KAFKA_CONSUMER_GROUPID_PROCESSENGINECOMMANDS_DISCONNECT | engine-commands-disconnect | Consumer group ID for processing engine commands disconnect messages |
KAFKA_CONSUMER_GROUPID_PROCESSENGINECOMMANDS_CONNECT | engine-commands-connect | Consumer group ID for processing engine commands connect messages |
KAFKA_CONSUMER_GROUPID_PROCESS_TASKCOMMANDS_MESSAGE | task-commands-message | Consumer group ID for processing task commands |
KAFKA_CONSUMER_GROUPID_PROCESSVERSIONCOMMANDS_MESSAGE | process-version-commands-message | Consumer group ID for processing process version commands messages |
KAFKA_CONSUMER_GROUPID_GENERICCOMMANDS | generic-commands-message | Consumer group ID for processing generic commands messages |
KAFKA_CONSUMER_GROUPID_USERBROADCASTCOMMANDS | user-broadcast-commands-message | Consumer group ID for processing user broadcast commands messages |
Threads
The configuration parameters “KAFKA_CONSUMER_THREADS_*” are utilized to specify the number of threads assigned to Kafka consumers for processing messages from topics. These parameters allow you to fine-tune the concurrency and parallelism of your Kafka consumer application, enabling efficient and scalable message consumption from Kafka topics.
| Configuration Parameter | Default value | Description |
|---|---|---|
KAFKA_CONSUMER_THREADS_PROCESSENGINECOMMANDS_MESSAGE | 10 | Number of threads for processing engine commands messages |
KAFKA_CONSUMER_THREADS_PROCESSENGINECOMMANDS_DISCONNECT | 5 | Number of threads for processing engine commands disconnect messages |
KAFKA_CONSUMER_THREADS_PROCESSENGINECOMMANDS_CONNECT | 5 | Number of threads for processing engine commands connect messages |
KAFKA_CONSUMER_THREADS_TASKCOMMANDS | 10 | Number of threads for task commands |
KAFKA_CONSUMER_THREADS_PROCESSVERSIONCOMMANDS | 10 | Number of threads for processing process version commands messages |
KAFKA_CONSUMER_THREADS_GENERICCOMMANDS | 10 | Number of threads for processing generic commands messages |
KAFKA_CONSUMER_THREADS_USERBROADCASTCOMMANDS | 10 | Number of threads for processing user broadcast commands messages |
Kafka topics related to process instances
| Configuration Parameter | Default value |
|---|---|
KAFKA_TOPIC_EVENTSGATEWAY_PROCESSINSTANCE_IN_MESSAGE | ai.flowx.dev.eventsgateway.engine.commands.message.v1 |
KAFKA_TOPIC_EVENTSGATEWAY_PROCESSINSTANCE_IN_DISCONNECT | ai.flowx.dev.eventsgateway.engine.commands.disconnect.v1 |
KAFKA_TOPIC_EVENTSGATEWAY_PROCESSINSTANCE_IN_CONNECT | ai.flowx.dev.eventsgateway.engine.commands.connect.v1 |
Kafka topics related to process versions
| Configuration Parameter | Default value |
|---|---|
KAFKA_TOPIC_EVENTSGATEWAY_PROCESSVERSION_IN_MESSAGE | ai.flowx.dev.eventsgateway.process-version-commands.message.v1 |
Kafka topics related to user messages
| Configuration Parameter | Default value |
|---|---|
KAFKA_TOPIC_EVENTSGATEWAY_USERMESSAGES_IN_MESSAGE | ai.flowx.dev.core.designer.notification.user.v1 |
Configuring authorization & access roles
Set the following environment variables to connect to the identity management platform:
| Configuration Parameter | Description |
|---|---|
SECURITY_OAUTH2_BASESERVERURL | Base URL of the OAuth2 server |
SECURITY_OAUTH2_CLIENT_CLIENTID | Client ID for OAuth2 authentication |
SECURITY_OAUTH2_CLIENT_CLIENTSECRET | Client secret for OAuth2 authentication |
SECURITY_OAUTH2_REALM | Realm for OAuth2 authentication |
Redis
The process engine sends the messages to the events-gateway, which is responsible for sending them to Redis.
| Configuration Parameter | Description |
|---|---|
SPRING_DATA_REDIS_HOST | Hostname of the Redis server |
SPRING_DATA_REDIS_PASSWORD | Password for Redis server |
SPRING_DATA_REDIS_PORT | Connect to the Redis server |
Master replica
The events-gateway can be configured to communicate with Redis using the MASTER_REPLICA replication mode by configuring the following property:
spring.data.redis.sentinel.nodes: replica1, replica2, replica3, etc…
Correspondent environment variable:
SPRING_DATA_REDIS_SENTINEL_NODES
Example
In the above example, the Spring Boot application will connect to three Redis Sentinel nodes: host1:26379, host2:26379, and host3:26379.
The property value should be a comma-separated list of host:port pairs, where each pair represents the hostname or IP address and the port number of a Redis Sentinel node.
By default, Redis is standalone, so the configuration with redis-replicas is optional for high load use cases.
In the context of Spring Boot and Redis Sentinel integration, the spring.redis.sentinel.nodes property is used to specify the list of Redis Sentinel nodes that the Spring application should connect to. These nodes are responsible for monitoring and managing Redis instances.
Events
This configuration helps manage how event data is stored and accessed in Redis.
| Configuration Parameter | Default | Description |
|---|---|---|
EVENTS_REDIS_FREQUENCYMILLIS | 200 | Time interval (in milliseconds) between Redis queries by the events gateway to check for new messages |
EVENTS_REDIS_TTLHOURS | 4 | Sets the time-to-live for events in Redis to 4 hours |
Configuring logging
The following environment variables could be set in order to control log levels:
| Configuration Parameter | Description |
|---|---|
LOGGING_LEVEL_ROOT | Logging level for the root Spring Boot microservice logs |
LOGGING_LEVEL_APP | Logging level for the application-level logs |
Was this page helpful?