Liferay

 and  the  Future  

of  Portal  Development  
A  Liferay  Webinar  Series  

Paul Hinz
Chief Marketing Officer
Liferay, Inc.
Agenda  
•  Web Development Demands
•  Portal Promises Unmet and
Market Response
•  The Future of Portals
•  Community Plans
 Preface:  Liferay  
•  Over  3  Million  Downloads  
•  Analyst  PosiBoned  as  Visionary  Leader  
•  11,000  AcBve  Forum  Members  
•  ~60  Formal  Partners     Used  world-­‐wide  for:  
"   Web Pub & CMS
"   Internet / Intranet / Extranet
"   Social Collaboration
"   EAI framework / Dashboards
"   Web-based applications

3  
 Evolving  Focus  
Where to focus – Developers
(Feature Development) /
Administrators / End Users
Social  
Collab  /     User  Focused  
RIA  /  Lite   Portals  
Development  
SOA  

Portals  

Apps  

As additional features are added -

Content  
All Stand Alone Applications
Became Portals.
Development  EvoluBon  
•  Single  Apps  –  with  “iliBes”  
•  IntegraBon  
•  Code  Reuse  
•  SimplificaBon  
•  Rich  ApplicaBon  Development  

Rich  –  Simple  –  Reuse  Common  Components  

 CollaboraBon  EvoluBon  
1:Many   1:Some:Many  

•  People  CollaboraBon   •  Social  CollaboraBon  

–  Email   –  User  Social  Network  
–  Calendar   •  Everyone,  Friend,  Etc.  
–  IM   –  ApplicaBons  
–  Mtg  /  Teleconferences   •  CommuniBes/Pages  
–  Document  Sharing   •  User  defined  membership  
–  Task  Mgmt  SoXware   •  User  defined    policy  
–  Human  Workflow   •  User  Defined    content,  
apps,  data  
ApplicaBons   –  Socially  aware  
–  User  Content  Publishing   –  Non-­‐Socially  aware  

Growing the Capability to Communicate, Coordinate, Share

End  User  EvoluBon  
•  Anonymous  
•  Login    
•  PersonalizaBon  
•  Social  Networking  –  CustomizaBon  

Growing  the  capability  of  the  End  User  

Portals  –  Promises  Unmet  
•  Single  PresentaBon  /  Web  Desktop  
•  Central  access  point  for  B2B,  B2C,  B2E,  G2P  
•  PresentaBon  Layer  of  complete  SOA  
•  PresentaBon  Layer  for  ApplicaBon  Pla_orm  
•  UnificaBon  of  Content  Management  and  
ApplicaBon  Development  

•  RealizaBon  
–  Too  Big  –  Too  Complex  (Install/Dev/Admin)  –  Vendor  Lock-­‐in  
–  New  Technologies  (Social  Network  /  JavaScript  /  User  Publishing)  

8  
 Promises  Unmet  
•  Difficult  to  develop  using  a  Portal   So    
–  Need  for  clean  separaBon  but  easy  “connectedness”   -­‐  
•  Portlet  API  good  for  separaBon  –  not  connectedness   Are  portals  a  
commodity?    
–  Java  as  a  language  didn’t  help  either    
-­‐  
•  Great  Security,  OS  AgnosBc,  Standards,  etc.  
Simply  part  of  
•  But  Bloated*  –  Servlets  harder  than  PHP,  require  complex  app   an  App  Stack?  
servers,  long  learning  curve   -­‐  
–  Web  2.0  dev  methods  easy  but  not  core  in  Portal   Only  used  for  
Portlet    
aggregaBon?  
•  Difficult  Deployments  
–  Had  to  know  JAR/WAR/Class  Loaders    
–  Had  to  install  “LARGE”  ApplicaBon  Servers  
*Note Java EE 6 solves this with Profiles, however, other frameworks have grown in Enterprises

9  
Market  Response  and  New  Demands  
•  Open  Source  
•  Light  Weight  Development  
•  Distributed  Dev/Deploy  
•  Rich  Apps  
•  IdenBty  Compliance  
•  Separate  Social  CollaboraBon  Tools  
But  new  problems  have  arisen  

