Customized output from:
Document Release Date: January 2016 Software Release Date: January 2016 |
|
The only warranties for Hewlett Packard Enterprise Development LP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HPE required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2010-2016 Hewlett-Packard Development Company, L.P.
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
The OpenStack® Word Mark and the Square O Design, together or apart, are trademarks or registered trademarks marks of OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
RED HAT READY™ Logo and RED HAT CERTIFIED PARTNER™ Logo are trademarks of Red Hat, Inc.
This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.
The Cloud Service Automation Installation Guide for 4.60 is an interactive document that provides the information necessary to install the CSA (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 CSA, see the Cloud Service Automation Concepts Guide.
For information about the supported components and versions, see the Cloud Service Automation System and Software Support Matrix.
If you want to upgrade to CSA version 4.60, see the Cloud Service Automation Upgrade Guide.
Version: 4.60
Document Release Date: January 2016
Software Release Date: January 2016
The following steps are customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
Based on your selections 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 CSA application. Successful implementation of the application requires knowledge of the integrated products, as well as the CSA 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 Cloud Service Automation Concepts Guide.
You should review the Cloud Service Automation System and Software Support Matrix for version requirements.
Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)..
Configure a group and user for 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 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 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
CSA will be installed.
Note the location where you save the file(s) as this information must be provided when
CSA is installed.
These tasks must be completed before CSA is installed.
Separate database instances are required for CSA and the components it uses. You must create a separate database instance for:
Work with the database administrator to create a database that is used by the embedded Operations Orchestration, CSA (if it has not already been created), and the Identity Management component. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
You must provide the service name (global database name) of these databases when prompted for the database information during the installation of CSA. For example, when prompted for the CSA database information, provide the service of the CSA database. When prompted for the Identity Management component database information, provide the service name of the Identity Management component database. When prompted for the embedded Operations Orchestration database information, provide the service name of the embedded Operations Orchestration database.
A database user, used by the embedded Operations Orchestration, is needed when installing CSA. Work with the database administrator to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the csaoodbuser user:
Create user csaoodbuser identified by csaoodbuser default tablespace system temporary tablespace temp quota unlimited on system account unlock;
Grant CONNECT to csaoodbuser;
Grant CREATE VIEW, CREATE SEQUENCE, CREATE TABLE, CREATE PROCEDURE to csaoodbuser;
Commit;
You must provide this database username and password when prompted for the Operations Orchestration database information during the installation of CSA.
Create an Operations Orchestration database user (for example, csaoodbuser
). The Operations Orchestration database user, used by the embedded Operations Orchestration, is required. This user should inherit rights from parent roles and have superuser privileges.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role csaoodbuser login password '<csaoodbuser_password>' superuser inherit;
This is the user to whom you will grant access to the Operations Orchestration database when you create this database.
A database user is needed when installing the Identity Management component for CSA. Work with the database administrator to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the csaidmdbrole role and csaidmdbuser user:
Create user csaidmdbuser identified by csaidmdbuser;
Create role csaidmdbrole;
Grant CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE ANY SYNONYM to csaidmdbuser;
Grant csaidmdbrole to csaidmdbuser;
Alter user csaidmdbuser default role csaidmdbrole;
You must provide this user's username and password when prompted for the Identity Management component database information during the installation of CSA.
A database user is needed when installing CSA. Work with the database administrator to do the following (or refer to the manufacturer’s documentation for more information):
Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the csadbrole role and csadbuser user:
Create user csadbuser identified by csadbuser default tablespace system temporary tablespace temp quota unlimited on system account unlock;
Grant CONNECT to csadbuser;
Create role csadbrole;
Grant CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE ANY SYNONYM to csadbuser;
Grant csadbrole to csadbuser;
Alter user csadbuser default role csadbrole;
You must provide this user's username and password when prompted for the CSA database information during the installation of CSA.
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of 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 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 CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
USE csadb;
-- or connect to csadb in another wayCREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser;
Optionally, create a reporting
database user for CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
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 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, HPE 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 CSA (or refer to the manufacturer’s documentation for more information). HPE recommends that the initial tablespace size should be at least 3 GB.
The tablespace must be created before installing CSA and then must be configured immediately after CSA is installed.
Refer to 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 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 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 CSA database user is needed when installing 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 CSA, do the following:
Create a new database for CSA (for example, csadb
).
Caution:
CSA database only supports 'Case Insensitive' Collation.
The CSA database collation and the tempDB collation in SQL server must be the same.
csadbuser
) with the following roles:
For example, run the following commands to create the csadbuser
user with the specified roles:
Microsoft SQL Server 2012
USE csadb;
-- or connect to csadb in another wayCREATE LOGIN csadbuser WITH PASSWORD = '<csadbuser_password>';
CREATE USER csadbuser FOR LOGIN csadbuser;
ALTER ROLE db_datareader ADD MEMBER csadbuser;
ALTER ROLE db_datawriter ADD MEMBER csadbuser;
ALTER ROLE db_owner ADD MEMBER csadbuser;
You must provide this database name, database username, and user's password when prompted for the CSA database information during the installation of CSA.
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of 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 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 CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
USE csadb;
-- or connect to csadb in another wayCREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser;
Optionally, create a reporting
database user for CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
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 CSA.
An Identity Management component database user is needed when installing CSA.
Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Connect to the new database created for the Identity Management component (for example, csaidmdb
).
Caution:
IdM database only supports 'Case Insensitive' Collation.
The IdM database collation and the tempDB collation in SQL server must be the same.
Create a new user for the Identity Management component database (for example, csaidmdbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Identity Management component database (for example, csaidmdbuser
).
For example, run the following commands to create the csaidmdbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaidmdb;
-- or connect to csaidmdb in another way CREATE LOGIN csaidmdbuser WITH PASSWORD = '<csaidmdbuser_password>';
CREATE USER csaidmdbuser FOR LOGIN csaidmdbuser;
ALTER ROLE db_datareader ADD MEMBER csaidmdbuser;
ALTER ROLE db_datawriter ADD MEMBER csaidmdbuser;
ALTER ROLE db_owner ADD MEMBER csaidmdbuser;
You must provide this database name, database username and, user's password when prompted for the Identity Management component database information during the installation of CSA.
Create a new database for the Identity Management component. Grant the Identity Management component database user (if you configured this user) or CSA database user all rights to this database.
Caution: The database name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, to create a database named csaidmdb
granting access to the Identity Management component database user named csaidmdbuser
, from the psql prompt, enter the following commands:
create database csaidmdb with owner=csaidmdbuser connection limit=-1;
grant all on database csaidmdb to csaidmdbuser;
If you did NOT create an Identity Management component database user named csaidmdbuser
, create a database named csaidmdb
and grant access to this database to the CSA database user named csadbuser
. From the psql prompt, enter the following commands:
create database csaidmdb with owner=csadbuser connection limit=-1;
grant all on database csaidmdb to csadbuser;
You must provide this database name, database username and, user's password when prompted for the Identity Management component database information during the installation of CSA.
An Operations Orchestration database user, used by the embedded Operations Orchestration, is needed when installing 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 an Operations Orchestration database user for CSA, do the following:
Work with the database administrator to create a database that is used by the embedded Operations Orchestration. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
You must provide the service (global database) name of this database when prompted for the Operations Orchestration database information during the installation of CSA.
Create a new database for Operations Orchestration (for example, csaoodb).
As of the release date of the CSA software (listed at the top of this guide), the mandatory database options for the Microsoft SQL Server for Operations Orchestration are:
Caution: You should verify the latest mandatory options and follow the instructions in the HPE Operations Orchestration Database Guide when creating the Operations Orchestration database.
Create a new user for the Operations Orchestration database (for example, csaoodbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Operations Orchestration database (for example, csaoodbuser
).
For example, run the following commands to create the csaoodbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaoodb;
CREATE LOGIN csaoodbuser WITH PASSWORD = '<csaoodbuser_password>';
CREATE USER csaoodbuser FOR LOGIN csaoodbuser;
ALTER ROLE db_datareader ADD MEMBER csaoodbuser;
ALTER ROLE db_datawriter ADD MEMBER csaoodbuser;
ALTER ROLE db_owner ADD MEMBER csaoodbuser;
Create a new database for Operations Orchestration. Grant the Operations Orchestration database user all rights to this database. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
Caution: The database name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, if you create
a database named csaoodb
and
an Operations Orchestration
user named csaoodbuser
, from the psql prompt, enter
the following commands:
create database csaoodb with owner=csaoodbuser connection limit=-1;
grant all on database csaoodb to csaoodbuser;
You must provide this database name, database username and, user's password when prompted for the Operations Orchestration database information during the installation of CSA.
You must provide this database name, database username, and user's password when prompted for the Operations Orchestration database information during the installation of 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 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 CSA is installed.
Refer to 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 CSA is installed. Work with the database administrator to complete the following tasks (or refer to the manufacturer’s documentation for more information).
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 CSA database user (for example, csadbuser
). The 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;
This is the user to whom you will grant access to the CSA database when you create this database.
Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, run the following commands to create the csaoodbuser user:
Create user csaoodbuser identified by csaoodbuser default tablespace system temporary tablespace temp quota unlimited on system account unlock;
Grant CONNECT to csaoodbuser;
Grant CREATE VIEW, CREATE SEQUENCE, CREATE TABLE, CREATE PROCEDURE to csaoodbuser;
Commit;
You must provide this database username and password when prompted for the Operations Orchestration database information during the installation of CSA.
Create an Operations Orchestration database user (for example, csaoodbuser
). The Operations Orchestration database user, used by the embedded Operations Orchestration, is required. This user should inherit rights from parent roles and have superuser privileges.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role csaoodbuser login password '<csaoodbuser_password>' superuser inherit;
This is the user to whom you will grant access to the Operations Orchestration database when you create this database.
Optionally, create an Identity Management component database user (for example, csaidmdbuser
). This user should inherit rights from parent roles and be a superuser.
Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
From the psql prompt, enter the following:
create role csaidmdbuser login password '<csaidmdbuser_password>' superuser inherit;
This is the user to whom you will grant access to the Identity Management component database when you create this database. If you do not create this user, you can use the CSA database user (for example, csadbuser
) instead.
A reporting database role and read-only user are needed only if you want to use the reporting capabilities of 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 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 CSA database with no roles.
For example, run the following commands to create the CSAReportingDBUser read-only user:
USE csadb;
-- or connect to csadb in another wayCREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser;
Optionally, create a reporting
database user for CSA
(for example, CSAReportingDBUser
).
A reporting database user is needed only if you want to use the reporting capabilities of
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 CSA.
Create a new database for CSA. Grant the 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
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;
You must provide this database name, database username and, user's password when prompted for the CSA database information during the installation of CSA.
Work with the database administrator to create a database that is used by the embedded Operations Orchestration. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
You must provide the service (global database) name of this database when prompted for the Operations Orchestration database information during the installation of CSA.
Create a new database for Operations Orchestration (for example, csaoodb).
As of the release date of the CSA software (listed at the top of this guide), the mandatory database options for the Microsoft SQL Server for Operations Orchestration are:
Caution: You should verify the latest mandatory options and follow the instructions in the HPE Operations Orchestration Database Guide when creating the Operations Orchestration database.
Create a new user for the Operations Orchestration database (for example, csaoodbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Operations Orchestration database (for example, csaoodbuser
).
For example, run the following commands to create the csaoodbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaoodb;
CREATE LOGIN csaoodbuser WITH PASSWORD = '<csaoodbuser_password>';
CREATE USER csaoodbuser FOR LOGIN csaoodbuser;
ALTER ROLE db_datareader ADD MEMBER csaoodbuser;
ALTER ROLE db_datawriter ADD MEMBER csaoodbuser;
ALTER ROLE db_owner ADD MEMBER csaoodbuser;
Create a new database for Operations Orchestration. Grant the Operations Orchestration database user all rights to this database. Refer to the HPE Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.
Caution: The database name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, if you create
a database named csaoodb
and
an Operations Orchestration
user named csaoodbuser
, from the psql prompt, enter
the following commands:
create database csaoodb with owner=csaoodbuser connection limit=-1;
grant all on database csaoodb to csaoodbuser;
You must provide this database name, database username and, user's password when prompted for the Operations Orchestration database information during the installation of CSA.
An Identity Management component database user is needed when installing CSA.
Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
Connect to the new database created for the Identity Management component (for example, csaidmdb
).
Caution:
IdM database only supports 'Case Insensitive' Collation.
The IdM database collation and the tempDB collation in SQL server must be the same.
Create a new user for the Identity Management component database (for example, csaidmdbuser
) with the following roles. You can use the existing database login you created for the CSA database (for example, csadbuser
) or you may create a new database login for the Identity Management component database (for example, csaidmdbuser
).
For example, run the following commands to create the csaidmdbuser
login and user with the specified roles:
Microsoft SQL Server 2012
USE csaidmdb;
-- or connect to csaidmdb in another way CREATE LOGIN csaidmdbuser WITH PASSWORD = '<csaidmdbuser_password>';
CREATE USER csaidmdbuser FOR LOGIN csaidmdbuser;
ALTER ROLE db_datareader ADD MEMBER csaidmdbuser;
ALTER ROLE db_datawriter ADD MEMBER csaidmdbuser;
ALTER ROLE db_owner ADD MEMBER csaidmdbuser;
You must provide this database name, database username and, user's password when prompted for the Identity Management component database information during the installation of CSA.
Create a new database for the Identity Management component. Grant the Identity Management component database user (if you configured this user) or CSA database user all rights to this database.
Caution: The database name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.
For example, to create a database named csaidmdb
granting access to the Identity Management component database user named csaidmdbuser
, from the psql prompt, enter the following commands:
create database csaidmdb with owner=csaidmdbuser connection limit=-1;
grant all on database csaidmdb to csaidmdbuser;
If you did NOT create an Identity Management component database user named csaidmdbuser
, create a database named csaidmdb
and grant access to this database to the CSA database user named csadbuser
. From the psql prompt, enter the following commands:
create database csaidmdb with owner=csadbuser connection limit=-1;
grant all on database csaidmdb to csadbuser;
You must provide this database name, database username and, user's password when prompted for the Identity Management component database information during the installation of CSA.
Exit psql. From the psql prompt, enter the following:
\q
Install Operations Orchestration to the correct version and patch level. See Cloud Service Automation System and Software Support Matrix for version requirements, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).
If you are using an existing installation of Operations Orchestration, you should verify that the correct versions of patches and updates have been applied.
Caution:
If you are using an earlier version of Operations Orchestration:
YOU MUST UPGRADE HPE OPERATIONS ORCHESTRATION TO VERSION 10.21.0001 BEFORE INSTALLING CSA.
After upgrading to Operations Orchestration 10.21.0001, update it by following the instructions below.
Update Operations Orchestration version 10.21.0001 by installing hotfix HF_27629.
For your convenience, the hotfix is delivered with the CSA installation media. Locate the readme file for this hotfix and follow the instructions on how to upgrade Operations Orchestration.
Alternatively, you can download the hotfix from https://patch-central.corp.hp.com/crypt-web/protected/viewContent.do?patchId=HF_27629.
The CSA Installer will require the Operations Orchestration administrator credentials where administrator for this purpose is any user that has the ADMINISTRATOR and SYSTEM_ADMIN roles.
If you want to use HPE Single Sign-On and the user name for Operations Orchestration administrator is different than "admin", you may want to setup an account with user name as "admin" and assign ADMINISTRATOR and SYSTEM_ADMIN roles. This will enable you to click through from CSA to OO without an extra login step.
You can review, add, or manage users and their roles in Operations Orchestration through the Operations Orchestration Central; click System Configuration, Security, Internal Users. Ensure that "Enable authentication" option is turned on (once the administrative user is defined).
Export Operations Orchestration's certificate from Operations Orchestration's truststore and, if Operations Orchestration and CSA are not installed on the same system, copy the certificate to the CSA system. This certificate will be imported into CSA's truststore by the CSA installer. TLS must be configured between CSA and Operations Orchestration.
For example, do the following:
Run the following command:
Windows
.\java\bin\keytool -export
-alias tomcat -file C:\oo.crt
-keystore .\Central\var\security\key.store -storepass changeit
Linux
./java/bin/keytool -export
-alias tomcat
-file /tmp/oo.crt
-keystore ./Central/var/security/key.store -storepass changeit
where C:\oo.crt
and /tmp/oo.crt
are examples of filenames and locations used to store the exported root certificate (you can choose a different filename and location).
oo.crt
from the Operations Orchestration system to the system running CSA.
Note: Installation log files are written to the
%CSA_HOME%\_CSA_4_60_0_installation\Logs\
directory.
To install Cloud Service Automation (CSA), complete the following steps.
Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
Unzip the setup.zip
file. Go to the directory to which the files have been extracted and run the setup.bat
installation file. A command window (which will display until the script has completed) and a dialog that shows the progress of installation preparation are displayed. Do not close either window. The installation preparation progress dialog will disappear when installation preparation has completed.
Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
Unzip the setup.zip
file. Go to the directory to which the files have been extracted and run the setup.bat
installation file. A command window (which will display until the script has completed) and a dialog that shows the progress of installation preparation are displayed. Do not close either window. The installation preparation progress dialog will disappear when installation preparation has completed.
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 CSA
is configured in the registry. However, CSA
has been uninstalled (the CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing CSA. Refer to the
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
CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select CSA and Marketplace Portal and click Next.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you only want to install the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install both the CSA and Marketplace Portal are different from the tasks to install only the Marketplace Portal.
Choose a location in which to install 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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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.
Select the JRE that will be used by 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 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 CSA. If you want to use the OpenJDK JRE, select 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 CSA, select Oracle JRE, choose 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 CSA, click Choose and select the location in which you installed the JRE that will be used by 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.
Install CSA database components onto the database instance to create the CSA database schema, if it does not exist.
Click Yes to install CSA database components and create the CSA database schema. When you select this option, the CSA service automatically starts when you exit the installer.
Click No if you are using an existing CSA database schema that was created as part of a prior successful installation of CSA version 4.60. When you select this option, you cannot use the installer to deploy sample content and the 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 CSA service.
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 CSA system). For a list of supported JDBC driver versions, refer to the Cloud Service Automation System and Software Support Matrix, available on the
HP Software Support Web site at
http://h20230.www2.hp.com/selfsolve/manuals/
(this site requires that you register with HP Passport).. Click Choose to select the directory.
Define the database instance on which the 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 service name |
The service or global database name of the database instance on which the CSA database schema will be installed (for example, csadb). If you are creating a new CSA database schema, this is the service name of the database instance on which the CSA database components will be installed. If you are using an existing CSA database schema that was created as part of a prior successful installation of HPE CSA version 4.60, this is the service name of the database instance on which the CSA database schema exists. |
Database Username | The username of the database user you configured for CSA in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, csadbuser). |
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 CSA in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, CSAReportingDBUser). |
CSA Reporting Database Password | The password for the CSA reporting database user. |
Enter the database information for the database used by the Identity Management component and click Next. The database used by the Identity Management component must be the same type of database used by CSA (Microsoft SQL ServerOraclePostgreSQL).
Field Name | Description |
---|---|
MSSQLOraclePostgreSQL Database Host | The hostname or IP address of the server where the Identity Management component database is located. |
MSSQLOraclePostgreSQL Database Port | The Identity Management component database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
HPEIDM Database Name Oracle Service Name |
The service or global database name of the database instance used by the Identity Management component (for example, csaidmdb). |
HPEIDM Database Username | The username of the database user you configured for the Identity Management component database in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, csaidmdbuser or csadbuser). |
HPEIDM Database Password | The password for the Identity Management component database user. |
From the hostname configuration screen, enter the fully-qualified domain name of the system on which you are installing CSA. This name is used to generate the self-signed certificate and configure CSA, the Marketplace Portal, and the Identity Management component.
The self-signed certificate is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after 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 CSA and manually reconfigure CSA and the Marketplace Portal to use this certificate. For more information, refer to the Cloud Service Automation Configuration Guide.
By default, Single Sign-On (SSO) is included with CSA and is enabled. The SSO that is included with CSA can only be used when launching an application, such as Operations Orchestration or HPE IT Business Analytics, from the Cloud Service Management Console. Refer to the Cloud Service Automation Configuration Guide and SSO documentation for more information on integrating SSO with an application.
Applications launched from the Cloud Service Management Console and Marketplace Portal with which you want to use SSO must be installed on systems that belong to this domain.
Note: You must enter the full domain name of the server. For example, if you are installing 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.
You can enable SSO in the Cloud Service Management Console and the Marketplace Portal. If enabled, enter the domain name of the network to which the server on which you are installing CSA belongs and click Next.
If you do not want to use SSO, you can disable it.
Note: You MUST disable Single Sign-On if you are installing CSA in a FIPS 140-2 compliant environment.
Specify if you want to install the embedded (new) Operations Orchestration instance with CSA or if you are integrating with an external (existing) instance of Operations Orchestration.
Select Use external OO and click Next1 and select Enter to integrate with an external (existing) instance of Operations Orchestration.Select Install embedded OO and click Next2 and select Enter to install the embedded Operations Orchestration.
If you are using unsupported version of Operations Orchestration, you will get a warning message. HPE recommends that you stop the current installation, check the System and Software Support Matrix document, install or upgrade to a supported Operations Orchestration version, then restart the CSA installation.
If you continue with the installation, you may get provisioning errors. Using an unsupported version of Operations Orchestration may also result in a limited amount of demo content that users can select for installation.
(Not Recommended) If you have understood the warning, click Next to continue with the installation.
Next, select the CSA content you would like to import. CSA and Codar are the available content options. If neither option is selected, the install will not proceed.
Define the Operations Orchestration instance with which CSA is to be integrated. Enter the following information and click Next.
Field Name | Description |
---|---|
HPE OO Hostname | The fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate Operations Orchestration's certificate. The hostname is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured). |
HPE OO Port | The port number used to communicate with Operations Orchestration, such as 8443. The port number is used to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration. By default, Operations Orchestration uses this port and port 8080. Applications running on the system on which Operations Orchestration is installed should not be using these ports. |
HPE OO User |
The
name of the user who logs in to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, this is the |
HPE OO Password | The
password used by the HP OO user to log in to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, use the password cloud . |
HPE OO Certificate File | The filename and location of Operations Orchestration's certificate from Operations Orchestration's truststore on the CSA system. If you have not already done so, export Operations Orchestration's certificate and copy it to the CSA system (see the Install Operations Orchestration section in this guide for more information). |
This information is used to set the Operations Orchestration properties in the csa.properties
file and import Operations Orchestration's certificate into CSA's truststore. Refer to the Cloud Service Automation Configuration Guide for more information about these properties.
Choose a location in which to install the embedded Operations Orchestration and click Next.
Configure an internal Operations Orchestration user and click Next. This user is used for provisioning topology designs.
Field Name | Description |
---|---|
HPE OO User Name | The name of the user used for provisioning topology designs. This user is given the ADMINISTRATOR and SYSTEM_ADMIN roles. The recommended username is admin. |
HPE OO User Password | The password used by Operations Orchestration for the user who provisions topology designs. The recommended password is cloud. |
HPE OO Port | The embedded Operations Orchestration port number, such as 8445, used to access Operations Orchestration Central. By default, Operations Orchestration uses this port and port 8080. The embedded Operations Orchestration should not use the same port as other applications running on the system. |
Enter the database information for the database used by the embedded Operations Orchestration and click Next. The database used by the embedded Operations Orchestration must be the same type of database used by CSA (Microsoft SQL ServerOraclePostgreSQL).
Field Name | Description |
---|---|
MSSQLOraclePostgreSQL Database Host | The hostname or IP address of the server where the embedded Operations Orchestration database is located. |
MSSQLOraclePostgreSQL Database Port | The embedded Operations Orchestration database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
HPE OO Database NameOracle Operations Orchestration service name |
The service or global database name of the database instance used by the embedded Operations Orchestration (for example, csaoodb). |
HPE OO Database Username | The username of the database user you configured for the Operations Orchestration database in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, csaoodbuser). |
HPE OO Database Password | The password for the Operations Orchestration database user. |
By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with CSA. You can choose to deploy this content during installation (making the sample service designs available in the Designs area of the Cloud Service Management Console) or deploy the content at a later time (refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information).
To deploy the sample content during the CSA installation process, select Install additional provider integration service designs, components and content and click Next.
To deploy the sample content at a later time, select Skip content installation and click Next.
If you choose to skip content installation, you can install the content at a later time by running the Cloud Content Capsule Installer. Refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information.
Note: If you chose not to install the database components, this dialog will not display.
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 CSA, Elasticsearch 1.6.1, HPE Search Service, and Marketplace Portal, and Operations Orchestration Central services have started by navigating to Start > Administrative Tools > Services. It can take up to five minutes for the CSA to start. If one or more services have not started, right-click on the service and select Start.
The installer creates the CSA and Marketplace Portal services. If you opted to install the CSA database components, the installer starts these services. The CSA 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, and the Operations Orchestration Central service must be running in order to access Operations Orchestration Central.
To start, stop, and restart the CSA, Elasticsearch 1.6.1, HPE Search Service, and Marketplace Portal, and Operations Orchestration Central services, navigate to Start > Administrative Tools > Services, right-click on a service, and select the desired action.
Note: Installation log files are written to the
$CSA_HOME/_CSA_4_60_0_installation/Logs/
directory and are named csa_*.txt
.
To install CSA (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 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 CSA as another user,
you may not be able to run 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 CSA is configured in the registry. However, CSA has been uninstalled (the CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing CSA. Refer to the Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the $HOME/.com.zerog.registry.xml
file (for example, /home/csauser/.com.zerog.registry.xml
), make a backup copy, delete all CSA entries from the .com.zerog.registry.xml
file, and restart the installer.
Select CSA and Marketplace Portal and click Enter.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you only want to install the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install both the CSA and Marketplace Portal are different from the tasks to install only the Marketplace Portal.
Enter a location in which to install 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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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.
Select the JRE that will be used by 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 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 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 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 CSA, type in the location in which you installed the JRE that will be used by CSA and select Enter.
Install CSA database components onto the database instance to create the CSA database schema, if it does not already exist.
Type yes to install CSA database components and create the CSA database schema. When you select this option, the CSA process automatically starts when you exit the installer.
Type no if you are using an existing HP CSA database schema that was created as part of a prior successful installation of CSA version 4.60. When you select this option, you cannot use the installer to deploy sample content and the CSA process does not start when you exit the installer. Refer to the end of this section for information on how to start and stop the CSA service.
Define the database instance on which the 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 CSA system). For a list of supported JDBC driver versions, refer to the Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)..
[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 Oracle service namedatabase name. This is the service or global database name of the database instance on which the
CSA
database schema will be installed. If you are creating a new
CSA
database schema, this is the service name of the database instance on which the
CSA database components
will be installed). If you are using an existing
CSA database schema
that was created as part of a prior successful installation of
CSA version
HP 4.60,
this is the service name of the database instance on which
the 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 in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide.
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
CSA in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide.
If you followed the examples in this document, enter CSAReportingDBUser
.
Provide the database instance used by the Identity Management component. Enter the following database information (select Enter after each entry).
[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 Oracle servicedatabase name. This is the service or global database name of the database instance used by the Identity Management component.
If you followed the examples in this document, enter csaidmdb
.
Enter the Identity Management component database user name. This is the user name of the database user you configured for the Identity Management component database
in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide.
If you followed the examples in this document, enter csaidmdbuser
or csadbuser
.
Enter the CSA server hostname. This is the fully-qualified domain name of the system on which you are installing CSA. This name is used to generate the self-signed certificate and configure CSA, the Marketplace Portal, and the Identity Management component.
The self-signed certificate is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after 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 CSA and manually reconfigure CSA and the Marketplace Portal to use this certificate. For more information, refer to the Cloud Service Automation Configuration Guide.
By default, Single Sign-On (SSO) is included with CSA and is enabled. The SSO that is included with CSA can only be used when launching an application, such as Operations Orchestration or HPE IT Business Analytics, from the Cloud Service Management Console. Refer to the Cloud Service Automation Configuration Guide and SSO documentation for more information on integrating SSO with an application.
If you do not want to use SSO, you can disable it. Type 2 and select Enter.
To enable SSO, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing CSA) and select Enter.
Note: You must enter the full domain name of the server. For example, if you are installing 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 and Marketplace Portal with which you want to use SSO must be installed on systems that belong to this domain.
Specify if you want to install the embedded (new) Operations Orchestration instance with CSA or if you are integrating with an external (existing) instance of Operations Orchestration.
Select Use external OO and click Next1 and select Enter to integrate with an external (existing) instance of Operations Orchestration.Select Install embedded OO and click Next2 and select Enter to install the embedded Operations Orchestration.
If you are using unsupported version of Operations Orchestration, you will get a warning message. HPE recommends that you stop the current installation, check the System and Software Support Matrix document, install or upgrade to a supported Operations Orchestration version, then restart the CSA installation.
If you continue with the installation, you may get provisioning errors. Using an unsupported version of Operations Orchestration may also result in a limited amount of demo content that users can select for installation.
(Not Recommended) If you have understood the warning, click Next to continue with the installation.
Next, select the CSA content you would like to import. CSA and Codar are the available content options. If neither option is selected, the install will not proceed.
Define the Operations Orchestration instance with which CSA is to be integrated. Enter the following information (select Enter after each entry).
Enter the HP OO hostname. This is the fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate Operations Orchestration's certificate. The hostname is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured).
Enter the HP OO user. This is the
name of the user who logs in to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, this is the admin
user.
cloud
.
This information is used to set the Operations Orchestration properties in the csa.properties
file and import Operations Orchestration's certificate into CSA's truststore. Refer to the Cloud Service Automation Configuration Guide for more information about these properties.
Enter a location in which to install the embedded Operations Orchestration.
Enter the database information for the database used by the embedded Operations Orchestration (select Enter after each entry). The database used by the embedded Operations Orchestration must be the same type of database used by CSA (Microsoft SQL ServerOraclePostgreSQL).
csaoodb
.csaoodbuser
.Configure an internal Operations Orchestration user (select Enter after each entry). This user is used for provisioning topology designs.
By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with CSA. You can choose to deploy this content during installation (making the sample service designs available in the Designs area of the Cloud Service Management Console) or deploy the content at a later time (refer to the Cloud Service Automation Content Pack User's Guide for more information).
To deploy the sample content during the CSA installation process, type 1 (Install additional provider integration service designs, components and content) and select Enter.
To deploy the sample content at a later time, type 2 (Skip content installation) and select Enter.
If you choose to skip content installation, you can install the content at a later time by running the Cloud Content Capsule Installer. Refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information.
Note: If you chose not to install the database components, this selection will not display.
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.
If you selected to use the OpenJDK JRE with CSA and installed CSA on a system running a headless Ubuntu Linux version 14, install the "Standard Java or Java-compatible Runtime" package. Enter the following:
apt-get install default-jre
Define the CSA_HOME and JAVA_HOME environment variables for the csauser user. Set CSA_HOME to the location where
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
<csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed.Source the startup file in
which you set the CSA_HOME and JAVA_HOME
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 CSA service and Marketplace Portal service to start and stop the CSA and Marketplace Portal processes.
Go to the directory in which 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 CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
As csauser, restart the Operations Orchestration Central service. Enter the following:
/usr/local/hp/csa/OO/central/bin/central stop
/usr/local/hp/csa/OO/central/bin/central start
The CSA service must
be running in order to access the
Cloud Service Management Console.
You can start this service by running the command service csa start
.
You can restart this service by running the command service csa restart
.
You can stop the service by running the command service csa stop
.
You can check the status of the service by running the command service csa status
.
The Marketplace Portal service must be running in order to access the
Marketplace Portal.
You can start this service by running the command service mpp start
.
You can restart this service by running the command service mpp restart
.
You can stop the service by running the command service mpp stop
.
You can check the status of the service by running the command service mpp status
.
The Operations Orchestration Central service must be running in order to access Operations Orchestration Central. you can start this service by running the command /usr/local/hp/csa/OO/central/bin/central start
. you can stop this service by running the command /usr/local/hp/csa/OO/central/bin/central stop
.
Note: Installation log files are written to the
%CSA_HOME%\_CSA_4_60_0_installation\Logs\
directory.
To install a remote instance of the Marketplace Portal, complete the following steps.
Unzip the setup.zip
file. Go to the directory to which the files have been extracted and run the setup.bat
installation file. A command window (which will display until the script has completed) and a dialog that shows the progress of installation preparation are displayed. Do not close either window. The installation preparation progress dialog will disappear when installation preparation has completed.
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 CSA
is configured in the registry. However, CSA
has been uninstalled (the CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing CSA. Refer to the
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
CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select Marketplace Portal and click Next.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you want to install CSA and the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install only the Marketplace Portal are different from the tasks to install both CSA and the Marketplace Portal.
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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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 CSA is installed and the location of the CSA certificate that was copied to the local system. Enter the following information and click Next.
Field Name | Description |
---|---|
CSA Host | The fully-qualified domain name of the system on which CSA is installed. |
CSA Port | The port number used to communicate with CSA. |
CSA Certificate | The name and location of the CSA certificate file that was copied from the 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 Next.
Review your selections 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
$CSA_HOME/_CSA_4_60_0_installation/Logs/
directory and are named csa_*.txt
.
To install HP Cloud Service Automation (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 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 CSA as another user,
you may not be able to run 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 CSA
is configured in the registry. However, CSA
has been uninstalled (the CSA installation
directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before
installing CSA. Refer to the
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
CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select Marketplace Portal and select Enter.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you want to install CSA and the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install only the Marketplace Portal are different from the tasks to install both CSA and the Marketplace Portal.
Enter a location in which to install 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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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 CSA is installed and the location of the CSA certificate that was copied to the local system. Enter the following information and select Enter.
Field Name | Description |
---|---|
CSA Host | The fully-qualified domain name of the system on which CSA is installed. |
CSA Port | The port number used to communicate with CSA. |
CSA Certificate | The name and location of the CSA certificate file that was copied from the 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 running the command service mpp start
.
You can restart this service by running the command service mpp restart
.
You can stop the service by running the command service mpp stop
.
You can check the status of the service by running the command service mpp status
.
Configure the Oracle tablespace you created for CSA only if you are installing CSA for the first time and there is no data in the CSA_DOCUMENT table. The tablespace must have been created before CSA is installed and then must be configured immediately after CSA 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 CSA is installed.
Configure the Microsoft SQL server filegroup you created for CSA only if you are installing CSA for the first time and there is no data in the CSA_DOCUMENT table. The filegroup must have been created before CSA is installed and then must be configured immediately after CSA 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
CSA 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 CSA when you installed CSA and %CSA_HOME%
$CSA_HOME
is the directory in which
CSA is installed.
Restart the csa and mpp services by running the following commands:
service csa restart
service mpp restart
Update and redeploy the oo10-sm-cp-1.0.3.jar
base content pack. If you deployed an earlier version of the Service Manager base content pack, you must do the following (if this is a fresh installation of Operations Orchestration and you did not deploy an earlier version of the Service Manager base content pack, you do not have to complete these steps):
Stop the Operations Orchestration services:
Windows:
On the server that hosts Operations Orchestration, navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration Central service and select Stop.
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration RAS service and select Stop.
Linux:
On the server that hosts Operations Orchestration, run the following command: <HPOOinstallation>/central/bin/central stop
For example, /usr/local/hpe/csa/OO/central/bin/central stop
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), run the following command: <HPOOinstallation>/ras/bin/ras stop
.
For example, /usr/local/hpe/csa/OO/ras/bin/ras stop
Clear the Operations Orchestration Central cache by deleting the following folder:
<HPOOinstallation>\central\var\cache
For example,
Windows: C:\Program Files\HPE\HP Operations Orchestration\central\var\cache
Linux: /usr/local/hpe/csa/oo/central/var/cache
If RAS is installed, clear the RAS artifact cache by deleting the following folder (on all RAS systems, including localhost):
<HPOOinstallation>\ras\var\cache
For example,
Windows: C:\Program Files\HPE\HP Operations Orchestration\ras\var\cache
Linux: /usr/local/hpe/csa/oo/ras/var/cache
Run the following SQL command against the Operations Orchestration database:
DELETE from OO_ARTIFACTS where NAME = 'org/apache/ws/security/wss4j/1.5.7/wss4j-1.5.7.pom' or NAME = 'org/apache/ws/security/wss4j/1.5.7/wss4j-1.5.7.jar'
Start the Operations Orchestration services:
Windows:
On the server that hosts Operations Orchestration, navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration Central service and select Start.
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), navigate to Start > Administrative Tools > Services.
Right-click on the Operations Orchestration RAS service and select Start.
Linux:
On the server that hosts Operations Orchestration, run the following command: <HPOOinstallation>/central/bin/central start
For example, /usr/local/hpe/csa/OO/central/bin/central start
If you installed the Remote Action Server (RAS), on all RAS systems (including localhost), run the following command: <HPOOinstallation>/ras/bin/ras start
.
For example, /usr/local/hpe/csa/OO/ras/bin/ras start
Redeploy the oo10-sm-cp-1.0.3.jar
base content pack:
Log in to Operations Orchestration Central and click Content Management.
Navigate to the CSA_HOME\oo\ooContentPack
directory and select oo10-sm-cp-1.0.3.jar.
Click Deploy.
The deployment may take a few minutes and the dialog will show a progress bar.
You have completed the initial installation and configuration of CSA and can begin familiarizing yourself with the capabilities of 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).
After 90 days, the Operations Orchestration license that is packaged with CSA will expire and prompt you to install a new license.
You must contact HPE Customer Support to acquire the new license. After HPE Customer Support provides you with a new Operations Orchestration license, download it onto your system.
To install your new Operations Orchestration license:
The Operations Orchestration license is now installed.
To complete the configuration of CSA, refer to the following documents:
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 secure connections, customizing the Cloud Service Management Console, configuring CSA to be compliant with FIPS 140-2, and performing other CSA customizations. The configuration guide also describes the process of how to import the sample Operations Orchestration flows included with CSA.
Configuring a CSA Cluster for High Availability Using an Apache Web Server: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using an Apache Web server.
Configuring a CSA Cluster for High Availability Using a Load Balancer: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using a load balancer.
Cloud Service Automation Content Pack User's Guide: This guide describes how to install and configure resource providers (such as Matrix OE, VMware vCenter, SiteScope, Universal CMDB, and Server Automation), how to deploy the sample Operations Orchestration flows included with CSA, how to deploy the sample resource offerings and service designs included with CSA that target these resource providers, and includes additional documentation on each of the out-of-the-box resource offerings and service designs. If you installed the additional provider integration service designs, components, and content during installation, the sample Operations Orchestration flows, resource offerings, and service designs have been deployed.
Cloud Service Automation Service Design Guide: The service design guide describes how to use CSA to create automated, on-demand cloud services. The guide covers key concepts and steps for 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 CSA application. Successful implementation of the application requires knowledge of the integrated products, as well as the CSA 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 Cloud Service Automation Concepts Guide.
You should review the Cloud Service Automation System and Software Support Matrix for version requirements.
Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)..
From the system on which CSA is installed, copy the CSA certificate to the system on which the remote instance of the Marketplace Portal will be installed.
On the system on which CSA is installed, the CSA certificate is located in %CSA_HOME%\jboss-as\standalone\configuration\jboss.crt$CSA_HOME/jboss-as/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 certificate as you will be asked for this information when you install the remote instance of the Marketplace Portal.
This file is needed for TLS verification which, by default, is enabled for the Marketplace Portal.
Configure a group and user for 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 CSA. See the Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)..
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
%CSA_HOME%\_CSA_4_60_0_installation\Logs\
directory.
To install Cloud Service Automation (CSA), complete the following steps.
Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
Unzip the setup.zip
file. Go to the directory to which the files have been extracted and run the setup.bat
installation file. A command window (which will display until the script has completed) and a dialog that shows the progress of installation preparation are displayed. Do not close either window. The installation preparation progress dialog will disappear when installation preparation has completed.
Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
Unzip the setup.zip
file. Go to the directory to which the files have been extracted and run the setup.bat
installation file. A command window (which will display until the script has completed) and a dialog that shows the progress of installation preparation are displayed. Do not close either window. The installation preparation progress dialog will disappear when installation preparation has completed.
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 CSA
is configured in the registry. However, CSA
has been uninstalled (the CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing CSA. Refer to the
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
CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select CSA and Marketplace Portal and click Next.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you only want to install the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install both the CSA and Marketplace Portal are different from the tasks to install only the Marketplace Portal.
Choose a location in which to install 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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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.
Select the JRE that will be used by 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 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 CSA. If you want to use the OpenJDK JRE, select 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 CSA, select Oracle JRE, choose 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 CSA, click Choose and select the location in which you installed the JRE that will be used by 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.
Install CSA database components onto the database instance to create the CSA database schema, if it does not exist.
Click Yes to install CSA database components and create the CSA database schema. When you select this option, the CSA service automatically starts when you exit the installer.
Click No if you are using an existing CSA database schema that was created as part of a prior successful installation of CSA version 4.60. When you select this option, you cannot use the installer to deploy sample content and the 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 CSA service.
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 CSA system). For a list of supported JDBC driver versions, refer to the Cloud Service Automation System and Software Support Matrix, available on the
HP Software Support Web site at
http://h20230.www2.hp.com/selfsolve/manuals/
(this site requires that you register with HP Passport).. Click Choose to select the directory.
Define the database instance on which the 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 service name |
The service or global database name of the database instance on which the CSA database schema will be installed (for example, csadb). If you are creating a new CSA database schema, this is the service name of the database instance on which the CSA database components will be installed. If you are using an existing CSA database schema that was created as part of a prior successful installation of HPE CSA version 4.60, this is the service name of the database instance on which the CSA database schema exists. |
Database Username | The username of the database user you configured for CSA in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, csadbuser). |
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 CSA in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, CSAReportingDBUser). |
CSA Reporting Database Password | The password for the CSA reporting database user. |
Enter the database information for the database used by the Identity Management component and click Next. The database used by the Identity Management component must be the same type of database used by CSA (Microsoft SQL ServerOraclePostgreSQL).
Field Name | Description |
---|---|
MSSQLOraclePostgreSQL Database Host | The hostname or IP address of the server where the Identity Management component database is located. |
MSSQLOraclePostgreSQL Database Port | The Identity Management component database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
HPEIDM Database Name Oracle Service Name |
The service or global database name of the database instance used by the Identity Management component (for example, csaidmdb). |
HPEIDM Database Username | The username of the database user you configured for the Identity Management component database in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, csaidmdbuser or csadbuser). |
HPEIDM Database Password | The password for the Identity Management component database user. |
From the hostname configuration screen, enter the fully-qualified domain name of the system on which you are installing CSA. This name is used to generate the self-signed certificate and configure CSA, the Marketplace Portal, and the Identity Management component.
The self-signed certificate is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after 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 CSA and manually reconfigure CSA and the Marketplace Portal to use this certificate. For more information, refer to the Cloud Service Automation Configuration Guide.
By default, Single Sign-On (SSO) is included with CSA and is enabled. The SSO that is included with CSA can only be used when launching an application, such as Operations Orchestration or HPE IT Business Analytics, from the Cloud Service Management Console. Refer to the Cloud Service Automation Configuration Guide and SSO documentation for more information on integrating SSO with an application.
Applications launched from the Cloud Service Management Console and Marketplace Portal with which you want to use SSO must be installed on systems that belong to this domain.
Note: You must enter the full domain name of the server. For example, if you are installing 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.
You can enable SSO in the Cloud Service Management Console and the Marketplace Portal. If enabled, enter the domain name of the network to which the server on which you are installing CSA belongs and click Next.
If you do not want to use SSO, you can disable it.
Note: You MUST disable Single Sign-On if you are installing CSA in a FIPS 140-2 compliant environment.
Specify if you want to install the embedded (new) Operations Orchestration instance with CSA or if you are integrating with an external (existing) instance of Operations Orchestration.
Select Use external OO and click Next1 and select Enter to integrate with an external (existing) instance of Operations Orchestration.Select Install embedded OO and click Next2 and select Enter to install the embedded Operations Orchestration.
If you are using unsupported version of Operations Orchestration, you will get a warning message. HPE recommends that you stop the current installation, check the System and Software Support Matrix document, install or upgrade to a supported Operations Orchestration version, then restart the CSA installation.
If you continue with the installation, you may get provisioning errors. Using an unsupported version of Operations Orchestration may also result in a limited amount of demo content that users can select for installation.
(Not Recommended) If you have understood the warning, click Next to continue with the installation.
Next, select the CSA content you would like to import. CSA and Codar are the available content options. If neither option is selected, the install will not proceed.
Define the Operations Orchestration instance with which CSA is to be integrated. Enter the following information and click Next.
Field Name | Description |
---|---|
HPE OO Hostname | The fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate Operations Orchestration's certificate. The hostname is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured). |
HPE OO Port | The port number used to communicate with Operations Orchestration, such as 8443. The port number is used to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration. By default, Operations Orchestration uses this port and port 8080. Applications running on the system on which Operations Orchestration is installed should not be using these ports. |
HPE OO User |
The
name of the user who logs in to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, this is the |
HPE OO Password | The
password used by the HP OO user to log in to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, use the password cloud . |
HPE OO Certificate File | The filename and location of Operations Orchestration's certificate from Operations Orchestration's truststore on the CSA system. If you have not already done so, export Operations Orchestration's certificate and copy it to the CSA system (see the Install Operations Orchestration section in this guide for more information). |
This information is used to set the Operations Orchestration properties in the csa.properties
file and import Operations Orchestration's certificate into CSA's truststore. Refer to the Cloud Service Automation Configuration Guide for more information about these properties.
Choose a location in which to install the embedded Operations Orchestration and click Next.
Configure an internal Operations Orchestration user and click Next. This user is used for provisioning topology designs.
Field Name | Description |
---|---|
HPE OO User Name | The name of the user used for provisioning topology designs. This user is given the ADMINISTRATOR and SYSTEM_ADMIN roles. The recommended username is admin. |
HPE OO User Password | The password used by Operations Orchestration for the user who provisions topology designs. The recommended password is cloud. |
HPE OO Port | The embedded Operations Orchestration port number, such as 8445, used to access Operations Orchestration Central. By default, Operations Orchestration uses this port and port 8080. The embedded Operations Orchestration should not use the same port as other applications running on the system. |
Enter the database information for the database used by the embedded Operations Orchestration and click Next. The database used by the embedded Operations Orchestration must be the same type of database used by CSA (Microsoft SQL ServerOraclePostgreSQL).
Field Name | Description |
---|---|
MSSQLOraclePostgreSQL Database Host | The hostname or IP address of the server where the embedded Operations Orchestration database is located. |
MSSQLOraclePostgreSQL Database Port | The embedded Operations Orchestration database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL). |
HPE OO Database NameOracle Operations Orchestration service name |
The service or global database name of the database instance used by the embedded Operations Orchestration (for example, csaoodb). |
HPE OO Database Username | The username of the database user you configured for the Operations Orchestration database in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide (for example, csaoodbuser). |
HPE OO Database Password | The password for the Operations Orchestration database user. |
By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with CSA. You can choose to deploy this content during installation (making the sample service designs available in the Designs area of the Cloud Service Management Console) or deploy the content at a later time (refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information).
To deploy the sample content during the CSA installation process, select Install additional provider integration service designs, components and content and click Next.
To deploy the sample content at a later time, select Skip content installation and click Next.
If you choose to skip content installation, you can install the content at a later time by running the Cloud Content Capsule Installer. Refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information.
Note: If you chose not to install the database components, this dialog will not display.
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 CSA, Elasticsearch 1.6.1, HPE Search Service, and Marketplace Portal, and Operations Orchestration Central services have started by navigating to Start > Administrative Tools > Services. It can take up to five minutes for the CSA to start. If one or more services have not started, right-click on the service and select Start.
The installer creates the CSA and Marketplace Portal services. If you opted to install the CSA database components, the installer starts these services. The CSA 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, and the Operations Orchestration Central service must be running in order to access Operations Orchestration Central.
To start, stop, and restart the CSA, Elasticsearch 1.6.1, HPE Search Service, and Marketplace Portal, and Operations Orchestration Central services, navigate to Start > Administrative Tools > Services, right-click on a service, and select the desired action.
Note: Installation log files are written to the
$CSA_HOME/_CSA_4_60_0_installation/Logs/
directory and are named csa_*.txt
.
To install CSA (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 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 CSA as another user,
you may not be able to run 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 CSA is configured in the registry. However, CSA has been uninstalled (the CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing CSA. Refer to the Cloud Service Automation Installation Guide for more information about deleting the registry entry.
exit the installer. Locate the $HOME/.com.zerog.registry.xml
file (for example, /home/csauser/.com.zerog.registry.xml
), make a backup copy, delete all CSA entries from the .com.zerog.registry.xml
file, and restart the installer.
Select CSA and Marketplace Portal and click Enter.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you only want to install the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install both the CSA and Marketplace Portal are different from the tasks to install only the Marketplace Portal.
Enter a location in which to install 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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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.
Select the JRE that will be used by 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 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 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 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 CSA, type in the location in which you installed the JRE that will be used by CSA and select Enter.
Install CSA database components onto the database instance to create the CSA database schema, if it does not already exist.
Type yes to install CSA database components and create the CSA database schema. When you select this option, the CSA process automatically starts when you exit the installer.
Type no if you are using an existing HP CSA database schema that was created as part of a prior successful installation of CSA version 4.60. When you select this option, you cannot use the installer to deploy sample content and the CSA process does not start when you exit the installer. Refer to the end of this section for information on how to start and stop the CSA service.
Define the database instance on which the 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 CSA system). For a list of supported JDBC driver versions, refer to the Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)..
[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 Oracle service namedatabase name. This is the service or global database name of the database instance on which the
CSA
database schema will be installed. If you are creating a new
CSA
database schema, this is the service name of the database instance on which the
CSA database components
will be installed). If you are using an existing
CSA database schema
that was created as part of a prior successful installation of
CSA version
HP 4.60,
this is the service name of the database instance on which
the 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 in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide.
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
CSA in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide.
If you followed the examples in this document, enter CSAReportingDBUser
.
Provide the database instance used by the Identity Management component. Enter the following database information (select Enter after each entry).
[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 Oracle servicedatabase name. This is the service or global database name of the database instance used by the Identity Management component.
If you followed the examples in this document, enter csaidmdb
.
Enter the Identity Management component database user name. This is the user name of the database user you configured for the Identity Management component database
in the Configure OracleMicrosoft SQL ServerPostgreSQL section of this guide.
If you followed the examples in this document, enter csaidmdbuser
or csadbuser
.
Enter the CSA server hostname. This is the fully-qualified domain name of the system on which you are installing CSA. This name is used to generate the self-signed certificate and configure CSA, the Marketplace Portal, and the Identity Management component.
The self-signed certificate is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after 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 CSA and manually reconfigure CSA and the Marketplace Portal to use this certificate. For more information, refer to the Cloud Service Automation Configuration Guide.
By default, Single Sign-On (SSO) is included with CSA and is enabled. The SSO that is included with CSA can only be used when launching an application, such as Operations Orchestration or HPE IT Business Analytics, from the Cloud Service Management Console. Refer to the Cloud Service Automation Configuration Guide and SSO documentation for more information on integrating SSO with an application.
If you do not want to use SSO, you can disable it. Type 2 and select Enter.
To enable SSO, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing CSA) and select Enter.
Note: You must enter the full domain name of the server. For example, if you are installing 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 and Marketplace Portal with which you want to use SSO must be installed on systems that belong to this domain.
Specify if you want to install the embedded (new) Operations Orchestration instance with CSA or if you are integrating with an external (existing) instance of Operations Orchestration.
Select Use external OO and click Next1 and select Enter to integrate with an external (existing) instance of Operations Orchestration.Select Install embedded OO and click Next2 and select Enter to install the embedded Operations Orchestration.
If you are using unsupported version of Operations Orchestration, you will get a warning message. HPE recommends that you stop the current installation, check the System and Software Support Matrix document, install or upgrade to a supported Operations Orchestration version, then restart the CSA installation.
If you continue with the installation, you may get provisioning errors. Using an unsupported version of Operations Orchestration may also result in a limited amount of demo content that users can select for installation.
(Not Recommended) If you have understood the warning, click Next to continue with the installation.
Next, select the CSA content you would like to import. CSA and Codar are the available content options. If neither option is selected, the install will not proceed.
Define the Operations Orchestration instance with which CSA is to be integrated. Enter the following information (select Enter after each entry).
Enter the HP OO hostname. This is the fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate Operations Orchestration's certificate. The hostname is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured).
Enter the HP OO user. This is the
name of the user who logs in to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, this is the admin
user.
cloud
.
This information is used to set the Operations Orchestration properties in the csa.properties
file and import Operations Orchestration's certificate into CSA's truststore. Refer to the Cloud Service Automation Configuration Guide for more information about these properties.
Enter a location in which to install the embedded Operations Orchestration.
Enter the database information for the database used by the embedded Operations Orchestration (select Enter after each entry). The database used by the embedded Operations Orchestration must be the same type of database used by CSA (Microsoft SQL ServerOraclePostgreSQL).
csaoodb
.csaoodbuser
.Configure an internal Operations Orchestration user (select Enter after each entry). This user is used for provisioning topology designs.
By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with CSA. You can choose to deploy this content during installation (making the sample service designs available in the Designs area of the Cloud Service Management Console) or deploy the content at a later time (refer to the Cloud Service Automation Content Pack User's Guide for more information).
To deploy the sample content during the CSA installation process, type 1 (Install additional provider integration service designs, components and content) and select Enter.
To deploy the sample content at a later time, type 2 (Skip content installation) and select Enter.
If you choose to skip content installation, you can install the content at a later time by running the Cloud Content Capsule Installer. Refer to the Cloud Service Automation Content Pack User's Guide or Cloud Service Automation Configuration Guide for more information.
Note: If you chose not to install the database components, this selection will not display.
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.
If you selected to use the OpenJDK JRE with CSA and installed CSA on a system running a headless Ubuntu Linux version 14, install the "Standard Java or Java-compatible Runtime" package. Enter the following:
apt-get install default-jre
Define the CSA_HOME and JAVA_HOME environment variables for the csauser user. Set CSA_HOME to the location where
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
<csa_jre>
$CSA_JRE_HOME
is the directory
in which the JRE that is used by CSA
is installed.Source the startup file in
which you set the CSA_HOME and JAVA_HOME
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 CSA service and Marketplace Portal service to start and stop the CSA and Marketplace Portal processes.
Go to the directory in which 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 CSA and Marketplace Portal services. Enter the following:
service csa start
service mpp start
As csauser, restart the Operations Orchestration Central service. Enter the following:
/usr/local/hp/csa/OO/central/bin/central stop
/usr/local/hp/csa/OO/central/bin/central start
The CSA service must
be running in order to access the
Cloud Service Management Console.
You can start this service by running the command service csa start
.
You can restart this service by running the command service csa restart
.
You can stop the service by running the command service csa stop
.
You can check the status of the service by running the command service csa status
.
The Marketplace Portal service must be running in order to access the
Marketplace Portal.
You can start this service by running the command service mpp start
.
You can restart this service by running the command service mpp restart
.
You can stop the service by running the command service mpp stop
.
You can check the status of the service by running the command service mpp status
.
The Operations Orchestration Central service must be running in order to access Operations Orchestration Central. you can start this service by running the command /usr/local/hp/csa/OO/central/bin/central start
. you can stop this service by running the command /usr/local/hp/csa/OO/central/bin/central stop
.
Note: Installation log files are written to the
%CSA_HOME%\_CSA_4_60_0_installation\Logs\
directory.
To install a remote instance of the Marketplace Portal, complete the following steps.
Unzip the setup.zip
file. Go to the directory to which the files have been extracted and run the setup.bat
installation file. A command window (which will display until the script has completed) and a dialog that shows the progress of installation preparation are displayed. Do not close either window. The installation preparation progress dialog will disappear when installation preparation has completed.
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 CSA
is configured in the registry. However, CSA
has been uninstalled (the CSA installation
directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before
installing CSA. Refer to the
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
CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select Marketplace Portal and click Next.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you want to install CSA and the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install only the Marketplace Portal are different from the tasks to install both CSA and the Marketplace Portal.
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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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 CSA is installed and the location of the CSA certificate that was copied to the local system. Enter the following information and click Next.
Field Name | Description |
---|---|
CSA Host | The fully-qualified domain name of the system on which CSA is installed. |
CSA Port | The port number used to communicate with CSA. |
CSA Certificate | The name and location of the CSA certificate file that was copied from the 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 Next.
Review your selections 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
$CSA_HOME/_CSA_4_60_0_installation/Logs/
directory and are named csa_*.txt
.
To install HP Cloud Service Automation (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 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 CSA as another user,
you may not be able to run 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 CSA
is configured in the registry. However, CSA
has been uninstalled (the CSA installation
directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before
installing CSA. Refer to the
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
CSA entries from
the .com.zerog.registry.xml
file, and
restart the installer.
Select Marketplace Portal and select Enter.
Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.
Selecting Marketplace Portal installs only the Marketplace Portal on the system.
If you want to install CSA and the Marketplace Portal, go to the top of this document and click Change to change the selections you made to create this document. The tasks to install only the Marketplace Portal are different from the tasks to install both CSA and the Marketplace Portal.
Enter a location in which to install 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 CSA is not empty, existing content in the directory may be overwritten or deleted when 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 CSA is installed and the location of the CSA certificate that was copied to the local system. Enter the following information and select Enter.
Field Name | Description |
---|---|
CSA Host | The fully-qualified domain name of the system on which CSA is installed. |
CSA Port | The port number used to communicate with CSA. |
CSA Certificate | The name and location of the CSA certificate file that was copied from the 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 running the command service mpp start
.
You can restart this service by running the command service mpp restart
.
You can stop the service by running the command service mpp stop
.
You can check the status of the service by running the command 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
CSA 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 CSA when you installed CSA and %CSA_HOME%
$CSA_HOME
is the directory in which
CSA 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\standalone\deployments\csa.war\WEB-INF\classes\csa.properties
$CSA_HOME/jboss-as/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 CSA.
To restart CSA:
On the server that hosts CSA, navigate to Control Panel > Administrative Tools > Services.
Right-click on the CSA service and select Restart.
Right-click on the HP Marketplace Portal service and select Restart.
To restart CSA, on the server that hosts 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 CSA is installed and the URL in the CSA_HOME\jboss-as\standalone\deployments\mpp.war\index.html
file (on the system on which 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
file (on the system on which the Marketplace Portal instance resides). By default, this is the sample organization that is installed with 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
CSA 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 CSA 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 CSA and can begin familiarizing yourself with the capabilities of 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).
After 90 days, the Operations Orchestration license that is packaged with CSA will expire and prompt you to install a new license.
You must contact HPE Customer Support to acquire the new license. After HPE Customer Support provides you with a new Operations Orchestration license, download it onto your system.
To install your new Operations Orchestration license:
The Operations Orchestration license is now installed.
To complete the configuration of CSA, refer to the following documents:
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 secure connections, customizing the Cloud Service Management Console, configuring CSA to be compliant with FIPS 140-2, and performing other CSA customizations. The configuration guide also describes the process of how to import the sample Operations Orchestration flows included with CSA.
Configuring a CSA Cluster for High Availability Using an Apache Web Server: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using an Apache Web server.
Configuring a CSA Cluster for High Availability Using a Load Balancer: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using a load balancer.
Cloud Service Automation Content Pack User's Guide: This guide describes how to install and configure resource providers (such as Matrix OE, VMware vCenter, SiteScope, Universal CMDB, and Server Automation), how to deploy the sample Operations Orchestration flows included with CSA, how to deploy the sample resource offerings and service designs included with CSA that target these resource providers, and includes additional documentation on each of the out-of-the-box resource offerings and service designs. If you installed the additional provider integration service designs, components, and content during installation, the sample Operations Orchestration flows, resource offerings, and service designs have been deployed.
Cloud Service Automation Service Design Guide: The service design guide describes how to use CSA to create automated, on-demand cloud services. The guide covers key concepts and steps for 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-2016 Hewlett-Packard Development Company, L.P.