#Liferay Named a Leader in Portals for the Sixth Year

As one of Liferay’s proud Platinum partners, we are thrilled to see it named a leader in Gartner’s Horizontal Portals Magic Quadrant. Liferay Inc., which makes open source portal software, is a Leader for the sixth consecutive year and positioned furthest in completeness of vision and ability to execute in the Leaders quadrant.

Gartner, a leading information technology research and advisory company, positioned the evaluated vendors in the portal market based on independent research and analysis.   The Magic Quadrant gives enterprises a way to assess how well technology providers are executing their stated visions and how well they are performing against Gartner’s market view.

According to Gartner, “the past five years has witnessed a massive transformation of the market for horizontal portals. The nexus of mobile, social, cloud and information has at once heightened the demand for this ‘personalized point of access.’

Liferay will be showcasing its award-winning portal technologies at the annual Liferay Symposium North America, held November 16th and 17th in Chicago. Attendees representing businesses in several verticals will find strategies for increasing enterprise productivity, mobility, and audience engagement from over 60 available business sessions, case studies, and technical workshops

Veriday will also be in attendance at the Liferay Symposium as an event sponsor. As a dedicated Liferay technology partner, we look forward to this event to learn more about the latest and greatest innovations Liferay has to offer.

To lean more about Liferay, visit www.liferay.com.

A Recap of Veriday’s 1st Liferay Meetup


Veriday held its 1st Liferay Meetup on August 18th, 2015 at our new office location. It was a successful evening full of great people, food, refreshments, and insightful presentations on Liferay. A big thank you to Chris Lamoureux, Patrick Lafond, Scott Ord & Nick Quach for sharing their insights and wisdom on everything from Liferay Inc. to user experience design to agile development.



For those of you who missed it, here’s a quick recap of the night:

Nick Quach, VP of Technology and Solutions at Veriday, got the evening going as the first presenter of the night.  Nick spoke about Liferay as a System of Engagement, a term coined by Geoffrey Moore, a business author of such books as Crossing the Chasm. Nick discussed Systems of Engagement and the transition from current enterprise systems to systems that are focused on human culture, communication, and peer interactions, as opposed to processes. Systems of Engagement focus on a totally new user experience. Nick’s discussion highlighted how many enterprises are turning to Liferay to provide an effective System of Engagement in order to more effectively systematize their organization.

The next speaker up was Patrick Lafond, a Solutions Engineer at Veriday.  Patrick presented an insightful presentation on Liferay as an Integrations platform. Patrick focused on sharing some of his observations and experiences using Liferay as an integration platform (both providing and consuming web services).  Patrick’s background in Enterprise Integration provides a unique perspective on an implementation pattern commonly used in a Portal ecosystem. His discussion highlighted that Liferay provides developers the ability to leverage numerous tools, libraries, and frameworks in order to quickly and easily integrate with many diverse systems.

The 3rd presenter of the night was Scott Ord, a senior consultant at Veriday. Scott discussed “3rd Party Integration with Liferay”.  Scott covered 3 different means to add the necessary files to Liferay based on the type of framework (front MVC or front-end presentation).

Chris Lamoureux,  co-founder and executive VP of Veriday, closed off the evening as the last presenter. Chris spoke about his experiences working on many Liferay projects over the years.  Chris discussed, through his experiences, how Liferay has consistently streamlined the development process, from design to deployment, and as a result of Liferay’s efficiencies, saved enterprises significant time and money.


If you’d like more information on any of the presentations, feel free to get in touch with us and we will be happy to help.

Join us for our next Liferay Meetup, and a great night of food, refreshments, networking and all things Liferay.  The next event will take place at the end of September. More details are to follow, or feel free to sign up for our newsletter to receive updates right to your inbox.

Turn Your Website Into a Hub for Engaging Experiences

This post was authored by Angela Wu and originally appeared here on Liferay.com


In the digital age, companies are learning fast that meeting customer expectations and driving business outcomes go beyond brand recognition or product availability.

