This section provides the upgrade procedure for DLM on a two-server and a three-server setup.
Before You Begin
  • Make sure that you are upgrading DLM when you upgrade TeamForge though the upgrade processes of both TeamForge and DLM are interdependent.
  • If you are upgrading from DLM 17.4 to 17.8, see Post-upgrade Steps for DLM 17.4 to DLM 17.8 Upgrade, after you have completed the upgrade process.

Upgrade DLM on a Two-server Setup

In this setup, DLM is on the same server where TeamForge and EventQ services are hosted and running. In other words, in this two-server setup, TeamForge, EventQ and DLM services are hosted on one server and ActionFlow is hosted on a second server.

Do This on the TeamForge Application Server

  1. Follow the TeamForge upgrade steps until you run the stop teamForge command as discussed in the TeamForge 17.8 upgrade instructions.

  2. Stop the following DLM services.

    systemctl stop actionhubserver
    systemctl stop actionhubdaemon
    
  3. Proceed with the TeamForge upgrade steps until you run the yum install teamforge command. For more information, see Upgrade to TeamForge 17.8.

  4. Install the following DLM application packages.

    yum install CN-actionhub CN-actionhubdaemon CN-actionhubserver actionhub-installer
    
  5. Proceed with the rest of the TeamForge upgrade steps. For more information, see Upgrade to TeamForge 17.8.

Do This on the ActionFlow Server

After upgrading TeamForge and DLM to 17.8, perform the following steps on the ActionFlow Server.

  1. Run the following command to restart ActionFlow.

    st2ctl reload
    
  2. Verify the status of ActionDesigner.

    systemctl status actiondesigner
    
  3. Restart ActionDesigner.

    systemctl restart actiondesigner
    

Upgrade DLM on a Three-server Setup

In this setup, DLM is on the same server where TeamForge services are hosted and running. In other words, in this three-server setup, TeamForge and DLM are hosted on one server and EventQ and ActionFlow are hosted on two other servers respectively.

Do This on the TeamForge Application Server

  1. Follow the TeamForge upgrade steps until you run the stop teamForge command. For more information, see Upgrade to TeamForge 17.8.

  2. Stop the following DLM services.

    systemctl stop actionhubserver
    systemctl stop actionhubdaemon
    
  3. Proceed with the TeamForge upgrade steps until you run the yum install teamforge command. For more information, see Upgrade to TeamForge 17.8.

  4. Install the following DLM application packages.

    yum install CN-actionhub CN-actionhubdaemon CN-actionhubserver actionhub-installer
    
  5. Proceed with the rest of the TeamForge upgrade steps. For more information, see Upgrade to TeamForge 17.8.

Do This on the EventQ Server

  1. Upgrade ActionHub.

    yum install actionhub_installer
    

Do This on the ActionFlow Server

After upgrading TeamForge and DLM to 17.8, perform the following steps on the ActionFlow Server.

  1. Run this command to restart ActionFlow.

    st2ctl reload
    
  2. Verify the status of ActionDesigner.

    systemctl status actiondesigner
    
  3. Restart ActionDesigner.

    systemctl restart actiondesigner
    

Post-upgrade Steps for DLM 17.4 to DLM 17.8 Upgrade

Even after you have successfully upgraded from DLM 17.4 to 17.8, the DLM version number is not getting updated as “17.8” due to an issue with one of the port settings.

To fix this:

  1. Log on to TeamForge as a site administrator.
  2. Select My Workspace > Admin > Integrated Apps.
  3. Click DLM.
  4. Click Export from the View Integrated Application page.
  5. Save the downloaded zip folder to your server.
  6. Extract the zip folder.
  7. Open the DLM_application.xml file and change the version number from “17.4” to “17.8”.
  8. Save and close the file.
  9. Open the DLM_deploy.xml file and remove the port number 443 from baseurl, gourl, and adminurl properties.
  10. Save and close the file.
  11. Select My Workspace > Admin > Integrated Apps.
  12. Select DLM and click Edit.
  13. Click CHOOSE FILE from Deployment Properties and select the DLM_deploy.xml file (Deployment Configuration File).
  14. Click CHOOSE FILE from Application Properties and select the DLM_application.xml file (Application Configuration File).
  15. Click Next.
  16. Verify the properties from the uploaded deploy and application details and click Save.
  17. Select My Workspace > Admin > Integrated Apps. You can see the version number changed to “17.8”.