Can one roll back to previous version of Vertigis Studio Web
Is it possible roll back to previous on-premise version of Vertigis Studio Web, such as 5.32.0 to 5.30.2?
We are planning on upgrading to 5.32.0 later this week, and while I fully expect everything will go smooth, out of caution I'm wonder what would need to be done if we needed to roll back. I assume we would need to backup all the AGOL items. However, would we also need to create a backup of all the files on the server too, or would we need to uninstall and re-install the Vertigis Studio Web software?
Has anyone done this?
Cheers,
Mike
-
Hey Mike
It is possible to uninstall and reinstall an older version of Studio Web Designer, yes.
An important facet of this is that you are referring to the Studio Web Designer, while there are also the end product applications that are the output of your Designer. These are stored in your AGOL org and they only upgrade when you open the app in designer and save it with that new version.If you are not already, I would suggest making use of our Deployment Stages to deploy production versions of your applications which will give you a buffer of having a Development app (and perhaps a Testing or Staging stage). That way, when you upgrade VSW Designer you can then upgrade the Dev app, test that and once satisfied push to production.
You can also, in VSW Designer, roll back the development app by replacing it with the production environment version.
0 -
Just to verify, I assume I would simply:
1) Run the installer again, and pick “remove”
2) Run the installer for the older version (i.e. 4.30.2) and go through the standard process.
3) Would I then need to reconfigure in to link to the proper AGOL item and related settings, or would the previous settings be copied over. Same applies for any IIS configurations, etc.
If I needed to do the same for workflow or print (we haven't used report or mobile yet), would I need to re-apply the config file settings, like workflow database connection strings?
0 -
Yes that's right! You would remove and install an old version using that approach. It would be necessary to run through the post installer just as though you were installing for the first time, which involves configuring the sign in provider and deploying the components to IIS.
In terms of Workflow, Printing and others that create config and application data specific to you, I would expect that to persist. Those config and app data files are not removed as part of the application uninstall process, by design. The uninstall only removes the application components.
0 -
That's wonderful. You made my day. BTW, I'm running the upgrade right now. Very timely.
0 -
This chat is very helpful. Is a roll back to an earlier version of VertiGIS Web Studio when using the SaaS product possible also? We have a slightly different requirement to the one Mike mentioned. We run everything as SaaS, but have maintained back ups of each version.
Is it correct to assume that if we were to roll back to an earlier saved backup, that the version would be forced to upgrade to the current one when saved and deployed?
0 -
Mike Diss-Torrance did the uninstall and reinstall of an older version work for you? Did you have to export a copy of your VS Web apps before running the steps, or did them remaining in your AGOL/Portal after the install and simple reconnect to the fresh install of the older version of VS Web after the install? I'm about to look at doing the same.
0 -
We have a dedicated webserver and installation of Vertigis Studio for R&D purposes, primary to test what (if any) potential changes to the software will impact our production viewers before we apply the upgrade on those production servers. For this particular effort, I needed to uninstall Vertigis Studio Web from that R&D environment, followed by installing the older version.
Had we had a viewer that I didn't want to be corrupted with the old version of web, I believe I would need to edit the underlying JSON of the viewer and do a find/replace of the version numbers and possibly remove any code that was introduced with the newer version.
0
Please sign in to leave a comment.
Comments
7 comments