Customized output from:
Document Release Date: January 2016 Software Release Date: January 2016 |
|
The only warranties for Hewlett Packard Enterprise Development LP 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. HPE 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 HPE 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-2016 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.
The OpenStack® Word Mark and the Square O Design, together or apart, are trademarks or registered trademarks marks of OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission.
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 Cloud Service Automation Upgrade Guide is an interactive document that provides the information necessary to upgrade your CSA (CSA) solution from version 4.2x or 4.50 to version 4.60, based on the information you supply.
Note: You can only upgrade from CSA version 4.2x or 4.50 to version 4.60. If you are running an earlier version, you must first upgrade to CSA version 4.2x or 4.50. Refer to the Cloud Service Automation Upgrade Guide for CSA version 4.2x or 4.50 for more information on how to upgrade to version 4.2x or 4.50.
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 CSA, see the Cloud Service Automation Concepts Guide.
For information about the supported components and versions, see the 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 version of CSA from which you are upgrading (if you want to upgrade from a version of CSA earlier than 4.2x, you must first upgrade to version 4.2x or 4.50).
Select the operating system of the server on which CSA is being upgraded.
Select the database used by CSA.
Select the JRE used by CSA.
Caution: CSA supports JRE version 8. If you are using the JRE that is installed with CSA version 4.60, you are automatically upgraded to version 8. If you are using an earlier version of Oracle JRE:
YOU MUST UPGRADE THE ORACLE JRE BEFORE UPGRADING CSA.
Select OpenJDK JRE if you are using the JRE that is installed with CSA version 4.60. After running the upgrade installer, you must manually export the CSA and all other certificates from the existing truststore and import them into the truststore that is installed with CSA.
Select Oracle JRE if you are using a supported version of Oracle JRE. After running the upgrade installer, you must manually export the CSA and all other certificates from the existing truststore and import them into the upgraded Oracle JRE truststore.
Select the version of Operations Orchestration with which the upgraded CSA instance will be integrated.
Caution: CSA supports Operations Orchestration 9.07, 10.21.0001, and 10.50. If you are using an earlier version of Operations Orchestration:
YOU MUST UPGRADE Operations Orchestration BEFORE UPGRADING CSA.
If you are using the existing embedded Operations Orchestration, the embedded Operations Orchestration will be automatically upgraded to version 10.50.
If you select an existing embedded Operations Orchestration, you must be upgrading a CSA instance that is already integrated with an embedded Operations Orchestration. You cannot upgrade a CSA instance to integrate with the embedded Operations Orchestration if CSA is already integrated with Operations Orchestration (an external instance).
If you select Operations Orchestration 9.07 and 10.21.0001, you must be upgrading a CSA instance that is already integrated with Operations Orchestration 9.07 and 10.21.0001.
If you are integrating with both Operations Orchestration 9.07 and 10.21.0001 and are using Operations Orchestration 10.21.0001 for topology designs only, select the check box if want to import the CSA flows for sequential designs into the Operations Orchestration 10.21.0001 instance (additional configuration on the 10.21.0001 instance is required). If you want to continue to use Operations Orchestration 9.07 for sequential designs and Operations Orchestration 10.21.0001 for only topology designs, or if you are already using Operations Orchestration 10.21.0001 for sequential designs, no additional configuration is required on the 10.21.0001 instance (do not select the check box).
If you select Operations Orchestration 10.21.0001, you must be upgrading a CSA instance that is already integrated with Operations Orchestration 10.21.0001. You cannot upgrade a CSA instance that is integrated with an earlier unsupported version of Operations Orchestration.
If you select Operations Orchestration 9.07, you must be upgrading an CSA instance that is already integrated with Operations Orchestration 9.07. You cannot upgrade a CSA instance that is integrated with an earlier unsupported version of Operations Orchestration. You cannot upgrade a CSA instance that is integrated with Operations Orchestration and then add or switch to an integration with Operations Orchestration 9.07.
If you select no Operations Orchestration installed, you can choose to install the embedded Operations Orchestration.
Select if you are upgrading a system that is running either the Cloud Service Management Console and the Marketplace Portal, or if you are upgrading a system running a remote Marketplace Portal.
Select the features that you configured for CSA (select only the features that were configured, customized, or used prior to upgrade). If you want to configure, customize, or use any of these features for the first time, after you have completed the upgrade, refer to one or more of the guides listed below.
For more information about the listed features, refer to one or more of the following guides:
Version: 4.60
Document Release Date: January 2016
Software Release Date: January 2016
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
Based on your selections from the previous page, you must perform the following steps. It is recommended that you perform each step in the following order:
This guide provides information for upgrading CSA. Successful implementation requires knowledge of the integrated products, as well as HPE 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 CSA. Successful implementation requires knowledge of HPE Cloud Service Automation.
For information about CSA, see the Cloud Service Automation Concepts Guide. Review the 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)..
When CSA is upgraded, new directories (and content)
are added and existing directories (and content) are preserved, backed up, or updated. The following is a list of the
affected directories (where %CSA_HOME%$CSA_HOME
is the directory in which CSA is installed, such as
C:\Program Files\Hewlett-Packard\CSA
/usr/local/hp/csa
).
%CSA_HOME%\_CSA_4_60_0_installation
Preserved directories and content are not affected by the upgrade. If these directories existed before the upgrade, they are preserved during the upgrade, and remain on your system after the upgrade.
%CSA_HOME%\CSAKit
%CSA_HOME%\CSAKit-3.01
%CSA_HOME%\CSAKit-3.10
%CSA_HOME%\CSAKit-3.20
%CSA_HOME%\CSAKit-4.00
%CSA_HOME%\CSAKit-4.01
%CSA_HOME%\CSAKit-4.10
%CSA_HOME%\CSAKit-4.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%\_CSA_4_0_0_installation
%CSA_HOME%\_CSA_4_0_1_installation
%CSA_HOME%\_CSA_4_1_0_installation
%CSA_HOME%\_CSA_4_2_0_installation
%CSA_HOME%\CSAKit
%CSA_HOME%\CSAKit-3.01
%CSA_HOME%\CSAKit-3.10
%CSA_HOME%\CSAKit-3.20
%CSA_HOME%\CSAKit-4.00
%CSA_HOME%\CSAKit-4.01
%CSA_HOME%\CSAKit-4.10
%CSA_HOME%\_CSA_3_0_0_installation
%CSA_HOME%\_CSA_3_0_1_installation
%CSA_HOME%\_CSA_3_1_0_installation
%CSA_HOME%\_CSA_3_2_0_installation
%CSA_HOME%\_CSA_4_0_0_installation
%CSA_HOME%\_CSA_4_0_1_installation
%CSA_HOME%\_CSA_4_1_0_installation
%CSA_HOME%\node.js
%CSA_HOME%\_CSA_4_60_0_installation\Backup\node.js
)%CSA_HOME%\portal
%CSA_HOME%\_CSA_4_60_0_installation\Backup\portal
)%CSA_HOME%\Tools
%CSA_HOME%\_CSA_4_60_0_installation\Backup\Tools\
)%CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\deployments\*.war
(backed up to %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\*.war
)
%CSA_HOME%\jboss-as-7.1.1.Final\domain\servers\<server_name>\deployments\*.war
%CSA_HOME%\_CSA_4_60_0_installation\Backup\domain\*.war
)$CSA_HOME/_CSA_4_60_0_installation
Preserved directories and content are not affected by the upgrade. If these directories existed before the upgrade, they are preserved during the upgrade, and remain on your system after the upgrade.
$CSA_HOME/CSAKit-3.10
$CSA_HOME/CSAKit-3.20
$CSA_HOME/CSAKit-4.00
$CSA_HOME/CSAKit-4.01
$CSA_HOME/CSAKit-4.10
$CSA_HOME/CSAKit-4.20
$CSA_HOME/_CSA_3_1_0_installation
$CSA_HOME/_CSA_3_2_0_installation
$CSA_HOME/_CSA_4_0_0_installation
$CSA_HOME/_CSA_4_0_1_installation
$CSA_HOME/_CSA_4_1_0_installation
$CSA_HOME/_CSA_4_2_0_installation
$CSA_HOME/jre
or
$CSA_HOME/openjre
$CSA_HOME/CSAKit-3.10
$CSA_HOME/CSAKit-3.20
$CSA_HOME/CSAKit-4.00
$CSA_HOME/CSAKit-4.01
$CSA_HOME/CSAKit-4.10
$CSA_HOME/_CSA_3_1_0_installation
$CSA_HOME/_CSA_3_2_0_installation
$CSA_HOME/_CSA_4_0_0_installation
$CSA_HOME/_CSA_4_0_1_installation
$CSA_HOME/_CSA_4_1_0_installation
$CSA_HOME/jre
or
$CSA_HOME/openjre
$CSA_HOME/node.js
$CSA_HOME/_CSA_4_60_0_installation/Backup/node.js
)$CSA_HOME/portal
$CSA_HOME/_CSA_4_60_0_installation/Backup/portal
)$CSA_HOME/Tools
$CSA_HOME/_CSA_4_60_0_installation/Backup/Tools/
)$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/deployments/*.war
$CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/*.war
)$CSA_HOME/jboss-as-7.1.1.Final/domain/servers/<server_name>/deployments/*.war
$CSA_HOME/_CSA_4_60_0_installation/Backup/domain/*.war
)Before CSA is upgraded, you may need to back up customized files if they are not automatically restored or backed up by the upgrade installer. Automatically restored files retain their customizations after the upgrade. Automatically backed up files have been saved to the backup directory but must be manually restored after the upgrade.
This section lists customized files by location. The customized files listed are based on the features that you selected as being configured, customized, or used prior to the upgrade (if you want to configure, customize, or use any of these features for the first time, refer to the following guides for more information: Cloud Service Automation Configuration Guide, Cloud Service Management Console Help, Cloud Service Automation Content Archive Tool, Cloud Service Automation Provider Configuration Tool, Cloud Service Automation Customizing the Marketplace Portal, Cloud Service Automation Integration with ArcSight Logger, Configuring CSA to Work with Oracle RAC). For files listed by feature and the actions to perform, refer to Recustomize CSA. For a list of customized files that must be manually backed up, refer to Initial Setup.
Caution:
If you customized a file that is not listed here, you must manually back up this file (to a directory outside of %CSA_HOME%
$CSA_HOME
) before running the upgrade installer and then manually restore the file after running the upgrade installer. If you do not back up this file, the customizations will be lost after running the upgrade installer.
File | Action |
---|
standalone.conf.batstandalone.conf | Automatically backed up, manually restore |
vault.batvault.sh | Automatically restored |
File | Action |
---|
*.crt | Automatically restored |
.keystore | Automatically restored |
standalone.xml | Automatically backed up; however, you must manually restore this file (for all features). |
File | Action |
---|
message.properties | Automatically restored |
File | Action |
---|
index.jsp | Automatically restored |
File | Action |
---|
config.json | Automatically backed up, manually restore |
File | Action |
---|
message.properties | Automatically backed up, manually restore |
File | Action |
---|
*.gif, *.jpeg, *.jpg, *.png | Automatically restored |
File | Action |
---|
*.jsp | Automatically backed up, manually restore |
File | Action |
---|
applicationContext-security.xml |
Automatically backed up, manually restore (for the following feature(s): single sign-on, common access card, CSA seeded users, SiteMinder) |
ssologout.jsp | Automatically backed up, manually restore |
web.xml |
Automatically backed up, manually restore (for the following feature(s): Cloud Service Management Console: session timeout , SiteMinder) |
File | Action |
---|
csa.properties | Automatically restored |
log4j.properties | Automatically backed up, manually restore to log4j2.xml |
File | Action |
---|
* | Automatically backed up, manually restore |
File | Action |
---|
csa-consumer-users.properties | Automatically backed up, manually restore |
csa-provider-users.properties | Automatically backed up, manually restore |
integrationusers.properties | Automatically backed up, manually restore |
File | Action |
---|
applicationContext.properties | Automatically backed up, manually restore |
applicationContext.xml | Automatically backed up, manually restore |
applicationContext-common.xml | Automatically restored |
applicationContext-security.xml | Automatically backed up, manually restore |
File | Action |
---|
index.html | Automatically restored |
File | Action |
---|
* | Automatically backed up, manually restore |
File | Action |
---|
* | Automatically restored |
File | Action |
---|
* | Automatically backed up, manually restore |
File | Action |
---|
rb.json | Automatically backed up, manually restore |
File | Action |
---|
* | Automatically backed up, manually restore |
File | Action |
---|
main.css | Automatically backed up, manually restore |
File | Action |
---|
main.css | Automatically backed up, manually restore |
File | Action |
---|
main.css | Automatically backed up, manually restore |
File | Action |
---|
config.properties | Automatically backed up, manually restore |
File | Action |
---|
config.properties | Automatically backed up, manually restore |
File | Action |
---|
db.properties | Automatically backed up, manually restore |
HPOOInfoInput.xml | Automatically backed up, manually restore |
File | Action |
---|
config.properties | Automatically backed up, manually restore |
provider.xml | Automatically backed up, manually restore |
File | Action |
---|
config.properties | Automatically backed up, manually restore |
File | Action |
---|
cacerts | manually back up, manually restore |
java.security | manually back up, manually restore |
File | Action |
---|
*.jar (for dynamic queries) | manually back up, manually restore |
*.jsp (custom for the CSA dashboard defined in the %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\deployments\csa.war\dashboard\
$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/deployments/csa.war/dashboard/config.json configuration file) |
manually back up, manually restore |
keystore file (defined by the certificate-key-file property of the connector attribute in %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\configuration\standalone.xml$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/configuration/standalone.xml ) |
manually back up, manually restore |
Before you back up and upgrade your remote installation of the Marketplace Portal, on the system running the Cloud Service Management Console, upgrade to CSA 4.60, if you have not already done so.
On the remote system, do the following:
Create a directory named
C:\csabackup\
. /tmp/csabackup/
.
Copy the
%CSA_HOME%\portal\
$CSA_HOME/portal/
directory to
C:\csabackup\
. /tmp/csabackup/
.
Copy the
%CSA_HOME%\jre\lib\security\cacerts
$CSA_HOME/jre/lib/security/cacerts
file to
C:\csabackup\
./tmp/csabackup/
.
Copy the JDBC drivers from the system running
the Cloud Service Management Console (in
%CSA_HOME%\jboss-as\modules\com\oracle\ojdbc6\main\
)
$CSA_HOME/jboss-as/modules/com/oracle/ojdbc6/main/
)
to the remote system (to a directory outside of the
%CSA_HOME%
$CSA_HOME
directory). For example, copy ojdbc*.jar
and ora*.jar
to
C:\csabackup\jdbc\
. /tmp/csabackup/jdbc/
.
Before you run the upgrade installer, the following steps must be completed.
The following files must be manually backed up outside of %CSA_HOME%
$CSA_HOME
(these files are not automatically restored nor backed up by the upgrade installer):
<csa_jre>\lib\security\<csa_jre>/lib/security/cacerts
<csa_jre>\lib\security\<csa_jre>/lib/security/java.security
The keystore file defined by the certificate-key-file property of the connector attribute in %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\configuration\standalone.xml$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/configuration/standalone.xml
if you are not using the default keystore file (the default keystore file, %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\configuration\.keystore$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/configuration/.keystore
, is automatically backed up and restored)
Any .jar
files used by dynamic query scripts
Any Java server page (.jsp
) files created for the CSA dashboard and saved in a directory within the CSA 4.2x4.10 installation but not in a directory whose content is backed up by the upgrade installer (the directory where the Cloud Service Management Console expects to find these files is defined in the %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\deployments\csa.war\dashboard\$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/deployments/csa.war/dashboard/config.json
configuration file)
You MUST back up all files that you have created, customized, or manually installed in the %CSA_HOME%
$CSA_HOME
installation directory that are not automatically restored or backed up by the upgrade installer (see Customized Files Affected by the Upgrade for a list of customized files and the action performed during the upgrade). These files should be backed up outside of %CSA_HOME%
$CSA_HOME
.
Caution: You MUST back up all files that you have customized with undocumented changes in the %CSA_HOME%
$CSA_HOME
installation directory. Files with undocumented customizations may not be backed up and must be manually restored.
You must back up these files to preserve them. While the upgrade installer will back up some files and directories, it does not back up all files and directories. If the upgrade installer fails before it backs up the selected files and directories, these files and directories may be deleted or corrupted.
Examples of files that you may have created, customized, or manually installed that may not be automatically backed up include custom graphic files, Oracle JDBC drivers, and jar files used by custom widgets or dynamic query scripts.
Note:
If you are not sure what files may have been created, customized, or manually installed in the CSA installation directory, back up the entire %CSA_HOME%$CSA_HOME
directory.
Caution:
Back up files outside of the CSA installation directory (%CSA_HOME%
$CSA_HOME
). The existing CSA installation directory and all of its contents are deleted during upgrade.
Caution:
Do not remove any directories in %CSA_HOME%
$CSA_HOME
. Doing so may cause the upgrade to fail.
Back up the database.If you have not already done so, back up the database used by CSA 4.2x4.10.
Caution: If the upgrade installer fails, the database may be corrupted.
If it exists, back up the registry file (outside of %CSA_HOME%
).$CSA_HOME
). The registry file name and location is: C:\Program Files\Zero G Registry\.com.zerog.registry.xml
/home/csauser/.com.zerog.registry.xml
or /var/.com.zerog.registry.xml
Caution: If the upgrade installer fails, the registry file may be corrupted or deleted.
If you mounted a file system within the CSA installation directory (for example, within $CSA_HOME
), you must unmount the file system. The upgrade installer cannot remove the mounted file system during the upgrade.
Caution: The upgrade will fail if you do not unmount the file system.
The User should ensure that there are no files owned by the root
in the Operations Orchestration installation folder or in any sub-folder. If there are any such files, you should change the ownership and group to match the ownership and group of the other files. For example, If files with root
ownership exist, then the upgrade will fail, destroying the Operations Orchestration installation without the possibility to rollback the changes.
Create a database instance, user, and schema for the embedded Operations Orchestration:
Work with the database administrator to create a database that is used by the embedded Operations Orchestration. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
You must provide the service (global database) name of this database when prompted for the Operations Orchestration database information during the upgrade of CSA.
Create a new database for Operations Orchestration (for example, csaoodb).
As of the release date of the CSA software (listed at the top of this guide), the mandatory database options for the Microsoft SQL Server for Operations Orchestration are:
Caution: You should verify the latest mandatory options and follow the instructions in the HPE Operations Orchestration Database Guide when creating the Operations Orchestration database.
Create a new user for the Operations Orchestration database (for example, csaoodbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Operations Orchestration database (for example, csaoodbuser
).
For example, run the following commands to create the csaoodbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaoodb;
CREATE LOGIN csaoodbuser WITH PASSWORD = '<csaoodbuser_password>';
CREATE USER csaoodbuser FOR LOGIN csaoodbuser;
ALTER ROLE db_datareader ADD MEMBER csaoodbuser;
ALTER ROLE db_datawriter ADD MEMBER csaoodbuser;
ALTER ROLE db_owner ADD MEMBER csaoodbuser;
Create a new database for Operations Orchestration. Grant the Operations Orchestration database user all rights to this database. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
Caution: The database name 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, if you create
a database named csaoodb
and
an Operations Orchestration
user named csaoodbuser
, from the psql prompt, enter
the following commands:
create database csaoodb with owner=csaoodbuser connection limit=-1;
grant all on database csaoodb to csaoodbuser;
You must provide this database name, database username and, user's password when prompted for the Operations Orchestration database information during the upgrade of CSA.
A database user, used by the embedded Operations Orchestration, is needed when upgrading CSA. Work with the database administrator to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The database name and 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 csaoodbuser user:
Create user csaoodbuser identified by csaoodbuser default tablespace system temporary tablespace temp quota unlimited on system account unlock;
Grant CONNECT to csaoodbuser;
Grant CREATE VIEW, CREATE SEQUENCE, CREATE TABLE, CREATE PROCEDURE to csaoodbuser;
Commit;
You must provide this database username and password when prompted for the Operations Orchestration database information during the upgrade of CSA.
Create an Operations Orchestration database user (for example, csaoodbuser
). The Operations Orchestration database user, used by the embedded Operations Orchestration, is required. This user should inherit rights from parent roles and have superuser privileges.
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 csaoodbuser login password '<csaoodbuser_password>' superuser inherit;
This is the user to whom you will grant access to the Operations Orchestration database when you create this database.
Create a database instance and user for the embedded Operations Orchestration:
Caution: The database name and 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.
Work with the database administrator to create a database that is used by the embedded Operations Orchestration. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
You must provide the service (global database) name of this database when prompted for the Operations Orchestration database information during the upgrade of CSA.
Create a new database for Operations Orchestration (for example, csaoodb).
As of the release date of the CSA software (listed at the top of this guide), the mandatory database options for the Microsoft SQL Server for Operations Orchestration are:
Caution: You should verify the latest mandatory options and follow the instructions in the HPE Operations Orchestration Database Guide when creating the Operations Orchestration database.
Create a new user for the Operations Orchestration database (for example, csaoodbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Operations Orchestration database (for example, csaoodbuser
).
For example, run the following commands to create the csaoodbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaoodb;
CREATE LOGIN csaoodbuser WITH PASSWORD = '<csaoodbuser_password>';
CREATE USER csaoodbuser FOR LOGIN csaoodbuser;
ALTER ROLE db_datareader ADD MEMBER csaoodbuser;
ALTER ROLE db_datawriter ADD MEMBER csaoodbuser;
ALTER ROLE db_owner ADD MEMBER csaoodbuser;
Create a new database for Operations Orchestration. Grant the Operations Orchestration database user all rights to this database. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
Caution: The database name 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, if you create
a database named csaoodb
and
an Operations Orchestration
user named csaoodbuser
, from the psql prompt, enter
the following commands:
create database csaoodb with owner=csaoodbuser connection limit=-1;
grant all on database csaoodb to csaoodbuser;
You must provide this database name, database username and, user's password when prompted for the Operations Orchestration database information during the upgrade of CSA.
Create a database instance and user for the embedded Operations Orchestration:
Log in to psql as the postgres user. Enter the following:
psql -h localhost -U postgres -d template1
When prompted, enter the password for the postgres user.
Caution: The database name and 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 csaoodbuser user:
Create user csaoodbuser identified by csaoodbuser default tablespace system temporary tablespace temp quota unlimited on system account unlock;
Grant CONNECT to csaoodbuser;
Grant CREATE VIEW, CREATE SEQUENCE, CREATE TABLE, CREATE PROCEDURE to csaoodbuser;
Commit;
You must provide this database username and password when prompted for the Operations Orchestration database information during the upgrade of CSA.
Create an Operations Orchestration database user (for example, csaoodbuser
). The Operations Orchestration database user, used by the embedded Operations Orchestration, is required. This user should inherit rights from parent roles and have superuser privileges.
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 csaoodbuser login password '<csaoodbuser_password>' superuser inherit;
This is the user to whom you will grant access to the Operations Orchestration database when you create this database.
Work with the database administrator to create a database that is used by the embedded Operations Orchestration. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
You must provide the service (global database) name of this database when prompted for the Operations Orchestration database information during the upgrade of CSA.
Create a new database for Operations Orchestration (for example, csaoodb).
As of the release date of the CSA software (listed at the top of this guide), the mandatory database options for the Microsoft SQL Server for Operations Orchestration are:
Caution: You should verify the latest mandatory options and follow the instructions in the HPE Operations Orchestration Database Guide when creating the Operations Orchestration database.
Create a new user for the Operations Orchestration database (for example, csaoodbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Operations Orchestration database (for example, csaoodbuser
).
For example, run the following commands to create the csaoodbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaoodb;
CREATE LOGIN csaoodbuser WITH PASSWORD = '<csaoodbuser_password>';
CREATE USER csaoodbuser FOR LOGIN csaoodbuser;
ALTER ROLE db_datareader ADD MEMBER csaoodbuser;
ALTER ROLE db_datawriter ADD MEMBER csaoodbuser;
ALTER ROLE db_owner ADD MEMBER csaoodbuser;
Create a new database for Operations Orchestration. Grant the Operations Orchestration database user all rights to this database. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
Caution: The database name 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, if you create
a database named csaoodb
and
an Operations Orchestration
user named csaoodbuser
, from the psql prompt, enter
the following commands:
create database csaoodb with owner=csaoodbuser connection limit=-1;
grant all on database csaoodb to csaoodbuser;
You must provide this database name, database username and, user's password when prompted for the Operations Orchestration database information during the upgrade of CSA.
Exit psql. From the psql prompt, enter the following:
\q
You must provide this database instance, username, and password when prompted for the HP OO database configuration during the upgrade of CSA.
Create a database instance, user, and schema for the Identity Management component. Work with the database administrator to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The database name and 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 csaidmdbrole role and csaidmdbuser user:
Create user csaidmdbuser identified by csaidmdbuser;
Create role csaidmdbrole;
Grant CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE ANY SYNONYM to csaidmdbuser;
Grant csaidmdbrole to csaidmdbuser;
Alter user csaidmdbuser default role csaidmdbrole;
You must provide this database's service (global database) name, database username and, user's password when prompted for the Identity Management component database information during the upgrade of CSA.
An Identity Management component database and database user are needed when upgrading CSA.
Caution: The database name and 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.
Connect to the new database created for the Identity Management component (for example, csaidmdb
).
Caution:
IdM database only supports 'Case Insensitive' Collation.
The IdM database collation and the tempDB collation in SQL server must be the same.
Create a new user for the Identity Management component database (for example, csaidmdbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Identity Management component database (for example, csaidmdbuser
).
For example, run the following commands to create the csaidmdbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaidmdb;
-- or connect to csaidmdb in another way CREATE LOGIN csaidmdbuser WITH PASSWORD = '<csaidmdbuser_password>';
CREATE USER csaidmdbuser FOR LOGIN csaidmdbuser;
ALTER ROLE db_datareader ADD MEMBER csaidmdbuser;
ALTER ROLE db_datawriter ADD MEMBER csaidmdbuser;
ALTER ROLE db_owner ADD MEMBER csaidmdbuser;
Create a new database for the Identity Management component. Grant the Identity Management component database user (if you configured this user) or CSA database user all rights to this database.
Caution: The database name 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, to create a database named csaidmdb
granting access to the Identity Management component database user named csaidmdbuser
, from the psql prompt, enter the following commands:
create database csaidmdb with owner=csaidmdbuser connection limit=-1;
grant all on database csaidmdb to csaidmdbuser;
If you did NOT create an Identity Management component database user named csaidmdbuser
, create a database named csaidmdb
and grant access to this database to the CSA database user named csadbuser
. From the psql prompt, enter the following commands:
create database csaidmdb with owner=csadbuser connection limit=-1;
grant all on database csaidmdb to csadbuser;
You must provide this database name, database username and, user's password when prompted for the Identity Management component database information during the upgrade of CSA.
Create a new database user (optional) and database (required) for the Identity Management component:
Log in to psql as the postgres user. Enter the following:
psql -h localhost -U postgres -d template1
When prompted, enter the password for the postgres user.
Optionally, create an Identity Management component database user (for example, csaidmdbuser
). This user should inherit rights from parent roles and be a superuser.
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 csaidmdbuser login password '<csaidmdbuser_password>' superuser inherit;
This is the user to whom you will grant access to the Identity Management component database when you create this database. If you do not create this user, you can use the CSA database user (for example, csadbuser
) instead.
Caution: The database name and 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.
Connect to the new database created for the Identity Management component (for example, csaidmdb
).
Caution:
IdM database only supports 'Case Insensitive' Collation.
The IdM database collation and the tempDB collation in SQL server must be the same.
Create a new user for the Identity Management component database (for example, csaidmdbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Identity Management component database (for example, csaidmdbuser
).
For example, run the following commands to create the csaidmdbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaidmdb;
-- or connect to csaidmdb in another way CREATE LOGIN csaidmdbuser WITH PASSWORD = '<csaidmdbuser_password>';
CREATE USER csaidmdbuser FOR LOGIN csaidmdbuser;
ALTER ROLE db_datareader ADD MEMBER csaidmdbuser;
ALTER ROLE db_datawriter ADD MEMBER csaidmdbuser;
ALTER ROLE db_owner ADD MEMBER csaidmdbuser;
Create a new database for the Identity Management component. Grant the Identity Management component database user (if you configured this user) or CSA database user all rights to this database.
Caution: The database name 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, to create a database named csaidmdb
granting access to the Identity Management component database user named csaidmdbuser
, from the psql prompt, enter the following commands:
create database csaidmdb with owner=csaidmdbuser connection limit=-1;
grant all on database csaidmdb to csaidmdbuser;
If you did NOT create an Identity Management component database user named csaidmdbuser
, create a database named csaidmdb
and grant access to this database to the CSA database user named csadbuser
. From the psql prompt, enter the following commands:
create database csaidmdb with owner=csadbuser connection limit=-1;
grant all on database csaidmdb to csadbuser;
Exit psql. From the psql prompt, enter the following:
\q
You must provide this database name, database username and, user's password when prompted for the Identity Management component database information during the upgrade of CSA.
%CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\bin
.Run the following command:
jboss-cli.bat --connect command=:shutdown
Navigate to Start > Administrative Tools > Services.
Right-click on the HP Marketplace Portal service and select Stop.
Run the following commands:
service csa stop
service mpp stop
Install Operations Orchestration to the correct version and patch level. See Cloud Service Automation System and Software Support Matrix for version requirements, 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)..
Upgrade Operations Orchestration to version 10.21.0000. Then, update version 10.21.0001 by installing hotfix HF_27629.
For your convenience, the hotfix is delivered with the CSA installation media. Locate the readme file for this hotfix and follow the instructions on how to upgrade Operations Orchestration.
Alternatively, you can download the hotfix from https://patch-central.corp.hp.com/crypt-web/protected/viewContent.do?patchId=HF_27629.
If you have upgraded Operations Orchestration, you may need to upgrade your content packs. Refer to the Operations Orchestration release notes for more information.
Complete this step for Operations Orchestration 10.21.0001 only.
Export Operations Orchestration's certificate from Operations Orchestration's truststore and, if Operations Orchestration and CSA are not installed on the same system, copy the certificate to the CSA system. This certificate will be imported into CSA's truststore by the CSA installer. TLS must be configured between CSA and Operations Orchestration.
For example, do the following:
Run the following command:
Windows
.\java\bin\keytool -export
-alias tomcat -file C:\oo.crt
-keystore .\Central\var\security\key.store -storepass changeit
Linux
./java/bin/keytool -export
-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 Operations Orchestration system to the system running CSA.Export the certificate from the truststore of Operations Orchestration as it is needed during the upgrade process. Do the following:
Open a command prompt and navigate to a directory outside of %CSA_HOME%$CSA_HOME
and the embedded Operations Orchestration installation (for example, the embedded Operations Orchestration may be installed in C:\Program Files\Hewlett-Packard\Operations Orchestration\
) in which you will store the certificate file (for example, create the directory C:\tmp
and store the certificate file in this directory).
Run the following command:
"<csa_jre>\bin\keytool" ‑exportcert ‑keystore "C:\Program Files\Hewlett-Packard\Operations Orchestration\central\var\security\key.store" ‑alias tomcat ‑file .\<filename> -storepass changeit$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore /usr/local/hp/csa/OO/central/var/security/key.store ‑alias tomcat ‑file ./<filename> -storepass changeit
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed and <file_name> is a unique filename given to the certificate file that will be imported into CSA version 4.60 later during the upgrade process.
Because the JRE has been upgraded in this release, you must export the certificate from the truststore of CSA version 4.2x4.10 so that you may import it (at a later time during the upgrade process) into the truststore of CSA version 4.60.
To export the certificate, do the following:
Open a command prompt and navigate to a directory outside of %CSA_HOME%$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_HOME/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\standalone\configuration\.keystore" ‑alias <alias> ‑file .\<filename>$CSA_JRE_HOME/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as/standalone/configuration/.keystore ‑alias <alias> ‑file ./<filename>
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed, .keystore
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/standalone/configuration/standalone.xml
, <alias> is the name used by the CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into CSA version 4.60 later during the upgrade process.
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed, .keystore
is the keystore file defined by the certificate-key-file
property of the connector attribute in %CSA_HOME%\jboss-as\standalone\configuration\standalone.xml
, $CSA_HOME/jboss-as/standalone/configuration/standalone.xml
, <alias> is the name used by the CSA server keystore to identify the SSL certificate, and <file_name> is a unique filename given to the certificate file that will be imported into CSA version 4.60 later during the upgrade process.
For example, run the following command if the JRE used by CSA version 4.2x4.10 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/standalone/configuration/.keystore ‑alias csa ‑file ./csa.cert"%CSA_HOME%\jre\bin\keytool" ‑exportcert ‑keystore "%CSA_HOME%\jboss-as\standalone\configuration\.keystore" ‑alias csa ‑file .\csa.cert$CSA_HOME/jre/bin/keytool ‑exportcert ‑keystore $CSA_HOME/jboss-as/standalone/configuration/.keystore ‑alias csa ‑file ./csa.cert
Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
Caution: The upgrade will fail if any program is accessing an CSA file or directory.
Note:
Upgrade log files are written to the
%CSA_HOME%\_CSA_4_60_0_installation\Logs
$CSA_HOME/_CSA_4_60_0_installation/Logs
directory.
setup.zip
file. Go to the directory to which the files have been extracted and run the setup.exe
upgrade file.Verify that you want to upgrade to CSA version 4.60 of the Marketplace Portal and click OK.
Select the JRE used by CSA.
Use OpenJDK JRE if you want to use the JRE that is installed with CSA version 4.60. You must manually export the CSA certificate from the existing truststore and import it into the truststore that is installed with CSA.
Use Oracle JRE if you want to use an Oracle JRE. You must manually export the 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 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.
Select Yes to install CSA database components and upgrade the CSA database schema then click Next.
Select the environment in which CSA is running 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.Finaljboss-as\standalone\configuration\standalone.xml
).
If you select cluster, the database instance information is read from
the JBoss server's domain.xmlstandalone-full-ha.xml
file
(%CSA_HOME%\jboss-as-7.1.1.Final\domainjboss-as\standalone\configuration\domain.xmlstandalone-full-ha.xml
).
Enter the CSA database user password and click Next.
If you configured a reporting database user, enter the reporting database user and password and click Next. If you did not configure a reporting database user, click Next.
Define the Identity Management component database instance and click Next.
Field Name | Description |
---|---|
HP Identity Management component Database Host | The hostname or IP address of the server where the Identity Management component database is located. |
HP Identity Management component Database Name | The service name of the database used by Identity Management component. |
HP Identity Management component Database Port | The Identity Management component database port number, such as 143315215432. |
HP Identity Management component Database User Name | The user name of the database user you configured for the Identity Management component database. |
HP Identity Management component Database Password | The password for the Identity Management component database user. |
By default, Single Sign-On (SSO) is included with CSA and is enabled. The SSO that is included with CSA can only be used when launching an application, such as Operations Orchestration or HPE IT Business Analytics, from the Cloud Service Management Console. Refer to the Cloud Service Automation Configuration Guide and SSO documentation for more information on integrating SSO with the application.
If you do not want to use SSO, you can disable it.
You MUST disable Single Sign-On if you are installing CSA in a FIPS 140-2 compliant environment of if you plan on integrating with CA SiteMinder.
If enabled, enter the domain name of the network to which the server on which you are installing CSA belongs and click Next.
Applications launched from the Cloud Service Management Console and Marketplace Portal with which you want to use SSO must be installed on systems that belong to this domain.
Specify your integration with Operations Orchestration.
If you are integrating with Operations Orchestration 10.21.0001 and Operations Orchestration 9.07, click Configure connection to a running HP OO server and click Next.enter 1 (Configure connection to a running HP OO server) and select Enter. The upgrade installer requires additional information to complete the integration with Operations Orchestration 10.21.0001.
Operations Orchestration 10.21.0001 must be installed and running in order to complete the upgrade of CSA.
If you are integrating with only Operations Orchestration 9.07do not want to integrate with Operations Orchestration, click Do not configure HP OO connection and click Next.enter 3 (Do not configure HP OO connection and select Enter. The upgrade installer does not require any additional information.
If you are integrating with the embedded Operations Orchestration, click Configure embedded HP OO server and click Next.enter 2 (Configure embedded HP OO server) and select Enter. The upgrade installer requires additional information to complete the integration.
If you are integrating with an existing embedded Operations Orchestration, enter the HP OO server password and HP OO server certificate and click Next.enter the HP OO server password and HP OO server certificate and select Enter.
Caution:
You will get this error:
CSA Properties file is not valid
--------------------------------
File /home/builder/csa_upg/jboss-as/standalone/deployments/csa.war/WEB-INF/clas
ses/csa.properties contains duplicated properties with values:
Property "embedded.oo.root.dir" is defined with different values:
""/home/builder/csa_upg/OO""
""/home/builder/csa_upg/OO2""
See /home/builder/csa46/csa-properties-validation.log for more details.
OK -- exit installer
When this occurs, you have to manually remove the obsolete root directory:
embedded.oo.root.dir=
and run the CSA upgrade installer again.
csauser
.
If the Embedded Operations Orchestration Upgrade Service uses the root user
, then the installer will not function
properly and the Operations Orchestration upgrade will fail.Define the Operations Orchestration 10.21.0001 instance with which CSA is to be integrated. Enter the following information and click Next.
Field Name | Description |
---|---|
HP OO Hostname |
The
fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate Operations Orchestration's certificate. The hostname is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured).
|
HP OO Port | The port number used to communicate with Operations Orchestration, such as 8443. The port number is used to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration. By default, Operations Orchestration uses this port and port 8080. Applications running on the system on which Operations Orchestration is installed should not be using these ports. |
HP OO User |
The
name of the user who logs in to Operations Orchestration Central. HP recommends that you use the |
HP OO Password | The password used by the HP OO user to log in to Operations Orchestration Central. |
HP OO Certificate File | The filename and location of Operations Orchestration's certificate from Operations Orchestration's truststore on the CSA system. If you have not already done so, export Operations Orchestration's certificate and copy it to the CSA system (see the Initial Setup section in this guide for more information). |
Note:
This information is used to set the Operations Orchestration properties in the csa.properties
file and import Operations Orchestration's certificate into CSA's truststore. Refer to the Cloud Service Automation Configuration Guide for more information about these properties.
Enter the HP OO installation folder. This is the location in which to install the embedded Operations Orchestration.
Define the user and port used by the embedded Operations Orchestration. Enter the following information and click Next.
Field Name | Description |
---|---|
HP OO User Name |
This is the name of the user used for provisioning topology designs. This user is given the ADMINISTRATOR and SYSTEM_ADMIN roles. The recommended username is admin. |
HP OO User Password (and Confirm Password) | This is the password used by the embedded Operations Orchestration for the user who provisions topology designs. The recommended password is cloud. |
HP OO Port | The embedded Operations Orchestration port number, such as 8445. By default, Operations Orchestration uses this port and port 8080. Applications running on the system on which CSA and the embedded Operations Orchestration are installed should not be using these ports. |
Define the database instance used by the embedded Operations Orchestration. Enter the following information and click Next.
Field Name | Description |
---|---|
Microsoft SQL ServerOraclePostgreSQL Database Host |
This is the hostname or IP address of the server where the embedded Operations Orchestration database is located. |
Microsoft SQL ServerOraclePostgreSQL Database Port |
This is the embedded Operations Orchestration database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
HP OO Database NameOracle HP OO service name |
This is the service (global database) name of the database instance used by the embedded Operations Orchestration. You configured this database instance in the Initial Setup section of this guide. |
HP OO Database User Name |
This is the username of the database user you configured (in the Initial Setup section of this guide) for the Operations Orchestration database. |
HP OO Database Password |
This is the password for the Operations Orchestration database user. |
By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) can be installed with CSA. You can choose to deploy this content during upgrade (making the sample service designs available in the Designs area of the Cloud Service Management Console) or deploy the content at a later time (refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information).
To deploy the sample content during the CSA installation process, select Install additional provider integration service designs, components and content and click Next.
To deploy the sample content at a later time, select Skip content installation and click Next.
If you choose to skip content installation, you can install the content at a later time by running the Cloud Content Capsule Installer. Refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information.
Note: If you chose not to install the database components, this dialog will not display.
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 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
root user
and log in as csauser
.Check the values of the CSA_HOME, PS1, and TITLEBAR environment variables. If they are set, verify that they do not contain any escape sequences. If any of these variables contain an escape sequence, the variable will cause the installer to fail. The variable must either be reset to a value that does not contain an escape sequence or must be unset.
Source the startup file in
which you set the CSA_HOME and PATH
environment variables. If you edited .bash_profile.bashrc
,
enter the following:
. .bash_profile.bashrc
setup.bin
) to the system and go to the directory in which it has been copied.Verify that setup.bin
is owned by csauser
and that csauser
has full permissions to the file. If necessary,
do the following:
Enter the following commands:
chown csauser setup.bin
chmod 755 setup.bin
root user
and then log in as csauser
.Run the setup.bin
upgrade file as the csauser
.
Note: You must run setup.bin
as the csauser
. If you
install CSA as any other user,
you may not be able to run CSA .
As the csauser
, enter the following:
./setup.bin
Introduction
Read the Introduction and click enter to continue with the installation.
License Agreement
Read the license agreement. Click enter after reading each page to scroll through the entire agreement.
DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT?
Select Y and enter to accept the license agreement and continue with the installation. Type N and enter if you do not accept the license agreement and to exit the installation.
Stop CSA
Verify that you have stopped CSA version 4.2x4.10 and click enter.
CSA Installation Detected
Select the environment in which
CSA
is running.
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.Finaljboss-as/standalone/configuration/standalone.xml
).
If you select cluster, the database instance information is read from
the JBoss server's domain.xmlstandalone-full-ha.xml
file
($CSA_HOME/jboss-as-7.1.1.Final/domainjboss-as/standalone/configuration/domain.xmlstandalone-full-ha.xml
).The installer detects that you are upgrading a remote installation of the Marketplace Portal. Click enter to continue.
Select appropriate JRE
Select the JRE used by CSA and click Enter.
Because the JRE must be upgraded for this release, you cannot use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with CSA version 4.60. You must manually export the CSA certificate from the existing truststore and import it into the truststore that is installed with CSA.
Select Oracle JRE if you want to use an Oracle JRE. Then, select the location in which you installed this JRE. You must manually export the 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
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
1 (Existing JRE) 2 (Open JRE) 3 (Oracle JRE),
select the location in which you installed this JRE,
and click enter.
Select the JRE used by CSA and click Enter.
Because the JRE must be upgraded for this release, you cannot use the existing JRE.
Select OpenJDK JRE if you want to use the JRE that is installed with CSA version 4.60. You must manually export the CSA certificate from the existing truststore and import it into the truststore that is installed with CSA.
Select Oracle JRE if you want to use an Oracle JRE. Then, select the location in which you installed this JRE. You must manually export the 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
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
1 (Existing JRE) 2 (Open JRE) 3 (Oracle JRE),
select the location in which you installed this JRE,
and click enter.
Warning: CSA JRE Home
Acknowledge that you will manually export the CSA certificate from the existing truststore and import it into the truststore that is installed with CSA version 4.60the Oracle JRE truststore. Select 1 and click enter.
Oracle JRE
Enter the directory in which the Oracle JRE is installed and click enter.
In this documentation, the directory in which the JRE is installed will be referred to as <csa_jre>
.
CSA Installation Detected
Verify
the database instance information and click enter.
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.
CSA Database User Password
Enter the CSA database user password and click enter.
Reporting User
Enter the CSA reporting database user and click enter. If you did not configure a reporting database user, click enter to continue.
If you entered a reporting database user, enter the CSA reporting database user password and click enter. If you did not enter a reporting database user, this option is not available.
Install Database Components?
Type 1 (Yes) to install CSA database components and upgrade the CSA database schema then click enter.
SSO Configuration
By default, Single Sign-On (SSO) is included with CSA and is enabled. The SSO that is included with CSA can only be used when launching an application, such as Operations Orchestration or HPE IT Business Analytics, from the Cloud Service Management Console. Refer to the Cloud Service Automation Configuration Guide and SSO documentation for more information on integrating SSO with the application.
If you do not want to use SSO, you can disable it.
To enable SSO, type 1 (Enable SSO) and click enter. To disable SSO, type 2 (Disable SSO) and click enter.
Enable SSO
If SSO is enabled, enter the domain name of the network to which the server on which you are installing CSA belongs and click enter.
Applications launched from the Cloud Service Management Console and Marketplace Portal with which you want to use SSO must be installed on systems that belong to this domain.
Operations Orchestration Configuration
Specify your integration with Operations Orchestration.
If you are integrating with Operations Orchestration 10.21.0001 and Operations Orchestration 9.07, click Configure connection to a running HP OO server and click Next.enter 1 (Configure connection to a running HP OO server) and select Enter. The upgrade installer requires additional information to complete the integration with Operations Orchestration 10.21.0001.
Operations Orchestration 10.21.0001 must be installed and running in order to complete the upgrade of CSA.
If you are integrating with only Operations Orchestration 9.07do not want to integrate with Operations Orchestration, click Do not configure HP OO connection and click Next.enter 3 (Do not configure HP OO connection and select Enter. The upgrade installer does not require any additional information.
If you are integrating with the embedded Operations Orchestration, click Configure embedded HP OO server and click Next.enter 2 (Configure embedded HP OO server) and select Enter. The upgrade installer requires additional information to complete the integration.
If you are integrating with an existing embedded Operations Orchestration, enter the HP OO server password and HP OO server certificate and click Next.enter the HP OO server password and HP OO server certificate and select Enter.
Caution:
You will get this error:
CSA Properties file is not valid
--------------------------------
File /home/builder/csa_upg/jboss-as/standalone/deployments/csa.war/WEB-INF/clas
ses/csa.properties contains duplicated properties with values:
Property "embedded.oo.root.dir" is defined with different values:
""/home/builder/csa_upg/OO""
""/home/builder/csa_upg/OO2""
See /home/builder/csa46/csa-properties-validation.log for more details.
OK -- exit installer
When this occurs, you have to manually remove the obsolete root directory:
embedded.oo.root.dir=
and run the CSA upgrade installer again.
csauser
.
If the Embedded Operations Orchestration Upgrade Service uses the root user
, then the installer will not function
properly and the Operations Orchestration upgrade will fail.Define the Operations Orchestration 10.21.0001 instance with which CSA is to be integrated. Enter the following information (select Enter after each entry).
Enter the HP OO hostname. This is the
fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate Operations Orchestration's certificate. The hostname is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured).
When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4]
or [::1]
.
admin
user.
This is the user that was configured for provisioning topology designs (typically, admin).Note:
This information is used to set the Operations Orchestration properties in the csa.properties
file and import Operations Orchestration's certificate into CSA's truststore. Refer to the Cloud Service Automation Configuration Guide for more information about these properties.
Operations Orchestration Installation Folder
Enter the HP OO installation folder. This is the location in which to install the embedded Operations Orchestration.
Operations Orchestration Database Configuration
Configure the database instance used by the embedded Operations Orchestration. Enter the following information (select Enter after each entry).
Operations Orchestration Port
Enter the embedded Operations Orchestration port number, such as 8445. By default, Operations Orchestration uses this port and port 8080. Applications running on the system on which CSA and the embedded Operations Orchestration are installed should not be using these ports.
Operations Orchestration User
Enter the HP OO user. This is the name of the user used for provisioning topology designs. This user is given the ADMINISTRATOR and SYSTEM_ADMIN roles. The recommended username is admin.
Operations Orchestration Password and Confirm Password
Enter the HP OO password. This is the password used by the embedded Operations Orchestration for the user who provisions topology designs. The recommended password is cloud.
Pre-Installation Summary
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 CSA services to start and stop the CSA process and the Marketplace Portal process.
Remove the old version of the CSA scripts. Enter the following:
rm /etc/init.d/csa
rm /etc/init.d/mpp
Go to the directory in which CSA is installed. For example:
cd /usr/local/hp/csa
Copy the new scripts
to the /etc/init.d
directory. Enter the following:
cp ./scripts/csa /etc/init.d
cp ./scripts/mpp /etc/init.d
cp ./scripts/elasticsearch /etc/init.d
Change permissions of the scripts. Enter the following:
chmod 755 /etc/init.d/csa
chmod 755 /etc/init.d/mpp
chmod 755 /etc/init.d/elasticsearch
Complete the following tasks:
If it exists, remove the
%CSA_HOME%\jboss-as-7.1.1.Final
$CSA_HOME/jboss-as-7.1.1.Final
directory.
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 CSA
is installed.
You must recustomize CSA for the features configured, customized, or used prior to the upgrade only (complete only the tasks for features that were configured, customized, or used prior to upgrade; if you want to configure, customize, or use any of these features for the first time, refer to the following guides for more information: Cloud Service Automation Configuration Guide, Cloud Service Management Console Help, Cloud Service Automation Content Archive Tool, Cloud Service Automation Provider Configuration Tool, Cloud Service Automation Customizing the Marketplace Portal, Cloud Service Automation Integration with ArcSight Logger, Configuring CSA to Work with Oracle RAC). If you did not select any features from the selection page, this section may be empty.
The following is the file that you may have customized if you updated the password of the CSA database user and the actions required when you upgrade CSA:
File | Action |
---|---|
standalone.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
standalone.xml |
|
---|---|
Action |
Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you may have customized if you updated the password of one or more seeded users and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext-security.xml |
Required. If this file was customized, you must recustomize this file (see table below for more information). |
csa-consumer-users.properties |
Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
csa-provider-users.properties |
Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
integrationusers.properties |
Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
applicationContext.properties |
Required. If this file was customized, you must recustomize this file (see table below for more information. |
Files, Actions, and Locations
applicationContext-security.xml | |
---|---|
Action |
Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
csa-consumer-users.properties | |
---|---|
Action |
Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60.No action required. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
csa-provider-users.properties | |
---|---|
Action |
Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60.No action required. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
integrationusers.properties | |
---|---|
Action |
Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60.No action required. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.properties | |
---|---|
Action |
Required. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade CSA:
Directory | Action |
---|---|
<theme_directory> |
Required. If you created a customized theme for the Marketplace Portal, you must manually copy these directories (one for the Marketplace Portal and one for the Identity Management component) and theirthis directory (for the Marketplace Portal) and its content from the backup directory to the CSA 4.60 directory (see table below for more information). |
Directories, Actions, and Locations
<theme_directory> (Marketplace Portal) | |
---|---|
Action | Required. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
<theme_directory> (Identity Management Component) | |
---|---|
Action |
Required. If you created a customized theme for the Marketplace Portal, you must recreate this theme by creating a new directory in the CSA 4.60 directory :
|
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the directory where you may have added customized widgets for the Marketplace Portal and the action required when you upgrade CSA:
Directory | Action |
---|---|
<iFRAME_URL_structure> | Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.60 directory (see table below for more information). |
Directory, Action, and Locations
<iFRAME_URL_structure> | |
---|---|
Action | Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you customized when integrating CSA with a Common Access Card (CAC) and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext.xml (Cloud Service Management Console) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-v0.xml (Identity Management component) | Required. This is a new file that must be customized (see table below for more information). |
csa.properties | No action required. |
java.security | Required. If this file was customized, you must recustomize this file (see table below for more information). |
standalone.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
java.security | No action required. |
Files, Actions, and Locations
applicationContext.xml (Cloud Service Management Console) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-v0.xml (Identity Management Component) | |
---|---|
Action | Required. This is a new file that requires customization. Refer to the Cloud Service Automation Configuration Guide for more information. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | N/A |
csa.properties | |
---|---|
Action | No action required. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\ $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\csa.war\WEB-INF\classes\ $CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/csa.war/WEB-INF/classes/ |
java.security | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | This file is not backed up. You should have manually backed this file up prior to running the upgrade installer. |
standalone.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you customized when configuring CSA to use a single sign-on (SSO) and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
hpssoConfiguration.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
hpssoConfiguration.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
applicationContext.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
hpssoConfiguration.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (default) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (pilot) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (<theme_directory>) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
rb.json | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
File | Action |
---|---|
web.xml |
Required. If this file was customized, you must recustomize this file (see table below for more information). |
hpssoConfig.xml |
Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-v0.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
web.xml | |
---|---|
Action |
Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\idm-service.war\WEB-INF\
|
hpssoConfig.xml | |
---|---|
Action |
Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\idm-service.war\WEB-INF\
|
applicationContext-v0.xml | |
---|---|
Action |
Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml | |
---|---|
Action |
Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring |
The following is a list of files that you customized when integrating CSA with SiteMinder and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext-security.xml (Cloud Service Management Console) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
web.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
ssologout.jsp | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
applicationContext-security.xml (Cloud Service Management Console) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
ssologout.jsp | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
web.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
rb.json | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (default) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (pilot) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (<theme_directory>) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you customized when integrating CSA with SiteMinder and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext-security.xml (Cloud Service Management Console) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
web.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
ssologout.jsp | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
applicationContext-security.xml (Cloud Service Management Console) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
ssologout.jsp | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
web.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
rb.json | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (default) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (pilot) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (<theme_directory>) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
If you customized the Marketplace Portal configuration file, the customizations have been merged with the upgraded file. Refer to the Cloud Service Automation Configuration Guide for more information about the configurable properties in this file.
File | Action |
---|
mpp.json | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
index.html | No action required. If this file was customized, the customizations have been restored. |
Files, Actions, and Locations
mpp.json | |
---|---|
Action | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
index.html | |
---|---|
Action | No action required. If this file was customized, the customizations have been restored. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
To start the Marketplace Portal service:
On the system running the remote Marketplace Portal, navigate to Start > Administrative Tools > Services.
Start the HP Marketplace Portal service.
On the system running the remote Marketplace Portal,
type service mpp start
.
The following tasks must be completed before CSA can be restarted:
If you generated or copied SSL certificates that are used by CSA, you must copy these files to the appropriate directory in CSA 4.60.
Note:
If the automatically generated self-signed certificate for CSA has expired, you may still be able to use the Cloud Service Management Console. However, you will not be able to use the Marketplace Portal or Identity Management component unless you disable the strictSSL
attribute in the Marketplace Portal's configuration file. If SSL must be enabled, you can generate another self-signed certificate or a Certificate Authority-signed certificate. If you generate a new certificate, you MUST import that certificate into CSA's JRE. Refer to the Configure SSL for Client Browsers section in the Cloud Service Automation Configuration Guide for more information.
The following is a list of files that you may have customized for SSL/security and the actions required when you upgrade CSA:
File | Action |
---|---|
certificate files | Required. Manually copy certificate files that do not use the .crt extension that are used by CSA from the backup directory to the CSA 4.60 directory (see table below for more information). |
cacerts | Required. (missing or bad snippet) |
Keystore file defined by the |
Required (if not using the default keystore file). Manually copy the custom keystore file back from the location outside of the %CSA_HOME% $CSA_HOME installation directory where you manually backed it up. |
standalone.xml |
Required (if not using the default keystore file). Manually copy the custom keystore file back from the location outside of the %CSA_HOME% $CSA_HOME installation directory where you manually backed it up. |
Files, Actions, and Locations
certificate files | |
---|---|
Action | Required. Manually copy certificate files that do not use the .crt extension that are used by CSA from the backup directory to the CSA 4.60 directory. Files that use the .crt extension are automatically restored. If you saved .crt files in a different directory, you must manually copy these files back after upgrade. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
cacerts | |
---|---|
Action | Required. (missing or bad snippet) |
File Location in CSA 4.60 |
where |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | This file is not backed up. |
Keystore file defined by the certificate-key-file property of the connector attribute in standalone.xml |
|
---|---|
Action | Required (if not using the default keystore file). Manually copy the keystore file back from the location outside of the %CSA_HOME% $CSA_HOME installation directory where you manually backed it up. If you are using the default keystore file (C:\Program Files\Hewlett-Packard\CSA\jboss-as\standalone\configuration\.keystore/usr/local/hp/csa/jboss-as/standalone/configuration/.keystore ), no action is required (the default keystore file is automatically backed up and restored). |
File Location in CSA 4.60 |
The file and its location are determined by the value defined by |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
If you are using a custom keystore file, this file is not backed up. The default keystore file is backed up to |
standalone.xml | |
---|---|
Action | If this file was customized, manually copy the custom keystore file back from the location outside of the CSA installation directory where you manually backed it up. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
Prior to running the upgrade installer, you should have exported the SSL certificate from the truststore of CSA version 4.2x4.10. Import this certificate and other application's certificates into the truststore of CSA version 4.60. Do the following:
If you did not export the SSL certificate from the truststore of CSA version 4.2x4.10, the truststore has been backed up to the %CSA_HOME%\_CSA_4_60_0_installation\Backup\security\keystores\$CSA_HOME/_CSA_4_60_0_installation/Backup/security/keystores/
directory. Follow the instructions in the Initial Setup section of this document to export CSA's SSL certificate from the backed up truststore (you will need to modify the location of the truststore in the command).
Import the CSA certificate into the new 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
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed, <alias> is the name used by the 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
Import the Operations Orchestration certificate into the new CSA truststore. Do the following:
If the root certificate of Operations Orchestration's Certificate Authority is stored in a file on this system, import that file. Otherwise, export Operations Orchestration's certificate from Operations Orchestration's truststore:
%ICONCLUDE_HOME%
(Windows)
or $ICONCLUDE_HOME
(Linux).Run the following command:
Windows
.\jre1.6\bin\keytool exportcert alias pas file C:\oo.crt keystore .\Central\conf\rc_keystore storepass bran507025
Linux
./jre1.6/bin/keytool ‑exportcert ‑alias pas ‑file /tmp/oo.crt
‑keystore ./Central/conf/rc_keystore ‑storepass bran507025
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 Operations Orchestration system
to the system running CSA
(in this example, the file is copied to
C:\
/tmp
).On the system running CSA, 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
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed.
If other applications, such as the database, LDAP, SMTP, Operations Orchestration Load Balancer, or 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 CSA version 4.60.
If you customized host or port values in the %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\configuration\$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/configuration/standalone.xml
file in a previous version of CSA, those customizations will not exist following the upgrade. Edit the %CSA_HOME%\jboss-as\standalone\configuration\$CSA_HOME/jboss-as/standalone/configuration/standalone.xml
file and make the necessary host and port customizations.
If you do not remember the customizations you made to the file, refer to the backed up copy in %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\configuration\$CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/configuration/
.
If you customized CSA files that are not documented as being customizable or customized CSA files with undocumented customizations, you will need to manually recustomize those files.
Caution:
All files that you have customized with undocumented changes in the %CSA_HOME%
$CSA_HOME
installation directory MUST BE MANUALLY RESTORED. If you followed all the steps in the Initial Setup section of this guide, you should have backed up these files before upgrading CSA.
Note:
The logger was upgraded to a new version in this release. The log4j.properties
file is not compatible with this new version. If you made undocumented manual customizations to log4j.properties
, you must manually update the log4j2.xml
file.
If you unmounted one or more shared file systems within the CSA installation directory before running the upgrade installer, remount these file systems after the upgrade installer has completed.
For security purposes, you must manually update the 5recentWidget mashup and every copy of this mashup for every organization that existed prior to upgrade. Do the following:
Create a temporary organization:
Copy the content of the 5recentWidget mashup from the temporary organization:
Select the 5recentWidget mashup and click edit.
Copy the text from the Content field.
For every organization (except the temporary organization you just created), do the following:
For the 5recentWidget mashup and every mashup that is a copy of the 5recentWidget mashup that has not been customized, do the following:
Select the mashup and click edit.
If you have not customized the 5recentWidget mashup, paste the content from the temporary organization's 5recentWidget mashup to this organization's 5recentWidget mashup. If you made a copy of the organization's 5recentWidget mashup but did not customize it, paste the contents from the temporary organization's 5recentWidget mashup to this mashup.
If you have customized the 5recentWidget mashup or made a copy of the 5recentWidget mashup and customized it, do the following:
render
function.data[i].name
in the function and change every occurrence of data[i].name
to htmlEncode(data[i].name) (except variable declarations). In the uncustomized 5recentWidget mashup, this content appears three times, but only two occurrences need to be updated (do not update the variable declaration).Add the following functions to the mashup (the content can be copied from the temporary organization's 5recentWidget mashup):
function htmlEncode(value){
//create a in-memory div, set its inner text (which jQuery automatically encodes)
//then grab the encoded contents back out. The div never exists on the page.
return $('<div/>').text(value).html();
}
function htmlDecode(value){
return $('').html(value).text();
}
Click Update.
After you have updated all organizations, delete the temporary organization:
After upgrade to CSA 4.60, if Enable HP SSO is selected during upgrade, and if the initString value in the %CSA_HOME%\jboss-as-7.1.1.Finaljboss-as\standalone\deployments\csa.war\WEB-INF\$CSA_HOME/jboss-as-7.1.1.Finaljboss-as/standalone/deployments/csa.war/WEB-INF/hpssoConfiguration.xml
file is detected to be the default value created during a previous install of CSA, the initString value is regenerated as a security measure. If you selected Install embedded HP OO during upgrade, the initString value will be configured in the embedded Operations Orchestration to enable HP SSO between CSA and Operations Orchestration. If you selected Use external HP OO during upgrade, and if the external Operations Orchestration had not already been configured for HP SSO, the upgrade process will attempt to update the external Operations Orchestration’s HP SSO configuration with the new initString value generated during install. Any other products that you had configured for HP SSO with CSA will need to be updated to share a common initString with CSA. After upgrade to CSA 4.60, you should review and update, as needed, the HP SSO configuration in Operations Orchestration and other integrated products. For more information on configuring HP SSO between CSA and other products, refer to the Cloud Service Automation Configuration Guide.
To restart the CSA and Marketplace Portal services:
On the server that hosts CSA, navigate to Start > Administrative Tools > Services.
Global Search is on by default in CSA 4.60. If you find that global search is off, you can re-enable global search by doing the following:
Right-click on the Elasticsearch 1.6.1 service and select Restart.
Wait for a minute for the Elasticsearch 1.6.1 service to restart, then right-click on HPE Search Service and select Restart.
Right-click on the Cloud Service Automation service and select Restart.
Right-click on the Marketplace Portal service and select Restart.
Right-click on the Operations Orchestration Central service and select Restart.
On the server that hosts CSA,
log in as csauser
and enter the following:
service csa restart
service mpp restart
As csauser
, start Operations Orchestration Central:
<embeddedHPOOinstallation>/central/bin/central stop
<embeddedHPOOinstallation>/central/bin/central start
For example, type /usr/local/hp/csa/OO/central/bin/central stop
.
/usr/local/hp/csa/OO/central/bin/central start
You must recustomize CSA for the features configured, customized, or used prior to the upgrade only (complete only the tasks for features that were configured, customized, or used prior to upgrade; if you want to configure, customize, or use any of these features for the first time, refer to the following guides for more information: Cloud Service Automation Configuration Guide, Cloud Service Management Console Help, Cloud Service Automation Content Archive Tool, Cloud Service Automation Provider Configuration Tool, Cloud Service Automation Customizing the Marketplace Portal, Cloud Service Automation Integration with ArcSight Logger, Configuring CSA to Work with Oracle RAC). If you did not select any features from the selection page, this section may be empty.
The following is the file that you may have customized for the Cloud Service Management Console and the actions required when you upgrade CSA:
File | Action |
---|---|
csa.properties | No action required. |
File, Actions, and Locations
csa.properties | |
---|---|
Action | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\ $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\csa.war\WEB-INF\classes\ $CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/csa.war/WEB-INF/classes/
|
The following is a list of files that you may have customized for the Cloud Service Management Console dashboard and the actions required when you upgrade CSA:
File | Action |
---|---|
*.jsp | Required. Manually copy the JSP files from the backup directory to the appropriate directory in CSA 4.60 directory (see table below for more information). |
config.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
messages.properties | Required. Manually copy the file from the backup directory to the CSA 4.60 directory (see table below for more information). |
index.jsp | No action required. |
Files, Actions, and Locations
*.jsp | |
---|---|
Action | Required. If you created custom Java server page (JSP) files for the CSA dashboard and saved them in a directory within the CSA 4.2x4.10 installation but not in a directory whose content is backed up by the upgrade installer, you should have backed up these files to preserve them. Otherwise, they will be deleted by the upgrade installer. Manually copy the JSP files from the backup directory to the appropriate directory in CSA 4.60 directory. |
File Location in CSA 4.60 | The directory where the Cloud Service Management Console expects to find these files, defined in the |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | The directory to which the JSP files were backed up, either manually or by the upgrade installer, depending on where the files were located in CSA 4.2x4.10. |
config.json | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
messages.properties | |
---|---|
Action | Required. Manually copy the file from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
index.jsp | |
---|---|
Action | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\custom-content\$CSA_HOME/jboss-as/standalone/deployments/csa.war/custom-content/ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\deployments\csa.war\custom-content\$CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/deployments/csa.war/custom-content/ |
The following is the file that you customized to import large archives using the Cloud Service Management Console or REST API and the actions required when you upgrade CSA:
File | Action |
---|---|
standalone.conf.batstandalone.conf | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File, Action, and Locations
standalone.conf.batstandalone.conf | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following file may have been customized if you updated the Cloud Service Management Console session:
File | Action |
---|---|
web.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File, Action, and Locations
web.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following file may have been customized if you updated the Cloud Service Management Console dashboard title:
File | Action |
---|---|
messages.properties | Required. Manually copy the file from the backup directory to the CSA 4.60 directory (see table below for more information). |
File, Action, and Locations
messages.properties | |
---|---|
Action | Required. Manually copy the file from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of custom files that you may have added and the actions required when you upgrade CSA:
File | Action |
---|---|
*.jsp (dynamic query scripts) | Required. Manually copy any custom dynamic query scripts from the backup directory to the CSA 4.60 directory (see table below for more information). |
*.jar (dynamic query scripts) | Required. Manually copy any custom dynamic query scripts from the manual backup copies you made before running the upgrade installer. |
*.jpg, *.jpeg, *.gif, *.png | No action required. |
Files, Actions, and Locations
*.jsp (dynamic query scripts) | |
---|---|
Action | Required. Manually copy any custom dynamic query scripts from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
*.jar (dynamic query scripts) | |
---|---|
Action | Required. Manually copy any custom dynamic query scripts from the manual backup copies you made before running the upgrade installer. |
File Location in CSA 4.60 | <user-specified location> |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | <user-specified location> |
*.jpg, *.jpeg, *.gif, *.png | |
---|---|
Action | No action required. All custom graphics of the listed types in the associated directory are automatically restored. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you may have customized if you ran any of the CSA tools and the actions required when you upgrade CSA:
File | Action |
---|---|
config.properties (Content Archive Tool, Purge Tool, Provider Configuration Tool) | Required. Manually copy any custom configuration files from the backup directory to the CSA 4.60 directory (see table below for more information). |
db.properties (Process Definition Tool, Schema Installation Tool) | Required. Manually copy any custom configuration files from the backup directory to the CSA 4.60 directory (see table below for more information). |
HPOOInfoInput.xml (Process Definition Tool) | Required. Manually copy any custom input files from the backup directory to the CSA 4.60 directory (see table below for more information). |
provider.xml (Provider Configuration Tool) | Required. Manually copy any custom input files from the backup directory to the CSA 4.60 directory (see table below for more information). |
Files, Actions, and Locations
config.properties | |
---|---|
Action | Required. Manually copy any custom configuration files from the backup directory to the CSA 4.60 directory. This is the generic name of the configuration file used in some examples for the Content Archive Tool, Purge Tool, and Provider Configuration Tool. If you used a different name for the configuration file, copy that file instead. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
db.properties | |
---|---|
Action | Required. Manually copy any custom configuration files from the backup directory to the CSA 4.60 directory. This is the generic name of the configuration file used in some examples for the Process Definition Tool and Schema Installation Tool. If you used a different name for the configuration file, copy that file instead. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
HPOOInfoInput.xml | |
---|---|
Action | Required. Manually copy any custom input files from the backup directory to the CSA 4.60 directory. This is the generic name of the input file used in some examples for the Process Definition Tool. If you used a different name for the input file, copy that file instead. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
provider.xml | |
---|---|
Action | Required. Manually copy any custom provider input files from the backup directory to the CSA 4.60 directory. This is the generic name of the input file used in some examples for the Provider Configuration Tool. If you used a different name for the provider input file, copy that file instead. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the file that you may have customized if you updated the password of the CSA database user and the actions required when you upgrade CSA:
File | Action |
---|---|
standalone.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
standalone.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you may have customized if you updated the password of one or more seeded users and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext-security.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
csa-consumer-users.properties | Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
csa-provider-users.properties | Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
integrationusers.properties | Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
applicationContext.properties | Required. If this file was customized, you must recustomize this file (see table below for more information. |
Files, Actions, and Locations
applicationContext-security.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
csa-consumer-users.properties | |
---|---|
Action | Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60.No action required. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
csa-provider-users.properties | |
---|---|
Action | Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60.No action required. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
integrationusers.properties | |
---|---|
Action | Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60.No action required. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.properties | |
---|---|
Action | Required. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade CSA:
Directory | Action |
---|---|
<theme_directory> | Required. If you created a customized theme for the Marketplace Portal, you must manually copy these directories (one for the Marketplace Portal and one for the Identity Management component) and theirthis directory (for the Marketplace Portal) and its content from the backup directory to the CSA 4.60 directory (see table below for more information). |
Directories, Actions, and Locations
<theme_directory> (Marketplace Portal) | |
---|---|
Action | Required. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
<theme_directory> (Identity Management Component) | |
---|---|
Action | Required. If you created a customized theme for the Marketplace Portal, you must recreate this theme by creating a new directory in the CSA 4.60 directory :
|
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the directory where you may have added customized widgets for the Marketplace Portal and the action required when you upgrade CSA:
Directory | Action |
---|---|
<iFRAME_URL_structure> | Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.60 directory (see table below for more information). |
Directory, Action, and Locations
<iFRAME_URL_structure> | |
---|---|
Action | Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.60 directory. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the file that you may have customized if you integrated with the ArcSight Logger and the actions required when you upgrade CSA:
File | Action |
---|---|
log4j.properties | Required. You must recustomize the log4j2.xml file (see table below for more information). |
File, Actions, and Locations
log4j.properties | |
---|---|
Action | Required. You must recustomize the Caution: Do NOT copy the backed up file over the new file. The logger has been upgraded in CSA 4.60 and the backed up file is not compatible with the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\ $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/ log4j2.xml |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\csa.war\WEB-INF\classes\ $CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/csa.war/WEB-INF/classes/ log4j.properties |
The following is a list of files that you customized when integrating CSA with a Common Access Card (CAC) and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext.xml (Cloud Service Management Console) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-v0.xml (Identity Management component) | Required. This is a new file that must be customized (see table below for more information). |
csa.properties | No action required. |
java.security | Required. If this file was customized, you must recustomize this file (see table below for more information). |
standalone.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
java.security | No action required. |
Files, Actions, and Locations
applicationContext.xml (Cloud Service Management Console) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-v0.xml (Identity Management Component) | |
---|---|
Action | Required. This is a new file that requires customization. Refer to the Cloud Service Automation Configuration Guide for more information. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | N/A |
csa.properties | |
---|---|
Action | No action required. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\ $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\csa.war\WEB-INF\classes\ $CSA_HOME/_CSA_4_60_0_installation/Backup/standalone/csa.war/WEB-INF/classes/ |
java.security | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | This file is not backed up. You should have manually backed this file up prior to running the upgrade installer. |
standalone.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you may have customized for the Identity Management component and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext.properties | No action required. |
applicationContext-common.xml | No action required. |
Files, Actions, and Locations
applicationContext.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.properties | |
---|---|
Action | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-common.xml | |
---|---|
Action | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the file that you may have customized if you configured IPv6 and the actions required when you upgrade CSA:
File | Action |
---|---|
standalone.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File, Actions, and Locations
standalone.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the file that you may have customized if you configured the JBoss password vault and the actions required when you upgrade CSA:
File | Action |
---|---|
vault.batvault.sh | Required. If this file was customized, you must recustomize this file (see table below for more information. |
File, Actions, and Locations
vault.batvault.sh | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is the file that you may have customized if you configured Oracle RAC and the actions required when you upgrade CSA:
File | Action |
---|---|
standalone.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File, Actions, and Locations
standalone.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file is different from the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
The following is a list of files that you customized when configuring CSA to use a single sign-on (SSO) and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
hpssoConfiguration.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
hpssoConfiguration.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
applicationContext.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
hpssoConfiguration.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (default) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (pilot) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (<theme_directory>) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
rb.json | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
File | Action |
---|---|
web.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
hpssoConfig.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-v0.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
web.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\idm-service.war\WEB-INF\ |
hpssoConfig.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\ |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\idm-service.war\WEB-INF\ |
applicationContext-v0.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 | %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring |
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 | %CSA_HOME%\_CSA_4_60_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring |
The following is a list of files that you customized when integrating CSA with SiteMinder and the actions required when you upgrade CSA:
File | Action |
---|---|
applicationContext-security.xml (Cloud Service Management Console) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
web.xml | Required. If this file was customized, you must recustomize this file (see table below for more information). |
applicationContext-security.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information).No action required. |
applicationContext.xml (Identity Management component) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
ssologout.jsp | Required. If this file was customized, you must recustomize this file (see table below for more information). |
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
File | Action |
---|---|
rb.json | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (default) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (pilot) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
main.css (custom theme) | Required. If this file was customized, you must recustomize this file (see table below for more information). |
Files, Actions, and Locations
applicationContext-security.xml (Cloud Service Management Console) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
ssologout.jsp | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
web.xml | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext-security.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution:
Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
applicationContext.xml (Identity Management Component) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
rb.json | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (default) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (pilot) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
main.css (<theme_directory>) | |
---|---|
Action | Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.60. Caution: Do NOT copy the backed up file over the new file. The file has changed in CSA 4.60 and the backed up file does not contain all the required attributes for the current version. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
If you deleted the sample consumer organization on your CSA 4.2x4.10 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 Cloud Service Automation Configuration Guide for more information if you are deleting this organization for the first time.
If you created 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 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_60_0_installation\Change HP Cloud Service Automation Installation.exe
.
If you customized the Marketplace Portal configuration file, the customizations have been merged with the upgraded file. Refer to the Cloud Service Automation Configuration Guide for more information about the configurable properties in this file.
File | Action |
---|
mpp.json | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
index.html | No action required. If this file was customized, the customizations have been restored. |
Files, Actions, and Locations
mpp.json | |
---|---|
Action | No action required. If this file was customized, the customizations have been merged with the upgraded file. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
index.html | |
---|---|
Action | No action required. If this file was customized, the customizations have been restored. |
File Location in CSA 4.60 |
|
Backed Up CSA 4.2x4.10 File Location in CSA 4.60 |
|
Update and redeploy the oo10-sm-cp-1.0.3.jar
base content pack. If you deployed an earlier version of the Service Manager base content pack, you must do the following (if this is a fresh installation of Operations Orchestration and you did not deploy an earlier version of the Service Manager base content pack, you do not have to complete these steps):
Stop the Operations Orchestration services:
Windows:
On the server that hosts Operations Orchestration, navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration Central service and select Stop.
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration RAS service and select Stop.
Linux:
On the server that hosts Operations Orchestration, run the following command: <HPOOinstallation>/central/bin/central stop
For example, /usr/local/hpe/csa/OO/central/bin/central stop
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), run the following command: <HPOOinstallation>/ras/bin/ras stop
.
For example, /usr/local/hpe/csa/OO/ras/bin/ras stop
Clear the Operations Orchestration Central cache by deleting the following folder:
<HPOOinstallation>\central\var\cache
For example,
Windows: C:\Program Files\HPE\HP Operations Orchestration\central\var\cache
Linux: /usr/local/hpe/csa/oo/central/var/cache
If RAS is installed, clear the RAS artifact cache by deleting the following folder (on all RAS systems, including localhost):
<HPOOinstallation>\ras\var\cache
For example,
Windows: C:\Program Files\HPE\HP Operations Orchestration\ras\var\cache
Linux: /usr/local/hpe/csa/oo/ras/var/cache
Run the following SQL command against the Operations Orchestration database:
DELETE from OO_ARTIFACTS where NAME = 'org/apache/ws/security/wss4j/1.5.7/wss4j-1.5.7.pom' or NAME = 'org/apache/ws/security/wss4j/1.5.7/wss4j-1.5.7.jar'
Start the Operations Orchestration services:
Windows:
On the server that hosts Operations Orchestration, navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration Central service and select Start.
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration RAS service and select Start.
Linux:
On the server that hosts Operations Orchestration, run the following command: <HPOOinstallation>/central/bin/central start
For example, /usr/local/hpe/csa/OO/central/bin/central start
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), run the following command: <HPOOinstallation>/ras/bin/ras start
.
For example, /usr/local/hpe/csa/OO/ras/bin/ras start
Redeploy the oo10-sm-cp-1.0.3.jar
base content pack:
Log in to Operations Orchestration Central and click Content Management.
Navigate to the CSA_HOME\oo\ooContentPack
directory and select oo10-sm-cp-1.0.3.jar.
Click Deploy.
The deployment may take a few minutes and the dialog will show a progress bar.
If you did not install the sample content during the upgrade or if the sample content deployment failed, you can run the Cloud Content Capsule Installer to install the sample content. Refer to the CSA Content Installation Guide and Cloud Service Automation Content Pack User's Guide for more information.
Install and import CSA flows for sequential designs and deploy a content pack for topology designs. If you have not installed flows for sequential designs before, you should configure Operations Orchestration for sequential designs instead. Refer to the Configure Operations Orchestration for Sequential Designs section in the Cloud Service Automation Configuration Guide for more information.
If you upgraded CSA that uses an existing external Operations Orchestration version 10.21.0001, you must manually deploy a content pack for topology designs.
To deploy the content pack, do the following from the system on which CSA is installed:
Log in to Operations Orchestration Central (version 10.21.0001)and click the Content Management button.
Navigate to the %CSA_HOME%\Tools\ComponentTool\contentpacks\$CSA_HOME/Tools/ComponentTool/contentpacks/
directory.
Select the CSA-SA-CP-04.10.0000 content pack, and click Open.
Note: You do not need to select the other content packs in this directory. The other content packs were automatically deployed during the upgrade.
Click Deploy.
The deployment may take a few minutes and the dialog will show a progress bar.
Install CSA flows on the system running Operations Orchestration:
If CSA and
Operations Orchestration are running on different systems, from the
CSA system, copy the
%CSA_HOME%\CSAKit-4.5\OO Flow Content\9X\CSA-4_10-ContentInstaller.jar
file to the Operations Orchestration 9.07 system and %CSA_HOME%\CSAKit-4.5\OO Flow Content\10X\oo10-csa-cp-4.60.000.jar
$CSA_HOME/CSAKit-4.5/OO Flow Content/>9X/CSA-4_10-ContentInstaller.jar
file to the Operations Orchestration 9.07 system and $CSA_HOME/CSAKit-4.5/OO Flow Content/10X/oo10-csa-cp-4.60.000.jar
file to the Operations Orchestration 10.20 system.
CSA-4_10-ContentInstaller.jar
/oo10-csa-cp-4.60.000.jar
file is located.From the command prompt, run the following command:
Windows (9.07):
"<location_of_OO_jre>\bin\java" -jar CSA-4_10-ContentInstaller.jar -centralPassword <OOAdminPassword>
Windows (10.20): "<location_of_OO_jre>\bin\java" -jar oo10-csa-cp-4.60.000.jar -centralPassword <OOAdminPassword>
Linux (9.07):
<location_of_OO_jre>/bin/java -jar CSA-4_10-ContentInstaller.jar -centralPassword <OOAdminPassword>
Linux (10.20): <location_of_OO_jre>/bin/java -jar oo10-csa-cp-4.60.000.jar -centralPassword <OOAdminPassword>
where <location_of_OO_jre>
is the location of the JRE installed
for Operations Orchestration. For example,
"%ICONCLUDE_HOME%\jre1.6"
or $ICONCLUDE_HOME/jre1.6
on the 9.07 system and "%ICONCLUDE_HOME%\java"
or $ICONCLUDE_HOME/java
on the 10.20 system.
Import the CSA 4.60 flows using the process definition tool (for more information about the process definition tool, refer to the Cloud Service Automation Configuration Guide).
Note:
If you upgraded CSA that uses an existing external Operations Orchestration, you must regenerate the Operations Orchestration input file
(HPOOInputSample.xml
) in order to import the flows that have been updated in
CSA 4.60.
Refer to the steps below for more information.
csauser
.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
(CSA 4.2x4.10)
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.RegenerateGenerate the sample database properties files and Operations Orchestration input file. For example, run the following command (you may need to specify different options; refer to the 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 CSA
is installed.
HPOOInputSample.xml
to HPOOInfoInput4.60.xml
.HPOOInfoInput4.60.xml
file by making the
same customizations you made in the
CSA 4.2x4.10
version of the 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 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.60.xml
"<csa_jre>\bin\java" $CSA_JRE_HOME/bin/java
–jar process-defn-tool.jar –d db.properties
–i HPOOInfoInput4.60.xml
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed.
Note:
If you have applied the CSA 4.2x4.10 content pack on Operations Orchestration 10.21.0001, when the content pack is imported, it is named Customer
. After upgrading to CSA 4.60, when importing the CSA 4.60 content pack, if you encounter any issues, remove the Customer
content pack and re-import the CSA 4.60 content pack. The CSA 4.60 content pack includes all content from the CSA 4.2x4.10 content pack. If you customized any of the content in the CSA 4.2x4.10 content pack, you will need to recustomize that content in the CSA 4.60 content pack.
Import the CSA 4.60 sample service designs:
If you are importing a sequential design, do the following:
If you are importing a topology design, do the following:
Navigate to
%CSA_HOME%\CSAKit-4.5\Content Archives,
$CSA_HOME/CSAKit-4.5/Content Archives,
select a zip file from one of the directories, and click Open.
Content Archives
directory and its subdirectories.Note: HP recommends that you start using the CSA 4.60 versions of the service designs immediately.
Refer to the CSA Integration Pack whitepaper and CSA Service Design Guide for more information about the CSA service designs.
Refer to the README file of the resource provider to verify if it requires and upgrade. The README file can be found in the following location:
%CSA_HOME%\CSAKit-4.5\Lib\<resource_provider>\
$CSA_HOME/CSAKit-4.5/Lib/<resource_provider>/
It may be necessary to clear your Web browser cache on systems that previously accessed the Cloud Service Management Console prior to upgrading to CSA 4.60. To clear your Web browser cache:
If you are using a Chrome Web browser:
If you are using a Firefox Web browser:
If you are using a Windows IE Web browser:
To restart the CSA and Marketplace Portal services:
On the server that hosts CSA, navigate to Start > Administrative Tools > Services.
Global Search is on by default in CSA 4.60. If you find that global search is off, you can re-enable global search by doing the following:
Right-click on the Elasticsearch 1.6.1 service and select Restart.
Wait for a minute for the Elasticsearch 1.6.1 service to restart, then right-click on HPE Search Service and select Restart.
Right-click on the Cloud Service Automation service and select Restart.
Right-click on the Marketplace Portal service and select Restart.
Right-click on the Operations Orchestration Central service and select Restart.
On the server that hosts CSA,
log in as csauser
and enter the following:
service csa restart
service mpp restart
As csauser
, start Operations Orchestration Central:
<embeddedHPOOinstallation>/central/bin/central stop
<embeddedHPOOinstallation>/central/bin/central start
For example, type /usr/local/hp/csa/OO/central/bin/central stop
.
/usr/local/hp/csa/OO/central/bin/central start
© Copyright 2010-2016 Hewlett-Packard Development Company, L.P.