Connections

July 2009

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

« From Blogging Tools To Blogging Services | Main | BEA Finds Plumtree Ripe For Picking »

July 27, 2005

Let's Not Forget About Portals

Since joining Burton Group things have been pretty busy in terms of becoming "Burton-ized", getting my home office environment setup, reconnecting with vendors, introducing myself to clients and immersing myself in my current research assignment on enterprise portals. That's the list of excuses at least for not posting lately!

Portals play a critically important role in delivering contextual user experiences. Portals are not considered an integral component of the core technology manifest for collaboration (e.g., e-mail, calendaring, group scheduling, IM, presence, Web conferencing, virtual workspaces, blogs, wikis, etc). However, portals have become the superstructure of SOA frameworks that intelligently aggregate, integrate and orchestrate the presentation/interaction management layer.

Portals are not be the only interaction model that enables contextual interfaces but their evolution from simple point-and-click gateways to component applications frameworks enables them to blend portlets comprised of applications, information, communication and collaboration services based on a variety of factors that include role, user/group profile information or other types of meta data.

Whatever choice you make on portals will have a direct impact on your collaboration services and visa-versa. Standards such as WSRP and JSR 168 do not provide a silver-bullet for plug-and-play when it comes to replicating complete application functionality and behaviors across different portal frameworks. Many portal products also have their own models when it comes to things like page layout, eventing, inter-portlet communication, look-and-feel when it comes to behaviors and such making portal syndication or federation across different products based on common/reusable portlet components difficult.

Increasingly, enterprises will not make silo decisions around portals, collaboration or other domains but will examine the entire “stack” from major platform vendors (e.g., BEA, IBM, Microsoft, Oracle, SAP). Considerations around modularity, extensibility, integration and interoperability will span portal, applications, analytics, enterprise content management, collaboration and communication. This does not mean you have to go 100% with any single vendor – it’s likely you will have a couple major superplatform players that dominate certain application or infrastructure categories – but it is likely that many enterprises will be looking at a minimal amount of core trusted vendors around whose SOA scaffolding you can connect best of breed solutions where they make sense.

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d834515a5969e200d8351ce2e453ef

Listed below are links to weblogs that reference Let's Not Forget About Portals:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Normally I wouldn’t comment on posts but I felt that I had to as your writing style is really good. You have broken down a difficult area so that it easy to understand. I think that you would enjoy reading what another good blogger has to say on the subject.

The points you make in this post are excellent. I really find this an interesting topic.

Best Of Luck!

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment