Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

How to find whether the Liferay bundle is Community Edition or Enterprise Edition

Written By

Sivakumar Perumal

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.

Issue

  • How to find whether the Liferay bundle is Community Edition or Enterprise Edition

Environment

  • Liferay Portal 6.x
  • Liferay DXP 7.x

Resolution

  • There are four ways to find whether the bundle is CE or EE:
    1) Check if the bundle is having the patching-tool folder in the Liferay home folder. If it is present then it is EE, if not its CE.
    Note: The patching tool folder will not be available for the manual installation of Liferay.
    2) While starting the server, you will see the version in the server console.
     
    Starting Liferay Community Edition Portal 7.2.0 CE GA1 (Mueller / Build 7200 / June 4, 2019)
    Please refer the below attachment.
    untitled.png
    3) Start the server, if the portal can be accessed without deploying the license, its CE. If license is required to access, its EE.
    4) If the server is running, drop the Hello World portlet on the page. It shows the exact version of Liferay.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?