Portable Services and Liferay

Applications evolve. Every developer realizes this fact after a few years of writing code. The trick is to write applications in such a way that there is always room for evolution. While the necessity for code refactor is sometimes inevitable due to several different reasons, applications that have been designed following a few well-known principles are less likely to be completely re-written due to requirement and architecture change.

Portability is the principle that motivates this text. There are definitions of software portability that can be found in different sources, but let us keep it simple and just say that an application is portable if it can be moved from one infrastructure to another with minimal change. For example, a portable rich client application can be converted to a web application by changing the user interface only. A portable web application should be moved from one web server to another with no change to code. To make it possible, the application should not be dependent on the underlying infrastructure code. If that is inevitable, the infrastructure-dependent code should not be allowed to spread across the application; it should be contained behind, say, an interface.

Applications start small, and they should if one would like to minimize risks and deliver a minimum viable product as soon as possible. When designing such applications, architects frequently refer to the the now classic three-tiered model: a front-end tier that contains the user interface code, a back-end application tier that contains the business logic, and a database tier that manages the application’s data. The back-end tier is frequently designed as a three-layered application, with a service façade to communicate with the user interface, a business service layer and a data access layer to interface with the database tier. This model works well when designed properly and, if the tiers and layers are respected, they may be ported to a richer environment as the application grows larger.

With success comes opportunity. A partnership with a third-party service provider may emerge from all the traffic drawn to our application. For instance, someone representing a large company may ask us, “how would you like to see your content on the screens of all subway stations in the city?” Wouldn’t that be sweet? However, there is catch: our partner has its own set of services that need to be integrated with our application. A precedent is set as yet another interested partner is brought in and they also have their own services. Now our well designed application has to communicate with not only its database, but also these inumerous services. What now?

Instead of reaching out to them directly, an integration tier is adopted. All partners communicate with each other through this tier and never directly. The integration tier in turn calls the services exposed by each provider. On the other hand, each service is unique across the environment and is unaware of any other service. A Service Oriented Architecture (SOA) solution is born. And how does SOA help our solution? Through scalability. But scalability is not the word of the day; portability is. So we will leave SOA alone for now.

Let us go back to the beginning and use a more concrete scenario. This time we are designing a Liferay Portal-based application where content, websites, pages and users are maintained. These features are provided out-of-the-box; however, requirements often mandate that they have extra information. On top of that, features not supported by the portal may be requested. Therefore a few extra services are added to the project.

Application developers sometimes regard Liferay as not only a portal and portlet container, but also as a platform, almost an Enterprise Application Server. That is completely understandable. After all, Liferay allows developers to use its security layer, make services join its transactional context, create configurable data sources and more. The motivation for leveraging such infrastructure has already been mentioned here: applications start small, and the facilities offered seem very attractive. The portal even provides the Control Panel as a user interface for many out-of-the-box and custom features. So why not use Liferay as a launching pad?

Liferay recommends the use of its Service Builder to write services deployed in a Liferay environment. The Service Builder is very useful, easy to use and well described in the Developer Guide, but it has a downside. Anyone who has used it probably noticed the dependencies to Liferay code, meaning that custom services are doomed to be only deployable in a Liferay environment. And that is not very portable (this is not entirely true but the code remains dependent on Liferay libraries nevertheless). Liferay-dependent services are okay in a SOA environment because what stays deployed in the portal is only portal-related code such as website and page management. Non-related services are deployed somewhere else. But in our illustrative example we are not there just yet; we are still designing a starter application and our fictitious budget does not support additional infrastructure.

Building our solution, while looking ahead at opportunities for growth beyond the Portal, requires a few techniques, which are illustrated here with an example. Regardless of building the application as a set of portlets or a Javascript front-end communicating with a JSON over REST back-end, the architect has decided to design our application as a set of services.

Services are often built to maintain an entity that is defined by the application domain. That means, if our application defines a user entity and its attributes (name, email, address, phone, roles), there should be a service responsible for maintaining these user attributes. Basic operations are often referred to as Create, Retrieve, Update and Delete (CRUD).

