Executing Post-Upgrade Tasks

Since you optimized your system for upgrading, after the upgrade is complete you must re-optimize it for production.

Tuning Your Database for Production

Prior to upgrading your Liferay DXP database, you tuned it for upgrade. Now that upgrade is complete, restore the production database tuning you used previously.

Re-enabling Search Indexing and Re-indexing Search Indexes

Make sure to re-enable search indexing by removing the com.liferay.portal.search.configuration.IndexStatusManagerConfiguration.config file from your [Liferay Home]/osgi/configs folder or setting this property in it:


Then re-index Liferay DXP’s search indexes. Don’t just do this blindly, however. By default, Liferay DXP ships with an embedded configuration for Elasticsearch. This configuration works great for demo purposes, but is not supported in production. Make sure to install and configure a standalone Elasticsearch instance to run in production.

Enabling Web Content View Permissions

Prior to Liferay DXP 7.1, all users could view web content articles by default. Now view permissions are checked by default. Here are options for opening view permissions:

Option 1: Edit view permissions per web content article per role.

Option 2: Open view permissions for all web content articles by going to System Settings → Web Experience → Web Content and deselecting Article view permissions check enabled.

Once you’ve configured search, re-indexed your search index, and set web content view permissions, your upgraded system is ready for action! Congratulations!

« Upgrading Modules Using Gogo ShellUpgrading a Sharded Environment »