Connection of the Repository Database schemas

Workbooks are stored in database-based repositories, as are the object types of imported data. The database schemas intended for repositories must be prepared.

In order to connect the prepared databases and the XML repositories, their access data must be stored in a configuration file.

Configuration (Overview)

  • At least one database schema for a database-based repository must be connected.

Optional:

  • The name of the configuration file can be changed.

Connecting a Database Schema for a Repository

A database prepared for this purpose must be connected so that a repository can be created in the Management Center. Several repositories can be created in such a database schema.

In the configuration file repositoryList.xml, the connection to the database schema must be entered analogous to the following example for an Oracle database schema:

  <databaseRepository name="repository1" printName="Repository 1">
    <driverName>oracle.jdbc.OracleDriver</driverName>
    <jdbcURL>jdbc:oracle:thin:@//example.oracle.server:1521/my_repositoryDB</jdbcURL>
    <user>USER</user>
    <password encrypted="true">the_disy_encoded_password</password>
    <connectionPoolSize>10</connectionPoolSize>
    <properties>
      …
    </properties>
    <polling enabled="true">
      <duration>PT15M</duration>
    </polling>
  </databaseRepository>

The following applies:

  • <databaseRepository>: Access data and other connection properties to the database schemas of the repository

    • name: Unique ID of the repository

    • printName: Name of the repository as it should be displayed on the user interface

  • <driverName>: Name of the JDBC driver used. Environment variable, system properties and Cadenza variable can be used. Information on the standard drivers used by Cadenza

  • <jdbcURL>: JDBC URL of the database. Environment variable, system properties and Cadenza variable can be used. The JDBC URL can optionally be parameterized, for example with a schema.

  • <userName>: Database user to be used to establish the database connection. Environment variable, system properties and Cadenza variable can be used.

  • <password>: Password of the database user. Environment variable, system properties and Cadenza variable can be used.

  • encrypted: Specifies whether the password is encrypted (default value is true). (Learn how to encode passwords for Cadenza)

  • <connectionPoolSize> (optional): Number of connections that the connection pool may generate to the database (default value is 10). This number should increase with the number of repositories stored in the database. Monitoring the available connections helps finding a good value for this parameter. Variables like $SYSTEM{CONNECTION_POOL_SIZE} can be used.

  • <properties> (optional): Database-specific connection parameters, for example for the secure database connection with Oracle Advanced Security (OAS). Environment variable, system properties and Cadenza variable can be used.

  • <polling> (optional): Specifications for cyclic change requests from Cadenza Web Classic to the database

    • Enabled (optional): Specifies whether polling should be carried out (default value = true)

    • <duration>: Specification of the intervals at which polling is to be carried out. The duration is specified according to ISO 8601 in PnYnMnDTnHnMnS format, e.g. PT600S means "until in 600 seconds from now" (more information)

Change the Name of the Configuration File

By default, the name of the configuration file is repositoryList.xml. If a different name is to be used, this must be configured:

To do this, the <repositoryListFile> element must be added to the cadenza-config.xml file, analogous to the following example:

<repositoryListFile>myRepositoryList.xml</repositoryListFile>