HP Cloud Service Automation

For the Windows ® and Linux operating systems

Software Version: 4.10

Customized output from:

Installation Guide

Document Release Date: July 2014

Software Release Date: July 2014

HP logo

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2010-2014 Hewlett-Packard Development Company, L.P.

Trademark Notices

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.

 
 
 
 

Installation Guide

Installation Overview

The HP Cloud Service Automation Installation Guide for 4.10 is an interactive document that provides the information necessary to install the HP Cloud Service Automation (HP CSA) application, based on the information you provide.

Select from the options below and click View or Print to create a customized installation document. In this document, when available, detailed tasks are provided to complete the installation. In other cases, you may need to refer to the manufacturer's documentation to complete the steps.

Note: If a selection is disabled (it cannot be selected), it is not a supported selection based on the other options you have selected. If a disabled selection is selected, choose an enabled selection instead. In some cases, there may be only one selection that can be enabled in a section.

For general information about HP Cloud Service Automation, see the HP Cloud Service Automation Concepts Guide.

For information about the supported components and versions, see the HP Cloud Service Automation System and Software Support Matrix.

If you want to upgrade to HP CSA version 4.10, see the HP Cloud Service Automation Upgrade Guide.

Select an Operating System

Windows
Linux, Red Hat Enterprise
Linux, Ubuntu
Select the operating system of the server on which HP CSA is going to be installed.

Select a database

Oracle
Microsoft SQL Server
PostgreSQL
This is the database used for resource management by HP CSA. Other providers may also have database requirements and they should be met by following the manufacturer's recommendations.

Select the HP CSA components

Install the full HP CSA product
Install a remote instance of the Marketplace Portal
Select to install the full HP CSA product (includes the Cloud Service Management Console and Marketplace Portal) or only the Marketplace Portal.

Select the version of HP Operations Orchestration

HP Operations Orchestration 9.07
HP Operations Orchestration 10.10
Optional. Required. Select the version of HP Operations Orchestration with which HP CSA is going to be integrated.

An embedded HP Operations Orchestration is automatically installed with HP CSA. However, you may also install a standalone version of HP Operations Orchestration.


You must install a standalone version of HP Operations Orchestration. Select the version of HP Operations Orchestration with which you are integrating.


HP Operations Orchestration version 9.07 supports sequential designs only. HP Operations Orchestration version 10.10 supports both sequential designs and topology designs.

Select resource providers

HP Matrix Operating Environment infrastructure orchestration (infrastructure orchestration)
VMware vCenter
HP Network Automation
HP Server Automation
HP SiteScope for monitoring
HP Universal CMDB for configuration management
HP Cloud Services
HP Service Manager for external approvals
Resource providers are used to provision infrastructure for HP CSA, for monitoring, configuration management, application deployment, and other purposes.
HP Server Automation must be installed with HP Application Deployment Manager (ADM) for application deployment, with HP Database and Middleware Automation (DMA) for data center automation management, or with HP Server Automation Software Policies for application deployment.
For resource providers not listed here, follow the manufacturer's recommendations to install the product. Refer to the HP Cloud Service Automation Integration Guide for information on how to integrate these resource providers with HP CSA.

View or Print

Click view or print.

Version: 4.10
Document Release Date: July 2014
Software Release Date: July 2014

Check your selections

The following steps are customized according to your selections. Check that your selections are correct.

 

If any selections are not correct, click Change.

Installation Overview

Based on your selections on the previous page, perform the following steps. It is recommended that you perform each step in the following order:

  1. Configure a group and user.
  2. Install and initially configure Oracle.
  3. Install and initially configure Microsoft SQL Server.
  4. Install and configure PostgreSQL.
  5. Install HP Operations Orchestration.
  6. Install HP Cloud Service Automation.
  7. Secure the Marketplace Portal.
  8. Configure HP Operations Orchestration.
  9. Install and configure resource providers. If your resource provider is not listed below, follow the manufacturer's recommendations to install it. Refer to the HP Cloud Service Automation Integration Guide for information on how to integrate these providers with HP Cloud Service Automation.
  10. What's next?
  1. Copy the HP CSA SSL certificate to the remote system.
  2. Configure a group and user.
  3. Install HP Cloud Service Automation.
  4. What's next?

This guide provides information for installing the HP Cloud Service Automation application. Successful implementation of the application requires knowledge of the integrated products, as well as the HP Cloud Service Automation solution. Information in this guide augments information provided in the integrated products documentation but is not intended to replace that documentation. Primary product documentation contains the most up-to-date information. Cross references are provided to those documents where appropriate.

For information about how these parts fit together, see the HP Cloud Service Automation Concepts Guide.

You should review the HP Cloud Service Automation System and Software Support Matrix for version requirements.

Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure a Group and User for HP CSA

Configure a group and user for HP CSA:

  1. Log in to the system as the root user.
  2. Create a group called csagrp. Enter the following:

    groupadd csagrp

  3. Create a user called csauser and assign this user to the csagrp. Enter the following:

    useradd -g csagrp -m csauser (Ubuntu) or
    useradd -g csagrp -m csauser -s /bin/bash (RHEL)

  4. Assign a password to the csauser. Enter the following:

    passwd csauser

    When prompted, enter the password.

Install Oracle Database and JDBC Drivers

Install the Oracle Database (Required)

For a list of supported database versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Install the database according to the manufacturer’s documentation. Database installation is typically done in partnership with a database administrator.

Download Oracle JDBC Drivers (Required)

For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix (available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport)).

Download a supported version of the JDBC .jar file(s) and save them on the system on which HP CSA will be installed. Note the location where you save the file(s) as this information must be provided when HP CSA is installed.

Configure Oracle

These tasks must be completed before HP CSA is installed.

Create a Database Instance Used by HP CSA (Required)

If the database instance used by HP CSA has not already been created, work with the database administrator to create this database.

Configure Oracle Role and User for HP CSA (Required)

A database user is needed when installing HP CSA. Work with the database administrator to do the following (or refer to the manufacturer’s documentation for more information):

Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

  1. Create a schema for HP CSA by creating a database user.
  2. Create a role for this HP CSA database user and grant the following privileges to the role:
    • CREATE SESSION
    • CREATE TABLE
    • CREATE VIEW
    • CREATE SEQUENCE
    • CREATE ANY SYNONYM
  3. Grant the role to the HP CSA database user.
  4. Alter the HP CSA database user by setting this role as the user's default role.

You must provide this user's username and password when prompted for the CSA database user during the installation of HP CSA.

Configure a Reporting Role and Read-Only User for HP CSA (Required for Reporting)

A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):

Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

  1. Create a database user (for example, CSAReportingDBUser).
  2. Create a role for this HP CSA database user (for example, CSAReportingDBRole) and grant the following privilege to the role:
    • CREATE SESSION
  3. Grant the role to the HP CSA database user.
  4. Alter the HP CSA database user by setting this role as the user's default role.

For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:

Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;

A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.

Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

Add a reporting database user to the HP CSA database with no roles.

For example, run the following commands to create the CSAReportingDBUser read-only user:

CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;

Optionally, create a reporting database user for HP CSA (for example, CSAReportingDBUser). A reporting database user is needed only if you want to use the reporting capabilities of HP CSA. This user should have read-only rights.

Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

From the psql prompt, enter the following:

create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;

If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the installation of HP CSA.

Configure Oracle for Localization (Required for Localization)

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):

  • NLS_CHARACTERSET = AL32UTF8
  • NLS_LENGTH_SEMANTICS = CHAR

Create a Tablespace for HP CSA(Recommended)

For performance reasons, HP recommends that you create a new tablespace which stores LOBs for the CSA_DOCUMENT table. Work with the database administrator to create a tablespace to be used by HP CSA (or refer to the manufacturer’s documentation for more information). HP recommends that the initial tablespace size should be at least 3 GB.

The tablespace must be created before installing HP CSA and then must be configured immediately after HP CSA is installed.

Install Microsoft SQL Server

Refer to HP Cloud Service Automation System and Software Support Matrix for a list of supported database versions, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Database installation is typically done in partnership with a database administrator. Microsoft SQL Server must be installed with Mixed Mode authentication. During the installation of Microsoft SQL Server, from the Database Engine Configuration dialog, for Authentication Mode, select Mixed Mode (SQL Server authentication and Windows authentication).

Configure Microsoft SQL Server

These tasks must be completed before HP CSA is installed. Work with the database administrator to complete the following tasks (or refer to the manufacturer’s documentation for more information).

Enable TCP/IP (Required)

TCP/IP must be enabled on the Microsoft SQL Server in order for HP CSA to log in to the database. By default, TCP/IP may be disabled on the Microsoft SQL Server. Verify the TCP/IP configuration.

From the SQL Server Configuration Manager:

  1. Select SQL Server Network Configuration > Protocols for <instance_name>.
  2. Double-Click TCP/IP to open the TCP/IP Properties dialog.
  3. From the TCP/IP Properties dialog, select the IP Addresses tab.
  4. Verify TCP/IP is active and enabled, and verify the TCP port is set to 1433. Update any properties that are not set correctly.

Configure a Microsoft SQL Server User for HP CSA (Required)

An HP CSA database user is needed when installing HP CSA.

Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

To create a database user for HP CSA, do the following:

  1. Create a new database for HP CSA.
  2. Add an HP CSA database user with the following roles:
    • db_datareader
    • db_datawriter
    • db_owner

You must provide this user's username and password when prompted for the CSA database user during the installation of HP CSA.

Configure a Reporting Database User for HP CSA (Required for Reporting)

A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):

Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

  1. Create a database user (for example, CSAReportingDBUser).
  2. Create a role for this HP CSA database user (for example, CSAReportingDBRole) and grant the following privilege to the role:
    • CREATE SESSION
  3. Grant the role to the HP CSA database user.
  4. Alter the HP CSA database user by setting this role as the user's default role.

For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:

Create user CSAReportingDBUser identified by CSAReportingDBUser;
Create role CSAReportingDBRole;
Grant CREATE SESSION to CSAReportingDBUser;
Grant CSAReportingDBRole to CSAReportingDBUser;
Alter user CSAReportingDBUser default role CSAReportingDBRole;

A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.

Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

Add a reporting database user to the HP CSA database with no roles.

For example, run the following commands to create the CSAReportingDBUser read-only user:

CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;

Optionally, create a reporting database user for HP CSA (for example, CSAReportingDBUser). A reporting database user is needed only if you want to use the reporting capabilities of HP CSA. This user should have read-only rights.

Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

From the psql prompt, enter the following:

create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;

If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the installation of HP CSA.

Create a Filegroup (Recommended)

For performance reasons, HP recommends that you associate a new filegroup with the CSA_DOCUMENT table. Work with the database administrator to configure a filegroup to be used by HP CSA (or refer to the manufacturer’s documentation for more information). HP recommends that the initial filegroup size should be at least 3 GB.

The filegroup is configured after HP CSA is installed.

Install PostgreSQL

Refer to HP Cloud Service Automation System and Software Support Matrix for a list of supported database versions, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Install the database according to the manufacturer’s documentation. Database installation is typically done in partnership with a database administrator.

Configure PostgreSQL

These tasks must be completed before HP CSA is installed. Work with the database administrator to complete the following tasks (or refer to the manufacturer’s documentation for more information).

Configure PostgreSQL Users and Database (Required)

At least two database users are needed when installing HP CSA. Do the following:

  1. 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-clientrpm -ivh postgres-client.rpm

  2. 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

  3. 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.

  4. Create an HP CSA database user (for example, csadbuser). The HP CSA database user is required. This user should inherit rights from parent roles and be a superuser.

    Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

    From the psql prompt, enter the following:

    create role csadbuser login password '<csadbuser_password>' superuser inherit;

    You must provide this user's username and password when prompted for the CSA database user during the installation of HP CSA.

  5. A reporting database role and read-only user are needed only if you want to use the reporting capabilities of HP CSA. Work with the database administrator to create a role and read-only user to do the following (or refer to the manufacturer’s documentation for more information):

    Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

    1. Create a database user (for example, CSAReportingDBUser).
    2. Create a role for this HP CSA database user (for example, CSAReportingDBRole) and grant the following privilege to the role:
      • CREATE SESSION
    3. Grant the role to the HP CSA database user.
    4. Alter the HP CSA database user by setting this role as the user's default role.

    For example, run the following commands to create the CSAReportingDBRole role and CSAReportingDBUser read-only user:

    Create user CSAReportingDBUser identified by CSAReportingDBUser;
    Create role CSAReportingDBRole;
    Grant CREATE SESSION to CSAReportingDBUser;
    Grant CSAReportingDBRole to CSAReportingDBUser;
    Alter user CSAReportingDBUser default role CSAReportingDBRole;

    A reporting database user is needed only if you want to use the reporting capabilities of HP CSA.

    Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

    Add a reporting database user to the HP CSA database with no roles.

    For example, run the following commands to create the CSAReportingDBUser read-only user:

    CREATE LOGIN CSAReportingDBUser WITH PASSWORD = '<csareportingdbuser_password>';
    CREATE USER CSAReportingDBUser FOR LOGIN CSAReportingDBUser WITH DEFAULT_SCHEMA = csa;

    Optionally, create a reporting database user for HP CSA (for example, CSAReportingDBUser). A reporting database user is needed only if you want to use the reporting capabilities of HP CSA. This user should have read-only rights.

    Caution: The username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

    From the psql prompt, enter the following:

    create role CSAReportingDBUser login password '<csareportingdbuser_password>' nosuperuser nocreatedb nocreaterole inherit;

    If you configure this user, you must provide this user's username and password when prompted for the CSA reporting database user during the installation of HP CSA.

  6. Create a new database for HP CSA. Grant the HP CSA database user all rights to this database and grant the reporting database user read-only access to this database.

    Caution: The database name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

    For example, if you create a database named csadb, an HP CSA user named csadbuser, and a reporting database user CSAReportingDBUser, from the psql prompt, enter the following commands:

    create database csadb with owner=csadbuser connection limit=-1;
    grant all on database csadb to csadbuser;
    grant connect on database csadb to CSAReportingDBUser;

  7. Create a new database for HP Operations Orchestration. Grant the HP Operations Orchestration database user all rights to this database.

    Caution: The database name cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

    For example, if you create a database named csaoodb and an HP Operations Orchestration user named csaoodbuser, from the psql prompt, enter the following commands:

    create database csaoodb with owner=csaoodbuser connection limit=-1;
    grant all on database csaoodb to csaoodbuser;

  8. Exit psql. From the psql prompt, enter the following:

    \q

