Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Deployment issues using the App Manager in Liferay PaaS

Written By

Jose Jimenez

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

You upload an application/plugin using the App Manager in DXP and you only see that it is deployed in only one instance, and from time to time, you even lose the application in that instance.

Environment

  • All Liferay DXP versions running on Liferay PaaS

Resolution

LXC-SM relies on the Liferay workspace and a couple of different deployment strategies to update running instances: direct deploy using the LCP/cli tool or the preferred one, a new build and the Web Console.
  1. Copy the application to the liferay/configs/{ENV}/deploy/ folder of the Liferay Workspace ({env} will be the specific environment name: prd, uat, dev...) or the liferay/configs/common/deploy/ folder if you want to deploy the application in all the environments in where the Liferay service is.
  2. Deploy the changes, the preferred way is via a new build and the Cloud Web Console, and the recommended for production updates. This option allows to have a complete photo in a single build of the full stack that is going to run which can be used to easily replicate the environment in case of need.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?