Administer > HA Configuration > Configure the CSA node > Upgrade CSA on each CSA node

Upgrade CSA on each CSA node

To upgrade CSA, on each CSA node, do the following:

  1. If you are using the JRE that is installed with CSA (OpenJRE), back up the truststore
    (CSA_JRE_HOME/lib/security/cacerts) and/or the Apache load balancer/load balancer certificate outside of CSA_HOME.

    Because the JRE will be upgraded, the truststore is also upgraded. Any certificates you manually imported into the truststore will be lost unless you back up the truststore or the certificates. Do not re-use the truststore from the old version of the JRE (in case it contains public Certificate Authority certificates that are no longer trusted). Instead, you must export any root and/or self-signed certificates from the old truststore (certificates that you had manually imported into the old truststore) and import them into the new JRE truststore after running the upgrade installer.

  2. Upgrade CSA as described in the Cloud Service Automation Upgrade Guide with the following exceptions:

    • When running the upgrade installer, install CSA database components and upgrade the database schema on one and only one of the CSA nodes. It is recommended that you upgrade the schema on the first CSA node that you upgrade. Then, you do not need to install CSA database components and upgrade the database schema when you upgrade CSA on the other CSA nodes.

      Note All CSA nodes must connect to the same database schema. However, you only need to install CSA database components and upgrade the database schema once.

    • When running the upgrade installer, you must continue to use an external (existing) instance of Operations Orchestration. You cannot install or upgrade to use an embedded Operations Orchestration instance.

    • When running the upgrade installer, you cannot install the additional sample content. You can deploy the content after the upgrade has completed. See the Cloud Service Automation Content At a Glance Guide for information on how to manually deploy this content.

    • After running the upgrade installer, any references to the CSA_HOME/jboss-as/standalone/configuration/standalone.xml file in the Cloud Service Automation Upgrade Guide should be applied to the CSA_HOME/jboss-as/standalone/configuration/standalone-full-ha.xml file instead.

      For example, in CSA version 4.50, if you customized the host or ports in the standalone-full-ha.xml file, when you follow the instructions in the Recustomize Host and Ports section of the Cloud Service Automation Upgrade Guide, instead of updating the standalone.xml file, you should update the standalone-full-ha.xml file. If you do not remember the customizations you made to the file, see the backed up copy, CSA_HOME/_CSA_4_70_0_installation/Backup/standalone/standalone-full-ha.xml.

    • After upgrade to CSA 4.80.0002, if the initString value in the CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/hpssoConfig.xml file is detected to be the default value created during a previous installation of CSA, the initString value is regenerated as a security measure.

      If the external Operations Orchestration had not already been configured for SSO, the upgrade process will attempt to update the external Operations Orchestration’s SSO configuration with the new initString value generated during installation.

      Any other products that you had configured for SSO with CSA will need to be updated to share a common initString with CSA. After upgrade to CSA 4.80.0002, you should review and update, as needed, the SSO configuration in Operations Orchestration and other integrated products. For more information on configuring SSO between CSA and other products, see the Cloud Service Automation Configuration Guide.

  3. Follow the instructions in Configure CSA on each CSA node to configure after running the upgrade installer. Do not copy back files from an earlier version of CSA unless you are instructed to do so. Many components of CSA, such as the JRE, JBoss, and Identity Management component, have been updated and therefore, the configuration files have also been updated. Some files may have retained the information you configured in the previous version. However, you should verify all information in the upgraded files.

  4. Manually Backed up directories and content - all the files listed below must be backed up manually before upgrade:

    • CSA_HOME/jboss-as/standalone/deployments/csa.war/WEBINF/classes/csa.properties
    • CSA_HOME/jboss-as/standalone/deployments/csa.war/WEBINF/classes/swagger.properties
    • CSA_HOME/jboss-as/standalone/deployments/csa.war/WEBINF/applicationContext.xml
    • CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/applicationContext-security.xml
    • CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/flex/services-config.xml
    • CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/applicationContext.properties
    • CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEBINF/spring/applicationContext-saml.xml
    • CSA_HOME/jboss-as/standalone/deployments/mpp.war/index.html
    • CSA_HOME/jboss-as/standalone/configuration/*.*
    • CSA_HOME/portal/conf/mpp.json
    • CSA_HOME\jboss-as\bin\service.bat
    • CSA_HOME/elasticsearch-1.6.1/config/elasticsearch.yml
    • CSA_HOME/csa-search-service/app.json

Send Help Center feedback