Install HP Operations Orchestration

Install HP Operations Orchestration to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

If you are using an existing installation of HP Operations Orchestration, you should verify that the correct versions of patches and updates have been applied.

Install HP Cloud Service Automation

Note: Installation log files are written to the %CSA_HOME%$CSA_HOME\_CSA_4_1_0_installation\Logs\ directory.

To install HP Cloud Service Automation (HP CSA), complete the following steps.

  1. Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
  2. Run the setup.exe installation file.

  3. On the Introduction screen, read the information and click Next.

  4. Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml file (you may need to show hidden files), make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  5. Select HP CSA and Marketplace Portal and click Next.

  6. Choose a location in which to install HP CSA and click Next (%CSA_HOME%$CSA_HOME is set to this location).

    The default location is C:\Program Files\Hewlett-Packard\CSA.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    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.

  7. Choose the JRE that will be used by HP CSA.

    In this documentation, the directory in which the JRE is installed will be referred to as <csa_jre>.

    For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

    OpenJDK JRE

    The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, click Open JRE and click Next.

    The default location in which the OpenJDK JRE is installed is C:\Program Files\Hewlett-Packard\CSA\openjre.

    Oracle JRE

    If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE, select the location in which you installed this JRE, and click Next.

    The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, click Choose and select the location in which you installed the JRE that will be used by HP CSA.

    Caution:

    The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.

  8. Select the type of database installed (Microsoft SQL Server)(Oracle)(PostgreSQL) and click Next.

    For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport). Click Choose to select the directory.

    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.

  9. Define the database instance on which the HP CSA database components should be installed or where the HP CSA database schema already exists. Enter the following database information and click Next.

    Field Name Description
    Database Host The hostname or IP address of the server where the database is located. When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4] or [::1].
    Database Port The database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL).

    Database NameOracle SID

    The name of the database instance on which the HP CSA database schema will be installed. If you are creating a new HP CSA database schema, this is the name of the database instance on which the HP CSA database components will be installed. If you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version HP 4.10, this is the name of the database instance on which the HP CSA database schema exists. For an Oracle database, this is the System ID (SID).
    Database Username The username of the database user you configured for HP CSA after installing the database.
    Database Password The password for the database user.

    If you created a reporting database role and read-only userreporting database user when you configured the database, select the Reporting User checkbox and enter the following information:

    Field Name Description
    CSA Reporting Database Username The username of the database user you configured for reporting purposes for HP CSA after installing the database.
    CSA Reporting Database Password The password for the CSA reporting database user.
  10. Install HP CSA database components onto the database instance to create the HP CSA database schema, if it does not exist.

    Click Yes to install HP CSA database components and create the HP CSA database schema. When you select this option, the HP CSA service automatically starts when you exit the installer.

    Click No if you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version 4.10. When you select this option, the HP CSA service does not start when you exit the installer. Refer to the end of this section for information on how to start and stop the HP CSA service.

  11. From the Enter host name screen, enter the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.

    Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.

  12. By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.

    If you do not want to use HPSSO, you can disable it.

    You MUST disable HP Single Sign-On if you are installing HP CSA in a FIPS 140-2 compliant environment.

    If enabled, enter the domain name of the network to which the server on which you are installing HP CSA belongs and click Next.

    Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.

    Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.

  13. Review your selections and click Install to complete the installation.

  14. 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.

  15. Click Done to exit the installer.

  16. Verify that the HP Cloud Service Automation and Marketplace Portal services have started by navigating to Control Panel > Administrative Tools > Services. It can take up to five minutes for the HP Cloud Service Automation to start. If one or both services have not started, right-click on the service and select Start.

    The installer creates the HP Cloud Service Automation and Marketplace Portal services. If you opted to install the HP Cloud Service Automation database components, the installer starts these services. The HP Cloud Service Automation service must be running in order to access the Cloud Service Management Console and the Marketplace Portal service must be running in order to access the Marketplace Portal.

To start, stop, and restart the HP Cloud Service Automation and Marketplace Portal services, navigate to Control Panel > Administrative Tools > Services, right-click on a service, and select the desired action.

Note: Installation log files are written to the %CSA_HOME%$CSA_HOME/_CSA_4_1_0_installation/Logs/ directory and are named csa_*.txt.

To install HP Cloud Service Automation (HP CSA), complete the following steps.

  1. Log in to the system as the root user.
  2. Install the unzip utility if it is not already installed. Enter the following:

    apt-get install unzip

  3. Create an installation directory for HP CSA (this document assumes that you will install the product in /usr/local/hp/csa and all examples used in this document are based on this assumption). Enter the following:

    mkdir -p /usr/local/hp/csa

  4. 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

  5. Log out as the root user and log in as csauser.
  6. Copy the HP CSA installation file (setup.bin) to the system and go to the directory in which it has been copied.
  7. Verify that setup.bin is owned by csauser and csauser has full permissions to the file. If necessary, do the following:

    1. Log in as the root user
    2. Enter one or both of the following commands:

      chown csauser setup.bin
      chmod u+rwx setup.bin

    3. Log out as the root user and log in as csauser.
  8. 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.

  9. Run the setup.bin installation file (as the csauser).

    Note: You must run setup.bin as the csauser. If you install HP CSA as another user, you may not be able to run HP CSA.

    As the csauser, enter the following:

    ./setup.bin

  10. Read the Introduction and click enter to continue with the installation.

  11. Read the license agreement. Click enter to scroll through the entire agreement.
  12. Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml file, make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  13. Verify that no HP CSA services are running on the system. Open a command prompt and type ps -ef | grep csa. If the csa process is running, kill it.

    After verifying that no HP CSA services are running on the system, close the command prompt.

    Select enter to continue the installation.

  14. Select the application to install and click Enter.

    HP CSA and Marketplace Portal

    Installs the entire HP CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.

    Marketplace Portal

    Installs only the Marketplace Portal on the system.

  15. Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.

    The default location is /usr/local/hp/csa.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.

  16. Choose the JRE that will be used by HP CSA.

    In this documentation, the directory in which the JRE is installed will be referred to as $CSA_JRE_HOME.

    For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

    OpenJDK JRE

    The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, type 1 and select Enter.

    The default location in which the OpenJDK JRE is installed is /usr/local/hp/csa/openjre.

    Oracle JRE

    If you have installed a supported version of Oracle JRE to be used by HP CSA, type 2 and select Enter. Type the location in which you installed this JRE and select Enter.

    The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, type in the location in which you installed the JRE that will be used by HP CSA and select Enter.

  17. Define the database instance on which the HP CSA database components should be installed. Enter the following database information (select Enter after each entry).

    1. Enter the type of database you have installed: MSSql (Microsoft SQL Server)OraclePostgres (PostgreSQL).

      For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

    2. Enter the database hostname. This is 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]. The default value is the IP address of the localhost (127.0.0.1).
    3. Enter the database port. This is the database port number, such as 1433 (Microsoft SQL Server)1521 (Oracle)5432 (PostgreSQL).

    4. Enter the database name. This is the name of the database instance on which the HP CSA database schema will be installed. If you are creating a new HP CSA database schema, this is the name of the database instance on which the HP CSA database components will be installed. If you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version HP 4.10, this is the name of the database instance on which the HP CSA database schema already exists.

      If you followed the examples in this document, enter csadb.

    5. Enter the CSA database user name. This is the user name of the database user you configured for HP Cloud Service Automation after installing the database.

      If you followed the examples in this document, enter csadbuser.

    6. Enter the CSA database password. This is the password for the CSA database user.
    7. Enter the CSA reporting database username (optional). This is the username of the database user you configured for reporting purposes for HP CSA after installing the database.

      If you followed the examples in this document, enter csareportingdbuser.

    8. Enter the CSA reporting database password. This is the password for the CSA reporting database user.
  18. Enter the HP CSA server hostname. This is the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.

    Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.

  19. By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.

    If you do not want to use HPSSO, you can disable it. Type 2 and select Enter.

    To enable HPSSO, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing HP CSA) and select Enter.

    Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.

    Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.

  20. Review your selections and select Enter to complete the installation or Ctrl-c to exit the installation.

  21. When the installation completes, select enter to exit the installer.

  22. Define the CSA_HOME and JAVA_HOME environment variables and add /sbin to the PATH variable for the csauser user. Set CSA_HOME to the location where HP CSA is installed. In a startup script for the csauser user (for example, .profile (Ubuntu) or .bash_profile (Red Hat Enterprise Linux)), add the following:

    export CSA_HOME=/usr/local/hp/csa
    export JAVA_HOME=<csa_jre>$CSA_JRE_HOME
    export PATH=$PATH:/sbin

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.
  23. Source the startup file in which you set the CSA_HOME, JAVA_HOME, and PATH environment variables. If you edited .bashrc (Ubuntu) or .bash_profile (Red Hat Enterprise Linux), enter the following:

    . ./.bashrc (Ubuntu)
    . ./.bash_profile (Red Hat Enterprise Linux)

  24. Create an HP CSA service and a Marketplace Portal service to start and stop the HP CSA and Marketplace Portal processes.

    1. Log in as the root user.
    2. Go to the directory in which HP CSA is installed. For example:

      cd /usr/local/hp/csa

    3. 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

    4. Change permissions of the scripts. Enter the following:

      chmod 755 /etc/init.d/csa
      chmod 755 /etc/init.d/mpp

    5. Log out as the root user.
  25. Log in as csauser and start the HP CSA and Marketplace Portal services. Enter the following:

    service csa start
    service mpp start

The HP Cloud Service Automation service must be running in order to access the Cloud Service Management Console. You can start this service by typing service csa start. You can restart this service by typing service csa restart. You can stop the service by typing service csa stop. You can check the status of the service by typing service csa status.

The Marketplace Portal service must be running in order to access the Marketplace Portal. You can start this service by typing service mpp start. You can restart this service by typing service mpp restart. You can stop the service by typing service mpp stop. You can check the status of the service by typing service mpp status.

Note: Installation log files are written to the %CSA_HOME%$CSA_HOME\_CSA_4_1_0_installation\Logs\ directory.

To install a remote instance of the Marketplace Portal, complete the following steps.

  1. Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
  2. Run the setup.exe installation file.

  3. On the Introduction screen, read the information and click Next.

  4. Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml file (you may need to show hidden files), make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  5. Select Marketplace Portal and click Next.

  6. Choose a location in which to install the Marketplace Portal and click Next (%CSA_HOME%$CSA_HOME is set to this location).

    The default location is C:\Program Files\Hewlett-Packard\CSA.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    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.

  7. Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.

    Field Name Description
    HP CSA Host The fully-qualified domain name of the system on which HP CSA is installed.
    HP CSA Port The port number used to communicate with HP CSA.
    HP CSA Certificate The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system.
  8. 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.

  9. Click Done to exit the installer.

  10. 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_HOME/_CSA_4_1_0_installation/Logs/ directory and are named csa_*.txt.

To install HP Cloud Service Automation (HP CSA), complete the following steps.

  1. Log in to the system as the root user.
  2. Install the unzip utility if it is not already installed. Enter the following:

    apt-get install unzip

  3. Create an installation directory for HP CSA (this document assumes that you will install the product in /usr/local/hp/csa and all examples used in this document are based on this assumption). Enter the following:

    mkdir -p /usr/local/hp/csa

  4. 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

  5. Log out as the root user and log in as csauser.
  6. Copy the HP CSA installation file (setup.bin) to the system and go to the directory in which it has been copied.
  7. Verify that setup.bin is owned by csauser and csauser has full permissions to the file. If necessary, do the following:

    1. Log in as the root user
    2. Enter the following commands:

      chown csauser setup.bin
      chmod u+rwx setup.bin

    3. Log out as the root user and log in as csauser.
  8. Run the setup.bin installation file (as the csauser).

    Note: You must run setup.bin as the csauser. If you install HP CSA as another user, you may not be able to run HP CSA.

    As the csauser, enter the following:

    ./setup.bin

  9. Read the Introduction and click enter to continue with the installation.

  10. Read the license agreement. Click enter to scroll through the entire agreement.
  11. Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml file, make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  12. Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.

    The default location is /usr/local/hp/csa.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.

  13. Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.

    Field Name Description
    HP CSA Host The fully-qualified domain name of the system on which HP CSA is installed.
    HP CSA Port The port number used to communicate with HP CSA.
    HP CSA Certificate The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system.
  14. 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.

  15. Review your selections and select enter to complete the installation or ctrl-c to exit the installation.

  16. When the installation completes, select enter to exit the installer.

  17. 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

  18. 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)

  19. Create the Marketplace Portal service to start and stop the Marketplace Portal process.

    1. Log in as the root user.
    2. Go to the directory in which the Marketplace Portal is installed. For example:

      cd /usr/local/hp/csa

    3. Copy the mpp script to the /etc/init.d directory. Enter the following:

      cp ./scripts/mpp /etc/init.d

    4. Change permissions of the script. Enter the following:

      chmod 755 /etc/init.d/mpp

    5. Log out as the root user.
  20. Log in as csauser and start the Marketplace Portal service. Enter the following:

    service mpp start

