tracker issue : CF-4205256

select a category, or use search below
(searches all categories and all time range)
Title:

The wsconfig "update" feature should back up changed connector files, similar to how a remove does

| View in Tracker

Status/Resolution/Reason: Open//

Reporter/Name(from Bugbase): Charlie A. / ()

Created: 09/25/2019

Components: connector

Versions: 2018

Failure Type:

Found In Build/Fixed In Build: /

Priority/Frequency: Normal /

Locale/System: / Windows 10 64 bit

Vote Count: 5

When we run the wsconfig "update" feature (in the wsconfig UI), that simply updates the needed files (usually just the isapi_redirect.dll for IIS, or mod_jk.so for Apache). While it's simple and fast, a problem happens if it turns out the connector update has a problem. Then there's no easy way to revert back to the old connector file(s).

At least when we "remove" a web server connector (with the wsconfig UI, since CF11), we are offered the option to let it backup the current connector files.

The "update" feature should offer the same. Or at least backup what the update CHANGES, whether it's just the dll or .so file, or perhaps also a properties file. I don't know if the update may ever change a properties file, but if it did, that could lose customizations that a user did to that file, and again this backup of whatever the update changes could be used to detect and/or recover from that.

Attachments:

Comments:

I should have added that I do think the same should apply if one does the command-line wsconfig with the update flag.
Comment by Charlie A.
31387 | September 25, 2019 09:52:24 PM GMT