A typical service is designed as a three-layered module. It has a service façade layer which can be either a Struts action, a Spring controller, a JSF backing bean or a RESTful web service. The façade invokes the business service layer which contains the business rules. The service layer persists data by either invoking the data access layer, if it is stored locally, or by invoking a service provider interface to communicate with the data host. The whole service module is transactional. If the service only retrieves data and presents it to the client, then the transaction is marked as read-only. It is also secured by the architect’s framework of choice. Services are then packaged as regular Liferay plugins.

The important aspect here is to keep the service code decoupled from the underlying infrastructure. The first thing to keep in mind is to package it as libraries and configure the plugin to import them. Second, these libraries should not have any dependency on Liferay code, even if the application uses out-of-the-box features such as workflow. If that is the case, then wrap the feature invocation with a service provider interface and write the implementation in a separate, Liferay-dependent library.

Our architect came across a few concerns related to infrastructure while designing the application. Fortunately, there are a few tools available that minimize development or make it easier to do. The following aspects were considered. I will only enumerate the concepts behind them and not go into details as they are all described in the Developer Guide, unless stated otherwise:

  • Security: Register custom entities as Liferay resources by configuring resource-action files. The Control Panel offers a user interface to define permissions on these entities. Most security frameworks validated by the industry offer interfaces for permission evaluation. Provide one that invokes Liferay security services.
  • Workflow: Register custom Workflow Handlers. The Control Panel offers a user interface to configure workflow definitions to be applied on these entities. Wrap the workflow engine invocations in a service provider interface to facilitate migration.
  • Transaction: Register a transaction interceptor in an advice chain configured by a service bean auto-proxy creator, defined in the plugin’s Spring context (see kaleo-web source code as an example). Make sure that the chosen transaction attribute source, such as a Transactional annotation, is Liferay-independent. The Spring annotation is recommended.
  • Liferay out-of-the-box feature maintenance requires synchronization with custom feature: Use service wrappers.
  • Custom feature maintenance requires synchronization with Liferay feature: Use Aspect Oriented Programming (AOP) advices. Write Liferay service calls in a separate, Liferay-dependent library.
  • Custom feature is fundamentally related to the Portal and is not expected to change in the foreseeable future: Use Service Builder. Make sure services not dependent on Liferay do not reference Service Builder-generated code.
  • Custom feature extends existing out-of-the-box feature (example, new page and website attributes): Use Expando Bridge.

I will cover the topics above in more detail in the near future, always from a perspective that takes portability into account.

Applying these techniques will most certainly help scaling solutions to a larger, more diverse environment. While Liferay offers an excellent starting point for small applications, the time may come when most services need to be transferred to external application servers and inter-communication becomes handled by an integration tier such as a service bus. Keeping application and Liferay code decoupled will ease the transition and minimize development time and cost.

 

The Business Case for Liferay

How to Troubleshoot 3 Common Jersey Exceptions

,

When building a web application, web services are an intrinsic component; without web services to supply data to the browser, the application is very limited in delivering value to the user.

Web applications have come a long way from the days of writing XMLHttpRequest objects from scratch and configuring basic Servlets to respond to the requests – there are many frameworks available that can simplify the web service interaction and save precious development time.

The Digital Agent tech stack includes Backbone.js in the front-end and the Jersey module supplied by the Spring Framework in the back-end. Together these two frameworks make implementing web services a breeze, but there are a few common exceptions that can be frustrating if you’re new to the frameworks and don’t know what they mean (or how to resolve them).

When developing with and debugging Jersey, you may have come across these exceptions (these are all HTTP 500 responses). I’ll use a simple ‘User’ web service to illustrate:

Exception 1: NullPointerException

  • @Controller annotation missing

From what I understand, for Spring to allow Jersey to handle requests to a given URL and utilize service-level classes, the ‘@Controller’ annotation must be present in the list of annotations immediately before the class declaration:

@Controller
public class UserWebService

If this annotation isn’t present, Spring isn’t aware of how to properly handle the request using the declared services. My first experience with this exception was writing the web service class from scratch, instead of ‘smartly reusing’ another working web service class.

Exception 2: Runtime Exception – com.sun.jersey.api.NotFoundException: null for uri: http://localhost:8080/delegate/services/user

  • @Path of web service class missing or web service class not deployed

