Customized output from:
Document Release Date: March 2014 Software Release Date: January 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, based on the information you supply.
Note: You can only upgrade from HP CSA version 3.20 to version 4.00. If you are running an earlier version, you must first upgrade to HP CSA version 3.20.
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 System 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.
Oracle and Microsoft SQL Server databases are supported by HP CSA running on Windows and Red Hat Enterprise Linux.
PostgreSQL databases are supported by HP CSA running on Windows, Ubuntu Linux, and Red Hat Enterprise Linux.
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 JRE used by HP CSA.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
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 Cloud Subscriber Portal or if you are upgrading a system running a remote Cloud Subscriber Portal.
Remote Cloud Subscriber Portal instances are supported by HP CSA running on Windows or Red Hat Enterprise Linux in a standalone environment.
The Cloud Subscriber Portal will be upgraded to the Marketplace Portal.
Version: 4.00
Document Release Date: March 2014
Software Release Date: January 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(Ubuntu), standalone environment,
and a remote Cloud Subscriber Portal instance
(HP CSA does not support
a remote Cloud Subscriber Portal instance
running on Linux (Ubuntu)
in a standalone environment).
Click Change and update your selections.
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 System 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).
In HP CSA 4.00, two new components are automatically installed: the Marketplace Portal (which replaces the Cloud Subscriber Portal) and the Identity Management component (see diagram below). You will need to configure the Marketplace Portal before you can start to use it. Information on how to configure the Marketplace Portal is included in this guide.
The Identity Management component is used for optional secondary authentication (LDAP will continue to be used as the primary authentication and authorization), logging in to the Marketplace Portal, configuring the seeded consumer user, FIPS 140‑2 compliance, and single sign-on (if it is configured).
If you are upgrading a clustered environment, you will need to install additonal applications on two additional nodes. These tasks are included in this guide.
The following diagram displays the existing components in HP CSA 3.20 and the new components that are automatically installed in an upgrade to HP CSA 4.00.
When HP CSA is upgraded, new directories (and content)
are added and existing directories (and content) are preserved, backed up, updated, or deleted. 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
and
).
The information in this section applies to an upgrade of an installation of
HP CSA running the
Cloud Service Management Console/Cloud Subscriber Portal,
not a remote Cloud Subscriber Portal installation.
%CSA_HOME%\_CSA_4_0_1_installation
%CSA_HOME%\Autopass
%CSA_HOME%\CSAKit-4.0
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\mpp.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\mpp.war
%CSA_HOME%\node.js
%CSA_HOME%\openjre
%CSA_HOME%\portal
%CSA_HOME%\Tools\ConfigurationTool
%CSA_HOME%\Tools\DBPurgeTool
%CSA_HOME%\Tools\ProviderTool
%CSA_HOME%\Tools\SchemaInstallationTool
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%\_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%\jre
%CSA_HOME%\Tools
(backed up to %CSA_HOME%\_CSA_4_0_1_installation\Backup\
)%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\*.war
(backed up to %CSA_HOME%\_CSA_4_0_1_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_installation\Backup\domain\*.war
)%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa-subscriber-help.war
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csp.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa-subscriber-help.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csp.war
%CSA_HOME%\Tools\LocalizationTool
$CSA_HOME/_CSA_4_0_1_installation
$CSA_HOME/Autopass
$CSA_HOME/CSAKit-4.0
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/mpp.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/mpp.war
$CSA_HOME/node.js
$CSA_HOME/openjre
$CSA_HOME/portal
$CSA_HOME/Tools/ConfigurationTool
$CSA_HOME/Tools/DBPurgeTool
$CSA_HOME/Tools/ProviderTool
$CSA_HOME/Tools/SchemaInstallationTool
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/jre
$CSA_HOME/Tools
(backed up to $CSA_HOME/_CSA_4_0_1_installation/Backup/
)$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/*.war
(backed up to $CSA_HOME/_CSA_4_0_1_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_installation/Backup/domain/*.war
)$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa-subscriber-help.war
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csp.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa-subscriber-help.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csp.war
$CSA_HOME/Tools/LocalizationTool
When HP CSA is upgraded, the files listed in the tables below are affected in one or more of the following ways:
If you customized files that are not included in this list, they must be manually updated. The information in this section applies to an upgrade of an installation of HP CSA running the Cloud Service Management Console/Cloud Subscriber Portal, not a remote Cloud Subscriber Portal installation.a remote Cloud Subscriber Portal.
The tables below list the location of specific files in HP CSA 3.20, their location in HP CSA 4.00, and the location of their backup files (if they exist) based on the your selections from the previous page.
Note: Verify that preserved and merged files contain any customizations you made in HP CSA 3.20.
N/A. FIPS 140-2 compliant systems only. This file was upgraded but the customizations for FIPS 140-2 compliance have not been merged with the upgraded file. This file is also backed up. If this file was customized (for example, you have integrated HP CSA with a Common Access Card (CAC) or a single sign-on (SSO) solution), the customizations have been backed up. If you made any customizations to this file, you will need to re-customize the HP CSA 4.00 file. HP CSA 3.20 Directory If this file was customized, the customizations have been merged with the upgraded file. This file is also backed up. HP CSA 3.20 Directory If this file was customized, the customizations have been backed up. If you made customizations for the Custom tile in the Cloud Service Management Console in version 3.20, you can add this tile to the HP CSA dashboard in version 4.00. Refer to the Upgrade the Cloud Service Management Console Custom Tile section in this guide for more information. HP CSA 3.20 Directory If this file was customized, the customizations have been merged with the upgraded file. This file is also backed up. HP CSA 3.20 Directory If this file was customized, the customizations have been backed up.
If you made any customizations to this file, you will need to re-customize the
HP CSA 4.00
file (if the content is localized, the file may be named HP CSA 3.20 Directory
web.xml
N/A. Clustered environments only. If this file was customized, the customizations have been merged with the
upgraded file. This file is also backed up. If you added scripts for dynamic queries, these files are backed up. Copy them from
HP CSA 3.20 DirectoryCloud Service Management Console Files
File Description
applicationContext.xml
HP CSA 3.20 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/
applicationContext-security.xml %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/
csa.properties %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\classes\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\classes\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/classes/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/classes/
index.jsp %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\custom-content\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\custom-content\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/custom-content/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/custom-content/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\custom-content\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\custom-content\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/custom-content/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/custom-content/
log4j.properties %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\classes\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\classes\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/classes/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/classes/
messages.properties messages_<locale>.properties
where <locale>
identifies the language to which the text has been translated,
for example, en
for English or ja
for Japanese).%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\msgs\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\msgs\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/msgs/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/msgs/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\dashboard\messages\common\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\common\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/dashboard/messages/common/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/common/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/
HP CSA 3.20 Directory%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\msgs\
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/msgs/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\classes\msgs\
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/classes/msgs/
*.jsp %CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\propertysources\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\propertysources\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/propertysources/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/propertysources/
to
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/
after the upgrade has been performed.%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\propertysources\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\propertysources\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/propertysources/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/propertysources/
In HP CSA version 4.00, the Cloud Subscriber Portal has been replaced by the Marketplace Portal.
All files in the
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csp.war
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csp.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csp.war
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csp.war
and/or
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\<org_instance>
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\<org_instance>
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/<org_instance>
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/<org_instance>
directories are backed up.
Customizations made to the Cloud Subscriber Portal
using the csp.properties
file
can be made to the Marketplace Portal using the
Cloud Service Management Console or by editing the
%CSA_HOME%\portal\conf\mpp.json$CSA_HOME/portal/conf/mpp.json
file.
Refer to the Configure the Marketplace Portal section in this guide for more information.
File | Description |
---|---|
standalone.xml domain.xml |
If this file was customized, the customizations have been merged with the upgraded file.
HP CSA 3.20 Directory
|
host.xml |
N/A. Clustered environments only. If this file was customized, the customizations have been merged with the
upgraded file. This file is also backed up.
|
File | Description |
---|---|
*.crt |
These certificate files are backed up. If any of these files are being used, copy them from
HP CSA 3.20 Directory
|
keystore |
The keystore file defined by the
HP CSA 3.20 File Defined by the Certificate Key File
|
cacerts |
This file is preserved. Note:
HP CSA 3.20 Directory
|
File | Description |
---|---|
ojdbc6*.jar | These file(s) are copied to the listed HP CSA 4.00 directories. HP CSA 3.20 Directories
|
Caution: Once you have upgraded to HP CSA version 4.00, you cannot revert back to an earlier version of HP CSA.
Before you run the upgrade installer, ensure the following steps are completed.
%CSA_HOME%
.$CSA_HOME
.If you have not already done so, back up the database used by HP CSA 3.20.
If you symbolically linkedmounted a shared filesystem for HP CSA in your clustered environment in %CSA_HOME%
,$CSA_HOME
, (such as for sharing a common resource for images), you will need to unlinkunmount the filesystem from the master and slave nodes. Otherwise, the upgrade installer will remove the files from the linkedmounted filesystem during the upgrade.
Configure a reporting role and read-only user for HP CSA (required for reporting).Configure a reporting database user for HP CSA (required for reporting).
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the upgrade of HP CSA.
Add the CREATE ANY SYNONYM privilege to the HP CSA database user. This allows the HP CSA database user to create synonyms for the HP CSA reporting (read-only) database user during the upgrade.
For example, if the HP CSA database user is named CSADBUser, run the following command:
Grant CREATE ANY SYNONYM to CSADBUser
Because you selected the option to use another JRE, you must export the SSL certificate from the truststore of HP CSA version 3.20 so that you may import it (at a later time during the upgrade process) into the truststore of HP CSA version 4.00.
To export the SSL certificate, do the following:
Open a command prompt and navigate to a directory outside of %CSA_HOME%
in which you will store the certificate file.
Run the following command:
<csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias <alias> ‑file ./<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed, .keystore
keystore_csaID.p12
is 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
, $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml
, <alias> is the name used by the HP CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into HP CSA version 4.00 later during the upgrade process.
For example, run the following command if the JRE used by HP CSA version 3.20 is located in %CSA_HOME%\jre$CSA_HOME/jre
, the alias used to identify the certificate is csa
, and the file the certificate is saved to is csa.cert
:
%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias csa ‑file ./csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert
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 3.20.
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 System 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: Run the following command: Run the following command: where Run the following command:%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
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.jboss-cli.bat --connect --controller=<IP_address>:9999 --command=/host=<unique_host>:shutdown
<IP_address>
is the IP address or fully-qualified domain name used to identify
this system in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file and
<unique_host>
is the name that uniquely identifies this host in the cluster and is defined in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file.$CSA_HOME/jboss-as-7.1.1.Final/bin
.jboss-cli.sh --connect --command=:shutdown
Note:
Upgrade log files are written to the
%CSA_HOME%\_CSA_4_0_0_installation\Logs
$CSA_HOME/_CSA_4_0_1_installation/Logs
directory.
setup.exe
upgrade file.Select the JRE used by HP CSA.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Use OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Use Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
Choose the JRE that will be used by HP CSA. By default, the OpenJDK JRE that is bundled with HP CSA is selected and will be installed. If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE and click Next.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select OpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
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, the
CSA reporting database username
(if you configured this user during initial setup), and
the CSA reporting database user's password.
Then, 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
Cloud Subscriber 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.00
will be installed (the upgrade installer uses this location to install
HP CSA 4.00).
In a startup script for the csauser user (for example, .profile
), 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 .profile
,
enter the following:
. .profile
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 JRE used by
HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
Existing JREOpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Choose the JRE that will be used by
HP CSA and click Enter.
By default, the OpenJDK JRE that is bundled with
HP CSA
is selected.
If you have installed a supported version of Oracle JRE to be used by
HP CSA,
select 2 and click Enter.
In this documentation,
the directory in which the JRE is installed will be referred to as
$CSA_JRE_HOME
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
OpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Select the JRE used by HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Enter.
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.
Enter the CSA
reporting database username (if you configured this user during initial setup)
and click enter.
If you are upgrading
a slave node, this option is not available.
Enter the CSA
reporting database user's 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.00.
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 script. Enter the following:
rm /etc/init.d/csa
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
As csauser, start the HP CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
The upgrade installer may not have been able to automatically update all files. Complete the following tasks:
HP CSA version 4.00 requires a software license. HP CSA licensing is based on the number of operating system instances (OSIs) being used in current, active subscriptions.
After upgrade to HP CSA version 4.00, when you log in to the Cloud Service Management Console, a temporary 90‑day trial license is activated. Once the trial license expires, you are limited to 25 OSIs. If you created more than 25 OSIs during the trial period, you cannot create any additional OSIs. You can add more licenses at any time to increase your OSI capacity.
If you received an Electronic Delivery Receipt, use the link to the licensing portal located in the receipt and follow the online instructions to request a software license. Otherwise, to access the licensing portal, go to http://www.hp.com/software/licensing, enter your Entitlement Order Number, and follow the online instructions to request a software license.
Refer to the Software License Activation Quick Start Guide for more
information about requesting a software license.
In a clustered environment, use the IP address of the HP CSA proxy server (in the examples given in the Configuring an HP CSA Cluster for Server Failover, this is the APACHE_MASTER_IP_ADDR). The license should be installed on only one node in the clustered environment.
Do NOT use the following IP addresses when requesting a software license:
Loopback address - 127.0.0.1 (IPv4) or ::1 (IPv6)
To add a software license, log in to the Cloud Service Management Console as the CSA Administrator. From the Options menu, select Licensing. For more detailed information about adding a license, refer to the HP Cloud Service Management Console Help.
For information on how to view, add, or delete a license, refer to the HP Cloud Service Management Console Help.
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_installation\Change HP Cloud Service Automation Installation.exe
.
The applicationContext.xml
file for the Cloud Service Management Console
must be updated to be FIPS 140-2 compliant.
Do the following:
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">
<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>
Restart HP CSA.
To restart HP CSA, 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 Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.Run the following commands:
jboss-cli.bat --connect --command=:shutdown
.\domain.bat
Navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
$CSA_HOME/jboss-as-7.1.1.Final/bin
.Run the following commands:
jboss-cli.sh --connect --command=:shutdown
.\domain.sh
service mpp restart
Prior to running the upgrade installer, you should have exported the SSL certificate from the truststore of HP CSA version 3.20. Import this certificate and other application's certificates into the truststore of HP CSA version 4.00. Do the following:
If you did not export the SSL certificate from the truststore of HP CSA version 3.20, the truststore has been backed up to the %CSA_HOME%\_CSA_4_0_1_installation\Backup\security\keystores\$CSA_HOME/_CSA_4_0_1_installation/Backup/security/keystores/
directory. Follow the instructions in the Initial Setup section of this document to export HP CSA's SSL certificate from the backed up truststore (you will need to modify the location of the truststore in the command).
Import the HP CSA certificate into the new HP CSA truststore. Do the following:
Run the following command:
<csa_jre>\bin\keytool ‑importcert ‑keystore <csa_jre>\lib\security\cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\openjre\lib\security\cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_JRE_HOME/lib/security/cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/openjre/lib/security/cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit<csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename><csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed, keystore_csaID.p12
is the keystore file defined by the certificate-key-file
property of the connector attribute in
%CSA_HOME%\jboss-as-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
, $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml
, <alias> is the name used by the HP CSA server keystore to identify the SSL certificate, and <file_name> is the filename given to the certificate file to be imported.
For example, run the following command where the alias used to identify the certificate is csa
, and the file the certificate is named csa.cert
and is saved in the current directory:
<csa_jre>\bin\keytool ‑importcert ‑keystore <csa_jre>\lib\security\cacerts ‑alias csa ‑file .\csa.cert ‑storepass changeit%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore <csa_jre>\openjre\lib\security\cacerts ‑alias csa ‑file .\csa.cert ‑storepass changeit$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/lib/security/cacerts ‑alias csa ‑file ./csa.cert ‑storepass changeit$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/openjre/lib/security/cacerts ‑alias csa ‑file ./csa.cert ‑storepass changeit<csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert<csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert
Import the HP Operations Orchestration certificate into the new HP CSA truststore. Do the following:
If the root certificate of HP Operations Orchestration's Certificate Authority is stored in a file on this system, import that file. Otherwise, export HP Operations Orchestration's certificate from HP Operations Orchestration's truststore:
%ICONCLUDE_HOME%
(Windows)
or $ICONCLUDE_HOME
(Linux).Run the following command:
HP Operations Orchestration 9.x, Windows
.\jre1.6\bin\keytool ‑exportcert ‑alias pas ‑file C:\oo.crt
‑keystore .\Central\conf\rc_keystore ‑storepass bran507025
HP Operations Orchestration 10, Windows
.\jre1.6\bin\keytool ‑exportcert ‑alias tomcat ‑file C:\oo.crt
‑keystore .\Central\var\security\key.store ‑storepass changeit
HP Operations Orchestration 9.x, Linux
./jre1.6/bin/keytool ‑exportcert ‑alias pas ‑file /tmp/oo.crt
‑keystore ./Central/conf/rc_keystore ‑storepass bran507025
HP Operations Orchestration 10, Linux
./jre1.6/bin/keytool ‑exportcert ‑alias tomcat ‑file /tmp/oo.crt
‑keystore ./Central/var/security/key.store ‑storepass changeit
where C:\oo.crt
and /tmp/oo.crt
are examples of filenames
and locations used to
store the exported root certificate (you can choose a different filename and location).
oo.crt
from the HP Operations Orchestration system
to the system running HP Cloud Service Automation
(in this example, the file is copied to
C:\
/tmp
).On the system running HP Cloud Service Automation, run the following command:
<csa_jre>\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore <csa_jre>\lib\security\cacerts ‑storepass changeit%CSA_HOME%\openjre\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\openjre\lib\security\cacerts ‑storepass changeit$CSA_JRE_HOME/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_JRE_HOME/lib/security/cacerts ‑storepass changeit$CSA_HOME/openjre/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/openjre/lib/security/cacerts ‑storepass changeit<csa_jre>\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12%CSA_HOME%\openjre\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12$CSA_JRE_HOME/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12$CSA_HOME/openjre/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12<csa_jre>\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12%CSA_HOME%\openjre\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12$CSA_JRE_HOME/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12$CSA_HOME/openjre/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed.
If other applications, such as the database, LDAP, SMTP, HP Operations Orchestration Load Balancer, or HP Continuous Delivery Automation require SSL, and/or you have installed an instance of the Marketplace Portal on a remote system, you must import these applications' certificates into the truststore of HP CSA version 4.00.
Restart the HP Cloud Service Automation
To restart HP CSA, 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 Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.Run the following commands:
jboss-cli.bat --connect --command=:shutdown
.\domain.bat
Navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
$CSA_HOME/jboss-as-7.1.1.Final/bin
.Run the following commands:
jboss-cli.sh --connect --command=:shutdown
.\domain.sh
service mpp restart
In HP CSA version 3.20,
you could customize the Cloud Subscriber Portal by configuring
the Cloud Subscriber Portal attributes in the
csp.properties
file.
In HP CSA version
4.00, the
Cloud Subscriber Portal has been replaced by the
Marketplace Portal and attributes that were configured in the
csp.properties
file are
configured from the Cloud Service Management Console by the
CSA Administrator,
by editing the
%CSA_HOME%\portal\conf\mpp.json
$CSA_HOME/portal/conf/mpp.json
configuration file, and
by using the Identity Management component.
When you upgrade from
HP CSA version 3.20
to HP CSA version
4.00, all attribute values
for the Marketplace Portal are
configured with default values. If the attribute values in the
Cloud Subscriber Portal property file
were customized, the
CSA Administrator
must manually reconfigure the attribute values in the Cloud Service Management Console,
mpp.json
file, and Identity Management component.
Note: The default value for the Marketplace Portal session timeout is different from the default value for the Cloud Subscriber Portal session timeout (session-timeout).
To review customizations you made to the csp.properties
file, refer to the backup copy
of the file in
%CSA_HOME%\_CSA_3_2_0_installation\Backup\standalone\<org_instance>\WEB-INF\classes\
%CSA_HOME%\_CSA_3_2_0_installation\Backup\domain\<org_instance>\WEB-INF\classes\
$CSA_HOME/_CSA_3_2_0_installation/Backup/<org_instance>/WEB-INF/classes/
C:\csabackup\<org_instance>\WEB-INF\classes\
/tmp/<org_instance>/WEB-INF/classes/
(where
<org_instance>
is the directory name of the
Cloud Subscriber Portal
instance for the organization, such as csp.war
).
To edit the Marketplace Portal properties, do the following:
Launch
the Cloud Service Management Console by typing the following URL in a supported
Web browser: https://<csahostname>:8444/csa
where
<csahostname>
is the fully‑qualified domain name of the system on which the
Cloud Service Management Console resides.
Log in to the Cloud Service Management Console as the CSA Administrator.
Provide the information to customize the Marketplace Portal. The following table maps the items from the Portal Customization area to the deprecated property names and shows the default values for both.
Portal Customization Item | New Default Value | csp.properties Property Name |
Old Default Value |
---|---|---|---|
Theme | <none provided> | csa.consumer.portal.theme | Default |
Security Classification | No Banner | csa.consumer.agency | (disabled) |
Security Classification | No Banner | csa.consumer.contentType | (disabled) |
%CSA_HOME%\portal\conf\mpp.json
$CSA_HOME/portal/conf/mpp.json
file.Provide the information to customize the Marketplace Portal.
The following table maps the attributes from the mpp.json
file
to the deprecated property names and shows the default values for both.
Note: The default value for the Marketplace Portal session timeout is different from the default value for the Cloud Subscriber Portal session timeout (session-timeout).
mpp.json Attribute |
New Default Value | Property Name | Old Default Value |
---|---|---|---|
url attribute for the provider |
localhost | csa.provider.hostname | localhost |
url attribute for the provider |
8444 | csa.provider.port | 8444 |
url attribute for the provider |
https | csa.provider.rest.protocol | https |
defaultOrganizationName attribute |
CSA_CONSUMER | csa.consumer.orgName | CSA_CONSUMER |
strictSSL attribute for the provider and idmProvider (you will also need to configure the ca attribute for the provider and idmProvider, completed in the next step) |
true | csa.provider.verifyHostName | false |
pfx attribute for https |
%CSA_HOME%\portal\conf\.mpp_keystore
$CSA_HOME/portal/conf/.mpp_keystore
|
keystore | <none> |
key attribute for https |
<none> | encryptedKeyFile | <none> |
mpp.json Attribute |
New Default Value | Property Name | Old Default Value |
---|---|---|---|
timeoutDuration attribute for the session |
1800 (seconds) | session-timeout | 20 (minutes) |
Configure the ca
attribute for the provider and idmProvider. This attribute
is the path to and name of the file that is an actual certificate or contains a comma-delimited
list of certificates for HP CSA.
Certificate files were backed up during the upgrade. If you have not already done so,
copy the certificate files from
%CSA_HOME%\_CSA_4_0_1_installation\Backup\security\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\security\
$CSA_HOME/_CSA_4_0_1_installation/Backup/security/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/security/
to
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/
$CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/
.
If you are using the self-signed certificate that was generated during the installation of
HP CSA, the file is named
jboss.crt
. Set the ca
attribute to the name and location of the
certificate file to be used.
If you need to regenerate the certificate, refer to the Configure SSL for Client Browsers section in the HP Cloud Service Automation Configuration Guide. You may choose to generate a Certificate Authority-signed certificate, a subordinate Certificate Authority-signed certificate, or a self-signed certificate.
The following properties are configured through the Identity Management component:
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/csa.properties
)%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/csa.properties
)The following portal properties are deprecated:
For information on how to configure the Marketplace Portal to be compliant with FIPS 140-2, integrate the Marketplace Portal with a Common Access Card, or integrate the Marketplace Portal with a single sign-on application, refer to the HP Cloud Service Automation Configuration Guide.
If you upgrade HP Operations Orchestration 10, this file excludes HP CSA content from being upgraded.
Copy the
%CSA_HOME%\CSAKit-4.0\OO Flow Content\oo10-csa-cp-uuids.txt$CSA_HOME/CSAKit-4.0/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 deleted the sample consumer organization on your HP CSA 3.20 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 added a Custom tile to the Cloud Service Management Console, you can add this tile to the HP CSA dashboard. Do the following:
custom-content
in the
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war
%CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war
$CSA_HOME/jboss‑as‑7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
directory
(where %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed). Match the spelling and capitalization of the custom-content
folder name exactly.%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\custom-content\index.jsp
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\custom-content\index.jsp
$CSA_HOME/_CSA_4_0_1_installation/Backup/standalone/csa.war/custom-content/index.jsp
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/custom-content/index.jsp
to the custom-content
directory.Edit the
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\dashboard\config.json
%CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\config.json
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/dashboard/config.json
$CSA_HOME/jboss‑as‑7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/config.json
file:
id
and name
are set to custom
.enabled
attribute to true.Update the name and description of the Custom tile displayed
in the Cloud Service Management Console,
edit the
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\dashboard\messages\common\messages.properties
%CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\common\messages.properties
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/dashboard/messages/common/messages.properties
$CSA_HOME/jboss‑as‑7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/common/messages.properties
file (if the content is localized, the file may be named messages_<locale>.properties
where
<locale>
identifies the language to which the text has been translated, for example,
en
for English or ja
for Japanese):
custom=Custom
property and value.Custom
value with the desired tile name. For example, to name the
tile "My Content," change the entry to
custom=My Content
.custom_description=Custom integration content
property and value.Custom integration content
value with the desired description to be displayed in
the tile. For example, to display "My Custom Content" in the tile description, change the entry to
custom_description=My Custom Content
.index.jsp
page.See the HP Cloud Service Automation Configuration Guide for more information about customizing the Cloud Service Management Console dashboard.
The Redis data structure server is used by the Marketplace Portal in a clustered environment only. The Redis data structure server should be installed independently from the Marketplace Portal.
To install the Redis data structure server:
Download and install the Redis data structure server from
github.com (https://github.com/MSOpenTech/redis/archive/2.6.zip).redis.io (http://download.redis.io/releases/redis-2.6.16.tar.gz).
Follow the instructions at http://redis.io/download to extract and compile the Redis data structure server.
Start the Redis Data Structure Server
To start the Redis data structure server:
<path_to>\redis-2.6\redis-2.6\
bin\release\redisbin64
.<path_to>/src/redis
.This section describes how to install and configure the applications needed to set up the Marketplace Portal proxy node in an HP CSA cluster configured for server failover.
The Marketplace Portal proxy node consists of:
Install a Proxy Server
On a separate node in the clustered environment, install a proxy server for the Marketplace Portal (referred to as the Marketplace Portal proxy node). Do the following:
Download and install the Apache HTTP Server (including SSL) from apache.org (http://httpd.apache.org/download.cgi). The names in the directory path in which the Apache HTTP Server is installed must not contain any spaces.
If you are installing the Apache HTTP server on a system running Ubuntu Linux, log in as csauser and run the following command: sudo apt-get install apache2
Verify that the following modules exist in the
<path_to>\Apache2.2\modules
/etc/httpd/modules
/usr/lib/apache2/modules
directory:
mod_proxy.so
mod_proxy_ajp.so
mod_proxy_balancer.so
mod_proxy_connect.so
mod_proxy_http.so
Configure SSL on the Marketplace Portal Proxy Node
Configure SSL on the Apache HTTP Web server for outbound communication.
Generate the SSL certificate and private key. For a test environment, you can create a self-signed SSL certificate and key using the following command:
openssl req -new -x509 -days 365 -sha1 -newkey rsa:2048 -nodes
-keyout /etc/httpd/conf/apache_mpp.key
-out /etc/httpd/conf/apache_mpp.crt
-config /etc/httpd/conf/openssl.cnf
-subj /O=HP/OU=HP/CN=[MASTER_HOSTNAME]
openssl req -new -x509 -days 365 -sha1 -newkey rsa:2048 -nodes
-keyout /etc/apache2/cert/apache_mpp.key
-out /etc/apache2/cert/apache_mpp.crt
-config <path_to>/openssl.cnf
-subj /O=HP/OU=HP/CN=[MASTER_HOSTNAME]
where [MASTER_HOSTNAME]
is the fully-qualified domain name of the node that is hosting the Apache master proxy (the proxy server for the HP CSA JBoss server).
For detailed instructions on how to create SSL certificates, refer to the Apache documentation (http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#aboutcerts).
Load the SSL module:
Edit /etc/httpd/conf/httpd.conf
to include the SSL configuration and load the SSL module.
Include conf/extra/httpd-ssl.conf
LoadModule ssl_module modules/mod_ssl.so
Place the certificate (apache_mpp.crt
) and the private key, apache_mpp.key
, in the /etc/httpd/conf
directory.
Enable the SSL module. Verify the following files exist in /etc/apache2/modules-enabled
(if they do not exist, copy them from /etc/apache2/modules-available
):
ssl.conf
ssl.load
Update the SSL port used by the VirtualHost. Edit the /etc/apache2/sites-available/default-ssl
file and update the following port entry:
<VirtualHost _default_:[APACHE_MPP_HTTPS_PORT]>
For example, if you want to change the SSL port to 8089, update the port entry to the following:
<VirtualHost _default_:8089>
Create a symbolic link to the /etc/apache2/sites-available/default-ssl
directory from the /etc/apache2/sites-enabled
directory. Run the following command:
ln -s /etc/apache2/sites-available/default-ssl /etc/apache2/sites-enabled/default-ssl
Start the Apache Web server:
sudo invoke-rc.d apache2 start
Configure the Apache HTTP Web Server on the Marketplace Portal Proxy Node
To configure the Apache HTTP Web server on the Marketplace Portal proxy node, do the following:
Edit the /etc/httpd/conf/httpd.conf
file:
Enable port 8089. Add the following port entries:
Listen 8089
ServerName *:8089
Add or update the list of modules that are loaded to include the following comments and modules:
# Disable mod_proxy_balancer.so
# LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
# The mod_proxy.so and mod_proxy_ajp.so modules should already be configured in apache2.conf
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
# Additionally load the following modules
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule slotmem_module modules/mod_slotmem.so
Edit the /etc/httpd/conf.d/ssl.conf
file.
Set up a virtual host for the MPP_Proxy node:
<VirtualHost _default_:8089>
ErrorLog /etc/httpd/logs/mpp_proxy_error.log
TransferLog /etc/httpd/logs/mpp_proxy_access.log
LogLevel warn
SSLProtocol all -SSLv2
SSLProxyEngine On
SSLEngine on
SSLCertificateFile /etc/httpd/conf/apache_mpp.crt
SSLCertificateKeyFile /etc/httpd/conf/apache_mpp.key
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
<Proxy balancer://mycluster/>
BalancerMember https://[MASTER_HOSTNAME]:8089
BalancerMember https://[SLAVE_HOSTNAME]:8089
</Proxy>
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
</VirtualHost>
Add a port used by the Apache HTTP Server. Edit the /etc/apache2/ports.conf
file. Change or add the following port entries:
NameVirutalHost *:8089
Listen 8089
In the /usr/lib/apache2/mods-enabled
directory, create a file named csa-ha.load
with the following contents:
LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module /usr/lib/apache2/modules/mod_proxy_balancer.so
LoadModule proxy_connect_module /usr/lib/apache2/modules/mod_proxy_connect.so
LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so
Set up a virtual host. Add the following to the
/etc/apache2/sites-available/default-ssl.conf
file:
<VirtualHost _default_:8089>
ErrorLog /etc/apache2/logs/mpp_proxy_error.log
TransferLog /etc/apache2/logs/mpp_proxy_access.log
LogLevel warn
SSLProtocol all -SSLv2
SSLProxyEngine On
SSLEngine on
SSLCertificateFile /etc/apache2/cert/apache_mpp.crt
SSLCertificateKeyFile /etc/apache2/cert/apache_mpp.key
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
<Proxy balancer://mycluster/>
BalancerMember https://[MASTER_HOSTNAME]:8089
BalancerMember https://[SLAVE_HOSTNAME]:8089
</Proxy>
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
</VirtualHost>
Run the Configuration Tool on the Marketplace Portal Proxy Node
Set up the Apache Web server on the Marketplace Portal proxy node in the cluster by running the Configuration tool. The Configuration tool allows you to configure the Apache Web server as a load balancer from an interface rather than manually editing configuration files.
The examples in this guide shows how to configure the Apache Web server as a load balancer for the Marketplace Portal on the Marketplace Portal proxy node.
The examples in this section show running the Configuration tool in an interface or "swing" mode. Examples on how to run the Configuration tool in other modes are not provided.
To set up the Marketplace Portal proxy node by configuring the Apache Web server as a load balancer for the Marketplace Portal, do the following:
From the master or slave node, copy the
%CSA_HOME%\Tools\ConfigurationTool\
file to the Marketplace Portal proxy node.
configuration-tool.jar
Note:
The Configuration tool 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.
For a list of supported JRE versions, refer to the
HP Cloud Service Automation System 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).
On the Marketplace Portal proxy node, launch the Configuration tool:
From a command prompt, navigate to where you copied the configuration-tool.jar
file.
"<jre_installation>\bin\java" -jar configuration-tool.jar -i swing
Configure an Apache Web server as a proxy for Marketplace Portal.
Enter the following information:
Field | Description | |
---|---|---|
Apache Home Directory | Required. Choose the absolute directory path to the location where the Apache Web server is installed. | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Apache Web server instance. | |
HTTP Port | Required. The port used by the Apache Web server (for example, 8080). | |
Allowed IP Addresses or Hostnames | Optional. The IP addresses or fully-qualified domain names of the master and slave nodes. The IP addresses or hostnames must be separated by a comma. | |
Configure SSL | Optional. Select this option if you want the Apache Web server to communicate with Marketplace Portal over SSL. | |
HTTPS Port | The port used by the Apache Web server when SSL is enabled (for example, 8089). | |
Create a self-signed certificate | Select this option to generate a self-signed certificate and key for the Apache Web server. Typically, a self-signed certificate is only used in a test environment. | |
Import key/certificate files | Select this option to use the Apache Web server’s Certificate Authority-signed certificate. Click Import to select the key/certificate file(s) to import into the Marketplace Portal’s truststore. For detailed instructions on how to create SSL certificates, refer to the Apache documentation (http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#aboutcerts). |
Start the Apache HTTP Web Server
To start the Apache HTTP Web server, open a command prompt and type service httpd start
service apache2 start
.
Configure the master and slave nodes in the cluster by running the Configuration tool on each node. The Configuration tool allows you to configure a node from an interface rather than manually editing configuration files.
The examples in this guide have the Apache Web server as a proxy for HP CSA installed on the master node. You may also configure the Apache Web server as a proxy on the slave node or on a remote system instead. However, examples for these configurations are not provided.
The examples in this section show running the Configuration Tool in an interface or "swing" console mode. Examples on how to run the Configuration Tool in other modes are not provided.
To configure the master and slave nodes, do the following:
On the master and slave nodes, launch the Configuration tool:
Type "<csa_jre>\bin\java" -jar configuration-tool.jar -i swing
Enter the following information:
Field | Description | |
---|---|---|
IP Address or Hostname | Required. The IP address or hostname of the Apache Web server on the Marketplace Portal proxy node. | |
HTTP Port | Required. The port used by the Apache Web server on the Marketplace Portal proxy node (for example, 8080). | |
Configured with SSL | Optional. Select this option if you want the Apache Web server on the Marketplace Portal proxy node to communicate with the Marketplace Portal over SSL. | |
HTTPS Port | The port used by the Apache Web server on the Marketplace Portal proxy node (for example, 8089). |
Enter the following information:
Field | Description |
---|---|
Redis Data Structure Server | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Redis data structure server. |
Port | Required. The port used by the Redis data structure server. |
CSA Provider | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Identity Management Component | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Import HP CSA Certificate | |
Import |
Required. Click Import to importImport the SSL certificate for HP CSA. If HP CSA is in a clustered environment using the Apache Web server as a proxy, enter the SSL certificate of the Apache Web server as a proxy for HP CSA. |
On the master and slave nodes, launch the Configuration tool:
Type $CSA_JRE_HOME/bin/java -jar configuration-tool.jar -i console
Select a configuration option
Set up a Marketplace Portal clustered node. Select 2 and enter.
Use an Existing Apache Web Server as a Proxy
Configure an Apache Web server as a proxy. Type y and select enter.
Verify your selection. You should have selected to set up a Marketplace Portal clustered node and an existing Apache Web server as a proxy on the HP CSA clustered node. If you made any errors in your selections, select ctrl c to exit the Configuration tool and start over. To continue the configuration, select enter.
Use an Existing Apache Web Server as a Proxy for Marketplace Portal
Enter the following information:
Field | Description |
---|---|
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Apache Web server instance. |
Configured with SSL | Optional. Select yes if you want the Apache Web server on the Marketplace Portal proxy node to communicate with the Marketplace Portal over SSL or no if SSL is not required. |
HTTP(S) Port | Required. The port used by the Apache Web server on the Marketplace Portal proxy node (for example, 8080 (HTTP) or 8089 (HTTPS)). |
Import Certificate | Required. Import the SSL certificate for HP CSA. If HP CSA is in a clustered environment using the Apache Web server as a proxy, enter the SSL certificate of the Apache Web server as a proxy for the Marketplace Portal. |
Configure a Marketplace Portal Node
Enter the following information:
Field | Description |
---|---|
Redis Data Structure Server | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Redis data structure server. |
Port | Required. The port used by the Redis data structure server. |
CSA Provider | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Identity Management Component | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Import HP CSA Certificate | |
Import | Required. Click Import to importImport the SSL certificate for HP CSA. If HP CSA is in a clustered environment using the Apache Web server as a proxy, enter the SSL certificate of the Apache Web server as a proxy for HP CSA. |
Restart HP CSA on the Master and Slave Nodes
To restart HP CSA, 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 Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.Run the following commands:
jboss-cli.bat --connect --command=:shutdown
.\domain.bat
Navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
$CSA_HOME/jboss-as-7.1.1.Final/bin
.Run the following commands:
jboss-cli.sh --connect --command=:shutdown
.\domain.sh
service mpp restart
If you symbolically linked a shared filesystem 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 Configuring an HP CSA Cluster for Server Failover guide for more information.
Install and import HP CSA flows:
HP Operations Orchestration 9.x
Install HP CSA flows on the system running HP Operations Orchestration 9.x:
If HP CSA and
HP Operations Orchestration are running on different systems, from the
HP CSA system, copy the
%CSA_HOME%\CSAKit-4.0\OO Flow Content\CSA-3_20-ContentInstaller.jar
$CSA_HOME/CSAKit-4.0/OO Flow Content/CSA-3_20-ContentInstaller.jar
file to the HP Operations Orchestration system.
CSA-3_20-ContentInstaller.jar
is located.From the command prompt, run the following command:
Windows: "<location_of_OO_jre>\bin\java" -jar CSA-3_20-ContentInstaller.jar -centralPassword <OOAdminPassword>
Linux: <location_of_OO_jre>/bin/java -jar CSA-3_20-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
.
HP Operations Orchestration 10.01
Install HP CSA flows on the system running HP Operations Orchestration 10.01:
If HP CSA and
HP Operations Orchestration are running on different systems, from the
HP CSA system, copy the
%CSA_HOME%\CSAKit-4.0\OO Flow Content\oo10-csa-cp-4.0.0.jar
$CSA_HOME/CSAKit-4.0/OO Flow Content/oo10-csa-cp-4.0.0.jar
file to the HP Operations Orchestration system.
Deploy the HP CSA content pack:
Select the oo10-csa-cp-4.0.0 content pack and click Open.
Click Deploy.
The deployment may take a few minutes and the cursor will show the "busy" icon.
Information about the success or failure of the deployment is displayed in the Deployment Result section.
Import the HP CSA 4.00 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.00.
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 3.20)
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.00.xml
.HPOOInfoInput4.00.xml
file by making the
same customizations you made in the
HP CSA 3.20
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.00.xml
"<csa_jre>\bin\java" $CSA_JRE_HOME/bin/java
–jar process-defn-tool.jar –d db.properties
–i HPOOInfoInput4.00.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.00 sample service designs:
Navigate to
%CSA_HOME%\CSAKit-4.0\Content Archives,
$CSA_HOME/CSAKit-4.0/Content Archives,
select a zip file from one of the directories, and click Open.
Content Archives
directory and it subdirectories.Note: HP recommends that you start using the HP CSA 4.00 versions of the service designs immediately.
HP CSA 4.00 Service Design Archives: HP CSA 4.00 service designs are imported from and exported to archive files. An archive file contains XML files for a service design and XML files of all resource offerings used by that service design. HP CSA service designs and resource offerings that were exported to XML files using HP CSA 3.01 or earlier cannot be imported into HP CSA 4.00. However, you should have imported these service designs and resource offerings prior to an upgrade from HP CSA 3.01. After you upgrade to HP CSA 4.00, these service designs and resource offerings referenced by these service designs can be exported to an archive file. You can also export these resource offerings to the updated HP CSA 4.00 XML format.
Refer to the HP CSA Integration Pack whitepaper for more information about the HP CSA 4.00 service designs.
The following resource providers require an upgrade:
%CSA_HOME%\CSAKit-4.0\Lib\matrix operating environment\README.txt
$CSA_HOME/CSAKit-4.0/Lib/matrix operating environment/README.txt
for more information.
Note:
The ADM_WEB_DB_TIER_TEMPLATE.xml
file has not been changed and does not need to be re-imported.
The MOE_71_SCL_TEMPLATE.xml
file is new and must be imported if you are using
HP Matrix Operating Environment infrastructure orchestration version 7.1.
The MOE_SCL_TEMPLATE.xml
file was renamed but does not need to be re-imported.
The following resource providers do NOT require an upgrade. Therefore, no additional steps are necessary for these resource providers for upgrade. See the HP Cloud Service Automation Installation Guide for more information on how to install and configure these resource providers.
Clear the Web browser cache on systems that accessed the Cloud Service Management Console or Cloud Subscriber Portal prior to upgrading to HP CSA 4.00. 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:
When HP CSA is upgraded, new directories (and content)
are added and existing directories (and content) are preserved, backed up, updated, or deleted. 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
and
).
The information in this section applies to an upgrade of an installation of
HP CSA running the
Cloud Service Management Console/Cloud Subscriber Portal,
not a remote Cloud Subscriber Portal installation.
%CSA_HOME%\_CSA_4_0_1_installation
%CSA_HOME%\Autopass
%CSA_HOME%\CSAKit-4.0
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\idm-service.war
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\mpp.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\idm-service.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\mpp.war
%CSA_HOME%\node.js
%CSA_HOME%\openjre
%CSA_HOME%\portal
%CSA_HOME%\Tools\ConfigurationTool
%CSA_HOME%\Tools\DBPurgeTool
%CSA_HOME%\Tools\ProviderTool
%CSA_HOME%\Tools\SchemaInstallationTool
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%\_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%\jre
%CSA_HOME%\Tools
(backed up to %CSA_HOME%\_CSA_4_0_1_installation\Backup\
)%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\*.war
(backed up to %CSA_HOME%\_CSA_4_0_1_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_installation\Backup\domain\*.war
)%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa-subscriber-help.war
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csp.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa-subscriber-help.war
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csp.war
%CSA_HOME%\Tools\LocalizationTool
$CSA_HOME/_CSA_4_0_1_installation
$CSA_HOME/Autopass
$CSA_HOME/CSAKit-4.0
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/idm-service.war
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/mpp.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/idm-service.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/mpp.war
$CSA_HOME/node.js
$CSA_HOME/openjre
$CSA_HOME/portal
$CSA_HOME/Tools/ConfigurationTool
$CSA_HOME/Tools/DBPurgeTool
$CSA_HOME/Tools/ProviderTool
$CSA_HOME/Tools/SchemaInstallationTool
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/jre
$CSA_HOME/Tools
(backed up to $CSA_HOME/_CSA_4_0_1_installation/Backup/
)$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/*.war
(backed up to $CSA_HOME/_CSA_4_0_1_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_installation/Backup/domain/*.war
)$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa-subscriber-help.war
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csp.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa-subscriber-help.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csp.war
$CSA_HOME/Tools/LocalizationTool
When HP CSA is upgraded, the files listed in the tables below are affected in one or more of the following ways:
If you customized files that are not included in this list, they must be manually updated. The information in this section applies to an upgrade of an installation of HP CSA running the Cloud Service Management Console/Cloud Subscriber Portal, not a remote Cloud Subscriber Portal installation.a remote Cloud Subscriber Portal.
The tables below list the location of specific files in HP CSA 3.20, their location in HP CSA 4.00, and the location of their backup files (if they exist) based on the your selections from the previous page.
Note: Verify that preserved and merged files contain any customizations you made in HP CSA 3.20.
N/A. FIPS 140-2 compliant systems only. This file was upgraded but the customizations for FIPS 140-2 compliance have not been merged with the upgraded file. This file is also backed up. If this file was customized (for example, you have integrated HP CSA with a Common Access Card (CAC) or a single sign-on (SSO) solution), the customizations have been backed up. If you made any customizations to this file, you will need to re-customize the HP CSA 4.00 file. HP CSA 3.20 Directory If this file was customized, the customizations have been merged with the upgraded file. This file is also backed up. HP CSA 3.20 Directory If this file was customized, the customizations have been backed up. If you made customizations for the Custom tile in the Cloud Service Management Console in version 3.20, you can add this tile to the HP CSA dashboard in version 4.00. Refer to the Upgrade the Cloud Service Management Console Custom Tile section in this guide for more information. HP CSA 3.20 Directory If this file was customized, the customizations have been merged with the upgraded file. This file is also backed up. HP CSA 3.20 Directory If this file was customized, the customizations have been backed up.
If you made any customizations to this file, you will need to re-customize the
HP CSA 4.00
file (if the content is localized, the file may be named HP CSA 3.20 Directory
web.xml
N/A. Clustered environments only. If this file was customized, the customizations have been merged with the
upgraded file. This file is also backed up. If you added scripts for dynamic queries, these files are backed up. Copy them from
HP CSA 3.20 DirectoryCloud Service Management Console Files
File Description
applicationContext.xml
HP CSA 3.20 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/
applicationContext-security.xml %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/
csa.properties %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\classes\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\classes\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/classes/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/classes/
index.jsp %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\custom-content\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\custom-content\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/custom-content/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/custom-content/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\custom-content\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\custom-content\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/custom-content/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/custom-content/
log4j.properties %CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\classes\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\classes\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/classes/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/classes/
messages.properties messages_<locale>.properties
where <locale>
identifies the language to which the text has been translated,
for example, en
for English or ja
for Japanese).%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\msgs\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\msgs\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/msgs/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/msgs/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\dashboard\messages\common\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\common\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/dashboard/messages/common/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/common/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\WEB-INF\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/WEB-INF/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/
HP CSA 3.20 Directory%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\msgs\
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/msgs/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\WEB-INF\classes\msgs\
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/WEB-INF/classes/msgs/
*.jsp %CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\propertysources\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\propertysources\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/propertysources/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/propertysources/
to
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/
after the upgrade has been performed.%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/
HP CSA 4.00 Directory%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\propertysources\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\propertysources\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/propertysources/
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/propertysources/
HP CSA 4.00 Backup Directory%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\propertysources\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\propertysources\
$CSA_HOME/_CSA_4_0_1_installation/Backup/csa.war/propertysources/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/propertysources/
In HP CSA version 4.00, the Cloud Subscriber Portal has been replaced by the Marketplace Portal.
All files in the
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csp.war
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csp.war
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csp.war
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csp.war
and/or
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\<org_instance>
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\<org_instance>
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/<org_instance>
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/<org_instance>
directories are backed up.
Customizations made to the Cloud Subscriber Portal
using the csp.properties
file
can be made to the Marketplace Portal using the
Cloud Service Management Console or by editing the
%CSA_HOME%\portal\conf\mpp.json$CSA_HOME/portal/conf/mpp.json
file.
Refer to the Configure the Marketplace Portal section in this guide for more information.
File | Description |
---|---|
standalone.xml domain.xml |
If this file was customized, the customizations have been merged with the upgraded file.
HP CSA 3.20 Directory
|
host.xml |
N/A. Clustered environments only. If this file was customized, the customizations have been merged with the
upgraded file. This file is also backed up.
|
File | Description |
---|---|
*.crt |
These certificate files are backed up. If any of these files are being used, copy them from
HP CSA 3.20 Directory
|
keystore |
The keystore file defined by the
HP CSA 3.20 File Defined by the Certificate Key File
|
cacerts |
This file is preserved. Note:
HP CSA 3.20 Directory
|
File | Description |
---|---|
ojdbc6*.jar | These file(s) are copied to the listed HP CSA 4.00 directories. HP CSA 3.20 Directories
|
Caution: Once you have upgraded to HP CSA version 4.00, you cannot revert back to an earlier version of HP CSA.
Before you run the upgrade installer, ensure the following steps are completed.
%CSA_HOME%
.$CSA_HOME
.If you have not already done so, back up the database used by HP CSA 3.20.
If you symbolically linkedmounted a shared filesystem for HP CSA in your clustered environment in %CSA_HOME%
,$CSA_HOME
, (such as for sharing a common resource for images), you will need to unlinkunmount the filesystem from the master and slave nodes. Otherwise, the upgrade installer will remove the files from the linkedmounted filesystem during the upgrade.
Configure a reporting role and read-only user for HP CSA (required for reporting).Configure a reporting database user for HP CSA (required for reporting).
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the upgrade of HP CSA.
Add the CREATE ANY SYNONYM privilege to the HP CSA database user. This allows the HP CSA database user to create synonyms for the HP CSA reporting (read-only) database user during the upgrade.
For example, if the HP CSA database user is named CSADBUser, run the following command:
Grant CREATE ANY SYNONYM to CSADBUser
Because you selected the option to use another JRE, you must export the SSL certificate from the truststore of HP CSA version 3.20 so that you may import it (at a later time during the upgrade process) into the truststore of HP CSA version 4.00.
To export the SSL certificate, do the following:
Open a command prompt and navigate to a directory outside of %CSA_HOME%
in which you will store the certificate file.
Run the following command:
<csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias <alias> ‑file ./<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed, .keystore
keystore_csaID.p12
is 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
, $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml
, <alias> is the name used by the HP CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into HP CSA version 4.00 later during the upgrade process.
For example, run the following command if the JRE used by HP CSA version 3.20 is located in %CSA_HOME%\jre$CSA_HOME/jre
, the alias used to identify the certificate is csa
, and the file the certificate is saved to is csa.cert
:
%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias csa ‑file ./csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert
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 3.20.
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 System 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: Run the following command: Run the following command: where Run the following command:%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
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.jboss-cli.bat --connect --controller=<IP_address>:9999 --command=/host=<unique_host>:shutdown
<IP_address>
is the IP address or fully-qualified domain name used to identify
this system in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file and
<unique_host>
is the name that uniquely identifies this host in the cluster and is defined in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file.$CSA_HOME/jboss-as-7.1.1.Final/bin
.jboss-cli.sh --connect --command=:shutdown
Note:
Upgrade log files are written to the
%CSA_HOME%\_CSA_4_0_0_installation\Logs
$CSA_HOME/_CSA_4_0_1_installation/Logs
directory.
setup.exe
upgrade file.Select the JRE used by HP CSA.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Use OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Use Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
Choose the JRE that will be used by HP CSA. By default, the OpenJDK JRE that is bundled with HP CSA is selected and will be installed. If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE and click Next.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select OpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
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, the
CSA reporting database username
(if you configured this user during initial setup), and
the CSA reporting database user's password.
Then, 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
Cloud Subscriber 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.00
will be installed (the upgrade installer uses this location to install
HP CSA 4.00).
In a startup script for the csauser user (for example, .profile
), 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 .profile
,
enter the following:
. .profile
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 JRE used by
HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
Existing JREOpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Choose the JRE that will be used by
HP CSA and click Enter.
By default, the OpenJDK JRE that is bundled with
HP CSA
is selected.
If you have installed a supported version of Oracle JRE to be used by
HP CSA,
select 2 and click Enter.
In this documentation,
the directory in which the JRE is installed will be referred to as
$CSA_JRE_HOME
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
OpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Select the JRE used by HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Enter.
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.
Enter the CSA
reporting database username (if you configured this user during initial setup)
and click enter.
If you are upgrading
a slave node, this option is not available.
Enter the CSA
reporting database user's 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.00.
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 script. Enter the following:
rm /etc/init.d/csa
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
As csauser, start the HP CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
The upgrade installer may not have been able to automatically update all files. Complete the following tasks:
HP CSA version 4.00 requires a software license. HP CSA licensing is based on the number of operating system instances (OSIs) being used in current, active subscriptions.
After upgrade to HP CSA version 4.00, when you log in to the Cloud Service Management Console, a temporary 90‑day trial license is activated. Once the trial license expires, you are limited to 25 OSIs. If you created more than 25 OSIs during the trial period, you cannot create any additional OSIs. You can add more licenses at any time to increase your OSI capacity.
If you received an Electronic Delivery Receipt, use the link to the licensing portal located in the receipt and follow the online instructions to request a software license. Otherwise, to access the licensing portal, go to http://www.hp.com/software/licensing, enter your Entitlement Order Number, and follow the online instructions to request a software license.
Refer to the Software License Activation Quick Start Guide for more
information about requesting a software license.
In a clustered environment, use the IP address of the HP CSA proxy server (in the examples given in the Configuring an HP CSA Cluster for Server Failover, this is the APACHE_MASTER_IP_ADDR). The license should be installed on only one node in the clustered environment.
Do NOT use the following IP addresses when requesting a software license:
Loopback address - 127.0.0.1 (IPv4) or ::1 (IPv6)
To add a software license, log in to the Cloud Service Management Console as the CSA Administrator. From the Options menu, select Licensing. For more detailed information about adding a license, refer to the HP Cloud Service Management Console Help.
For information on how to view, add, or delete a license, refer to the HP Cloud Service Management Console Help.
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_installation\Change HP Cloud Service Automation Installation.exe
.
The applicationContext.xml
file for the Cloud Service Management Console
must be updated to be FIPS 140-2 compliant.
Do the following:
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">
<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>
Restart HP CSA.
To restart HP CSA, 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 Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.Run the following commands:
jboss-cli.bat --connect --command=:shutdown
.\domain.bat
Navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
$CSA_HOME/jboss-as-7.1.1.Final/bin
.Run the following commands:
jboss-cli.sh --connect --command=:shutdown
.\domain.sh
service mpp restart
Prior to running the upgrade installer, you should have exported the SSL certificate from the truststore of HP CSA version 3.20. Import this certificate and other application's certificates into the truststore of HP CSA version 4.00. Do the following:
If you did not export the SSL certificate from the truststore of HP CSA version 3.20, the truststore has been backed up to the %CSA_HOME%\_CSA_4_0_1_installation\Backup\security\keystores\$CSA_HOME/_CSA_4_0_1_installation/Backup/security/keystores/
directory. Follow the instructions in the Initial Setup section of this document to export HP CSA's SSL certificate from the backed up truststore (you will need to modify the location of the truststore in the command).
Import the HP CSA certificate into the new HP CSA truststore. Do the following:
Run the following command:
<csa_jre>\bin\keytool ‑importcert ‑keystore <csa_jre>\lib\security\cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\openjre\lib\security\cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_JRE_HOME/lib/security/cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/openjre/lib/security/cacerts ‑alias <alias> ‑file <filename> ‑storepass changeit<csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename><csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename>$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file <filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed, keystore_csaID.p12
is the keystore file defined by the certificate-key-file
property of the connector attribute in
%CSA_HOME%\jboss-as-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
, $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml
, <alias> is the name used by the HP CSA server keystore to identify the SSL certificate, and <file_name> is the filename given to the certificate file to be imported.
For example, run the following command where the alias used to identify the certificate is csa
, and the file the certificate is named csa.cert
and is saved in the current directory:
<csa_jre>\bin\keytool ‑importcert ‑keystore <csa_jre>\lib\security\cacerts ‑alias csa ‑file .\csa.cert ‑storepass changeit%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore <csa_jre>\openjre\lib\security\cacerts ‑alias csa ‑file .\csa.cert ‑storepass changeit$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/lib/security/cacerts ‑alias csa ‑file ./csa.cert ‑storepass changeit$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/openjre/lib/security/cacerts ‑alias csa ‑file ./csa.cert ‑storepass changeit<csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert<csa_jre>\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\openjre\bin\keytool ‑importcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_JRE_HOME/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/openjre/bin/keytool ‑importcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert
Import the HP Operations Orchestration certificate into the new HP CSA truststore. Do the following:
If the root certificate of HP Operations Orchestration's Certificate Authority is stored in a file on this system, import that file. Otherwise, export HP Operations Orchestration's certificate from HP Operations Orchestration's truststore:
%ICONCLUDE_HOME%
(Windows)
or $ICONCLUDE_HOME
(Linux).Run the following command:
HP Operations Orchestration 9.x, Windows
.\jre1.6\bin\keytool ‑exportcert ‑alias pas ‑file C:\oo.crt
‑keystore .\Central\conf\rc_keystore ‑storepass bran507025
HP Operations Orchestration 10, Windows
.\jre1.6\bin\keytool ‑exportcert ‑alias tomcat ‑file C:\oo.crt
‑keystore .\Central\var\security\key.store ‑storepass changeit
HP Operations Orchestration 9.x, Linux
./jre1.6/bin/keytool ‑exportcert ‑alias pas ‑file /tmp/oo.crt
‑keystore ./Central/conf/rc_keystore ‑storepass bran507025
HP Operations Orchestration 10, Linux
./jre1.6/bin/keytool ‑exportcert ‑alias tomcat ‑file /tmp/oo.crt
‑keystore ./Central/var/security/key.store ‑storepass changeit
where C:\oo.crt
and /tmp/oo.crt
are examples of filenames
and locations used to
store the exported root certificate (you can choose a different filename and location).
oo.crt
from the HP Operations Orchestration system
to the system running HP Cloud Service Automation
(in this example, the file is copied to
C:\
/tmp
).On the system running HP Cloud Service Automation, run the following command:
<csa_jre>\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore <csa_jre>\lib\security\cacerts ‑storepass changeit%CSA_HOME%\openjre\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\openjre\lib\security\cacerts ‑storepass changeit$CSA_JRE_HOME/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_JRE_HOME/lib/security/cacerts ‑storepass changeit$CSA_HOME/openjre/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/openjre/lib/security/cacerts ‑storepass changeit<csa_jre>\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12%CSA_HOME%\openjre\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12$CSA_JRE_HOME/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12$CSA_HOME/openjre/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12<csa_jre>\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12%CSA_HOME%\openjre\bin\keytool ‑importcert ‑alias pas ‑file C:\oo.crt ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12$CSA_JRE_HOME/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12$CSA_HOME/openjre/bin/keytool ‑importcert ‑alias pas ‑file /tmp/oo.crt ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed.
If other applications, such as the database, LDAP, SMTP, HP Operations Orchestration Load Balancer, or HP Continuous Delivery Automation require SSL, and/or you have installed an instance of the Marketplace Portal on a remote system, you must import these applications' certificates into the truststore of HP CSA version 4.00.
Restart the HP Cloud Service Automation
To restart HP CSA, 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 Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.Run the following commands:
jboss-cli.bat --connect --command=:shutdown
.\domain.bat
Navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
$CSA_HOME/jboss-as-7.1.1.Final/bin
.Run the following commands:
jboss-cli.sh --connect --command=:shutdown
.\domain.sh
service mpp restart
In HP CSA version 3.20,
you could customize the Cloud Subscriber Portal by configuring
the Cloud Subscriber Portal attributes in the
csp.properties
file.
In HP CSA version
4.00, the
Cloud Subscriber Portal has been replaced by the
Marketplace Portal and attributes that were configured in the
csp.properties
file are
configured from the Cloud Service Management Console by the
CSA Administrator,
by editing the
%CSA_HOME%\portal\conf\mpp.json
$CSA_HOME/portal/conf/mpp.json
configuration file, and
by using the Identity Management component.
When you upgrade from
HP CSA version 3.20
to HP CSA version
4.00, all attribute values
for the Marketplace Portal are
configured with default values. If the attribute values in the
Cloud Subscriber Portal property file
were customized, the
CSA Administrator
must manually reconfigure the attribute values in the Cloud Service Management Console,
mpp.json
file, and Identity Management component.
Note: The default value for the Marketplace Portal session timeout is different from the default value for the Cloud Subscriber Portal session timeout (session-timeout).
To review customizations you made to the csp.properties
file, refer to the backup copy
of the file in
%CSA_HOME%\_CSA_3_2_0_installation\Backup\standalone\<org_instance>\WEB-INF\classes\
%CSA_HOME%\_CSA_3_2_0_installation\Backup\domain\<org_instance>\WEB-INF\classes\
$CSA_HOME/_CSA_3_2_0_installation/Backup/<org_instance>/WEB-INF/classes/
C:\csabackup\<org_instance>\WEB-INF\classes\
/tmp/<org_instance>/WEB-INF/classes/
(where
<org_instance>
is the directory name of the
Cloud Subscriber Portal
instance for the organization, such as csp.war
).
To edit the Marketplace Portal properties, do the following:
Launch
the Cloud Service Management Console by typing the following URL in a supported
Web browser: https://<csahostname>:8444/csa
where
<csahostname>
is the fully‑qualified domain name of the system on which the
Cloud Service Management Console resides.
Log in to the Cloud Service Management Console as the CSA Administrator.
Provide the information to customize the Marketplace Portal. The following table maps the items from the Portal Customization area to the deprecated property names and shows the default values for both.
Portal Customization Item | New Default Value | csp.properties Property Name |
Old Default Value |
---|---|---|---|
Theme | <none provided> | csa.consumer.portal.theme | Default |
Security Classification | No Banner | csa.consumer.agency | (disabled) |
Security Classification | No Banner | csa.consumer.contentType | (disabled) |
%CSA_HOME%\portal\conf\mpp.json
$CSA_HOME/portal/conf/mpp.json
file.Provide the information to customize the Marketplace Portal.
The following table maps the attributes from the mpp.json
file
to the deprecated property names and shows the default values for both.
Note: The default value for the Marketplace Portal session timeout is different from the default value for the Cloud Subscriber Portal session timeout (session-timeout).
mpp.json Attribute |
New Default Value | Property Name | Old Default Value |
---|---|---|---|
url attribute for the provider |
localhost | csa.provider.hostname | localhost |
url attribute for the provider |
8444 | csa.provider.port | 8444 |
url attribute for the provider |
https | csa.provider.rest.protocol | https |
defaultOrganizationName attribute |
CSA_CONSUMER | csa.consumer.orgName | CSA_CONSUMER |
strictSSL attribute for the provider and idmProvider (you will also need to configure the ca attribute for the provider and idmProvider, completed in the next step) |
true | csa.provider.verifyHostName | false |
pfx attribute for https |
%CSA_HOME%\portal\conf\.mpp_keystore
$CSA_HOME/portal/conf/.mpp_keystore
|
keystore | <none> |
key attribute for https |
<none> | encryptedKeyFile | <none> |
mpp.json Attribute |
New Default Value | Property Name | Old Default Value |
---|---|---|---|
timeoutDuration attribute for the session |
1800 (seconds) | session-timeout | 20 (minutes) |
Configure the ca
attribute for the provider and idmProvider. This attribute
is the path to and name of the file that is an actual certificate or contains a comma-delimited
list of certificates for HP CSA.
Certificate files were backed up during the upgrade. If you have not already done so,
copy the certificate files from
%CSA_HOME%\_CSA_4_0_1_installation\Backup\security\
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\security\
$CSA_HOME/_CSA_4_0_1_installation/Backup/security/
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/security/
to
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\
$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/
$CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/
.
If you are using the self-signed certificate that was generated during the installation of
HP CSA, the file is named
jboss.crt
. Set the ca
attribute to the name and location of the
certificate file to be used.
If you need to regenerate the certificate, refer to the Configure SSL for Client Browsers section in the HP Cloud Service Automation Configuration Guide. You may choose to generate a Certificate Authority-signed certificate, a subordinate Certificate Authority-signed certificate, or a self-signed certificate.
The following properties are configured through the Identity Management component:
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/csa.properties
)%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties
$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/WEB-INF/classes/csa.properties
)The following portal properties are deprecated:
For information on how to configure the Marketplace Portal to be compliant with FIPS 140-2, integrate the Marketplace Portal with a Common Access Card, or integrate the Marketplace Portal with a single sign-on application, refer to the HP Cloud Service Automation Configuration Guide.
If you upgrade HP Operations Orchestration 10, this file excludes HP CSA content from being upgraded.
Copy the
%CSA_HOME%\CSAKit-4.0\OO Flow Content\oo10-csa-cp-uuids.txt$CSA_HOME/CSAKit-4.0/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 deleted the sample consumer organization on your HP CSA 3.20 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 added a Custom tile to the Cloud Service Management Console, you can add this tile to the HP CSA dashboard. Do the following:
custom-content
in the
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war
%CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war
$CSA_HOME/jboss‑as‑7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war
directory
(where %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed). Match the spelling and capitalization of the custom-content
folder name exactly.%CSA_HOME%\_CSA_4_0_1_installation\Backup\standalone\csa.war\custom-content\index.jsp
%CSA_HOME%\_CSA_4_0_1_installation\Backup\domain\csa.war\custom-content\index.jsp
$CSA_HOME/_CSA_4_0_1_installation/Backup/standalone/csa.war/custom-content/index.jsp
$CSA_HOME/_CSA_4_0_1_installation/Backup/domain/csa.war/custom-content/index.jsp
to the custom-content
directory.Edit the
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\dashboard\config.json
%CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\config.json
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/dashboard/config.json
$CSA_HOME/jboss‑as‑7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/config.json
file:
id
and name
are set to custom
.enabled
attribute to true.Update the name and description of the Custom tile displayed
in the Cloud Service Management Console,
edit the
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\dashboard\messages\common\messages.properties
%CSA_HOME%\jboss‑as‑7.1.1.Final\domain\servers\hp-cloud\deployments\csa.war\dashboard\messages\common\messages.properties
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/dashboard/messages/common/messages.properties
$CSA_HOME/jboss‑as‑7.1.1.Final/domain/servers/hp-cloud/deployments/csa.war/dashboard/messages/common/messages.properties
file (if the content is localized, the file may be named messages_<locale>.properties
where
<locale>
identifies the language to which the text has been translated, for example,
en
for English or ja
for Japanese):
custom=Custom
property and value.Custom
value with the desired tile name. For example, to name the
tile "My Content," change the entry to
custom=My Content
.custom_description=Custom integration content
property and value.Custom integration content
value with the desired description to be displayed in
the tile. For example, to display "My Custom Content" in the tile description, change the entry to
custom_description=My Custom Content
.index.jsp
page.See the HP Cloud Service Automation Configuration Guide for more information about customizing the Cloud Service Management Console dashboard.
The Redis data structure server is used by the Marketplace Portal in a clustered environment only. The Redis data structure server should be installed independently from the Marketplace Portal.
To install the Redis data structure server:
Download and install the Redis data structure server from
github.com (https://github.com/MSOpenTech/redis/archive/2.6.zip).redis.io (http://download.redis.io/releases/redis-2.6.16.tar.gz).
Follow the instructions at http://redis.io/download to extract and compile the Redis data structure server.
Start the Redis Data Structure Server
To start the Redis data structure server:
<path_to>\redis-2.6\redis-2.6\
bin\release\redisbin64
.<path_to>/src/redis
.This section describes how to install and configure the applications needed to set up the Marketplace Portal proxy node in an HP CSA cluster configured for server failover.
The Marketplace Portal proxy node consists of:
Install a Proxy Server
On a separate node in the clustered environment, install a proxy server for the Marketplace Portal (referred to as the Marketplace Portal proxy node). Do the following:
Download and install the Apache HTTP Server (including SSL) from apache.org (http://httpd.apache.org/download.cgi). The names in the directory path in which the Apache HTTP Server is installed must not contain any spaces.
If you are installing the Apache HTTP server on a system running Ubuntu Linux, log in as csauser and run the following command: sudo apt-get install apache2
Verify that the following modules exist in the
<path_to>\Apache2.2\modules
/etc/httpd/modules
/usr/lib/apache2/modules
directory:
mod_proxy.so
mod_proxy_ajp.so
mod_proxy_balancer.so
mod_proxy_connect.so
mod_proxy_http.so
Configure SSL on the Marketplace Portal Proxy Node
Configure SSL on the Apache HTTP Web server for outbound communication.
Generate the SSL certificate and private key. For a test environment, you can create a self-signed SSL certificate and key using the following command:
openssl req -new -x509 -days 365 -sha1 -newkey rsa:2048 -nodes
-keyout /etc/httpd/conf/apache_mpp.key
-out /etc/httpd/conf/apache_mpp.crt
-config /etc/httpd/conf/openssl.cnf
-subj /O=HP/OU=HP/CN=[MASTER_HOSTNAME]
openssl req -new -x509 -days 365 -sha1 -newkey rsa:2048 -nodes
-keyout /etc/apache2/cert/apache_mpp.key
-out /etc/apache2/cert/apache_mpp.crt
-config <path_to>/openssl.cnf
-subj /O=HP/OU=HP/CN=[MASTER_HOSTNAME]
where [MASTER_HOSTNAME]
is the fully-qualified domain name of the node that is hosting the Apache master proxy (the proxy server for the HP CSA JBoss server).
For detailed instructions on how to create SSL certificates, refer to the Apache documentation (http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#aboutcerts).
Load the SSL module:
Edit /etc/httpd/conf/httpd.conf
to include the SSL configuration and load the SSL module.
Include conf/extra/httpd-ssl.conf
LoadModule ssl_module modules/mod_ssl.so
Place the certificate (apache_mpp.crt
) and the private key, apache_mpp.key
, in the /etc/httpd/conf
directory.
Enable the SSL module. Verify the following files exist in /etc/apache2/modules-enabled
(if they do not exist, copy them from /etc/apache2/modules-available
):
ssl.conf
ssl.load
Update the SSL port used by the VirtualHost. Edit the /etc/apache2/sites-available/default-ssl
file and update the following port entry:
<VirtualHost _default_:[APACHE_MPP_HTTPS_PORT]>
For example, if you want to change the SSL port to 8089, update the port entry to the following:
<VirtualHost _default_:8089>
Create a symbolic link to the /etc/apache2/sites-available/default-ssl
directory from the /etc/apache2/sites-enabled
directory. Run the following command:
ln -s /etc/apache2/sites-available/default-ssl /etc/apache2/sites-enabled/default-ssl
Start the Apache Web server:
sudo invoke-rc.d apache2 start
Configure the Apache HTTP Web Server on the Marketplace Portal Proxy Node
To configure the Apache HTTP Web server on the Marketplace Portal proxy node, do the following:
Edit the /etc/httpd/conf/httpd.conf
file:
Enable port 8089. Add the following port entries:
Listen 8089
ServerName *:8089
Add or update the list of modules that are loaded to include the following comments and modules:
# Disable mod_proxy_balancer.so
# LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
# The mod_proxy.so and mod_proxy_ajp.so modules should already be configured in apache2.conf
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
# Additionally load the following modules
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule slotmem_module modules/mod_slotmem.so
Edit the /etc/httpd/conf.d/ssl.conf
file.
Set up a virtual host for the MPP_Proxy node:
<VirtualHost _default_:8089>
ErrorLog /etc/httpd/logs/mpp_proxy_error.log
TransferLog /etc/httpd/logs/mpp_proxy_access.log
LogLevel warn
SSLProtocol all -SSLv2
SSLProxyEngine On
SSLEngine on
SSLCertificateFile /etc/httpd/conf/apache_mpp.crt
SSLCertificateKeyFile /etc/httpd/conf/apache_mpp.key
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
<Proxy balancer://mycluster/>
BalancerMember https://[MASTER_HOSTNAME]:8089
BalancerMember https://[SLAVE_HOSTNAME]:8089
</Proxy>
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
</VirtualHost>
Add a port used by the Apache HTTP Server. Edit the /etc/apache2/ports.conf
file. Change or add the following port entries:
NameVirutalHost *:8089
Listen 8089
In the /usr/lib/apache2/mods-enabled
directory, create a file named csa-ha.load
with the following contents:
LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module /usr/lib/apache2/modules/mod_proxy_balancer.so
LoadModule proxy_connect_module /usr/lib/apache2/modules/mod_proxy_connect.so
LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so
Set up a virtual host. Add the following to the
/etc/apache2/sites-available/default-ssl.conf
file:
<VirtualHost _default_:8089>
ErrorLog /etc/apache2/logs/mpp_proxy_error.log
TransferLog /etc/apache2/logs/mpp_proxy_access.log
LogLevel warn
SSLProtocol all -SSLv2
SSLProxyEngine On
SSLEngine on
SSLCertificateFile /etc/apache2/cert/apache_mpp.crt
SSLCertificateKeyFile /etc/apache2/cert/apache_mpp.key
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
<Proxy balancer://mycluster/>
BalancerMember https://[MASTER_HOSTNAME]:8089
BalancerMember https://[SLAVE_HOSTNAME]:8089
</Proxy>
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
</VirtualHost>
Run the Configuration Tool on the Marketplace Portal Proxy Node
Set up the Apache Web server on the Marketplace Portal proxy node in the cluster by running the Configuration tool. The Configuration tool allows you to configure the Apache Web server as a load balancer from an interface rather than manually editing configuration files.
The examples in this guide shows how to configure the Apache Web server as a load balancer for the Marketplace Portal on the Marketplace Portal proxy node.
The examples in this section show running the Configuration tool in an interface or "swing" mode. Examples on how to run the Configuration tool in other modes are not provided.
To set up the Marketplace Portal proxy node by configuring the Apache Web server as a load balancer for the Marketplace Portal, do the following:
From the master or slave node, copy the
%CSA_HOME%\Tools\ConfigurationTool\
file to the Marketplace Portal proxy node.
configuration-tool.jar
Note:
The Configuration tool 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.
For a list of supported JRE versions, refer to the
HP Cloud Service Automation System 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).
On the Marketplace Portal proxy node, launch the Configuration tool:
From a command prompt, navigate to where you copied the configuration-tool.jar
file.
"<jre_installation>\bin\java" -jar configuration-tool.jar -i swing
Configure an Apache Web server as a proxy for Marketplace Portal.
Enter the following information:
Field | Description | |
---|---|---|
Apache Home Directory | Required. Choose the absolute directory path to the location where the Apache Web server is installed. | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Apache Web server instance. | |
HTTP Port | Required. The port used by the Apache Web server (for example, 8080). | |
Allowed IP Addresses or Hostnames | Optional. The IP addresses or fully-qualified domain names of the master and slave nodes. The IP addresses or hostnames must be separated by a comma. | |
Configure SSL | Optional. Select this option if you want the Apache Web server to communicate with Marketplace Portal over SSL. | |
HTTPS Port | The port used by the Apache Web server when SSL is enabled (for example, 8089). | |
Create a self-signed certificate | Select this option to generate a self-signed certificate and key for the Apache Web server. Typically, a self-signed certificate is only used in a test environment. | |
Import key/certificate files | Select this option to use the Apache Web server’s Certificate Authority-signed certificate. Click Import to select the key/certificate file(s) to import into the Marketplace Portal’s truststore. For detailed instructions on how to create SSL certificates, refer to the Apache documentation (http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#aboutcerts). |
Start the Apache HTTP Web Server
To start the Apache HTTP Web server, open a command prompt and type service httpd start
service apache2 start
.
Configure the master and slave nodes in the cluster by running the Configuration tool on each node. The Configuration tool allows you to configure a node from an interface rather than manually editing configuration files.
The examples in this guide have the Apache Web server as a proxy for HP CSA installed on the master node. You may also configure the Apache Web server as a proxy on the slave node or on a remote system instead. However, examples for these configurations are not provided.
The examples in this section show running the Configuration Tool in an interface or "swing" console mode. Examples on how to run the Configuration Tool in other modes are not provided.
To configure the master and slave nodes, do the following:
On the master and slave nodes, launch the Configuration tool:
Type "<csa_jre>\bin\java" -jar configuration-tool.jar -i swing
Enter the following information:
Field | Description | |
---|---|---|
IP Address or Hostname | Required. The IP address or hostname of the Apache Web server on the Marketplace Portal proxy node. | |
HTTP Port | Required. The port used by the Apache Web server on the Marketplace Portal proxy node (for example, 8080). | |
Configured with SSL | Optional. Select this option if you want the Apache Web server on the Marketplace Portal proxy node to communicate with the Marketplace Portal over SSL. | |
HTTPS Port | The port used by the Apache Web server on the Marketplace Portal proxy node (for example, 8089). |
Enter the following information:
Field | Description |
---|---|
Redis Data Structure Server | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Redis data structure server. |
Port | Required. The port used by the Redis data structure server. |
CSA Provider | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Identity Management Component | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Import HP CSA Certificate | |
Import |
Required. Click Import to importImport the SSL certificate for HP CSA. If HP CSA is in a clustered environment using the Apache Web server as a proxy, enter the SSL certificate of the Apache Web server as a proxy for HP CSA. |
On the master and slave nodes, launch the Configuration tool:
Type $CSA_JRE_HOME/bin/java -jar configuration-tool.jar -i console
Select a configuration option
Set up a Marketplace Portal clustered node. Select 2 and enter.
Use an Existing Apache Web Server as a Proxy
Configure an Apache Web server as a proxy. Type y and select enter.
Verify your selection. You should have selected to set up a Marketplace Portal clustered node and an existing Apache Web server as a proxy on the HP CSA clustered node. If you made any errors in your selections, select ctrl c to exit the Configuration tool and start over. To continue the configuration, select enter.
Use an Existing Apache Web Server as a Proxy for Marketplace Portal
Enter the following information:
Field | Description |
---|---|
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Apache Web server instance. |
Configured with SSL | Optional. Select yes if you want the Apache Web server on the Marketplace Portal proxy node to communicate with the Marketplace Portal over SSL or no if SSL is not required. |
HTTP(S) Port | Required. The port used by the Apache Web server on the Marketplace Portal proxy node (for example, 8080 (HTTP) or 8089 (HTTPS)). |
Import Certificate | Required. Import the SSL certificate for HP CSA. If HP CSA is in a clustered environment using the Apache Web server as a proxy, enter the SSL certificate of the Apache Web server as a proxy for the Marketplace Portal. |
Configure a Marketplace Portal Node
Enter the following information:
Field | Description |
---|---|
Redis Data Structure Server | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the Redis data structure server. |
Port | Required. The port used by the Redis data structure server. |
CSA Provider | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the HP CSA Provider is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Identity Management Component | |
IP Address or Hostname | Required. The IP address or fully-qualified domain name of the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the IP address or fully-qualified domain name of the Apache Web server. |
Port | Required. The port used by the system that hosts HP CSA. If the Identity Management Component is in a clustered environment using the Apache Web server as a proxy, enter the port of the Apache Web server. |
Import HP CSA Certificate | |
Import | Required. Click Import to importImport the SSL certificate for HP CSA. If HP CSA is in a clustered environment using the Apache Web server as a proxy, enter the SSL certificate of the Apache Web server as a proxy for HP CSA. |
Restart HP CSA on the Master and Slave Nodes
To restart HP CSA, 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 Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.Run the following commands:
jboss-cli.bat --connect --command=:shutdown
.\domain.bat
Navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
To restart HP CSA, stop and restart HP CSA on the master and slave nodes. On each node:
$CSA_HOME/jboss-as-7.1.1.Final/bin
.Run the following commands:
jboss-cli.sh --connect --command=:shutdown
.\domain.sh
service mpp restart
If you symbolically linked a shared filesystem 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 Configuring an HP CSA Cluster for Server Failover guide for more information.
Install and import HP CSA flows:
HP Operations Orchestration 9.x
Install HP CSA flows on the system running HP Operations Orchestration 9.x:
If HP CSA and
HP Operations Orchestration are running on different systems, from the
HP CSA system, copy the
%CSA_HOME%\CSAKit-4.0\OO Flow Content\CSA-3_20-ContentInstaller.jar
$CSA_HOME/CSAKit-4.0/OO Flow Content/CSA-3_20-ContentInstaller.jar
file to the HP Operations Orchestration system.
CSA-3_20-ContentInstaller.jar
is located.From the command prompt, run the following command:
Windows: "<location_of_OO_jre>\bin\java" -jar CSA-3_20-ContentInstaller.jar -centralPassword <OOAdminPassword>
Linux: <location_of_OO_jre>/bin/java -jar CSA-3_20-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
.
HP Operations Orchestration 10.01
Install HP CSA flows on the system running HP Operations Orchestration 10.01:
If HP CSA and
HP Operations Orchestration are running on different systems, from the
HP CSA system, copy the
%CSA_HOME%\CSAKit-4.0\OO Flow Content\oo10-csa-cp-4.0.0.jar
$CSA_HOME/CSAKit-4.0/OO Flow Content/oo10-csa-cp-4.0.0.jar
file to the HP Operations Orchestration system.
Deploy the HP CSA content pack:
Select the oo10-csa-cp-4.0.0 content pack and click Open.
Click Deploy.
The deployment may take a few minutes and the cursor will show the "busy" icon.
Information about the success or failure of the deployment is displayed in the Deployment Result section.
Import the HP CSA 4.00 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.00.
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 3.20)
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.00.xml
.HPOOInfoInput4.00.xml
file by making the
same customizations you made in the
HP CSA 3.20
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.00.xml
"<csa_jre>\bin\java" $CSA_JRE_HOME/bin/java
–jar process-defn-tool.jar –d db.properties
–i HPOOInfoInput4.00.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.00 sample service designs:
Navigate to
%CSA_HOME%\CSAKit-4.0\Content Archives,
$CSA_HOME/CSAKit-4.0/Content Archives,
select a zip file from one of the directories, and click Open.
Content Archives
directory and it subdirectories.Note: HP recommends that you start using the HP CSA 4.00 versions of the service designs immediately.
HP CSA 4.00 Service Design Archives: HP CSA 4.00 service designs are imported from and exported to archive files. An archive file contains XML files for a service design and XML files of all resource offerings used by that service design. HP CSA service designs and resource offerings that were exported to XML files using HP CSA 3.01 or earlier cannot be imported into HP CSA 4.00. However, you should have imported these service designs and resource offerings prior to an upgrade from HP CSA 3.01. After you upgrade to HP CSA 4.00, these service designs and resource offerings referenced by these service designs can be exported to an archive file. You can also export these resource offerings to the updated HP CSA 4.00 XML format.
Refer to the HP CSA Integration Pack whitepaper for more information about the HP CSA 4.00 service designs.
The following resource providers require an upgrade:
%CSA_HOME%\CSAKit-4.0\Lib\matrix operating environment\README.txt
$CSA_HOME/CSAKit-4.0/Lib/matrix operating environment/README.txt
for more information.
Note:
The ADM_WEB_DB_TIER_TEMPLATE.xml
file has not been changed and does not need to be re-imported.
The MOE_71_SCL_TEMPLATE.xml
file is new and must be imported if you are using
HP Matrix Operating Environment infrastructure orchestration version 7.1.
The MOE_SCL_TEMPLATE.xml
file was renamed but does not need to be re-imported.
The following resource providers do NOT require an upgrade. Therefore, no additional steps are necessary for these resource providers for upgrade. See the HP Cloud Service Automation Installation Guide for more information on how to install and configure these resource providers.
Clear the Web browser cache on systems that accessed the Cloud Service Management Console or Cloud Subscriber Portal prior to upgrading to HP CSA 4.00. 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:
An upgrade of the Cloud Subscriber Portal on a remote system requires you to delete the existing HP CSA installation on the remote system. Follow the steps below to back up your customized files before uninstalling HP CSA.
Before you back up and upgrade your remote installation of the Cloud Subscriber Portal, on the system running the Cloud Service Management Console, upgrade to HP CSA 4.00, if you have not already done so.
On the remote system, do the following:
Make a copy of
all WAR directories in
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\
. $CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/
.
Copies should be located outside of the
%CSA_HOME%
$CSA_HOME
directory.
Copy the following file to
C:\csabackup\
: /tmp/csabackup/
:
%CSA_HOME%\jre\lib\security\cacerts
$CSA_HOME/jre/lib/security/cacerts
If you configured a new SSL certificate for this Cloud Subscriber Portal and
want to continue using the same SSL certificate after upgrading to
HP CSA 4.00,
copy the following files to
C:\csabackup\
: /tmp/csabackup/
:
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml
$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml
%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/
.
Uninstalling HP CSA removes the
%CSA_HOME%
directory and all of its contents
(where %CSA_HOME%
is the directory in which
HP CSA is installed).
If all the contents in %CSA_HOME%
are not deleted,
you must manually delete them and the %CSA_HOME%
directory.
Note: The HP CSA database is NOT updated nor uninstalled.
To uninstall HP CSA:
%CSA_HOME%
directory and any remaining contents,
if they exist.Uninstalling HP CSA removes
all the contents of $CSA_HOME
(where $CSA_HOME
is the directory in which
HP CSA is installed).
Note: The HP CSA database is NOT updated or uninstalled.
To uninstall HP CSA:
csauser
).Stop the HP CSA service. Enter the following:
service csa stop
Verify that the service was stopped. For example, if
HP CSA was installed in
/usr/local/hp/csa
, enter the following:
ps -ef | grep /usr/local/hp/csa
If there are HP CSA services running, repeat step 2 or kill the HP CSA service.
Go to the $CSA_HOME/_CSA_4_0_1_installation
directory. Enter the following:
cd $CSA_HOME/_CSA_4_0_1_installation
Uninstall HP CSA. Enter the following:
./Change \ HP\ Cloud\ Service\ Automation\ Installation
When uninstallation completes, log in as root and do the following:
$CSA_HOME
are not deleted,
you must manually delete them and the $CSA_HOME
directory.Delete the HP CSA service script. Enter the following:
rm /etc/init.d/csa
csauser
user and csagrp
group.Before you run the upgrade installer, ensure the following steps are completed.
%CSA_HOME%
.$CSA_HOME
.If you have not already done so, back up the database used by HP CSA 3.20.
If you symbolically linkedmounted a shared filesystem for HP CSA in your clustered environment in %CSA_HOME%
,$CSA_HOME
, (such as for sharing a common resource for images), you will need to unlinkunmount the filesystem from the master and slave nodes. Otherwise, the upgrade installer will remove the files from the linkedmounted filesystem during the upgrade.
Configure a reporting role and read-only user for HP CSA (required for reporting).Configure a reporting database user for HP CSA (required for reporting).
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the upgrade of HP CSA.
Add the CREATE ANY SYNONYM privilege to the HP CSA database user. This allows the HP CSA database user to create synonyms for the HP CSA reporting (read-only) database user during the upgrade.
For example, if the HP CSA database user is named CSADBUser, run the following command:
Grant CREATE ANY SYNONYM to CSADBUser
Because you selected the option to use another JRE, you must export the SSL certificate from the truststore of HP CSA version 3.20 so that you may import it (at a later time during the upgrade process) into the truststore of HP CSA version 4.00.
To export the SSL certificate, do the following:
Open a command prompt and navigate to a directory outside of %CSA_HOME%
in which you will store the certificate file.
Run the following command:
<csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias <alias> ‑file ./<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed, .keystore
keystore_csaID.p12
is 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
, $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml
, <alias> is the name used by the HP CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into HP CSA version 4.00 later during the upgrade process.
For example, run the following command if the JRE used by HP CSA version 3.20 is located in %CSA_HOME%\jre$CSA_HOME/jre
, the alias used to identify the certificate is csa
, and the file the certificate is saved to is csa.cert
:
%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias csa ‑file ./csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert
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 3.20.
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 System 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: Run the following command: Run the following command: where Run the following command:%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
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.jboss-cli.bat --connect --controller=<IP_address>:9999 --command=/host=<unique_host>:shutdown
<IP_address>
is the IP address or fully-qualified domain name used to identify
this system in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file and
<unique_host>
is the name that uniquely identifies this host in the cluster and is defined in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file.$CSA_HOME/jboss-as-7.1.1.Final/bin
.jboss-cli.sh --connect --command=:shutdown
Note:
Upgrade log files are written to the
%CSA_HOME%\_CSA_4_0_0_installation\Logs
$CSA_HOME/_CSA_4_0_1_installation/Logs
directory.
setup.exe
upgrade file.Select the JRE used by HP CSA.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Use OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Use Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
Choose the JRE that will be used by HP CSA. By default, the OpenJDK JRE that is bundled with HP CSA is selected and will be installed. If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE and click Next.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select OpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
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, the
CSA reporting database username
(if you configured this user during initial setup), and
the CSA reporting database user's password.
Then, 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
Cloud Subscriber 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.00
will be installed (the upgrade installer uses this location to install
HP CSA 4.00).
In a startup script for the csauser user (for example, .profile
), 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 .profile
,
enter the following:
. .profile
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 JRE used by
HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
Existing JREOpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Choose the JRE that will be used by
HP CSA and click Enter.
By default, the OpenJDK JRE that is bundled with
HP CSA
is selected.
If you have installed a supported version of Oracle JRE to be used by
HP CSA,
select 2 and click Enter.
In this documentation,
the directory in which the JRE is installed will be referred to as
$CSA_JRE_HOME
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
OpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Select the JRE used by HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Enter.
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.
Enter the CSA
reporting database username (if you configured this user during initial setup)
and click enter.
If you are upgrading
a slave node, this option is not available.
Enter the CSA
reporting database user's 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.00.
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 script. Enter the following:
rm /etc/init.d/csa
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
As csauser, start the HP CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
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
In HP CSA version 4.00, the Cloud Subscriber Portal has been replaced with the Marketplace Portal. The remote instance of the Marketplace Portal must be configured to use the system on which HP CSA and the Identity Management component is installed. Do the following:
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.00 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 3.20 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.
To start the HP Marketplace Portal service:
On the system running the remote Marketplace Portal, navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Start.
To start the HP Marketplace Portal service, on the system running the remote Marketplace Portal, type service mpp start
.
An upgrade of the Cloud Subscriber Portal on a remote system requires you to delete the existing HP CSA installation on the remote system. Follow the steps below to back up your customized files before uninstalling HP CSA.
Before you back up and upgrade your remote installation of the Cloud Subscriber Portal, on the system running the Cloud Service Management Console, upgrade to HP CSA 4.00, if you have not already done so.
On the remote system, do the following:
Make a copy of
all WAR directories in
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\deployments\
. $CSA_HOME/jboss-as-7.1.1.Final/standalone/deployments/
.
Copies should be located outside of the
%CSA_HOME%
$CSA_HOME
directory.
Copy the following file to
C:\csabackup\
: /tmp/csabackup/
:
%CSA_HOME%\jre\lib\security\cacerts
$CSA_HOME/jre/lib/security/cacerts
If you configured a new SSL certificate for this Cloud Subscriber Portal and
want to continue using the same SSL certificate after upgrading to
HP CSA 4.00,
copy the following files to
C:\csabackup\
: /tmp/csabackup/
:
%CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\standalone.xml
$CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/standalone.xml
%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/
.
Uninstalling HP CSA removes the
%CSA_HOME%
directory and all of its contents
(where %CSA_HOME%
is the directory in which
HP CSA is installed).
If all the contents in %CSA_HOME%
are not deleted,
you must manually delete them and the %CSA_HOME%
directory.
Note: The HP CSA database is NOT updated nor uninstalled.
To uninstall HP CSA:
%CSA_HOME%
directory and any remaining contents,
if they exist.Uninstalling HP CSA removes
all the contents of $CSA_HOME
(where $CSA_HOME
is the directory in which
HP CSA is installed).
Note: The HP CSA database is NOT updated or uninstalled.
To uninstall HP CSA:
csauser
).Stop the HP CSA service. Enter the following:
service csa stop
Verify that the service was stopped. For example, if
HP CSA was installed in
/usr/local/hp/csa
, enter the following:
ps -ef | grep /usr/local/hp/csa
If there are HP CSA services running, repeat step 2 or kill the HP CSA service.
Go to the $CSA_HOME/_CSA_4_0_1_installation
directory. Enter the following:
cd $CSA_HOME/_CSA_4_0_1_installation
Uninstall HP CSA. Enter the following:
./Change \ HP\ Cloud\ Service\ Automation\ Installation
When uninstallation completes, log in as root and do the following:
$CSA_HOME
are not deleted,
you must manually delete them and the $CSA_HOME
directory.Delete the HP CSA service script. Enter the following:
rm /etc/init.d/csa
csauser
user and csagrp
group.Before you run the upgrade installer, ensure the following steps are completed.
%CSA_HOME%
.$CSA_HOME
.If you have not already done so, back up the database used by HP CSA 3.20.
If you symbolically linkedmounted a shared filesystem for HP CSA in your clustered environment in %CSA_HOME%
,$CSA_HOME
, (such as for sharing a common resource for images), you will need to unlinkunmount the filesystem from the master and slave nodes. Otherwise, the upgrade installer will remove the files from the linkedmounted filesystem during the upgrade.
Configure a reporting role and read-only user for HP CSA (required for reporting).Configure a reporting database user for HP CSA (required for reporting).
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the upgrade of HP CSA.
Add the CREATE ANY SYNONYM privilege to the HP CSA database user. This allows the HP CSA database user to create synonyms for the HP CSA reporting (read-only) database user during the upgrade.
For example, if the HP CSA database user is named CSADBUser, run the following command:
Grant CREATE ANY SYNONYM to CSADBUser
Because you selected the option to use another JRE, you must export the SSL certificate from the truststore of HP CSA version 3.20 so that you may import it (at a later time during the upgrade process) into the truststore of HP CSA version 4.00.
To export the SSL certificate, do the following:
Open a command prompt and navigate to a directory outside of %CSA_HOME%
in which you will store the certificate file.
Run the following command:
<csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias <alias> ‑file ./<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename><csa_jre>\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias <alias> ‑file ./<filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed, .keystore
keystore_csaID.p12
is 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
, $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/domain.xml
, <alias> is the name used by the HP CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into HP CSA version 4.00 later during the upgrade process.
For example, run the following command if the JRE used by HP CSA version 3.20 is located in %CSA_HOME%\jre$CSA_HOME/jre
, the alias used to identify the certificate is csa
, and the file the certificate is saved to is csa.cert
:
%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\.keystore ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\.keystore ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/.keystore ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/.keystore ‑alias csa ‑file ./csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\standalone\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert%CSA_HOME%\jre\bin\keytool ‑exportcert ‑keystore %CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\keystore_csaID.p12 ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/standalone/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as-7.1.1.Final/domain/configuration/keystore_csaID.p12 ‑alias csa ‑file ./csa.cert
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 3.20.
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 System 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: Run the following command: Run the following command: where Run the following command:%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
%CSA_HOME%\jboss-as-7.1.1.Final\bin
.jboss-cli.bat --connect --controller=<IP_address>:9999 --command=/host=<unique_host>:shutdown
<IP_address>
is the IP address or fully-qualified domain name used to identify
this system in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file and
<unique_host>
is the name that uniquely identifies this host in the cluster and is defined in the
%CSA_HOME%\jboss-as-7.1.1.Final\domain\configuration\host.xml
file.$CSA_HOME/jboss-as-7.1.1.Final/bin
.jboss-cli.sh --connect --command=:shutdown
Note:
Upgrade log files are written to the
%CSA_HOME%\_CSA_4_0_0_installation\Logs
$CSA_HOME/_CSA_4_0_1_installation/Logs
directory.
setup.exe
upgrade file.Select the JRE used by HP CSA.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Use OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Use Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
Choose the JRE that will be used by HP CSA. By default, the OpenJDK JRE that is bundled with HP CSA is selected and will be installed. If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE and click Next.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select OpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Next.
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, the
CSA reporting database username
(if you configured this user during initial setup), and
the CSA reporting database user's password.
Then, 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
Cloud Subscriber 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.00
will be installed (the upgrade installer uses this location to install
HP CSA 4.00).
In a startup script for the csauser user (for example, .profile
), 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 .profile
,
enter the following:
. .profile
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 JRE used by
HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
Existing JREOpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Choose the JRE that will be used by
HP CSA and click Enter.
By default, the OpenJDK JRE that is bundled with
HP CSA
is selected.
If you have installed a supported version of Oracle JRE to be used by
HP CSA,
select 2 and click Enter.
In this documentation,
the directory in which the JRE is installed will be referred to as
$CSA_JRE_HOME
.
For a list of supported JREs, refer to the
HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select
OpenJDK JREOracle JRE,
select the location in which you installed this JRE,
and click Enter.
Select the JRE used by HP CSA and click Enter.
Use the existing JRE to continue using the JRE that was used with HP CSA version 3.20. No additional configuration is required if you use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with HP CSA version 4.00. You must manually export the HP CSA certificate from the existing truststore and import it into the truststore that is installed with HP CSA.
Select Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with HP CSA version 3.20 (if you used Oracle JRE with HP CSA version 3.20 and want to continue using this same JRE, select Existing JRE). Then, select the location in which you installed this JRE. You must manually export the HP CSA certificate from the existing truststore and import it into the Oracle JRE truststore.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System 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).
Based on the options you selected in this guide, select Existing JREOpenJDK JREOracle JRE, select the location in which you installed this JRE, and click Enter.
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.
Enter the CSA
reporting database username (if you configured this user during initial setup)
and click enter.
If you are upgrading
a slave node, this option is not available.
Enter the CSA
reporting database user's 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.00.
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 script. Enter the following:
rm /etc/init.d/csa
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
As csauser, start the HP CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
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
In HP CSA version 4.00, the Cloud Subscriber Portal has been replaced with the Marketplace Portal. The remote instance of the Marketplace Portal must be configured to use the system on which HP CSA and the Identity Management component is installed. Do the following:
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.00 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 3.20 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.
To start the HP Marketplace Portal service:
On the system running the remote Marketplace Portal, navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Start.
To start the HP Marketplace Portal service, on the system running the remote Marketplace Portal, type service mpp start
.
© Copyright 2010 - 2014 Hewlett-Packard Development Company, L.P.