Liferay Digital Experience Platform Reviews

• Support OSGi Framework
• Excellent Content management system
• Administrative functions through the control panel
• Elastic search

These features are valuable because they all are basic requirements for all portals and have been achieved easily with the Liferay DXP portal.

You

Very important changes are OSGi modularization for existing portlets and new modules. It change the way of development and make life easy for developers

I have been playing liferay from last 9 years and palyed almost all the version and have seen many pros and cons across versions.

Yes we faced many issues during production deployment and specially performance tuning and best suppoprt architecture.

Yes as this is open source so don't see its big hurdle here.

I have not encountered any scalability issues.

10/10

Technical support is very nice for the EE customers.

I did not previously use a different solution.

If its first time then you will definatly struggle but later on it would be very easy if you understand the structure.

It should maintain a competitive price in the open source market.

Before choosing this product, I did not evaluate other options.

It is just awesome; you should experience DXP. I am blogging many useful solution on www.liferaysolution.com

The features I find valuable are its integration points with other systems and scalability. This is important because the portal (Liferay) is an addition to the current J2EE Framework. That being said, it lends itself to roll all processing (Spring batch) into the Liferay Tomcat bundle. This process can be done in reverse order to ensure performance.

For integration points using simple plugins with SAP, you can create your own secure service bus for information. If you would like to convert your Liferay platform to a presentation layer for CRM, you can leverage Dynamic MS CRM or SugarCRM with ease using plugins or a Java framework.

Our organization benefited by the automated client setup and an easy CMS setup.

Major upgrades switch the Liferay framework core structure dramatically in EVERY occasion. However, there were only subtle changes from the last minor upgrade to the major upgrade.

I used this product for two years where I currently work. In my former job, I used it for six years.

I have encountered stability issues during the upgrade process from 5.2 EE to 6.1.XX EE. There are always issues with Social Office.

We had no scalability issues.

The technical support need was moderate as the tool lends itself to be customized away from the (out-of-the box) OOB portal product. Liferay does not always support these custom components.

We used ColdFusion for a previous project for a CMS portal.

The installation was simple on a Linux-based operating system. It was complex with Windows Servers, but we still managed.

We recommend never leveraging static components when developing licensing requirements because the operating system layer and its environment will always change to fit support costs.

We did not evaluate alternative solutions.

Make sure you understand what you want the product to do. If your company has an overall future for growth, then Liferay is a good choice as it is an enterprise solution.

We have two primary use cases for this solution between two installations. One is being used as a national business portal, and the other is used as an archival and preservation system.

The most valuable features are the content manager, where you can configure events, the archival and preservation feature, and the workflow feature where before the document is scanned and awaiting approval to be archived, the chief archivist can provide an opinion of whether the content is of preservation value or archival value. He puts a comment in the workflow.

We chose Liferay because it is open-source and that we can make any number of users apply, register into the system and use the system, as opposed to other solutions where the cost is based on user licenses.  This is one of the most attractive features.

The integration area needs to be improved. It needs to be more user-friendly.

The integration and configuration need to be simplified. If for example, I had to configure the application to a payment module, especially in the business licensing system, it would be better if we could have a feature that would require less code to enable easy integration with other systems.

The end-user requires training, some knowledge transfer is needed. It has been proven to be a challenge, because we don't have any in Tanzania, and we don't have a data center for Liferay.

In the next release, the integration capabilities need to be easier to use by someone who is not as technical. Also, when it comes to troubleshooting, the logs need to be published on a page that's easier to use rather than going to a folder somewhere.

I have been using this solution since 2016.

We are using Enterprise Edition 6 and I know that it is not the latest edition available, but so far, this edition of this solution is stable. We have not experienced any issues. Later, with an increased number of users, there may be some issues. We don't know, but for now, it's good.

Anyone in Tanzania who wants to register for a business license has to log into the system. There are many users. Just to give you some statistics 30,000 people have applied for business licenses and 8,000 have been issued. The remainder 20,000+ are waiting for their applications that are still in the workflow.

The reason Liferay Digital Experience was chosen over other products was the fact that we did not have to pay for user licenses. Liferay supported an infinite number of users.

