11 docs tagged with "configuration"

The Genesis Application Platform supports the following database technology:

The entity-management micro front-end provides a seamless way to interact with back-end resources, enabling users to manage entities directly from the front-end.

Genesis Router is responsible for all communication between the front end and back end.

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.

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).

Initialising and adding to a new application

This section gives an overview of server configuration items applications may need to create or override.

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.

Site specific is an area of the run directory, on a deployed application instance, where you can override the standard definitions found elsewhere in your application.

The system-definition file genesis-system-definition.kts is the main configuration file for your application, controlling how the application behaves at runtime.