In this article we will first list some of the offered services and then have a deeper look at an important aspect of thecurrent internal architecture.
JBoss Portal comes with components and services ready to use. Here is a list of the main ones.
The portlet container is an implementation of the JSR-286 specification. This component is part of JBoss Portal 2.7(And the Enterprise Portal Platform 4.3) and is also available as a separate project without the other services. Theseparate project comes with a basic tag library for themes and can be used for prototyping or development. Thiscomponent enables portlets to run on a portal. Portlets are mostly designed to provide a modular approach to portalswhere components of a page can't collide but still communicate on top of which web application frameworks can bebuilt.
Most portals are partially restricted to some users and require authentication. The portal framework makes sure youcan integrate with an existing identity server that is already in place or let you configure a new one withoutnecessarily forcing a specific scheme.JBoss Portal will be able to store or retrieve users from databases supported by Hibernate, Red Hat Directory Server,OpenDS, OpenLDAP, Microsoft Active Directory... But provides an SPI to implement to be able to support proprietaryidentity servers.The authentication mechanism is based on JAAS and existing JBoss Application Server identity modules can beused, this gives a whole range of out of the box solutions for various scenarios. One major benefit is that portalauthentication benefits from modules based against JBoss AS security mechanism. (Such as Windows Desktop or Kerberos authentication through JBoss Negotiation that still need testing though).As far as SSO is concerned, not only all applications integrated within the portal must not require additionalauthentication but the portal itself must be able to be part of an SSO infrastructure and JBoss Portal has been testedagainst CAS, OpenSSO, JOSSO but again an SPI is available to plug into any solution.
CMS (And GUI)
A basic CMS/ECM/WCM/DMS (whatever we call those today) is available as part of JBoss Portal, the implementationis based on the command pattern and can directly be used through the provided services. A GUI is also available withworkflow support and Wysiwyg editor. Integration with ECM vendors is also possible (but requires some work) toreplace the basic CMS with a full-blown ECM such as Alfresco.
WSRP (And GUI)
The Web Services for Remote Portlet implementation of the 1.0 version is embedded in JBoss Portal. It lets the portalbeing able to produce content to be aggregated in other portal framework or solutions such as IBM WebspherePortal, BEA/Oracle Portals, Microsoft Sharepoint... The other way is also possible, content provided by thoseproducts can find its place within JBoss Portal. A relaxed mode is available to loose on the specification for better interoperability with other providers.