Few days’ back I got to know about the something called “portal-like” . wow…a new word and a new concept after Collaboration, Web2.0 and SOA in the portal space. Drilled down a little deeper I came to know that this concept make sense when it comes to mid-size enterprise ,here it goes….
Portals Implementation gives you the solution but with a huge investment of money, infrastructure, resources and support.
Mid sized Customers who wants the portal features (with less investments) now can use the “Portal-like” products to leverage the features what a portal offers. These “Portal-like“ frameworks uses the Jsp, Jsf environment as a core language to built the applications and provide the addition runtime environment (portlet container) to consume/include the portlets on top of the jsp, jsf application. These frameworks support the deployment of standard based portlets (jsr168, wsrp1.0) together with the vendor specific portlets.
End users can also be provided with “virtually” customization features that will be a part of JSF/JSP/AJAX implementation.
These products are well suited where the core application takes more functional space than the utility portlets, which is opposite in the case of actual portal implementation.
There are few pros and cons of these frameworks/tools/products –
1) Comparatively less investment than the Portal product
2) No portal expertise required to develop “Portal-like“ application
3) Use of standard based pre-built portlets (blogs,wikis,cms,rss etc )
1) Application can not be easily scaled to portlets in the near future 🙂
2) Cannot be used as Integration point with other Enterprise/legacy applications.
3) Confidence of the customer towards the solution vendors.
The Introduction of such a framework is done by Oracle with its Web Center Suite. That provides the Content Integration, Runtime Customization, Metadata Management and Communication Services (Again a new Word for me “Presence Server”)