Upgrading the CDA Component from Version 7 to 10

This page includes the following:

Stop the Components

Stop CDA (IIS server), and AWI (for example, Tomcat server).

Make sure that no Automation Engine workflows (including Actions) are open or being executed.

Create New WebUI Folder

Create a new WebUI folder (Automic\Release.Manager\WebUI) and copy the content from the installation package (including all subfolders).
Configure IIS. See: Configuring IIS for CDA

Install the Utilities

Unpack and copy the utilities to your utilities folder (for example, c:\Automic\Release.Manager\Utilities\).

Run the Release Manager Unified Upgrade Wizard

Watch the video:

The wizard is located in the RamiusUpgradeTools folder: Automic\Release.Manager\Utilities\RamiusUpgradeTools

Review the prerequisites before starting the wizard: Prerequistes for the Release Manager Unified Upgrade tool.
Execute the Release Manager Unified Upgrade tool to upgrade the CDA clients and update the configuration files. For more information, see Release Manager Unified Upgrade.
(Optional) Review and update the customer.config file (Configuring the Web Application - Customer.Config) and the web.config file (Configuring the Web Application - Web.Config). For more information see:
(Optional) Review and update the client settings VARA objects. See: Configuring the RM.CLIENT_SETTINGS/RM.SYSTEM_SETTINGS VARA Objects

Important! Historical installation data is not migrated. This might have an impact on some views and widgets, for example, the Deployment Timeline widget and the Installations view.

Replace the Task4Analytics Report

Replace the CDA Report to support Analytics

Open the command line and enter the following command to check if the report is installed in the system. (admin-cli.exe is located here:Automic\Release.Manager\Utilities\AdminCLI):
admin-cli.exe list report -con http://ARAserver/ara -usr 100/ADMIN/AUTOMIC -pwd XXX
The output should look like this:
Connection: MainDatabase
------------------------------------------------
Type name | Table name | Status
------------------------------------------------
Execution | Data4AnalyticsExecution | Operational
ReleaseTask | Task4Analytics | Operational
------------------------------------------------
Enter the following command to remove the Data4AnalyticsExecution report:

admin-cli.exe delete report -tn Data4AnalyticsExecution -con http://ARAserver/ara -usr 100/ADMIN/AUTOMIC -pwd XXX
Enter the following command to install the new report. The report definition file is located in the following folder of the CDA package: Automic\Release.Manager\ReportDefinitions.

admin-cli.exe create report -con http://ARAserver/ara -usr 100/ADMIN/AUTOMIC -pwd XXX -fi c:\download\Release.Manager\ReportDefinitions\Data4Analytics.xml -connection MainDatabase

Enter the following command to check if the installation was successful:

admin-cli.exe list report -con http://ARAserver/ara -usr 100/ADMIN/AUTOMIC -pwd XXX

The output should be as follows:

Connection: MainDatabase
------------------------------------------------------------------------------
            Type name            |          Table name            |  Status
------------------------------------------------------------------------------
Deployment                       |Data4AnalyticsExecution         |Operational
------------------------------------------------------------------------------

Important! The new Data4Analytics report no longer uses execution type data, but deployment type data (Applications, Components). This might have an impact on your existing dashboards.

Update the Index Data

Execute the following commands in the CLI:

admin-cli clearallindex -con (connection string) -usr (user credentials) -pwd (password)

Example:

admin-cli clearallindex -con http://vviedev01/ara -usr 120/ARA/AUTOMIC -pwd ara123
admin-cli index -con (connection string) -usr (user credentials) -pwd (password)

Example:

admin-cli index -con http://vviedev01/ara -usr 120/ARA/AUTOMIC -pwd ara123

Tip: Check the log.txt file to see the execution outcome. For more information, see: CDA Logging Files

Install the CDA Plug-in and Update the connection.properties in the Tomcat Config Folder

Copy the following files to the AWI autoinstall Tomcat folder:
- webui-plugin-bond-*.jar
- webui-plugin-pluginmanager-*.jar
- webui-plugin-actionbuilder-*.jar
(Example path: C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\AWI\WEB-INF\autoinstall).

Note: Further updates can be performed by simply replacing the existing .jar file in the autoinstall folder within the webapps/ directory of the Tomcat server running AWI with the new version. The configuration file will not be overwritten.
Start Tomcat.
Check and configure the CDA plug-in configuration file (for example, C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\awi\config\webui-plugin-bond\connection.properties).

Open the configuration file connection.properties.

Important! Ensure that the URL matches the CDA URL defined in IIS while installing the CDA Web Server Application

Example content in connection.properties:

url=http://host/rm_main (URL of BOND on IIS)

timeout=60000 (BOND session timeout)

package_folder=/PACKAGES (folder containing Automic Continuous Delivery Automation packages)

use_dedicated_api=true

rest_connect_timeout=60000

rest_read_timeout=60000

use_dedicated_api=true (allows to use dedicated API for Deployment Pipeline)

Install the CDA/KPI Dashboards

The CDA start page has been replaced with the CDA dashboard, which contains widgets that provide an overview of the CDA system state.

To install the CDA /KPI Dashboards

The CDA & KPI dashboards can be manually installed by importing the corresponding files ARA.DASH.DEFAULT.xml/KPI.DASH.DEFAULT.xml(located in the \Release.Manager\AE folder) into the correct AE-client. For more information, see Working with Dashboards. To import the XMLs, you can use the Automation Engine import function. For more information, see Importing/Exporting Objects.

Note: The Access to Dashboard privilege must be assigned to the users to whom you want to grant access to dashboards. For more information, see Setting Up Dashboards.

Add the PM_INDEX_URL and PM_PACK_RELEASENOTE_URL Keys to the UC_SYSTEM_SETTINGS Variable

To connect to the repository containing the release notes of the Packs and show the latest version of the Action Packs in the Packs view of the Administration Perspective, two keys must be defined in the UC_SYSTEM_SETTINGS variable. If the keys are not displayed, add them manually.

To Add the Keys

Log into client 0.
Open the UC_SYSTEM_SETTINGS variable.
Enter the pack release note key as described here: PM_PACK_RELEASENOTE_URL
Enter the index url key as described here: PM_INDEX_URL
Save your changes.

Tip: For more information, read the Working with Packs and Plug-ins topic.

Clear your Browser Cache Before Opening the Upgraded AWI/CDA

Microsoft Internet Explorer

Navigate to Internet Options > General > Browsing history.
Select Delete.
Deactivate the Preserve Favorites website data option.
Activate the Temporary Internet files and website files option.
Select Delete.

Firefox

Navigate to Options > Advanced.
Select the Network tab.
In the Cached Web Content section, select the Clear Now option.

Google Chrome

Select the Menu button in the upper-right corner.
Go to More Tools > Clear browsing data.
From the Obliterate the following items from drop-down list, select the beginning of time.
Select Clear browsing data.
Activate Browsing history, Cookies and other site & plug-in data, and Cached images and files.
Select Clear browsing data.

Important! Ensure that all your AWI/CDA users clear their browser cache before they start working with the upgraded AWI/CDA.

Next step:

Upgrading the Package Manager