ECC unpacking is missing most of the files in the configfolder

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

ECC unpacking is missing most of the files in the configfolder

Environment

Release: WAASER99000-1.0-Automic Workload Automation-Services
Component:

Resolution

Symptoms

When attempting an upgrade of the ECC, the .war package does not unpack the full listing of files within the config folder. After attempting execution, you receive the following error:

FAIL - Application at context path <ECCPATH> could not be started.

---

Cause

The previous installation of your ECC system is interfering with the installation of the upgrade.

---

Resolution

Perform the following steps:

1.) Backup your current installation for all configuration files.

2.) Enter into the Tomcat Manager (default <tomcat path>/manager/html).

3.) Undeploy any instances of the ECC ( Display Name - Automic Enterprise Control Center).

4.) Using the Tomcat Manager, deploy the new .war file. 

5.) Update the new system with your previous configuration

6.) Start the new system within the Tomcat Manager