Legacy Knowledge Base
Published Jul. 2, 2025

How to successfully install Marketplace Apps when using Liferay PaaS

Written By

Isaac Wilson

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.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • While using Liferay PaaS, what is the process to install an application from web.liferay.com/marketplace? When I install an App through the portal's UI in Control Panel > Apps > Purchased, the application is no longer installed after restarting the Liferay service or deploying a new build

Environment

  • Liferay PaaS
  • DXP 7.x

Resolution

  • To install an App from Marketplace when using Liferay PaaS, and have the installation persist across restarts, the following steps must be performed:
    1. Navigate to web.liferay.com/marketplace, click the user icon in the top right, then select "Purchased Apps" to select the icon of the desired App to install (within your project)
    2. Click "App" next to the appropriate Liferay version to download the corresponding .lpkg file
    3. Add the downloaded app to the desired environment in your Liferay Experience Cloud SM project's working repository (for example, [Repository_Name]/lcp/liferay/deploy/common when using the 3.x.x workspace, or [Repository_Name]/liferay/configs/common/deploy for a 4.x.x workspace)
    4. Create a new build with those changes, then deploy that build

       

Additional Information

  • Including the .lpkg file within the build is necessary because each restart of DXP while using Cloud will essentially start a new clean image, which consequently wipes out the installation of the desired application (as it is not included in the base image)
  • For similar reasons, if the Liferay Marketplace.lpkg is ever out of date and a new version is required, it will also need to be manually installed (instead of automatically installed by clicking the "Update" button in the UI), as a successful update will initiate a restart of the portal.
  • More information on creating and working with builds can be found in the following articles:
  • Deploying Liferay SAML Connector in Liferay PaaS
Did this article resolve your issue ?

Legacy Knowledge Base