The Marketplace Portal service must be running in order to access the Marketplace Portal. You can start this service by typing service mpp start. You can restart this service by typing service mpp restart. You can stop the service by typing service mpp stop. You can check the status of the service by typing service mpp status.

Configure Oracle Tablespace

Configure the Oracle tablespace you created for HP Cloud Service Automation only if you are installing HP Cloud Service Automation for the first time and there is no data in the CSA_DOCUMENT table. The tablespace must have been created before HP Cloud Service Automation is installed and then must be configured immediately after HP Cloud Service Automation is installed.

Work with the database administrator to perform the following (or refer to the manufacturer’s documentation for more information):

Modify the CSA_DOCUMENT table such that LOB segments are stored in the tablespace. For example:

ALTER TABLE csa_document
MOVE LOB(content)
STORE AS (TABLESPACE <new_tablespace>);

Configure Microsoft SQL Server

These tasks must be completed after HP Cloud Service Automation is installed.

Configure Microsoft SQL Server Filegroup

Configure the Microsoft SQL server filegroup you created for HP Cloud Service Automation only if you are installing HP Cloud Service Automation for the first time and there is no data in the CSA_DOCUMENT table. The filegroup must have been created before HP Cloud Service Automation is installed and then must be configured immediately after HP Cloud Service Automation is installed.

Work with the database administrator to perform the following (or refer to the manufacturer’s documentation for more information):

  1. Drop all constraints from the CSA_DOCUMENT table.
  2. Drop the CSA_DOCUMENT table.
  3. Recreate the CSA_DOCUMENT table and associate it with the filegroup.
  4. Recreate the constraints for the CSA_DOCUMENT table.

Secure the Marketplace Portal

For security reasons, the Marketplace Portal file system must be protected by the operating system. Do the following:

  1. Open an elevated command prompt (a command prompt that is run as the administrator). For example, navigate to All Programs > Accessories. Right-click on Command Prompt and select Run as administrator.
  2. From the elevated command prompt, run the following command:

    attrib +s +h "%CSA_HOME%\portal" /S /D /L

    where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed.

  3. Restart the HP Cloud Service Automation and Marketplace Portal services. For example, navigate to Control Panel > Administrative Tools > Services. Right-click on the service and select Restart.
  1. Log in as the root user.
  2. Run the following commands:

    chown –R csauser:csagrp $CSA_HOME/portal
    chmod –R 700 $CSA_HOME/portal

    where csauser and csagrp are the user and group you configured for HP CSA when you installed HP CSA and %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed.

  3. Log out as root and log in as csauser.
  4. Restart the csa and mpp services by running the following commands:

    service csa restart
    service mpp restart

Configure HP Operations Orchestration

The HP CSA solution includes a number of HP Operations Orchestration flows that perform HP CSA operations.

Complete the following tasks to configure HP Operations Orchestration to integrate with HP CSA:

  • Add a JRE to the system path
  • Install HP CSA flows
  • Set remote action services
  • Configure system accounts settings
  • Configure system properties settings
  • Configure general system configuration settings in HP Operations Orchestration Central
  • Configure SSL between HP CSA and HP Operations Orchestration
  • Check RAS timeout settings (optional)
  • Change HP Operations Orchestration REST API timeout (optional)

Note: In the following instructions, %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed and %ICONCLUDE_HOME% or $ICONCLUDE_HOME is where you installed HP Operations Orchestration.

Be sure all the latest patches for HP Operations Orchestration have been installed. See the HP Cloud Service Automation System and Software Support Matrix for more information, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Add a JRE to the System Path

The HP CSA flows that are imported require that a JRE be included in the system path on the system running HP CSA.

Windows

  1. Open the Environment Variables dialog:

    1. Right-click Computer and select Properties.
    2. Select Advanced System Settings.
    3. Click Environment Variables.

  2. Select the Path system variable.
  3. Click Edit.
  4. At the end of the value for Variable value, add a semicolon (;) and the following path:

    If HP Operations Orchestration and HP CSA are installed on the same system:

    %ICONCLUDE_HOME%\jre1.6\bin

    or

    If HP Operations Orchestration and HP CSA are installed on different systems:

    <csa_jre>\bin

  5. Click OK and close all windows.

Linux

  1. Open a shell and enter the following command:

    If HP Operations Orchestration and HP CSA are installed on the same system:

    export PATH=$PATH:$ICONCLUDE_HOME/jre1.6/bin

    or

    If HP Operations Orchestration and HP CSA are installed on different systems:

    export PATH=$PATH:$CSA_JRE_HOME/bin

Note: By setting the system path, all applications (that require a JRE) use the JRE that is installed with HP Operations Orchestration (if it is the only path or the first path set to a JRE in the system path). If you need to run another JRE with an application, you must type in the relative path to that JRE in order to run it (for example, when you configure SSL).

Install HP CSA Flows

The flows for HP Cloud Service Automation must be installed in the HP Operations Orchestration Flow Library.

To install HP Cloud Service Automation flows:

  1. If HP Cloud Service Automation and HP Operations Orchestration are running on different systems, copy the %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/OO Flow Content\/9X\/CSA-4_10-ContentInstaller.jar file from the HP Cloud Service Automation system to the HP Operations Orchestration system (where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed).
  2. On the system running HP Operations Orchestration, open a command prompt (Windows) or shell (Linux) and change to the directory where the CSA-4_10-ContentInstaller.jar is located.
  3. Run the following command:

    Windows
    "%ICONCLUDE_HOME%\jre1.6\bin\java" ‑jar CSA-4_10-ContentInstaller.jar ‑centralPassword <OOAdminPassword>

    Linux
    $ICONCLUDE_HOME/jre1.6/bin/java ‑jar CSA-4_10-ContentInstaller.jar ‑centralPassword <OOAdminPassword>

Set Remote Action Services

  1. Log in to HP Operations Orchestration Studio.
  2. Open the Configuration > Remote Action Services folder.
  3. Double-click RAS_Operator_Path.
  4. Set the URL to:

    https://<FQDN>:9004/RAS/services/RCAgentService

    where <FQDN> is the fully qualified domain name or IP address of the HP Operations Orchestration host. Do not use localhost in the URL. Using localhost does not work correctly even though it appears to work when you run HP Operations Orchestration Studio on the same machine as the RAS.

    RAS must be run on the same system as HP Operations Orchestration Studio. Running HP Operations Orchestration Studio on another machine produces errors and turns flows red with a cryptic error message about result assignments to result variables that do not exist.

Configure System Accounts Settings

  1. Log in to HP Operations Orchestration Studio.
  2. Open the Configuration > System Accounts folder.
  3. Double-click CSA_REST_CREDENTIALS.
  4. Verify the Credentials are set to the following values:

    • User Name: ooInboundUser
    • Password: cloud

    where CSA_REST_CREDENTIALS are the credentials for HP CSA REST authentication.

    Note: The User Name configured for the CSA_REST_CREDENTIALS System Account setting must match the Property Value (HP Operations Orchestration version 9.07) or Override Value (HP Operations Orchestration version 10.10) configured for the CSA_OO_USER System Property setting.

Configure System Properties Settings

  1. Log in to HP Operations Orchestration Studio.
  2. Open the Configuration > System Properties folder.
  3. Double-click CSA_REST_URI.
  4. Set the Property Value to:

    https://<csa_hostname>:8444/csa/rest

  5. Double-click CSA_OO_USER.
  6. Verify the Property Value is set to:

    ooInboundUser

    Note: The Property Value (HP Operations Orchestration version 9.07) or Override Value (HP Operations Orchestration version 10.10) configured for the CSA_OO_USER System Property setting must match the User Name configured for the CSA_REST_CREDENTIALS System Account setting.

The other settings can be optionally configured. For information about the settings, refer to the HP Cloud Service Automation Configuration Guide.

Configure General System Configuration Settings in HP Operations Orchestration Central

  1. Log in to HP Operations Orchestration Central.
  2. Open the Administration > System Configuration > General tab.
  3. Set the Save history base on flags property to true.

Configure SSL Between HP Cloud Service Automation and HP Operations Orchestration

For each system running HP CSA, import the root certificate of each HP Operations Orchestration's Certificate Authority.

Import HP Operations Orchestration's certificate into HP CSA

Import the root certificate of HP Operations Orchestration's Certificate Authority into HP Cloud Service Automation (you must first export HP Operations Orchestration's certificate from HP Operations Orchestration's truststore and then import it into HP CSA's truststore).

  1. On the system running HP Operations Orchestration, open a command prompt and change the directory to %ICONCLUDE_HOME% (Windows) or $ICONCLUDE_HOME (Linux).
  2. Run the following command:

    Windows
    .\jre1.6\bin\keytool -exportcert -alias pas -file C:\oo.crt -keystore .\Central\conf\rc_keystore -storepass bran507025

    Linux
    ./jre1.6/bin/keytool -exportcert -alias pas -file /tmp/oo.crt -keystore ./Central/conf/rc_keystore -storepass bran507025

    where C:\oo.crt and /tmp/oo.crt are examples of filenames and locations used to store the exported root certificate (you can choose a different filename and location).

  3. If HP Operations Orchestration is not running on the same system as HP Cloud Service Automation, copy oo.crt from the HP Operations Orchestration system to the system running HP Cloud Service Automation (in this example, the file is copied to C:\/tmp).
  4. On the system running HP Cloud Service Automation, run the following command:

    "<csa_jre>\bin\keytool" -importcert -alias pas -file C:\oo.crt -keystore <csa_jre>\lib\security\cacerts -storepass changeit$CSA_JRE_HOME/bin/keytool -importcert -alias pas -file /tmp/oo.crt -keystore $CSA_JRE_HOME/lib/security/cacerts -storepass changeit

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

  5. When prompted to trust the certificate, enter yes.
  6. Restart the HP CSA services.

    To restart HP CSA:

    1. On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.

    2. Right-click on the HP Cloud Service Automation service and select Restart.

    3. Right-click on the HP Marketplace Portal service and select Restart.

    To restart HP CSA, on the server that hosts HP CSA, type the following:

    service csa restart
    service mpp restart

Check RAS Timeout Settings (Optional)

Remote Access Server (RAS) operations are subject to a default timeout limit of 20 minutes on HP Operations Orchestration Central. You can change the time-out setting to support operations that are likely to take more than 20 minutes to complete.

If you expect to run large deployments, change the time-out setting according to Changing the timeout limit for RAS operations in the HP Operations Orchestration Software Administrator’s Guide. You may also refer to HP Operations Orchestration User's Guide sections Adding a RAS override and Best practices for runtime environment overrides. Both documents are available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Change HP Operations Orchestration REST API Timeout (Optional)

The calls HP CSA makes to the HP Operations Orchestration REST APIs are synchronous, and HP Operations Orchestration will time-out the connection after one hour by default. To extend this time-out, do the following:

  1. Open the following file in a text editor:

    Windows
    %ICONCLUDE_HOME%\Central\conf\Central.properties

    Linux
    $ICONCLUDE_HOME/Central/conf/Central.properties

  2. Add the following lines:

    # the maximum flow timeout value in milliseconds, this is equivalent to 2 hrs
    dharma.headless2.continuation.timeout=7200000

  3. Open the following file in a text editor:

    Windows
    %ICONCLUDE_HOME%\Central\WEB-INF\applicationContext.xml

    Linux
    $ICONCLUDE_HOME/Central/WEB-INF/applicationContext.xml

  4. Add the following property to the dharma.RCDefaults section:

    <bean id="dharma.RCDefaults" class="com.iconclude.dharma.util.spring.RCDefaultsSpringFactory" lazy-init="false" singleton="true">

    ................

    <prop key="dharma.headless2.continuation.timeout">${dharma.headless2.continuation.timeout}</prop>

  5. Restart the HP Operations Orchestration Central service.

Complete the following tasks to configure HP Operations Orchestration to integrate with HP CSA:

  • Add a JRE to the system path
  • Install the HP CSA content pack
  • Configure internal users
  • Deploy content packs required by HP CSA
  • Set up system accounts for the HP CSA content pack
  • Set up system properties
  • Configure HP Single Sign-On
  • Configure properties in HP CSA
  • Configure SSL between HP Cloud Service Automation and HP Operations Orchestration

Note: In the following instructions, %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed and %ICONCLUDE_HOME% or $ICONCLUDE_HOME is where you installed HP Operations Orchestration.

Be sure all the latest patches for HP Operations Orchestration have been installed. See the HP Cloud Service Automation System and Software Support Matrix for more information, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Add a JRE to the System Path

The HP CSA flows that are imported require that a JRE be included in the system path on the system running HP CSA.

Windows

  1. Open the Environment Variables dialog:

    1. Right-click Computer and select Properties.
    2. Select Advanced System Settings.
    3. Click Environment Variables.

  2. Select the Path system variable.
  3. Click Edit.
  4. At the end of the value for Variable value, add a semicolon (;) and the following path:

    If HP Operations Orchestration and HP CSA are installed on the same system:

    %ICONCLUDE_HOME%\java\bin

    or

    If HP Operations Orchestration and HP CSA are installed on different systems:

    <csa_jre>\bin

  5. Click OK and close all windows.

Linux

  1. Open a shell and enter the following command:

    If HP Operations Orchestration and HP CSA are installed on the same system:

    export PATH=$PATH:$ICONCLUDE_HOME/java/bin

    or

    If HP Operations Orchestration and HP CSA are installed on different systems:

    export PATH=$PATH:$CSA_JRE_HOME/bin

Note: By setting the system path, all applications (that require a JRE) use the JRE that is installed with HP Operations Orchestration (if it is the only path or the first path set to a JRE in the system path). If you need to run another JRE with an application, you must type in the relative path to that JRE in order to run it (for example, when you configure SSL).

