Install Cloud Service Automation for Linux

To install CSA, complete the following steps.

1. Log on to the system as the root user.

2. Run the following command to install the unzip utility, assuming it is not already installed:

   apt-get install unzip

3. Enter the following command to create an installation directory for CSA :
   mkdir -p /usr/local/hpe/csa

   Note This section assumes that you install the product in the /usr/local/hpe/csa directory. All of the examples shown in this document use this path and directory.

4. For the installation directory, run the following command to set the owner to csauser and the group to csagrp:

   chown -R csauser:csagrp /usr/local/hpe/csa

5. Log off as the root user and log on as the csauser.
6. Copy the 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 that csauser has full permissions to the file. If necessary, do the following:

   1. Log on as the root user

   2. Enter one or both of the following commands:

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

   3. Log off as the root user and log on as the 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 causes the installer to fail. Either set the variable to a value that does not contain an escape sequence or change the variable so that is it not set.

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

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

10. Read the Introduction. 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 you see an error similar to the following message, complete the steps show beneath this message:

    Another version of CSA is configured in the registry. However, CSA has been uninstalled (the CSA installation directory $CSA_HOME does not exist). You must exit the installer and delete the entry in the registry before installing CSA.

    1. Exit the installer.
    2. Locate the $HOME/.com.zerog.registry.xml file (for example, /home/csauser/.com.zerog.registry.xml)
    3. Make a backup copy of the .com.zerog.registry.xml file.
    4. Delete all of the CSA entries from the .com.zerog.registry.xml file.
    5. Run the setup.bin installation file as the csauser and follow the interactive instructions as shown in the previous steps.

13. Select CSA and Marketplace Portal, then click Enter.

    Note Selecting CSA and Marketplace Portal installs the entire CSA application, including the Cloud Service Management Console, Identity Management component, and Marketplace Portal, on the system.

    Selecting Marketplace Portal installs only the Marketplace Portal on the system.

14. Accept the default location or enter the absolute path to a location in which to install CSA, then select Enter.

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

15. Do one of the following to select the JRE that will be used by CSA:

    • If you want to use the OpenJDK JRE, which is is bundled with CSAenter 1.

    • If you have installed a supported version of Oracle JRE to be used by CSA, enter 2, then enter the location in which you installed this JRE.

    Note In this instruction set, the directory in which the JRE is installed is referred to as $CSA_JRE_HOME. For a list of supported JREs, see the Cloud Service Automation System and Software Support Matrix.

16. Complete only one of the following options to install the CSA database components on the database instance and create the CSA database schema, if it does not already exist.

    Note In this version of CSA, Organizations are now stored in the Identity Management component, not in CSA. If you selected Yes during the installation, the CSA installer will populate the database and migrate the organizations automatically; however, if you selected No during the installation, you will need to populate the database and migrate organizations manually using CSA tools.

    • Options 1: Type Yes to install CSA database components and create the CSA database schema. When you select this option, the CSA process automatically starts when you exit the installer.

    • Option 2: Type No and complete the following steps if you are using an existing HPECSA database schema that was created as part of a prior successful installation of CSA version 4.80.0002. When you select this option, you cannot use the installer to deploy sample content and the CSA process does not start when you exit the installer.

      Do the following if you need to import content into the database and your organizations into the Identity Management component for CSA:

      1. Run the SchemaInstallationTool to populate the database.

         1. Go to <CSA_HOME>/Tools/SchemaInstallationTool/
         2. Run <JAVA_HOME>/bin/java –jar schema-installation-tool.jar

      2. Run the OrgMigrationTool to migrate organizations from CSA to the Identity Management component.

         1. Go to <CSA_HOME>/Tools/OrgMigrationTool/
         2. Run <JAVA_HOME>/bin/java –jar org-migration-tool.jar –c config.properties –csa.home <CSA_HOME> -t json –j <JDBC_DRIVER>

    See Restarting the CSA Service: for information about how to start and stop the CSA service.

