CDA Installation Check and Post-Installation Tasks

This page includes the following:

CDA Installation Check

The following checklist provides a high-level overview of the installation process and it should be used only as a reference.

Database Configuration

  • Installed software prerequisites
  • Database installed (SQL Server/Oracle/PostgreSQL)
  • Database created
  • User created
  • Correct permissions applied to user
  • Schema loaded from DDL

Webserver Configuration

  • Installed software prerequisites
  • IIS installed
  • Configured customer.config (Automic\Release.Manager\WebUI\customer.config)
    • AE configured
    • CDA callback URL
    • AWI callback URL
  • Created Website in IIS
  • Created Application Pool
  • Created user
  • Imported Custom Types
  • Imported Actions

CDA Checks

  • Test creation of users/folders
  • Test CDA callback URL in AWI

To check if the CDA plug-in, the CDA server, and the CDA database are correctly installed and configured, follow the steps below.

To Check a CDA Installation

  1. Open your browser.
  2. Insert the URL to request the CDA/AWI web application
  3. Log in with the default administrative CDA user 'admin', password 'password' .

    Note: See Before Logging in for the First Time

  4. Open the Release Automation Perspective
  5. Check the installation status using the Post-Installation Checklist Widget.

    Note: You can find the Post-Installation Checklist Widget on the CDA dashboard.

    6. If you can perform all steps successfully, CDA is installed correctly.

Note: After the installation, if you did not import any package, the application does not contain any types. See Administering CDA via Web Interface to learn how to create and configure them.

Post-Installation Tasks

After CDA has been installed, the system is ready to be uses.

The following tasks help you check the status and fine-tune your CDA system after installation:

  • CDA System Check

    Task: Check the installation status using the Post-Installation Checklist Widget.

    Mandatory: Yes

  • Actions

    Task: Install more packages as described in Package Manager.

    After a manual installation, you must install the packages manually according to your needs. Otherwise, you cannot use the actions delivered with CDA.

    Note: All packages with actions available at the time of the release are delivered with the installation package. If you installed CDA with the ONE Installer, all packages are already installed.

    Mandatory: No

  • Performance

    Task: As a performance enhancing task, you can change Max Perm Size and Heap Size of your Tomcat prepared by the ONE Installer.

    Note: This task is recommended when using CDA.

    Mandatory: No

  • Security

    Task: You may change the ownership of the installed files to the executing user.

    Mandatory: No

  • Configuration settings

    The RM.CLIENT_SETTINGS and RM.SYSTEM_SETTINGS VARA objects contain global definitions (general configurations for the web applications), application, approval, deployment-related, and execution parameters for CDA. The RM.CLIENT_SETTINGS VARA object is created by the Release Manager Unified Upgrade tool.

    If you have installed a new CDA system manually or with the ONE Installer, or if you have performed a manual upgrade of the system, you can change the default configuration by creating the objects manually or importing the VARA templates located in the Automic\Release.Manager\AE folder.

    Note: The RM.CLIENT_SETTINGS and RM.SYSTEM_SETTINGS VARA objects are case sensitive. Make sure to define them in uppercase if you create them manually.

    For more information, see: Configuring CDA via RM.CLIENT_SETTINGS/RM.SYSTEM_SETTINGS VARA Objects