Install the HP CSA Content Pack

  • Copy the %CSA_HOME%$CSA_HOME\CSAKit-4.1\OO Flow Content\10X\oo10-csa-cp-4.10.000-uuids.txt%CSA_HOME%$CSA_HOME/CSAKit-4.1/OO Flow Content/10X/oo10-csa-cp-4.10.000-uuids.txt file to:

    Windows
    %ICONCLUDE_HOME%\central\cmu\exclusions

    Linux
    $ICONCLUDE_HOME/central/cmu/exclusions

  • If HP CSA and HP Operations Orchestration are running on different systems, copy the %CSA_HOME%$CSA_HOME\CSAKit-4.1\OO Flow Content\10X\oo10-csa-cp-4.10.000.jar%CSA_HOME%$CSA_HOME/CSAKit-4.1/OO Flow Content/10X/oo10-csa-cp-4.10.000.jar file from the HP Cloud Service Automation system to the HP Operations Orchestration system (where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed).

Configure Internal Users

Internal users can be used to configure HP Operations Orchestration for HP CSA.

  1. Log in to HP Operations Orchestration Central.

  2. Click the System Configuration button.
  3. Select Security > Internal Users.
  4. Click the Add button.
  5. Enter the following information:

    Field Recommended Value
    User Name csaoouser
    Password cloud
    Roles ADMINISTRATOR, SYSTEM_ADMIN

    The csaoouser user is used to import the HP Operations Orchestration flows. When importing flows, this user is configured in the HP Operations Orchestration input file used by the process definition tool.

  6. Click Save.
  7. Enable authentication by selecting the Enable Authentication check box.
  8. Select OK in the confirmation dialog.
  9. Click the Add button.

  10. Enter the following information:

    Field Recommended Value
    User Name admin
    Password cloud
    Roles ADMINISTRATOR, SYSTEM_ADMIN

    The admin user is used with HP Single Sign-On (HPSSO). When HP Operations Orchestration is launched from the Cloud Service Management Console, this user allows access to HP Operations Orchestration without having to log in.

  11. Click Save.
  12. Enable authentication by selecting the Enable Authentication check box.
  13. Select OK in the confirmation dialog.
  14. Log out of HP Operations Orchestration Central and log back in as the csaoouser.

Deploy Content Packs Required by HP CSA

The HP CSA content packs must be deployed after you have deployed the base HP Operations Orchestration content packs.

  1. From HP Operations Orchestration Central, click the Content Management button.

  2. Click the Content Packs tab.
  3. Click the Deploy New Content icon.
  4. In the Deploy New Content dialog, click the Add files for deployment icon.
  5. Browse to the content packs on the system. Select a content pack and click Open then Deploy. Find, select, open, and deploy the following base content packs in the order shown below:

    Note: These are the base content packs provided by HP Operations Orchestration. Refer to the HP Operations Orchestration documentation for the location of these content packs. These base content packs are not included in the installation of HP CSA.

    • oo10-base-cp-1.1.1
    • oo10-cloud-cp-1.1.0
    • oo10-hp-solutions-cp-1.1.2
    • oo10-virtualization-cp-1.1.0
    • oo10-sa-cp-1.0.2
    • oo10-sm-cp-1.0.1

    Note: Do not deploy the HP CSA content pack until after you have deployed the base content packs. The HP CSA content pack must be deployed separately and after you have deployed the base content packs.

    The deployment may take a few minutes and the dialog will show a progress bar.

    When the deployment succeeds, click Close to close the dialog.

  6. Click the Deploy New Content icon.
  7. Click the Add files for deployment icon.
  8. Navigate to the %CSA_HOME%$CSA_HOME\CSAKit-4.1\OO Flow Content\10X%CSA_HOME%$CSA_HOME/CSAKit-4.1/OOFlowContent/10X directory, select the oo10-csa-cp-4.10.000 content pack, and click Open.

  9. Click Deploy.

    The deployment may take a few minutes and the dialog will show a progress bar.

  10. When the deployment succeeds, click Close to close the dialog.
  11. Click the Deploy New Content icon.

  12. Click the Add files for deployment icon.
  13. Navigate to the %CSA_HOME%$CSA_HOME\Tools\ComponentTool\contentpacks\%CSA_HOME%$CSA_HOME/Tools/ComponentTool/contentpacks/ directory, select all the content packs, and click Open.

  14. Click Deploy.

    The deployment may take a few minutes and the dialog will show a progress bar.

  15. When the deployment succeeds, click Close to close the dialog.

Set Up System Accounts for the HP CSA Content Pack

Set up system accounts for the HP CSA content pack:

  1. Log in to HP Operations Orchestration Central.
  2. Click the Content Management button.
  3. Select Configuration Items > System Accounts.
  4. Click the Add icon.
  5. Enter the following information if it is not already configured:

    Field Recommended Value
    System Account Name CSA_REST_CREDENTIALS
    User Name ooInboundUser
    Password cloud

    Note: The User Name configured for the CSA_REST_CREDENTIALS System Account setting must match the Property Value (HP Operations Orchestration version 9.07) or Override Value (HP Operations Orchestration version 10.10) configured for the CSA_OO_USER System Property setting.

  6. Click Save.
  7. Click the Add icon.
  8. Enter the following information if it is not already configured:

    Field Recommended Value
    System Account Name CSA_SERVICEMANAGER_CREDENTIALS
    User Name falcon
    Password

    <leave_blank>

  9. Click Save.

Set Up System Properties for the HP CSA Content Pack

Set up the following system properties for the HP CSA content pack:

  1. Log in to HP Operations Orchestration Central.
  2. Click the Content Management button.
  3. Select Configuration Items > System Properties.
  4. Click the Add icon.
  5. Enter the following information if it is not already configured:

    Field Recommended Value
    Name CSA_REST_URI
    Override Value https://<csa_hostname>:8444/csa/rest
  6. Click Save.

Configure HP Single Sign-On Between HP CSA and HP Operations Orchestration

If the HP Single Sign-On (HPSSO) was enabled during installation of HP CSA, HPSSO can be configured between HP CSA and HP Operations Orchestration. Configuring HPSSO allows you to launch HP Operations Orchestration from the Cloud Service Management Console without having to log in to HP Operations Orchestration.

HP CSA provides an out-of-the-box user (admin) and password (cloud) and, earlier in this section, you configured an internal user for HP Operations Orchestration with the same username and password. When HP Single Sign-On is configured between HP CSA and HP Operations Orchestration, this user can be used for single sign-on. That is, if you are logged in to HP CSA as the admin user, you can launch HP Operations Orchestration from the Cloud Service Management Console and not have to log in to HP Operations Orchestration. You can also configure LDAP users for single sign-on.

Note: In order to use HPSSO between HP CSA and HP Operations Orchestration, the systems on which HP CSA and HP Operations Orchestration are installed must be in the same domain.

Configure and Enable HP Single Sign-On

To configure and enable HPSSO on HP Operations Orchestration, do the following:

  1. Log in to HP Operations Orchestration Central.

  2. Click the System Configuration button.

  3. Select Security > SSO.

  4. Select the Enable checkbox.

  5. Enter the InitString. This is the value to which the crypto InitString attribute is set in the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\WEB-INF\hpssoConfiguration.xml$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/WEB-INFhpssoConfiguration.xml file. For example, if the entry in the file is crypto InitString="lOJisF9Slbf79hmLsd", copy lOJisF9Slbf79hmLsd to this field. This string is used to encrypt and decrypt the LWSSO_COOKIE_KEY cookie that is used to authenticate the user for single sign-on.

  6. Enter the Domain. This is the domain name of the network of the servers on which HP CSA and HP Operations Orchestration are installed.

  7. Click Save.

Configure LDAP Users for Single Sign-On

In order to enable single sign-on for LDAP users, you must either configure HP CSA and HP Operations Orchestration to use the same LDAP source or, if HP CSA and HP Operations Orchestration use different LDAP sources, configure the same users in both sources. In either case, the HP CSA user must be assigned to the CSA Administrator or Service Operations Manager role and the HP Operations Orchestration user must be assigned any role that allows flows to be viewed.

To configure LDAP for HP Operations Orchestration, do the following:

  1. Log in to HP Operations Orchestration Central.

  2. Click the System Configuration button.

  3. Select Security > LDAP.

  4. Enter the information to configure LDAP.
  5. Click Save.

Configure HP Operations Orchestration Properties in the csa.properties File

These properties are used to integrate with HP Operations Orchestration. In the subscription event overview section of the Operations area in the Cloud Service Management Console, for HP Operations Orchestration version 10.10, selecting the Process ID opens HP Operations Orchestration to the detailed page of the selected process when these properties are configured.

Edit the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties file and configure the following properties:

Property Description
OOS_URL

The URL used to access HP Operations Orchestration Central. This is the HP Operations Orchestration used for provisioning topology designs (HP Operations Orchestration version 10.10).

Set this URL to the system on which HP Operations Orchestration version 10.10 is installed. For example, https://<hostname>:8443.

OOS_USERNAME

The username used to log in to HP Operations Orchestration Central.

Set this username to admin.

OOS_PASSWORD

The encrypted password used by the user defined in OOS_USERNAME to log in to HP Operations Orchestration Central.

Set this property to the encrypted value of the user defined in OOS_USERNAME. For more information about encrypting passwords, refer to the HP Cloud Service Automation Configuration Guide

Configure SSL Between HP Cloud Service Automation and HP Operations Orchestration

For each system running HP CSA, import the root certificate of each HP Operations Orchestration's Certificate Authority.

Import HP Operations Orchestration's certificate into HP CSA

Import the root certificate of HP Operations Orchestration's Certificate Authority into HP Cloud Service Automation (you must first export HP Operations Orchestration's certificate from HP Operations Orchestration's truststore and then import it into HP CSA's truststore).

  1. On the system running HP Operations Orchestration, open a command prompt and change the directory to %ICONCLUDE_HOME% (Windows) or $ICONCLUDE_HOME (Linux).
  2. 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).

  3. If HP Operations Orchestration is not running on the same system as HP Cloud Service Automation, copy oo.crt from the HP Operations Orchestration system to the system running HP Cloud Service Automation (in this example, the file is copied to C:\/tmp).
  4. On the system running HP Cloud Service Automation, run the following command:

    "<csa_jre>\bin\keytool" -importcert -alias tomcat -file C:\oo.crt -keystore <csa_jre>\lib\security\cacerts -storepass changeit$CSA_JRE_HOME/bin/keytool -importcert -alias tomcat -file /tmp/oo.crt -keystore $CSA_JRE_HOME/lib/security/cacerts -storepass changeit

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.

  5. When prompted to trust the certificate, enter yes.
  6. Restart the HP CSA services.

    To restart HP CSA:

    1. On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.

    2. Right-click on the HP Cloud Service Automation service and select Restart.

    3. Right-click on the HP Marketplace Portal service and select Restart.

    To restart HP CSA, on the server that hosts HP CSA, type the following:

    service csa restart
    service mpp restart

Install Infrastructure Orchestration

Install HP Matrix Operating Environment infrastructure orchestration (infrastructure orchestration) according to the manufacturer's recommendations. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

The HP Cloud Service Automation System and Software Support Matrix is available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure Infrastructure Orchestration

To configure HP Matrix Operating Environment infrastructure orchestration, refer to %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/matrix operating environment\/README.txt for more information.

Install VMware vCenter

Install vCenter according to the manufacturer's recommendations. For example, follow the VMware best practices for managing individual ESX servers from a vCenter instance. You can find the VMware documentation at http://www.vmware.com/support/pubs/.

You must have a vCenter instance that can support the flows that actuate vSphere VMs. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

Both the HP Cloud Service Management Console Help, which is available in a printable PDF format, and the HP Cloud Service Automation System and Software Support Matrix are available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Install HP Network Automation

Install HP Network Automation according to the manufacturer's recommendations. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

Installation notes:

  • Do not install HP Network Automation on the same system as HP Operations Orchestration. HP Network Automation and HP Operations Orchestration must run on separate systems.
  • Calculate the resources needed for the HP Network Automation server using the information provided in the HP Network Automation Installation and Upgrade Guide.

HP software product documentation and the HP Cloud Service Automation System and Software Support Matrix are available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure HP Network Automation

The following tasks are required to configure HP Network Automation to integrate successfully with HP Cloud Service Automation:

Step 1: Import Command Scripts to the HP Network Automation Portal

  1. If HP CSA and HP Network Automation are not installed on the same system, copy the HPN Virtual Network.exp command script to the system on which HP Network Automation is installed.

    The default location of the command script file is %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/network automation where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed (for example, C:\Program Files\Hewlett-Packard\CSA/usr/local/hp/csa).

  2. Log in to the HP Network Automation portal as the Administrator (the Administrator user was created during HP Network Automation portal installation).
  3. Click Devices > Device Tools > Command Scripts.
  4. Click Import/Export Command Scripts.
  5. From the Import/Export Scripts/Diagnostics page, click Choose File and browse to the location of the HPN Virtual Network.exp command script.

  6. Click Import.
  7. From the Import Scripts page, verify that the HPN Create Vlan and HPN Delete Vlan checkboxes are selected.
  8. Click Continue.

    The message Important: You have successfully imported one or more Command Scripts or Diagnostics. displays.

  9. Verify that the command scripts were imported. Click Devices > Device Tools > Command Scripts and verify that HPN Create Vlan and HPN Delete Vlan are listed in the Command Scripts page.

Step 2: Validate the Imported Command Script

  1. Click Devices > Device Tools > Command Scripts.
  2. From the Command Scripts page, for HPN Create Vlan, click Run.
  3. From the New Task/Template - Run Command Script page, select switch management ip address ('Applies to' field) of your discovered switch and enter values for Vlan Id, Vlan SubnetIP, and Vlan SubnetMask. For example, set Vlan Id = 200, Vlan Subnet IP = 192.168.30.1 and Vlan Subnet Mask = 255.255.255.0.
  4. Click Save.

    If the networking switch is already discovered and a device snapshot is successfully taken in the HP Network Automation portal, the message Succeeded displays.