If you’re just created a new web service and are anxious to see it interact with the front-end of the application, you may run into this exception…because you either missed the @Path annotation or didn’t deploy the most up-to-date web service classes. The class declaration now looks like this:

@Controller
@Path("/services/user")
public class UserWebService

The end result is the same – the front-end makes a request to a URI that Jersey isn’t aware of. Check that the necessary annotation is present and deploy those JAR files!

Exception 3: Runtime Exception – javax.ws.rs.WebApplicationException

  • Terminating Rule – @Path of web service class satisfied, but @Path of method not satisfied

This exception can surface when you are adding endpoints to an existing (and working) web service and fail to supply all of the path parameters, such as the ID of a resource.

@GET
@Path("/{id}")
public UserDto getUserById(@PathParam("id") long id)

The root cause is the @Path annotation of a method not being satisfied, in the case of a User web service, a ‘get by ID’ endpoint would require the ID of the user in question – if it’s not supplied (either due to user input or mis-use of a framework), this exception will be thrown.

Bonus! If you see a 404 response from your web service request, the fault is not that of the back-end. Check the URL that your front-end framework is making a request to, chances are it’s incorrect – either a missing leading ‘/’, or a typo in the path parameters.

At the end of the day, despite a few cryptic exceptions, these frameworks will drastically improve development times for web application projects. If (and when) you encounter an exception, it’s a huge time saver if you or someone on your team knows what the root cause is, and can translate the stack trace to plain English for you! Hopefully I’ve provided some human-readable assistance for you and these tips help you out!

The Business Case for Liferay

Four Common Pitfalls to Avoid in Migrating to Liferay

Moving to a new portal can be compared to moving into a new home. It takes a lot of planning, and always proves harder than anticipated. There are many things you need to figure out beforehand to ensure that migrating to Liferay is successful, and nothing is left behind (your data, for example).

Since there are a lot of moving parts and confusion around migrating to a new portal, Duke H, a Website Communicator at Liferay, has shared the top 4 pitfalls that Liferay’s customers encounter when migrating to Liferay. In the process of migrating, good planning and keeping in mind the pitfalls below, can help to ensure a seamless transfer between portals.

  1. Failing to backup migration
  2. Not identifying key stakeholders
  3. Not allowing for user acceptance testing/signing off without concrete guidelines or standards
  4. Not outlinining a strategy for content freeze during the migration execution

To read more of Duke’s article on migration pitfalls, click here.

Liferay Recognizes Veriday as a New Platinum Partner

,

Enterprise demand for better customer and employee engagement drives Veriday’s implementations of the leading portal provider

LOS ANGELES – (February 24, 2015) – Liferay, Inc., which makes enterprise, open source portals, announced today that Veriday has achieved Platinum Partner status. As a partner since 2011 and one of Liferay’s fastest growing technology partners, Veriday works with clients to design and implement customer- and employee-facing solutions using Liferay Portal. Major clients for whom Veriday has implemented Liferay Portal solutions include Canadian Tire, Saskatchewan Government Insurance, CIBC and FNF Canada.

“We count Veriday among our strongest partners,” said Brian Kim, Liferay’s Chief Operating Officer. “In combining a keen design point of view with technical engineering expertise, Veriday delivers high-performance user experiences to clients through Liferay Portal. They understand the unique approach Liferay offers in building web experiences that foster relationships with customers and employees. We look forward to furthering our partnership as Veriday’s client portfolio continues to expand in Canada.”

Veriday believes Liferay is essential to fulfilling the growing needs of the enterprise, especially those who are looking to move beyond the constraints of their current technology platforms. Liferay Portal provides key functionalities to meet the needs of modern users by enabling the delivery of mobile applications, both native and web, mobile responsive design and audience personalized content targeting.

“Veriday is very excited that our customers have enthusiastically embraced Liferay as a valuable technology investment. This is further evidence of Liferay’s effectiveness as a strategic investment for employee and customer engagement,” said Marc Lamoureux, CEO, Veriday. “We plan on continuing to invest in our Liferay partnership and expanding our impact across North America.”