The business case for the application was the business community in Tanzania to be able to register in the portal and apply for a business license. So however much the users of the system grow we are confident Liferay shall handle the load without any issues

So in terms of scalability, my answer is that Liferay is okay.

In terms of hardware we have multiple servers. The setup we had was for purposes of having improved responsiveness and availability.

We have not received support from Liferay because we have done everything through the integrator. We would prefer to have our people trained than getting support from Liferay itself.

This is something we are working on at the SLA level.

As a national business portal, it is used as a content management solution and we have not used any other solution. For the archival and preservation system, we used an application called Saperion Enterprise Content Management System. 

When compared to Saperion Enterprise Content Management System it can support more users without having an impact on the cost. That was favorable for us because we need any researcher anywhere in the world to be able to access the Tanzania  National Archive without having any cost on the software. We chose Liferay mainly because of that.

Based on the document specifications, it was time-consuming because of the nature of the deployment. 

Before even looking at Liferay, the system requirements took six months because we use different stakeholders from different government institutions and other stakeholders from the private sector. 

The configuration of Liferay took six weeks.

Another task that took a lot of time was deployment because once it was set up, different people had to start testing the application. This took a lot of time because all of the different stakeholders had to be given time to test it. 

Overall, it took a year, with ten staff to deploy and maintain.

We haven't had any issues with our deployment of Liferay.

We used Melink to help with the implementation. The experience with them was fair.

It's an open-source structure.

The licensing cost was a one-off. Other costs are for professional services to integrate Liferay to other existing systems. Those are the main costs and also costs related to deployment, setting up the load balancing, and later on having to configure the disaster recovery site. These are all related costs to the deployment of Liferay in different scenarios.

We knew of applications like Drupal, but we did some research through Google. We settled on Liferay because of it's open-source functionality and our end-user was keen on getting an open-source platform. It was exactly what Liferay offered.

We didn't have extensive comparison tests with other platforms or applications.

With any application, the number one thing is to get the requirements-gathering stage done well, to identify your requirements to do your analysis properly.

The requirements gathering needs to be very thorough and all-inclusive. All stakeholders need to be involved.

Get a good company for the implementation.

You must have the proper hardware sizing.

I would recommend Liferay for any company that is looking at deploying an enterprise-wide content management system. I would recommend Liferay any day, anytime.

I would rate this solution a seven out of ten.

Aggregation and personalization (think dashboards) are the really unique selling points of a portal. If you don't need those, you don't need a portal and there will be other libraries or frameworks that are better suited to solve your problem.

We are not really using it ourselves.

The easy, straightforward cases are usually the only ones that are documented. Once you need to do something a little more advanced, you usually won't find any examples and will have to resort to looking through the code to find a place where they do something similar and figure out how it works by stepping through that in a debugger.

They also really like to create new libraries to do stuff (AlloyUI, Metal.js, Senna.js, etc.) instead of seeing what is already available and trying to adapt that for portal use (and possibly committing that back). And lastly, we've run in to a lot of bugs that tend to come back in every version. Things get fixed in one version and after upgrading you run into the same bug again.