10  
Market  Response  …  and  New  Problems  
•  New  problems  
–  MulBple  dev  paradigms,  Silo’ed  dev/apps  
–  Divergent  ID  Policy,  Content,  Apps  

•  All  Apps  Become  Portals  

–  Ext  E.g.  Facebook,  JIRA,  Salesforce  
–  Each  begin  as  a  single  applicaBon    
–  Grow  to  need  more  apps  /  features  
–  Need  UI  paradigm  to  support  growth  
–  Allow  users  to  add  funcBonality  desired  

11  
Content,  ApplicaBons,  Data  

•  Formal  Pages   Pages  Created  for  

•  Centrally  created  for  audience   Me  
from  Apps,  Content,  Policy  

•  Community  Pages  
•  End  User  Created  
•  New  content   External  
Content,  Data,   Pages  Created  
•  Leverage  pre-­‐built  apps  
ApplicaBons   By  Me  
•  Define  new  apps?   Available    
•  Make  apps  available  for  others    
End  User  Focused  Portal  
   People,  Content  &  ApplicaBons  
Me

Pages or Views
Formal   My  
Views   Views  

People
Formal  IdenBty   Individuals  
Policy   Social  Network  

Applications User  Defined  ApplicaBons  

Packaged  ApplicaBons   3rd  Party  ApplicaBons  

Content and Data

Enterprise  Content   Social  Content  
 Portal  Page  Hierarchy    
 -­‐  And  the  Power  of  Social  Community  Sites  
Pages are: Pages Contain
- Formally defined - Apps and Data
ABC.com  
- User Defined - Content
- Access Policy
- Tags / Meta Data
Employee   Customer  
Pages   Website   - Rules

Individual   Public   Customer   Partner   Customer  

HR  Pages   OperaBons   Sales  
Pages   Pages   Portal   Portal   Login  Pages  

Bob   SaBsh   Mya   Customer  A   Customer  B  

Community   Community  
1   2  
ApplicaBons  /  Content  
End  User  as  Developer  
2n Application / Content Growth
New Dynamic in Productivity Increase

ApplicaBon  Repository  
(Portlets-­‐  Gadgets-­‐Widgts)  

Define
Users  /  Roles  /  Policy  

Community  Data  /  
Content  
Community Templates
http://www.ABC.com/CommunityX
Keywords: Collab, Networking, People…. - User Defined
- Administrator Defined
Portal  Fabric  
MulBple  Portals  and  Repositories  
Portal  
ApplicaBon  
Portal  
ApplicaBon  
Repository  
Repository  
ApplicaBon    
Reg/Repository  

Portal   Data    
Repository   ApplicaBon    
Content  
Repository  
Portal  2   Reg/Repository  
IDM  
Repository  
Portal  3  
Data    
Repository  

Content  
Portal  5   Repository  
(vendor  x)  
IDM  
Portal  4   Repository  
The  Future  of  Portals  
People,  Content,  Apps  
•  People  
–  Enabling  the  End  User  as  Developer   www.sesamestreet.org

–  Integrated  CollaboraBve  Services  

–  Integrated  Social  and  Formal  IdenBty  
•  Content  
–  Workflow  –  unify  pla_orm  for  internal   nbase.nba.com
and  external  web  
–  Knowledge  Worker  ProducBvity  
Pla_orm  
•  CombinaBon  of  content,  social  rules  and  
collaboraBve  services   lufthansa-flight-training.de

17  
The  Future  of  Portals  
People,  Content,  Apps  
•  ApplicaBons  
–  Best  of  Enterprise  and  HTML/Web  Dev  
–  Portlets  and  Gadgets  
•   Gadgets  -­‐  Easy  to  develop  (JavaScript/
HTML),  Easy  to  Deploy  (XML  vs.  WAR)    -­‐  
but  basically  IFrames  
•   Portlets  -­‐  Load  a  page  with  20  Gadgets  
and  you  really  have  20  different  browser  
sessions  and  requests.    Load  a  page  in  
Liferay  with  20  portlets,  and  you  have  one  
request.  
•  Deployments  
–  Incremental  Growth  and  MigraBons  
–  Portal  Fabric  

