HP Cloud Service Automation

For the Windows ® and Linux operating systems

Software Version: 4.01

Customized output from:

Upgrade Guide

Document Release Date: April 2014

Software Release Date: April 2014

HP logo

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2010-2014 Hewlett-Packard Development Company, L.P.

Trademark Notices

Adobe™ is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

RED HAT READY™ Logo and RED HAT CERTIFIED PARTNER™ Logo are trademarks of Red Hat, Inc.

This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.

 
 
 
 

Upgrade Guide

Overview

The HP Cloud Service Automation Upgrade Guide is an interactive document that provides the information necessary to upgrade your HP Cloud Service Automation (HP CSA) solution from version 4.00 to version 4.01, based on the information you supply.

Note: You can only upgrade from HP CSA version 4.00 to version 4.01. If you are running an earlier version, you must first upgrade to HP CSA version 4.00. Refer to the HP Cloud Service Automation Upgrade Guide for HP CSA version 4.00 for more information on how to upgrade to version 4.00.

You will need to supply the following information by selecting from the available options:

  • Operating system on which HP CSA is running
  • Database used by HP CSA
  • If this is a clustered system
  • If HP CSA is configured to be compliant with FIPS 140-2
  • System configuration (upgrading the Cloud Service Management Console or a remote Marketplace Portal)
  • Features configured

Note: If a selection is disabled (it cannot be selected), it is not a supported selection based on the other options you have selected. If a disabled selection is selected, choose an enabled selection instead. In some cases, there may be only one selection that can be enabled in a section.

For general information about HP Cloud Service Automation, see the HP Cloud Service Automation Concepts Guide.

For information about the supported components and versions, see the HP Cloud Service Automation Solution and Software Support Matrix.

Select from the options below and click View or Print to create a customized upgrade document. In this document, when available, detailed tasks are provided to complete the upgrade.

Select an operating system

Windows
Linux, Red Hat Enterprise
Linux, Ubuntu

Select the operating system of the server on which HP CSA is being upgraded.

Select a database

Oracle
Microsoft SQL Server
PostgreSQL

Select the database used by HP CSA.

If you are running Oracle RAC, you must undo your configuration changes to HP CSA before running the upgrade installer. Refer to Configuring HP CSA to Work with Oracle RAC for more information.

Select if the system is running in a clustered environment

Standalone environment
Clustered environment

Select the environment in which HP CSA is running.

Select if HP CSA is configured for FIPS 140-2 compliance

Not compliant with FIPS 140-2
Compliant with FIPS 140-2

Select if HP CSA is or is not compliant with FIPS 140-2.

Select the system configuration

I am upgrading a Cloud Service Management Console/Marketplace Portal
I am upgrading a remote Marketplace Portal

Select if you are upgrading a system running the Cloud Service Management Console and/or the Marketplace Portal or if you are upgrading a system running a remote Marketplace Portal.

Select configured features

Cloud Service Management Console properties
Cloud Service Management Console dashboard tile(s)
Cloud Service Management Console import large archives
Cloud Service Management Console session timeout
Cloud Service Management Console title
Cloud Service Management Console custom files
HP CSA tools
HP CSA seeded users
Marketplace Portal themes
Marketplace Portal widgets
ArcSight Logger
Common access card
Identity Management component
IPv6
Oracle RAC
Single sign-on
SiteMinder

Select the features that you configured for HP CSA (select only the features that were configured, customized, or used prior to upgrade). If you want to configure, customize, or use any of these features for the first time, after you have completed the upgrade, refer to one or more of the guides listed below.

For more information about the listed features, refer to one or more of the following guides:

  • HP Cloud Service Automation Configuration Guide
  • HP Cloud Service Management Console Help
  • HP Cloud Service Automation Content Archive Tool
  • HP Cloud Service Automation Provider Configuration Tool
  • HP Cloud Service Automation Customizing the Marketplace Portal
  • HP Cloud Service Automation Integration with ArcSight Logger
  • Configuring HP CSA to Work with Oracle RAC

View or Print

Click view or print.

Version: 4.01
Document Release Date: April 2014
Software Release Date: April 2014

Check your selections

The following steps are customized according to your selections. Check that your selections are correct.

 

If any selections are not correct, click Change.

Upgrade Overview


Caution: You have selected an unsupported configuration:

Linux (RHEL) (Ubuntu) and compliant with FIPS 140-2 (HP CSA does not support a system compliant with FIPS 140-2 running on Linux (RHEL)(Ubuntu)).

Click Change and update your selections.






Caution: You have selected an unsupported configuration:

OpenJDK JRE and compliant with FIPS 140-2 (HP CSA does not support a system compliant with FIPS 140-2 using the OpenJDK JRE).

Click Change and update your selections.






Caution: You have selected an unsupported configuration:

Oracle PostgreSQL database and compliant with FIPS 140-2 (HP CSA does not support a system compliant with FIPS 140-2 using an Oracle a PostgreSQL database).

Click Change and update your selections.






Caution: You have selected an unsupported configuration: a clustered environment and a remote Cloud Subscriber Portal instance (HP CSA does not support a remote Cloud Subscriber Portal instance in a clustered environment).

Click Change and update your selections.





Based on your selections from the previous page, you must perform the following steps. It is recommended that you perform each step in the following order:

  1. Review the Directories Affected by the Upgrade section below.
  2. Perform initial setup
  3. Run the HP CSA  4.01 upgrade installer.
  4. Update HP CSA.
  5. Recustomize HP CSA.
  6. Update HP CSA flows.
  7. Import service designs.
  8. Upgrade resource providers.
  9. Clear the Web browser cache.
  10. Start HP CSA.
  1. Review the Directories Affected by the Upgrade section below.
  2. Perform initial setup
  3. Run the HP CSA  4.01 upgrade installer.
  4. Update HP CSA.
  5. Recustomize HP CSA.
  6. Update HP CSA flows.
  7. Import service designs.
  8. Upgrade resource providers.
  9. Clear the Web browser cache.
  10. Start HP CSA.
  1. Back up HP CSA.
  2. Perform initial setup.
  3. Run the HP CSA  4.01 upgrade installer.
  4. Update HP CSA.
  5. Recustomize HP CSA.
  6. Start the HP Marketplace Portal service.

This guide provides information for upgrading HP Cloud Service Automation. Successful implementation requires knowledge of the integrated products, as well as HP Cloud Service Automation. Information in this guide augments information provided in the integrated products documentation but is not intended to replace that documentation. Primary product documentation contains the most up-to-date information. Cross references are provided to those documents where appropriate.This guide provides information for upgrading HP Cloud Service Automation. Successful implementation requires knowledge of HP Cloud Service Automation.

For information about HP CSA, see the HP Cloud Service Automation Concepts Guide. Review the HP Cloud Service Automation Solution and Software Support Matrix for version requirements.

Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Directories Affected by the Upgrade

When HP CSA is upgraded, new directories (and content) are added and existing directories (and content) are preserved, backed up, or updated. The following is a list of the affected directories (where %CSA_HOME%$CSA_HOME is the directory in which HP CSA is installed, such as C:\Program Files\Hewlett-Packard\CSA/usr/local/hp/csa). The information in this section applies to an upgrade of an installation of HP CSA running the Cloud Service Management Console/Marketplace Portal, not a remote Marketplace Portal installation.

New directories and content

  • %CSA_HOME%\_CSA_4_0_1_0_installation

Preserved directories and content

Preserved directories and content are not affected by the upgrade. If these directories existed before the upgrade, they are preserved during the upgrade, and remain on your system after the upgrade.

  • %CSA_HOME%\CSAKit
  • %CSA_HOME%\CSAKit-3.01
  • %CSA_HOME%\CSAKit-3.10
  • %CSA_HOME%\CSAKit-3.20
  • %CSA_HOME%\CSAKit-4.0
  • %CSA_HOME%\_CSA_3_0_0_installation
  • %CSA_HOME%\_CSA_3_0_1_installation
  • %CSA_HOME%\_CSA_3_1_0_installation
  • %CSA_HOME%\_CSA_3_2_0_installation
  • %CSA_HOME%\_CSA_4_0_0_installation
  • %CSA_HOME%\jre or
    %CSA_HOME%\openjre

Backed up directories and content

  • %CSA_HOME%\portal (backed up to %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal)
  • %CSA_HOME%\Tools (backed up to %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\Tools)
  • %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\*.war (backed up to %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\*.war)

  • %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\*.war (backed up to %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\*.war)

New directories and content

  • $CSA_HOME/_CSA_4_0_1_0_installation

Preserved directories and content

Preserved directories and content are not affected by the upgrade. If these directories existed before the upgrade, they are preserved during the upgrade, and remain on your system after the upgrade.

  • $CSA_HOME/CSAKit-3.10
  • $CSA_HOME/CSAKit-3.20
  • $CSA_HOME/_CSA_3_1_0_installation
  • $CSA_HOME/_CSA_3_2_0_installation
  • $CSA_HOME/_CSA_4_0_0_installation
  • $CSA_HOME/jre or
    $CSA_HOME/openjre

