Submit Feedback

Stage 4: Migrating DXP Configurations and Customizations

Now that your database and document library are applied to your Liferay Cloud environment, the next stage of migration is to migrate your on-premises Liferay installation’s configurations and custom code. This involves organizing property files, OSGi configurations, and custom modules, themes, and WAR files to the appropriate folders before deployment.

Organize Configuration Files

First, organize the Liferay configuration files from your on-premises installation you want to migrate. This includes any portal property files you are using.

Tip

Liferay-specific code belongs in the liferay folder, which is organized like a Liferay DXP workspace.

In the Liferay Cloud project repository you cloned previously, navigate to the liferay/configs/[ENV]/ folders (which correspond to your Liferay Cloud environments), and put all of your Liferay portal property files (e.g., portal-ext.properties) into each appropriate environment folder.

Put OSGi configuration files (e.g., .cfg or .config files) into a subfolder in the appropriate environment folders called osgi/.

For example, for a dev environment, put portal property files into liferay/configs/dev, and OSGi configuration files into liferay/configs/dev/osgi/.

Tip

Any files put into the liferay/configs/common/ folder applies to all environments when deployed.

When the changes are deployed, any portal property files put into the liferay/configs/ environment folders are automatically copied to the $LIFERAY_HOME folder within the liferay service’s container in the corresponding environment(s). OSGi properties are automatically copied to the $LIFERAY_HOME/osgi/configs/ folder.

Organize OSGi Modules

If you have custom OSGi modules used for your self-hosted Liferay installation, put all OSGi module source code into the liferay/modules/ folder (with the same workspace folder structure).

When the changes are deployed, custom module code is automatically compiled and then deployed to the liferay service container’s $LIFERAY_HOME/deploy/ folder.

Organize Custom Themes

Next, put the source code for all of your custom themes into the liferay/themes folder.

When the changes are deployed, custom themes are automatically built and deployed to the liferay service container’s $LIFERAY_HOME/deploy/ folder.

Organize WAR Files

Next, put all of your Liferay installation’s WAR files into the liferay/wars folder.

When the changes are deployed, WAR files are automatically deployed to the $LIFERAY_HOME/deploy/ folder within the liferay service’s container in the appropriate environment(s).

Create and Deploy a Build

Next, you must create and deploy a build with these changes to apply them to your Liferay Cloud environments.

Create a Jenkins Build with the Change

Run Git commands to submit your changes using any terminal with Git installed.

Add the changed files to Git:
```
git add .
```

Make a commit with your changes and a message:

git commit -m "Liferay Cloud Migration Stage 4"

Push the changes to GitHub:
```
git push origin master
```

Since your project is linked to the GitHub repository, pushing the changes automatically creates a build. Wait for the build to complete before proceeding.

Deploy the Build to Your Chosen Environment

Finally, use the Liferay Cloud Console to deploy the completed build to your chosen environment.

In the Liferay Cloud Console, go to the Builds page (using the link at the top of the page).
Find the build you created previously in the list, and from the Actions menu, click Deploy build to.
Select the environment to deploy the build to (e.g., acme-dev).
Read the information below and select the confirmation boxes to confirm the results of the deployment.
Click Deploy Build.

The build is deployed to your chosen environment, and your Liferay configurations and customizations are applied to the chosen environment once the liferay service restarts.