Step 3: Verify/Update the Command Script mode

If you are using an HP networking switch, verify that the HPN Create Vlan and HPN Delete Vlan command scripts use the EXT_HP_Procurve Network Automation driver that supports a wide range of HP networking switches. If you want to use another networking switch, update the mode of each command script.

To verify/update the command script mode:

  1. Click Devices > Device Tools > Command Scripts.
  2. For HPN Create Vlan, click Edit.
  3. From the Edit Command Script page:
    • If you are using an HP networking switch, verify the Mode is ProCurve configuration.
    • If you are using another networking switch, select an appropriate Mode from the drop-down box.
  4. Repeat steps 2 and 3 for the HPN Delete Vlan command script.

Install HP Server Automation

Install HP Server Automation to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

You can determine your version and patch level by using the HP Server Automation Client and selecting Help > About.

Installation notes:

  • You can use the DHCP services included with HP Server Automation. For information on configuring a DHCP server with HP Server Automation, see HP Server Automation Simple/Advanced Installation Guide.
  • The HP Server Automation Client should be installed on the HP Operations Orchestration server.
  • The HP Server Automation Client does not register right away after installation. A delay occurs before you can continue with configuration.

HP software product documentation is available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure HP Server Automation

Configure Read and Write Access

The following tasks are required to configure HP Server Automation to allow read and write access to the required areas:

  • Create the HP Cloud Service Automation service account
  • Create the HP Cloud Service Automation administrators group and assign the proper permissions.
  • Validate the HP Cloud Service Automation service account
  • Validate the HP Server Automation client

Step 1: Create the HP Cloud Service Automation Service Account

  1. Open the HP Server Automation Web Client in a browser.
  2. Log in using the HP Server Automation Administrator user name and password (created when the HP Server Automation server was installed).
  3. Click Administration > Users & Groups.
  4. Click New User in the Users tab toolbar and complete the following fields using the values listed in the following table:

    Field Name Value
    Last Name Service Account
    First Name CSA
    Full Name CSA Service Account
    Email Address <your email address>
    User Name hpcsa
    Password <password>
  5. Select Superusers from the Group Membership list to enable this option.
  6. Click Save.
  7. Click Log Out.

Step 2: Create the HP Cloud Service Automation Administrators Group and Assign Permissions

  1. Open the HP Server Automation Web Client in a browser.
  2. Log in using the HP Server Automation Administrator user name and password.
  3. Click Administration > Users & Groups.
  4. Select the Groups tab.
  5. Click New Group and complete the following fields using the values listed in the following table:

    Field Name Value
    Group Name hpcsa-admin
    Group Description HPCSA Administrators
    Not Assigned Read & Write
    Opsware Read
  6. Click Save.
  7. Select hpsca-admin in the list of groups.
  8. Select the Users tab and add the admin and hpcsa users to the hpcsa-admin group.
  9. Click Save.
  10. Select the Facilities tab and select Read & Write to the appropriate facility.

    If only one facility exists, select Read & Write for it.

  11. Click Save.
  12. Select the Features tab and click Select All in the header row to select all features.
  13. Click Save.
  14. Select the Client Features tab and change all values to Read & Write and Yes where applicable.
  15. Click Save.
  16. Select the Other tab and select all options except Generate Security Reports.
  17. Click Save.
  18. Select the OGFS Permissions tab, click Add Permissions, and enter the following permissions:

    • Features: Select Run Command on Server.
    • Servers: Click the Customers option and select Not Assigned from the list.
    • Login Names: Select Opsware user name, and select Log in as and enter root.
  19. Click Grant.
  20. Click Add Permissions and enter the following permissions:

    • Features: Select Launch Global Shell.
  21. Click Grant.
  22. Click Log Out.

Step 3: Validate the Cloud Service Automation Service Account

  1. Open the HP Server Automation Web Client in a browser and verify that the login screen appears.
  2. Log in using the Cloud Service Automation Service Account credentials you created in the previous steps.
  3. Verify that the HP Server Automation Web Client home page is displayed. A list of tasks and jobs is shown.
  4. Click the Managed Servers option on the left side of the screen and verify that a list of servers with their IP addresses and operating system information is displayed.
  5. Click Log Out and close the Web browser.

Step 4: Validate the HP Server Automation Client

  1. Connect to the system where HP Operations Orchestration is installed.
  2. Verify that the client is installed.

    • If an icon appears on the desktop labeled HP Server Automation Client or a link appears in the Start Menu, the client is installed. Continue to step 3.
    • If neither the icon nor the Start Menu link appear, then you need to install the client by performing the following steps:

      1. Open the HP Server Automation Web Client in a browser and select Download Opsware Launcher at the login screen.
      2. Install the client using the default parameters.

      You must have a JRE installed in order to use the Opsware Launcher on a Windows system.

  3. Launch the client with the following credentials:

    • Username: hpcsa
    • Password: <hpcsa password>
    • Core Server: <SA Server Host Name>

    The above login information may vary depending on your installation.

  4. Verify that the HP Server Automation application starts and Device Groups appear in the left hand navigation pane.
  5. Click All Managed Servers and verify that a list of servers with their names, IP addresses, and operating system information is displayed.
  6. Exit the client.

Prepare a VMware Template to Self-Register with HP Server Automation

These steps prepare a VMware template to self-register with HP Server Automation.

Virtual machines (VMs) created by the HP Cloud Service Automation solution are created based on virtual machine templates. The HP Cloud Service Automation flows reference a vSphere template name, and perform a clone operation to provision new virtual machines. These templates would generally provide an operating system image only, with no application software installed.

To allow applications (such as Apache) to be deployed to the image, you must install and configure HP Server Automation and create a template that includes the HP Server Automation Agent software. That is, in order to manage the virtual server and to install application software, the clones are configured to self-register upon power-on with an HP Server Automation system. Once registered as a managed server, software policies are applied to the server in order to install and configure the correct applications. Refer to the HP Server Automation Policy Setter Guide and the HP Server Automation Application Deployment User Guide in the HP Server Automation documentation for more information on managing servers and configuring software policies. HP software product documentation is available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Template Preparation Overview

For cloned virtual machines to register with the HP Server Automation system upon power-on, prepare a template with an HP Server Automation agent. The following is a general outline of the steps to be performed:

  • First, create a virtual machine with the appropriate operating system image that you would like to template. Provision the VM with an operating system through any method supported by vSphere:

    • Manually install the operating system on a prepared, configured VM.
    • Provision the operating system through a network boot operation from the HP Server Automation system.

    Refer to the appropriate vSphere documentation to create a new virtual machine with an installed operating system image.

  • When preparing a virtual machine as a template to be used to clone many new virtual machines, leave the configuration as generic as possible. No hostname can be configured, and the network configuration can be obtained via DHCP.
  • Install and test the appropriate VMware Tools on the virtual machine.
  • Install the HP Server Automation agent. The agent registers the template with the HP Server Automation system so that this machine is in a Managed state for the next step.
  • An APX utility in the HP Server Automation system library is run to prepare the agent on the virtual machine to re-install and register with the HP Server Automation system on the next bootup.
  • The virtual machine is shut down and converted to a template.
  • Delete the virtual machine server record from the HP Server Automation system.

Detailed Process

Refer to the vSphere documentation set for detailed information on the creation, configuration, and operating system installation for a new virtual machine. There are several options to install an operating system onto a new virtual machine. One of the options available is to use the PXE network boot facility from the HP Server Automation server, with an operating system installation profile that integrates the installation of an HP Server Automation agent. A virtual machine which is provisioned using this method starts the agent upon bootup, and attempts to register it with the HP Server Automation system.

If you use another method to provision an operating system on the virtual machine, the HP Server Automation agent can be installed from the HP Server Automation system. You can refer to the product documentation for an expanded discussion of this process; the following instructions describe one method.

Step 1: Provision an Operating System on a Virtual Machine

  1. Boot the virtual machine and make sure that it is connected to the network. Verify that the HP Server Automation (HP SA) system can be reached.
  2. Discover the virtual machine in the Unmanaged Servers (HP SA 9.x) or SA Agent Installation (HP SA 10.x) window in HP Server Automation. You can scan an entire subnet or enter the IP address for the virtual machine and initiate a scan to discover it.

  3. Select the virtual machine, right-click, and then select Manage Server (HP SA 9.x) or Install SA Agent (HP SA 10.x). A new dialog opens.
  4. Provide the appropriate login credentials, and select the action to verify prerequisites, copy installer, and install the agent. Set any desired Installer Options at this time, referring to the HP Server Automation documentation for details.
  5. Click OK.

    When the installation process completes successfully, the agent is installed, and the virtual machine is visible in the All Managed Servers tab. The hostname has not been set, as we plan to convert this virtual machine to a generic template. So, the default host name is used for the virtual machine.

  6. From the Server Information Properties tab, select the virtual machine and press Enter.
  7. Select Properties.
  8. Record the Object ID of the virtual machine, which can be found in the Management Information section of the Properties panel.

Step 2: Sanitize the Agent Configuration on a Template Machine

The agent on our virtual machine template must be prepared to install and register a new machine server with HP Server Automation each time we create a new clone. To prepare the agent we must "sanitize" the agent configuration on our template machine by doing the following:

  1. Switch to the Library tab in the HP Server Automation client.
  2. Expand the Extensions folder.
  3. Select Program.
  4. Locate the BRDC HPSA agent sanitizer Automation Platform Extension (APX).
  5. Execute the BRDC HPSA agent sanitizer APX:

    1. Right-click the APX and select Run.
    2. Select the Options tab in the Run Program Extensions dialog.
    3. In the Specify any needed parameters for this program execution field, enter the Object ID, which you previously obtained for the virtual server template:

    4. Click Start Job.
    5. Shut down the virtual machine after the job completes successfully and the agent has been prepared.

    6. Do not reboot this virtual machine again until after it has been converted to a vSphere template.

    7. Using the vSphere client, convert this virtual machine to a template.
    8. The last step is to clean up the server records for the virtual machine template from HP Server Automation. In the All Managed Servers tab:
      1. Deactivate the server.
      2. Delete the server.

The template is now ready to use to clone new virtual machines. HP Cloud Service Automation uses a simple customization template that sets the hostname equal to the VM name. Additional customization is possible during the clone operation. See the Basic Customization section below.

When a newly cloned virtual machine powers up, the HP Server Automation Agent installs and then contacts the HP Server Automation system to self-register. Shortly after power on, you can refresh the All Managed Servers view in the HP Server Automation client to locate the new virtual machine record.

Step 3: Basic Customization

Perform the following basic customizations:

  1. On the vCenter environment click View > Management > Customization Specifications Manager.
  2. Click the New icon.
  3. Select Windows or Linux for your Target Virtual Machine OS. You can create one of each.
  4. If you are creating a Windows target, name it useVmName_Windows. If you are creating a Unix target, name it useVmName_Linux.
  5. Customize as appropriate, noting two important items:

    • On the screen with the NetBIOS Name you must choose Use the virtual machine name.
    • If the virtual machine name exceeds 15 characters, it will be truncated.

Step 4: Install the Prepared Template

The template must be installed on the system containing the vSphere client software. See Configure VMware vCenter for more information.

Consult the vSphere documentation for additional details. You can find the VMware documentation at http://www.vmware.com/support/pubs/.

Configure VMware vCenter

Configure VMware vCenter by installing prepared templates. In the vSphere environment, a template is a master copy of a virtual machine that can be used to create many clones. A clone is a copy of a virtual machine.

You can learn more about creating templates and working with clones in vSphere by referring to VMware's vSphere Virtual Machine Administration Guide for vCenter Server (EN-000312-02), available in the VMware documentation. You can find the VMware documentation at http://www.vmware.com/support/pubs/.

Virtual machines created by the HP Cloud Service Automation solution are created based on virtual machine templates. To allow applications (such as Apache) to be deployed to the image, you must create a template that includes HP Server Automation Agent software. See Prepare a VMware Template to Self-Register with HP Server Automation for more information.

To install a prepared template, do the following:

  1. Locate a prepared template.
  2. Copy the template folder to the system containing the vSphere client software.
  3. From your vSphere client software menu, select View > Inventory > Datastores to see a list of available datastores on your vCenter server.
  4. Right-click one of the available datastores and select Browse Datastore to see the directory structure of that datastore.
  5. Copy the template folder to the datastore by clicking on the Upload files to this datastore button.

    The following image shows the Datastore Browser window with Upload files to this datastore highlighted. It also shows a rhel53x64-clone folder that was uploaded to this datastore:

Consult the vSphere documentation for additional details. You can find the VMware documentation at http://www.vmware.com/support/pubs/.

Install HP SiteScope

Install HP SiteScope to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

Installation notes:

  • Do not install HP SiteScope on the HP Operations Orchestration server. It must be on its own server.
  • Calculate the resources needed for the HP SiteScope server using the information in the HP SiteScope documentation. This calculation should include the number of target servers that you expect Cloud Service Automation to monitor.
  • During installation, you can change the port for the HP SiteScope service to avoid potential conflicts with other web servers that use the default port value of 8080. Select any available port on the system and keep track of the port number that you select.

HP software product documentation is available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure HP SiteScope

The following tasks are required to configure HP SiteScope to integrate successfully with HP Cloud Service Automation:

Step 1: Enable HP Cloud Service Automation to Configure HP SiteScope Monitors

HP SiteScope is installed with a default of secured API calls required for configuring monitors. HP Cloud Service Automation does not support secured API calls; therefore, you must change this setting. To re-configure HP SiteScope so it does not use secure APIs, you must make the following change to the configuration:

  1. Stop the HP SiteScope service by typing the following command in a console window:

    net stop SiteScope

  2. Open the HP SiteScope <sitescopeInstallDir>\groups\master.config file in a text editor.
  3. Change the _accessControlled=true property value to _accessControlled=false.

  4. Restart the HP SiteScope service by typing the following command in a console window:

    net start SiteScope

