Infrastructure Prerequisites
Before setting up the Admin microservice, ensure the following components are properly set up:- Database Instance: The Admin microservice connects to the same database as the FlowX.AI Engine.
- MongoDB: For additional data management.
- Redis: For caching and transient data storage.
- Kafka: For audit logs, events, and messaging (if using FlowX.AI Audit functionality).
Core configuration
Server configuration
Database configuration
The Admin microservice connects to the same PostgreSQL or Oracle database as the FlowX.AI Engine for storing process definitions.The database schema is managed by a Liquibase script provided with the Engine.
MongoDB configuration
The Admin microservice also connects to a MongoDB database instance for additional data management.Ensure that the MongoDB configuration is compatible with the same database requirements as the FlowX.AI Engine, especially if sharing database instances.
Redis and caching configuration
Redis is used for caching and storing transient data.Kafka configuration
The Admin microservice uses Kafka for sending audit logs, managing scheduled timer events, platform component versions, and start timer event updates.General Kafka settings
Kafka producer configuration
Kafka consumer configuration
Topic naming configuration
Kafka topics configuration
Audit topics
Platform Topics
Events gateway topics
Build topics
Resource topics
OAuth authentication for Kafka
When using thekafka-auth profile, the following variables configure OAuth for Kafka:
When using the
kafka-auth profile, the security protocol will automatically be set to SASL_PLAINTEXT and the SASL mechanism will be set to OAUTHBEARER.Logging configuration
The FlowX Admin microservice provides granular control over logging levels for different components:Localization settings
Health monitoring
Platform health configuration
Multi-edit and undo/redo configuration
Resources usage configuration
Authentication and Authorization Configuration
The FlowX Admin microservice supports authentication and authorization through OpenID Connect (with Keycloak as the default provider) and allows detailed role-based access control.OpenID Connect Configuration
Service Account Configuration
Spring Security OAuth2 Client Configuration
Identity Provider Configuration
Keycloak Configuration
Microsoft Entra ID configuration
The role-based access control is configured in the application YAML and grants specific permissions for platform management, user management, process management, integrations management, and configuration management.

