To upgrade to uPortal 4.2.0 you must do an ant initdb. Export your current layouts, portlet definitions, and other entities and integrate the changes into the uPortal 4.2's uportal-war/src/main/data folder. uPortal 4.2 does not support the Universality theme so you will need to re-do your layout files using the Respondr theme.
To use the database-backed PAGS configuration, you must integrate your custom changes to PAGSGroupStoreConfig.xml into default.person-attribute-group-store.xml.

4.1 to 4.2

Do not need to do an initdb (unless you are using the Universality theme, see above)
If using XML-based PAGS suggest switching to database-backed PAGS. This will be strongly suggested with uPortal 4.3 to take advantage of Ad-hoc groups (
Jira Legacy
server Apereo Issues
serverId 76221f40-4501-3df1-8578-6c87908cbdf7
key UP-4459
)

4.2 to 4.3

...