Q:- Liferay Code migration process from 6.2 to 7.1/DXP

 Liferay Code migration process from 6.2 to 7.1/DXP

---------------------------------------------

Step1:-Remove unused objects

Sites

Remove unused sites and it’s content.

Instances

Remove instance which is no longer needed. Since they consume highest object in the hierarchy, removing it can optimize upgradation process.

Web Content

Liferay generates a new version whenever we are updating any web content. You can safely delete all older versions of web content.

Users

Remove all inactive users and it’s related data to optimize the process.

Layouts

Remove unnecessary layouts.

Step2:-After removing unused objects from your portal, make sure to test those in your older environment.

 In that case, you can more easily find out any issues, knowing that they’re not related to upgrade processes

Step3:-Liferay Database migration

Step4:-Code migration

Once your database will migrate to DXP you need to update your existing code to make it compatible with DXP. Liferay provides code upgrade tool for it.

You can follow LR’s documentation to upgrade your existing code to LR DXP

Step5:-Change in Deployment Process

As we know Liferay DXP adopted OSGi framework container which is based on modules based application.

Due to this reason deployment process in LR has been changed.

Step6:- Post-migration issues

Here I’ve added some of the common post migration issues which generally happen.

1:-You must first upgrade to Liferay Portal 7100

This exception will be thrown when you started LR 7.x with 6.x database.

To resolve this issue you need to re-run the database upgrade tool before starting LR DXP.

2:-PwdEncryptorException: invalid keyLength value

You will face this kind of exception when an incorrect password encryption algorithm.

To resolve this error you need to add below property in the portal.properties file.

passwords.encryption.algorithm.legacy=SHA.

STep7:-Search Engine

From Liferay DXP, they have integrated elasticsearch as an embedded search engine.

For production use, Liferay only supports Elasticsearch when it runs in a separate JVM