Managing digital expectations may seem daunting; however, it’s clear that companies that understand their buyers and create consistent experiences across channels will more successfully attract, engage, and retain customers.

In light of this, we asked Bryan Cheung to share his thoughts on the digital consumer, data-driven marketing, and building better web experiences.

Q. How do you customize a web experience for today’s digital consumers whose backgrounds and interests vary?

BRYAN CHEUNG: Today’s customers expect to be addressed “Audience of One”: they want to be the center of your digital attention. Personas, segments, and rules are a great start but the ultimate goal is to understand each person’s need at any given moment.Q. How do you customize a web experience for today’s digital consumers whose backgrounds and interests vary?

People interacting digitally tend to be more transactional and purpose-driven than in traditional marketing, which means less browsing and more doing. They’re looking for specific information, educating themselves about you and your competitors, or gaining understanding of a problem. It’s important to create continuity across channels: if someone is trying to execute a transaction on a mobile app, then switches to your website, do you let them continue where they left off?

Lastly, using digital tools and technology help tailor their experience. By looking at their search terms, click behavior, and level of engagement—how long they stay with you—you can figure out what they’re looking for and deliver exactly what they need.

Q. It sounds like you’re talking about the Buyer’s Journey. Do you take that into account when creating web content?

BC: Yes, the Buyer’s Journey is a concept that we use to help understand the path a lead takes on his/her way to becoming a customer, partner, advocate, star employee or some other role that’s important to your organization. Of course, there’s no single journey for everyone, and buyers tend to jump all over the place. However, modeling the journey can still help you accelerate the development of the customer’s relationship with your organization.

Then, the short answer is this: it helps to write your content with the Buyer in mind. They’re not going to want to hear about competitors or detailed technical specs in the beginning when it’s important to show empathy for their problems rather than the superiority of your solution. Later, as you build trust and credibility, you can be more confident and assertive in presenting your products.

Your site should also be designed to be flexible and dynamic, so that the most appropriate content for what the users need can be presented on any visit. The front page isn’t the single entry point for visitors; they’re going to find most content on your site through searches and social referrals.

Q. Data has been called the new oil. Where do you begin in knowing what to measure?

BC: At Liferay, we try to identify the inflection points that make the biggest impact on Buyer Journey acceleration. We start with a theory on which digital touchpoints indicate readiness to engage at the next stage; there might be one key touchpoint or several that work in tandem. Once we’ve run the model for a long enough period that covers the sales cycle, we test our assumptions and see whether those inflection points were indeed influential.

Sometimes your data gives you very obvious conclusions, but it’s usually more nuanced than that and requires deliberate and prolonged attention. You should hire dedicated data analysts and give them enough leeway to find the insights in your data.

Q. Tell us about the roadmap for mobile content and design.

BC: We’ve been building a lot of exciting mobile-related capabilities into Liferay, including adding targeted content to native mobile apps and supporting mobile push notifications. We work with the worldview that digital platforms are inherently omni-channel. Users are going to start their journey on the web or mobile but quickly switch to in-store or phone-based interactions before completing their journey, for example, on a tablet or at a digital kiosk. So Liferay is trying to make it easy to connect those dots together into a unified journey.

Liferay Vs. WebSphere: Support and Community Examined

Why is Liferay accelerating in the Gartner magic quadrant and why are so many medium to large enterprises continuing to adopt open source products? Has open source software now become the preferred choice for enterprises? According to a Black Duck Software report, over half of all enterprises will utilize or contribute to open source in some manner in 2015.

This is the 2nd Infographic in a series that provides side by side comparisons of Liferay Vs. Websphere, examining different aspects of the Liferay and IBM portal products. The first in the series examined “Liferay Vs. WebSphere: total cost of ownership”, while this article will examine the support and community aspects of both portal products.

