Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Liferay CE update 7.1.2 GA3 to 7.2.1 GA2
Good afternoon,Since some critical vulnerabilities affecting versions of LR 7.0 and 7.1 have been known recently and it is recommended to update to the latest version of LR CE which is 7.2.1 GA2, the state looking at the documentation to get an idea of the scope This may mean an update of this magnitude, but it is not clear to me at all what are the steps to follow.Luckily I have a virtual platform and I have a Development environment that is where I am going to perform the update tests, but the truth is that I am not at all clear what are the steps to follow, since the documentation is not clear to me each one of the steps or if the steps must be done obligatorily.Anyone who can help me to have this vision and know the steps to follow?thank you very much
1) Do everything first on a backup/clone
2) Upgrade the database. If you don't run into any problems, you are pretty much golden. If not, you either need to fix the issues, find workarounds, ask in the forum, ...
3) Upgrade your modules
This one really depends on the features you use. For some modules it can be sufficient to just update the dependencies in build.gradle. Others will have to be changed in some way. This one really depends on your code and what you did. Do it one by one, upgrade dependencies, deploy, does it work? (Yes -> all good, no -> Fix things)
4) Test.
2) Upgrade the database. If you don't run into any problems, you are pretty much golden. If not, you either need to fix the issues, find workarounds, ask in the forum, ...
3) Upgrade your modules
This one really depends on the features you use. For some modules it can be sufficient to just update the dependencies in build.gradle. Others will have to be changed in some way. This one really depends on your code and what you did. Do it one by one, upgrade dependencies, deploy, does it work? (Yes -> all good, no -> Fix things)
4) Test.
Hi Admin Cauce,
Christoph is right, the documentation tries to cover all aspects but it's not complex to execute the upgrade. Read the different sections and discard the ones don't affect to you. At the end it's basically as Christoph explained. I recommend you to use the Liferay IDE and the Upgrade Planner to complete it, they are really helpful.
Cheers!
Christoph is right, the documentation tries to cover all aspects but it's not complex to execute the upgrade. Read the different sections and discard the ones don't affect to you. At the end it's basically as Christoph explained. I recommend you to use the Liferay IDE and the Upgrade Planner to complete it, they are really helpful.
Cheers!
Good morning and happy new year first of allThank you very much for the answers!What is still not clear to me is the following. On the server where I have installed version 7.1 of Liferay, I download and also upload the new version 7.2. And inside this new version 7.2, launched the process that they tell me about updating the database, located in [liferay] /tools/portal-tools-db-upgrade-client/db_upgrade.sh
From what I have seen this process is asking you a series of routes and parameters that you will have to set manually. Once this process of updating the database is finished, I will be able to start Liferay but from the new route where version 7.2 is deployed and then as they say, I deploy the developments we have made.Am I on the right path or have I been wrong at some step? I understand that I do not have to duplicate the database in another database, but that the process itself is responsible for adding the corresponding connections in the portal.properties file in the new version of LR.Thank you very much in advance.
From what I have seen this process is asking you a series of routes and parameters that you will have to set manually. Once this process of updating the database is finished, I will be able to start Liferay but from the new route where version 7.2 is deployed and then as they say, I deploy the developments we have made.Am I on the right path or have I been wrong at some step? I understand that I do not have to duplicate the database in another database, but that the process itself is responsible for adding the corresponding connections in the portal.properties file in the new version of LR.Thank you very much in advance.
Hi Admin,You have to configure the portal*.properties by yourself. For the upgrade you have to configure the portal-upgrade-database.properties pointing to your old schema (do a backup first). When the upgrade finishes you can start up the Liferay 7.2 server but first you need to configure the portal-ext.properties ad you did in 7.1. That's all.
I hope it helps.
Best regards.
I hope it helps.
Best regards.
Hi AlbertoThank you very much for the answer. I have followed the instructions and everything seems to be that it has come out correctly, or at least it is what I want to understand that it has been so. I have reviewed the file "upgrade.log" which is where the trace of the process of "db_upgrade.sh" is seen and in principle I do not see anything strange that some error. I do not know if in case the update process failed, write something informing you of the error at the end of the file.
Done this and checked, I have started the Liferay server in the new installation, and in principle it has raised everything correctly and without errors. Logically, now we just need to deploy all the developments that have been implemented, in this case, the area development has implemented JSON webservices, theme and portlets. I understand that failure will simply load scrolled and see that everything correctly.
Now the million dollar question,For a cluster environment, would the process be the same or should something else be taken into account?
I have been reviewing the official documentation, and I don't see anything related to processes of updating to version 7.2 of a cluster mode environment, instead of a standalone environment like the one I have mounted in the development environment.
The steps to take would be the same, or do you have to take into account something that can escape me !?Thank you very much in advance.
Done this and checked, I have started the Liferay server in the new installation, and in principle it has raised everything correctly and without errors. Logically, now we just need to deploy all the developments that have been implemented, in this case, the area development has implemented JSON webservices, theme and portlets. I understand that failure will simply load scrolled and see that everything correctly.
Now the million dollar question,For a cluster environment, would the process be the same or should something else be taken into account?
I have been reviewing the official documentation, and I don't see anything related to processes of updating to version 7.2 of a cluster mode environment, instead of a standalone environment like the one I have mounted in the development environment.
The steps to take would be the same, or do you have to take into account something that can escape me !?Thank you very much in advance.
Attachments:
Hi Admin,
Congratulations, the upgrade seems to have finished properly :-)
The upgrade process is the same for cluster environments since it just works with the database. You just need to set up your cluster after the upgrade process.
Cheers!
Congratulations, the upgrade seems to have finished properly :-)
The upgrade process is the same for cluster environments since it just works with the database. You just need to set up your cluster after the upgrade process.
Cheers!
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™