For more information about Liferay, visit www.liferay.com.

For more information about Veriday, visit http://www.veriday.com.

About Liferay, Inc.

Liferay, Inc. is a leading provider of enterprise open source portal and collaboration software products, servicing Fortune 500 companies worldwide. Clients include Allianz, Carrefour, Cisco Systems, Danone, Lufthansa Flight Training, Siemens, Société Générale, Toyota and the United Nations. Liferay offers Enterprise Subscriptions, which provide access to emergency fixes, software updates, 24/7 support SLAs, and subscription-only features. Liferay also offers professional services and training to ensure successful deployments for its customers. Liferay, Liferay Portal, and the Liferay logo are trademarks or registered trademarks of Liferay, Inc., in the United States and other countries.

About Veriday

Veriday is a Technology and Digital Marketing Firm whose sole purpose is to help you delight your target audience and turn them into your promoters. We achieve your goals by educating your teams with proven methodologies and practices coupled with the latest, leading edge portal technologies.  From conceptual planning to implementation to technical support, we have your back when it comes to making your next online project a milestone success.

The Top 3 Business Benefits of Liferay

Veriday has been in the business of implementing Liferay Solutions since 2005. Our experiences building solutions on the Liferay platform have solidified our choice for Liferay as the leading enterprise portal platform.  Although there are many reasons why Liferay provides an effective technology investment for your business, we’ve narrowed it down to a quick top 3 business benefits that Liferay has to offer:

Smarter Investment

Liferay users have been smart about their savings, and investing in their futures. Liferay users get the most flexible and dynamic technology at the lowest Total Cost of Ownership and highest Return on Investment. Fortunately, Liferay is less expensive to maintain and grow with your business over time. Competing solutions require that you pay for additional features whereas Liferay comes equipped with as many resources as businesses need to accomplish whatever it is that your business needs to do.

image_gallery

Liferay is famous for its compatibility with a wide range of existing infrastructure software, including the popular contenders like MySQL, Oracle DB, SQLServer, DB2, WebLogic AS, Websphere AS, Oracle AS, JBoss AS, and Tomcat. This means Liferay not only costs less to acquire because of its open source license, but it also has lower ancillary costs.

Easy Adoption

Liferay understands that a major part of their value proposition lies in providing an easily adoptable and reusable presentation layer. This is why they have strongly invested and focused on improving and innovating around their user experience. Liferay is lightweight in nature which allows for businesses to get it configured, secured and implemented quickly. The Liferay solution has an award-winning user interface, familiar desktop conveniences and easy navigation making it extremely simple to use and adopt by all users in organizations.

Agility for the future and investment in the long-term

Liferay Portal evolves with your organization and for your organization. One of the many things that attract customers to Liferay is its ability to be customizable to integrate into the specific needs of businesses. If you require new functionality, tools can be added with just a few clicks.   Liferay continues to evolve with ideas and innovations that speak to the changing needs of their diverse audience of business, marketing and technical users with the goal of always providing a competitive advantage to their customers.

The Business Case for Liferay

Liferay as a Content Management System (CMS)

,

There is no denying that Content Management Systems are important in today’s web ecosystem. They allow you to spend less time staring at your computer screen and more time doing business. A Content Management System (CMS) is a tool that allows you to create, edit, manage and maintain website pages on a central interface without the use of codes and scripts.

CMS allows non-technical users to publish content to the web without having advanced knowledge of web technology or programming of any sort. It eliminates the need for a developer or HTML designer to be involved every time you want to change something on your site, resulting in increased work efficiency.

Liferay provides a powerful and flexible CMS to make fundamental changes to the way you do business. It is is one of the most popular CMS in the market for managing and administering website content and is recommended by many industry experts. Despite its many other robust features, many customers use Liferay Portal just for its content management system, whether it be web content management or management of file-based content. It comes with many features that make your content management task simple, and is used for both developing personal as well as enterprise websites.

Liferay continues to grow in popularity due to the fact that it simplifies the work and user experience, and can easily be customized to satisfy specific business needs. Advocates of Liferay point to its open source architecture, ease-of-use and integration capabilities as reasons for its continued success and popularity. If your business is looking for a CMS solution, Liferay is definitely worthy of consideration.

