Customized output from:
Document Release Date: April 2014 Software Release Date: April 2014 |
|
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.
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 2010-2014 Hewlett-Packard Development Company, L.P.
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.
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:
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 the operating system of the server on which HP CSA is being upgraded.
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 the environment in which HP CSA is running.
Select if HP CSA is or is not compliant with FIPS 140-2.
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 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:
Version: 4.01
Document Release Date: April 2014
Software Release Date: April 2014
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
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.
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).
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.
%CSA_HOME%\_CSA_4_0_1_0_installation
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
%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
)$CSA_HOME/_CSA_4_0_1_0_installation
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
$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
)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:
Create a directory named
C:\csabackup\
. /tmp/csabackup/
.
Make a copy of
%CSA_HOME%\portal\
$CSA_HOME/portal/
to
C:\csabackup\
. /tmp/csabackup/
.
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
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
)
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/
.
Before you run the upgrade installer, ensure the following steps are completed.
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
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:
Run the following command: Navigate to Control Panel > Administrative Tools > Services. Right-click on the HP Marketplace Portal service and select Stop. Run the following commands: Run the following command: Navigate to Control Panel > Administrative Tools > Services. Right-click on the HP Marketplace Portal service and select Stop. Run the following commands:%CSA_HOME%\jboss-as-7.1.1.Final\bin
.jboss-cli.bat --connect --command=:shutdown
Stop
HP CSA on the master
and slave nodes:
service csa stop
service mpp stop%CSA_HOME%\jboss-as-7.1.1.Final\bin
.jboss-cli.bat --connect --command=:shutdown
$CSA_HOME/jboss-as-7.1.1.Final/bin
.jboss-cli.sh --connect --command=:shutdown
service mpp stop
Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
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.
setup.exe
upgrade file.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
).
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.
Enter the HP CSA
database user password and click Next.
If you are upgrading a slave node,
this option is not available.
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.
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.
|
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. |
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.
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
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
).
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
setup.bin
) to the system and go to the directory in which it has been copied.Verify that setup.bin
is owned by csauser and csauser has full permissions to the file. If necessary,
do the following:
Enter the following commands:
chown csauser setup.bin
chmod 755 setup.bin
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
Read the Introduction and click enter to continue with the installation.
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
).
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.
Enter the HP CSA
database user password and click enter.
If you are upgrading
a slave node, this option is not available.
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.
Review your selections and click enter to complete the installation or ctrl-c to exit the installation.
When the installation completes, click enter to exit the installer.
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.
Remove the old version of the HP CSA scripts. Enter the following:
rm /etc/init.d/csa
rm /etc/init.d/mpp
Go to the directory in which HP CSA is installed. For example:
cd /usr/local/hp/csa
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
Change permissions of the scripts. Enter the following:
chmod 755 /etc/init.d/csa
chmod 755 /etc/init.d/mpp
Complete the following tasks:
cacerts
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
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:
Edit the
%CSA_HOME%\portal\conf\mpp.json
$CSA_HOME/portal/conf/mpp.json
file.
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
.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
.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:
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
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.
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==)
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.
If you backed up your SSL certificate files, do the following:
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
.
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.
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.
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.
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
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
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.
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.
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
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 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:
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
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.
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
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
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:
File | Action |
---|---|
csa.properties | No action required. |
File, Actions, and Locations
csa.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
*.jsp | Required. 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.json | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information). |
messages.properties | Required. 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 |
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 | |
---|---|
Action | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
messages.properties | |
---|---|
Action | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
Increase the JVM heap size for HP CSA.
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.
Locate the following line:
set "JAVA_OPTS=%JAVA_OPTS%$JAVA_OPT -Xms1024M -Xmx1024M -XX:PermSize=256M
-XX:MaxPermSize=256M"
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"
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.
The following file may have been customized if you updated the Cloud Service Management Console session:
File | Action |
---|---|
web.xml | Required. No action required. |
File, Action, and Locations
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following file may have been customized if you updated the Cloud Service Management Console dashboard title:
File | Action |
---|---|
messages.properties | Required. 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 | |
---|---|
Action | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following is a list of custom files that you may have added and the actions required when you upgrade HP CSA:
File | Action |
---|---|
*.jpg, *.jpeg, *.gif, *.png | Required. 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 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
*.jsp (dynamic query scripts) | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
db.properties | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
HPOOInfoInput.xml | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
provider.xml | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade HP CSA:
Directory | Action |
---|---|
<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) | |
---|---|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
<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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
Directory | Action |
---|---|
<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> | |
---|---|
Action | 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
log4j.properties | No action required. |
File, Actions, and Locations
log4j.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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.json | Required. 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.xml | No action required. |
java.security | No 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
java.security | |
---|---|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 | This file is not backed up. |
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:
File | Action |
---|---|
*.p12 | Required. 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.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
node.exe | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
standalone.xmldomain.xml | No action required. |
idm-service.properties | No action required. |
java.security | No action required. |
Files, Actions, and Locations
*.p12 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
applicationContext.xml | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
node.exe | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
idm-service.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
java.security | |
---|---|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 | This file is not backed up. |
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/
file in a text editor. For example, edit the following file:
standalone/deployments/csa.war/WEB-INF/applicationContext.xml
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
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>
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>
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:
File | Action |
---|---|
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext.properties | No action required. |
applicationContext-common.xml | No action required. |
idm-service.properties | No 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
idm-service.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following is the file that you may have customized if you configured IPv6 and the actions required when you upgrade HP CSA:
File | Action |
---|---|
standalone.xmldomain.xml | No action required. |
File, Actions, and Locations
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following is the file that you may have customized if you configured Oracle RAC and the actions required when you upgrade HP CSA:
File | Action |
---|---|
standalone.xmldomain.xml | No action required. |
File, Actions, and Locations
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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.json | Required. 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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.json | Required. 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.xml | No 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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.
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.
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
.
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.
File | Action |
---|---|
node.exe | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory.No action required. |
mpp.json | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
Files, Actions, and Locations
node.exe | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
mpp.json | |
---|---|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
To start the Marketplace Portal service:
On the system running the remote Marketplace Portal, navigate to Control Panel > Administrative Tools > Services.
Start the HP Marketplace Portal service.
On the system running the remote Marketplace Portal,
type service mpp start
.
The following tasks must be completed before HP CSA can be restarted:
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 |
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
where |
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.xml domain.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 |
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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.
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.
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
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
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.
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.
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
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 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:
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
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.
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
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
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:
File | Action |
---|---|
csa.properties | No action required. |
File, Actions, and Locations
csa.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
*.jsp | Required. 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.json | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory (see table below for more information). |
messages.properties | Required. 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 |
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 | |
---|---|
Action | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
messages.properties | |
---|---|
Action | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
Increase the JVM heap size for HP CSA.
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.
Locate the following line:
set "JAVA_OPTS=%JAVA_OPTS%$JAVA_OPT -Xms1024M -Xmx1024M -XX:PermSize=256M
-XX:MaxPermSize=256M"
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"
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.
The following file may have been customized if you updated the Cloud Service Management Console session:
File | Action |
---|---|
web.xml | Required. No action required. |
File, Action, and Locations
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following file may have been customized if you updated the Cloud Service Management Console dashboard title:
File | Action |
---|---|
messages.properties | Required. 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 | |
---|---|
Action | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following is a list of custom files that you may have added and the actions required when you upgrade HP CSA:
File | Action |
---|---|
*.jpg, *.jpeg, *.gif, *.png | Required. 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 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
*.jsp (dynamic query scripts) | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
db.properties | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
HPOOInfoInput.xml | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
provider.xml | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade HP CSA:
Directory | Action |
---|---|
<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) | |
---|---|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
<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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
Directory | Action |
---|---|
<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> | |
---|---|
Action | 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
log4j.properties | No action required. |
File, Actions, and Locations
log4j.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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.json | Required. 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.xml | No action required. |
java.security | No 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
java.security | |
---|---|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 | This file is not backed up. |
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:
File | Action |
---|---|
*.p12 | Required. 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.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
node.exe | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory. |
standalone.xmldomain.xml | No action required. |
idm-service.properties | No action required. |
java.security | No action required. |
Files, Actions, and Locations
*.p12 | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
applicationContext.xml | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
node.exe | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
idm-service.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
java.security | |
---|---|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 | This file is not backed up. |
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/
file in a text editor. For example, edit the following file:
standalone/deployments/csa.war/WEB-INF/applicationContext.xml
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
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>
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>
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:
File | Action |
---|---|
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext.properties | No action required. |
applicationContext-common.xml | No action required. |
idm-service.properties | No 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
idm-service.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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following is the file that you may have customized if you configured IPv6 and the actions required when you upgrade HP CSA:
File | Action |
---|---|
standalone.xmldomain.xml | No action required. |
File, Actions, and Locations
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
The following is the file that you may have customized if you configured Oracle RAC and the actions required when you upgrade HP CSA:
File | Action |
---|---|
standalone.xmldomain.xml | No action required. |
File, Actions, and Locations
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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.json | Required. 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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:
File | Action |
---|---|
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.json | Required. 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.xml | No 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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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. |
File Location in HP CSA 4.01 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
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.
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.
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
.
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.
File | Action |
---|---|
node.exe | Required. Manually copy the file from the backup directory to the HP CSA 4.01 directory.No action required. |
mpp.json | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
Files, Actions, and Locations
node.exe | |
---|---|
Action | Required. 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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
mpp.json | |
---|---|
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 |
|
Backed Up HP CSA 4.00 File Location in HP CSA 4.01 |
|
Install and import HP CSA flows:
Install HP CSA flows on the system running HP Operations Orchestration:
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.
CSA-4_00-ContentInstaller.jar
is located.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 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.
Navigate to the
%CSA_HOME%\Tools\ProcessDefinitionTool
$CSA_HOME/Tools/ProcessDefinitionTool
directory.
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.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.
HPOOInputSample.xml
to HPOOInfoInput4.01.xml
.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.db.properties
is the name of the database properties file.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 the HP CSA 4.01 sample service designs:
If you are importing a sequential design, do the following:
If you are importing a topology design, do the following:
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.
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.
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>/
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:
If you are using a Firefox Web browser:
If you are using a Windows IE Web browser:
To start the HP Cloud Service Automation and Marketplace Portal services:
On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Cloud Service Automation service and select Start.
Right-click on the HP Marketplace Portal service and select Start.
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.