17. Define the database instance on which the 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, Oracle, or PostgreSQL.

       Note For an Oracle database, you must also enter the JDBC Driver Directory. This is the absolute directory path to the location of the JDBC drivers (these are the JDBC drivers you downloaded onto the CSA system). For a list of supported JDBC driver versions, see the Cloud Service Automation System and Software Support Matrix.

       Guides are available on the HPE Software Support web site at: https://softwaresupport.hpe.com (this site requires a Passport ID). Select Dashboards > Manuals.

    2. Enter the database host name. This is the host name or IP address of the server on which the database is located.

       Note 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. For example, 1433: (Microsoft SQL Server), 1521: (Oracle), 5432: (PostgreSQL).

    4. Enter the Oracle service name or database name. This is the service or global database name of the database instance on which the CSA database schema will be installed.

       Note If you are creating a new CSA database schema, enter the service or database name of the database instance on which the CSA database components will be installed.

       If you are using an existing CSA database schema that was created as part of a prior successful installation of CSA version HPE 4.80.0002, enter the service or database name of the database instance on which the 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 HPE Cloud Service Automation in the Configure (Oracle / Microsoft SQL Server / PostgreSQL) section.
       

       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 user name (optional). This is the user name of the database user you configured for reporting purposes for CSA in the Configure (Oracle / Microsoft SQL Server / PostgreSQL) section.
       
       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. Provide the database instance used by the Identity Management component. Enter the following database information (select Enter after each entry).

    1. Enter the database host name. This is the host name or IP address of the server on which the database is located.

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

    2. Enter the database port. This is the database port number. For example, 1433: (Microsoft SQL Server), 1521: (Oracle), 5432: (PostgreSQL).

    3. Enter the Oracle service or database name. This is the service or global database name of the database instance used by the Identity Management component.
       

       Note If you followed the examples in this document, enter csaidmdb.

    4. Enter the Identity Management component database user name. This is the user name of the database user you configured for the Identity Management component database in the Configure (Oracle / Microsoft SQL Server / PostgreSQL) section.

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

    5. Enter the CSA database password. This is the password for the Identity Management component database user.

19. Enter the CSA server host name. This entry is the fully-qualified domain name of the system on which you are installing CSA.

    Note This host name is used to generate the self-signed certificate and configure CSA, the Marketplace Portal, and the Identity Management component.

    The self-signed certificate is used when https browser requests are issued for the Cloud Service Management Console and Marketplace Portal. This self-signed certificate expires 120 days after CSA is installed.

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

20. Do one of the following to integrate with an external (existing) instance of Operations Orchestration or to install the embedded (new) Operations Orchestration instance with CSA.

    • External OO: to integrate with an external (existing) instance of Operations Orchestration, complete the following steps:

      1. Select Use external OO.
      2. Click Next.
      3. Select Enter.

      Note If you are using an unsupported version of Operations Orchestration, you will get a warning message. If you continue with the installation, you may get provisioning errors. Using an unsupported version of Operations Orchestration could result in a limited amount of demo content that users can select for installation.

      Stop the current installation and do the following:

      1. Check the System and Software Support Matrix document for the supported Operations Orchestration versions.

      2. Install or upgrade to a supported Operations Orchestration version.

      3. Restart the CSA installation.

    • Embedded OO: To install the embedded (new) Operations Orchestration instance, complete the following steps:

      1. Select Install embedded OO.

      2. Click Next.

      3. Select Enter to install the embedded Operations Orchestration.

    After you successfully complete one of the above options, select the CSA content you would like to import (either CSA or Codar) to continue.

