Customized output from:
Document Release Date: July 2014 Software Release Date: July 2014 |
|
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2010-2014 Hewlett-Packard Development Company, L.P.
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
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 HP Cloud Service Automation Installation Guide for 4.10 is an interactive document that provides the information necessary to install the HP Cloud Service Automation (HP CSA) application, based on the information you provide.
Select from the options below and click View or Print to create a customized installation document. In this document, when available, detailed tasks are provided to complete the installation. In other cases, you may need to refer to the manufacturer's documentation to complete the steps.
Note: If a selection is disabled (it cannot be selected), it is not a supported selection based on the other options you have selected. If a disabled selection is selected, choose an enabled selection instead. In some cases, there may be only one selection that can be enabled in a section.
For general information about HP Cloud Service Automation, see the HP Cloud Service Automation Concepts Guide.
For information about the supported components and versions, see the HP Cloud Service Automation System and Software Support Matrix.
If you want to upgrade to HP CSA version 4.10, see the HP Cloud Service Automation Upgrade Guide.
Version: 4.10
Document Release Date: July 2014
Software Release Date: July 2014
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 on the previous page, perform the following steps. It is recommended that you perform each step in the following order:
This guide provides information for installing the HP Cloud Service Automation application. Successful implementation of the application requires knowledge of the integrated products, as well as the HP Cloud Service Automation solution. 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.
For information about how these parts fit together, see the HP Cloud Service Automation Concepts Guide.
You should review the HP Cloud Service Automation System and Software Support Matrix for version requirements.
Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
Configure a group and user for HP CSA:
Create a group called csagrp. Enter the following:
groupadd csagrp
Create a user called csauser and assign this user to the csagrp. Enter the following:
useradd -g csagrp -m csauser
(Ubuntu) oruseradd -g csagrp -m csauser -s /bin/bash
(RHEL)
Assign a password to the csauser. Enter the following:
passwd csauser
When prompted, enter the password.
For a list of supported database versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
Install the database according to the manufacturer’s documentation. Database installation is typically done in partnership with a database administrator.
For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix (available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)).
Download a supported version of the JDBC .jar
file(s) and save them on the system on which
HP CSA will be installed.
Note the location where you save the file(s) as this information must be provided when
HP CSA is installed.
These tasks must be completed before HP CSA is installed.
If the database instance used by HP CSA has not already been created, work with the database administrator to create this database.
A database user is needed when installing HP 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.
You must provide this user's username and password when prompted for the CSA database user during the installation of HP CSA.
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the installation of HP CSA.
To support localization, the Oracle database instance must support UTF-8 character encoding and multi-byte characters. Work with the database administrator to set the following parameters to the specified values (or refer to the manufacturer’s documentation for more information):
For performance reasons, HP recommends that you create a new tablespace which stores LOBs for the CSA_DOCUMENT table. Work with the database administrator to create a tablespace to be used by HP CSA (or refer to the manufacturer’s documentation for more information). HP recommends that the initial tablespace size should be at least 3 GB.
The tablespace must be created before installing HP CSA and then must be configured immediately after HP CSA is installed.
Refer to HP Cloud Service Automation System and Software Support Matrix for a list of supported database versions, 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).
Database installation is typically done in partnership with a database administrator. Microsoft SQL Server must be installed with Mixed Mode authentication. During the installation of Microsoft SQL Server, from the Database Engine Configuration dialog, for Authentication Mode, select Mixed Mode (SQL Server authentication and Windows authentication).
These tasks must be completed before HP CSA is installed. Work with the database administrator to complete the following tasks (or refer to the manufacturer’s documentation for more information).
TCP/IP must be enabled on the Microsoft SQL Server in order for HP CSA to log in to the database. By default, TCP/IP may be disabled on the Microsoft SQL Server. Verify the TCP/IP configuration.
From the SQL Server Configuration Manager:
An HP CSA database user is needed when installing HP 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.
To create a database user for HP CSA, do the following:
You must provide this user's username and password when prompted for the CSA database user during the installation of HP CSA.
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the installation of HP CSA.
For performance reasons, HP recommends that you associate a new filegroup with the CSA_DOCUMENT table. Work with the database administrator to configure a filegroup to be used by HP CSA (or refer to the manufacturer’s documentation for more information). HP recommends that the initial filegroup size should be at least 3 GB.
The filegroup is configured after HP CSA is installed.
Refer to HP Cloud Service Automation System and Software Support Matrix for a list of supported database versions, 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).
Install the database according to the manufacturer’s documentation. Database installation is typically done in partnership with a database administrator.
These tasks must be completed before HP CSA is installed. Work with the database administrator to complete the following tasks (or refer to the manufacturer’s documentation for more information).
At least two database users are needed when installing HP CSA. Do the following:
On the system hosting the database, install
postgresql-client
postgres-client.rpm
if it is not already installed.
As the root user, enter the following:
apt-get install postgresql-client
rpm -ivh postgres-client.rpm
Set the shared library path to
include the PostgreSQL libraries (<postgresql_installation>/lib
).
For example, if you installed PostgreSQL in /opt/PostgreSQL/9.2/
, run the
following command:
export LD_LIBRARY_PATH=/opt/PostgreSQL/9.2/lib:$LD_LIBRARY_PATH
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.
Create an HP CSA
database user (for example, csadbuser
).
The HP CSA
database user is required.
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 csadbuser login password '<csadbuser_password>' superuser inherit;
You must provide this user's username and password when prompted for the CSA database user during the installation of HP CSA.
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:
Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;
A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Add a reporting database user to the HP CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;
Optionally, create a reporting
database user for HP CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
HP CSA.
This user should have read-only rights.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;
If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the installation of HP CSA.
Create a new database for HP CSA. Grant the HP CSA database user all rights to this database and grant the reporting database user read-only access 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, if you create
a database named csadb
, an
HP CSA
user named csadbuser
, and a reporting database user
CSAReportingDBUser
, from the psql prompt, enter
the following commands:
create database csadb with owner=csadbuser connection limit=-1;
grant all on database csadb to csadbuser;
grant connect on database csadb to CSAReportingDBUser;
Create a new database for HP Operations Orchestration. Grant the HP Operations Orchestration 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, if you create
a database named csaoodb
and
an HP 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;
Exit psql. From the psql prompt, enter the following:
\q
Install HP Operations Orchestration to the correct version and patch level. See HP 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).
If you are using an existing installation of HP Operations Orchestration, you should verify that the correct versions of patches and updates have been applied.
Note: Installation log files are written to the
directory.%CSA_HOME%
$CSA_HOME
\_CSA_4_1_0_installation\Logs\
To install HP Cloud Service Automation (HP CSA), complete the following steps.
Run the setup.exe
installation file.
On the Introduction screen, read the information and click Next.
Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.
If the following error message displays:
Another version of HP CSA
is configured in the registry. However, HP CSA
has been uninstalled (the HP CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing HP CSA. Refer to the
HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml
file (you may need to show hidden files), make a backup copy, delete all
HP CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select HP CSA and Marketplace Portal and click Next.
Choose a location in which to install HP CSA and click Next (
is set to this location).%CSA_HOME%
$CSA_HOME
The default location is
C:\Program Files\Hewlett-Packard\CSA
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
Choose the JRE that will be used by HP CSA.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
OpenJDK JRE
The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, click Open JRE and click Next.
The default location in which the OpenJDK JRE is installed is
C:\Program Files\Hewlett-Packard\CSA\openjre
.
Oracle JRE
If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE, select the location in which you installed this JRE, and click Next.
The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, click Choose and select the location in which you installed the JRE that will be used by HP CSA.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
Select the type of database installed (Microsoft SQL Server)(Oracle)(PostgreSQL) and click Next.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($).
For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths.
However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the
HP Software Support Web site at
http://h20230.www2.hp.com/selfsolve/manuals/
(this site requires that you register with HP Passport). Click Choose to select the directory.
Define the database instance on which the HP CSA database components should be installed or where the HP CSA database schema already exists. Enter the following database information and click Next.
Field Name | Description |
---|---|
Database Host | The hostname or IP address of the server where the database is located. When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4] or [::1] . |
Database Port | The database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
Database NameOracle SID |
The name of the database instance on which the HP CSA database schema will be installed. If you are creating a new HP CSA database schema, this is the name of the database instance on which the HP CSA database components will be installed. If you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version HP 4.10, this is the name of the database instance on which the HP CSA database schema exists. For an Oracle database, this is the System ID (SID). |
Database Username | The username of the database user you configured for HP CSA after installing the database. |
Database Password | The password for the database user. |
If you created a reporting database role and read-only userreporting database user when you configured the database, select the Reporting User checkbox and enter the following information:
Field Name | Description |
---|---|
CSA Reporting Database Username | The username of the database user you configured for reporting purposes for HP CSA after installing the database. |
CSA Reporting Database Password | The password for the CSA reporting database user. |
Install HP CSA database components onto the database instance to create the HP CSA database schema, if it does not exist.
Click Yes to install HP CSA database components and create the HP CSA database schema. When you select this option, the HP CSA service automatically starts when you exit the installer.
Click No if you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version 4.10. When you select this option, the HP CSA service does not start when you exit the installer. Refer to the end of this section for information on how to start and stop the HP CSA service.
From the Enter host name screen, enter the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.
Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.
By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.
If you do not want to use HPSSO, you can disable it.
You MUST disable HP Single Sign-On if you are installing HP CSA in a FIPS 140-2 compliant environment.
If enabled, enter the domain name of the network to which the server on which you are installing HP CSA belongs and click Next.
Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.
Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.
Review your selections and click Install to complete the installation.
In some instances, you may be asked to restart your system.
Click Yes, restart my system to restart your system when you exit the installer.
Click No, I will restart my system myself to restart your system at a more convenient time.
Click Done to exit the installer.
Verify that the HP Cloud Service Automation and Marketplace Portal services have started by navigating to Control Panel > Administrative Tools > Services. It can take up to five minutes for the HP Cloud Service Automation to start. If one or both services have not started, right-click on the service and select Start.
The installer creates the HP Cloud Service Automation and Marketplace Portal services. If you opted to install the HP Cloud Service Automation database components, the installer starts these services. The HP Cloud Service Automation service must be running in order to access the Cloud Service Management Console and the Marketplace Portal service must be running in order to access the Marketplace Portal.
To start, stop, and restart the HP Cloud Service Automation and Marketplace Portal services, navigate to Control Panel > Administrative Tools > Services, right-click on a service, and select the desired action.
Note: Installation log files are written to the
directory and are named %CSA_HOME%
$CSA_HOME
/_CSA_4_1_0_installation/Logs/csa_*.txt
.
To install HP Cloud Service Automation (HP CSA), complete the following steps.
Install the unzip utility if it is not already installed. Enter the following:
apt-get install unzip
Create an installation directory for HP CSA
(this document assumes that you will install the product in
/usr/local/hp/csa
and all examples
used in this document are based on this assumption). Enter the following:
mkdir -p /usr/local/hp/csa
For the installation directory, set the owner to csauser and the group to csagrp. Enter the following:
chown -R csauser:csagrp /usr/local/hp/csa
setup.bin
) to the system and go to the directory in which it has been copied.Verify that setup.bin
is owned by csauser and csauser has full permissions to the file. If necessary,
do the following:
Enter one or both of the following commands:
chown csauser setup.bin
chmod u+rwx setup.bin
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.
Run the setup.bin
installation file (as the csauser).
Note: You must run setup.bin
as the csauser. If you
install HP CSA as another user,
you may not be able to run HP CSA.
As the csauser, enter the following:
./setup.bin
Read the Introduction and click enter to continue with the installation.
Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.
If the following error message displays:
Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml
file, make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml
file, and restart the installer.
Verify that no HP CSA services are running on the system. Open a command prompt and type ps -ef | grep csa
. If the csa
process is running, kill it.
After verifying that no HP CSA services are running on the system, close the command prompt.
Select enter to continue the installation.
Select the application to install and click Enter.
HP CSA and Marketplace Portal
Installs the entire HP CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Marketplace Portal
Installs only the Marketplace Portal on the system.
Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.
The default location is /usr/local/hp/csa
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.
Choose the JRE that will be used by HP CSA.
In this documentation,
the directory in which the JRE is installed will be referred to as
$CSA_JRE_HOME
.
For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
OpenJDK JRE
The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, type 1 and select Enter.
The default location in which the OpenJDK JRE is installed is
/usr/local/hp/csa/openjre
.
Oracle JRE
If you have installed a supported version of Oracle JRE to be used by HP CSA, type 2 and select Enter. Type the location in which you installed this JRE and select Enter.
The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, type in the location in which you installed the JRE that will be used by HP CSA and select Enter.
Define the database instance on which the HP CSA database components should be installed. Enter the following database information (select Enter after each entry).
Enter the type of database you have installed: MSSql (Microsoft SQL Server)OraclePostgres (PostgreSQL).
For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
[f000:253c::9c10:b4b4]
or [::1]
. The default value is the IP address of the localhost (127.0.0.1).Enter the database port. This is the database port number, such as 1433 (Microsoft SQL Server)1521 (Oracle)5432 (PostgreSQL).
Enter the database name. This is the name of the database instance on which the
HP CSA
database schema will be installed. If you are creating a new
HP CSA
database schema, this is the name of the database instance on which the
HP CSA database components
will be installed. If you are using an existing
HP CSA database schema
that was created as part of a prior successful installation of
HP CSA version
HP 4.10,
this is the name of the database instance on which
the HP CSA database schema already exists.
If you followed the examples in this document, enter csadb
.
Enter the CSA database user name. This is the user name of the database user you configured for
HP Cloud Service Automation after installing the database.
If you followed the examples in this document, enter csadbuser
.
Enter the CSA reporting database username (optional). This is the username of the database user you configured for reporting purposes for
HP CSA after installing the database.
If you followed the examples in this document, enter csareportingdbuser
.
Enter the HP CSA server hostname. This is the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.
Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.
By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.
If you do not want to use HPSSO, you can disable it. Type 2 and select Enter.
To enable HPSSO, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing HP CSA) and select Enter.
Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.
Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.
Review your selections and select Enter to complete the installation or Ctrl-c to exit the installation.
When the installation completes, select enter to exit the installer.
Define the CSA_HOME and JAVA_HOME environment variables
and add /sbin
to the PATH variable for the csauser user. Set CSA_HOME to the location where
HP CSA is installed. In a startup script
for the csauser user (for example, .profile
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux)), add the following:
export CSA_HOME=/usr/local/hp/csa
export JAVA_HOME=<csa_jre>$CSA_JRE_HOME
export PATH=$PATH:/sbin
<csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed.Source the startup file in
which you set the CSA_HOME, JAVA_HOME,
and PATH environment variables. If you edited
.bashrc
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux),
enter the following:
. ./.bashrc
(Ubuntu). ./.bash_profile
(Red Hat Enterprise Linux)
Create an HP CSA service and a Marketplace Portal service to start and stop the HP CSA and Marketplace Portal processes.
Go to the directory in which HP CSA is installed. For example:
cd /usr/local/hp/csa
Copy the csa
and mpp
scripts to the /etc/init.d
directory. Enter the following:
cp ./scripts/csa /etc/init.d
cp ./scripts/mpp /etc/init.d
Change permissions of the scripts. Enter the following:
chmod 755 /etc/init.d/csa
chmod 755 /etc/init.d/mpp
Log in as csauser and start the HP CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
The HP Cloud Service Automation service must
be running in order to access the
Cloud Service Management Console.
You can start this service by typing service csa start
.
You can restart this service by typing service csa restart
.
You can stop the service by typing service csa stop
.
You can check the status of the service by typing service csa status
.
The Marketplace Portal service must be running in order to access the
Marketplace Portal.
You can start this service by typing service mpp start
.
You can restart this service by typing service mpp restart
.
You can stop the service by typing service mpp stop
.
You can check the status of the service by typing service mpp status
.
Note: Installation log files are written to the
directory.%CSA_HOME%
$CSA_HOME
\_CSA_4_1_0_installation\Logs\
To install a remote instance of the Marketplace Portal, complete the following steps.
Run the setup.exe
installation file.
On the Introduction screen, read the information and click Next.
Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.
If the following error message displays:
Another version of HP CSA
is configured in the registry. However, HP CSA
has been uninstalled (the HP CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing HP CSA. Refer to the
HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml
file (you may need to show hidden files), make a backup copy, delete all
HP CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select Marketplace Portal and click Next.
Choose a location in which to install the Marketplace Portal and click Next (
is set to this location).%CSA_HOME%
$CSA_HOME
The default location is
C:\Program Files\Hewlett-Packard\CSA
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.
Field Name | Description |
---|---|
HP CSA Host | The fully-qualified domain name of the system on which HP CSA is installed. |
HP CSA Port | The port number used to communicate with HP CSA. |
HP CSA Certificate | The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system. |
From the Hostname Configuration screen, enter the fully-qualified domain name of this system, the one on which you are installing the Marketplace Portal, and click Install to complete the installation.
Click Done to exit the installer.
Verify that the Marketplace Portal service has started by navigating to Control Panel > Administrative Tools > Services. If the service has not started, right-click on the service and select Start.
The Marketplace Portal service must be running in order to access the Marketplace Portal.
To start, stop, and restart the Marketplace Portal service, navigate to Control Panel > Administrative Tools > Services, right-click on the Marketplace Portal service, and select the desired action.
Note: Installation log files are written to the
directory and are named %CSA_HOME%
$CSA_HOME
/_CSA_4_1_0_installation/Logs/csa_*.txt
.
To install HP Cloud Service Automation (HP CSA), complete the following steps.
Install the unzip utility if it is not already installed. Enter the following:
apt-get install unzip
Create an installation directory for HP CSA
(this document assumes that you will install the product in
/usr/local/hp/csa
and all examples
used in this document are based on this assumption). Enter the following:
mkdir -p /usr/local/hp/csa
For the installation directory, set the owner to csauser and the group to csagrp. Enter the following:
chown -R csauser:csagrp /usr/local/hp/csa
setup.bin
) to the system and go to the directory in which it has been copied.Verify that setup.bin
is owned by csauser and csauser has full permissions to the file. If necessary,
do the following:
Enter the following commands:
chown csauser setup.bin
chmod u+rwx setup.bin
Run the setup.bin
installation file (as the csauser).
Note: You must run setup.bin
as the csauser. If you
install HP CSA as another user,
you may not be able to run HP CSA.
As the csauser, enter the following:
./setup.bin
Read the Introduction and click enter to continue with the installation.
Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.
If the following error message displays:
Another version of HP CSA
is configured in the registry. However, HP CSA
has been uninstalled (the HP CSA installation
directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before
installing HP CSA. Refer to the
HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml
file, make a backup copy, delete all
HP CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.
The default location is /usr/local/hp/csa
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.
Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.
Field Name | Description |
---|---|
HP CSA Host | The fully-qualified domain name of the system on which HP CSA is installed. |
HP CSA Port | The port number used to communicate with HP CSA. |
HP CSA Certificate | The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system. |
From the Hostname Configuration screen, enter the fully-qualified domain name of this system, the one on which you are installing the Marketplace Portal, and click Install to complete the installation.
Review your selections and select enter to complete the installation or ctrl-c to exit the installation.
When the installation completes, select enter to exit the installer.
Define the CSA_HOME and JAVA_HOME environment variables and add /sbin
to the PATH variable for the csauser user. In a startup script
for the csauser user (for example, .profile
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux)), add the following:
export CSA_HOME=/usr/local/hp/csa
export JAVA_HOME=<csa_jre>$CSA_JRE_HOME
export PATH=$PATH:/sbin
Source the startup file in
which you set the CSA_HOME, JAVA_HOME,
and PATH environment variables. If you edited
.profile
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux),
enter the following:
. .profile
(Ubuntu). .bash_profile
(Red Hat Enterprise Linux)
Create the Marketplace Portal service to start and stop the Marketplace Portal process.
Go to the directory in which the Marketplace Portal is installed. For example:
cd /usr/local/hp/csa
Copy the mpp
script to the /etc/init.d
directory. Enter the following:
cp ./scripts/mpp /etc/init.d
Change permissions of the script. Enter the following:
chmod 755 /etc/init.d/mpp
Log in as csauser and start the Marketplace Portal service. Enter the following:
service mpp start
The Marketplace Portal service must be running in order to access the
Marketplace Portal.
You can start this service by typing service mpp start
.
You can restart this service by typing service mpp restart
.
You can stop the service by typing service mpp stop
.
You can check the status of the service by typing service mpp status
.
Configure the Oracle tablespace you created for HP Cloud Service Automation only if you are installing HP Cloud Service Automation for the first time and there is no data in the CSA_DOCUMENT table. The tablespace must have been created before HP Cloud Service Automation is installed and then must be configured immediately after HP Cloud Service Automation is installed.
Work with the database administrator to perform the following (or refer to the manufacturer’s documentation for more information):
Modify the CSA_DOCUMENT table such that LOB segments are stored in the tablespace. For example:
ALTER TABLE csa_document
MOVE LOB(content)
STORE AS (TABLESPACE <new_tablespace>);
These tasks must be completed after HP Cloud Service Automation is installed.
Configure the Microsoft SQL server filegroup you created for HP Cloud Service Automation only if you are installing HP Cloud Service Automation for the first time and there is no data in the CSA_DOCUMENT table. The filegroup must have been created before HP Cloud Service Automation is installed and then must be configured immediately after HP Cloud Service Automation is installed.
Work with the database administrator to perform the following (or refer to the manufacturer’s documentation for more information):
For security reasons, the Marketplace Portal file system must be protected by the operating system. Do the following:
From the elevated command prompt, run the following command:
attrib +s +h "%CSA_HOME%\portal" /S /D /L
where %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed.
Run the following commands:
chown –R csauser:csagrp $CSA_HOME/portal
chmod –R 700 $CSA_HOME/portal
where csauser and csagrp are the user and group you configured for HP CSA when you installed HP CSA and %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed.
Restart the csa and mpp services by running the following commands:
service csa restart
service mpp restart
The HP CSA solution includes a number of HP Operations Orchestration flows that perform HP CSA operations.
Complete the following tasks to configure HP Operations Orchestration to integrate with HP CSA:
Note: In the following instructions, %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed and %ICONCLUDE_HOME%
or $ICONCLUDE_HOME
is where you installed HP Operations Orchestration.
Be sure all the latest patches for HP Operations Orchestration have been installed. See the HP Cloud Service Automation System and Software Support Matrix for more information, 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).
The HP CSA flows that are imported require that a JRE be included in the system path on the system running HP CSA.
Windows
Open the Environment Variables dialog:
At the end of the value for Variable value, add a semicolon (;) and the following path:
If HP Operations Orchestration and HP CSA are installed on the same system:
%ICONCLUDE_HOME%\jre1.6\bin
or
If HP Operations Orchestration and HP CSA are installed on different systems:
<csa_jre>\bin
Linux
Open a shell and enter the following command:
If HP Operations Orchestration and HP CSA are installed on the same system:
export PATH=$PATH:$ICONCLUDE_HOME/jre1.6/bin
or
If HP Operations Orchestration and HP CSA are installed on different systems:
export PATH=$PATH:$CSA_JRE_HOME/bin
Note: By setting the system path, all applications (that require a JRE) use the JRE that is installed with HP Operations Orchestration (if it is the only path or the first path set to a JRE in the system path). If you need to run another JRE with an application, you must type in the relative path to that JRE in order to run it (for example, when you configure SSL).
The flows for HP Cloud Service Automation must be installed in the HP Operations Orchestration Flow Library.
To install HP Cloud Service Automation flows:
%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
OO Flow Content\
/
9X\
/
CSA-4_10-ContentInstaller.jar
file
from the HP Cloud Service Automation
system to the HP Operations Orchestration system (where
%CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed). CSA-4_10-ContentInstaller.jar
is located.Run the following command:
Windows
"%ICONCLUDE_HOME%\jre1.6\bin\java" ‑jar CSA-4_10-ContentInstaller.jar ‑centralPassword <OOAdminPassword>
Linux
$ICONCLUDE_HOME/jre1.6/bin/java ‑jar CSA-4_10-ContentInstaller.jar ‑centralPassword <OOAdminPassword>
Set the URL to:
https://<FQDN>:9004/RAS/services/RCAgentService
where <FQDN>
is the fully qualified domain name or IP address of the
HP Operations Orchestration host. Do not use localhost in the URL.
Using localhost does not work correctly even though it appears
to work when you run HP Operations Orchestration Studio on the same
machine as the RAS.
RAS must be run on the same system as HP Operations Orchestration Studio. Running HP Operations Orchestration Studio on another machine produces errors and turns flows red with a cryptic error message about result assignments to result variables that do not exist.
Verify the Credentials are set to the following values:
where CSA_REST_CREDENTIALS are the credentials for HP CSA REST authentication.
Note: The User Name configured for the CSA_REST_CREDENTIALS System Account setting must match the Property Value (HP Operations Orchestration version 9.07) or Override Value (HP Operations Orchestration version 10.10) configured for the CSA_OO_USER System Property setting.
Set the Property Value to:
https://<csa_hostname>:8444/csa/rest
Verify the Property Value is set to:
ooInboundUser
Note: The Property Value (HP Operations Orchestration version 9.07) or Override Value (HP Operations Orchestration version 10.10) configured for the CSA_OO_USER System Property setting must match the User Name configured for the CSA_REST_CREDENTIALS System Account setting.
The other settings can be optionally configured. For information about the settings, refer to the HP Cloud Service Automation Configuration Guide.
true
.For each system running HP CSA, import the root certificate of each HP Operations Orchestration's Certificate Authority.
Import HP Operations Orchestration's certificate into HP CSA
Import the root certificate of HP Operations Orchestration's Certificate Authority into HP Cloud Service Automation (you must first export HP Operations Orchestration's certificate from HP Operations Orchestration's truststore and then import it into HP CSA'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 HP Operations Orchestration system
to the system running HP Cloud Service Automation
(in this example, the file is copied to
C:\
/tmp
).On the system running HP Cloud Service Automation, run the following command:
"<csa_jre>\bin\keytool" -importcert -alias pas -file C:\oo.crt
-keystore <csa_jre>\lib\security\cacerts -storepass changeit$CSA_JRE_HOME/bin/keytool -importcert -alias pas -file /tmp/oo.crt
-keystore $CSA_JRE_HOME/lib/security/cacerts -storepass changeit
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed.
yes
.To restart HP CSA:
On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Cloud Service Automation service and select Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
Remote Access Server (RAS) operations are subject to a default timeout limit of 20 minutes on HP Operations Orchestration Central. You can change the time-out setting to support operations that are likely to take more than 20 minutes to complete.
If you expect to run large deployments, change the time-out setting according to Changing the timeout limit for RAS operations in the HP Operations Orchestration Software Administrator’s Guide. You may also refer to HP Operations Orchestration User's Guide sections Adding a RAS override and Best practices for runtime environment overrides. Both documents are 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).
The calls HP CSA makes to the HP Operations Orchestration REST APIs are synchronous, and HP Operations Orchestration will time-out the connection after one hour by default. To extend this time-out, do the following:
Open the following file in a text editor:
Windows
%ICONCLUDE_HOME%\Central\conf\Central.properties
Linux
$ICONCLUDE_HOME/Central/conf/Central.properties
Add the following lines:
# the maximum flow timeout value in milliseconds, this is equivalent to 2 hrs
dharma.headless2.continuation.timeout=7200000
Open the following file in a text editor:
Windows
%ICONCLUDE_HOME%\Central\WEB-INF\applicationContext.xml
Linux
$ICONCLUDE_HOME/Central/WEB-INF/applicationContext.xml
Add the following property to the dharma.RCDefaults
section:
<bean id="dharma.RCDefaults" class="com.iconclude.dharma.util.spring.RCDefaultsSpringFactory" lazy-init="false" singleton="true">
................
<prop key="dharma.headless2.continuation.timeout">${dharma.headless2.continuation.timeout}</prop>
Complete the following tasks to configure HP Operations Orchestration to integrate with HP CSA:
Note: In the following instructions, %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed and %ICONCLUDE_HOME%
or $ICONCLUDE_HOME
is where you installed HP Operations Orchestration.
Be sure all the latest patches for HP Operations Orchestration have been installed. See the HP Cloud Service Automation System and Software Support Matrix for more information, 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).
The HP CSA flows that are imported require that a JRE be included in the system path on the system running HP CSA.
Windows
Open the Environment Variables dialog:
At the end of the value for Variable value, add a semicolon (;) and the following path:
If HP Operations Orchestration and HP CSA are installed on the same system:
%ICONCLUDE_HOME%\java\bin
or
If HP Operations Orchestration and HP CSA are installed on different systems:
<csa_jre>\bin
Linux
Open a shell and enter the following command:
If HP Operations Orchestration and HP CSA are installed on the same system:
export PATH=$PATH:$ICONCLUDE_HOME/java/bin
or
If HP Operations Orchestration and HP CSA are installed on different systems:
export PATH=$PATH:$CSA_JRE_HOME/bin
Note: By setting the system path, all applications (that require a JRE) use the JRE that is installed with HP Operations Orchestration (if it is the only path or the first path set to a JRE in the system path). If you need to run another JRE with an application, you must type in the relative path to that JRE in order to run it (for example, when you configure SSL).
Copy the
file to:%CSA_HOME%
$CSA_HOME
\CSAKit-4.1\OO Flow Content\10X\oo10-csa-cp-4.10.000-uuids.txt%CSA_HOME%
$CSA_HOME
/CSAKit-4.1/OO Flow Content/10X/oo10-csa-cp-4.10.000-uuids.txt
Windows
%ICONCLUDE_HOME%\central\cmu\exclusions
Linux
$ICONCLUDE_HOME/central/cmu/exclusions
If HP CSA and
HP Operations Orchestration are running on different systems,
copy the
file
from the HP Cloud Service Automation
system to the HP Operations Orchestration system (where
%CSA_HOME%
$CSA_HOME
\CSAKit-4.1\OO Flow Content\10X\oo10-csa-cp-4.10.000.jar%CSA_HOME%
$CSA_HOME
/CSAKit-4.1/OO Flow Content/10X/oo10-csa-cp-4.10.000.jar%CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed).
Internal users can be used to configure HP Operations Orchestration for HP CSA.
Log in to HP Operations Orchestration Central.
Enter the following information:
Field | Recommended Value |
---|---|
User Name | csaoouser |
Password | cloud |
Roles | ADMINISTRATOR, SYSTEM_ADMIN |
The csaoouser user is used to import the HP Operations Orchestration flows. When importing flows, this user is configured in the HP Operations Orchestration input file used by the process definition tool.
Click the Add button.
Enter the following information:
Field | Recommended Value |
---|---|
User Name | admin |
Password | cloud |
Roles | ADMINISTRATOR, SYSTEM_ADMIN |
The admin user is used with HP Single Sign-On (HPSSO). When HP Operations Orchestration is launched from the Cloud Service Management Console, this user allows access to HP Operations Orchestration without having to log in.
Log out of HP Operations Orchestration Central and log back in as the csaoouser.
The HP CSA content packs must be deployed after you have deployed the base HP Operations Orchestration content packs.
From HP Operations Orchestration Central, click the Content Management button.
Browse to the content packs on the system. Select a content pack and click Open then Deploy. Find, select, open, and deploy the following base content packs in the order shown below:
Note: These are the base content packs provided by HP Operations Orchestration. Refer to the HP Operations Orchestration documentation for the location of these content packs. These base content packs are not included in the installation of HP CSA.
Note: Do not deploy the HP CSA content pack until after you have deployed the base content packs. The HP CSA content pack must be deployed separately and after you have deployed the base content packs.
The deployment may take a few minutes and the dialog will show a progress bar.
When the deployment succeeds, click Close to close the dialog.
Navigate to the
directory, select the oo10-csa-cp-4.10.000 content pack, and click Open.%CSA_HOME%
$CSA_HOME
\CSAKit-4.1\OO Flow Content\10X%CSA_HOME%
$CSA_HOME
/CSAKit-4.1/OOFlowContent/10X
Click Deploy.
The deployment may take a few minutes and the dialog will show a progress bar.
Click the Deploy New Content icon.
Navigate to the
directory, select all the content packs, and click Open.%CSA_HOME%
$CSA_HOME
\Tools\ComponentTool\contentpacks\%CSA_HOME%
$CSA_HOME
/Tools/ComponentTool/contentpacks/
Click Deploy.
The deployment may take a few minutes and the dialog will show a progress bar.
Set up system accounts for the HP CSA content pack:
Enter the following information if it is not already configured:
Field | Recommended Value |
---|---|
System Account Name | CSA_REST_CREDENTIALS |
User Name | ooInboundUser |
Password | cloud |
Note: The User Name configured for the CSA_REST_CREDENTIALS System Account setting must match the Property Value (HP Operations Orchestration version 9.07) or Override Value (HP Operations Orchestration version 10.10) configured for the CSA_OO_USER System Property setting.
Enter the following information if it is not already configured:
Field | Recommended Value |
---|---|
System Account Name | CSA_SERVICEMANAGER_CREDENTIALS |
User Name | falcon |
Password |
<leave_blank> |
Set up the following system properties for the HP CSA content pack:
Enter the following information if it is not already configured:
Field | Recommended Value |
---|---|
Name | CSA_REST_URI |
Override Value | https://<csa_hostname>:8444/csa/rest |
If the HP Single Sign-On (HPSSO) was enabled during installation of HP CSA, HPSSO can be configured between HP CSA and HP Operations Orchestration. Configuring HPSSO allows you to launch HP Operations Orchestration from the Cloud Service Management Console without having to log in to HP Operations Orchestration.
HP CSA provides an out-of-the-box user (admin) and password (cloud) and, earlier in this section, you configured an internal user for HP Operations Orchestration with the same username and password. When HP Single Sign-On is configured between HP CSA and HP Operations Orchestration, this user can be used for single sign-on. That is, if you are logged in to HP CSA as the admin user, you can launch HP Operations Orchestration from the Cloud Service Management Console and not have to log in to HP Operations Orchestration. You can also configure LDAP users for single sign-on.
Note: In order to use HPSSO between HP CSA and HP Operations Orchestration, the systems on which HP CSA and HP Operations Orchestration are installed must be in the same domain.
To configure and enable HPSSO on HP Operations Orchestration, do the following:
Log in to HP Operations Orchestration Central.
Click the System Configuration button.
Select Security > SSO.
Select the Enable checkbox.
Enter the InitString. This is the value to which the crypto InitString
attribute is set in the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\WEB-INF\hpssoConfiguration.xml
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/WEB-INFhpssoConfiguration.xml
file. For example, if the entry in the file is crypto InitString="lOJisF9Slbf79hmLsd"
, copy lOJisF9Slbf79hmLsd
to this field. This string is used to encrypt and decrypt the LWSSO_COOKIE_KEY cookie that is used to authenticate the user for single sign-on.
Enter the Domain. This is the domain name of the network of the servers on which HP CSA and HP Operations Orchestration are installed.
Click Save.
In order to enable single sign-on for LDAP users, you must either configure HP CSA and HP Operations Orchestration to use the same LDAP source or, if HP CSA and HP Operations Orchestration use different LDAP sources, configure the same users in both sources. In either case, the HP CSA user must be assigned to the CSA Administrator or Service Operations Manager role and the HP Operations Orchestration user must be assigned any role that allows flows to be viewed.
To configure LDAP for HP Operations Orchestration, do the following:
Log in to HP Operations Orchestration Central.
Click the System Configuration button.
Select Security > LDAP.
Click Save.
These properties are used to integrate with HP Operations Orchestration. In the subscription event overview section of the Operations area in the Cloud Service Management Console, for HP Operations Orchestration version 10.10, selecting the Process ID opens HP Operations Orchestration to the detailed page of the selected process when these properties are configured.
Edit the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties
file and configure the following properties:
Property | Description |
---|---|
OOS_URL |
The URL used to access HP Operations Orchestration Central. This is the HP Operations Orchestration used for provisioning topology designs (HP Operations Orchestration version 10.10). Set this URL to the system on which HP Operations Orchestration version 10.10 is installed. For example, |
OOS_USERNAME |
The username used to log in to HP Operations Orchestration Central. Set this username to admin. |
OOS_PASSWORD |
The encrypted password used by the user defined in Set this property to the encrypted value of the user defined in |
For each system running HP CSA, import the root certificate of each HP Operations Orchestration's Certificate Authority.
Import HP Operations Orchestration's certificate into HP CSA
Import the root certificate of HP Operations Orchestration's Certificate Authority into HP Cloud Service Automation (you must first export HP Operations Orchestration's certificate from HP Operations Orchestration's truststore and then import it into HP CSA's truststore).
%ICONCLUDE_HOME%
(Windows)
or $ICONCLUDE_HOME
(Linux).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 HP Operations Orchestration system
to the system running HP Cloud Service Automation
(in this example, the file is copied to
C:\
/tmp
).On the system running HP Cloud Service Automation, run the following command:
"<csa_jre>\bin\keytool" -importcert -alias tomcat -file C:\oo.crt
-keystore <csa_jre>\lib\security\cacerts -storepass changeit$CSA_JRE_HOME/bin/keytool -importcert -alias tomcat -file /tmp/oo.crt
-keystore $CSA_JRE_HOME/lib/security/cacerts -storepass changeit
where <csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed.
yes
.To restart HP CSA:
On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Cloud Service Automation service and select Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
Install HP Matrix Operating Environment infrastructure orchestration (infrastructure orchestration) according to the manufacturer's recommendations. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
The HP Cloud Service Automation System and Software Support Matrix is 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).
To configure HP Matrix Operating Environment infrastructure orchestration, refer to
for more information.%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
matrix operating environment\
/
README.txt
Install vCenter according to the manufacturer's recommendations. For example, follow the VMware best practices for managing individual ESX servers from a vCenter instance. You can find the VMware documentation at http://www.vmware.com/support/pubs/.
You must have a vCenter instance that can support the flows that actuate vSphere VMs. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
Both the HP Cloud Service Management Console Help, which is available in a printable PDF format, and the HP Cloud Service Automation System and Software Support Matrix are 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).
Install HP Network Automation according to the manufacturer's recommendations. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
Installation notes:
HP software product documentation and the HP Cloud Service Automation System and Software Support Matrix are 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).
The following tasks are required to configure HP Network Automation to integrate successfully with HP Cloud Service Automation:
If HP CSA and HP Network Automation are not installed on the same system, copy the HPN Virtual Network.exp
command script to the system on which HP Network Automation is installed.
The default location of the command script file is
where
%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
network automation%CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed (for example,
C:\Program Files\Hewlett-Packard\CSA/usr/local/hp/csa
).
From the Import/Export Scripts/Diagnostics page, click Choose File and
browse to the location of the HPN Virtual Network.exp
command script.
Click Continue.
The message Important: You have successfully imported one or more Command Scripts or
Diagnostics.
displays.
Vlan Id
, Vlan SubnetIP
, and Vlan SubnetMask
.
For example, set Vlan Id = 200, Vlan Subnet IP = 192.168.30.1 and Vlan Subnet Mask = 255.255.255.0.Click Save.
If the networking switch is already discovered and a device snapshot is successfully
taken in the HP Network Automation portal, the message
Succeeded
displays.
If you are using an HP networking switch, verify that the HPN Create Vlan
and
HPN Delete Vlan
command scripts use the EXT_HP_Procurve Network Automation driver
that supports a wide range of HP networking switches. If you want to use another networking switch,
update the mode of each command script.
To verify/update the command script mode:
HPN Create Vlan
, click Edit.HPN Delete Vlan
command script.Install HP Server Automation to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
You can determine your version and patch level by using the HP Server Automation Client and selecting Help > About.
Installation notes:
HP software product documentation is 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).
The following tasks are required to configure HP Server Automation to allow read and write access to the required areas:
Click New User in the Users tab toolbar and complete the following fields using the values listed in the following table:
Field Name | Value |
---|---|
Last Name | Service Account |
First Name | CSA |
Full Name | CSA Service Account |
Email Address | <your email address> |
User Name | hpcsa |
Password | <password> |
Click New Group and complete the following fields using the values listed in the following table:
Field Name | Value |
---|---|
Group Name | hpcsa-admin |
Group Description | HPCSA Administrators |
Not Assigned | Read & Write |
Opsware | Read |
Select the Facilities tab and select Read & Write to the appropriate facility.
If only one facility exists, select Read & Write for it.
Select the OGFS Permissions tab, click Add Permissions, and enter the following permissions:
root
.Click Add Permissions and enter the following permissions:
Verify that the client is installed.
If neither the icon nor the Start Menu link appear, then you need to install the client by performing the following steps:
You must have a JRE installed in order to use the Opsware Launcher on a Windows system.
Launch the client with the following credentials:
The above login information may vary depending on your installation.
These steps prepare a VMware template to self-register with HP Server Automation.
Virtual machines (VMs) created by the HP Cloud Service Automation solution are created based on virtual machine templates. The HP Cloud Service Automation flows reference a vSphere template name, and perform a clone operation to provision new virtual machines. These templates would generally provide an operating system image only, with no application software installed.
To allow applications (such as Apache) to be deployed to the image, you must install and configure HP Server Automation and create a template that includes the HP Server Automation Agent software. That is, in order to manage the virtual server and to install application software, the clones are configured to self-register upon power-on with an HP Server Automation system. Once registered as a managed server, software policies are applied to the server in order to install and configure the correct applications. Refer to the HP Server Automation Policy Setter Guide and the HP Server Automation Application Deployment User Guide in the HP Server Automation documentation for more information on managing servers and configuring software policies. HP software product documentation is 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).
For cloned virtual machines to register with the HP Server Automation system upon power-on, prepare a template with an HP Server Automation agent. The following is a general outline of the steps to be performed:
First, create a virtual machine with the appropriate operating system image that you would like to template. Provision the VM with an operating system through any method supported by vSphere:
Refer to the appropriate vSphere documentation to create a new virtual machine with an installed operating system image.
Refer to the vSphere documentation set for detailed information on the creation, configuration, and operating system installation for a new virtual machine. There are several options to install an operating system onto a new virtual machine. One of the options available is to use the PXE network boot facility from the HP Server Automation server, with an operating system installation profile that integrates the installation of an HP Server Automation agent. A virtual machine which is provisioned using this method starts the agent upon bootup, and attempts to register it with the HP Server Automation system.
If you use another method to provision an operating system on the virtual machine, the HP Server Automation agent can be installed from the HP Server Automation system. You can refer to the product documentation for an expanded discussion of this process; the following instructions describe one method.
Discover the virtual machine in the Unmanaged Servers (HP SA 9.x) or SA Agent Installation (HP SA 10.x) window in HP Server Automation. You can scan an entire subnet or enter the IP address for the virtual machine and initiate a scan to discover it.
Click OK.
When the installation process completes successfully, the agent is installed, and the virtual machine is visible in the All Managed Servers tab. The hostname has not been set, as we plan to convert this virtual machine to a generic template. So, the default host name is used for the virtual machine.
The agent on our virtual machine template must be prepared to install and register a new machine server with HP Server Automation each time we create a new clone. To prepare the agent we must "sanitize" the agent configuration on our template machine by doing the following:
Execute the BRDC HPSA agent sanitizer APX:
In the Specify any needed parameters for this program execution field, enter the Object ID, which you previously obtained for the virtual server template:
Shut down the virtual machine after the job completes successfully and the agent has been prepared.
Do not reboot this virtual machine again until after it has been converted to a vSphere template.
The template is now ready to use to clone new virtual machines. HP Cloud Service Automation uses a simple customization template that sets the hostname equal to the VM name. Additional customization is possible during the clone operation. See the Basic Customization section below.
When a newly cloned virtual machine powers up, the HP Server Automation Agent installs and then contacts the HP Server Automation system to self-register. Shortly after power on, you can refresh the All Managed Servers view in the HP Server Automation client to locate the new virtual machine record.
Perform the following basic customizations:
Customize as appropriate, noting two important items:
The template must be installed on the system containing the vSphere client software. See Configure VMware vCenter for more information.
Consult the vSphere documentation for additional details. You can find the VMware documentation at http://www.vmware.com/support/pubs/.
Configure VMware vCenter by installing prepared templates. In the vSphere environment, a template is a master copy of a virtual machine that can be used to create many clones. A clone is a copy of a virtual machine.
You can learn more about creating templates and working with clones in vSphere by referring to VMware's vSphere Virtual Machine Administration Guide for vCenter Server (EN-000312-02), available in the VMware documentation. You can find the VMware documentation at http://www.vmware.com/support/pubs/.
Virtual machines created by the HP Cloud Service Automation solution are created based on virtual machine templates. To allow applications (such as Apache) to be deployed to the image, you must create a template that includes HP Server Automation Agent software. See Prepare a VMware Template to Self-Register with HP Server Automation for more information.
To install a prepared template, do the following:
Copy the template folder to the datastore by clicking on the Upload files to this datastore button.
The following image shows the Datastore Browser window with Upload files to this datastore highlighted. It also shows a rhel53x64-clone
folder that was uploaded to this datastore:
Consult the vSphere documentation for additional details. You can find the VMware documentation at http://www.vmware.com/support/pubs/.
Install HP SiteScope to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
Installation notes:
HP software product documentation is 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).
The following tasks are required to configure HP SiteScope to integrate successfully with HP Cloud Service Automation:
HP SiteScope is installed with a default of secured API calls required for configuring monitors. HP Cloud Service Automation does not support secured API calls; therefore, you must change this setting. To re-configure HP SiteScope so it does not use secure APIs, you must make the following change to the configuration:
Stop the HP SiteScope service by typing the following command in a console window:
net stop SiteScope
<sitescopeInstallDir>\groups\master.config
file in a text editor.Change the _accessControlled=true
property value to _accessControlled=false
.
Restart the HP SiteScope service by typing the following command in a console window:
net start SiteScope
From the HP Cloud Service Automation server, copy the
file
to the %CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
sitescope\
/
CSA templates autoimport.tmpl<sitescopeInstallDir>\persistency\import
directory on the
HP SiteScope server. When the
CSA templates autoimport.tmpl
file is processed,
HP SiteScope creates a template container
(CSA templates
) and two credential profiles
(WINDOWS-CSA-TARGETS
and LINUX-CSA-TARGETS
).
CSA templates
container. You must wait for the
HP SiteScope server to finish processing the
CSA templates autoimport.tmpl
file before the CSA templates
template container is displayed.WINDOWS-CSA-TARGETS
and LINUX-CSA-TARGETS
credential profiles, which you will
configure in Step 4: Configure
HP Cloud Service Automation Credential Profiles.Two additional HP Cloud Service Automation templates,
CSA templates Silver
and CSA templates Gold
, must be
manually imported. These templates are used by the CSA_BP_VCENTER_COMPUTE_SITESCOPE_MODIFY_v4.10.00 service design.
Note: You must be able to access files in the
directory from the
HP SiteScope Dashboard. If necessary,
copy this directory to the system from which you are
launching the HP SiteScope Dashboard.%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
sitescope
%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
sitescope
(or the directory to which
this directory was copied) and import CSA templates Silver.tmpl
.CSA templates Gold.tmpl
.Configure the credentials used to log in to every Windows system and every Linux system monitored by HP SiteScope. The credentials to all Windows systems must be the same. Likewise, the credentials to all Linux systems must be the same.
Configure the credentials used to log in as the administrator of HP SiteScope. These credentials are used by HP Cloud Service Automation when configuring HP SiteScope resource providers from the Cloud Service Management Console.
Install HP Universal CMDB to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
If you are using an existing installation of HP Universal CMDB, then you should verify that the necessary patches and updates have been applied. If not, then follow the instructions presented here to update your installation.
If you are installing HP Universal CMDB, then you should follow the installation instructions in the HP Universal CMDB documentation and then follow the instructions presented here to configure your installation.
Monitor the service status by browsing to http://localhost:8080/status.
You will need to wait until the Default Client status is up on the status page. This takes approximately five minutes. Until then, the HP Universal CMDB console cannot be used.
HP software product documentation is 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).
To configure HP Universal CMDB, deploy a file to your HP Universal CMDB server:
From the HP Cloud Service Automation server, navigate
to the
folder where
%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
ucmdb%CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed.
%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
ucmdb\
/
CSAIntegration.zip
to the
HP Universal CMDB server.%CSA_HOME%
$CSA_HOME
\
/
CSAKit-4.1\
/
Lib\
/
ucmdb\
/
README.txt
file
for more information on how to deploy the zipped file.No installation is required for HP Cloud Services as it is accessible through the Web. However, you will need to configure HP Cloud Services to integrate with HP Cloud Service Automation. See Configure HP Cloud Services in this document for more information.
The following tasks are required to configure HP Cloud Services to integrate successfully with HP Cloud Service Automation:
In order to access HP Cloud Services, you must be a registered user. Sign up for HP Cloud Services by accessing this URL from a supported Web browser: https://console.hpcloud.com/signup
To create an HP Cloud Services instance, you must have a Security Group and KeyPair configured in the HP Cloud Services environment:
You can configure the Security Group and KeyPair values as default values in the Server Group component properties of an HP CSA service design.
Install HP Service Manager according to the manufacturer's recommendations. See HP Cloud Service Automation System and Software Support Matrix for version requirements.
Installation notes:
HP software product documentation and the HP Cloud Service Automation System and Software Support Matrix are 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).
The following tasks are required to configure HP Service Manager to integrate successfully with HP CSA:
Importing the HP CSA integration file into HP Service Manager creates the OO_CSA and WSCentralServiceService script libraries and OnChangeApproval and OnChangeDenied macros.
Locate the HPSM_CSA_Integration_file.unl
file installed with
HP CSA.
The default location of the file is
%CSA_HOME%\CSAKit-4.1\Lib\service manager$CSA_HOME/CSAKit-4.1/Lib/service manager
where
%CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed (for example,
C:\Program Files\Hewlett-Packard\CSA/usr/local/hp/csa
).
If HP CSA and HP Service Manager are installed on different systems, copy this file to the system running HP Service Manager.
Enter unload in the command window and click RUN. Verify that the HPSM CSA Integration
file is listed.
localhost
with the hostname of the HP Operations Orchestration Central server. Click Save.Update the sample Approval Definition provided with HP Service Manager to create a new subscription approval.
Verify or set the following fields and values:
Field Name | Value |
---|---|
Name | Subscription Approval |
Approval Condition | true |
Approval Type | All must approve |
Group/Oper | Change.Approver |
Sequence | 1 |
Condition | true |
Create a self-signed certificate using the fully-qualified domain name of the system on which HP Operations Orchestration is installed to replace the existing HP Operations Orchestration Central server certificate.
Note: If the existing HP Operations Orchestration Central server certificate uses a CN with the fully-qualified domain name of the system on which HP Operations Orchestration is installed, you do not need to create a self-signed certificate. You can use the existing HP Operations Orchestration Central server certificate.
Refer to Replacing the Central SSL/TLS Server Certificate with a Self-Signed Certificate section in the System Configuration and Hardening Guide (a copy of this guide can be found in %ICONCLUDE_HOME%\docs\Configuration and Hardening Guide.pdf
or $ICONCLUDE_HOME/docs/ConfigurationandHardeningGuide.pdf
).
Export HP Operations Orchestration's SSL certificate. On the system on which HP Operations Orchestration is installed, open a command prompt and type the following:
Windows
cd "%ICONCLUDE_HOME%"
.\java\bin\keytool -export -alias tomcat -file pas.crt
-keystore .\Central\var\security\key.store -storepass changeit
Linux
cd $ICONCLUDE_HOME
./java/bin/keytool -export- -alias tomcat -file pas.crt
-keystore ./Central/var/security/key.store -storepass changeit
Windows
cd "%ICONCLUDE_HOME%"
.\jre1.6\bin\keytool.exe -exportcert -alias pas -file pas.crt
-keystore .\Central\conf\rc_keystore -storepass bran507025
Linux
cd $ICONCLUDE_HOME
./jre1.6/bin/keytool.exe -exportcert -alias pas -file pas.crt
-keystore ./Central/conf/rc_keystore -storepass bran507025
pas.crt
to the system on which HP Service Manager is installed,
to the <HPSM_install_directory>\Server\RUN\jre\lib\security
(Windows)
or <HPSM_install_directory>/Server/RUN/jre/lib/security
(Linux) directory.On the system on which HP Service Manager is installed, import the HP Operations Orchestration certificate. Open a command prompt and type the following:
Windows
cd "<HPSM_install_directory>\Server\RUN\jre\lib\security"
"<HPSM_install_directory>\Server\RUN\jre\bin\keytool.exe"
-importcert -alias tomcatpas -file pas.crt
-keystore cacerts -storepass changeit
Linux
cd <HPSM_install_directory>/Server/RUN/jre/lib/security
<HPSM_install_directory>/Server/RUN/jre/bin/keytool.exe
-importcert -alias tomcatpas -file pas.crt
-keystore cacerts -storepass changeit
When HP Service Manager accesses HP Operations Orchestration as a client, the HP Operations Orchestration certificate uses a hardcoded key for the CN. On the system running HP Service Manager, this CN (opsware.comthe fully-qualified domain name (FQDN) of the system on which HP Operations Orchestration is installed) must be mapped to the IP address of the system on which HP Operations Orchestration Central server is installed. The following is an example of how to map the CN to the IP address:
On the system running HP Service Manager,
open C:\Windows\system32\drivers\etc\hosts
(Windows)
or /etc/hosts
(Linux) in a text editor.
Add the following to the file:
<IP_address_of_HPOO_central_server> <FQDN>opsware.com
where <IP_address_of_HPOO_central_server> is the IP address of the system on which HP Operations Orchestration Central server is installed and <FQDN> is the fully-qualified domain name of the system on which HP Operations Orchestration Central server is installed.
You have completed the initial installation and configuration of HP CSA and can begin familiarizing yourself with the capabilities of HP CSA.
Launch the Cloud Service Management Console
(type the following URL in a supported Web browser:
https://<csahostname>:8444/csa
) and log in using
the out-of-the-box user (admin) and password (cloud).
Launch the default Marketplace Portal
(type the following URL in a supported Web browser:
https://<csahostname>:8444/mpp
) and log in using
the out-of-the-box user (consumer) and password (cloud).
To complete the configuration of HP CSA, refer to the following documents:
HP Cloud Service Automation Configuration Guide: The configuration guide describes the process for preparing LDAP for the Cloud Service Management Console and for consumer organizations, requesting software licenses, configuring SSL, customizing the Cloud Service Management Console, configuring HP CSA to be compliant with FIPS 140-2, and performing other HP CSA customizations. The configuration guide also describes the process of how to import the sample HP Operations Orchestration flows included with HP CSA.
Configuring an HP CSA Cluster for Server Failover: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using an Apache Web server as a proxy.
HP Cloud Service Automation Service Design Guide: The service design guide describes how to use HP CSA to create automated, on-demand cloud services. The guide covers key concepts and steps for HP CSA service design, including sequenced and topology design models, the role of the service design, design layouts and components, service lifecycles, and service options.
You have completed the initial installation and configuration of the Marketplace Portal and can begin familiarizing yourself with the capabilities of the Marketplace Portal.
Launch the default Marketplace Portal
(type the following URL in a supported Web browser:
https://<csahostname>:8444/mpp
) and log in using
the out-of-the-box user (consumer) and password (cloud).
For more information about the Marketplace Portal, refer to the online help.
Based on your selections on the previous page, perform the following steps. It is recommended that you perform each step in the following order:
This guide provides information for installing the HP Cloud Service Automation application. Successful implementation of the application requires knowledge of the integrated products, as well as the HP Cloud Service Automation solution. 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.
For information about how these parts fit together, see the HP Cloud Service Automation Concepts Guide.
You should review the HP Cloud Service Automation System and Software Support Matrix for version requirements.
Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
From the system on which HP CSA is installed, copy the HP CSA SSL certificate to the system on which the remote instance of the Marketplace Portal will be installed.
On the system on which HP CSA is installed, the HP CSA SSL certificate is located in %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\configuration\jboss.crt$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/configuration/jboss.crt
. Copy this file to the system on which you are installing the remote instance of the Marketplace Portal. Remember the name and location to which you have copied this SSL certificate as you will be asked for this information when you install the remote instance of the Marketplace Portal.
This file is needed for SSL verification which, by default, is enabled for the Marketplace Portal.
Configure a group and user for HP CSA:
Create a group called csagrp. Enter the following:
groupadd csagrp
Create a user called csauser and assign this user to the csagrp. Enter the following:
useradd -g csagrp -m csauser
(Ubuntu) oruseradd -g csagrp -m csauser -s /bin/bash
(RHEL)
Assign a password to the csauser. Enter the following:
passwd csauser
When prompted, enter the password.
This section describes how to install the Marketplace Portal on a remote system, a system that is not the same system on which the Cloud Service Management Console is installed. The remote system must meet the same system requirements for HP Cloud Service Automation. See the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
Note: In the following instructions, %CSA_HOME%
$CSA_HOME
is the directory in which the Marketplace Portal is installed.
Note: Installation log files are written to the
directory.%CSA_HOME%
$CSA_HOME
\_CSA_4_1_0_installation\Logs\
To install HP Cloud Service Automation (HP CSA), complete the following steps.
Run the setup.exe
installation file.
On the Introduction screen, read the information and click Next.
Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.
If the following error message displays:
Another version of HP CSA
is configured in the registry. However, HP CSA
has been uninstalled (the HP CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing HP CSA. Refer to the
HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml
file (you may need to show hidden files), make a backup copy, delete all
HP CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select HP CSA and Marketplace Portal and click Next.
Choose a location in which to install HP CSA and click Next (
is set to this location).%CSA_HOME%
$CSA_HOME
The default location is
C:\Program Files\Hewlett-Packard\CSA
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
Choose the JRE that will be used by HP CSA.
In this documentation,
the directory in which the JRE is installed will be referred to as
<csa_jre>
.
For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
OpenJDK JRE
The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, click Open JRE and click Next.
The default location in which the OpenJDK JRE is installed is
C:\Program Files\Hewlett-Packard\CSA\openjre
.
Oracle JRE
If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE, select the location in which you installed this JRE, and click Next.
The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, click Choose and select the location in which you installed the JRE that will be used by HP CSA.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
Select the type of database installed (Microsoft SQL Server)(Oracle)(PostgreSQL) and click Next.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($).
For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths.
However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the
HP Software Support Web site at
http://h20230.www2.hp.com/selfsolve/manuals/
(this site requires that you register with HP Passport). Click Choose to select the directory.
Define the database instance on which the HP CSA database components should be installed or where the HP CSA database schema already exists. Enter the following database information and click Next.
Field Name | Description |
---|---|
Database Host | The hostname or IP address of the server where the database is located. When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4] or [::1] . |
Database Port | The database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
Database NameOracle SID |
The name of the database instance on which the HP CSA database schema will be installed. If you are creating a new HP CSA database schema, this is the name of the database instance on which the HP CSA database components will be installed. If you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version HP 4.10, this is the name of the database instance on which the HP CSA database schema exists. For an Oracle database, this is the System ID (SID). |
Database Username | The username of the database user you configured for HP CSA after installing the database. |
Database Password | The password for the database user. |
If you created a reporting database role and read-only userreporting database user when you configured the database, select the Reporting User checkbox and enter the following information:
Field Name | Description |
---|---|
CSA Reporting Database Username | The username of the database user you configured for reporting purposes for HP CSA after installing the database. |
CSA Reporting Database Password | The password for the CSA reporting database user. |
Install HP CSA database components onto the database instance to create the HP CSA database schema, if it does not exist.
Click Yes to install HP CSA database components and create the HP CSA database schema. When you select this option, the HP CSA service automatically starts when you exit the installer.
Click No if you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version 4.10. When you select this option, the HP CSA service does not start when you exit the installer. Refer to the end of this section for information on how to start and stop the HP CSA service.
From the Enter host name screen, enter the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.
Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.
By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.
If you do not want to use HPSSO, you can disable it.
You MUST disable HP Single Sign-On if you are installing HP CSA in a FIPS 140-2 compliant environment.
If enabled, enter the domain name of the network to which the server on which you are installing HP CSA belongs and click Next.
Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.
Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.
Review your selections and click Install to complete the installation.
In some instances, you may be asked to restart your system.
Click Yes, restart my system to restart your system when you exit the installer.
Click No, I will restart my system myself to restart your system at a more convenient time.
Click Done to exit the installer.
Verify that the HP Cloud Service Automation and Marketplace Portal services have started by navigating to Control Panel > Administrative Tools > Services. It can take up to five minutes for the HP Cloud Service Automation to start. If one or both services have not started, right-click on the service and select Start.
The installer creates the HP Cloud Service Automation and Marketplace Portal services. If you opted to install the HP Cloud Service Automation database components, the installer starts these services. The HP Cloud Service Automation service must be running in order to access the Cloud Service Management Console and the Marketplace Portal service must be running in order to access the Marketplace Portal.
To start, stop, and restart the HP Cloud Service Automation and Marketplace Portal services, navigate to Control Panel > Administrative Tools > Services, right-click on a service, and select the desired action.
Note: Installation log files are written to the
directory and are named %CSA_HOME%
$CSA_HOME
/_CSA_4_1_0_installation/Logs/csa_*.txt
.
To install HP Cloud Service Automation (HP CSA), complete the following steps.
Install the unzip utility if it is not already installed. Enter the following:
apt-get install unzip
Create an installation directory for HP CSA
(this document assumes that you will install the product in
/usr/local/hp/csa
and all examples
used in this document are based on this assumption). Enter the following:
mkdir -p /usr/local/hp/csa
For the installation directory, set the owner to csauser and the group to csagrp. Enter the following:
chown -R csauser:csagrp /usr/local/hp/csa
setup.bin
) to the system and go to the directory in which it has been copied.Verify that setup.bin
is owned by csauser and csauser has full permissions to the file. If necessary,
do the following:
Enter one or both of the following commands:
chown csauser setup.bin
chmod u+rwx setup.bin
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.
Run the setup.bin
installation file (as the csauser).
Note: You must run setup.bin
as the csauser. If you
install HP CSA as another user,
you may not be able to run HP CSA.
As the csauser, enter the following:
./setup.bin
Read the Introduction and click enter to continue with the installation.
Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.
If the following error message displays:
Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml
file, make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml
file, and restart the installer.
Verify that no HP CSA services are running on the system. Open a command prompt and type ps -ef | grep csa
. If the csa
process is running, kill it.
After verifying that no HP CSA services are running on the system, close the command prompt.
Select enter to continue the installation.
Select the application to install and click Enter.
HP CSA and Marketplace Portal
Installs the entire HP CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Marketplace Portal
Installs only the Marketplace Portal on the system.
Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.
The default location is /usr/local/hp/csa
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.
Choose the JRE that will be used by HP CSA.
In this documentation,
the directory in which the JRE is installed will be referred to as
$CSA_JRE_HOME
.
For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
OpenJDK JRE
The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, type 1 and select Enter.
The default location in which the OpenJDK JRE is installed is
/usr/local/hp/csa/openjre
.
Oracle JRE
If you have installed a supported version of Oracle JRE to be used by HP CSA, type 2 and select Enter. Type the location in which you installed this JRE and select Enter.
The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, type in the location in which you installed the JRE that will be used by HP CSA and select Enter.
Define the database instance on which the HP CSA database components should be installed. Enter the following database information (select Enter after each entry).
Enter the type of database you have installed: MSSql (Microsoft SQL Server)OraclePostgres (PostgreSQL).
For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
[f000:253c::9c10:b4b4]
or [::1]
. The default value is the IP address of the localhost (127.0.0.1).Enter the database port. This is the database port number, such as 1433 (Microsoft SQL Server)1521 (Oracle)5432 (PostgreSQL).
Enter the database name. This is the name of the database instance on which the
HP CSA
database schema will be installed. If you are creating a new
HP CSA
database schema, this is the name of the database instance on which the
HP CSA database components
will be installed. If you are using an existing
HP CSA database schema
that was created as part of a prior successful installation of
HP CSA version
HP 4.10,
this is the name of the database instance on which
the HP CSA database schema already exists.
If you followed the examples in this document, enter csadb
.
Enter the CSA database user name. This is the user name of the database user you configured for
HP Cloud Service Automation after installing the database.
If you followed the examples in this document, enter csadbuser
.
Enter the CSA reporting database username (optional). This is the username of the database user you configured for reporting purposes for
HP CSA after installing the database.
If you followed the examples in this document, enter csareportingdbuser
.
Enter the HP CSA server hostname. This is the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.
Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.
By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.
If you do not want to use HPSSO, you can disable it. Type 2 and select Enter.
To enable HPSSO, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing HP CSA) and select Enter.
Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.
Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.
Review your selections and select Enter to complete the installation or Ctrl-c to exit the installation.
When the installation completes, select enter to exit the installer.
Define the CSA_HOME and JAVA_HOME environment variables
and add /sbin
to the PATH variable for the csauser user. Set CSA_HOME to the location where
HP CSA is installed. In a startup script
for the csauser user (for example, .profile
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux)), add the following:
export CSA_HOME=/usr/local/hp/csa
export JAVA_HOME=<csa_jre>$CSA_JRE_HOME
export PATH=$PATH:/sbin
<csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by HP CSA
is installed.Source the startup file in
which you set the CSA_HOME, JAVA_HOME,
and PATH environment variables. If you edited
.bashrc
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux),
enter the following:
. ./.bashrc
(Ubuntu). ./.bash_profile
(Red Hat Enterprise Linux)
Create an HP CSA service and a Marketplace Portal service to start and stop the HP CSA and Marketplace Portal processes.
Go to the directory in which HP CSA is installed. For example:
cd /usr/local/hp/csa
Copy the csa
and mpp
scripts to the /etc/init.d
directory. Enter the following:
cp ./scripts/csa /etc/init.d
cp ./scripts/mpp /etc/init.d
Change permissions of the scripts. Enter the following:
chmod 755 /etc/init.d/csa
chmod 755 /etc/init.d/mpp
Log in as csauser and start the HP CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
The HP Cloud Service Automation service must
be running in order to access the
Cloud Service Management Console.
You can start this service by typing service csa start
.
You can restart this service by typing service csa restart
.
You can stop the service by typing service csa stop
.
You can check the status of the service by typing service csa status
.
The Marketplace Portal service must be running in order to access the
Marketplace Portal.
You can start this service by typing service mpp start
.
You can restart this service by typing service mpp restart
.
You can stop the service by typing service mpp stop
.
You can check the status of the service by typing service mpp status
.
Note: Installation log files are written to the
directory.%CSA_HOME%
$CSA_HOME
\_CSA_4_1_0_installation\Logs\
To install a remote instance of the Marketplace Portal, complete the following steps.
Run the setup.exe
installation file.
On the Introduction screen, read the information and click Next.
Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.
If the following error message displays:
Another version of HP CSA
is configured in the registry. However, HP CSA
has been uninstalled (the HP CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing HP CSA. Refer to the
HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml
file (you may need to show hidden files), make a backup copy, delete all
HP CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select Marketplace Portal and click Next.
Choose a location in which to install the Marketplace Portal and click Next (
is set to this location).%CSA_HOME%
$CSA_HOME
The default location is
C:\Program Files\Hewlett-Packard\CSA
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
Caution:
The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.
Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.
Field Name | Description |
---|---|
HP CSA Host | The fully-qualified domain name of the system on which HP CSA is installed. |
HP CSA Port | The port number used to communicate with HP CSA. |
HP CSA Certificate | The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system. |
From the Hostname Configuration screen, enter the fully-qualified domain name of this system, the one on which you are installing the Marketplace Portal, and click Install to complete the installation.
Click Done to exit the installer.
Verify that the Marketplace Portal service has started by navigating to Control Panel > Administrative Tools > Services. If the service has not started, right-click on the service and select Start.
The Marketplace Portal service must be running in order to access the Marketplace Portal.
To start, stop, and restart the Marketplace Portal service, navigate to Control Panel > Administrative Tools > Services, right-click on the Marketplace Portal service, and select the desired action.
Note: Installation log files are written to the
directory and are named %CSA_HOME%
$CSA_HOME
/_CSA_4_1_0_installation/Logs/csa_*.txt
.
To install HP Cloud Service Automation (HP CSA), complete the following steps.
Install the unzip utility if it is not already installed. Enter the following:
apt-get install unzip
Create an installation directory for HP CSA
(this document assumes that you will install the product in
/usr/local/hp/csa
and all examples
used in this document are based on this assumption). Enter the following:
mkdir -p /usr/local/hp/csa
For the installation directory, set the owner to csauser and the group to csagrp. Enter the following:
chown -R csauser:csagrp /usr/local/hp/csa
setup.bin
) to the system and go to the directory in which it has been copied.Verify that setup.bin
is owned by csauser and csauser has full permissions to the file. If necessary,
do the following:
Enter the following commands:
chown csauser setup.bin
chmod u+rwx setup.bin
Run the setup.bin
installation file (as the csauser).
Note: You must run setup.bin
as the csauser. If you
install HP CSA as another user,
you may not be able to run HP CSA.
As the csauser, enter the following:
./setup.bin
Read the Introduction and click enter to continue with the installation.
Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.
If the following error message displays:
Another version of HP CSA
is configured in the registry. However, HP CSA
has been uninstalled (the HP CSA installation
directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before
installing HP CSA. Refer to the
HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml
file, make a backup copy, delete all
HP CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.
The default location is /usr/local/hp/csa
.
Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.
If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.
Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.
Field Name | Description |
---|---|
HP CSA Host | The fully-qualified domain name of the system on which HP CSA is installed. |
HP CSA Port | The port number used to communicate with HP CSA. |
HP CSA Certificate | The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system. |
From the Hostname Configuration screen, enter the fully-qualified domain name of this system, the one on which you are installing the Marketplace Portal, and click Install to complete the installation.
Review your selections and select enter to complete the installation or ctrl-c to exit the installation.
When the installation completes, select enter to exit the installer.
Define the CSA_HOME and JAVA_HOME environment variables and add /sbin
to the PATH variable for the csauser user. In a startup script
for the csauser user (for example, .profile
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux)), add the following:
export CSA_HOME=/usr/local/hp/csa
export JAVA_HOME=<csa_jre>$CSA_JRE_HOME
export PATH=$PATH:/sbin
Source the startup file in
which you set the CSA_HOME, JAVA_HOME,
and PATH environment variables. If you edited
.profile
(Ubuntu) or .bash_profile
(Red Hat Enterprise Linux),
enter the following:
. .profile
(Ubuntu). .bash_profile
(Red Hat Enterprise Linux)
Create the Marketplace Portal service to start and stop the Marketplace Portal process.
Go to the directory in which the Marketplace Portal is installed. For example:
cd /usr/local/hp/csa
Copy the mpp
script to the /etc/init.d
directory. Enter the following:
cp ./scripts/mpp /etc/init.d
Change permissions of the script. Enter the following:
chmod 755 /etc/init.d/mpp
Log in as csauser and start the Marketplace Portal service. Enter the following:
service mpp start
The Marketplace Portal service must be running in order to access the
Marketplace Portal.
You can start this service by typing service mpp start
.
You can restart this service by typing service mpp restart
.
You can stop the service by typing service mpp stop
.
You can check the status of the service by typing service mpp status
.
For security reasons, the Marketplace Portal file system must be protected by the operating system. Do the following:
From the elevated command prompt, run the following command:
attrib +s +h "%CSA_HOME%\portal" /S /D /L
where %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed.
Run the following commands:
chown –R csauser:csagrp $CSA_HOME/portal
chmod –R 700 $CSA_HOME/portal
where csauser and csagrp are the user and group you configured for HP CSA when you installed HP CSA and %CSA_HOME%
$CSA_HOME
is the directory in which
HP Cloud Service Automation is installed.
Restart the csa and mpp services by running the following commands:
service csa restart
service mpp restart
The URL to launch the Marketplace Portal is displayed in the Cloud Service Management Console. Edit the csa.properties
file to update this URL. Do the following:
%CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties
file.csa.subscriber.portal.url
property value. Set the hostname to the fully-qualified domain name or IP address of the system on which the Marketplace Portal is remotely installed.Restart HP CSA.
To restart HP CSA:
On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.
Right-click on the HP Cloud Service Automation service and select Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart HP CSA, on the server that hosts HP CSA, type the following:
service csa restart
service mpp restart
Launch the default remote instance of a Marketplace Portal
Launch the default remote instance of the Marketplace Portal by typing one of the following URLs in a supported Web browser:
https://<csahostname>:8444/mpp
https://<mpphostname>:8089
where:
<csahostname> is the fully-qualified domain name of the system on which HP CSA is installed and the URL in the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\mpp.war\index.html
$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/mpp.war/index.html
file (on the system on which HP CSA is installed) has been updated to https://<mpphostname>:8089
.
<mpphostname> is the fully-qualified domain name of the system on which the Marketplace Portal instance resides.
Examples:
https://csa_system.abc.com:8444/mpp
https://mpp_system.abc.com:8089
The organization associated with the default Marketplace Portal is defined in the %CSA_HOME%\portal\conf\mpp.json
$CSA_HOME/portal/conf/mpp.json
file (on the system on which the Marketplace Portal instance resides). By default, this is the sample organization that is installed with HP CSA (CSA_CONSUMER). To modify the organization associated with the default Marketplace Portal, modify the defaultOrganizationName
property value by setting it to the <organization_identifier> of the desired organization, where <organization_identifier> is
the unique name that
HP Cloud Service Automation assigns to the
organization, based on the organization display name
(the organization identifier can be found in the General Information section of the
Organizations tile of the
Cloud Service Management Console).
Launch an organization-specific remote instance of a Marketplace Portal
Launch an organization's remote instance of the Marketplace Portal by typing the following URL in a supported Web browser:
https://<mpphostname>:8089/org/<organization_identifier>
where:
<organization_identifier> is the unique name that HP Cloud Service Automation assigns to the organization, based on the organization display name (the organization identifier can be found in the General Information section of the Organizations tile of the Cloud Service Management Console)
Example:
https://mpp_system.xyz.com:8089/org/ORGANIZATION_A
Caution:
Do not launch more than one organization-specific Marketplace Portal
from the same browser session. For example, if you launch ORGANIZATION_A's
Marketplace Portal in a browser, do not open a tab or another window
from that browser and
launch ORGANIZATION_B's Marketplace Portal.
Otherwise, the user who has logged in to the Marketplace Portal launched for
ORGANIZATION_A will start to see data for ORGANIZATION_B.
Instead, start a new browser session to launch another organization's
Marketplace Portal.
Use the following instructions to start, stop, or restart the Marketplace Portal service on the remote system.
To start the Marketplace Portal service, do the following:
To stop the Marketplace Portal service, do the following:
To restart the Marketplace Portal service, do the following:
To start Marketplace Portal, on the remote system, open a command prompt and type service mpp start
.
To stop Marketplace Portal, on the remote system, open a command prompt and type service mpp stop
.
To restart Marketplace Portal, on the remote system, open a command prompt and type service mpp restart
.
You have completed the initial installation and configuration of HP CSA and can begin familiarizing yourself with the capabilities of HP CSA.
Launch the Cloud Service Management Console
(type the following URL in a supported Web browser:
https://<csahostname>:8444/csa
) and log in using
the out-of-the-box user (admin) and password (cloud).
Launch the default Marketplace Portal
(type the following URL in a supported Web browser:
https://<csahostname>:8444/mpp
) and log in using
the out-of-the-box user (consumer) and password (cloud).
To complete the configuration of HP CSA, refer to the following documents:
HP Cloud Service Automation Configuration Guide: The configuration guide describes the process for preparing LDAP for the Cloud Service Management Console and for consumer organizations, requesting software licenses, configuring SSL, customizing the Cloud Service Management Console, configuring HP CSA to be compliant with FIPS 140-2, and performing other HP CSA customizations. The configuration guide also describes the process of how to import the sample HP Operations Orchestration flows included with HP CSA.
Configuring an HP CSA Cluster for Server Failover: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using an Apache Web server as a proxy.
HP Cloud Service Automation Service Design Guide: The service design guide describes how to use HP CSA to create automated, on-demand cloud services. The guide covers key concepts and steps for HP CSA service design, including sequenced and topology design models, the role of the service design, design layouts and components, service lifecycles, and service options.
You have completed the initial installation and configuration of the Marketplace Portal and can begin familiarizing yourself with the capabilities of the Marketplace Portal.
Launch the default Marketplace Portal
(type the following URL in a supported Web browser:
https://<csahostname>:8444/mpp
) and log in using
the out-of-the-box user (consumer) and password (cloud).
For more information about the Marketplace Portal, refer to the online help.
© Copyright 2010-2014 Hewlett-Packard Development Company, L.P.