Liferay Portal is an open source portal that helps organizations collaborate more efficiently by providing a consolidated view of disparate applications. It is used by large and small organizations all over the world. Liferay has an extensive list of features that compares with most commercial portals, but without the high license fees. Open Source LicenseLiferay is made available under the MIT license, which is essentially the same as the Apache and BSD licenses. The MIT license is business friendly and contains no license fees or reciprocity clauses. You can bundle Liferay or your branch of Liferay and even resell it if you want. We do recommend that companies contribute their bug fixes and modifications back to Liferay so the community at large can benefit. It also allows your organization to easily upgrade to the latest version of Liferay.Features
JSR 168 (Portlet API) Compliant
You can hot deploy any JSR 168 compliant portlet. This means you can provide more functionality to your end users by writing custom portlets. Or, you can deploy portlets that you buy from a portlet vendor. WSRP Compliant
WSRP is a web services standard that allows you to publish portlets from your portal to external portals and allows you to consume portlets in your portal from external portals. This allows you to buy and sell portlet functionality as a service.
CMS
Liferay provides content management system functionality via a set of portlets that give your organization a flexible templating tool built on top of XSLT technologies. This allows you to build your site while cleanly separating content from the look and feel of a site. This page is served by the CMS tool. We will be JSR 170 (CMS API) compliant after the specification is finalized. Themes
Liferay provides a hot deployable theme architecture that allows you to change the look and feel of the portal without modifying Liferay's core code. Graphic designers can easily mock up new themes because all of our pages utilize DIVs and CSS standards. SSO
Liferay provides a built in connector for CAS,Yale's single sign on engine. You can write custom hooks to integrate with other SSO engines like Nategrity.Liferay can also synchronize its user list between the portal and an external data source like another database or LDAP server. A default connector for Microsoft Exchange is bundled with the portal. ASP Model
Liferay was designed from the ground up to be used by application service providers. This means you can host multiple instances of the portal (distinguished by unique URLs) on one application server and database. Application Server Agnostic
Unlike portals that come from application server vendors, Liferay is designed to be application server agnostic so you are not locked into a specific server. Liferay will work on lightweight servlet containers like Jetty and Tomcat, or on J2EE compliant servers like Borland ES, JBoss+Jetty/Tomcat, JOnAS+Jetty/Tomcat, JRun, Oracle9iAS, Orion, Pramati, RexIP, Sun JSAS, WebLogic, and WebSphere.An added bonus of being a Java portal means Liferay will work on many operating systems: BSD (FreeBSD, NetBSD, OpenBSD), Linux (Fedora, Novell), Solaris, Mac OS X, and Windows. Spring, EJB, and AOP
Liferay's business beans are built on top of Spring. This allows you to leverage Spring's AOP, IOC, and proxy features to customize Liferay.We use Spring to decide whether to call the POJO implementation of a business bean or the EJB wrapped implementation of a business bean. This allows deployers to decide whether to deploy Liferay on a heavyweight application server like Borland ES (and thus leverage VisiBroker's transaction features) or a lightweight container like Tomcat. Database Agnostic
Liferay uses Hibernate as the ORM tool for the persistence layer which enables pluggable databases (DB2, Firebird, Hypersonic, InterBase, JDataStore, MySQL, Oracle, PostgreSQL, SAP, SQL Server). This allows your organization to leverage existing resources without having to purchase new database hardware and software. Scalable N-Tier Cluster
Liferay is very scalable and uses OSCache to provide deployers with a clustered cache. You can scale by adding more nodes without sacrificing on caching.You can cluster the enterprise release of Liferay in multiple tiers: presentation tier, business logic tier, and database tier to meet your specific load requirements. Struts and Tiles
Liferay leverages off of Struts to follow the MVC pattern. Most programmers are already familiar with Struts, which means your developers will have an easier time of writing portlets in a familiar framework.The look and feel of the portal can be easily customized and reskinned because the display logic is concentrated in a few template files read by Tiles.. Internationalization
Liferay can display and receive input in multiple languages. Language resources for Chinese, Dutch, English, French, German, Greek, Italian, Japanese, Korean, Portuguese, Spanish, Turkish, and Vietnamese are already included. Personalization
Portlets can be rearranged to the unique preferences of a user or community. Move things up, down, and all around. Administration
Liferay allows administrators to easily manage users, groups, and roles through a GUI interface. Groups signify a collection of users. Roles signify permissions that a group or user can be bound to. Access to portlets are also restricted to users based on roles.Administrators can also specify community pages so that all users who belong to a certain group see the same page. Out of the Box Portlets
Liferay provides many useful portlets: Blogs, Calendar, Document Library, Journal (CMS), Image Gallery, Mail, Message Boards, Polls, RSS, and Wiki.Portals are only useful so long as there are portlets that provide functionality. Our bundled portlets are a great starting point for a portal deployment. They also serve as a large code base of examples from which you can glean patterns on how to write portlets. Community Based Portlets
Many of the bundled portlets are community aware. For example, if you add an event to your HR community calendar, then Marketing would not be aware of it. [email protected]
JSR 168 (Portlet API) Compliant
You can hot deploy any JSR 168 compliant portlet. This means you can provide more functionality to your end users by writing custom portlets. Or, you can deploy portlets that you buy from a portlet vendor. WSRP Compliant
WSRP is a web services standard that allows you to publish portlets from your portal to external portals and allows you to consume portlets in your portal from external portals. This allows you to buy and sell portlet functionality as a service.
CMS
Liferay provides content management system functionality via a set of portlets that give your organization a flexible templating tool built on top of XSLT technologies. This allows you to build your site while cleanly separating content from the look and feel of a site. This page is served by the CMS tool. We will be JSR 170 (CMS API) compliant after the specification is finalized. Themes
Liferay provides a hot deployable theme architecture that allows you to change the look and feel of the portal without modifying Liferay's core code. Graphic designers can easily mock up new themes because all of our pages utilize DIVs and CSS standards. SSO
Liferay provides a built in connector for CAS,Yale's single sign on engine. You can write custom hooks to integrate with other SSO engines like Nategrity.Liferay can also synchronize its user list between the portal and an external data source like another database or LDAP server. A default connector for Microsoft Exchange is bundled with the portal. ASP Model
Liferay was designed from the ground up to be used by application service providers. This means you can host multiple instances of the portal (distinguished by unique URLs) on one application server and database. Application Server Agnostic
Unlike portals that come from application server vendors, Liferay is designed to be application server agnostic so you are not locked into a specific server. Liferay will work on lightweight servlet containers like Jetty and Tomcat, or on J2EE compliant servers like Borland ES, JBoss+Jetty/Tomcat, JOnAS+Jetty/Tomcat, JRun, Oracle9iAS, Orion, Pramati, RexIP, Sun JSAS, WebLogic, and WebSphere.An added bonus of being a Java portal means Liferay will work on many operating systems: BSD (FreeBSD, NetBSD, OpenBSD), Linux (Fedora, Novell), Solaris, Mac OS X, and Windows. Spring, EJB, and AOP
Liferay's business beans are built on top of Spring. This allows you to leverage Spring's AOP, IOC, and proxy features to customize Liferay.We use Spring to decide whether to call the POJO implementation of a business bean or the EJB wrapped implementation of a business bean. This allows deployers to decide whether to deploy Liferay on a heavyweight application server like Borland ES (and thus leverage VisiBroker's transaction features) or a lightweight container like Tomcat. Database Agnostic
Liferay uses Hibernate as the ORM tool for the persistence layer which enables pluggable databases (DB2, Firebird, Hypersonic, InterBase, JDataStore, MySQL, Oracle, PostgreSQL, SAP, SQL Server). This allows your organization to leverage existing resources without having to purchase new database hardware and software. Scalable N-Tier Cluster
Liferay is very scalable and uses OSCache to provide deployers with a clustered cache. You can scale by adding more nodes without sacrificing on caching.You can cluster the enterprise release of Liferay in multiple tiers: presentation tier, business logic tier, and database tier to meet your specific load requirements. Struts and Tiles
Liferay leverages off of Struts to follow the MVC pattern. Most programmers are already familiar with Struts, which means your developers will have an easier time of writing portlets in a familiar framework.The look and feel of the portal can be easily customized and reskinned because the display logic is concentrated in a few template files read by Tiles.. Internationalization
Liferay can display and receive input in multiple languages. Language resources for Chinese, Dutch, English, French, German, Greek, Italian, Japanese, Korean, Portuguese, Spanish, Turkish, and Vietnamese are already included. Personalization
Portlets can be rearranged to the unique preferences of a user or community. Move things up, down, and all around. Administration
Liferay allows administrators to easily manage users, groups, and roles through a GUI interface. Groups signify a collection of users. Roles signify permissions that a group or user can be bound to. Access to portlets are also restricted to users based on roles.Administrators can also specify community pages so that all users who belong to a certain group see the same page. Out of the Box Portlets
Liferay provides many useful portlets: Blogs, Calendar, Document Library, Journal (CMS), Image Gallery, Mail, Message Boards, Polls, RSS, and Wiki.Portals are only useful so long as there are portlets that provide functionality. Our bundled portlets are a great starting point for a portal deployment. They also serve as a large code base of examples from which you can glean patterns on how to write portlets. Community Based Portlets
Many of the bundled portlets are community aware. For example, if you add an event to your HR community calendar, then Marketing would not be aware of it. [email protected]
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货