18  
1H  –  2010  Community  Plans  
Simplifying  Web  and  App    Dev   Enhance user capabilities:
•  RESTful  architectural  approaches  
•  support for user-defined business
•  integraBon  support  for  third-­‐party  
content  repositories   processes
•  stronger personalization
•  CMIS  support   capabilities
•  forms-based workflows
•  semantic web and faceted
search
•  “smart” content search
services
•  further enhancements to
social collaboration and
integrated workplace
technologies
2010  -­‐  Leading  the  Community    
For  the  Benefit  of  Everyone  
•  Defacto  Standards  and  Open  Source  
–  Major  vendors  will  focus  on  their  pla_orms  
•  Will  work  on  some  standards  to  leverage  their  pla_orm  
–  Open  Source  leaders  will  work  with  community  to  develop  
defacto  standards  
•  Liferay  Community  Leading  Defacto  Standards  
–  Alloy  Projects  
–  Alloy  UI  -­‐  htp://www.alloyui.org/  

20  
2010  -­‐  Leading  the  Community    
For  the  Benefit  of  Everyone  
•  Business  Leaders  
–  Webinar  Series  for  Business  Users  
–  EvaluaBon  Tools  
–  Marginal  Growth  
•  Community  Leaders  /  Members  
–  Community  Memberships  (Liferay.com)  
–  Technical  Webinars,  LifeCasts  and  more…  
–  Alloy  Series  

21  
 Open  Source  Release  Flow  
Prev   Beta  EE  GA   SP1   SP2   SP3  
Hot  Patches  

Prev   RC  x  

New  Features  
RC  1   CE  GA   Liferay  Trunk  

Prev   RC  x   CE  GA  

Key   Prev   Beta   EE  GA  

RC  1  
• Prev  =  Preview  release  –  opBonal  early  release  to  test  specific  features  
• RC1-­‐  RCx  =  Release  Candidates  –  progressive  QA  per  release  
• Beta  =  opBonal  release  to  test  in  real  world  deployments  
• GA  =  General  Availability    
Release  Cycle  
•   Major  releases  not  less  than  2  years  
• CE  GA  =  no  changes  /  patches  to  CE  aXer  GA  
•   Minor  releases  every  6-­‐12  months  
• EE  GA  =  Availability  of  EE,  Enterprise  support  begins  
•   Service  Packs  as  needed  throughout  year  
• SP  =  Service  Packs:  consolidated  hot  patches  avail  to  EE  customers  
•   New  Plugins  anyBme  during  the  year  
For  More  InformaBon  
•  Liferay  Portal  
–  Features:  htps://www.liferay.com/products/liferay-­‐portal/features/portal  
–  Docs:    htp://www.liferay.com/documentaBon/5.2  
–  AddiBonal  Resources:  htp://www.liferay.com/documentaBon/addiBonal-­‐resources/whitepapers  
•  Liferay  Training:  
–  Calendar:  htps://www.liferay.com/services/training  
•  Liferay  Community:  
–  Create  an  account:  htps://www.liferay.com/community  
–  Blogs:  htp://www.liferay.com/community/blogs  
•  Liferay,  Inc.  
–  Learn  more  about  Liferay:  htp://www.liferay.com/about-­‐us  
–  For  more  informaBon  about  Liferay,  please  email  Events@liferay.com  

23  
Q&A  
Thank  you  
Open  Source  Marketecture  

Liferay  Marketplace  

Liferay  IntegraBons   3rd  Party  Apps  and  Solns  

Toolset  
EE  Feature   EE  Feature   EE  Feature   (App  /    
Web  /  
Mashup  /  
Liferay  CE   OrchestraBon)  

Liferay EE (features/testing/support infrastructure)