Install HCM ARA on Linux

To configure a group and user for HCM ARA, complete the following steps:

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

2. Create a group called codargrp. Enter the following:

   addgroup codargrp (Ubuntu)
   groupadd codargrp (Red Hat Enterprise Linux)

3. Create a user called codaruser and assign this user to the codargrp. Enter the following:

   adduser -g codargrp -m codaruser (Ubuntu)
   useradd -g codargrp -m codaruser -s /bin/bash (Red Hat Enterprise Linux)

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

   passwd codaruser

   When prompted, enter the password.

Install Codar

To install Application Release Automation on Linux, complete the following steps.

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

2. Create an installation directory for HCM ARA (this document assumes that you will install the product in /usr/local/hpe/codar and all examples used in this document are based on this assumption). Enter the following:

   mkdir -p /usr/local/hpe/codar

3. For the installation directory, set the owner to codaruser and the group to codargrp. Enter the following:

   chown -R codaruser:codargrp /usr/local/hpe/codar

4. Log out as the root user and log in as codaruser.
5. Copy the HCM ARA installation file (setup-codar.bin) to the system and go to the directory in which it has been copied.

6. Verify that setup-codar.bin is owned by codaruser and that codaruser has full permissions for the file. If necessary, complete the following steps:

   1. Log in as the root user

   2. Enter one or both of the following commands:

      chown codaruser setup-codar.bin
chmod u+rwx setup-codar.bin

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

8. Run the setup-codar.bin installation file.

   Note You must run setup-codar.bin as the codaruser. If you install as another user, you may not be able to run HCM ARA.

   As the codaruser, enter the following:

   ./setup-codar.bin

9. Read the Introduction and press Enter to continue with the installation.

10. Read the license agreement. Press Enter to scroll through the entire agreement.

11. Select Y and Enter to accept the license agreement and continue with the installation. Select N press Enter to exit the installation.

12. Select HPE Codar and press Enter.

13. Enter a location in which to install HCM ARA (enter the absolute path to the location) and press Enter. Or, press Enter to accept the default location.

    The default location is /usr/local/hpe/codar.

    Note If the directory in which you choose to install HCM ARA is not empty, existing content in the directory may be overwritten or deleted when HCM ARA 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.

14. Choose the JRE that will be used by HCM ARA.

    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, see the Codar System and Software Support Matrix.

    Open JRE

    The Open JRE is bundled with HCM ARA. If you want to use the Open JRE, type 1 and press Enter.

    The default location in which the Open JRE is installed is /usr/local/hpe/codar/openjre.

    Oracle JRE

    If you have installed a supported version of Oracle JRE to be used by HCM ARA, type 2 and press Enter. Type the location in which you installed this JRE and press Enter key.

    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 HCM ARA, type in the location in which you installed the JRE that will be used by HCM ARA and press Enter key.

    Proceed to Step 26 for instructions on configuring Oracle JRE.

15. Enter the port number in the HPE Codar Port field and press Enter key. The default port number is 8444.
16. Set passwords for the following system accounts used for administration and integrations between CSA components and other products:
    

    Account	Description
    Admin	Main administrator
    consumerAdmin	Administrator account in sample consumer organization
    consumer	End-user account in sample consumer organization
    csaTransportUser	Used for CSA IDM to CSA communication
    ooInboundUser	Used for HPE OO to CSA communication
    csaReportingUser	Used internally for dynamic list properties
    codarIntegrationUser	Used in Jenkins for Codar communication
    csaCatalogAggregationTransportUser	Used for aggregation
    securityEncryptedSigningKey	Used for encryption of SSO cookie

    You can set passwords in any of the following methods:

    • Use generated passwords or set custom passwords: Use passwords that are automatically generated by the Codar installer software. You can also edit the generated passwords.
    • Load passwords from a file and review: Load a text file in which the passwords for all system accounts are saved. You can also edit the loaded passwords from the system account password fields.

    Example: 
    #HPE CSA passwords of system users
    #Mon Nov 16 01:38:04 PST 2015
    ooInboundUser=p0s7f1tbmlse18v2
    consumer=23tdvbntir6thmf3
    csaTransportUser=jjcigu4kl6a989km
    codarIntegrationUser=m16c2de8gaqqcc7c
    securityEncryptedSigningKey=2surchgk13lsk7ll
    csaCatalogAggregationTransportUser=cubouc8ptjnemesn
    csaReportingUser=3l31d1nhsb3dqts9
    admin=5q0mjmv7uckip5d3
    consumerAdmin=gkemt4accuqiajeb

    • Set a single password for all accounts (Not recommended): Set a single password for all system accounts. HPE do not recommend to use a single for all system accounts.
    Note: You must enter your passwords twice for password confirmation.
    You can also edit the passwords by enabling Edit generated passwords.

