Upgrade Steps on Linux for Root to Root user

Steps to perform before the upgrade

1. Back up your Zephyr data, nodedata, and the database.

2. Restart MySQL DB before doing the upgrade

3. Save all the contents of the following pages (license details, the start and end dates, indexing statistics, the current JVM size, and so on). You will need them for post-upgrade verification:

• https://<your instance>.yourzephyr.com/flex/assets/html/version.html

• https://<your instance>.yourzephyr.com/flex/version

Open

 

Open

 

4. Copy somewhere the following files:

• {Zephyr directory}\zephyr\tomcat\conf\server.xml

• {Zephyr directory}\zephyr\tomcat\conf\web.xml

• {Zephyr directory}\zephyr\tomcat\webapps\flex\WEB-INF\classes\jdbc.properties

• {Zephyr directory}\zephyr\tomcat\conf\<SSL certificate>

5. Back up the zephyrdata folder located in the common shared storage. If it is not there, back up the {Zephyr directory}\zephyrdata folder on each Zephyr node.

6. Back up the nodedata folder located in the common shared storage. If it is not there, back up the {Zephyr directory}\nodedata folder on each Zephyr node.

7. If you are not using the latest supported version of Elasticsearch 8.6.2, install it.

8. Do the echo of the $ZEPHYR_HOME environment variable. If nothing is returned, set the ZEPHYR_HOME environment variable:

9. Install RabbitMQ 3.12.10 (Optional): RabbitMQ 3.12.10 is a robust messaging and streaming broker that's easily deployable across cloud environments and on-premises setups. Currently, installing RabbitMQ 3.12.10 is optional for the users. Installing Java 17 is required for using RabbitMQ. You can download RabbitMQ 3.12.10 - here.

10. Install ZE-Services (Optional): Upgrading to Java 17 is mandatory for using ZE-Services:

• ZE-Webhook Service is the component responsible for accepting the incoming events from Jira and enqueues them to the message broker for further processing. You can download ZE-Webhook Service - here and find the installation instructions - here.

• ZE-Consumer Service is the component that picks the enqueued events from the message broker and updates ZE with the incoming data. You can download ZE-Consumer Service - here and find the installation instructions - here.

• ZE-AuditService is the component that acts as the incoming endpoint for the Audit Logs generated during the incoming webhook event processing and enqueues them to the message broker. You can download ZE-AuditService - here and find the installation instructions - here.

• ZE-AuditProcessor is the component responsible for reading the enqueued audit logs from the message broker and inserting them into ZE. You can download ZE-AuditProcessor - here and find the installation instructions - here.

The upgrade procedure

1. Stop the Zephyr service on all Zephyr cluster nodes:

2. Upgrade Zephyr on the first node using the installer:

3. When prompted to choose between a new installation and upgrading, choose Upgrade:

4. Choose No for now.

5. After you install Zephyr, make sure it is up and running. When Zephyr starts, you will see the following line in the zephyrlocation/tomcat/logs/thedinc.log log file:

6. Stop the Zephyr service:

7. Copy the SSL certificate files with those you saved at step 3 to the following folder if Zephyr is configured to use SSL:

{Zephyr directory}\zephyr\tomcat\conf\<SSL certificate>

8. After you upgrade Zephyr Enterprise on all the nodes, you need to modify the following file on each node:

<Zephyr Directory>/tomcat/webapps/flex/WEB-INF/classes/hazelcast.properties

 In this file, find the following lines and change the values as shown below:

• zephyr.hz.cluster.enabled=false - set it to true.

• zephyr.hz.cluster.name=zephyr-hazelcast-cluster - specify a unique name for each cluster, for example, zephyr-hazelcast-cluster_smartbear.

• zephyr.hz.interfaces.enabled=false - set to true.

• zephyr.hz.interface=127.0.0.1 - This is the IP of the IP interface. Replace it with an IP address that has asterisks instead of the last two components. For example: zephyr.hz.interface= 192.168.*.*

• zephyr.hz.tcp-ip.enabled=false - set it to true.

• zephyr.hz.members=127.0.0.1 - specify the IP addresses and port number of each node separated by a comma. For example: zephyr.hz.members=192.168.0.1:5701,192.168.0.2:5701

9. After modifying the hazelcast.properties file, start Zephyr on all the nodes by using the following commands:

When Zephyr starts, you will see the following line in the zephyrlocation/tomcat/logs/thedinc.log log file:

Steps to perform after the upgrade

• Check whether Zephyr and Elasticsearch are up and running.

• Check the logs for any errors and make sure that all the patches have been applied successfully.

• Log in as an Administrator and trigger the Full Reindexing manually.

• Check the re-indexing status:
  https://<your instance>.yourzephyr.com/flex/assets/html/version.html

• This Step is only applicable if the ZE-Service is enabled.
  Update the Jira Configuration for the new ZE-Services.

  • Once the upgrade is successful, on login into Zephyr, the user will get the below popup. (If Jira is integrated before the upgrade)
    
    

  • Once the user navigates to the Jira Integration page → the Jira connections will be highlighted in RED as shown in the screenshot below:
    
    

  • Once all services are up and running → For Automatic webhook management → click on the Update Webhook button from the Jira Integration page.
    
    

  • In Jira, the webhook URL will be updated as per the new webhook URL:

    The new webhook URL would be something like: https://webhook.yourzephyr.com/v1/jira/webhooks/callback
    
    

• This Step is only applicable if the ZE-Service is enabled.
  For Manual webhook management, copy the URL from the popup as shown in the below screenshot and go to Jira, to create a webhook with the new URL. The below popup will appear when integrating a Zephyr project with a Jira project or In Jira Integration → click on the Edit icon under the Action column and save the Jira Integration again.

See Also

Set Up Zephyr Data Center Cluster