HCL Workload Automation, Version 9.4

Upgrading a Dashboard Application Services Hub Version 3.1.1 or earlier cluster

Upgrade an existing High Availability configuration from Dashboard Application Services Hub Version 3.1.1 or earlier to a High Availability configuration in a Dashboard Application Services Hub, Version 3.1.2.1 environment. After performing the upgrade, you can proceed with the upgrade of the Dynamic Workload Console.

About this task

To move nodes from an existing High Availability configuration, you must remove all nodes from the old configuration and recreate the High Availability configuration in the new environment. On each node in the old configuration, except for the last node, run the disjoin command to remove it from the High Availability configuration. On the last node, you must first edit a script file and then run the uninstall command to remove the last node from the old configuration and clean up the database. You are then ready to create a High Availability configuration in the new environment.

Procedure

  1. In the existing environment for each node, except the last node, from a command prompt, change to the DASH_HOME/bin/ha directory and run the following command to disjoin it from the cluster:
    • JazzSM_WAS_Profile/bin/ws_ant.sh -f uninstall.ant disjoin -DdeleteExistingDataSource=true -Dusername=DB2_username -Dpassword=DB2password -DWAS_username=WAS_admin_username -DWAS_password=WAS_admin_password
    • JazzSM_WAS_Profile\bin\ws_ant.bat -f uninstall.ant disjoin -DdeleteExistingDataSource=true -Dusername=DB2_username -Dpassword=DB2password -DWAS_username=WAS_admin_username -DWAS_password=WAS_admin_password
    Important: The -DdeleteExistingDataSource parameter is mandatory and must be set to true.
  2. On the last remaining node, locate the following file and open it in a text editor:
    • DASH_HOME/bin/ha/uninstall.ant
  3. Locate the section that begins with <target name="uninstall" and edit that section so that it reads as follows: 
    <target name="uninstall" depends="checkinput,detectCurrentOSFamily
,setOSFileSeparator,resolveOsgiCfgInitExecutable,exportData,serverStatus">
    <java classname="DatastoreUninstall" classpathref="ha.uninstall.classpath"  
failonerror="true">
      <arg value="uninstall"/>
            <arg value="${username}"/>
            <arg value="${password}"/>
        </java>
        <delete file="${ProfilePath}/config/cells/${CellName}/applications
/${IscAppName}.ear/deployments/${IscAppName}
/isclite.war/WEB-INF/tipha.properties"/>
        <replace file="tipha.properties" token="HAEnabled=true" 
value="HAEnabled=false" />
        <antcall target="deleteDatasource"/>
        <antcall target="importData"/> 
     </target>
    Tip: The string exportData must be added to the first line of code and the line <antcall target="importData"/> must be added to the end of the extract.
  4. Save your changes to DASH_HOME/bin/ha/uninstall.ant.
  5. On the last remaining node in the old High Availability configuration, from a command prompt, change to the DASH_HOME/bin/ha directory and run the following command:
    • JazzSM_WAS_Profile/bin/ws_ant.sh -f uninstall.ant uninstall -DdeleteExistingDataSource=true -Dusername=DB2_username -Dpassword=DB2_password
    • JazzSM_WAS_Profile\bin\ws_ant.bat -f uninstall.ant uninstall -DdeleteExistingDataSource=true -Dusername=DB2_username -Dpassword=DB2_password -DWAS_username=WAS_admin_username -DWAS_password=WAS_admin_password
    Important: The -DdeleteExistingDataSource parameter is mandatory and must be set to true.
  6. Upgrade each node to Dashboard Application Services Hub Version 3.1.2.1, then proceed with the upgrade of the Dynamic Workload Console. After these two components have been upgraded, you can recreate the High Availability configuration in the new environment, see Setting up a High Availability configuration.