17. Select any of the following options to save passwords in your system and press Enter:
    • Save to file
    • Copy to clipboard

    If you do not want to save your passwords, enable Do not save the passwords. I can remember them all and press Enter.
    

18. Install HCM ARA database components onto the database instance to create the HCM ARA database schema, if it does not already exist.

    Type yes to install HCM ARA database components and create the HCM ARA database schema. When you select this option, the HCM ARA process automatically starts when you exit the installer.

    Type no if you are using an existing HCM ARA database schema that was created as part of a prior successful installation of HCM ARA version 1.90. When you select this option, the HCM ARA process does not start when you exit the installer. See the end of this section for information on how to start and stop the HCM ARA service.

19. Define the database instance on which the HCM ARA database components should be installed. Enter the following database information (press Enter after each entry).

    1. Enter the type of database you have installed: MSSql (Microsoft SQL Server), Oracle, or Postgres (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 Codar system). For a list of supported JDBC driver versions, see the Codar System and Software Support Matrix.

    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), or 5432 (PostgreSQL).

    4. Enter the database name. This is the name of the database instance on which the HCM ARA database schema will be installed.

       If you are creating a new HCM ARA database schema, this is the name of the database instance on which the HCM ARA database components will be installed.

       If you are using an existing HCM ARA database schema that was created as part of a prior successful installation of HCM ARA version  1.90, this is the name of the database instance on which the HCM ARA database schema already exists.

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

    5. Enter the HCM ARA database user name. This is the user name of the database user you configured for Application Release Automation in the appropriate database configuration section of this guide.

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

    6. Enter the HCM ARA database password. This is the password for the HCM ARA database user.

    7. Enter the HCM ARA reporting database user name (optional). This is the user name of the database user you configured for reporting purposes for HCM ARA. For details on configuring the reporting database user, see one of these sections, depending on which database you installed: Configure Oracle Database, Configure Microsoft SQL Server, or Configure PostgreSQL users and database.

    8. Enter the password for the HCM ARA reporting database user.

    Note You must be using both the Cloud Service Automation and HCM ARA licenses to use the Cloud Service Automation reporting capabilities. For details, see the Cloud Service Automation Reporting and Auditing Whitepaper.

20. Provide the database instance used by the Identity Management component. Enter the following database information (press Enter after each entry).

    1. Enter the database hostname. The host name 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].

    2. Enter the database port. This is the database port number, such as 1433 (Microsoft SQL Server), 1521 (Oracle), or 5432 (PostgreSQL).

    3. Enter the Identity Management component Database Name/Oracle SID. The name of the database instance used by the Identity Management component.

    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. For details on configuring the Identity Management component database user, see one of these sections, depending on which database you installed: Configure Oracle Database, Configure Microsoft SQL Server, or Configure PostgreSQL users and database.

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

21. Enter the HCM ARA server host name. This is the fully-qualified domain name of the system on which you are installing HCM ARA. The fully-qualified domain name is used to generate the self-signed SSL certificate which is used when https browser requests are issued for Codar. This self-signed certificate expires 120 days after HCM ARA 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 HCM ARA and manually reconfigure HCM ARA to use this certificate.

22. By default, Single Sign-On (HPE SSO) is included with Application Release Automation. The Single Sign-On that is included with Application Release Automation can only be used when launching an application, such as Operations Orchestration or HPE IT Executive Scorecard, from the Codar Console. See the Single Sign-On documentation for more information on integrating Single Sign-On with an application.
    

    If you do not want to use Single Sign-On, you can disable it. Type 2 and select Enter.

    To enable Single Sign-On, type 1 and select Enter. Enter the Domain name of the network to which the server belongs (the server on which you are installing Application Release Automation) and select Enter.

    Note You must enter the full domain name of the server. For example, if you are installing Application Release Automation 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 Codar Console.

    Applications launched from the Codar Console with which you want to use Single Sign-On must be installed on systems that belong to this domain.

