General Requirements for Upgrading CDA

This topic provides information about minimum requirements for hardware and software for servers and clients used for Automic Continuous Delivery Automation solutions.

Before You Start Installing/Upgrading, Check Compatibility and Prerequisites

You can obtain all system requirements and compatibility information from the Compatibility Matrix.

A Note on Hardware

The system requirements are broken down to the level of individual server and client machines. Within this section, each computer is described with its function and CA Automic components.

It is not necessary to have an individual computer for every purpose. Depending on your environment, combining two or more machines (physical, virtual, or both) is possible and useful.

The decision to install two or more components (for example, server software plus database) on a single hardware depends on.

• the designated usage (test versus production environment) and
• the planned load.

Prerequisites

• Ensure that you have the phone number and email address of Files to Aid Technical Support and your login data for https://downloads.automic.com/.

  You can request assistance from consultants or even support 24 hours a day, 7 days a week when you upgrade your system. Our experts are trained in providing excellent support when action is taken in critical and sensitive areas of your AE/CDA system. Contact your Account Manager or the Technical Support when you know when you are going to start the upgrading process.

• Carefully read the Release Notes of the relevant CDA version. They include information that must be considered during the upgrade process.
• Review the Troubleshooting Installation and Upgrade Errors section.
• Define an upgrade window (for an in-place upgrade) or a code freeze window (for a parallel upgrade).
• Download the latest version of the CDA Offering from https://downloads.automic.com/.

• Download and install .NET framework 4.8 on the CDA server:

  https://dotnet.microsoft.com/download/dotnet-framework

  Notes:

  • External links are subject to change at any time
  • Only Microsoft SQL Server 2016 and later versions are supported

• Install Oracle Data Access Component (ODAC) version x64.

  Notes:

  • The Machine wide configuration option must be enabled.
  • This requirement is only applicable if the CDA version you are upgrading from is lower or equal to 6.0.2 and for the Release Manager Unified Upgrade tool.
  • After installing ODAC, check if the Oracle.DataAccess.dll file exists in the Oracle ODAC folder. If not, copy it to the folder.

• To prevent display issues that are caused by mixed content, ensure that both CDA (IIS) and AWI (Tomcat) are configured to use either HTTP (unencrypted and therefore not recommended) or HTTPs (recommended). For more information, see Securing Access with HTTPS.

• Database:

  • Has your database been maintained regularly? Start a reorganization run with AE/CDA utilities and database means before you upgrade the database. The smaller the database, the quicker the upgrading process. For more information, see Working with the Clean-up Utility

    Note: You need sufficient disk space for having tables duplicated.

  • Back up the AE and CDA databases you want to upgrade.
  • Stop all CDA instances that access the databases you want to upgrade to avoid data corruption.
• In case of an In Place upgrade: Back up all the files you want to upgrade.
• Ensure that the following roles and features are installed:

  Features

  • .NET Framework 3.x Features
    • .NET Framework 3.x (includes .NET 2.0 and 3.0)
    • HTTP Activation
    • Non-HTTP Activation
  • .NET Framework 4.x Features (4 of 7)
    • .NET Framework 4.x
    • ASP.NET 4.x
    • WCF Services (2 of 5)
      • HTTP Activation
      • TCP Port
  • Windows PowerShell (3 of 5)
    • Windows PowerShell 4.0
    • Windows PowerShell 2.0 Engine
    • Windows PowerShell ISE
  • Windows Process Activation Service
    • Process Model
    • .NET Environment
    • Configuration APIs
  • WoW64 Support

  Roles

  • Web Server (IIS) (16 of 43)
    • Web Server (15 of 34)
      • Common HTTP Features (5 of 6)
        • Default Document
        • Directory Browsing
        • HTTP Errors
        • Static Content
        • HTTP Redirection
      • Health and Diagnostics (1 of 6)
        • HTTP Logging
      • Performance (1 of 2)
        • Static Content Compression
      • Security (1 of 9 installed)
        • Request Filtering
      • Application Development (7 of 11)
        • .NET Extensibility 3.x
        • .NET Extensibility 4.x
        • ASP.NET 3.x
        • ASP.NET 4.x
        • ISAPI Extensions
        • ISAPI Filters
        • WebSocket Protocol
    • Management Tools (1 of 7)
      • IIS Management Console

    Note: The version numbers may vary depending on your operating system.

• Prerequistes for the Release Manager Unified Upgrade tool.

  When using the Release Manager Unified Upgrade, also note the following:

  • Verify that the AE and CDA target versions are aligned.
  • Ensure that the service user has permission to modify AE users and RM.CLIENT_SETTING.
  • Encrypted configuration files cannot be upgraded. Verify that all files are unencrypted before running the Release Manager Unified Upgrade wizard.
  • The upgrade tool cannot write, edit or create any AE object in client 0. Therefore, the system settings (RM.SYSTEM_SETTINGS) cannot be created automatically. This step must be carried out manually by an Administrator.
  • If the CDA service user does not have write/create permissions on a selected client, the tool cannot write, edit, or create any AE object in that client. In this case, the upgrade tool cannot create RM.CLIENT_SETTINGS and modify user/user group objects. These steps must be performed manually.

  More information:

  • Migrate Existing Applications & Synchronize User Permissions