21. Define the Operations Orchestration instance with which CSA is to be integrated. Enter the following information (select Enter after each entry).

    1. Enter the OO host name. This host name is referred to as the This is the fully-qualified domain name or IP address of the server on which Operations Orchestration is located. Specify the host name that was used to generate Operations Orchestration's certificate. The host name is used for TLS validation and to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Cloud Service Management Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured).
       
       When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4] or [::1].
    2. Enter the OO port. This port is the port number used to communicate with Operations Orchestration, such as 8443. The port number is used to build the URL that the Cloud Service Management Console uses to interact with Operations Orchestration. By default, Operations Orchestration uses this port and port 8080. Applications running on the system on which Operations Orchestration is installed should not be using these ports.

    3. Enter the OO user. This user is the name of the user who logs on to Operations Orchestration Central. You should use the admin user. If you followed all the steps documented in the Install Operations Orchestration section, this is the admin user.

    4. Enter the OO password. This password is the password used by the OO user to log on to Operations Orchestration Central. If you followed all the steps documented in the Install Operations Orchestration section of this guide, use the password cloud.

    5. Re-enter the OO password.

    6. Enter the OO certificate file. This file is the file name and location of Operations Orchestration's certificate from Operations Orchestration's truststore on the CSA system. If you have not already done so, export Operations Orchestration's certificate and copy it to the CSA system. See the Install Operations Orchestration section in the Installation Guide or the Initial Setup section in the Upgrade Guide for more information).

    This information is used to set the Operations Orchestration properties in the csa.properties file and import Operations Orchestration's certificate into CSA's truststore. See the Configuration Overview for more information about these properties.

22. Enter a location in which to install the embedded Operations Orchestration.

23. Enter the database information for the database used by the embedded Operations Orchestration (select Enter after each entry). The database used by the embedded Operations Orchestration must be the same type of database used by CSA (Oracle / Microsoft SQL Server / PostgreSQL).

    1. Enter the database host name. This is the host name or IP address of the server where the embedded Operations Orchestration database is located.
    2. Enter the database port. This is the embedded Operations Orchestration database port number. For example, 1433: (Microsoft SQL Server), 1521: (Oracle), 5432: (PostgreSQL).
    3. Enter the  OO database or Oracle OO service name. This is the name of the database instance used by the embedded Operations Orchestration.
       
       If you followed the examples in this document, enter csaoodb.
    4. Enter the database username. This is the username of the database user you configured for the Operations Orchestration database.
       
       If you followed the examples in this document, enter csaoodbuser.
    5. Enter the database password. This is the password for the Operations Orchestration database user.
    6. Enter the embedded Operations Orchestration port number, such as 8445. By default, Operations Orchestration uses this port and port 8080. The embedded Operations Orchestration should not use the same port as other applications running on the system.

24. Configure an internal Operations Orchestration user (select Enter after each entry). This user is used for provisioning topology designs.

    1. Enter the OO username. This is the name of the user used for provisioning topology designs. This user is given the ADMINISTRATOR and SYSTEM_ADMIN roles. The recommended username is admin.
    2. Enter the OO password. This is the password used by Operations Orchestration for the user who provisions topology designs. The recommended password is cloud.

25. On the Workflow Designer screen, configure a Workflow Designer component. Depending on whether you wish to add a new database or reuse an existing one, select one of the following options, and click Next.

    • Option 1: No. I will provide new database information.

    • Option 2: Yes. Reuse configuration files from an existing node.

      Enter a comma separated list of number for selecting the required choice OR select the default.

      If this is standalone installation or first installation of clustered instance just hit Enter to choose default option which is option 1.

      In case of clustered installation choose option 2.