23. Specify whether you want to install the embedded (new) Operations Orchestration instance with HCM ARA or if you are integrating with an external (existing) instance of Operations Orchestration.

    • Select 1 and Enter to integrate with an external (existing) instance of Operations Orchestration. Proceed to Step 20a.
    • Select 2 and Enter to install the embedded Operations Orchestration. Proceed to Step 20b.

    By default, sample content (service designs and the components and flows required by the designs) are installed with . You can choose to deploy this content during installation (making the sample service designs available in the Designs are of the ) or deploy the content at a later time.
    
    To deploy the sample content during the installation process, type 1 (Install sample content) and press Enter.
    
    To deploy the sample content at a later time, type 2 (Skip content installation) and press Enter. If you choose to skip content installation, you can install the content at a later time, by running the . For details, see the Cloud Service Automation Content Pack User Guide.

    1. If you are integrating with an external (existing) Operations Orchestration, define the Operations Orchestration instance with which HCM ARA is to be integrated. Enter the following information (press Enter after each entry). Proceed to step 21.

       1. Enter the Operations Orchestration host name. This is the fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate the Operations Orchestration certificate. The hostname is used for TLS validation and to build the URL that the Codar Console uses to interact with Operations Orchestration (for example, in the subscription event overview section of the Operations area in the Codar Console, selecting the Process ID opens Operations Orchestration to the detailed page of the selected process when these properties are configured).

       2. Enter the Operations Orchestration port. This is the port number used to communicate with Operations Orchestration, such as 8445. The port number is used to build the URL that the Codar 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.

          Caution Ensure that port 8080 is not being used on the system where you install Codar and the embedded Operations Orchestration. If this port is used, then Operations Orchestration flows will not work properly.

       3. Enter the Operations Orchestration user. This is the name of the user who logs in to Operations Orchestration Central. HPE recommends that you use the admin user. If you followed all the steps documented in Install external Operations Orchestration, this is the admin user.

       4. Enter the Operations Orchestration password. This is the password used to log in to Operations Orchestration Central. If you followed all the steps documented in Install external Operations Orchestration, use the password cloud
       5. Re-enter the Operations Orchestration password.
       6. Enter the Operations Orchestration certificate file. This is the file name and location of Operations Orchestration's certificate from Operations Orchestration's truststore on the HCM ARA system. If you have not already done so, export the Operations Orchestration certificate and copy it to the HCM ARA system (see Install external Operations Orchestration for more information).

       Note This information is used to set the Operations Orchestration properties in the csa.properties file and to import Operations Orchestration's certificate into HCM ARA's truststore. See Codar Configuration Guide for more information about these properties.

    2. If you are installing embedded Operations Orchestration, enter a location and press Enter.

       1. Enter the database information for the database used by the embedded Operations Orchestration (press Enter after each entry). The database used by the embedded Operations Orchestration must be the same type of database used by the HCM ARA (Microsoft SQL Server, Oracle, or PostgreSQL).

          1. Enter the database hostname. This is the hostname or IP address of the server where the embedded Operations Orchestration database is located. When specifying an IPv6 address, it must be enclosed in square brackets. For example, [f000:253c::9c10:b4b4] or [::1].
          2. Enter the database port. This is the embedded Operations Orchestration database port number, such as 1433 for Microsoft SQL Server, 1521 for Oracle, or 5432 for PostgreSQL.
          3. Enter the Operations Orchestration database name or Oracle Operations Orchestration SID. This is the name of the database instance used by the embedded Operations Orchestration. For an Oracle database, this is the Oracle service name.
          4. Enter the Operations Orchestration database user name. This is the user name of the database user you configured for the Operations Orchestration database.
          5. Enter the Operations Orchestration 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. Applications running on the system on which Application Release Automation and the embedded Operations Orchestration are installed should not be using these ports.

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

          1. Enter the Operations Orchestration user name. This is the name of the user used for provisioning topology designs. This user is given the ADMINISTRATOR and SYSTEM ADMIN roles. The recommended user name is admin.

          2. Enter the Operations Orchestration password. This is the password used by Operations Orchestration for the user who provisions topology designs. The recommended password is cloud.

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

