Installing the CDA Database

Continuous Delivery Automation supports different databases. This topic guides you through the steps you have to perform to install each database type.

This page includes the following:

Tip: Save the database definition files in the following folder: C:\Automic\Release.Manager\Database

MS SQL

  1. Connect to your database server with a database administration tool. For example: Microsoft SQL Server Management Studio.
  2. Create a database. For example: "CDA".
    1. In the Object Explorer window, right-click Databases and select New Database... .
    2. Enter the name for your database. For example: "CDA" and click OK.
  3. Create and assign a database user to the created database. For example: "CDA".
    1. In the Object Explorer window, right-click Security/Logins and select New Login....
    2. Enter the user name. For example: "CDA".
    3. Select SQL Server authentication (this depends on your company security policies). For more information, see Installing the CDA Database.
    4. Enforce the password policy (this depends on your company security policies). Ensure that the database password does not include the special characters []{}(),;?*=!@\. Otherwise, the CDA components cannot access the database.

      Important! Unencrypted passwords cannot start with --10.

    5. Select the default database. For example: "CDA".
  4. Set the DB Owner database role for the created database user and database
    1. Select User Mapping in the left window area.
    2. Select your database ("CDA").
    3. Select the db_owner role.
  5. Set up IIS to work with the CDA server.
  6. Run the first-time setup screen to generate the DB schema. See: First-Time CDA Setup.

For more information, see Configuring SQL Server to Connect to AE and CDA DB.

ORACLE

  1. Run the Oracle Universal Installer and follow the steps as described in the Oracle documentation.
  2. Verify that you have the CREATE USER, CREATE ANY CONTEXT and GRANT ANY PRIVILEGE system privileges.
  3. Create a user, specify a password and define the default tablespace:

    Important! Unencrypted passwords cannot start with --10.

    Example:

    CREATE USER ARAUser IDENTIFIED BY abc123 DEFAULT TABLESPACE AUTOMIC_ARA_DATA

  4. Grant the privilege to create any context (a set of application-defined attributes that validates and secures an application):

    Example:

    GRANT CREATE ANY CONTEXT TO ARAUser

  5. Grant the privilege to create tables:

    Example:

    GRANT CREATE TABLE TO ARAUser

  6. Grant the privilege to create sequences:

    Example:

    GRANT CREATE SEQUENCE TO ARAUser

  7. Grant session rights:

    Example:

    GRANT CREATE SESSION TO ARAUser

  8. Grant the user the UNLIMITED TABLESPACE system privilege (which overrides all existing tablespace quotas and allows the user to allocate as much space as needed in every tablespace):

    GRANT UNLIMITED TABLESPACE TO ARAUser

  9. Use the previously created user to execute the Database\oracle-ddl.sql script.

    Note: When using Oracle as back-end, all entities are case-sensitive. For example, a user called CDA is different from a user called cda.

PostgreSQL

  1. Connect your database server with a database administrator tool (for example: pgAdmin). Log in as superuser.
  2. Right-click Login Roles and select New Login Role... to create a user (for example: CDA_user).

    Note: The new user must have at least Can Login privileges.

  3. Right-click Databases and select New Database... to create a database.

    1. Enter a name for the database.
    2. Select UTF8 encoding.
  4. (Optional) Create a new schema (for example: CDA schema)

    Important! Ignore this step if you are using a public schema.

    1. In the Schema dialog, fill out the fields on the General tab page to identify the schema (at least name and owner).
    2. Click the Security tab and grant Create and Usage privileges to the CDA_user.
    3. Click the Default Privileges tab > Tables nested tab and grant Insert + Select + Update + Delete privileges to the CDA_user.
    4. Click the Sequences nested tab and grant Select + Update + Usage privileges to the CDA_user.
    5. Click Save.

  5. Right-click the new schema and select Query tool.

    Note: The query tool is an environment that allows you to execute arbitrary SQL commands and review the result set.

    1. Load postgresql-dll.sql (example path: Automic\Release.Manager\Database)
    2. (Optional) Add set schema schema_name to the first row (for example: set schema 'cda';).

      Important! Ignore this step if you are using a public schema.

    3. Add a check next to Auto-Commit to instruct the server to automatically commit each transaction.
    4. Click the execute button.

Report Database

If you want to use the reporting functionality, you have to specify a dedicated reporting database and configure the connection and database type in the customer.config settings for ReportDatabase and ReportDatabase.Type (Automic\Release.Manager\WebUI\customer.config). The reporting database can be any supported SQL Server database. The user that is used to establish the connection needs the right to create tables.

  1. Define the database for storing the reporting data tables.

    Note: When you use the CDA database for reporting data, the reporting data tables are created among the other CDA database tables.
    Tip: Create a dedicated database for reporting data.

  2. Adapt the configuration file customer.config (Automic\Release.Manager\WebUI\customer.config) as follows:

    • Set the ReportDatabase connection string for the SQL database where the reporting data is saved.

    • Set the ReportDatabase.Type to the SQL database back-end which is used.

      For more information, see Configuring CDA via Customer.Config File.

Next step:

Installing the CDA Web Server