Liferay Vs. WebSphere: Support and Community Examined




  • Liferay Commercial offering provides the same level of support as what enterprises would expect from companies such as HP, IBM and Oracle.
  • Gartner reports have recognized Liferay as having a higher customer satisfaction in this space.
  • Security patches and fix packs are regularly provided to ensure the product remains secure, as new threats become known.
  • 24x7x365 support is available to all commercial clients.


  • Liferay is a strong and vibrant open source community with a development network that continues to grow.
  • Liferay has a strong community with roughly 4 million downloads.
    • 80,000 per month
    • 350,000-500,000 worldwide deployments
    • Over 19,000 registered users on liferay.com
  • The number of contributors (over 15,000), available documentation and available partner channels provides additional support on top of the Liferay commercial support offering.



  • IBM is a world-class product company, which provides support for its products and customers.
  • IBM provides extensive Web-based support.  Download fixes, search on keywords and find how-to information to help solve your challenges.


  • Today, more then 100,000 clients globally are using IBM WebSphere to build and integrate their infrastructure solutions.
  • WebSphere has more then 800 IBM Business Partners worldwide supporting it with software, solutions and services. It supports more than $1 quadrillion worth of business transactions daily.
  • WebSphere is used in B2C (approximately 75% of deployments) and B2B (25% of deployments) organizations.

5 Things to Consider When Purchasing Portal Software

This post was authored by Martin Yan and originally appeared here on Liferay.com

It’s not easy shopping for enterprise portal software. There are many factors to consider such as reliability, long-term costs and the ease of development. Not to mention things like meeting compliance standards or working with a customer service team that actually cares about your needs.

Regardless, the goal of any sensible organization is to maximize business value by reducing costs and mitigating risks. Here are five specific things to look for when evaluating the right portal vendor for your project:

1. Keeps it simple yet robust

Many enterprises are saying goodbye to the complex and monolithic systems of old. Instead, they are looking for something that is lightweight and feature-rich. They want a product that has the ability to evolve with business needs, which means having built-in expansion features like microkernel architecture and plugins. Having a tool or product that is simple yet robust lends itself to a rich user experience and ease of integration with other technology.

2. Makes it easy to consume relevant content

This is becoming all the more important as demand grows for personalized user experiences. A good portal infrastructure should allow new features and services to be added into the existing infrastructure. It should provide authentication, authorization and role-based content delivery (RBCD). This means that users receive content unique to them depending on their roles and permissions.

3. Combines content, portals, and apps

Not too long ago, portals were thought of mainly as a channel for a specific web experience (think employee portal) alongside other siloed products. App platforms were used to build individual apps. However, many modern portals now include a full workflow enabled WCM system as well as social collaboration and app platforms.

4. Addresses both the enterprise and department

In the past, it was not uncommon for companies to use different sets of software for various enterprise-wide and departmental projects. For instance, a company might use IBM for an enterprise implementation and Microsoft SharePoint at a department level. Now, trends are pointing towards products that can service both solutions—a scalable product that allows for code and feature reuse.

5. Allows you to code and develop as you choose

Java or PHP/Ruby? Spring or EJB? Eclipse or Dreamweaver? With various technology options to choose from, IT teams feel a lot of pressure to make the right choice when developing their project. Portals, however, aggregate content at the presentation layer and allow multiple technologies to be used in the application layer. Some products also allow the various web technologies in different programming languages to be aggregated by a single presentation layer to the end user. Rather than push for a development team to choose certain technologies, a portal interface opens up new possibilities for development.

Whether you are evaluating Liferay or another platform, make sure you are doing your due diligence. The last thing you want is to be stuck with a choice that will sap your time, energy and money. Be sure to ask the hard questions and expect to receive the right answers. Your research will ensure your project gets off on the right foot.

Liferay Vs. Websphere: Total Cost of Ownership Examined

Why is Liferay accelerating in the Gartner magic quadrant and why are so many medium to large enterprises continuing to adopt open source products? Has open source software now become the preferred choice for enterprises? According to a Black Duck Software report, over half of all enterprises will utilize or contribute to open source in some manner in 2015.

This series of Infographics will provide a side by side comparison of Liferay Vs. Websphere, examining different aspects of the Liferay and IBM portal products.  The Infographic below, the first of the series, examines the total cost of ownership.

