Data Source Templates for Using in Management Center

Certain settings for data sources are not available in the Management Center for security reasons; however, they are possible via configuration.

These are:

  • Parameterized URLs to the server of a data source, for example schema names for PostgreSQL databases (in the Management Center, the URL is built from the minimum specifications)

    For WMS, WMTS, or Vector Tile data sources, we recommend: Do not use any environment variables, system properties, or Cadenza variables that refer to sensitive information, as this information is automatically visible to users of these layers when accessing the geodata server directly. Geodata servers without authentication are currently always accessed directly. In this case, $SYSTEM/$VAR properties that are used in the URL are resolved and their values are automatically visible to the users of these layers. For geodata servers with authentication, access is not direct, but always via Cadenza. In this case, sensitive information in the URL remains hidden from the users of these layers.

  • For Oracle databases: JDBC URLs with SID or other syntax (in the Management Center, the database name must be specified via the service name)

  • Login credentials for the data source, especially if you need to use $SYSTEM/$VAR properties within the user name or password. If the credentials are configured, they cannot be changed in the Management Center.

    All authorized users (system privilege "Manage data sources") can use the configured templates, and when using a template with stored credentials they have direct access to the connected database or geodata service - without being prompted for a user name and password!

  • Driver, if the standard driver should not be used for the data source type. Information on the standard drivers used by Cadenza.

  • Datasource-specific properties to adapt the behavior of Cadenza to the sorting behavior of the data source when sorting in RAM. Cadenza adopts the behavior of the data source with regard to NULL value sorting and language-dependent alphabetical sorting. Except for pivoting and when providing the results for a text view with data, because here the sorting is performed in the RAM. This means that the sorting behavior can deviate from that of the data source. To prevent this, you can adapt the sorting behavior of Cadenza to that of the data source.

  • Datasource-specific properties to adapt the behavior of Cadenza to the sorting behavior of the data source when sorting in RAM. Cadenza adopts the behavior of the data source with regard to NULL value sorting and language-dependent alphabetical sorting. Except for pivoting and when providing the results for a text view with data, because here the sorting is performed in the RAM. This means that the sorting behavior can deviate from that of the data source. To prevent this, you can adapt the sorting behavior of Cadenza to that of the data source.

  • Data source type-specific connection properties that are passed on to the driver when the connection is established, for example to optimize the performance of RDBMS data sources

  • PL/SQL routines that are to be executed when the connection to the data source is opened or closed. For example, the VPD application context can be passed to an Oracle table that is protected via VPD (Virtual Private Database) (tested with Oracle 12c Enterprise Edition).

You create a template for an affected data source in the repositorydatasourcetemplates-config.xml configuration file. The template can then be selected and added for the data source in the Management Center. The URL to the data source is not visible in the Management Center.

The information in the configuration file is not saved in the data source, but is referenced. Changes in a template therefore affect the data source.