Versions Compared

Old Version 9

changes.mady.by.user Justin

Saved on

compared with

New Version Current

changes.mady.by.user Andrew

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Introduction

Joget Workflow v6 boosts boasts new features and capabilities that appeal to both new and existing users. Check out What is New in Joget Workflow v6 to find out more before performing the upgrade. 

General Upgrade

...

Flow

Warning

Compatibility: It is strongly recommended that you test the upgrade on a development or test environment first.  If you are upgrading from v3, please note that there have been security hardening changes since v4 so please refer to v4 Compatibility.

Licensing: For the Enterprise Edition, upgrades between major versions (e.g. v5 to v6) requires re-activation with a new license, so users with an active Enterprise Software Subscription are required to request for a new license.

IMPORTANT: Starting from v6.0.15, JAVA 8 is required due to fixes for vulnerability issues of a dependent libraryDo not upgrade over in production server without prior testing.

  1. Prepare a testing test server that mimic mimics the production server as close as possible in all possible aspects (e.g. user setup, networking environment, cpu/memory capabilities, database) without cloning the production's database server. Start with a fresh new database.
  2. Once you are ready with the testing test server, you may try to start with a fresh database without the data but just the Apps loaded in. Run through all the functionalities of your Apps to see if everything works as expected.
  3. If Step 2 goes well, you may then try to clone the existing production 's database to see on how your Apps fare with the existing production databasedata. Run through all the functionalities of your Apps again to see if everything works as expected.
  4. If you have integrated Joget Workflow with other solutions, you will also need to test them accordingly to against the new Joget Workflow v6 server.
  5. When you are ready, please continue on to Upgrading an Existing Installationto the next step.

Performing a Backup

Please backup your files and perform the necessary tests after the upgrade. If you are upgrading from v3, please note that there have been security hardening changes since v4 so please refer to v4 Compatibility .

Updating Joget Workflow

Warning

Do not upgrade directly in a production server without prior testing.


  1. Locate the new jw.war and jwdesigner.war files from either the:
    1. Downloadable Installers (in the /apache-tomcat-x.x.x/webapps directory); or 
    2. The Enterprise Support Site for Enterprise Software Subscribers.
  2. Stop Apache Tomcat / Joget.
  3. Backup the existing installation data (Please refer to Joget Workflow Deployment Best Practices)
  4. Delete the existing jw.war, jwdesigner.war, jw and jwdesigner directories in "[Joget Installation Directory]/apache-tomcat-x.x.x/webapps". 
  5. Delete the Apache Tomcat working directories i.e. the "jw" and "jwdesigner" directories in "[Joget Installation Directory]/apache-tomcat-x.x.x/work/Catalina/localhost".
  6. Copy the new jw.war and jwdesigner.war files into the Apache Tomcat webapps directory "[Joget Installation Directory]/apache-tomcat-x.x.x/webapps".
  7. Start Apache Tomcat / Joget Workflow.



Info
titleNote on Upgrading Joget

If in your earlier Joget version you changed the security key and salt hash, remember to edit the customApplicationContext.xml file and add in your original key and salt hash after upgrading your Joget else you will not be able to log in to Joget with your admin account.