So, what can Liferay’s content management feature do for your business and website?

  1. Web Publishing
    • Allows anyone to easily maintain fully functional websites. Non-technical users can create, edit and publish content with a simple point and click interface.
  2. Unified Documents & Media
    • Includes a unified document repository that houses documents, video, audio, images and other media types from one place. It can be used across an enterprise, within a specific group or for a single individual. Enterprise-wide repositories allow groups to store assets, tag them with key words, lock them, search for and leverage them in web pages, or download them for use offline.
  3. Live Page Editing and Scheduling
    • Pages from a live site can be edited and previewed without affecting what is seen on the public site, then scheduled for future publishing all within the online editor.
  4. Integrated Collaboration Tools
    • Wikis, message boards, blogs, activity tracking, instant message, e-mail, shared calendar, pools, announcements and alerts, tags and categories
  5. Advanced Workflow and Approval Processes
    • Allows users tο produce thеіr οwn personal workflow аnd define thе amount οf approval paths based on thеіr οwn distinctive business requirements аnd operational units.
  6. Customizable
    • Easily customizable platform to satisfy specific preferences, user requirements and business needs.
  7. Multi-Language Support
    • Supports international localization and includes out-of-the-box support for 30+ languages. Users can toggle between different language settings with just one click.
  8. Integration with Microsoft Office
  9. Quick Page and Site Creation
    • Web structures and templates allow common web layouts to be saved for future web pages. Users can create pages or sites with sets of predefined templates or pages, and immediately begin adding content without the help of any developer support.
  10. Search Engine Optimization
    • With its ability to create web content, blogs, wikis and to share documents, your website becomes a valuable source of information. Liferay also optimizes updates to the site map information and makes new pages instantaneously searchable by external search engines.

For more information on the features of Liferay’s Content Management System, click here.

——————————————————————

Is Liferay a good fit for your business? Drop us a line to discover how Liferay can be customized to meet your business strategy and goals.The Business Case for Liferay

 

The Top Reasons Why Enterprises are Choosing Liferay Portal

Liferay Portal is the leading open source enterprise portal, with a large customer base across many different industries. Since 2005, we’ve been building innovative solutions for our clients using the Liferay Portal.  At Veriday, we believe in Liferay’s unique approach to building web experiences in order to help build relationships with customers and employees across the lifecycle.  Liferay’s portal foundation makes it easy to get a fuller view of customer and employee relationships and tailor their experience from start to finish.

Our experiences building solutions on the Liferay platform have solidified our choice for Liferay as the leading enterprise portal platform. But, we aren’t the only ones. Below are the top reasons why enterprises are choosing to go with the Liferay portal:

1) For the fifth year, Gartner has named Liferay as a Leader in the Magic Quadrant for Horizontal Portals based on its innovation and strengths in the open source community, collaboration, web content management and document management.

2) Liferay’s rich out-of-the-box (OOTB) functionality in comparison to its competitors. Its rich out-of-the-box functionality centres around core portal, content management, collaboration, social, mobile, security and more.

3) Liferay has the lowest Total Cost of Ownership (TCO) compared to its competitors. Liferay’s savings start with its licensing and the savings continue through development costs, operational costs, and training/support costs.

4) Most portal products require extensions or additions to deliver basic functionality. With Liferay, you can do more within a specific budget. Liferay is the easiest and least expensive to install and maintain of its competitors.

5) Liferay is a mature enterprise open source product. For more information on open source vs. closed source, check out this article.

6) Customization and Tailoring Features.  Liferay’s hook and extension plugin model allows you to customize and tailor it to your needs without having to revamp from scratch or upgrade every time.

7) Superior business agility.  Liferay is lightweight in nature, which allows for users to get it configured, secured and implemented quickly. Liferay allows business users to configure, tailor, and develop custom functionality to meet their business objectives.

8) Liferay offers a full choice of application servers, databases, and operating systems to run on, thereby allowing you to leverage your infrastructure and skills investment.

