...

1. Prepare a test server that 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 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 database to see how your Apps fare with the existing production data. 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.
5. When you are ready, please continue to the next step.

Updating Joget Workflow Using jw.war

1. Locate the new jw.war and jwdesigner.war files  file 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 and jw 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 directort in "[Joget Installation Directory]/apache-tomcat-x.x.x/work/Catalina/localhost".
6. Copy the new jw.war and jwdesigner.war files  file into the Apache Tomcat webapps directory "[Joget Installation Directory]/apache-tomcat-x.x.x/webapps".
7. Start Apache Tomcat / Joget Workflow.

Note: The old jwdesigner.war process builder has been deprecated and need not be copied to your new Joget  installation.

...