I’ve a manual install of 3.2.0. This was done on a linux server years ago by manually unziping the distro file and just added a service file to run it.
I actaully think it started as a 3.1.x version and I unzipped the 3.2.0 over the top (or something like that), and that upgrade worked.
I think all you need is to run $OH_HOME/runtime/bin/update. That should download the latest release and do all the upgrade steps. However, I don’t know if that script existed or if it was comprehensive back in 3.2. But it’s worth a shot.
If that script doesn’t exist in your OH 3.2, I recommend looking at the upgrade script in the 4.2 zip file and follow those steps. I believe at a high level you’ll unzip over your existing install replacing existing files, clear the cache, and run java -jar $OH_HOME/runtime/bin/upgradeTool.jar.
Note that not all breaking changes are handled by upgradeTool and upgradeTool only works on managed configs, not text file based configs. And even with managed configs, I don’t know if it was ever tested on 3.2 to 4.x. It might miss some things.
Regardless you’ll need to go through the announcements for 3.3, 3.4, 4.0, 4.1 and 4.2 and review all the breaking changes you will need to apply to your configs.
In the end I decided to create a new instance. change the ports so they don’t class. run both at the same time time and just work my way though the things creating them in the new one, based on the old one. Once, I’ve finished will just shutdown the 3.2.0 and put ports back to standard on new one.