Comment on page
PACE Configuration
PACE is a Spring Boot Application configured via its standard mechanism. We typically use an
application.yaml in a /config subdirectory of the working directory the PACE server was started.An outline of the yaml file is as follows.
spring # The basis of the PACE web application.
datasource # This is where PACE stores its own data (such as the stored
# data-policies, the global policies etc.)
url # This is the jdbc url to the PACE database.
# Example: `jdbc:postgresql://localhost:5432/pace`. The last part
# of the url is the name of the database.
hikari # Hikari is the standard database connection pool used by Spring applications.
username # How to connect to the database.
password #
schema # Which database schema is used to create the tables that PACE needs.
# A typical value is `public`.
logging # Spring logging [configuration][spring-logging]. You can skip this section completely.
level #
some.java.package: [DEBUG|INFO|WARN|OFF][spring-logging]
app # This is the actual PACE configuration
processing # -platforms Defines a list of processing platforms that PACE connects to on startup.
..
catalogs # Defines a list of data catalogs that PACE connects to on startup.
..
global-transforms:
tag-transforms:
looseTagMatch # [See here](../global-policies/global-transforms/README.md#tag-value-matching).
Each of the supported processing platforms has a different configuration format. Every configuration must have a distinct id that can be any non-empty string.
Last modified 12d ago