I have about 8 years of experience with the product. I've worked with late 5.x versions up until the 7/DXP version now. I'm also a Liferay Highlighted blogger (https://web.liferay.com/web/fimez/blog) and I presented at Liferay Devcon last year.

We didn't encounter any real stability issues, only regressions and bugs.

We didn't encounter any real scalability issues, only regressions and bugs.

Technical support is better than most.

We previously used Sun Java System Portal Server. We switched because Sun Portal just plain sucked.

Initial setup is as easy as downloading, unpacking and starting. No hassle.

Always use the Enterprise Edition, as it isn't worth your own time to try and hunt down bugs in the Community Edition, and there are lots of bugs/regressions.

We looked at JBoss Portal and Pluto.

Only use it when you really need a portal and don't use it as an application framework. In that case, it only complicates your development and performance needlessly.

We tried the 'eat your own dog food' approach and used Liferay for our company's website, but Liferay just isn't meant to build websites. It wasn't easy/simple enough for normal web content editors to add or change content. It is also hard for our designers to create cutting edge designs that can be easily integrated into Liferay as a theme.

All the features that are provided by Liferay are very useful, such as Web Content, Document Library and Media, Roles, Permissioning, Resources, Organizations, Users, Sites, Custom Fields, Plugins, and so on. These features enable us to extend Liferay functionality and allow us to customize the out-of-the-box features of Portal to meet our customers’ requirements.

We are using it for projects to provide quick turnaround for our clients' requests. Liferay has a powerful feature for the hot deployment of plugins, and service builders for easily creating tables using Sprint, Hibernate, JPA, etc.

I would like to see them arrange more symposiums in India, because most of the resources who work on Liferay are from India, more than any other country.

I'd like for them to have more interactive sessions, training or face-to-face meetings with the Liferay core team for Developers, so that we can have our questions/clarifications clarified directly with them, rather than asking over a webinar session, through forums, through support tickets, etc.

I have been using Liferay for the past 10+ years now and I love to work with it.

I have not encountered any serious stability issues, but if we come across anything, we get great support from Liferay as a patch.

The portal is very easy in terms of adding more nodes to a cluster.

Technical support is 9/10.

I have used two other portal servers. I really did not like the way they allowed admins to do administrative actions. Liferay is easy to understand and complete the admin actions through the control panel with meaningful names and a short description about what each module does.

Initial setup is straightforward and I did not find it difficult. Liferay has great online documentation, which gives us more confidence in achieving anything with it.

It is a budget-friendly solution and less expensive than any other portal servers available on the market.

Go with this product, because there is great support from the company, rich forum support and online documentation, and the source code allows you to make changes on your own with an LGPL license from vendor.

We like Likeray because it's a secure platform.

The look and feel and the user interface are great.

PHP offers more plugins than Liferay. The plugins should be more affordable.

Liferay needs to offer more in terms of updates and development. WordPress is constantly offering new updates and new features; I hardly see that with Liferay — although, it could be because we don't have an enterprise license.

Also, an e-commerce plugin tool would be a nice feature. 

We have been using Liferay for at least three years.

Compared to WordPress, I hardly experience any issues or bugs.

For us, the initial setup was very complex — It's in Java. In Malaysia, there are not a lot of Java writers or developers.

Licensing costs can be very expensive.

I would recommend Liferay to another company, but the price cannot be overlooked. Maintaining a license can be a hefty investment.

Due to the licensing and plugin costs, on a scale from one to ten, I would give this solution a rating of eight.

• CMS lets business users to create and manage web content by business users, while maintaining revisions. Liferay enables users to be independent of developers and to be able to manage content within the portal.
• Roles and permissions management gives developers the ability to build persona- and preference-based functionality within the portal.
• Document library
• Plugins, workflows and rules provide flexibility to customize the portal.

• A self-service portal for customers
• An online community to share and get knowledge
• A portal for distributing manuals.

• Ability to create content
• A cloud offering

I have used Liferay for approximately five years.

Liferay is a very stable product (except for version 7, as it is relatively new).

We have no issues with scalability.

Technical support is very good.

We started using Liferay directly. There was no previous solution.

Setup was straightforward.

It is very affordable and licensing is similar to Red Hat Linux, where we pay only for the support.

We evaluated Adobe Experience Manager and WebSphere Portal v6.

Have a complete understanding of out-of-the-box features as Liferay makes most of the functionality required available without any customization.

Liferay is a good product and can reduce time and cost on project implementation. Liferay opens the door for most problems of our customers. If you have digital problems in your organizations, Liferay already solves more than 80% of them.

Most of my Liferay experience is working on projects to solve other organizations’ problems and meet their requirements. With one of our projects, I used Liferay as a document management solution. With Liferay, users are happy with its ability to manage digital documents.

I would like to see an improvement on the Ecommerce platform.

We have used this solution for over five years.

I did not encounter any issues with stability.

I have experience on enterprise and community versions with HA implementations for less than five servers. So far, I did not face any scalability issues.

I would give technical support a rating of 9/10.

We used Microsoft SharePoint and IBM WebSphere. They are not straightforward and have a complex user experience as a developer.

The setup is straightforward.

The solution has a good ROI.

The solution is inexpensive.

I suggest getting this product. It is easy to use and has a big impact to reduce implementation time. It is not just a product solution. It also has excellent features as a development platform.