Run upgrade installer on Windows

To run the upgrade installer on Windows, 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. Unzip the setup-codar.zip upgrade file. Go to the directory to which the files have been extracted and run the setup.bat 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.

   Note:
   When you upgrade Codar 1.5 patch 1 to Codar 1.7, the following message is displayed in the license Agreement Screen:
   
   HPE Codar Reporting Database Username was not provided during installation of HPE COdar 04.50.00000.1.
   
   You can ignore the Codar version number dispalayed in the message and continue with the upgrade.

5. Verify that you want to upgrade to Codar version 1.80 and click OK.

6. Select the JRE used by Codar.

   • Use the existing JRE to continue using the JRE that was used with Codar version 1.50 or 1.60. No additional configuration is required if you use the existing JRE.
   • Use Open JRE if you want to use the JRE that is installed with Codar version 1.80. You must manually export the Codar certificate from the existing truststore and import it into the truststore that is installed with the upgrade.
   • Use Oracle JRE if you want to use an Oracle JRE and it is a different JRE from the one used with Codar version 1.50 or 1.60. If you used Oracle JRE with Codar version 1.50 or 1.60 and want to continue using this same JRE, select Existing JRE. You must manually export the Codar certificate from the existing truststore and import it into the Oracle JRE truststore.

   In this documentation, the directory in which the JRE is installed will be referred to as CSA_HOME\openjre\.

   For a list of supported JREs, see the Codar System and Software Support Matrix,

   Click Next after you have selected a JRE option.

7. Verify that you have stopped the following services and click OK:

   • HPE Codar
   • HPE Search Services
   • Elasticsearch
   • HPE Marketplace Portal

8. Select the environment in which Codar is running and click Next.

   • Select Standalone if Codar is running in a non-clustered environment.

     This selection determines the file from which the database instance information is read. For example, if you select standalone, the database instance information is read from the JBoss server's standalone.xml file (CSA_HOME\jboss-as\standalone\configuration\standalone.xml).

   • Select Cluster if Codar is running in a clustered environment.

     If you select cluster, the database instance information is read from the JBoss server's domain.xml file (CSA_HOME\jboss-as\domain\configuration\domain.xml).

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

10. Select any of the following options to save passwords in your system and click Next:

    • 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 click Next.

11. Install the Codar database components onto the database instance to create the database schema, if it does not exist.
    
    Click Yes to install Codar database components and create the database schema. When you select this option, the Codar service automatically starts when you exit the installer.
    
    Click No if you are using an existing Codar database schema that was created as part of a prior successful installation of Codar version 1.80. When you select this option, the Codar service does not start when you exit the installer. See the end of this section for information on how to start the Codar service.
    

12. Verify the database instance information and click Next.

    If the upgrade installer could not find the database instance information, a message is displayed and you will need to reenter the database information again. Continue to the next screen to reenter the database information again and click Next to continue.

13. Enter the Codar database user password and click Next.

14. If you configured a reporting database user, enter the reporting database user and password and click Next. If you did not configure a reporting database user, click Next.

15. Select Yes to install Codar database components and upgrade the schema then click Next.

16. The Single Sign-On configuration used during the previous installation (enabled or disabled), must be the same configuration used during the upgrade. The Single Sign-On that is included with Codar can only be used when launching an application, such as Operations Orchestration from the Codar Console. See the Codar Configuration Guide and Single Sign-On documentation for more information on integrating Single Sign-On with the application.

    If you do not want to use Single Sign-On, you can disable it.

    You MUST disable Single Sign-On if you are installing Codar in a FIPS 140-2 compliant environment if you plan on integrating with CA SiteMinder.

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

    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.

17. Specify your integration with Operations Orchestration.

    If you are integrating with Operations Orchestration 10.5, click Configure connection to a running OO server and click Next to proceed to step 18. The upgrade installer requires additional information to complete the integration.

    Operations Orchestration 10.5 must be installed and running in order to complete the upgrade of Codar.

    Caution If you are upgrading your existing Embedded Operations Orchestration, before you begin using the Codar Upgrade Installer, make sure the Embedded Operations Orchestration is using the codaruser. If the Embedded Operations Orchestration Upgrade Service starts using the root user, then the installer will not function properly and the Operations Orchestration upgrade will fail.

    Note If you have chosen to upgrade the embedded Operations Orchestration from the previous Codar installation, and the upgrade has failed, you will need to delete the CODAR home folder that includes the unfinished installation, then restart the installer and resume the installation.

    Note If you have chosen to install a new version of Embedded OO during Codar upgrade, and the upgrade fails, do the following:

    • Stop the Operations Orchestration Central service (Windows)

    • Clear the database schema used for the Operations Orchestration installation;

    • Finally, restart the installer and resume installation.

18. Define the Operations Orchestration 10.5 instance with which Codar is to be integrated. Enter the following information and click Next.

    Field Name	Description
    Operations Orchestration Hostname	The fully-qualified domain name or IP address of the server where Operations Orchestration is located. Specify the hostname that was used to generate the Operations Orchestration's 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).
    Operations Orchestration Port	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.
    Operations Orchestration User	The name of the user who logs in to Operations Orchestration Central. This is the user that was configured for provisioning topology designs.
    Operations Orchestration Password	The password used by the Operations Orchestration user to log in to Operations Orchestration Central.
    Operations Orchestration Certificate File	The file name and location of Operations Orchestration's certificate from Operations Orchestration's truststore on the Codar system. If you have not already done so, export the Operations Orchestration's certificate and copy it to the Codar system (see the section in this guide for more information).

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

19. By default, sample content (service designs and the components and Operations Orchestration flows required by the designs) are installed with Codar. 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 Codar installation process, select any or all of the following sample contents and click Next.

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

    To deploy the sample content at a later time, click Nextwithout 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.

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

20. Review your selections and click Install to complete the upgrade.

21. Click Done to exit the installer.