Step 2: Auto-Deploy the HP Cloud Service Automation Templates and Credential Profiles

  1. Log in to the HP SiteScope server as Administrator.
  2. Log in to the HP Cloud Service Automation server.
  3. From the HP Cloud Service Automation server, copy the %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/sitescope\/CSA templates autoimport.tmpl file to the <sitescopeInstallDir>\persistency\import directory on the HP SiteScope server. When the CSA templates autoimport.tmpl file is processed, HP SiteScope creates a template container (CSA templates) and two credential profiles (WINDOWS-CSA-TARGETS and LINUX-CSA-TARGETS).

  4. Log in to the HP SiteScope Dashboard.
  5. Select the Templates context. In the template tree, look for the CSA templates container. You must wait for the HP SiteScope server to finish processing the CSA templates autoimport.tmpl file before the CSA templates template container is displayed.
  6. Select Preferences context > Credential Preferences and look for the WINDOWS-CSA-TARGETS and LINUX-CSA-TARGETS credential profiles, which you will configure in Step 4: Configure HP Cloud Service Automation Credential Profiles.

Step 3: Manually Import Additional HP Cloud Service Automation Templates

Two additional HP Cloud Service Automation templates, CSA templates Silver and CSA templates Gold, must be manually imported. These templates are used by the CSA_BP_VCENTER_COMPUTE_SITESCOPE_MODIFY_v4.10.00 service design.

  1. Log in to the HP SiteScope Dashboard.

    Note: You must be able to access files in the %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/sitescope directory from the HP SiteScope Dashboard. If necessary, copy this directory to the system from which you are launching the HP SiteScope Dashboard.

  2. Select the Templates context.
  3. In the template tree, right-click SiteScope and select Import.
  4. Browse to %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/sitescope (or the directory to which this directory was copied) and import CSA templates Silver.tmpl.
  5. Repeat steps 3 and 4, but import CSA templates Gold.tmpl.

Step 4: Configure HP Cloud Service Automation Credential Profiles

Configure the credentials used to log in to every Windows system and every Linux system monitored by HP SiteScope. The credentials to all Windows systems must be the same. Likewise, the credentials to all Linux systems must be the same.

  1. Log in to the HP SiteScope Dashboard.
  2. Select Preferences context > Credential Preferences.
  3. Edit the LINUX-CSA-TARGETS credential profile and supply login credentials for your Linux environment.
  4. Edit the WINDOWS-CSA-TARGETS credential profile and supply login credentials for your Windows environment.

Step 5: Configure HP SiteScope Administrator Credentials

Configure the credentials used to log in as the administrator of HP SiteScope. These credentials are used by HP Cloud Service Automation when configuring HP SiteScope resource providers from the Cloud Service Management Console.

  1. Log in to the HP SiteScope Dashboard.
  2. Select Preferences context > User Management Preferences.
  3. Right-click SiteScope Administrator and select Edit User.
  4. If not already specified, enter a login name and password for the SiteScope administrator.

Install HP Universal CMDB

Install HP Universal CMDB to the correct version and patch level. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

If you are using an existing installation of HP Universal CMDB, then you should verify that the necessary patches and updates have been applied. If not, then follow the instructions presented here to update your installation.

If you are installing HP Universal CMDB, then you should follow the installation instructions in the HP Universal CMDB documentation and then follow the instructions presented here to configure your installation.

  1. Click Start > All Programs > HP UCMDB > Start HP Universal CMDB Server.
  2. Monitor the service status by browsing to http://localhost:8080/status.

    You will need to wait until the Default Client status is up on the status page. This takes approximately five minutes. Until then, the HP Universal CMDB console cannot be used.

HP software product documentation is available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure HP Universal CMDB

To configure HP Universal CMDB, deploy a file to your HP Universal CMDB server:

  1. Log in to the HP Cloud Service Automation server.
  2. From the HP Cloud Service Automation server, navigate to the %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/ucmdb folder where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed.

  3. Copy the %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/ucmdb\/CSAIntegration.zip to the HP Universal CMDB server.
  4. Refer to the %CSA_HOME%$CSA_HOME\/CSAKit-4.1\/Lib\/ucmdb\/README.txt file for more information on how to deploy the zipped file.

Install HP Cloud Services

No installation is required for HP Cloud Services as it is accessible through the Web. However, you will need to configure HP Cloud Services to integrate with HP Cloud Service Automation. See Configure HP Cloud Services in this document for more information.

Configure HP Cloud Services

The following tasks are required to configure HP Cloud Services to integrate successfully with HP Cloud Service Automation:

Step 1: Sign Up as an HP Cloud Services User

In order to access HP Cloud Services, you must be a registered user. Sign up for HP Cloud Services by accessing this URL from a supported Web browser: https://console.hpcloud.com/signup

Step 2: Configure a Security Group and KeyPair

To create an HP Cloud Services instance, you must have a Security Group and KeyPair configured in the HP Cloud Services environment:

  1. Log in to HP Cloud Services using the login you created in step 1. From a supported Web browser, go to https://console.hpcloud.com/login.
  2. Under Managed Security Groups, add a group named frontend for each availability zone and region.
  3. Under Managed KeyPair, create a KeyPair for each availability zone and region.

You can configure the Security Group and KeyPair values as default values in the Server Group component properties of an HP CSA service design.

Step 3: Open a Port to Access HP Cloud Services

  1. In order to access the HP Cloud Services environment, port 35357 must be opened on the HP CSA system. Work with the system administrator to open this port.
  2. Access the HP Cloud Services environment from a supported Web browser using the following URL: https://region.geo.identity.hpcloudsvc.com:35357/v2.0.

Install HP Service Manager

Install HP Service Manager according to the manufacturer's recommendations. See HP Cloud Service Automation System and Software Support Matrix for version requirements.

Installation notes:

  • Do not install HP Service Manager on the same system as HP Operations Orchestration. HP Service Manager and HP Operations Orchestration must run on separate systems.
  • Calculate the resources needed for the HP Service Manager server using the information provided in the HP Service Manager Interactive Installation Guide.

HP software product documentation and the HP Cloud Service Automation System and Software Support Matrix are available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Configure HP Service Manager

The following tasks are required to configure HP Service Manager to integrate successfully with HP CSA:

Step 1: Import the HP CSA Integration File into HP Service Manager

Importing the HP CSA integration file into HP Service Manager creates the OO_CSA and WSCentralServiceService script libraries and OnChangeApproval and OnChangeDenied macros.

  1. Log in to the HP Service Manager Windows client using the falcon account or another account with administrator privileges.
  2. From the System Navigator, click Connection > Tailoring > Database Manager or enter db in the command window and click RUN.
  3. Click Import/Load.
  4. Locate the HPSM_CSA_Integration_file.unl file installed with HP CSA.

    The default location of the file is %CSA_HOME%\CSAKit-4.1\Lib\service manager$CSA_HOME/CSAKit-4.1/Lib/service manager where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed (for example, C:\Program Files\Hewlett-Packard\CSA/usr/local/hp/csa).

    If HP CSA and HP Service Manager are installed on different systems, copy this file to the system running HP Service Manager.

  5. Click Load FG.

Step 2: Verify the Installation of the Script Library and Macros

  1. Log in to the HP Service Manager Windows client using the falcon account or another account with administrator privileges.
  2. Enter unload in the command window and click RUN. Verify that the HPSM CSA Integration file is listed.

  3. From the System Navigator, click Connection > Tailoring > Script Library.
  4. Verify that the OO_CSA script library exists. In the Name field, type OO_CSA, and click Find.
  5. Verify that the WSCentralServiceService script exists. In the Name field, type WSCentralServiceService, and click Find.
  6. Validate the credentials for the HP Operations Orchestration Central server. View the OO_CSA script and validate the values for centralUser and centralPassword. Edit the script and update these values if they are not set to the correct credentials. If you updated a value, click Save.
  7. Update the URL for the HP Operations Orchestration Central server. View the OO_CSA script and update the value for centralURL. Replace localhost with the hostname of the HP Operations Orchestration Central server. Click Save.
  8. From the System Navigator, click Connection > Tailoring > Tailoring Tools > Macros.
  9. Verify the OnChangeApproval and OnChangeDenied macros exist.

Step 3: Modify the Approval Definition

Update the sample Approval Definition provided with HP Service Manager to create a new subscription approval.

  1. Use the HP Service Manager unload tools to back up the sample Approval Definition.
  2. Log in to the HP Service Manager Windows client using the falcon account or another account with administrator privileges.
  3. From the System Navigator, click Connection > Change Management > Maintenance > Approvals.
  4. Search for the Subscription Approval. In the Name field, type Subscription Approval, and click Find.
  5. Verify or set the following fields and values:

    Field Name Value
    Name Subscription Approval
    Approval Condition true
    Approval Type All must approve
    Group/Oper Change.Approver
    Sequence 1
    Condition true
  6. Click Save.

Step 4: Enable SSL between HP Service Manager and HP Operations Orchestration

  1. Create a self-signed certificate using the fully-qualified domain name of the system on which HP Operations Orchestration is installed to replace the existing HP Operations Orchestration Central server certificate.

    Note: If the existing HP Operations Orchestration Central server certificate uses a CN with the fully-qualified domain name of the system on which HP Operations Orchestration is installed, you do not need to create a self-signed certificate. You can use the existing HP Operations Orchestration Central server certificate.

    Refer to Replacing the Central SSL/TLS Server Certificate with a Self-Signed Certificate section in the System Configuration and Hardening Guide (a copy of this guide can be found in %ICONCLUDE_HOME%\docs\Configuration and Hardening Guide.pdf or $ICONCLUDE_HOME/docs/ConfigurationandHardeningGuide.pdf).

  2. Export HP Operations Orchestration's SSL certificate. On the system on which HP Operations Orchestration is installed, open a command prompt and type the following:

    Windows

    cd "%ICONCLUDE_HOME%"

    .\java\bin\keytool -export -alias tomcat -file pas.crt -keystore .\Central\var\security\key.store -storepass changeit

    Linux

    cd $ICONCLUDE_HOME

    ./java/bin/keytool -export- -alias tomcat -file pas.crt -keystore ./Central/var/security/key.store -storepass changeit

    Windows

    cd "%ICONCLUDE_HOME%"

    .\jre1.6\bin\keytool.exe -exportcert -alias pas -file pas.crt -keystore .\Central\conf\rc_keystore -storepass bran507025

    Linux

    cd $ICONCLUDE_HOME

    ./jre1.6/bin/keytool.exe -exportcert -alias pas -file pas.crt -keystore ./Central/conf/rc_keystore -storepass bran507025

  3. Copy pas.crt to the system on which HP Service Manager is installed, to the <HPSM_install_directory>\Server\RUN\jre\lib\security (Windows) or <HPSM_install_directory>/Server/RUN/jre/lib/security (Linux) directory.
  4. On the system on which HP Service Manager is installed, import the HP Operations Orchestration certificate. Open a command prompt and type the following:

    Windows

    cd "<HPSM_install_directory>\Server\RUN\jre\lib\security"

    "<HPSM_install_directory>\Server\RUN\jre\bin\keytool.exe" -importcert -alias tomcatpas -file pas.crt -keystore cacerts -storepass changeit

    Linux

    cd <HPSM_install_directory>/Server/RUN/jre/lib/security

    <HPSM_install_directory>/Server/RUN/jre/bin/keytool.exe -importcert -alias tomcatpas -file pas.crt -keystore cacerts -storepass changeit

Step 5: Map opsware.comthe Fully-Qualified Domain to the IP of the system on which HP Operations Orchestration is installed

When HP Service Manager accesses HP Operations Orchestration as a client, the HP Operations Orchestration certificate uses a hardcoded key for the CN. On the system running HP Service Manager, this CN (opsware.comthe fully-qualified domain name (FQDN) of the system on which HP Operations Orchestration is installed) must be mapped to the IP address of the system on which HP Operations Orchestration Central server is installed. The following is an example of how to map the CN to the IP address:

  1. On the system running HP Service Manager, open C:\Windows\system32\drivers\etc\hosts (Windows) or /etc/hosts (Linux) in a text editor.

  2. Add the following to the file:

    <IP_address_of_HPOO_central_server>   <FQDN>opsware.com

    where <IP_address_of_HPOO_central_server> is the IP address of the system on which HP Operations Orchestration Central server is installed and <FQDN> is the fully-qualified domain name of the system on which HP Operations Orchestration Central server is installed.

  3. Save and close the file.

What's Next?

You have completed the initial installation and configuration of HP CSA and can begin familiarizing yourself with the capabilities of HP CSA.