9) Liferay’s continues to grow and innovate. Liferay continues to grow at an unprecedented rate. Liferay has a strong community with roughly 4 million downloads (80,000 per month), 350,000-500,000 worldwide deployments and over 19,000 registered users on liferay.com

To learn more about who is using Liferay, check out  Who is Using this Technology. Looking for more insight on the different portal alternatives? We’ve got you covered here.

Alternatives to Oracle’s WebLogic

,

WebLogic, developed by the Oracle Corporation, is one of the leading portal frameworks and named a leader in the Gartner Magic Quadrant for Horizontal Portals. The WebLogic platform lets you provide a user interface to integrate dissimilar environments into an integrated, dynamic and customizable portal that can simultaneously support your customers, partners and employees. WebLogic is often used for managing enterprise portals and is known for improving business visibility and collaboration, and reducing integration costs.

In addition to a portal framework, WebLogic Portal provides many business services such as content management, communities, personalization, search and user management.

There are a number of Alternatives to WebLogic in the market today that offer similar functionalities. Which alternative you choose depends entirely on what tasks and objectives you are looking to accomplish with your portal technology. It is important to identify the needs and thus select the product with which you will build your platform on.

Below, we’ve put together a list of some of the best Alternatives to WebLogic:

Redhat JBoss

JBoss Portal is an open source platform for hosting and serving a portal’s web interface, publishing and managing its content, and customizing its experience. JBoss portal doesn’t aim at providing as many out of the box portal solutions as other platforms but is built to provide a fully reliable customized portal. JBoss features easy to use administration tools, a straightforward web content management system, and reliable performance and scalability.

Liferay

Liferay is the leading provider of open source enterprise portal and social collaboration software solutions, and a leader in Gartner’s Magic Quadrant for the 5th year in a row. Liferay is a web platform built to deliver immediate results with long-term value. With Liferay, you are able to build any kind of portal including social networks, e-learning portals, employee and customer portals. The platform also provides more out of the box portlets then any other portlet on the market including Liferay collaboration, web publishing, content management and social networking.

Apache Tomcat

Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. Apache Tomcat is used to power everything from simple one-server sites to large enterprise networks.  Tomcat powers numerous large-scale, mission critical web applications across a diverse range of industries and organizations.

IBM Websphere

IBM Websphere is an integrative software platform that enables organizations to build and manage web portals. Websphere was also named a leader in the Magic Quadrant for Horizontal Portals based on its scalability, flexibility and use in B2C and B2B organizations. Websphere is used to help organizations deliver exceptional web experiences regardless of location or device. The platform allows for people to interact with other people, applications, processes and documents in a unified, personalized and role-based fashion.

Every organization will eventually be faced with the challenge of choosing an enterprise portal solution and integrating it into their business processes. The decision is not one to take lightly as the portal technology you choose will be deeply integrated into your organization’s infrastructure and work as a corporate face for your systems and processes.   Choosing an alternative to WebLogic or Sharepoint depends entirely on what features are important for your organization.

———————————————–

What is your greatest challenge when it comes to choosing or implementing a new portal technology? Share your experiences below.

An Introduction to Portal Governance

,

So, your company has embarked on an enterprise portal implementation. You have completed your due diligence, established your business use case, calculated your ROI, and completed the process of vendor/product assessment and selection. The next inevitable question is what’s next; how do you ensure you deliver a product that satisfies your technology, business and end user requirements? How do you ensure that the portal delivers on its goals when launched, but more importantly, how do you ensure that the momentum is maintained?

The implementation of new portal technologies can fail for many reasons:

  • No vision or plan defined
  • No governance model, or have one but don’t follow it
  • No clearly defined process in place to coordinate between departments
  • No way to align technology to business needs
  • No person in place to make the final decisions
  • Mis-use of technology or poor architecture
  • Infrastructure not set up correctly
  • No process in place to prioritize the many things portals can do
  • Organizations underestimate the cost and complexity of portal implementations

Over the past 8 years, Veriday has been engaged in a number of enterprise portal implementations using Liferay. Though the size and scale have varied between small-scale implementation for targeted audiences to large-scale offerings in both commercial and enterprise rollouts, a common thread amongst the successful implementation is portal governance.