Liferay Portal Vs. Websphere Portal: Total Cost of Ownership Examined


  • Liferay Portal is a single product that provides the complete functionality without the need for any additional cost.
  • Over 70 out of the box portlets plus additional portlets are available through its marketplace. 3rd party portals and extensions are also available.
  • Liferay provides:
    • Liferay Social enhanced integrated collaboration
    • Liferay Sync
    • …at no additional cost to Liferay Portal customers.
  • Core products provide the following capabilities:
    • Content Management
    • Document Management
    • Full Collaboration Suite
    • Workflow Engine
  • Leveraging out of the box functionality can dramatically reduce development investments and accelerate time to market, while providing the core portal capabilities.
  • Liferay enables organizations to leverage existing infrastructure and open source, or lower cost options. There is an extensive list of supported operating systems, application services, database, caching and indexing appliances. Liferay does not lock you into a vendor
  • Commercial and Enterprise offerings of open source products continue to grow in the market place. The difference between traditional enterprise offerings and open source offerings are becoming narrower. Significant cost savings can be achieved by leveraging lower cost application servers. Database alternatives will only be further multiplied in deployments and architectures that support high availability and disaster recovering.
  • Liferay’s core products are based on its open source variant and rely heavily on open source libraries.


  • WebSphere Portal Family consists of 3 main products:
  1. WebSphere Portal Server is the base portal. This does not include collaboration or content management capability. WebSphere Portal Express is targeted at small to midsize businesses and has limits on the numbers of users.
  2. WebSphere Portal Enabled, which contains integrated Web Content Management capabilities.
  3. WebSphere Portal Extend, which contains additional collaboration features in additional to Web Content Management.
  • Licensing cost is significantly higher in the majority of WebSphere deployments due to its Processor Value Unit (PVU) pricing vs. Liferay’s Server and JVM base pricing, which allows organizations to take advantage of today’s multi-core processors without incurring additional costs.
  • WebSphere Portal Extend, which is IBM’s most feature rich portal product, is double the price of its base Portal server PVU cost, and is feature for feature most comparable against Liferay’s single platform.
  • WebSphere has a much more limited list of deployment options and is primarily limited to IBM infrastructure products such as IBM zOS, IBM application server, IBM DB2 and Oracle products, such as oracle dataset.
  • WebSphere Portal is tightly coupled with WebSphere Application Server and RAD, and has a more limited support for databases outside of IBM DB2, which limits enterprise flexibility and increases TCO.
  • Although IBM portal product is a closed product, at its core it relies heavily on open source libraries, so the “open source” factor is not as big of a factor.

How to Use Jenkins CI to Deploy Liferay Apps (Part 2)

Jenkins allows you to setup a deploy only project that would deploy artefacts from another build project. A typical setup at Veriday would look like the following:

Project 1 – Build and Deploy to Dev 1

Project 2 – Build and Deploy to Dev 2

Project 3 – Deploy to QA1

Project 4 – Deploy to QA2

Project 5 – Deploy to Prod. 1

Project 6 – Deploy to Prod. 2

In my previous blog post, I discussed how we setup projects like 1 and 2, in the list above. In this post, I will discuss projects similar to 3,4 and 5.

App Deployments

Before we build to QA1, one of our release steps is to configure project 3 to specify where the build artefacts will be coming from. Suppose we are promoting the latest development build from Dev 2 to QA 1. In this step we perform the following three steps:

  1. Match the SVN URL in Project 3 to the SVN URL in Project 2. This is important in case some build configurations were changed for that environment.
  2. Pick Project 2 as the source of the built artefacts and choose the build number. Each project has multiple builds depending on its setup. For example, Project 2, being a Development build task, would have a new build every night.
  3. We let Jenkins tag the current build in the SVN repository. This allows, in the case of emergency, fixes in production to perform the fix against the specific build that was released.

Deploying to different environments is a fast process, in this case. Instead of building code for deployment, you are just shipping the same application to a different environment.