Backed up directories and content

  • $CSA_HOME/portal (backed up to $CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal)
  • $CSA_HOME/Tools (backed up to $CSA_HOME/_CSA_4_0_1_0_installation/Backup/Tools)
  • $CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/*.war (backed up to $CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/*.war)
  • $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/*.war (backed up to $CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/*.war)

Back Up HP CSA

Before you back up and upgrade your remote installation of the Marketplace Portal, on the system running the Cloud Service Management Console, upgrade to HP CSA 4.01, if you have not already done so.

On the remote system, do the following:

  1. Create a directory named C:\csabackup\. /tmp/csabackup/.

  2. Make a copy of %CSA_HOME%\portal\ $CSA_HOME/portal/ to C:\csabackup\. /tmp/csabackup/.

  3. Copy the following files to C:\csabackup\: /tmp/csabackup/:

    • %CSA_HOME%\jre\lib\security\cacerts $CSA_HOME/jre/lib/security/cacerts

    • %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml

  4. If you configured a new SSL certificate for this Marketplace Portal and want to continue using the same SSL certificate after upgrading to HP CSA 4.01, copy the following files to C:\csabackup\: /tmp/csabackup/:

    • %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\*.crt $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/*.crt

    • The keystore file defined by the certificate-key-file property of the connector attribute in %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml

      (for example, if certificate-key-file="C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\standalone\configuration\.keystore", copy C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\standalone\configuration\.keystore)
      $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml

      (for example, if certificate-key-file="/usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/configuration/.keystore", copy /usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/configuration/.keystore)

  5. Copy the JDBC drivers from the system running the Cloud Service Management Console (in %CSA_HOME%\jboss-as-7.1.1.Final\modules\com\oracle\ojdbc6\main\) $CSA_HOME/jboss-as-7.1.1.Final/modules/com/oracle/ojdbc6/main/) to the remote system (to a directory outside of the %CSA_HOME% $CSA_HOME directory). For example, copy ojdbc*.jar and ora*.jar to C:\csabackup\jdbc\. /tmp/csabackup/jdbc/.

Initial Setup

Before you run the upgrade installer, ensure the following steps are completed.

  • Verify that you have upgraded to the latest versions of software components required for HP CSA version 4.01. For example, for some resource providers, you may need to install a hotfix or service pack. See the HP Cloud Service Automation Solution and Software Support Matrix for the latest versions of software components required for HP CSA version 4.01.
  • Back up HP CSA 4.00 outside of %CSA_HOME%.$CSA_HOME. If you created custom files (for example, custom dashboard tiles) and saved them in a directory within the HP CSA 4.00 installation but not in a directory whose content is backed up by the upgrade installer, you must back up these files to preserve them. Otherwise, they will be deleted by the upgrade installer.

  • If it exists, back up the registry file (outside of %CSA_HOME%).$CSA_HOME). The registry file name and location is: C:\Program Files\Zero G Registry\com.zerog.registry.xml/home/csauser/com.zerog.registry.xml or /var/com.zerog.registry.xml

  • Back up the database.
  • If you have not already done so, back up the database used by HP CSA 4.00.

  • If you mounted a file system within the HP CSA installation directory (for example, within $CSA_HOME), you must unmount the file system. Otherwise, the upgrade will fail because the upgrade installer cannot remove the mounted file system during the upgrade.

  • The HP CSA upgrade installer requires that a supported JRE version is installed on the system and that JRE is configured in the system registry or the path to the JRE binaries (<jre_installation>\bin) is defined in the system path variable. and the path to the JRE binaries (<jre_installation>/bin) is defined in the system path variable. You may use the existing JRE used by HP CSA 4.00. A task in the next section explains how to set the system path variable.

    For a list of supported JRE versions, refer to the HP Cloud Service Automation Solution and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

  • Stop HP CSA:

    1. Open a command prompt and navigate to %CSA_HOME%\jboss-as-7.1.1.Final\bin.
    2. Run the following command:

      jboss-cli.bat --connect --command=:shutdown

    3. Close the command prompt.
    4. Navigate to Control Panel > Administrative Tools > Services.

    5. Right-click on the HP Marketplace Portal service and select Stop.

    1. Open a command prompt.
    2. Run the following commands:

      service csa stop
      service mpp stop

    3. Close the command prompt.
    Stop HP CSA on the master and slave nodes:

    1. Open a command prompt and navigate to %CSA_HOME%\jboss-as-7.1.1.Final\bin.
    2. Run the following command:

      jboss-cli.bat --connect --command=:shutdown

    3. Close the command prompt.
    4. Navigate to Control Panel > Administrative Tools > Services.

    5. Right-click on the HP Marketplace Portal service and select Stop.

    1. Open a command prompt and navigate to $CSA_HOME/jboss-as-7.1.1.Final/bin.
    2. Run the following commands:

      jboss-cli.sh --connect --command=:shutdown
      service mpp stop

    3. Close the command prompt.

  • Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.

Run the Upgrade Installer

Note: Upgrade log files are written to the %CSA_HOME%\_CSA_4_0_0_installation\Logs$CSA_HOME/_CSA_4_0_1_0_installation/Logs directory.

  1. Run the setup.exe upgrade file.
  2. On the Introduction screen, read the information and click Next.
  3. Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.
  4. Select the environment in which HP CSA is running. Based on the options you selected in this guide, select Standalone (HP CSA is running in a non-clustered environment) Cluster (HP CSA is running in a clustered environment) and click Next.

    This selection determines the file from which the database instance information is read. For example, if you select standalone, the database instance information is read from the JBoss server's standalone.xml file (%CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml). If you select cluster, the database instance information is read from the JBoss server's domain.xml file (%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\domain.xml).

  5. The installer detects if HP CSA is compliant with FIPS 140-2. The installer also detects if you are upgrading a master or slave node.

    If you are upgrading a master node, verify


    Verify
    the database instance information and click Next.

    If the upgrade installer could not find the database instance information, a message is displayed and you will need to re-enter the database information. Continue to the next screen to re-enter the database information and click Next to continue.

    If you are upgrading a slave node, you do not need to upgrade the database (this will be done when you upgrade the master node). Click Next.

  6. Enter the HP CSA database user password and click Next.

    If you are upgrading a slave node, this option is not available.

  7. Choose a location in which to install HP CSA and click Next (%CSA_HOME%$CSA_HOME is set to this location).

    The default location is C:\Program Files\Hewlett-Packard\CSA.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

  8. Define the database instance where the HP CSA database schema already exists. Enter the database information and click Next.

    Field Name Description
    Database Type

    The type of database you have installed.

    For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you backed up from the system running the Cloud Service Management Console to the remote system, for example, to C:\csabackup\jdbc\). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation Solution and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport). Click Choose to select the directory.

    Database Name The name of the database instance on which the HP CSA database schema exists. For an Oracle database, this is the System ID (SID).
    Database Host The hostname or IP address of the server where the database is located.
    Database Port The database port number, such as 143315215432.
    Database Username The user name of the database user you configured for HP CSA after installing the database.
    Database Password The password for the database user.
  9. Select Yes to install HP CSA database components and upgrade the HP CSA database schema then click Next. Because you are upgrading only the Marketplace Portal on a remote system, click No, do not install database components as you are using an existing HP CSA database schema.

    If you are upgrading a slave node, this option is not available. The database schema is upgraded when you upgrade the master node.

  10. From the Enter host name screen, enter the fully-qualified domain name of the remote system on which you are installing the Marketplace Portal. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.
  11. Review your selections and click Install to complete the upgrade.
  12. Click Done to exit the installer.
  1. Log in to the system as the root user.
  2. Check the owner and group of $CSA_JRE_HOME/lib/security/cacerts, where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

    If the owner is not csauser or the group is not csagrp, reset the owner or group. For example, enter the following:

    chown csauser:csagrp $CSA_JRE_HOME/lib/security/cacerts

  3. Log out as the root user and log in as csauser.
  4. For the csauser user, define the CSA_HOME environment variable and add the JRE installation directory to the PATH variable. If not already defined, set CSA_HOME to the location where HP CSA 4.01 will be installed (the upgrade installer uses this location to install HP CSA 4.01). In a startup script for the csauser user (for example, .bash_profile.bashrc), add the following:

    export CSA_HOME=/usr/local/hp/csa
    export PATH=$PATH:$CSA_JRE_HOME

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed (for example, export PATH=$PATH:$CSA_HOME/jre/bin).

  5. Source the startup file in which you set the CSA_HOME and PATH environment variables. If you edited .bash_profile.bashrc, enter the following:

    .bash_profile.bashrc

  6. Copy the HP CSA upgrade file (setup.bin) to the system and go to the directory in which it has been copied.
  7. Verify that setup.bin is owned by csauser and csauser has full permissions to the file. If necessary, do the following:

    1. Log in as the root user
    2. Enter the following commands:

      chown csauser setup.bin
      chmod 755 setup.bin

    3. Log out as the root user and log in as csauser.
  8. Run the setup.bin upgrade file (as the csauser).

    Note: You must run setup.bin as the csauser. If you install HP CSA as another user, you may not be able to run HP CSA.

    As the csauser, enter the following:

    ./setup.bin

  9. Read the Introduction and click enter to continue with the installation.

  10. Read the license agreement. Click enter to scroll through the entire agreement.
  11. Select Y and enter to accept the license agreement and continue with the installation. Type N and enter to exit the installation.
  12. Select the environment in which HP CSA is running. Based on the options you selected in this guide, select 1 for standalone (HP CSA is running in a non-clustered environment) 2 for cluster (HP CSA is running in a clustered environment) and click enter.

    This selection determines the file from which the database instance information is read. For example, if you select standalone, the database instance information is read from the JBoss server's standalone.xml file ($CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml). If you select cluster, the database instance information is read from the JBoss server's domain.xml file ($CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml).

  13. The installer detects if HP CSA is compliant with FIPS 140-2. The installer also detects if you are upgrading a master or slave node.

    If you are upgrading a master node, verify


    Verify
    the database instance information and click Next.

    If the upgrade installer could not find the database instance information, a message is displayed and you will need to re-enter the database information. Continue to the next screen to re-enter the database information and click enter to continue.

    If you are upgrading a slave node, you do not need to upgrade the database (this will be done when you upgrade the master node). Only the file system is upgraded. Click enter.

  14. Enter the HP CSA database user password and click enter.

    If you are upgrading a slave node, this option is not available.

  15. Install or upgrade the HP CSA database components.

    Type yes and enter to upgrade the HP CSA database components and schema.

    Type no and enter if you are referencing a database that has already been upgraded to version 4.01.

    If you are upgrading a slave node, this option is not available.

  16. Review your selections and click enter to complete the installation or ctrl-c to exit the installation.

  17. When the installation completes, click enter to exit the installer.

  18. Upgrade the HP CSA service to start and stop the HP CSA process and add the Marketplace Portal service to start and stop the Marketplace Portal process.

    1. Log in as the root user.
    2. Remove the old version of the HP CSA scripts. Enter the following:

      rm /etc/init.d/csa
      rm /etc/init.d/mpp

    3. Go to the directory in which HP CSA is installed. For example:

      cd /usr/local/hp/csa

    4. Copy the new csa and mpp scripts to the /etc/init.d directory. Enter the following:

      cp ./scripts/csa /etc/init.d
      cp ./scripts/mpp /etc/init.d

    5. Change permissions of the scripts. Enter the following:

      chmod 755 /etc/init.d/csa
      chmod 755 /etc/init.d/mpp

Update HP CSA

Complete the following tasks:

Remove Directories and Files

Go to the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments %CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deploymentsr $CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments and remove the following directories (including subdirectories and all of its content) and files (if present):

  • csa.war
  • csa.war.deployed or csa.war.dodeploy
  • csa-provider-help.war
  • csa-provider-help.war.deployed or csa-provider-help.war.dodeploy
  • idm-service.war
  • idm-service.war.deployed or idm-service.war.dodeploy

Configure the Marketplace Portal

The remote instance of the Marketplace Portal must be configured to use the system on which HP CSA and the Identity Management component is installed. Do the following:

  1. Edit the %CSA_HOME%\portal\conf\mpp.json $CSA_HOME/portal/conf/mpp.json file.

  2. Update the url attribute value in the provider section. Enter the URL to the system on which HP CSA is installed. Use the fully-qualified domain name of the system. For example, https://csa_system.xyz.com:8444.
  3. Update the url attribute value in the idmProvider section. Enter the URL to the system on which the Identity Management component is installed. Use the fully-qualified domain name of the system. For example, https://csa_system.xyz.com:8444.
  4. If you changed the password for the idmTransportUser on the system on which HP CSA is installed, update the password attribute value in the idmProvider section for the Marketplace Portal.

    Encrypt the password by doing the following:

    1. Open a command prompt and change to the %CSA_HOME%\portal\bin$CSA_HOME/portal/bin directory. For example:

      C:\Program Files\Hewlett-Packard\CSA\portal\bin/usr/local/hp/csa/portal/bin

    2. Run the following command:

      passwordUtil

      When prompted, enter the key file name and location (for example, ../conf/.mpp_keystore../conf/.mpp_keystore cloud) and the password to encrypt.

    3. An encrypted password is displayed. Copy the encrypted password to the password attribute value. An encrypted password is preceded by ENC without any separating spaces and is enclosed in parentheses. For example ENC(3oKr7eAo25bEn3Zn2t9wIA==)

  5. Save and exit the file.

Restore cacerts

Restore C:\csabackup\cacerts /tmp/csabackup/cacerts to <csa_jre>\lib\security\cacerts <csa_jre>/lib/security/cacerts (overwrite the existing file) where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

Restore or Import SSL Certificate Files

If you backed up your SSL certificate files, do the following:

  1. Merge any changes you made in the HP CSA 3.20 standalone.xml domain.xml standalone.xml file (backed up in C:\csabackup\standalone.xml) C:\csabackup\domain.xml) /tmp/csabackup/standalone.xml) to %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml. %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\domain.xml. $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml.

  2. Restore your SSL certificate files from C:\csabackup\ /tmp/csabackup/ to the following directories (overwrite any existing files):

    • %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\*.crt %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\*.crt $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/*.crt

    • The keystore file defined by the certificate-key-file property of the connector attribute in %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\domain.xml $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml (for example, if certificate-key-file="C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml", restore C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml) restore C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\domain\configuration\domain.xml") certificate-key-file="/usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml", restore /usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml)

If you did NOT back up your SSL certificate files, import the SSL certificate (created by HP CSA 4.01 during installation) as a trusted certificate. Run the following commands:

cd %CSA_HOME% cd $CSA_HOME

"<csa_jre>\bin\keytool.exe" -importcert -trustcacerts -alias <alias> -file .\jboss-as-7.1.1.Final\standalone\configuration\jboss.crt -keystore "<csa_jre>\lib\security\cacerts" -storepass changeit "<csa_jre>\bin\keytool.exe" -importcert -trustcacerts -alias <alias> -file .\jboss-as-7.1.1.Final\domain\configuration\jboss.crt -keystore "<csa_jre>\lib\security\cacerts" -storepass changeit <csa_jre>/bin/keytool.exe" -importcert trustcacerts -alias <alias> -file ./jboss-as-7.1.1.Final/standalone/configuration/jboss.crt -keystore <csa_jre>/lib/security/cacerts -storepass changeit

where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

If you receive a message that the certificate already exists, you do not need to import the certificate again.

Delete the Sample Consumer Organization

If you deleted the sample consumer organization on your HP CSA 4.00 system, you should delete the sample consumer organization (if it still exists) if you are no longer using it, if you are moving the application to production, or if you are upgrading a production system. See the HP Cloud Service Automation Configuration Guide for more information if you are deleting this organization for the first time.

Recustomize HP CSA

You must recustomize HP CSA for the features configured, customized, or used prior to the upgrade (complete only the tasks for features that were configured, customized, or used prior to upgrade; if you want to configure, customize, or use any of these features for the first time, refer to the following guides for more information: HP Cloud Service Automation Configuration Guide, Configuring an HP CSA Cluster for Server Failover, HP Cloud Service Management Console Help, HP Cloud Service Automation Content Archive Tool, HP Cloud Service Automation Provider Configuration Tool, HP Cloud Service Automation Customizing the Marketplace Portal, HP Cloud Service Automation Integration with ArcSight Logger, Configuring HP CSA to Work with Oracle RAC. If you did not select any features from the selection page, this section may be empty.

Configure a Clustered Environment

The following is a list of files that you may have customized when configuring a clustered environment. If you symbolically linked a shared file system for HP CSA in your clustered environment (such as for sharing a common resource for images), you will need to recreate the link. Refer to the Update Shared Filesystem Resources (Master Node) and Update Shared Filesystem Resources (Slave Node) sections below for more information. Otherwise, no additional actions are required when you upgrade HP CSA in a clustered environment.

File Action
applicationContext-common.xml No action required.
domain.xml No action required.
host.xml No action required.
web.xml No action required.

Files, Actions, and Locations

  • applicationContext-common.xml
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • domain.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • host.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • web.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

Update Shared Filesystem Resources (Master Node)

Configure HP CSA to share filesystem resources to free up disk space (this task is optional). Static filesystem resources, such as images, can be stored on one system and shared by all nodes in the cluster. The following example shows how to share the images directory that is installed with each instance of HP CSA.

HP CSA provides images that are stored in an images directory (for example, %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images). From the Cloud Service Management Console, you may also upload images which are saved to the same images directory. You can store these images on a shared filesystem on a network and the images on this single shared filesystem can be used by all nodes in the cluster.

To configure HP CSA to use a shared filesystem to store images, do the following:

  1. Create a shared filesystem on the network. The master and slave nodes must be able to read and write to the shared location.
  2. Map the shared location as a network drive. For example, map S:\CSA on the master node to the shared location.

    Mount the shared location. For example, mount the shared location to /mnt/csa by typing mount -t cifs -o username=<user>, password=<pass> //sharedhost/CSA/ /mnt/csa

  3. Move the %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images directory to the shared location (for example, S:\CSA\images/mnt/csa/images).

    Ensure that the mapped mounted images directory is readable and writeable.

  4. Delete the %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images directory from the master and slave nodes.

  5. Create a symbolic link to the mapped mountedimages directory. For example, from a command prompt, type the following commands:

    cd %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war
    mklink /d images "S:\CSA\images"

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    ln -s /mnt/csa/images images

  6. Set the permissions and ownership for the images directory. Type the following:

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    chmod 755 images
    chown csauser:csagrp images

Update Shared Filesystem Resources (Slave Node)

Configure HP CSA to share filesystem resources to free up disk space (this task is optional). If you have not done so already, configure a shared filesystem resource from the master node.

The following example configures the images directory as a shared filesystem, using the shared images directory that you set up when you configured the master node (%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images).

To configure HP CSA to use a shared filesystem to store images, do the following:

  1. Map the shared location as a network drive. For example, map S:\CSA on the slave node to the shared location.

    Mount the shared location. For example, mount the shared location to /mnt/csa by typing mount -t cifs -o username=<user>, password=<pass> //sharedhost/CSA/ /mnt/csa

  2. Delete the %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images directory.

  3. Create a symbolic link to the mapped mountedimages directory. For example, from a command prompt, type the following commands:

    cd %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war
    mklink /d images "S:\CSA\images"

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    ln -s /mnt/csa/images images

  4. Set the permissions and ownership for the images directory. Type the following:

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    chmod 755 images
    chown csauser:csagrp images

Configure the Cloud Service Management Console Properties

The following is the file that you may have customized for the Cloud Service Management Console and the actions required when you upgrade HP CSA:

FileAction
csa.propertiesNo action required.

File, Actions, and Locations

  • csa.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/classes/

Recustomize the Cloud Service Management Console Dashboard

The following is a list of files that you may have customized for the Cloud Service Management Console dashboard and the actions required when you upgrade HP CSA:

FileAction
*.jspRequired. Manually copy the JSP files from the backup directory to the appropriate directory in HP CSA 4.01 directory (see table below for more information).
config.jsonRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).
messages.propertiesRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • *.jsp
    Action

    Required. If you created custom Java server page (JSP) files for the HP CSA dashboard and saved them in a directory within the HP CSA 4.00 installation but not in a directory whose content is backed up by the upgrade installer, you should have backed up these files to preserve them. Otherwise, they will be deleted by the upgrade installer. Manually copy the JSP files from the backup directory to the appropriate directory in HP CSA 4.01 directory.

    File Location in HP CSA 4.01

    The directory where the Cloud Service Management Console expects to find these files, defined in the config.json dashboard configuration file.

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    The directory to which the JSP files were backed up, either manually or by the upgrade installer, depending on where the files were located in HP CSA 4.00.

  • config.json
    ActionRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\dashboard\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/dashboard/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\dashboard\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\dashboard\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/dashboard/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/dashboard/

  • messages.properties
    ActionRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\dashboard\messages\common\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\common\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/dashboard/messages/common/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/common/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\dashboard\messages\common\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\dashboard\messages\common\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/dashboard/messages/common/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/dashboard/messages/common/

Configure the Cloud Service Management Console to Import Large Archives

The following is the file that you customized to import large archives using the Cloud Service Management Console or REST API and the actions required when you upgrade HP CSA:

FileAction

standalone.conf.batstandalone.conf

Required. If this file was customized, you must recustomize this file (see table below for more information).

File, Action, and Locations

  • standalone.conf.batstandalone.conf

    ActionRequired. If this file was customized, you must recustomize this file. Refer to Import Large Archives from the Cloud Service Management Console or through the REST API section in this guide for information on how to complete the recustomization.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\bin\$CSA_HOME/jboss-as-7.1.1.Final/bin/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/

Import Large Archives from the Cloud Service Management Console or through the REST API

If you want to import an archive larger than 1.5 MB, HP recommends using the Content Archive Tool. If you must use the Cloud Service Management Console or REST API to import a large archive, you must update the JVM heap size for HP CSA which requires HP CSA to be restarted. Also, importing a large archive from the Cloud Service Management Console or through the REST API may slow the performance of HP CSA.

To increase the JVM heap size before importing a large archive from the Cloud Service Management Console or through the REST API, do the following:

  1. Increase the JVM heap size for HP CSA.

    1. Open the %CSA_HOME%\jboss-as-7.1.1.Final\bin\standalone.conf.bat $CSA_HOME/jboss-as-7.1.1.Final/bin/standalone.conf file in a text editor.

    2. Locate the following line:

      set "JAVA_OPTS=%JAVA_OPTS%$JAVA_OPT -Xms1024M -Xmx1024M -XX:PermSize=256M
      -XX:MaxPermSize=256M"

    3. Increase the JVM heap size (by default, the JVM heap size is 1 GB). For example, to change the JVM heap size to 2 GB, change the line to:

      set "JAVA_OPTS=%JAVA_OPTS%$JAVA_OPT -Xms2048M -Xmx2048M -XX:PermSize=256M
      -XX:MaxPermSize=256M"

    4. Save and close the file.

For more information about importing archives from the Cloud Service Management Console, refer to the HP Cloud Service Management Console Help. For more information about importing archives through the REST API, refer to the HP CSA API Reference guide.

Recustomize the Cloud Service Management Console Session Timeout

The following file may have been customized if you updated the Cloud Service Management Console session:

FileAction
web.xmlRequired. No action required.

File, Action, and Locations

  • web.xml
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

Recustomize the Cloud Service Management Console Dashboard Title

The following file may have been customized if you updated the Cloud Service Management Console dashboard title:

FileAction
messages.propertiesRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).

File, Action, and Locations

  • messages.properties
    ActionRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\custom\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\custom\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/custom/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/custom/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\custom\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\custom\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/custom/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/custom/

Add Custom Graphic Files or Dynamic Query Scripts

The following is a list of custom files that you may have added and the actions required when you upgrade HP CSA:

FileAction
*.jpg, *.jpeg, *.gif, *.pngRequired. Manually copy any custom files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
*.jsp (dynamic query scripts)Required. Manually copy any custom dynamic query scripts from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • *.jpg, *.jpeg, *.gif, *.png
    ActionRequired. Manually copy any custom files from the backup directory to the HP CSA 4.01 directory. Custom files may include organization logos or images for provider types, categories, component palettes, component types, service designs, subscriber options, tags, service offerings, or catalogs.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\images\library\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images\library\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/images/library/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images/library/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\images\library\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\images\library\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/images/library/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/images/library/

  • *.jsp (dynamic query scripts)
    ActionRequired. Manually copy any custom dynamic query scripts from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\propertysources\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\propertysources\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/propertysources/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/propertysources/

Recustomize the HP CSA Tools

The following is a list of files that you may have customized if you ran any of the HP CSA tools and the actions required when you upgrade HP CSA:

FileAction
config.properties (content archive tool, purge tool, provider configuration tool)Required. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
db.properties (process definition tool, schema installation tool)Required. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
HPOOInfoInput.xml (process definition tool)Required. Manually copy any custom input files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
provider.xml (provider configuration tool)Required. Manually copy any custom input files from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • config.properties
    ActionRequired. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the configuration file used in some examples for the content archive tool, purge tool, and provider configuration tool. If you used a different name for the configuration file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ContentArchiveTool\
    %CSA_HOME%\Tools\db-purge-tool\
    %CSA_HOME%\Tools\ProviderTool\
    $CSA_HOME/Tools/ContentArchiveTool/
    $CSA_HOME/Tools/db-purge-tool/
    $CSA_HOME/Tools/ProviderTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ContentArchiveTool\
    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\db-purge-tool\
    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProviderTool\
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/ContentArchiveTool/
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/db-purge-tool/
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProviderTool/

  • db.properties
    ActionRequired. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the configuration file used in some examples for the process definition tool and schema installation tool. If you used a different name for the configuration file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ProcessDefinitionTool\
    %CSA_HOME%\Tools\SchemaInstallationTool\
    $CSA_HOME/Tools/ProcessDefinitionTool/
    $CSA_HOME/Tools/SchemaInstallationTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProcessDefinitionTool\
    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\SchemaInstallationTool\
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProcessDefinitionTool/
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/SchemaInstallationTool/

  • HPOOInfoInput.xml
    ActionRequired. Manually copy any custom input files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the input file used in some examples for the process definition tool. If you used a different name for the input file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ProcessDefinitionTool\$CSA_HOME/Tools/ProcessDefinitionTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProcessDefinitionTool\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProcessDefinitionTool/

  • provider.xml
    ActionRequired. Manually copy any custom provider input files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the input file used in some examples for the provider configuration tool. If you used a different name for the provider input file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ProviderTool\$CSA_HOME/Tools/ProviderTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProviderTool\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProviderTool/

Recustomize the HP CSA Seeded Users

The following is a list of files that you may have customized if you updated the password of one or more seeded users and the actions required when you upgrade HP CSA:

FileAction
applicationContext-security.xml

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

csa-consumer-users.properties

Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).No action required.

applicationContext.properties

No action required.

standalone.xmldomain.xml

No action required.Required. Manually copy the file from your backup to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • applicationContext-security.xml
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • csa-consumer-users.properties
    Action

    Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory.No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/classes/

  • applicationContext.properties
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • standalone.xmldomain.xml

    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.Required. Manually copy the file from your backup to the HP CSA 4.01 directory.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

Add Marketplace Portal Themes

The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade HP CSA:

DirectoryAction
<theme_directory>

Required. If you created a customized theme for the Marketplace Portal, you must manually copy these directories (one for the Marketplace Portal and one for the Identity Management component and their)this directory (for the Marketplace Portal and its) content from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Directories, Actions, and Locations

  • <theme_directory> (Marketplace Portal)
    ActionRequired. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\themes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/

  • <theme_directory> (Identity Management Component)
    Action

    Required. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the HP CSA 4.01 directory. This theme is used to customize the login page.No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\themes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\themes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/themes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/themes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\themes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\themes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/themes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/themes/

Add Marketplace Portal Widgets

The following is the directory where you may have added customized widgets for the Marketplace Portal and the action required when you upgrade HP CSA:

DirectoryAction
<iFRAME_URL_structure>Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Directory, Action, and Locations

  • <iFRAME_URL_structure>
    ActionRequired. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\$CSA_HOME/portal/node_modules/mpp-ui/dist/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/

Configure ArcSight Logger

The following is the file that you may have customized if you integrated with the ArcSight Logger and the actions required when you upgrade HP CSA:

FileAction
log4j.propertiesNo action required.

File, Actions, and Locations

  • log4j.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/classes/

Integrate HP CSA with a Common Access Card

The following is a list of files that you customized when integrating HP CSA with a Common Access Card (CAC) and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext.xml (Identity Management component)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Identity Management component)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

rb.jsonRequired. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)Required. If this file was customized, you must recustomize this file (see table below for more information).
standalone.xmlNo action required.
java.securityNo action required.

Files, Actions, and Locations

  • applicationContext.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • applicationContext-security.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • rb.json
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

  • main.css (default)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\default\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/default/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\default\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/default/styles/

  • main.css (pilot)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\pilot\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\pilot\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

  • main.css (<theme_directory>)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • java.security
    ActionNo action required. The file is preserved. Any changes made to this file are retained after the upgrade is completed.
    File Location in HP CSA 4.01

    <csa_jre>\lib\security\<csa_jre>/lib/security/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    This file is not backed up.

Configure HP CSA for FIPS 140-2 Compliance

The following is a list of files that you may have customized for FIPS 140-2 compliance and the actions required when you upgrade HP CSA:

FileAction
*.p12Required. Manually copy the keystore and truststore that support PKCS #12 used by HP CSA from the backup directory to the HP CSA 4.01 directory (see table below for more information).
applicationContext.xmlRequired. If this file was customized, you must recustomize this file (see table below for more information).
node.exeRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.

standalone.xmldomain.xml

No action required.
idm-service.propertiesNo action required.
java.securityNo action required.

Files, Actions, and Locations

  • *.p12
    ActionRequired. Manually copy the keystore and truststore that support PKCS #12 used by HP CSA from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\security\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\security\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/security/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/security/

  • applicationContext.xml
    ActionRequired. This file must be recustomized. Refer to Update applicationContext.xml to be FIPS 140-2 Compliant for information on how to complete the recustomization.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • node.exe
    ActionRequired. Customizations made to this file in HP CSA 4.00 are preserved in the file located in the backup directory. Make a copy of this file in the HP CSA 4.01 directory and then manually overwrite the installed file using the file from the backup directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\node.js\$CSA_HOME/node.js/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\node.js\bin\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/node.js/bin/

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • idm-service.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/classes/

  • java.security
    ActionNo action required. The file is preserved. Any changes made to this file are retained after the upgrade is completed.
    File Location in HP CSA 4.01

    <csa_jre>\lib\security\<csa_jre>/lib/security/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    This file is not backed up.

Update applicationContext.xml to be FIPS 140-2 Compliant

  1. Open the %CSA_HOME%\jboss-as-7.1.1.Final\
    standalone\deployments\csa.war\WEB-INF\applicationContext.xml
    $CSA_HOME/jboss-as-7.1.1.Final/
    standalone/deployments/csa.war/WEB-INF/applicationContext.xml
    file in a text editor. For example, edit the following file:

    C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\
    standalone\deployments\csa.war\WEB-INF\applicationContext.xml
    /usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/
    deployments/csa.war/WEB-INF/applicationContext.xml

  2. Locate the START Standard Mode Configuration comment and comment out the following content that appears between the START Standard Mode Configuration and END Standard Mode Configuration comments:

    <bean id="simpleEncryptionConfiguration" class="com.hp.csa.security.CSASimplePBEConfig" init-method="init">
    </bean>

    <bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
      <property name="config" ref="simpleEncryptionConfiguration" />
    </bean>

    <bean id="propertyConfigurer" class="org.jasypt.spring.properties.
    EncryptablePropertyPlaceholderConfigurer">
      <constructor-arg ref="configurationEncryptor" />
      <property name="locations">
        <list>
          <value>classpath:csa.properties</value>
        </list>
      </property>
    </bean>

  3. Locate the START FIPS Mode Configuration comment and uncomment the following content that appears between the START FIPS Mode Configuration and END FIPS Mode Configuration comments:

    <bean id="configurationEncryptor" class="com.hp.csa.security.util.CSASecurityHelper" />

    <bean id="propertyConfigurer" class=
    "com.hp.csa.security.CSAEncryptablePropertyPlaceholderConfigurer">
      <constructor-arg ref="configurationEncryptor" />
      <property name="locations">
        <list>
          <value>classpath:csa.properties</value>
        </list>
      </property>
    </bean>

  4. Save and close the file.

Configure the Identity Management Component

The following is a list of files that you may have customized for the Identity Management component and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml (Identity Management component)Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext.propertiesNo action required.
applicationContext-common.xmlNo action required.
idm-service.propertiesNo action required.

Files, Actions, and Locations

  • applicationContext.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • applicationContext.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • applicationContext-common.xml
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • idm-service.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/classes/

Configure IPv6

The following is the file that you may have customized if you configured IPv6 and the actions required when you upgrade HP CSA:

FileAction

standalone.xmldomain.xml

No action required.

File, Actions, and Locations

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

Configure Oracle RAC

The following is the file that you may have customized if you configured Oracle RAC and the actions required when you upgrade HP CSA:

FileAction

standalone.xmldomain.xml

No action required.

File, Actions, and Locations

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

Configure HP CSA to Use a Single Sign-On

The following is a list of files that you customized when configuring HP CSA to use a single sign-on (SSO) and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

rb.jsonRequired. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)Required. If this file was customized, you must recustomize this file (see table below for more information).

Files, Actions, and Locations

  • applicationContext.xml
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • rb.json
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

  • main.css (default)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\default\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/default/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\default\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/default/styles/

  • main.css (pilot)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\pilot\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\pilot\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

  • main.css (<theme_directory>)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

Integrate HP CSA with CA SiteMinder

The following is a list of files that you customized when integrating HP CSA with SiteMinder and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

ssologout.jsp

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Identity Management component)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

rb.jsonRequired. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)Required. If this file was customized, you must recustomize this file (see table below for more information).
web.xmlNo action required.

Files, Actions, and Locations

  • applicationContext.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • ssologout.jsp
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • rb.json
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

  • main.css (default)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\default\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/default/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\default\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/default/styles/

  • main.css (pilot)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\pilot\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\pilot\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

  • main.css (<theme_directory>)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

  • web.xml
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

Delete the Sample Consumer Organization

If you deleted the sample consumer organization on your HP CSA 4.00 system, you should delete the sample consumer organization (if it still exists) if you are no longer using it, if you are moving the application to production, or if you are upgrading a production system. See the HP Cloud Service Automation Configuration Guide for more information if you are deleting this organization for the first time.

Update the HP Operations Orchestration 10 Integration Pack Exclusion File

If you upgrade HP Operations Orchestration 10, copy this file to exclude HP CSA content from being upgraded.

Copy the %CSA_HOME%\CSAKit-4.01\OO Flow Content\oo10-csa-cp-uuids.txt$CSA_HOME/CSAKit-4.01/OO Flow Content/oo10-csa-cp-uuids.txt file to (replace the file if it already exists):

Windows
%ICONCLUDE_HOME%\central\cmu\exclusions\

Linux
$ICONCLUDE_HOME/central/cmu/exclusions\

where %ICONCLUDE_HOME% or $ICONCLUDE_HOME is where you installed HP Operations Orchestration.

Upgrade Shortcuts

If you created HP CSA shortcuts in the default directory (for example, C:\Users\<user>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Hewlett-Packard\Cloud Service Automation), these shortcuts are automatically upgraded. If you created HP CSA shortcuts and saved them to another directory other than the default directory (for example, in a Program Group, in the Start Menu, on the desktop, or in the Quick Launch Bar), you should delete these shortcuts as they will no longer work. Optionally, you can change the target of the shortcuts to %CSA_HOME%\_CSA_4_0_1_0_installation\Change HP Cloud Service Automation Installation.exe.

Marketplace Portal Configuration

If you customized the Marketplace Portal configuration file, the customizations have been merged with the upgraded file. Refer to the HP Cloud Service Automation Configuration Guide for more information about the configurable properties in this file.

FileAction
node.exeRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.No action required.
mpp.jsonNo action required. If this file was customized, the customizations have been merged with the upgraded file.

Files, Actions, and Locations

  • node.exe
    ActionRequired. Customizations made to this file in HP CSA 4.00 are preserved in the file located in the backup directory. Make a copy of this file in the HP CSA 4.01 directory and then manually overwrite the installed file using the file from the backup directory.No action required.
    File Location in HP CSA 4.01

    %CSA_HOME%\node.js\$CSA_HOME/node.js/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\node.js\bin\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/node.js/bin/

  • mpp.json
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\portal\conf\$CSA_HOME/portal/conf/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\conf\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/conf/

Start the  Marketplace Portal Service

To start the  Marketplace Portal service:

  1. On the system running the remote Marketplace Portal, navigate to Control Panel > Administrative Tools > Services.

  2. Start the HP Marketplace Portal service.

  3. On the system running the remote Marketplace Portal, type service mpp start.

Update HP CSA

The following tasks must be completed before HP CSA can be restarted:

Recustomize SSL/Security

If you generated or copied SSL certificates that are used by HP CSA, you must copy these files to the appropriate directory in HP CSA 4.01.

Note: If the automatically generated self-signed certificate for HP CSA has expired, you may still be able to use the Cloud Service Management Console. However, you will not be able to use the Marketplace Portal or Identity Management component unless you disable the strictSSL attribute in the Marketplace Portal's configuration file. If SSL must be enabled, you can generate another self-signed certificate or a Certificate Authority-signed certificate. If you generate a new certificate, you MUST import that certificate into HP CSA's JRE. Refer to the Configure SSL for Client Browsers section in the HP Cloud Service Automation Configuration Guide for more information.

The following is a list of files that you may have customized for SSL/security and the actions required when you upgrade HP CSA:

File Action
certificate files Required. Manually copy certificate files that do not use the .crt extension that are used by HP CSA from the backup directory to the HP CSA 4.01 directory (see table below for more information).

standalone.xmldomain.xml

No action required.
cacerts No action required.

Keystore file defined by the certificate-key-file property of the connector attribute in standalone.xmldomain.xml

No action required.

Files, Actions, and Locations

  • certificate files
    Action Required. Manually copy certificate files that do not use the .crt extension that are used by HP CSA from the backup directory to the HP CSA 4.01 directory. Files that use the .crt extension are automatically restored. If you saved .crt files in a different directory, you must manually copy these files back after upgrade.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\security\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\security\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/security/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/security/

  • standalone.xmldomain.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • cacerts
    Action No action required. The file is preserved. Any changes made to this file are retained after the upgrade is completed.
    File Location in HP CSA 4.01

    <csa_jre>\lib\security\<csa_jre>/lib/security/

    where <csa_jre> is the directory in which the JRE (used exclusively by HP CSA) is installed.

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01 This file is not backed up.
  • Keystore file defined by the certificate-key-file property of the connector attribute in standalone.xmldomain.xml
    Action No action required. The file defined by certificate-key-file is backed up and preserved. Any changes made to this file are retained after the upgrade is completed.
    File Location in HP CSA 4.01

    The file and its location are determined by the value defined by certificate-key-file. By default, the value is C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\standalone\configuration\.keystoreC:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\domain\configuration\.keystore/usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/configuration/.keystore/usr/local/hp/csa/jboss-as-7.1.1.Final/domain/configuration/.keystore

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\security\keystores\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\security\keystores\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/security/keystores/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/security/keystores/

Recustomize Manually Configured Files

If you customized HP CSA files that are not documented as being customizable, you will need to manually recustomize those files. Files that have been documented as being customizable are listed in the following sections in this guide: Update HP CSA and Recustomize HP CSA.

Remount Shared File Systems

If you unmounted one or more shared file systems within the HP CSA installation directory before running the upgrade installer, remount these file systems after the upgrade installer has completed.

Recustomize HP CSA

You must recustomize HP CSA for the features configured, customized, or used prior to the upgrade (complete only the tasks for features that were configured, customized, or used prior to upgrade; if you want to configure, customize, or use any of these features for the first time, refer to the following guides for more information: HP Cloud Service Automation Configuration Guide, Configuring an HP CSA Cluster for Server Failover, HP Cloud Service Management Console Help, HP Cloud Service Automation Content Archive Tool, HP Cloud Service Automation Provider Configuration Tool, HP Cloud Service Automation Customizing the Marketplace Portal, HP Cloud Service Automation Integration with ArcSight Logger, Configuring HP CSA to Work with Oracle RAC. If you did not select any features from the selection page, this section may be empty.

Configure a Clustered Environment

The following is a list of files that you may have customized when configuring a clustered environment. If you symbolically linked a shared file system for HP CSA in your clustered environment (such as for sharing a common resource for images), you will need to recreate the link. Refer to the Update Shared Filesystem Resources (Master Node) and Update Shared Filesystem Resources (Slave Node) sections below for more information. Otherwise, no additional actions are required when you upgrade HP CSA in a clustered environment.

File Action
applicationContext-common.xml No action required.
domain.xml No action required.
host.xml No action required.
web.xml No action required.

Files, Actions, and Locations

  • applicationContext-common.xml
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • domain.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • host.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • web.xml
    Action No action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

Update Shared Filesystem Resources (Master Node)

Configure HP CSA to share filesystem resources to free up disk space (this task is optional). Static filesystem resources, such as images, can be stored on one system and shared by all nodes in the cluster. The following example shows how to share the images directory that is installed with each instance of HP CSA.

HP CSA provides images that are stored in an images directory (for example, %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images). From the Cloud Service Management Console, you may also upload images which are saved to the same images directory. You can store these images on a shared filesystem on a network and the images on this single shared filesystem can be used by all nodes in the cluster.

To configure HP CSA to use a shared filesystem to store images, do the following:

  1. Create a shared filesystem on the network. The master and slave nodes must be able to read and write to the shared location.
  2. Map the shared location as a network drive. For example, map S:\CSA on the master node to the shared location.

    Mount the shared location. For example, mount the shared location to /mnt/csa by typing mount -t cifs -o username=<user>, password=<pass> //sharedhost/CSA/ /mnt/csa

  3. Move the %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images directory to the shared location (for example, S:\CSA\images/mnt/csa/images).

    Ensure that the mapped mounted images directory is readable and writeable.

  4. Delete the %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images directory from the master and slave nodes.

  5. Create a symbolic link to the mapped mountedimages directory. For example, from a command prompt, type the following commands:

    cd %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war
    mklink /d images "S:\CSA\images"

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    ln -s /mnt/csa/images images

  6. Set the permissions and ownership for the images directory. Type the following:

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    chmod 755 images
    chown csauser:csagrp images

Update Shared Filesystem Resources (Slave Node)

Configure HP CSA to share filesystem resources to free up disk space (this task is optional). If you have not done so already, configure a shared filesystem resource from the master node.

The following example configures the images directory as a shared filesystem, using the shared images directory that you set up when you configured the master node (%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images).

To configure HP CSA to use a shared filesystem to store images, do the following:

  1. Map the shared location as a network drive. For example, map S:\CSA on the slave node to the shared location.

    Mount the shared location. For example, mount the shared location to /mnt/csa by typing mount -t cifs -o username=<user>, password=<pass> //sharedhost/CSA/ /mnt/csa

  2. Delete the %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images directory.

  3. Create a symbolic link to the mapped mountedimages directory. For example, from a command prompt, type the following commands:

    cd %CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war
    mklink /d images "S:\CSA\images"

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    ln -s /mnt/csa/images images

  4. Set the permissions and ownership for the images directory. Type the following:

    cd $CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
    chmod 755 images
    chown csauser:csagrp images

Configure the Cloud Service Management Console Properties

The following is the file that you may have customized for the Cloud Service Management Console and the actions required when you upgrade HP CSA:

FileAction
csa.propertiesNo action required.

File, Actions, and Locations

  • csa.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/classes/

Recustomize the Cloud Service Management Console Dashboard

The following is a list of files that you may have customized for the Cloud Service Management Console dashboard and the actions required when you upgrade HP CSA:

FileAction
*.jspRequired. Manually copy the JSP files from the backup directory to the appropriate directory in HP CSA 4.01 directory (see table below for more information).
config.jsonRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).
messages.propertiesRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • *.jsp
    Action

    Required. If you created custom Java server page (JSP) files for the HP CSA dashboard and saved them in a directory within the HP CSA 4.00 installation but not in a directory whose content is backed up by the upgrade installer, you should have backed up these files to preserve them. Otherwise, they will be deleted by the upgrade installer. Manually copy the JSP files from the backup directory to the appropriate directory in HP CSA 4.01 directory.

    File Location in HP CSA 4.01

    The directory where the Cloud Service Management Console expects to find these files, defined in the config.json dashboard configuration file.

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    The directory to which the JSP files were backed up, either manually or by the upgrade installer, depending on where the files were located in HP CSA 4.00.

  • config.json
    ActionRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\dashboard\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/dashboard/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\dashboard\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\dashboard\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/dashboard/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/dashboard/

  • messages.properties
    ActionRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\dashboard\messages\common\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\common\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/dashboard/messages/common/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/common/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\dashboard\messages\common\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\dashboard\messages\common\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/dashboard/messages/common/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/dashboard/messages/common/

Configure the Cloud Service Management Console to Import Large Archives

The following is the file that you customized to import large archives using the Cloud Service Management Console or REST API and the actions required when you upgrade HP CSA:

FileAction

standalone.conf.batstandalone.conf

Required. If this file was customized, you must recustomize this file (see table below for more information).

File, Action, and Locations

  • standalone.conf.batstandalone.conf

    ActionRequired. If this file was customized, you must recustomize this file. Refer to Import Large Archives from the Cloud Service Management Console or through the REST API section in this guide for information on how to complete the recustomization.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\bin\$CSA_HOME/jboss-as-7.1.1.Final/bin/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/

Import Large Archives from the Cloud Service Management Console or through the REST API

If you want to import an archive larger than 1.5 MB, HP recommends using the Content Archive Tool. If you must use the Cloud Service Management Console or REST API to import a large archive, you must update the JVM heap size for HP CSA which requires HP CSA to be restarted. Also, importing a large archive from the Cloud Service Management Console or through the REST API may slow the performance of HP CSA.

To increase the JVM heap size before importing a large archive from the Cloud Service Management Console or through the REST API, do the following:

  1. Increase the JVM heap size for HP CSA.

    1. Open the %CSA_HOME%\jboss-as-7.1.1.Final\bin\standalone.conf.bat $CSA_HOME/jboss-as-7.1.1.Final/bin/standalone.conf file in a text editor.

    2. Locate the following line:

      set "JAVA_OPTS=%JAVA_OPTS%$JAVA_OPT -Xms1024M -Xmx1024M -XX:PermSize=256M
      -XX:MaxPermSize=256M"

    3. Increase the JVM heap size (by default, the JVM heap size is 1 GB). For example, to change the JVM heap size to 2 GB, change the line to:

      set "JAVA_OPTS=%JAVA_OPTS%$JAVA_OPT -Xms2048M -Xmx2048M -XX:PermSize=256M
      -XX:MaxPermSize=256M"

    4. Save and close the file.

For more information about importing archives from the Cloud Service Management Console, refer to the HP Cloud Service Management Console Help. For more information about importing archives through the REST API, refer to the HP CSA API Reference guide.

Recustomize the Cloud Service Management Console Session Timeout

The following file may have been customized if you updated the Cloud Service Management Console session:

FileAction
web.xmlRequired. No action required.

File, Action, and Locations

  • web.xml
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

Recustomize the Cloud Service Management Console Dashboard Title

The following file may have been customized if you updated the Cloud Service Management Console dashboard title:

FileAction
messages.propertiesRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).

File, Action, and Locations

  • messages.properties
    ActionRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\custom\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\custom\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/custom/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/custom/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\custom\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\custom\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/custom/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/custom/

Add Custom Graphic Files or Dynamic Query Scripts

The following is a list of custom files that you may have added and the actions required when you upgrade HP CSA:

FileAction
*.jpg, *.jpeg, *.gif, *.pngRequired. Manually copy any custom files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
*.jsp (dynamic query scripts)Required. Manually copy any custom dynamic query scripts from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • *.jpg, *.jpeg, *.gif, *.png
    ActionRequired. Manually copy any custom files from the backup directory to the HP CSA 4.01 directory. Custom files may include organization logos or images for provider types, categories, component palettes, component types, service designs, subscriber options, tags, service offerings, or catalogs.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\images\library\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\images\library\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/images/library/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/images/library/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\images\library\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\images\library\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/images/library/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/images/library/

  • *.jsp (dynamic query scripts)
    ActionRequired. Manually copy any custom dynamic query scripts from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\propertysources\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\propertysources\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/csa.war/propertysources/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/propertysources/

Recustomize the HP CSA Tools

The following is a list of files that you may have customized if you ran any of the HP CSA tools and the actions required when you upgrade HP CSA:

FileAction
config.properties (content archive tool, purge tool, provider configuration tool)Required. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
db.properties (process definition tool, schema installation tool)Required. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
HPOOInfoInput.xml (process definition tool)Required. Manually copy any custom input files from the backup directory to the HP CSA 4.01 directory (see table below for more information).
provider.xml (provider configuration tool)Required. Manually copy any custom input files from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • config.properties
    ActionRequired. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the configuration file used in some examples for the content archive tool, purge tool, and provider configuration tool. If you used a different name for the configuration file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ContentArchiveTool\
    %CSA_HOME%\Tools\db-purge-tool\
    %CSA_HOME%\Tools\ProviderTool\
    $CSA_HOME/Tools/ContentArchiveTool/
    $CSA_HOME/Tools/db-purge-tool/
    $CSA_HOME/Tools/ProviderTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ContentArchiveTool\
    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\db-purge-tool\
    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProviderTool\
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/ContentArchiveTool/
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/db-purge-tool/
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProviderTool/

  • db.properties
    ActionRequired. Manually copy any custom configuration files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the configuration file used in some examples for the process definition tool and schema installation tool. If you used a different name for the configuration file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ProcessDefinitionTool\
    %CSA_HOME%\Tools\SchemaInstallationTool\
    $CSA_HOME/Tools/ProcessDefinitionTool/
    $CSA_HOME/Tools/SchemaInstallationTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProcessDefinitionTool\
    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\SchemaInstallationTool\
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProcessDefinitionTool/
    $CSA_HOME/_CSA_4_0_1_0_installation/Backup/SchemaInstallationTool/

  • HPOOInfoInput.xml
    ActionRequired. Manually copy any custom input files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the input file used in some examples for the process definition tool. If you used a different name for the input file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ProcessDefinitionTool\$CSA_HOME/Tools/ProcessDefinitionTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProcessDefinitionTool\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProcessDefinitionTool/

  • provider.xml
    ActionRequired. Manually copy any custom provider input files from the backup directory to the HP CSA 4.01 directory. This is the generic name of the input file used in some examples for the provider configuration tool. If you used a different name for the provider input file, copy that file instead.
    File Location in HP CSA 4.01

    %CSA_HOME%\Tools\ProviderTool\$CSA_HOME/Tools/ProviderTool/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\ProviderTool\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/ProviderTool/

Recustomize the HP CSA Seeded Users

The following is a list of files that you may have customized if you updated the password of one or more seeded users and the actions required when you upgrade HP CSA:

FileAction
applicationContext-security.xml

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

csa-consumer-users.properties

Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information).No action required.

applicationContext.properties

No action required.

standalone.xmldomain.xml

No action required.Required. Manually copy the file from your backup to the HP CSA 4.01 directory (see table below for more information).

Files, Actions, and Locations

  • applicationContext-security.xml
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • csa-consumer-users.properties
    Action

    Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory.No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/classes/

  • applicationContext.properties
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • standalone.xmldomain.xml

    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.Required. Manually copy the file from your backup to the HP CSA 4.01 directory.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

Add Marketplace Portal Themes

The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade HP CSA:

DirectoryAction
<theme_directory>

Required. If you created a customized theme for the Marketplace Portal, you must manually copy these directories (one for the Marketplace Portal and one for the Identity Management component and their)this directory (for the Marketplace Portal and its) content from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Directories, Actions, and Locations

  • <theme_directory> (Marketplace Portal)
    ActionRequired. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\themes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/

  • <theme_directory> (Identity Management Component)
    Action

    Required. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the HP CSA 4.01 directory. This theme is used to customize the login page.No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\themes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\themes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/themes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/themes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\themes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\themes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/themes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/themes/

Add Marketplace Portal Widgets

The following is the directory where you may have added customized widgets for the Marketplace Portal and the action required when you upgrade HP CSA:

DirectoryAction
<iFRAME_URL_structure>Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the HP CSA 4.01 directory (see table below for more information).

Directory, Action, and Locations

  • <iFRAME_URL_structure>
    ActionRequired. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\$CSA_HOME/portal/node_modules/mpp-ui/dist/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/

Configure ArcSight Logger

The following is the file that you may have customized if you integrated with the ArcSight Logger and the actions required when you upgrade HP CSA:

FileAction
log4j.propertiesNo action required.

File, Actions, and Locations

  • log4j.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/classes/

Integrate HP CSA with a Common Access Card

The following is a list of files that you customized when integrating HP CSA with a Common Access Card (CAC) and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext.xml (Identity Management component)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Identity Management component)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

rb.jsonRequired. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)Required. If this file was customized, you must recustomize this file (see table below for more information).
standalone.xmlNo action required.
java.securityNo action required.

Files, Actions, and Locations

  • applicationContext.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • applicationContext-security.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • rb.json
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

  • main.css (default)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\default\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/default/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\default\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/default/styles/

  • main.css (pilot)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\pilot\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\pilot\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

  • main.css (<theme_directory>)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • java.security
    ActionNo action required. The file is preserved. Any changes made to this file are retained after the upgrade is completed.
    File Location in HP CSA 4.01

    <csa_jre>\lib\security\<csa_jre>/lib/security/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    This file is not backed up.

Configure HP CSA for FIPS 140-2 Compliance

The following is a list of files that you may have customized for FIPS 140-2 compliance and the actions required when you upgrade HP CSA:

FileAction
*.p12Required. Manually copy the keystore and truststore that support PKCS #12 used by HP CSA from the backup directory to the HP CSA 4.01 directory (see table below for more information).
applicationContext.xmlRequired. If this file was customized, you must recustomize this file (see table below for more information).
node.exeRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.

standalone.xmldomain.xml

No action required.
idm-service.propertiesNo action required.
java.securityNo action required.

Files, Actions, and Locations

  • *.p12
    ActionRequired. Manually copy the keystore and truststore that support PKCS #12 used by HP CSA from the backup directory to the HP CSA 4.01 directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\security\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\security\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/security/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/security/

  • applicationContext.xml
    ActionRequired. This file must be recustomized. Refer to Update applicationContext.xml to be FIPS 140-2 Compliant for information on how to complete the recustomization.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • node.exe
    ActionRequired. Customizations made to this file in HP CSA 4.00 are preserved in the file located in the backup directory. Make a copy of this file in the HP CSA 4.01 directory and then manually overwrite the installed file using the file from the backup directory.
    File Location in HP CSA 4.01

    %CSA_HOME%\node.js\$CSA_HOME/node.js/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\node.js\bin\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/node.js/bin/

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

  • idm-service.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/classes/

  • java.security
    ActionNo action required. The file is preserved. Any changes made to this file are retained after the upgrade is completed.
    File Location in HP CSA 4.01

    <csa_jre>\lib\security\<csa_jre>/lib/security/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    This file is not backed up.

Update applicationContext.xml to be FIPS 140-2 Compliant

  1. Open the %CSA_HOME%\jboss-as-7.1.1.Final\
    standalone\deployments\csa.war\WEB-INF\applicationContext.xml
    $CSA_HOME/jboss-as-7.1.1.Final/
    standalone/deployments/csa.war/WEB-INF/applicationContext.xml
    file in a text editor. For example, edit the following file:

    C:\Program Files\Hewlett-Packard\CSA\jboss-as-7.1.1.Final\
    standalone\deployments\csa.war\WEB-INF\applicationContext.xml
    /usr/local/hp/csa/jboss-as-7.1.1.Final/standalone/
    deployments/csa.war/WEB-INF/applicationContext.xml

  2. Locate the START Standard Mode Configuration comment and comment out the following content that appears between the START Standard Mode Configuration and END Standard Mode Configuration comments:

    <bean id="simpleEncryptionConfiguration" class="com.hp.csa.security.CSASimplePBEConfig" init-method="init">
    </bean>

    <bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
      <property name="config" ref="simpleEncryptionConfiguration" />
    </bean>

    <bean id="propertyConfigurer" class="org.jasypt.spring.properties.
    EncryptablePropertyPlaceholderConfigurer">
      <constructor-arg ref="configurationEncryptor" />
      <property name="locations">
        <list>
          <value>classpath:csa.properties</value>
        </list>
      </property>
    </bean>

  3. Locate the START FIPS Mode Configuration comment and uncomment the following content that appears between the START FIPS Mode Configuration and END FIPS Mode Configuration comments:

    <bean id="configurationEncryptor" class="com.hp.csa.security.util.CSASecurityHelper" />

    <bean id="propertyConfigurer" class=
    "com.hp.csa.security.CSAEncryptablePropertyPlaceholderConfigurer">
      <constructor-arg ref="configurationEncryptor" />
      <property name="locations">
        <list>
          <value>classpath:csa.properties</value>
        </list>
      </property>
    </bean>

  4. Save and close the file.

Configure the Identity Management Component

The following is a list of files that you may have customized for the Identity Management component and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml (Identity Management component)Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext.propertiesNo action required.
applicationContext-common.xmlNo action required.
idm-service.propertiesNo action required.

Files, Actions, and Locations

  • applicationContext.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • applicationContext.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • applicationContext-common.xml
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • idm-service.properties
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\classes\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\classes\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/classes/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/classes/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\classes\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/idm-service.war/WEB-INF/classes/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/classes/

Configure IPv6

The following is the file that you may have customized if you configured IPv6 and the actions required when you upgrade HP CSA:

FileAction

standalone.xmldomain.xml

No action required.

File, Actions, and Locations

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

Configure Oracle RAC

The following is the file that you may have customized if you configured Oracle RAC and the actions required when you upgrade HP CSA:

FileAction

standalone.xmldomain.xml

No action required.

File, Actions, and Locations

  • standalone.xmldomain.xml

    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/$CSA_HOME\jboss-as-7.1.1.Final/domain/configuration/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\configuration\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\configuration\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/configuration/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/configuration/C:\csabackup\/tmp/csabackup/

Configure HP CSA to Use a Single Sign-On

The following is a list of files that you customized when configuring HP CSA to use a single sign-on (SSO) and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

rb.jsonRequired. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)Required. If this file was customized, you must recustomize this file (see table below for more information).

Files, Actions, and Locations

  • applicationContext.xml
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • rb.json
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

  • main.css (default)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\default\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/default/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\default\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/default/styles/

  • main.css (pilot)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\pilot\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\pilot\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

  • main.css (<theme_directory>)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

Integrate HP CSA with CA SiteMinder

The following is a list of files that you customized when integrating HP CSA with SiteMinder and the actions required when you upgrade HP CSA:

FileAction
applicationContext.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Cloud Service Management Console)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

ssologout.jsp

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

applicationContext-security.xml (Identity Management component)

Required. If this file was customized, you must recustomize this file (see table below for more information).No action required.

rb.jsonRequired. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)Required. If this file was customized, you must recustomize this file (see table below for more information).
web.xmlNo action required.

Files, Actions, and Locations

  • applicationContext.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml (Cloud Service Management Console)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • ssologout.jsp
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

  • applicationContext-security.xml (Identity Management Component)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war\WEB-INF\spring\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war\WEB-INF\spring\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war/WEB-INF/spring/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war/WEB-INF/spring/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\idm-service.war\WEB-INF\spring\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/idm-service.war/WEB-INF/spring/

  • rb.json
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

  • main.css (default)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\default\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/default/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\default\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/default/styles/

  • main.css (pilot)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\pilot\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\pilot\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/pilot/styles/

  • main.css (<theme_directory>)
    Action

    Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with HP CSA 4.01.

    Caution: Do NOT copy the backed up file over the new file. The file has changed in HP CSA 4.01 and the backed up file does not contain all the required attributes for the current version.

    File Location in HP CSA 4.01

    %CSA_HOME%\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\$CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

  • web.xml
    Action

    No action required. If this file was customized, the customizations have been merged with the upgraded file.No action required.

    File Location in HP CSA 4.01

    %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\standalone\csa.war\WEB-INF\%CSA_HOME%\_CSA_4_0_1_0_installation\Backup\domain\csa.war\WEB-INF\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/standalone/csa.war/WEB-INF/$CSA_HOME/_CSA_4_0_1_0_installation/Backup/domain/csa.war/WEB-INF/

Delete the Sample Consumer Organization

If you deleted the sample consumer organization on your HP CSA 4.00 system, you should delete the sample consumer organization (if it still exists) if you are no longer using it, if you are moving the application to production, or if you are upgrading a production system. See the HP Cloud Service Automation Configuration Guide for more information if you are deleting this organization for the first time.

Update the HP Operations Orchestration 10 Integration Pack Exclusion File

If you upgrade HP Operations Orchestration 10, copy this file to exclude HP CSA content from being upgraded.

Copy the %CSA_HOME%\CSAKit-4.01\OO Flow Content\oo10-csa-cp-uuids.txt$CSA_HOME/CSAKit-4.01/OO Flow Content/oo10-csa-cp-uuids.txt file to (replace the file if it already exists):

Windows
%ICONCLUDE_HOME%\central\cmu\exclusions\

Linux
$ICONCLUDE_HOME/central/cmu/exclusions\

where %ICONCLUDE_HOME% or $ICONCLUDE_HOME is where you installed HP Operations Orchestration.

Upgrade Shortcuts

If you created HP CSA shortcuts in the default directory (for example, C:\Users\<user>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Hewlett-Packard\Cloud Service Automation), these shortcuts are automatically upgraded. If you created HP CSA shortcuts and saved them to another directory other than the default directory (for example, in a Program Group, in the Start Menu, on the desktop, or in the Quick Launch Bar), you should delete these shortcuts as they will no longer work. Optionally, you can change the target of the shortcuts to %CSA_HOME%\_CSA_4_0_1_0_installation\Change HP Cloud Service Automation Installation.exe.

Marketplace Portal Configuration

If you customized the Marketplace Portal configuration file, the customizations have been merged with the upgraded file. Refer to the HP Cloud Service Automation Configuration Guide for more information about the configurable properties in this file.

FileAction
node.exeRequired. Manually copy the file from the backup directory to the HP CSA 4.01 directory.No action required.
mpp.jsonNo action required. If this file was customized, the customizations have been merged with the upgraded file.

Files, Actions, and Locations

  • node.exe
    ActionRequired. Customizations made to this file in HP CSA 4.00 are preserved in the file located in the backup directory. Make a copy of this file in the HP CSA 4.01 directory and then manually overwrite the installed file using the file from the backup directory.No action required.
    File Location in HP CSA 4.01

    %CSA_HOME%\node.js\$CSA_HOME/node.js/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\node.js\bin\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/node.js/bin/

  • mpp.json
    ActionNo action required. If this file was customized, the customizations have been merged with the upgraded file.
    File Location in HP CSA 4.01

    %CSA_HOME%\portal\conf\$CSA_HOME/portal/conf/

    Backed Up HP CSA 4.00 File Location in HP CSA 4.01

    %CSA_HOME%\_CSA_4_0_1_0_installation\Backup\portal\conf\$CSA_HOME/_CSA_4_0_1_0_installation/Backup/portal/conf/

Update HP CSA Flows

Install and import HP CSA flows:

Install HP CSA Flows

Install HP CSA flows on the system running HP Operations Orchestration:

  1. If HP CSA and HP Operations Orchestration are running on different systems, from the HP CSA system, copy the %CSA_HOME%\CSAKit-4.01\OO Flow Content\CSA-4_01-ContentInstaller.jar$CSA_HOME/CSAKit-4.01/OO Flow Content/CSA-4_01-ContentInstaller.jar file to the HP Operations Orchestration system.

  2. On the system running HP Operations Orchestration, open a command prompt and change to the directory where the file CSA-4_00-ContentInstaller.jar is located.
  3. From the command prompt, run the following command:

    Windows: "<location_of_OO_jre>\bin\java" -jar CSA-4_01-ContentInstaller.jar -centralPassword <OOAdminPassword>

    Linux: <location_of_OO_jre>/bin/java -jar CSA-4_01-ContentInstaller.jar -centralPassword <OOAdminPassword>

    where <location_of_OO_jre> is the location of the JRE installed for HP Operations Orchestration. For example, "%ICONCLUDE_HOME%\jre1.6" or $ICONCLUDE_HOME/jre1.6.

Import HP CSA Flows

Import the HP CSA 4.01 flows using the process definition tool (for more information about the process definition tool, refer to the HP Cloud Service Automation Configuration Guide):

Note: You must regenerate the HP Operations Orchestration input file (HPOOInputSample.xml) in order to import the flows that have been updated in HP CSA 4.01. Refer to the steps below for more information.

  1. Log in as csauser.
  2. Navigate to the %CSA_HOME%\Tools\ProcessDefinitionTool $CSA_HOME/Tools/ProcessDefinitionTool directory.

  3. Make a backup of or rename your existing sample input files (MsSqlInputSample.properties, OracleInputSample.properties, PostgreSqlInputSample.properties, ProcessEngineInputSample.xml, and HPOOInputSample.xml). These files will be overwritten when you regenerate the properties files in the step below. Note that you can use the existing (HP CSA 4.00) database properties file. Therefore, at a minimum, if you did not change the existing sample database properties file name (from MsSqlInputSample.properties, OracleInputSample.properties, or PostgreSqlInputSample.properties), make a copy of the file before running the process definition tool so that you do not have to update the file again.
  4. Regenerate the sample database properties files and HP Operations Orchestration input file. For example, run the following command (you may need to specify different options; refer to the HP Cloud Service Automation Configuration Guide for more information about the process definition tool):

    "<csa_jre>\bin\java" –jar process-defn-tool.jar –g $CSA_JRE_HOME/bin/java –jar process-defn-tool.jar –g

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

  5. Rename the sample HP Operations Orchestration input file from HPOOInputSample.xml to HPOOInfoInput4.01.xml.
  6. Update the attributes and values in the HPOOInfoInput4.01.xml file by making the same customizations you made in the HP CSA 4.00 version of the HP Operations Orchestration input file.
  7. Verify that the database properties file you will be using is up-to-date. In the example below, db.properties is the name of the database properties file.
  8. Run the following command (you may need to specify different options; refer to the HP Cloud Service Automation Configuration Guide for more information about the process definition tool):

    "<csa_jre>\bin\java" $CSA_JRE_HOME/bin/java –jar process-defn-tool.jar –d db.properties –i HPOOInfoInput4.01.xml "<csa_jre>\bin\java" $CSA_JRE_HOME/bin/java –jar process-defn-tool.jar –d db.properties –i HPOOInfoInput4.01.xml

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

Import Service Designs

Import the HP CSA 4.01 sample service designs:

  1. Log in to the Cloud Service Management Console. You must be assigned the Service Designer or CSA Administrator role in order to import service designs.
  2. Click the Designs tile.
  3. If you are importing a sequential design, do the following:

    1. Click the Sequenced tile, which takes you to the All Designs area for sequenced designs.
    2. In the lower, right pane of the All Designs area, click Import.
  4. If you are importing a topology design, do the following:

    1. Click the Topology tile.
    2. From Browse Designs, click Import.
  5. Navigate to %CSA_HOME%\CSAKit-4.01\Content Archives, $CSA_HOME/CSAKit-4.01/Content Archives, select a zip file from one of the directories, and click Open.

  6. Repeat steps 3/4 and 5 for every zip file in the Content Archives directory and its subdirectories.

Note: HP recommends that you start using the HP CSA 4.01 versions of the service designs immediately.

Refer to the HP CSA Integration Pack whitepaper and HP CSA Service Design Guide for more information about the HP CSA service designs.

Upgrade Resource Providers

Refer to the README file of the resource provider to verify if it requires and upgrade. The README file can be found in the following location:

%CSA_HOME%\CSAKit-4.01\Lib\<resource_provider>\ $CSA_HOME/CSAKit-4.01/Lib/<resource_provider>/

Clear the Web Browser Cache

It may be necessary to clear your Web browser cache on systems that previously accessed the Cloud Service Management Console prior to upgrading to HP CSA 4.01. To clear your Web browser cache:

  • If you are using a Chrome Web browser:

    1. Open the browser.
    2. Select <Ctrl>+<Shift>+<Delete>.
    3. For Obliterate the following items from, select the beginning of time.
    4. Select only Empty the cache. Unselect all other items.
    5. Click Clear browsing data.
  • If you are using a Firefox Web browser:

    1. Open the browser.
    2. Select <Ctrl>+<Shift>+<Delete>.
    3. For Time range to clear, select Everything.
    4. Expand Details.
    5. Select only Cache. Unselect all other items.
    6. Click Clear Now.
  • If you are using a Windows IE Web browser:

    1. Open the browser.
    2. Select <Ctrl>+<Shift>+<Delete>.
    3. Select only Temporary Internet Files. Unselect all other items.
    4. Click Delete.

Start HP CSA

To start the HP Cloud Service Automation and Marketplace Portal services:

  1. On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.

  2. Right-click on the HP Cloud Service Automation service and select Start.

  3. Right-click on the HP Marketplace Portal service and select Start.

  4. On the server that hosts HP CSA, log in as csauser enter the following:

    service csa start
    service mpp start

© Copyright 2010-2014 Hewlett-Packard Development Company, L.P.