25. 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 Codar database schema will be installed. If you are creating a new Codar database schema, this is the name of the database instance on which the Codar database components will be installed. If you are using an existing Codar database schema that was created as part of a prior successful installation of Codar version 1.90, this is the name of the database instance on which the Codar 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 Codar (Oracle / Microsoft SQL Server / PostgreSQL) . Default: ooddb
    Workflow Designer Database User Name	The user name of the database user you configured for the Codar database in the Configure (Oracle / Microsoft SQL Server / PostgreSQL) section of this guide (for example, csaidmdbuser or 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 Codar is installed.

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

27. 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 Codar.

28. By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with Application Release Automation. You can choose to deploy this content during installation (making the sample service designs available in the Designs are of the Codar Console) or deploy the content at a later time.

    To deploy the sample content during the Application Release Automation installation process, select any or all of the following sample contents and press Enter:
    

    Account	Description
    CC-Vcentre-Topology-15.12.0000	This topology model integration demonstrates how to deploy virtual machine using VMWare vCentre server and flex resources such as the number of processors or memory.
    CC-Openstack-Topology-15.12.0000	This topology model integration demonstrates how to provision multiple instances of server, volume, and swift container in an OpenStack based environment.
    CC-Amazon-EC2-Topology-15.12.0000	This topology model integration demonstrates how to provision a classic Amazon EC2 instance using AWS interface.
    ICSP-Topology-Integration-15.12.0000	This topology model integration demonstrates how to deploy physical infrastructure (servers, storage, and networking) and operating systems as a part of Iaas or Saas offerings using HPE OneView and HPE Insight Control server provisioning.
    OneView-Topology-Integration-15.12.0000	This topology model integration demonstrates how to utilize HPE OneView to deploy physical infrastructure (servers, storage, and networking) as a part of Iaas or Saas offerings.
    Helion-Development-Platform	Helion development platform
    HPE-CODAR-1.80.0000	This topology model integration demonstrates how to provision instances of MySQL, PetClinic Application, Open Stack components, Tomcat Server.
    Docker	This topology model integration demonstrates how to use OOT Docker components to deploy applications.

    Note If you do not select all of the contents listed on this screen, some of the Codar features may not work as expected.

    To deploy the sample content at a later time, press Enterwithout selecting any of the sample contents.

    If you choose to skip content installation, you can install the content at a later time, by running the Content Capsule Installer. For details, see the Cloud Service Automation Content Pack User Guide.

29. Review your selections and press Enter to complete the installation or Ctrl-C to exit the installation.

30. When the installation completes, press Enter to exit the installer.

31. If you selected to use the OpenJDK JRE with HCM ARA and installed HCM ARA on a system running a headless Ubuntu Linux version 14, install the Standard Java or Java-compatible Runtime package. Enter the following:

    apt-get install default-jre

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

    export CSA_HOME=/usr/local/hpe/codar
export JAVA_HOME=CSA_JRE_HOME
export PATH=$PATH:/sbin

    where CSA_JRE_HOME is the directory where the JRE used by HCM ARA is installed.

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

34. Create an HCM ARA service to start and stop the HCM ARA processes.

    1. Log in as the root user.

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

       cd /usr/local/hpe/codar

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

       cp ./scripts/codar /etc/init.d

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

       chmod 755 /etc/init.d/codar

    5. Log out as the root user.

35. Log in as codaruser and start the HCM ARA service. Enter the following:

    service codar start

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

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

The Application Release Automation service must be running in order to access Codar Console. You can use the following commands:

service codar start - to start the Application Release Automation service

service codar restart - to restart the Application Release Automation service

service codar stop - to stop the Application Release Automation service

service codar status - to check the status of the Application Release Automation service

The Operations Orchestration Central service must be running in order to access Operations Orchestration Central. You can use the following commands:

/usr/local/hpe/codar/OO/central/bin/central start - to start the Operations Orchestration service

/usr/local/hpe/codar/OO/central/bin/central stop. - to stop the Operations Orchestration service