Post-Upgrade Considerations

After upgrading the database, you should configure Liferay for production again and check up on feature changes that might affect your Liferay instance.

Re-enable Production Settings

After upgrading your database, re-enable your production settings.

Search Indexing

If you disabled search indexing for upgrading to 7.2, re-enable it by removing the .config file you used to disable it or by setting indexReadOnly="false" in the .config file. For example,

rm osgi/configs/com.liferay.portal.search.configuration.IndexStatusManagerConfiguration.config

Reindexing search indexes is required after all Liferay upgrades. To reindex,

1. Click Global Menu () and open the Control Panel tab.

2. Click Search in the Configuration section and select the Index Actions tab.

3. Select either Concurrent or Full reindexing mode, then click Reindex for All search indexes. The reindex executes and displays a success message when done.

note

If you upgraded from an older version (7.1 and below) consider installing Elasticsearch to handle search indexing.

Database Configurations

If you tuned the database for the upgrade before upgrading it (see Database Tuning for Upgrades), restore your production database settings.

note

If you migrated from a sharded environment during data upgrade, you must make more adjustments to your configurations to complete the transition to virtual instances. See the Upgrade and Update Properties section for more information.

Installing the Latest Marketplace Apps

Install the latest version of your Marketplace apps for your new Liferay version and use Gogo shell commands to check for and execute any required database upgrades.

Accounting for Feature Changes

Features and behaviors change with new Liferay versions. Review how the following features and behaviors change.

Enable Web Content View Permissions

Prior to 7.1, all users could view web content articles by default. Now view permissions are checked by default. You can edit view permissions for each web content article per role.

note

Prior to 7.4, you could open view permissions for all web content articles by navigating to Control Panel → Configuration → System Settings → Web Content → Virtual Instance Scope → Web Content and de-selecting Article view permissions check enabled.

Check Web Content Images

Upgrading to 7.2 moves web content images to the File Store (also known as the Document Library) and then deletes their former table, JournalArticleImage. If an image can’t be migrated, Liferay reports the failure:

Unable to add the journal article image {filename} into the file repository

If there aren’t any messages, your images should now be in your file store. Preview your web content articles to verify the images.

Account for Deprecations and Features in Maintenance Mode

Review the deprecations and features in maintenance mode and plan for handling how they affect your Liferay instance.

Remove Obsolete Data

If you have data that’s unnecessary and useless, you can remove it. Here are two common obsolete data situations and tools for removing it.

• Data from obsolete Liferay apps or modules. The Data Cleanup tool removes it.

• Obsolete data from available Liferay apps and modules. The Data Removal tool removes it.

Conclusion

Once all necessary post-upgrade tasks are complete, your Liferay server is ready for normal operations as before. Congratulations!