Date: Thu, 28 Mar 2024 23:24:35 +0000 (UTC) Message-ID: <51149550.7189.1711668275391@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7188_935611403.1711668275390" ------=_Part_7188_935611403.1711668275390 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Upgrade instructions included in the release notes for each release, and= you MUST read these. General options are:
If your Grouper database is large (i.e. you have lots of groups and memb= erships), the upgrade may take some time (even hours), so don't expect it t= o be over in a few minutes. Subjects are resolved during import and export,= so any performance problems in your subject sources will slow down the upg= rade process.
Whichever method is used, backup the database first. In some cases I've = found that I haven't been able to do an XML export (possibly due to interna= l inconsistencies in the database), but an in-place upgrade works fine afte= r which an export also works. I'm fine with this as long as I'm certain tha= t I have a good backup of the database and that no further changes are goin= g to be made to that data. To stop anything making changes I stop the group= er-loader daemon and shutdown any web and web-services interfaces. If I'm f= eeling really paranoid I put the database engine into single user mode. If = you are less paranoid, and would like to maintain read-only access to group= er you can put the API into read-only mode using the "grouper.api.readonly = =3D true" parameter in grouper.properties (remember to do this in all deplo= yed copies of your config files. This parameter is available in version 1.5= .3 or higher.
Some config files may also need changes, check the release notes.