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¶
Now that you are done upgrading your database, re-enable your production settings.
Search Indexing¶
If you disabled search indexing for upgrading to 7.2, re-enable search indexing 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
Re-indexing search indexes is required for major version upgrades. When moving to a new update, applying a service pack, or upgrading to a new GA (rolling release) within the same Liferay version, consult the release highlights for the version to determine if a re-index is required. Here’s how to re-index:
Click on the Global Menu (
) and select the Control Panel tab. The Control Panel appears.Click on Search in the Configuration section, select the Index Actions tab, and click Execute for Re-index all search indexes. The re-index 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¶
Prior to upgrading the database, you may have tuned it for upgrade (see Database Tuning for Upgrades). Now that the upgrade is complete, restore your production database settings.
Note
If you migrated from a sharded environment during data upgrade, then 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¶
If you haven’t already installed the latest version of your Marketplace apps for your new Liferay version, install them and use Gogo shell commands to check for and execute any database upgrades they require.
Accounting for Feature Changes¶
Features and behaviors change with new Liferay versions. Review how the following changes.
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 instead. Here are the main options for opening view permissions:
Option 1: 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.
Option 2: If few Web Content articles exist, then edit view permissions per Web Content article per role.
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 such messages, all of your images should now be in your File Store. You can preview your Web Content articles to verify the images.
Account for Deprecations and Features in Maintenance Mode¶
If you haven’t done so already, review the deprecations and features in maintenance mode and plan for handling how they affect your Liferay instance.
Remove Obsolete Data¶
If you’re done using data that’s unnecessary and useless, you can remove it. Here are two common obsolete data situations and tools for removing the data.
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 you’ve completed all necessary post-upgrade tasks, your Liferay server is ready for normal operations as before. Congratulations!