Supported Data Sources (Details)

The tables and lists show which data sources are supported by which functions of Cadenza Workbooks. The generally supported versions of the data sources can be found on the overview page. You can also find an overview of the mapping of database data types to Cadenza data types here.

As a rule, further requirements must be met in order to use the functions, for example configuration via plug-ins or requirements for the data sources themselves.

Databases for Cadenza infrastructure functions

opt. Oracle PostgreSQL/EDB MSSQL

Cadenza infrastructure (Metadaten)

Access management

✅

✅

–

1)

Repositories

✅

✅

–

2)

✅

Performance logging

✅

–

–

✅

Audit logging

✅

✅

–

1)

Storage of user settings

✅

✅

–

2)

Job Scheduling

✅

✅

–

1)

Data management (factual and geodata)

Cadenza Data Store (CDS)
(for Self service data and derived or similar data)

✅

✅

✅

2)

1) also HSQLDB for test purposes (we expressly advise against using it in productive operation)

2) also H2 for test purposes (we expressly advise against using it in production operation)

Data Sources With Data

Information on the supported data types and their mapping to Cadenza data types

Data Sources for Data Analysis

Depending on the type of data source, there are technical restrictions on objecttypes, views and filters. Cadenza offers the option of downloading the required data by objecttype into a Cadenza Data Store so that the full Cadenza functionality can be used.

Relational Databases

  • Oracle, Oracle Spatial and Graph

  • PostgreSQL/EDB, PostGIS

  • Microsoft SQL Server (MSSQL) with the following limitations:

    • Objecttypes: no data enrichment

    • Filter: no text pattern filter

  • H2 (for test purposes; we expressly advise against use in productive operation)

Search and Analysis Engines

  • Elasticsearch with following limitations

    • Only individual indices are supported.

    • Data types: no binary, unsigned-long or nested data types and no dynamic attributes (e.g. _id or _score)

    • Data sources: no use as CDS

    • Objecttypes: no geometries, hierarchies or function attributes; No “Count (distinct)" aggregation, no sorting attributes; no associations or static data restrictions; no combined objecttypes; no data acquisition; no data import

    • Views: no advanced OLAP functionalities (e.g. subtotals, Top-N analysis); no JasperReports views

    • Filters: Supported are table, value interval, date, date interval and text pattern filters (text pattern filter: full Lucene functionality)

    • Location Finder: is not supported.

    • Test connection in Management Center: For authorized users to be able to test the connection to the Elasticsearch engine from the Management Center, users must have the monitor cluster permission in ELK (Elasticsearch/Kibana). If the permission is not granted, Cadenza can still connect (given other read permissions), only the Cadenza function Test connection will not work as expected.

  • OpenSearch

    OpenSearch has the same limitations as Elasticsearch.

Geodata Services

  • WFS with the following limitations:

    • Data sources: no use as CDS

    • Objecttypes: no function attributes or associations; no sorting attributes; no combined objecttypes; no variables for user-based restrictions; no data acquisition

    • Views: no Top-N analyses, intermediate values or total values (columns and rows); no display of dimension values without data; no JasperReports views

    • Filters: Supported are table, value interval, date, date interval and text pattern filters (text pattern filter: case sensitive), as well as spatial filters.

    • Filter: Attributes are not available in query filters.

    • Location Finder: Only text attributes (String) can be defined as searched attributes for the search source.

  • Feature service of ArcGIS Server (REST interface) with the following limitations:

    • Data sources: no use as CDS

    • Objecttypes: no function attributes, date hierarchies or associations; no sorting attributes; no combined objecttypes; no variables for user-based restrictions; no data acquisition

    • Views: no Top-N analyses or intermediate values; no display of dimension values without data; no JasperReports views

    • Filters: Attributes are not available in query filters.

    • Location Finder: Only text attributes (String) can be defined as searched attributes for the search source.

Further Data Sources

For visualization in a map view

  • WMS

  • WMTS, WFS, ArcGIS, OSM via Cadenza Classic Layer

  • Vector Tile Service