The system-definition file is the basis of all configurations. In this page, we describe the different functions available to get properties specified in the system-definition.kts file. Default methods have implementations to provide default values for each property.
Configuration options
This page gives details of the configuration requirements common to adaptors for all vendors.
Initialising and adding to a new application
Database caching on local microservices is supported out of the box. You can configure a caching layer for any Genesis module. The cache can reduce the database workload for tables that contain static data.
The Genesis low-code platform supports the following database technology:
Genesis Router is responsible for all communication between front end and back end.
Some files are essential to the development and running of your application. You need to know what they are for and how to configure them. The pages in this section provide the details.
Your application must have a -processes.xml file. This contains the configuration of each module in the application (Data Server, Request Server, Event Handler, etc). It is created automatically when you start a new Genesis project using GenX CLI tool, but you might well want to update it - and you certainly want to take a good look at it.
Every application must have a -service-definitions.xml file. This is where you specify the ports of the various processes. These are used to communicate internally between processes.
The system-definition file genesis-system-definition.kts is the main configuration file for your application.
Site-specific is an area of the run directory where you can override the standard definitions found elsewhere in your application. By default, its location is: