Testing Exalate in a Jira on-premise staging environment

    Warning: Despite our best efforts, code can change without notice due to a variety of factors. If you encounter an issue in any of the code shown here and find that a specific block of code is not correct, or is causing errors, please check with the Community to find an updated version.

    Let's assume you need to clone your prod machine to your test environment. If Exalate is installed and active on your prod instance, this can be problematic, since the new instances could automatically pick a sync from the production environments.

    In this article, we describe a recommended approach to clone Jiras with Exalate installed.

    Steps overview:

    Back up the production environment with the sync running

    WARNING: We strongly recommend you perform backups for both sync sides at the same time.

    Create a Staging environment

    You need to create a staging environment for both instances.

    WARNING: Please make sure that Exalate does not synchronize from staging environment to production and disables it. If that occurred,  you did not disable Exalate and 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.

      1 -Dcom.exalate.sync.disabled=true

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

      1 JVM_SUPPORT_RECOMMENDED_ARGS="... -Dcom.exalate.sync.disabled=true ..."
    2. Import the data.

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

    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.

      1 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.

      1 -Dcom.exalate.sync.disabled=true

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

    9. Start both Jiras.