The first age of portals – the prehistory of web portals so to speak – began in the late nineties and went until 2006. In those years, portals were mainly used as GUI integration technology: they integrated already existing applications with one login and with a unified navigation or menu. Application integration was the main concern during that era. That’s why portals still carry around a lot of different technologies how integration can be achieved: iframe, link integration, widgets, portlets, WSRP and others. Portlets became standardized with JSR 168 and JSR 286 and seemed to open up a new world of GUI components, some people even calling it GUI SOA.
The second age of portal started around 2007. From this time onwards, due to the necessities of web 2.0, people began using portals to implement web sites of all sizes, which put the emphasis on content. This is why most portals today offer extensive support for content integration like standardized JCR interfaces or even whole off-the-shelf web content repositories. But still, portals were regarded as an integration technology (cf. picture), albeit a complex one, offering individualized views for different roles of users. Moreover, portals became equipped with so-called social collaboration capabilities, like wiki, chat, communities and groups. Portal frameworks were very successful with this task – much more than with the integration objective – and a lot of programmers got to know them better and in more detail. Soon they realized: there is even more to portals…
|Portals as integration technology|
Actually, this is where a lot of trouble begins. But that’s a different story, and maybe another post.