The setup listed above has several benefits:

  1. On build day (or night) your activities are usually limited to picking the latest stable build on QA. i.e. the one that everybody has tested and is happy to ship to customers.
  2. Sometimes unexpected things happens. It is always a comfort to know that reverting to the previous application version is quick and easy. This would be done by picking the same build number you shipped to production the last time.

Depending on your Liferay project, a build may involve various types of deployments:

  • Portlets
  • Themes and Layouts
  • Various libraries, either your own or 3rd party ones

For portlets, themes, and layouts that typically get deployed into the Liferay /deploy path you usually don’t require a restart for Liferay to pick up the changes. However, deployments to Liferay or Tomcat’s lib paths typically require a restart. Our Jenkins build needs to be aware of this. All of the nuisances are configured on our Jenkins’s build tasks and deploys the various projects into the right paths, and then restarts Liferay.

In our case, deploying Liferay apps to a new environment takes about 2-3 minutes.

But, what about database changes? We haven’t crossed this bridge yet and we run database upgrade scripts manually during a release. This is a bridge that we definitely plan to cross in the coming year so stay tuned for a future blog post about Veriday’s experience with this.

3 Reasons Why Open Source Is On The Rise

This post was authored by Martin Yan and originally appeared here on Liferay.com

Has open source software now become the preferred choice for enterprises? According to a Black Duck Software report, over half of all enterprises will utilize or contribute to open source in some manner in 2015.

What was once considered on the fringes of technology circles, reserved for pockets of developers or small businesses, has now become a strong selling point for businesses across all industries. Increasingly, companies as well as individual contributors have opted to implement open source technology into their main system infrastructures.

What would explain the dramatic rise in open source interest? Perhaps we can point to the financial crisis in recent years, which has forced companies to reevaluate their purchasing budgets and operative costs. With greater savings and arguably much higher ROI potential, open source software serves as a more practical choice.

But there are several other good reasons people are gravitating towards the Linux’s and Firefox’s of the world:

  1. More security and reliability

The logic here kinda works backwards: the open source code is available for all eyes to see, which allows users to address more potential issues. (This is kind of like a surveillance society, though in this case it really is for your good.) In fact, hidden code tends to lead to more security vulnerabilities. Open source communities tend to respond more promptly to vulnerabilities, which in turn means a more stable and reliable product.

  1. No vendor lock-in

You don’t have to be stuck using one single software or company to develop a project. For the most part, open source software is compatible with other products that are developed with similar standards, open or closed, regardless of vendor. This means you aren’t limited to using the technologies from the same companies, which could result in expensive purchases of entire product suites or integrations. (In other words, FREEDOM!!!)

  1. Easier to customize and adapt

Open source software adapts to the needs of various users and sites. Certainly, having to modify the source code can be quite costly due to maintenance fees, so developers tend to build a product with baked-in extensibility. The more flexible it is, the easier it is for you to keep up with whatever your site demands.

These reasons, and many others, are contributing to the growth of a vibrant marketplace that is only expected to make room for more challengers and visionaries. And as well-known organizations like NASAGoogle and Facebook adopt and invest in open source, you can expect more enterprises to entrust their future projects to open source.


For more articles from the Liferay community, visit the Liferay Blog.

3 Opportunities for Employee Engagement

This post was authored by Shannon Chang and originally appeared here on Liferay.


Takeaways from intra.NET Reloaded Boston

Modern organizations are increasingly seeing the value of trading in their notoriously outdated and static intranets for social and collaborative digital workplaces, but the opportunity to greater facilitate employee engagement still exists. At the recent intra.NET Reloaded Boston event, attendees were asked to consider, “What is the single most important thing for employee engagement?”

3 Opportunities for Employee Engagement

Three themes stood out among the 80+ answers collected, reflecting industry challenges and moreover the opportunities to facilitate greater employee engagement ultimately leading to a successful intranet.

Employee Empowerment

“Of, by, for the people.” While a reference to the Gettysburg Address may seem a little extreme, it gives you an idea of how passionate the attendees are about “liberating” the traditional intranet and advancing it as a modern tool for employee engagement.