Launch the Cloud Service Management Console (type the following URL in a supported Web browser: https://<csahostname>:8444/csa) and log in using the out-of-the-box user (admin) and password (cloud). Launch the default Marketplace Portal (type the following URL in a supported Web browser: https://<csahostname>:8444/mpp) and log in using the out-of-the-box user (consumer) and password (cloud).

To complete the configuration of HP CSA, refer to the following documents:

  • HP Cloud Service Automation Configuration Guide: The configuration guide describes the process for preparing LDAP for the Cloud Service Management Console and for consumer organizations, requesting software licenses, configuring SSL, customizing the Cloud Service Management Console, configuring HP CSA to be compliant with FIPS 140-2, and performing other HP CSA customizations. The configuration guide also describes the process of how to import the sample HP Operations Orchestration flows included with HP CSA.

  • Configuring an HP CSA Cluster for Server Failover: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using an Apache Web server as a proxy.

  • HP Cloud Service Automation Integration Pack: The integration pack guide describes the process for installing and configuring resource providers such as HP Matrix Operating Environment, VMware vCenter, HP SiteScope, HP Universal CMDB, and HP Server Automation. The integration pack guide specifies how to import the sample HP Operations Orchestration flows included with HP CSA as well as the sample resource offerings and service designs included with HP CSA that target these resource providers. The integration pack guide also includes additional documentation on each of the out-of-the-box resource offerings and service designs.
  • HP Cloud Service Automation Service Design Guide: The service design guide describes how to use HP CSA to create automated, on-demand cloud services. The guide covers key concepts and steps for HP CSA service design, including sequenced and topology design models, the role of the service design, design layouts and components, service lifecycles, and service options.

You have completed the initial installation and configuration of the Marketplace Portal and can begin familiarizing yourself with the capabilities of the Marketplace Portal.

Launch the default Marketplace Portal (type the following URL in a supported Web browser: https://<csahostname>:8444/mpp) and log in using the out-of-the-box user (consumer) and password (cloud).

For more information about the Marketplace Portal, refer to the online help.

Installation Overview

Based on your selections on the previous page, perform the following steps. It is recommended that you perform each step in the following order:

  1. Configure a group and user.
  2. Install and initially configure Oracle.
  3. Install and initially configure Microsoft SQL Server.
  4. Install and configure PostgreSQL.
  5. Install HP Operations Orchestration.
  6. Install HP Cloud Service Automation.
  7. Secure the Marketplace Portal.
  8. Configure HP Operations Orchestration.
  9. Install and configure resource providers. If your resource provider is not listed below, follow the manufacturer's recommendations to install it. Refer to the HP Cloud Service Automation Integration Guide for information on how to integrate these providers with HP Cloud Service Automation.
  10. What's next?
  1. Copy the HP CSA SSL certificate to the remote system.
  2. Configure a group and user.
  3. Install HP Cloud Service Automation.
  4. What's next?

This guide provides information for installing the HP Cloud Service Automation application. Successful implementation of the application requires knowledge of the integrated products, as well as the HP Cloud Service Automation solution. Information in this guide augments information provided in the integrated products documentation but is not intended to replace that documentation. Primary product documentation contains the most up-to-date information. Cross references are provided to those documents where appropriate.

For information about how these parts fit together, see the HP Cloud Service Automation Concepts Guide.

You should review the HP Cloud Service Automation System and Software Support Matrix for version requirements.

Both documents are available from the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Copy the HP CSA SSL Certificate

From the system on which HP CSA is installed, copy the HP CSA SSL certificate to the system on which the remote instance of the Marketplace Portal will be installed.

On the system on which HP CSA is installed, the HP CSA SSL certificate is located in %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\configuration\jboss.crt$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/configuration/jboss.crt. Copy this file to the system on which you are installing the remote instance of the Marketplace Portal. Remember the name and location to which you have copied this SSL certificate as you will be asked for this information when you install the remote instance of the Marketplace Portal.

This file is needed for SSL verification which, by default, is enabled for the Marketplace Portal.

Configure a Group and User for HP CSA

Configure a group and user for HP CSA:

  1. Log in to the system as the root user.
  2. Create a group called csagrp. Enter the following:

    groupadd csagrp

  3. Create a user called csauser and assign this user to the csagrp. Enter the following:

    useradd -g csagrp -m csauser (Ubuntu) or
    useradd -g csagrp -m csauser -s /bin/bash (RHEL)

  4. Assign a password to the csauser. Enter the following:

    passwd csauser

    When prompted, enter the password.

Install an Instance of the Marketplace Portal on a Remote System

This section describes how to install the Marketplace Portal on a remote system, a system that is not the same system on which the Cloud Service Management Console is installed. The remote system must meet the same system requirements for HP Cloud Service Automation. See the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

Note: In the following instructions, %CSA_HOME%$CSA_HOME is the directory in which the Marketplace Portal is installed.

Install HP Cloud Service Automation

Note: Installation log files are written to the %CSA_HOME%$CSA_HOME\_CSA_4_1_0_installation\Logs\ directory.

To install HP Cloud Service Automation (HP CSA), complete the following steps.

  1. Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
  2. Run the setup.exe installation file.

  3. On the Introduction screen, read the information and click Next.

  4. Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml file (you may need to show hidden files), make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  5. Select HP CSA and Marketplace Portal and click Next.

  6. Choose a location in which to install HP CSA and click Next (%CSA_HOME%$CSA_HOME is set to this location).

    The default location is C:\Program Files\Hewlett-Packard\CSA.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    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.

  7. Choose the JRE that will be used by HP CSA.

    In this documentation, the directory in which the JRE is installed will be referred to as <csa_jre>.

    For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

    OpenJDK JRE

    The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, click Open JRE and click Next.

    The default location in which the OpenJDK JRE is installed is C:\Program Files\Hewlett-Packard\CSA\openjre.

    Oracle JRE

    If you have installed a supported version of Oracle JRE to be used by HP CSA, click Oracle JRE, select the location in which you installed this JRE, and click Next.

    The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, click Choose and select the location in which you installed the JRE that will be used by HP CSA.

    Caution:

    The entire directory path cannot contain more than one dollar sign symbol ($). For example, C:\HP\C$A\Java and C:\HP\CSA\Java$ are valid paths. However C:\HP\C$A\Java$ and C:\HP\C$$A\Java are not valid paths.

  8. Select the type of database installed (Microsoft SQL Server)(Oracle)(PostgreSQL) and click Next.

    For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport). Click Choose to select the directory.

    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.

  9. Define the database instance on which the HP CSA database components should be installed or where the HP CSA database schema already exists. Enter the following database information and click Next.

    Field Name Description
    Database Host The hostname or IP address of the server where the database is located. When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4] or [::1].
    Database Port The database port number, such as 1433 (Microsoft SQL Server).1521 (Oracle).5432 (PostgreSQL).

    Database NameOracle SID

    The name of the database instance on which the HP CSA database schema will be installed. If you are creating a new HP CSA database schema, this is the name of the database instance on which the HP CSA database components will be installed. If you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version HP 4.10, this is the name of the database instance on which the HP CSA database schema exists. For an Oracle database, this is the System ID (SID).
    Database Username The username of the database user you configured for HP CSA after installing the database.
    Database Password The password for the database user.

    If you created a reporting database role and read-only userreporting database user when you configured the database, select the Reporting User checkbox and enter the following information:

    Field Name Description
    CSA Reporting Database Username The username of the database user you configured for reporting purposes for HP CSA after installing the database.
    CSA Reporting Database Password The password for the CSA reporting database user.
  10. Install HP CSA database components onto the database instance to create the HP CSA database schema, if it does not exist.

    Click Yes to install HP CSA database components and create the HP CSA database schema. When you select this option, the HP CSA service automatically starts when you exit the installer.

    Click No if you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version 4.10. When you select this option, the HP CSA service does not start when you exit the installer. Refer to the end of this section for information on how to start and stop the HP CSA service.

  11. From the Enter host name screen, enter the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.

    Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.

  12. By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.

    If you do not want to use HPSSO, you can disable it.

    You MUST disable HP Single Sign-On if you are installing HP CSA in a FIPS 140-2 compliant environment.

    If enabled, enter the domain name of the network to which the server on which you are installing HP CSA belongs and click Next.

    Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.

    Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.

  13. Review your selections and click Install to complete the installation.

  14. 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.

  15. Click Done to exit the installer.

  16. Verify that the HP Cloud Service Automation and Marketplace Portal services have started by navigating to Control Panel > Administrative Tools > Services. It can take up to five minutes for the HP Cloud Service Automation to start. If one or both services have not started, right-click on the service and select Start.

    The installer creates the HP Cloud Service Automation and Marketplace Portal services. If you opted to install the HP Cloud Service Automation database components, the installer starts these services. The HP Cloud Service Automation service must be running in order to access the Cloud Service Management Console and the Marketplace Portal service must be running in order to access the Marketplace Portal.

To start, stop, and restart the HP Cloud Service Automation and Marketplace Portal services, navigate to Control Panel > Administrative Tools > Services, right-click on a service, and select the desired action.

Note: Installation log files are written to the %CSA_HOME%$CSA_HOME/_CSA_4_1_0_installation/Logs/ directory and are named csa_*.txt.

To install HP Cloud Service Automation (HP CSA), complete the following steps.

  1. Log in to the system as the root user.
  2. Install the unzip utility if it is not already installed. Enter the following:

    apt-get install unzip

  3. Create an installation directory for HP CSA (this document assumes that you will install the product in /usr/local/hp/csa and all examples used in this document are based on this assumption). Enter the following:

    mkdir -p /usr/local/hp/csa

  4. 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

  5. Log out as the root user and log in as csauser.
  6. Copy the HP CSA installation file (setup.bin) to the system and go to the directory in which it has been copied.
  7. Verify that setup.bin is owned by csauser and csauser has full permissions to the file. If necessary, do the following:

    1. Log in as the root user
    2. Enter one or both of the following commands:

      chown csauser setup.bin
      chmod u+rwx setup.bin

    3. Log out as the root user and log in as csauser.
  8. 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.

  9. Run the setup.bin installation file (as the csauser).

    Note: You must run setup.bin as the csauser. If you install HP CSA as another user, you may not be able to run HP CSA.

    As the csauser, enter the following:

    ./setup.bin

  10. Read the Introduction and click enter to continue with the installation.

  11. Read the license agreement. Click enter to scroll through the entire agreement.
  12. Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml file, make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  13. Verify that no HP CSA services are running on the system. Open a command prompt and type ps -ef | grep csa. If the csa process is running, kill it.

    After verifying that no HP CSA services are running on the system, close the command prompt.

    Select enter to continue the installation.

  14. Select the application to install and click Enter.

    HP CSA and Marketplace Portal

    Installs the entire HP CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.

    Marketplace Portal

    Installs only the Marketplace Portal on the system.

  15. Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.

    The default location is /usr/local/hp/csa.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.

  16. Choose the JRE that will be used by HP CSA.

    In this documentation, the directory in which the JRE is installed will be referred to as $CSA_JRE_HOME.

    For a list of supported JREs, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

    OpenJDK JRE

    The OpenJDK JRE is bundled with HP CSA. If you want to use the OpenJDK JRE, type 1 and select Enter.

    The default location in which the OpenJDK JRE is installed is /usr/local/hp/csa/openjre.

    Oracle JRE

    If you have installed a supported version of Oracle JRE to be used by HP CSA, type 2 and select Enter. Type the location in which you installed this JRE and select Enter.

    The default location displayed for the Oracle JRE Home is either a supported JRE that is configured in the system registry or a supported JRE in a path that is defined in the system path variable. If this is not the JRE that should be used by HP CSA, type in the location in which you installed the JRE that will be used by HP CSA and select Enter.

  17. Define the database instance on which the HP CSA database components should be installed. Enter the following database information (select Enter after each entry).

    1. Enter the type of database you have installed: MSSql (Microsoft SQL Server)OraclePostgres (PostgreSQL).

      For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the HP CSA system). For a list of supported JDBC driver versions, refer to the HP Cloud Service Automation System and Software Support Matrix, available on the HP Software Support Web site at http://h20230.www2.hp.com/selfsolve/manuals/ (this site requires that you register with HP Passport).

    2. Enter the database hostname. This is 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]. The default value is the IP address of the localhost (127.0.0.1).
    3. Enter the database port. This is the database port number, such as 1433 (Microsoft SQL Server)1521 (Oracle)5432 (PostgreSQL).

    4. Enter the database name. This is the name of the database instance on which the HP CSA database schema will be installed. If you are creating a new HP CSA database schema, this is the name of the database instance on which the HP CSA database components will be installed. If you are using an existing HP CSA database schema that was created as part of a prior successful installation of HP CSA version HP 4.10, this is the name of the database instance on which the HP CSA database schema already exists.

      If you followed the examples in this document, enter csadb.

    5. Enter the CSA database user name. This is the user name of the database user you configured for HP Cloud Service Automation after installing the database.

      If you followed the examples in this document, enter csadbuser.

    6. Enter the CSA database password. This is the password for the CSA database user.
    7. Enter the CSA reporting database username (optional). This is the username of the database user you configured for reporting purposes for HP CSA after installing the database.

      If you followed the examples in this document, enter csareportingdbuser.

    8. Enter the CSA reporting database password. This is the password for the CSA reporting database user.
  18. Enter the HP CSA server hostname. This is the fully-qualified domain name of the system on which you are installing HP CSA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for the Cloud Service Management Console. Marketplace Portal. This self-signed certificate expires 120 days after HP CSA is installed.

    Caution: If you enter an IP address, after installation completes, you must manually generate a self-signed certificate using the fully-qualified domain name of the system on which you installed HP CSA and manually reconfigure HP CSA and the Marketplace Portal to use this certificate. For more information, refer to the HP Cloud Service Automation Configuration Guide.

  19. By default, HP Single Sign-On (HPSSO) is included with HP CSA and is enabled. The HPSSO that is included with HP CSA can only be used when launching an application, such as HP Operations Orchestration or HP IT Executive Scorecard, from the Cloud Service Management Console. Refer to the HP Cloud Service Automation Configuration Guide and HPSSO documentation for more information on integrating HPSSO with an application.

    If you do not want to use HPSSO, you can disable it. Type 2 and select Enter.

    To enable HPSSO, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing HP CSA) and select Enter.

    Note: You must enter the full domain name of the server. For example, if you are installing HP CSA on a system whose fully-qualified domain name is machine1.marketing.xyz.com, you must enter marketing.xyz.com. If you enter only xyz.com, you will not be able to log in to the Cloud Service Management Console.

    Applications launched from the Cloud Service Management Console with which you want to use HPSSO must be installed on systems that belong to this domain.

  20. Review your selections and select Enter to complete the installation or Ctrl-c to exit the installation.

  21. When the installation completes, select enter to exit the installer.

  22. Define the CSA_HOME and JAVA_HOME environment variables and add /sbin to the PATH variable for the csauser user. Set CSA_HOME to the location where HP CSA is installed. In a startup script for the csauser user (for example, .profile (Ubuntu) or .bash_profile (Red Hat Enterprise Linux)), add the following:

    export CSA_HOME=/usr/local/hp/csa
    export JAVA_HOME=<csa_jre>$CSA_JRE_HOME
    export PATH=$PATH:/sbin

    where <csa_jre> $CSA_JRE_HOME is the directory in which the JRE that is used by HP CSA is installed.
  23. Source the startup file in which you set the CSA_HOME, JAVA_HOME, and PATH environment variables. If you edited .bashrc (Ubuntu) or .bash_profile (Red Hat Enterprise Linux), enter the following:

    . ./.bashrc (Ubuntu)
    . ./.bash_profile (Red Hat Enterprise Linux)

  24. Create an HP CSA service and a Marketplace Portal service to start and stop the HP CSA and Marketplace Portal processes.

    1. Log in as the root user.
    2. Go to the directory in which HP CSA is installed. For example:

      cd /usr/local/hp/csa

    3. 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

    4. Change permissions of the scripts. Enter the following:

      chmod 755 /etc/init.d/csa
      chmod 755 /etc/init.d/mpp

    5. Log out as the root user.
  25. Log in as csauser and start the HP CSA and Marketplace Portal services. Enter the following:

    service csa start
    service mpp start

