RE: Liferay 7.4 Bundle - How to deploy from Dev to UAT then to Production

Anish Kumar, modified 1 Year ago. New Member Posts: 18 Join Date: 4/11/23 Recent Posts

Hi All,

I have downloaded Lifereay 7.4 CE tomcat bundle, and configured in the dev environment. I have customized the portal pages, System Settings, Instance Settings, look & feel as desired and deployed few custom portlets to this environment. Now the dev environment is fully customized and have to deploy to UAT server.

I am looking for a solution to move the Liferay server running in the dev to UAT server. Otherwise I have to do the all customization again for the UAT and Production.

Below are the deployment constraints I am struggling

  1. UAT Liferay portal should use a different database (PostgreSQL). We can clone the Dev database to UAT DB server. How to point the UAT Liferay bundle to the cloned database. Shall I only need to change the portal setupwizard enabled = true?
  2. UAT Liferay server should use a different SSL configuration. We can edit the tomcat web/server.xml to point to the new keystore, before starting the portal.  Is this correct?
  3. There is a property include-and-override=portal-developer.properties in the portal-ext.properties. Can we remove this line for UAT and Production? Does this cause any Issue?
  4. In dev while starting the server its showing warning about elastic search sidecar-Do NOT use sidecar in production. How I can change this for UAT and Production bundles?

I tried configuring deployment environments in the Developer studio refering below URL. The generated bundle have all the portlets in the workspace, but it doesn't have the other customizations pages, instance settings, system settings etc.. I have done for the development.

URL: https://learn.liferay.com/w/dxp/building-applications/tooling/liferay-workspace/creating-deployment-environments

Looking for a solution from the community.

Thank you

 

thumbnail
Olaf Kock, modified 1 Year ago. Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

The basic principle is in this blog article: Make sure to distinguish between system configuration, code tests, and content creation.

That being said, for an initial release, I'd recommend to restore a backup of your environment to the next higher system, then tweak there what you need (e.g. TLS configuration, host names) but don't continue this way, rather adopt the strategies that Dave outlines in his well quoted article.