ServiceNow connector deployment guide

Difference Between the Liferay 6.2 and Liferay 7/DXP

  1. Basic Difference Between the Liferay 6.2 and Liferay 7/DXP



Liferay 6.2

Liferay 7/DXP


Modularity Development

Liferay 6.2 partially support and it’s an experiment and it need more effort to achieve the modularity.

Liferay 7 support modularity development using OSGi framework.


Bootstrap Version

Support Bootstrap 2 UI framework.

Liferay 7 support Bootstrap 3 UI framework.


AUI Version

AUI 2.x components are used.

AUI 3.x components are used.


Application Development

Liferay Application Development based on Plugins.

Liferay Application Development based on OSGi bundles.


Enterprises Editions name

We simply call Liferay 6.2 EE or CE

Liferay 7 EE called Liferay DXP


Application Packaged method

Liferay Applications packaged as war files and deployed in traditional application server.

Liferay Applications packaged as OSGi bundle jar files and deployed in OSGi container. It support WAR deployment as well.



Liferay 6.2 core portal and its default portlets all available in ROOT directory and deployed in Application Server.

Liferay 7 separate core portal and its default portlets. Core portal only have core features rest of features made it as portlets and packaged as bundles. Core portal files in ROOT directory deployed in Application Server. All portlet bundles available in data/OSGI directory. It means bundles deployed in OSGi container.


Search Engine

Liferay 6.2 in built search engine is Apache Lucene. Liferay 6.2 have SOLR web to enable SOLR search.

Liferay 7 inbuilt search engine Elastic Search. It support SOLR search as well.


Single Page Application

Liferay 6.2 does not have inbuilt Single Page Application support but we can integrate SPA framework to achieve it.

Liferay 7 have Single Page Application inbuilt support using Senna.js


Build tools Support

Liferay 6.2 support MAVEN, ANT.

Liferay 7 support MAVEN, GRADLE build tools.


Application development tools.

Liferay 6.2 have Plugins SDK Command Line Interface to create portlet, hook, theme and layout.

Liferay 7 introduce new tool called BLADE CLI to develop Liferay 7 Application as bundles. Internally its uses the Build tools GRADLE flavor.


Activate/Deactivate Application

Liferay 6.2 it is not possible. We should un-deploy the plugins from the server so that we can remove the unused features.

We can activate/deactivate Liferay Application Bundles simply using Apache Gogo shell Command Line Interface without un-deploy the bundle from the container.


Languages For UI

Liferay 6.2 does not have design languages like Clay and Lexicon. But it supports all necessary UI Languages like HTML, CSS, Bootstrap, JQuery, Alloy-UI etc

Liferay 7 have introduced Clay and Lexicon language to design UI. Lexicon is a design language that provides a common framework for building interfaces. Clay is web implementation of Lexicon.It’s built with HTML, CSS, and Javascript with Bootstrap as a foundation



Not So flexible environment, we need to perform code changes for any single change. like We cannot deactivate default portlets without change in the code.

Provide more flexible environment like We can easily deactivate default portlets if we are not using. We simply deactivate portlet bundle.