The document discusses the concept of a 'portal' in the context of app development, using a 'Lego set' analogy to describe the various components required for building a portal such as portlet containers, navigation, and security features. It highlights the integration of multiple applications on a single page and refers to standards like JSR 168 and JSR 286 to improve functionality and collaboration between different technologies. The presentation emphasizes the ease of use and shared resources within a portal environment, illustrating how developers can implement complex systems without starting from scratch.

2. Portal - Lego set for app
development
Bolesław Dawidowicz

3. About me
•Bolesław Dawidowicz
•Principal Software Engineer
•With RedHat / JBoss since 2006
•Currently GateIn Portal Project Lead
•(co leading with Julien Viet from eXo)
•Responsible for various stuff related to IDM component
in the past

4. Take a different view on
portal...

5. Why LEGO?

6. Many different pieces

7. Need to choose the
right set for your
project

12. Which one do I need?

13. Do I need portal?

14. Which one is Portal?

15. What is Portal then?

16. Integration technology

17. Set of services

18. Wait?
Wasn’t it about this
’portlet’ thing?

19. Portlet Specification
JSR 168 & 286

20. Way to serve many
applications on a single
page

22. Portlet Container
Portal Core Service

23. Portal LEGO Set
•Portlet Container

24. Simplest Portal
vs
GateIn Portal
Demo

25. Interesting concept?
Also check embedding Pluto

26. What is simple portal?
Portlet Container
+
Simple Web app to serve content

27. Wait? Is Portal just a
web application then?

28. Yes
with a lot of added
services

29. That you don’t need to
implement yourself ;)

30. Our LEGO set...

31. Whats beyond
Portlet Container?

32. Lets see what pieces are
in the box

33. Anatomy of Portal

34. Portal LEGO Set
• Portlet Container
• Page structure
• Portal Object Model
• Skins
• Internationalization
• IDM
• Bridges
•

35. Portal Objects

36. Portal Objects
• Application Registry
• Configuration / Properties
• Pages
• Structure / Management
• Navigation tree
• Dynamically generated
• Sites

37. Dynamic navigation
• Dynamic navigation
• Based on identity, role or
group membership
• Located where node &
page are created
• Configured navigation
• Nodes can be created
moved or delated
• Can link together
different portal

38. Skins
• Skins in war files
• Based on CSS

39. Imagine implementing it
yourself

40. For every project...
again and again

41. Pretty standard pieces

42. Giving control

43. Virtual Sites
• New portals can be
spawned inside a single
portal installation
• Can have independent look
& feel
• Each virtual portal shares
administration resources
• Shared portlets
• Shared administration
tools
• Delegated security drives
uniqueness

44. Dynamically

45. Templates

47. Want more?

48. Import / export
Demo

49. SCP content between
portals !!!

50. Identity Management

51. [TBD]

52. Security / SSO

53. Security / SSO
•Security on different levels
•Application / Page / Navigation Node / Site / Portal
• SSO
•CAS, OpenSSO/OpenAM, JOSSO, Custom SPI Impl
•SPNEGO

54. Ok, but I don’t really
need this ‘portlet’ thing

55. Bridges / Containers

56. OpenSocial
• Apache Shindig onboard
• Consume remote & local
widgets
• Host widgets for other sites
• Widgets coexist with with
portlets on pages

57. Standards...
•JSR 286 (Portlet 2.0 Specification)
•First delivered in JBoss EPP 4.3
•Backwards compatible with JSR 168 (Portlet 1.0)
•Supports a number of improvements
•Portlet eventing & parameter passing
•Improved portlet caching
•Improved AJAX & dynamic rendering
•JSR 301 and JSR 329 (JSF Portlets)
•Enables rich, secure delivery of JSF into a portal
•Foundation of the portlet bridge

58. ... and beyond
• Portlet Bridge
• Rich Faces
• JSF
• JBoss Seam
• Example portlets
• Struts
• Spring portlet
• Flash Flex
• GWT Portlet

59. Web Services for Remote
Portlets
• Use cases
• Portal Farms
• Migration strategies
• Complex integration
• (legacy system)

60. Things you don’t need
to implement yourself

61. What do I get more?

62. Clustering

63. Performance

64. QA

65. Want more?

66. Think LEGO again...

67. ... mix with another set
of pieces

68. WCM / ECM

69. Mashups

70. Ready to use
applications...

71. ... that you don’t need
to implement...

72. ... yourself!

73. Thank You!

74. Questions?