Upgrading Zowe on two Sysplexes with Convenience builds

Products

• Brightside

Issue/Introduction

When operating Zowe on two Sysplexes, one for developers and one for QA at this point. 
What are the best practices with respect to upgrades of minor versions. 
Ideally keeping in mind that the instances are used by users dureing their activities. 
Part of the question is how to keep the space clean without leftovers from previous Zowe versions. 
Convenience builds is used for the installations. 

Environment

Brightside
Zowe

Resolution

For Sysplex and convenience builds, upgrading minor versions is straightforward, without leaving remnants from the previous Zowe version.

For Zowe, There is a runtime directory and MVS datasets.

1 - Runtime Directory

When upgrading, simply back up the entire runtime directory. After that, delete the following files from the runtime:

• bin
• components
• example-zowe.yaml
• files
• fingerprint
• licenses
• manifest.json
• schemas
• DEVELOPERS.md
• README.md

It's a best practice to keep the following directories outside the runtime directory:

• extensions
• logs
• workspace

 

2 - MVS Datasets

• There’s no need to remove any datasets.
• Then upgrading the convenience build, use the --allow-overwrite parameter while executing ZWE commands. This will overwrite the datasets with the content from the new version.
  
  
  
  
  

 

Additional Information