Does it make sense to write a form based database web app using portal\portlet technology? Is there any criteria that should be used in deciding whether the app should be a plain old web app or a portal\portlet app?
some places that we can use portal are : 1-we have a community that each user is able to select which data,pages he want to see and in which order or shape. 2-we need to interact with several data sources from one page 3-we have an increasing need of functionalities , in term of new modules
usually portals provide : user and role management , platform for adding more portlets(web module) , access permissions based on users role to web modules..... page decoration , SSO ,....
One advantage of a portal is u get built-in benefits like access control,personalization..etc. There are also pre-built portals available.Once a portlet is created it can also be consumed by other portals
posted 13 years ago
Originally posted by Mark Spritzler: But won't that make you vendor locked if you use Weblogic specific controls?
But that is with every portal server. Controls which you create on weblogic portal server will not work on vigenette server and wise versa.
First of all portal server should be selected.
Now should I go for portal web application for a form based database access using portal/portlet technology needs certain question to be answered...
Like if you are going for personalization (want to personalize the content based on user profiles), uup components etc.
Hi Vic, I think of a portal as the aggregater of a number of disparate applications in a highly personalised manner. The critical component here is personalisation i.e. the ability to present only the relevant portlets based on a particular role, this is the key differentiater that portals possess that websites do not.
Many large organisations have at least two portals one being for internal staff (Intranet) and one for external facing customers. How personalisation is performed depends on the scope of the portal and the nature of an organisations business e.g. Staff portal may have business, management, technical and sales roles where an external facing customer portal may be have roles based on what product customers have bought etc.. Applications or portlets are then displayed to the user based on their role(s). Portals also allow the user to customise their applications which although being a nice feature most probably will not provide the level of business benefit that personalisation does.
Back to your question, should you develop as a web app or a portlet? That depends on whether you already have a portal in place and whether you want to target your app to certain roles. It also depends on other things such as whether you are introducing process centric type applications (that co-operative portlets can assist with) and the granularity of the app you are building.
A lot of good new stuff is emerging with portals such as inbuilt eForms and process management. Add that to the other stuff that Gobiraj mentioned plus SSO, WSRP, and a wealth of JSR-168 pre-written components, I would definately move to a portal if your business has capacity for one.
Gartner sees portals as the flagstone of any organisations IT systems in the coming 5 years.
Delivering systems from "the glass to the arse"! [ June 17, 2006: Message edited by: Rob Doughty ]