26. Based on the option you selected in the previous step, do one of the following:

    • If you chose to provide new database information, specify the following details:

    Field Name	Description
    Database Host: MSSQL, Oracle, or PostgreSQL	The hostname or IP address of the server where the database is located.
    Database Port: MSSQL, Oracle, or PostgreSQL	The database port number. For example, 1433: (Microsoft SQL Server), 1521: (Oracle), 5432: (PostgreSQL).
    Workflow Designer Database Name/ Oracle service name	The name of the database instance on which the CSA database schema will be installed. If you are creating a new CSA database schema, this is the name of the database instance on which the CSA database components will be installed. If you are using an existing CSA database schema that was created as part of a prior successful installation of CSA version 4.80, this is the name of the database instance on which the CSA database schema exists. For an Oracle database, this is the System ID (SID). NOTE The database used by the embedded Workflow Designer must be the same type of database used by CSA (Oracle / Microsoft SQL Server / PostgreSQL) . Default: ooddb
    Workflow Designer Database User Name	The user name of the database user you configured for the Workflow Designer database in the Configure (Oracle / Microsoft SQL Server / PostgreSQL) section (for example, csadbuser). Default: oouser
    Workflow Designer Database Password	The password for the database user.

    • If you chose to provide configuration files from an existing node, select the respective properties files available in an existing Workflow Designer to reuse the configuration values for the new installation by clicking the Choose button and navigating to the respective location of the properties file.

    Following are the parameters representing configuration files on machine with finished installation:

    CSA_HOME/workflow-designer/designer/conf/database.properties

    CSA_HOME/workflow-designer/designer/var/security/secured.properties

    CSA_HOME/workflow-designer/designer/var/security/encryption.properties

    CSA_HOME/workflow-designer/designer/var/security/encryption_repository

    where CSA_HOME is the directory in which CSA is installed.

27. Enter the Workflow Designer Port number click Next. The default port number is 8446.
    

28. Verify the default endpoint details and click Next.

    You can change the endpoint details by clicking Use a specific endpoint to connect to Workflow Designer, and providing the required details.

    NOTE: By default, there is no need to specify the Workflow Designer component endpoint as it is running on the same machine as HPE Cloud Service Automation. However, in case of a cluster installation, it is possible to connect to the component using a virtual IP (load balancer).

29. By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with CSA. You can choose to deploy this content during installation (making the sample service designs available in the Design area of the Cloud Service Management Console) or deploy the content at a later time (see the CSA/Codar Content at a Glance Guide for more information).

    To deploy the sample content during the CSA installation process, type 1 (Install additional provider integration service designs, components and content) and select Enter.

    To deploy the sample content at a later time, type 2 (Skip content installation) and select Enter.

    If you choose to skip content installation, you can install the content at a later time by running the Cloud Content Capsule Installer. See the CSA/Codar Content at a Glance Guide or Cloud Service Automation Configuration Guide for more information.

    Note If you chose not to install the database components, this selection will not display.

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

31. When the installation completes, select Enter to exit the installer.

32. Define the CSA_HOME and JAVA_HOME environment variables for the csauser user. Set CSA_HOME to the location where CSA is installed. In a startup script for the csauser user (for example, .bash_profile (Red Hat Enterprise Linux)), add the following:

    export CSA_HOME=/usr/local/hpe/csa
export JAVA_HOME=<csa_jre>$CSA_JRE_HOME

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

33. 
    . ./.bash_profile (Red Hat Enterprise Linux)

34. Create an CSA service and HPE Marketplace Portal service to start and stop the CSA and Marketplace Portal processes.

    1. Log on as the root user.

    2. Go to the directory in which CSA is installed. For example:

       cd /usr/local/hpe/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 off as the root user.

35. Log on as the csauser and start the CSA and HPE Marketplace Portal services. Enter the following:

    service csa start
service mpp start

36. As csauser, restart the HPE Operations Orchestration Central service. Enter the following:

    /usr/local/hpe/csa/OO/central/bin/central stop
/usr/local/hpe/csa/OO/central/bin/central start

Restarting the CSA Service:

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

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

The HPE Operations Orchestration Central service must be running in order to access Operations Orchestration Central. You can start this service by running the /usr/local/hpe/csa/OO/central/bin/central start command. You can stop this service by running the /usr/local/hpe/csa/OO/central/bin/central stop command.