Legacy Knowledge Base
Published Jul. 2, 2025

Restoring Testing Environment to Match the Production Environment

Written By

Christopher Lui

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.
Often times, you will need to change your testing environment to be the same as your production environment for your Liferay Portal. The following article outlines some guidelines for restoring your testing environment to match the production environment in a successful manner. Please note that these are merely guidelines and certain situations will require additional action steps.

Resolution

Follow these steps before restoring your testing environment to match your production environment. If there are any additional aspects of the restoration that you are unsure of, you can open a Help Center ticket.

  1. Before you do anything with either environment, backup everything. This is for safe measure in case something goes wrong.
  2. Make sure that the databases, documents, and images are updated and in-sync. This means that the ones that you use from the production backup are all taken at the exact same time. If they are out of sync, you run the possibility of not only losing important data but also encountering issues in Liferay when expected data is not found.
  3. Portal-ext.properties must be the same for the test and production environments with the exception of production environment data such as, Liferay home, document library location, database connection settings, cluster settings, etc.
  4. All portlets, themes, and additional customizations should be deployed with the latest versions, being careful to match the same versions found in the production environment.
  5. Make sure that any configured mail server settings are removed or changed to be different from the production environment. This is to prevent sending email from the wrong portal.
NOTE: Several Liferay Portal settings can be saved in both the portal-ext.properties file or the Control Panel (such as mail server settings). In addition, application servers can be configured in such a way as to affect Liferay Portal's functionality (mail server and database configuration, SSL). As such it is very important that the production's full environment be carefully reviewed to ensure that the desired settings are fully transferred over to the testing environment with special attention paid to the application server and the Control Panel.
Did this article resolve your issue ?

Legacy Knowledge Base