Initial Setup

While performing the initial setup steps described in the Cloud Service Automation Upgrade Guide, you should also complete the following tasks:

1. Manually back up the following file outside of %CSA_HOME% (this file is not automatically restored nor backed up by the upgrade installer):

   <csa_jre>\lib\security\java.security

2. If you are upgrading from a CSA environment that is using an existing embedded Operations Orchestration, export the certificate from the truststore of Operations Orchestration as it is needed during the upgrade process. Do the following:

   1. Open a command prompt and navigate to a directory outside of the location where the embedded Operations Orchestration installation (for example, the embedded Operations Orchestration may be installed in C:\Program Files\HPE\Operations Orchestration\) AND outside of %CSA_HOME% in which you will store the certificate file (for example, create the directory C:\tmp and store the certificate file in this directory).

   2. Run the following command:

      "<csa_jre>\bin\keytool" ‑exportcert ‑keystore "C:\Program Files\HPE\Operations Orchestration\central\var\security\key.store" ‑alias tomcat ‑file .\<filename>

      where <csa_jre> is the directory in which the JRE that is used by CSA is installed. and <file_name> is a unique filename given to the certificate file that will be imported into CSA version 4.80.0002 later during the upgrade process.

3. If you are upgrading from CSA version 4.20, the JRE has been upgraded in this release. You must export the certificate from the truststore of CSA 4.20 so that you may import it (at a later time during the upgrade process) into the upgraded truststore of CSA.

   To export the certificate, do the following:

   1. Open a command prompt and navigate to a directory outside of %CSA_HOME% in which you will store the certificate file.

   2. Run the following command:

      "<csa_jre>\bin\keytool" ‑exportcert ‑keystore "%CSA_HOME%\jboss-as\standalone\configuration\keystore_csaID.p12" ‑alias <alias> ‑file .\<filename>

      where <csa_jre> is the directory in which the JRE that is used by CSA is installed., keystore_csaID.p12 is the keystore file defined by the certificate-key-file property of the connector attribute in %CSA_HOME%\jboss-as\standalone\configuration\standalone.xml, <alias> is the name used by the CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into CSA version 4.80.0002 later during the upgrade process.

      For example, run the following command if the JRE used by CSA version 4.20 is located in %CSA_HOME%\jre, the alias used to identify the certificate is csa, and the file the certificate is saved to is csa.cert:

      "%CSA_HOME%\jre\bin\keytool" ‑exportcert ‑keystore "%CSA_HOME%\jboss-as\standalone\configuration\keystore_csaID.p12" ‑alias csa ‑file .\csa.cert

4. Create a CSA encryption keystore password file. The name and location of this file must match the value configured for the keystorePasswordFile property in the %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\csa.properties file.

   The password file must contain only the following content:
   keystorePassword=<CSA encryption keystore password>

   where <CSA encryption keystore password> is the CSA encryption keystore password in clear text.

   This file is required to start/restart the CSA service and is automatically deleted when the CSA service is started.

   The upgrade installer automatically starts the CSA service upon completion.