Whether creating a champion or rebel, empowering employees to become agents of change starts with:

  • Sharing knowledge by putting social tools in the hands of your employees
  • Allowing employees to use devices of their choosing
  • Creating emotion and a sense of belonging to promote culture

UX as the Key to User Adoption

The value of a productive and engaging intranet depends on user adoption, but is improving the user experience (UX) the answer? Some say yes.

L’Oréal proclaims to have devoted its energy and its competencies solely to one business: beauty. As Cara Kamenev of L’Oréal (@carakamenev) eloquently states, ”Every piece of content needs to be branded and beautiful.” When the UX reflects the culture of the organization, the digital experience becomes an approachable extension of the community that will drive adoption.

Content that Matters

“Clean out the ROT (Redundant, Outdated, Trivial) [content],” says Marcia Robinson (@MarciaRnyc) of Mercer. The cycle of improving productivity begins with making space for contextualized content that will actually help people make better decisions.

Employee Empowerment, UX as the Key to User Adoption, and Content that Matters sum up the inspired ideas resounding over the roundtable and three opportunities for employee engagement.

For more information on how to modernize your employee engagement with Liferay, check out: www.liferay.com/solutions/intranets

How to use Jenkins CI to deploy Liferay apps (Part 1)

Who is Jenkins CI?

Jenkins CI is an open source continuous integration server we use at Veriday to automate our builds and deployments to various environments. It is used at various companies including eBay, GitHub, Facebook, Liferay, Netflix, LinkedIn and many more. You can run your own instance in your office like we do, or even use a Jenkins cloud provider such as CloudBees.

We started using Jenkins CI about three years ago to produce nightly builds of Digital Agent so that our team could review and test the latest build of our product. Today our environment has grown to about a dozen servers compromised of development / integration instances, staging / testing instances, sales / demo instances  and finally, our production servers. All of the deployments to these environments are managed by our trusted friend, Mr. Jenkins, making most releases “minor events” that take a couple of minutes, and provide us the safety net of being able to roll back a release with just a click of a button.

Automating Builds

It starts with defining “jobs” for Jenkins to perform. These jobs can be automated or manually triggered. A job tells Jenkins what it needs to do. For example a “Build Job” would contain steps like this:

  • Check out the latest from an SVN branch
  • Build the code
  • Deploy it to one of the Liferay development servers
  • Restart Liferay
  • Notify the development team of any failures in the above steps

Our “Build Jobs” are automatic and happen overnight so that when we come in the next morning, we can review the latest on that development server. This year, we will also look at integrating our Selenium browser test cases into Jenkins so that with each build our UI test cases are executed and compared against the previous build.

One issue that we ran into while setting this up is that our Java application would build okay on our local environments but fail on Jenkins. Remember, on your local environment you have access to Liferay and Tomcat libraries that Jenkins would not necessarily have. To get around this problem we have a project in our workspace specifically for Jenkins that contains these “system” libraries. This project also contains configuration files for each environment that would contain paths to the Liferay home folder, IP addresses, the Jenkins user account to SSH, etc. Each Jenkins job would then define what environment the job is for ex. “DEV1”, “DEV2”, etc.

Adopting continuous builds is extremely beneficial to any software development team. I noticed the following three things on our team:

  1. Nobody wants Jenkins to send an e-mail saying their code check in broke the build – especially since the e-mail goes to the whole team. To avoid that, the team now always runs the builds locally and verifies it at least builds.
  2. We run several branches of development at the same time. At any time, we need to be able to review the status of the branch against the committed to tickets, enhancements, new features, etc. With our nightly builds, we can be sure that each of our development environments is up-to-date as of that morning.
  3. In the case that Jenkins does report a build fail, someone on the team (usually the first person) will spot the issue and make the correction the very next morning. Because of point (1) this is now usually a result of other reasons outside of the build itself. Ex. Jenkins ran out of space, or the target development environment was unreachable.

In Part 2 of this series, I will talk about how we use Jenkins to deploy our app on to Liferay using a build that was already verified and tested on a development server, and then on a staging environment, before the exact same build is promoted to production.