Upgrade Stability and Performance
When you upgrade a DXP instance for a production release, the data upgrades must be done correctly and swiftly. Here are some ways to help assure success:
- Create a test environment that uses copies of your database and installation
- Prune unnecessary database data to improve performance
- Tune the database for upgrade operations
- Upgrade the database and troubleshoot upgrade issues
- Test the upgraded database with DXP
Creating a Test Environment
It’s important to test upgrading in an environment that separate from production but that uses the same data, configurations, and apps. You can use copies of your installation (Liferay Home), database, and Marketplace apps. These should be readily available from your backup.
Pruning Unnecessary Data
If you actively update your DXP sites, it’s likely that there’s data you no longer need. This can include sites, roles, or organizations you’ve stopped using or revisions of content you no longer need. Deleting unneeded entities and data related to them can save you upgrade processing time. For more details, see Database Pruning for Faster Upgrades. And make sure to also check out the Example: Removing Intermediate Journal Article Versions.
Tuning the Database for the Upgrade
DXP upgrade processes write to the database more than is typically done in production. You can optimize your database for write operations. For guidance, see Database Tuning for Upgrades.
Upgrading and Troubleshooting Issues
After you’ve pruned and tuned your test database, upgrade it using the database upgrade tool. If you run into problems, such as unresolved dependencies, you can examine the logs and use Gogo shell commands to troubleshoot issues and complete the upgrades. Visit Upgrading Modules Using Gogo Shell to learn how.
Testing the Upgraded Database
Lastly, take time to test your DXP instance with your upgraded database.
After you’ve upgraded your DXP instance successfully, you can orchestrate releasing it to production.