Monday, June 19, 2006

San Diego - Gartner conference

San Diego, CA -- 19 Jun 2006 11 AM --
Greg and I are here in wonderful San Diego attending the Application Integration & Web Services Summit and the Enterprise Architecture Summit.
Things are going pretty good so far. We had a pretty uneventful trip, other than the fact that we missed the NBA Finals game...grrr. And then when we landed we found out the Mavs had LOST! Double grrr.
Anyway, just got out of the Keynote address. Very interesting focus on Web 2.0, Enterprise 2.0 etc with the overall look being SOA.
Just starting the session of Portals...must pay attention :)

Notes from Portals session
6 Generations of Portals
Gen 1 1998-2000 - Contnet mgmt agregation, serch, personalization
Gen 2 2000- 2002 - appications integration, mobile, wireless, mgmt tools, portlets starting to show up
Gen 3 2002-2003 - Portlet integration , process integration, advanced personalization, knowledge mgmt, web services
Gen 4 2004- 2005 - jsr168, WSRP, personal content, advanced web services, microsites, JSR168
Gen 5 2005 - 2007 - SOBA/PIP/PCA support, advanced collaboration, WSRP V2, JSR 286, orchestrations, user experience mgmt, portal as services
Gen 6 2008-2009 Portal ubiquity, user managed portal aggregation (Clent based/server based/hosted), peer portal federation

It is all about aggregation and integration
WSRP is the basics of federation
The WSRP standard defines a way in which a webpart can be delivered from a remote system (it stands for Web Services for Remote Portlets). One example of this would be a portal which supports publishing WSRP could communicate with a different portal which can subscribe to WSRP, and a portlet/webpart which was only written for the publisher could then be shown in the client.
JSR168 is a cross-vendor standard byt limited in scope. JSR286 is slowing coming
JSR will not be supported by Microsoft
WSRP maybe...WSRP 2.0 is here...
WSRP is an interoperability standard. It’s platform- and language-neutral. It’s all about requesting and transmitting chunks of HTML using SOAP.

BPEL - Orchestration
Business Process Modeling
BPEL is defined using XML. Accordingly, it was designed to be generated by tools, not written directly by developers. ep

AJAX is big...also potenttial security problem etc

Prepare for the Web 2.0 wave which introduces new approaches to platforms and processes.