The HP Cloud Service Automation service must be running in order to access the Cloud Service Management Console. You can start this service by typing service csa start. You can restart this service by typing service csa restart. You can stop the service by typing service csa stop. You can check the status of the service by typing service csa status.

The Marketplace Portal service must be running in order to access the Marketplace Portal. You can start this service by typing service mpp start. You can restart this service by typing service mpp restart. You can stop the service by typing service mpp stop. You can check the status of the service by typing service mpp status.

Note: Installation log files are written to the %CSA_HOME%$CSA_HOME\_CSA_4_1_0_installation\Logs\ directory.

To install a remote instance of the Marketplace Portal, complete the following steps.

  1. Close all instances of Windows Explorer and command prompts and exit all programs that are running on the system.
  2. Run the setup.exe installation file.

  3. On the Introduction screen, read the information and click Next.

  4. Read the license agreement and select I accept the terms of the License Agreement. Click Next to continue with the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory %CSA_HOME% does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the C:\Program Files\Zero G Registry\.com.zerog.registry.xml file (you may need to show hidden files), make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  5. Select Marketplace Portal and click Next.

  6. Choose a location in which to install the Marketplace Portal and click Next (%CSA_HOME%$CSA_HOME is set to this location).

    The default location is C:\Program Files\Hewlett-Packard\CSA.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    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.

  7. Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.

    Field Name Description
    HP CSA Host The fully-qualified domain name of the system on which HP CSA is installed.
    HP CSA Port The port number used to communicate with HP CSA.
    HP CSA Certificate The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system.
  8. 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.

  9. Click Done to exit the installer.

  10. 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_HOME/_CSA_4_1_0_installation/Logs/ directory and are named csa_*.txt.

To install HP Cloud Service Automation (HP CSA), complete the following steps.

  1. Log in to the system as the root user.
  2. Install the unzip utility if it is not already installed. Enter the following:

    apt-get install unzip

  3. Create an installation directory for HP CSA (this document assumes that you will install the product in /usr/local/hp/csa and all examples used in this document are based on this assumption). Enter the following:

    mkdir -p /usr/local/hp/csa

  4. 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

  5. Log out as the root user and log in as csauser.
  6. Copy the HP CSA installation file (setup.bin) to the system and go to the directory in which it has been copied.
  7. Verify that setup.bin is owned by csauser and csauser has full permissions to the file. If necessary, do the following:

    1. Log in as the root user
    2. Enter the following commands:

      chown csauser setup.bin
      chmod u+rwx setup.bin

    3. Log out as the root user and log in as csauser.
  8. Run the setup.bin installation file (as the csauser).

    Note: You must run setup.bin as the csauser. If you install HP CSA as another user, you may not be able to run HP CSA.

    As the csauser, enter the following:

    ./setup.bin

  9. Read the Introduction and click enter to continue with the installation.

  10. Read the license agreement. Click enter to scroll through the entire agreement.
  11. Select Y and enter to accept the license agreement and continue with the installation. Select N and enter to exit the installation.

    If the following error message displays:

    Another version of HP CSA is configured in the registry. However, HP CSA has been uninstalled (the HP CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing HP CSA. Refer to the HP Cloud Service Automation Installation Guide for more information about deleting the registry entry.

    exit the installer. Locate the $CSA_HOME/.com.zerog.registry.xml file, make a backup copy, delete all HP CSA entries from the .com.zerog.registry.xml file, and restart the installer.

  12. Enter a location in which to install HP CSA (enter the absolute path to the location) and select enter. Or, select enter to accept the default location.

    The default location is /usr/local/hp/csa.

    Note: If the directory in which you choose to install HP CSA is not empty, existing content in the directory may be overwritten or deleted when HP CSA is installed, upgraded, or uninstalled.

    If prompted, verify the installation folder. If the folder is correct, select Y and enter to continue with the installation. If the folder is not correct, select N and enter to re-enter the installation folder.

  13. Define the instance on which the HP CSA is installed and the location of the HP CSA SSL certificate that was copied to the local system. Enter the following information and click Next.

    Field Name Description
    HP CSA Host The fully-qualified domain name of the system on which HP CSA is installed.
    HP CSA Port The port number used to communicate with HP CSA.
    HP CSA Certificate The name and location of the HP CSA SSL certificate file that was copied from the HP CSA system to the local system.
  14. 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.

  15. Review your selections and select enter to complete the installation or ctrl-c to exit the installation.

  16. When the installation completes, select enter to exit the installer.

  17. 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

  18. 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)

  19. Create the Marketplace Portal service to start and stop the Marketplace Portal process.

    1. Log in as the root user.
    2. Go to the directory in which the Marketplace Portal is installed. For example:

      cd /usr/local/hp/csa

    3. Copy the mpp script to the /etc/init.d directory. Enter the following:

      cp ./scripts/mpp /etc/init.d

    4. Change permissions of the script. Enter the following:

      chmod 755 /etc/init.d/mpp

    5. Log out as the root user.
  20. Log in as csauser and start the Marketplace Portal service. Enter the following:

    service mpp start

The Marketplace Portal service must be running in order to access the Marketplace Portal. You can start this service by typing service mpp start. You can restart this service by typing service mpp restart. You can stop the service by typing service mpp stop. You can check the status of the service by typing service mpp status.

Secure the Marketplace Portal

For security reasons, the Marketplace Portal file system must be protected by the operating system. Do the following:

  1. Open an elevated command prompt (a command prompt that is run as the administrator). For example, navigate to All Programs > Accessories. Right-click on Command Prompt and select Run as administrator.
  2. From the elevated command prompt, run the following command:

    attrib +s +h "%CSA_HOME%\portal" /S /D /L

    where %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed.

  3. Restart the HP Cloud Service Automation and Marketplace Portal services. For example, navigate to Control Panel > Administrative Tools > Services. Right-click on the service and select Restart.
  1. Log in as the root user.
  2. Run the following commands:

    chown –R csauser:csagrp $CSA_HOME/portal
    chmod –R 700 $CSA_HOME/portal

    where csauser and csagrp are the user and group you configured for HP CSA when you installed HP CSA and %CSA_HOME%$CSA_HOME is the directory in which HP Cloud Service Automation is installed.

  3. Log out as root and log in as csauser.
  4. Restart the csa and mpp services by running the following commands:

    service csa restart
    service mpp restart

Update the Marketplace Portal in the Cloud Service Management Console

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:

  1. On the system on which HP CSA and the Cloud Service Management Console are installed, edit the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\csa.war\WEB-INF\classes\csa.properties$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/csa.war/WEB-INF/classes/csa.properties file.
  2. Update the 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.
  3. Save and exit the file.
  4. Restart HP CSA.

    To restart HP CSA:

    1. On the server that hosts HP CSA, navigate to Control Panel > Administrative Tools > Services.

    2. Right-click on the HP Cloud Service Automation service and select Restart.

    3. Right-click on the HP Marketplace Portal service and select Restart.

    To restart HP CSA, on the server that hosts HP CSA, type the following:

    service csa restart
    service mpp restart

Launch the Marketplace Portal

Launch the default remote instance of a Marketplace Portal

Launch the default remote instance of the Marketplace Portal by typing one of the following URLs in a supported Web browser:

  • https://<csahostname>:8444/mpp
  • https://<mpphostname>:8089

where:

  • <csahostname> is the fully-qualified domain name of the system on which HP CSA is installed and the URL in the %CSA_HOME%\jboss‑as‑7.1.1.Final\standalone\deployments\mpp.war\index.html$CSA_HOME/jboss‑as‑7.1.1.Final/standalone/deployments/mpp.war/index.html file (on the system on which HP CSA is installed) has been updated to https://<mpphostname>:8089.

  • <mpphostname> is the fully-qualified domain name of the system on which the Marketplace Portal instance resides.

Examples:

  • https://csa_system.abc.com:8444/mpp
  • https://mpp_system.abc.com:8089

The organization associated with the default Marketplace Portal is defined in the %CSA_HOME%\portal\conf\mpp.json$CSA_HOME/portal/conf/mpp.json file (on the system on which the Marketplace Portal instance resides). By default, this is the sample organization that is installed with HP CSA (CSA_CONSUMER). To modify the organization associated with the default Marketplace Portal, modify the defaultOrganizationName property value by setting it to the <organization_identifier> of the desired organization, where <organization_identifier> is the unique name that HP Cloud Service Automation assigns to the organization, based on the organization display name (the organization identifier can be found in the General Information section of the Organizations tile of the Cloud Service Management Console).

Launch an organization-specific remote instance of a Marketplace Portal

Launch an organization's remote instance of the Marketplace Portal by typing the following URL in a supported Web browser:

https://<mpphostname>:8089/org/<organization_identifier>

where:

  • <mpphostname> is the fully-qualified domain name of the system on which the Marketplace Portal instance resides.
  • <organization_identifier> is the unique name that HP Cloud Service Automation assigns to the organization, based on the organization display name (the organization identifier can be found in the General Information section of the Organizations tile of the Cloud Service Management Console)

Example:

https://mpp_system.xyz.com:8089/org/ORGANIZATION_A

Caution: Do not launch more than one organization-specific Marketplace Portal from the same browser session. For example, if you launch ORGANIZATION_A's Marketplace Portal in a browser, do not open a tab or another window from that browser and launch ORGANIZATION_B's Marketplace Portal. Otherwise, the user who has logged in to the Marketplace Portal launched for ORGANIZATION_A will start to see data for ORGANIZATION_B.

Instead, start a new browser session to launch another organization's Marketplace Portal.

Start, Stop, or Restart the Marketplace Portal Service on the Remote System

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:

  1. Navigate to the Services screen (Control Panel > Administrative Tools > Services).
  2. Right-click on the Marketplace Portal service and select Start.

To stop the Marketplace Portal service, do the following:

  1. Navigate to the Services screen (Control Panel > Administrative Tools > Services).
  2. Right-click on the Marketplace Portal service and select Stop.

To restart the Marketplace Portal service, do the following:

  1. Navigate to the Services screen (Control Panel > Administrative Tools > Services).
  2. Right-click on the Marketplace Portal service and select Restart.

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.

What's Next?

You have completed the initial installation and configuration of HP CSA and can begin familiarizing yourself with the capabilities of HP CSA.

Launch the Cloud Service Management Console (type the following URL in a supported Web browser: https://<csahostname>:8444/csa) and log in using the out-of-the-box user (admin) and password (cloud). Launch the default Marketplace Portal (type the following URL in a supported Web browser: https://<csahostname>:8444/mpp) and log in using the out-of-the-box user (consumer) and password (cloud).

To complete the configuration of HP CSA, refer to the following documents:

  • HP Cloud Service Automation Configuration Guide: The configuration guide describes the process for preparing LDAP for the Cloud Service Management Console and for consumer organizations, requesting software licenses, configuring SSL, customizing the Cloud Service Management Console, configuring HP CSA to be compliant with FIPS 140-2, and performing other HP CSA customizations. The configuration guide also describes the process of how to import the sample HP Operations Orchestration flows included with HP CSA.

  • Configuring an HP CSA Cluster for Server Failover: The cluster configuration guide describes how to configure the nodes in your clustered environment if you are using an Apache Web server as a proxy.

  • HP Cloud Service Automation Integration Pack: The integration pack guide describes the process for installing and configuring resource providers such as HP Matrix Operating Environment, VMware vCenter, HP SiteScope, HP Universal CMDB, and HP Server Automation. The integration pack guide specifies how to import the sample HP Operations Orchestration flows included with HP CSA as well as the sample resource offerings and service designs included with HP CSA that target these resource providers. The integration pack guide also includes additional documentation on each of the out-of-the-box resource offerings and service designs.
  • HP Cloud Service Automation Service Design Guide: The service design guide describes how to use HP CSA to create automated, on-demand cloud services. The guide covers key concepts and steps for HP CSA service design, including sequenced and topology design models, the role of the service design, design layouts and components, service lifecycles, and service options.

You have completed the initial installation and configuration of the Marketplace Portal and can begin familiarizing yourself with the capabilities of the Marketplace Portal.

Launch the default Marketplace Portal (type the following URL in a supported Web browser: https://<csahostname>:8444/mpp) and log in using the out-of-the-box user (consumer) and password (cloud).

For more information about the Marketplace Portal, refer to the online help.

© Copyright 2010-2014 Hewlett-Packard Development Company, L.P.