JIRA SERVER 

This article describes how you can test the latest Exalate version on a staging environment before upgrading the production environment. 

Steps overview:

Back up the production environment with the sync running

We strongly recommend to do backups for both sync sides at the same time

Create staging environment 

You need to create staging environment for both instances.

Please make sure that Exalate does not synchronize from staging environment to production and disable it. 

In case, you did not disable Exalate, the issue will be synchronized to the production environment. Make sure you disable Exalate to avoid synchronization errors.

  1. Add this parameter into the ${JIRA_INSTALL}/bin/setenv.sh file to stop the Exalate on the Jira startup. Setting properties and options on Jira startup.

    -Dcom.exalate.sync.disabled=true

    Below you can see how the line with added parameter should look like

    JVM_SUPPORT_RECOMMENDED_ARGS="... -Dcom.exalate.sync.disabled=true ..."

  2. Import the data

    If you used the external database export tools, use the same tool to import data via external tools on both staging Jira environment

  3. Start up both Jiras
    The Exalate is disabled, so no sync should happen and nothing should be messed up.

  4.  Upgrade Exalate to the latest version 
  5. Reconfigure the Destination instance URL in the Connection using the SQL query as below

    UPDATE "AO_08F1AF_INSTANCE" SET "URL" = 'https://staging. ...' WHERE 'INSTANCE_NAME' LIKE '%Public%';

  6. Delete all the connections which are not pointing to staging environments on both sides

  7. Stop both Jiras

  8. Remove the command from the ${JIRA_INSTALL}/bin/setenv.sh file on both sides 

    -Dcom.exalate.sync.disabled=true

    Below you can see how the line with added parameter should look like

    JVM_SUPPORT_RECOMMENDED_ARGS="... ..."

  9. Start both Jiras.