Portal governance is key to delivering an effective portal. Portal governance is the practices; policies and processes that govern and help maintain and foster the effectiveness of enterprise portals. It describes how your portal will be implemented and managed in your organization. The governance strategy is aligned with your business objectives so that your portal can continue to evolve along with your organization, and continuously deliver business value. Veriday creates portal governance strategies that clearly outline how activities, accountability and people should be structured, in your portal environment, in order to benefit your business, customers and employees.

Many organizations are faced with serious challenges when implementing an enterprise portal successfully. A portal implementation must align to the business and involve people, process, technology and policy. A well-defined portal governance structure should address the business and organization transformation, portal technology alignment with corporate objectives, ways to measure performance and management of people and accountabilities. Governance requires up front preparation to identify the ongoing processes, objectives and roles as they currently exist and will exist in the future.

The areas that require governance include:

  • Portal content
  • Portal roles
  • Workset design
  • Application integration
  • Desktop strategy and loadsets
  • Web content management
  • Collaboration tools
  • Search and taxonomies
  • Portal infrastructure and layout
  • Portal workflow

It is important to take into account all aspects of a portal and have clear lines of communication between the IT department and the business. Governance is important to keep the portal effective for a full return on investment.

————————————————————

Have you recently implemented a new portal technology in your organization? Did you have a portal governance model in place? What were some challenges that you ran into during the implementation process? Share your comments below!

Liferay Vs. Websphere: Who is using these technologies?

,

In a previous article, we discussed Liferay Vs. SharePoint and who is using these technologies.  This week, we will look into comparing Websphere with Liferay.  Before moving on, check out our article on the customers and uses of Liferay technology:

Liferay is the leading Open Source portal server and a leader in the Magic Quadrant for Horizontal Portal Platforms.  Many enterprises are using Liferay to build robust business solutions that deliver long-term value and results.  The company has seen a recent rapid growth in the past few years.  Liferay is an all-in-one enterprise portal with broad product capabilities that provide a user-friendly interface where you can centralize, share and collaborate.

Liferay has proven its real world performance globally with many clients across many diverse industries and business functions. It has been used in just about every industry around the world including automotive, education, government, healthcare, financial services, IT and Hi-Tech, media and entertainment and more.  It is primarily used for corporate websites, intranets and extranets but is highly scalable and easy to launch with many out of the box features.  Major organizations around the world choose Liferay for a wide variety of business functions beyond the traditional portal:

  • Intranet portals
  • Extranet portals
  • Content and Document Management
  • Web publishing and shared workspaces
  • Enterprise collaboration
  • Social networking
  • Enterprise portals and identify management

Liferay has a strong community with roughly 4 million downloads (80,000 per month), 350,000-500,000 worldwide deployments and over 19,000 registered users on liferay.com

Some of Liferay’s key customers include:

Liferay Clients
Learn more about their case studies and the enterprises using Liferay across industries and around the world.

Websphere – Who’s using it?

Gartner Research named IBM’s Websphere as a leader in the Magic Quadrant for Horizontal Portal Platforms based on its scalability, flexibility and use in B2C and B2B organizations. Websphere provides companies of all sizes with enterprise web portals that give users a single point of access to the applications, services, information and social connections they need.

Websphere was first released in 1992. Today, more then 100,000 clients globally are using IBM Websphere to build and integrate their infrastructure solutions. IBM 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.

Similar to Liferay, Websphere is used across just about every industry globally. It works across a variety of industries including banks, telecommunication companies, government agencies and more. Websphere is used in B2C (approximately 75% of deployments) and B2B (25% of deployments) organizations.

Below are the most common uses of Websphere:

  • Website generation
  • Content and document management
  • Enterprise employee and customer portals
  • Document collaboration
  • Shared workspaces

Some of Websphere’s key customers:

Websphere Clients

To learn more on Websphere case studies, click here.

—————————————————————

With a number of portal technologies on the market, many capable of powering your intranet portal, picking the one that’s right for your business can be daunting.  Looking to move to a new portal but aren’t sure where to start? Get in touch with us today!

What portal technology are you using for your business? Does your portal technology effectively support the technology demands placed on it in today’s digital economy?