1. IBM WebSphere Portal Roadmap
IBM WebSphere Portal Roadmap
Portal Foundation Architecture

2. WebSphere Portal Roadmap*
* Future product plans are
subject to change until release

3. WebSphere Portal Web 2.0 Features
IBM WebSphere Portal
WebSphere Portal Web 2.0 Features
Social Features
Social Software with Lotus Connections
Blogs and Wikis, and forums in Quickr
User Contribution to portal sites through WCM
Situational Development through the Portlet Palette, Drag and Drop page composition, Click-2-Action, Property Broker and Composite Application Templates
Technical Features
Support for AJAX Portlets
Portlet Factory builder, RAD tooling, DOJO, Samples,…
Exploits AJAX for context menus, search menu, and more
Provides REST services* for browser side programming
Client Side Aggregation* improves user experience
Semantic tags* and Microformats* support Smart Markup
Provides and consumes ATOM* Feeds
*WP 6.1Beta
Portal Foundation Architecture 3

4. composite applications
IBM WebSphere Portal
IBM WebSphere Portal and Google Gadget Integration
Seamless Integration With Thousands of Web-based Solutions Further Extends IBM’s Market Leadership
IBM Portlet for Google Gadgets
role-based
composite applications
in context
process-
driven
IBM WebSphere Portal
composite applications
Enterprise and internet data and services
Easily Configure Google Gadgets to Portal applications:
Search and select any Google Gadget
Customize to portlet
Leverages Portal’s Web 2.0 APIs support
Supports inter-portlet communication between Portal portlets and Google Gadget portlet instances.
Community SOA Wiki
Business Catalog forum
> 3600 Assets in IBM
SOA Business Catalog
role-based
in context
IBM is the first vendor to fully integrate consumer internet Google Gadget Services into an Enterprise Portal. A new IBM Portlet for Google Gadgets seamlessly integrates the familiar and easy to use internet Google Gadgets with WebSphere Portal and WebSphere Portal Express at no cost to our customers . Over 4000 Google Gadgets can now be combined with the over 5000 web services and portlets on our existing WebSphere Portlet Catalog and assembled into relevant, in context, composite applications for customers. This is a giant leap ahead of any competitor in delivering an unparalleled Portal ecosystem of web services to fuel our customers ability to innovate. All SWG products, Industry solutions, etc utilizing WebSphere portal as the user interaction component, now have increased business value and flexibility they can communicate to customers.
A few top Announcement highlights:
-Accessible Google Gadgets include a Podcast player with search, driving directions, translation services, delivery tracking, todos, surveys, business finder, and of course many more.
Business Benefit:
Extends reach of rich internet services to role-based business centric composite applications for improved flexibility and responsiveness.
Google Gadget Services
> 4000 Applications and Utilities
Portal Foundation Architecture

5. Client Side Aggregation
IBM WebSphere Portal
Client Side Aggregation
Turn your existing Portal Applications into “desktop like” applications
Highly reactive and direct user interface
Many actions possible without server roundtrips
Avoids page reloads
Improved performance and scalability
Reduced server side processing
Reduced bandwidth requirements
Reduced client-side processing
Improved cachability
Browser-side Aggregation, Navigation and Customization
Renders XML obtained from the server in the browser
Implemented using AJAX, XML, Dojo, and JavaScript
Accesses and manipulates Portal through REST*
REST-accessible Markup Fragments
Portlets or other
Atom / RSS Feeds
Gadgets
WSRP Services
In asiatischewn ländern gibt es bandbreiteb probleme.
*REST is the acronym for „Representational State Transfer“ It is the architectural model on which the WWW is based
“Most existing Portlets benefit directly from Web2.0 rendering model without any changes.”
WP 6.1Beta
Portal Foundation Architecture

6. Mashup Makers – Lotus Mashups
IBM WebSphere Portal
Mashup Makers – Lotus Mashups
Mashup Makers create Situational Applications
Rapidly created to address an immediate need of an individual or community
Typically, but not necessarily, short-lived (a just-in-time solution)
Good enough
Built by domain experts (knowledge workers) to solve their own problems
Make the points on the chart
Lotus Mashups provides a place for users to build and share Mashups without impacting other mission critical apps (such as those running on Portal)
Portal Foundation Architecture

7. Site Construction and Customization
IBM WebSphere Portal
Site Construction and Customization
Improved control for site owners by new Portal capabilities.
Theme Customizer Portlet
Customize the Look&Feel of Portal right within your Portal page
Improved readability of URLs
Navigation Link:
Action Link:
Enhanced Virtual Portal Support
Allow virtual portal identification by the hostname or a path segment
Configurable per VP if identification is encoded as part of the hostname or the path
HTML Page Aggregation
Deploy HTML pages to Portal (incl. all needed resources) and use it in your Portal site…
…protected by Portal entitlements…
…as full Page…or…decorated with banner and navigation…
…and use Portlets on your HTML pages if you want.
Do NOT automatically modify the WAS configuration when a new VP with hostname is created
Per default the virtual host mapping is *, so no configuration is required
If the host mapping has been restricted by a WAS admin, then this restriction should be removed by this WAS admin explicitly, not implicitly by the portal admin UI
WP 6.1Beta
Portal Foundation Architecture

8. Extended Business Process Support for WebSphere Portal
IBM WebSphere Portal
Extended Business Process Support for WebSphere Portal
Default Task Pages, access any tasks deployed to WebSphere Process Server
New My Tasks Portlet
More flexible views and sorting of tasks (Task Filters)
Hint: In the SOA Solution Catalog, you can find a Task List Portlet created in Portlet Factory that you can use as a jumpstart if you need your own Portlet.
Access to all human tasks defined in WID:
Exploit „task client“ information contained in the task description to allow dispatching to a default task page rendering the human task
Portal provides a default task page….
Task List dispatches to default task page if no specific page is specified.
This page contains a generic Portlet capable of rendering the task (build on BPC explorer JSF views).
Dedicated task pages can be defined for selected tasks.
Business Benefits:
Human tasks can be visualized on portal very easily.
Can focus on the key tasks and still support all.
Default task page can be modified in a central place to allow for consistent extensions.
Full flexibility with dedicated task pages.
WP 6.1
** Some of the ideas presented here may be delivered in future version of WebSphere Portal, but some will not.
Portal Foundation Architecture

9. Extend Search to more Search Services
Add your favorite search services to the WebSphere Portal Search Center Page. Integrate internal and external search services.
Dingering Search
Dingdong
Search
WP 6.1Beta

10. Portlet Standard Update
JSR 286 – Java™ Portlet Specification V2.0
IBM is leading this JSR, all major Java technology portal (commercial and open source) vendors represented in the EG
Reference implementation will be provided at Apache Pluto 2.0
TCK will be available for free (Will extend the JSR 168 TCK)
Schedule: final around early March 2008 (final Draft published)
Web Services for Remote Portlets (WSRP) V2.0
Standard protocol for accessing portlets as web service
Defined at OASIS, chaired by IBM
Common goals
Enable coordination between portlets and allow building composite applications based on portlet components (events and render context (e.g. public render parameters) )
Allow for a better user experience using AJAX patterns, Serving resources
WebSphere Portal seamlessly integrates JSR168, JSR286 and WSRP2.0 Portlets.
WebSphere Portal 6.1 Beta already supports JSR286 and WSRP 2.0.

11. Portlet Frameworks Supported by IBM Tooling
Java Server Faces (JSF) 1.1
JavaEE standard
Rational Application Developer (RAD) V7.0
Struts 1.1
IBM Struts Portlet Framework
Supports JSR 168 property broker extension
Portlet Factory
Build portlets based on models and builders instead of fine-grained UI components
Running on WebSphere Portal *
JSF V 1.2
Apache JSF Portlet Bridge
JSR 301 RI: Standard JSF-Portlet Bridge
covering JSR 168 (JSF 1.2), JSR 286 (JSF 1.2), RI part of Apache JSF Bridge
Apache Struts Portlet Bridge (V 1.x, V 2.0)
Spring MVC 2.0
Adobe Flex
Apache Wicket
And many more ...
The portlet bridge of the framework just needs to comply to either JSR 168 or 286
* IBM considers open source code and application frameworks installed by customers, either bundled as part of the application or as shared libraries, to be part of application code. Unless they are officially claimed as supported, it is the responsibility of the customer to ensure that these frameworks work with WebSphere Portal. If a problem is encountered when using these frameworks with WebSphere Portal, IBM will make reasonable efforts to ensure the problem does not lie with the WebSphere product. If the problem exists because of WebSphere Portal not behaving according to the specification that WebSphere Portal documents to support, IBM will try to address the issue. If the problem is caused by the framework or the customer code relying on an unofficial interface or undocumented behavior, it will be the responsibility of the customer or the framework owner to address the issue.

12. New APIs and SPIs - WebSphere Portal 6.1 Beta
Click to Action for every Portlet (API)
Enable the Click-to-Action paradigm for standards portlets (using Semantic Tags), Integrated with server side eventing
Portal Write Model (Java SPI and REST Service)
Create your own administration portlets (supports: Content-, Navigation-, Layout- and Portlet-Model, Unique names)
Client-side JavaScript library (API)
Convenience JavaScript APIs simplifying portlet development (e.g. support authentication proxies)
Step-up Authentication (SPI)
Define your own authentication levels (beyond what Portal 6.1 provides OOB), check for the rememberMe cookie
Login/logout/session validation Filters
Plug into the login/logout/session validation flow of portal
Property broker (SPI)
Write your own wiring portlet
Extend current portlet and portal models to support JSR 286 (SPI)
All APIs/SPIs available to JSR286 Portlets
Sitemanagment command (SPI)
Write your own Sitemanagement application
Encoding and decoding of friendly URLs (SPI)
Create friendly URLs and decode friendly URLs, Integrates into the resource addressability framework
Resource Addressability Data Source API (SPI)
Serve your resource addressable data via the default content handler servlet
LocalizedContext (API)
Allows you to get the preferred locales and titles / descriptions of Localized resources
WP 6.1Beta

13. AJAX Portlet Programming made Easy
Client-side aggregation (WebSphere Portal Capability)
Re-render only changed Portlets
In most cases no need to change the Portlet implementation
Client-side JavaScript library (API)
Convenience JavaScript APIs simplifying portlet development (e.g. support authentication proxies)
AJAX Proxy (WebSphere Portal Capability)
Allow portlets to connect to external data sources (in defined list) via WebSphere Portal Host
JSR 286 – resource serving (API)
ResourceURLs triggers method serveResource in interface ResourceServingPortlet
Portlet context available (render params, portlet mode, window state, preferences, ...)
Protected by Portal Access Control
WSRP resource proxy support (WebSphere Portal Capability)
Producer proxies in-band requests to resources
WP 6.1Beta

14. C2A for Standard Portlets – Live Text
IBM WebSphere Portal
C2A for Standard Portlets – Live Text
HTML Markup is enriched by tagging interesting areas in the Markup,
these parts become like (life) objects a user can interact with.
An Order Summary Portlet lists a set of active orders for the current month. (Each Order Id is represented as a “live object”)
The user clicks on the icon next to an Order Id.
A menu appears with a header that displays information about the item ordered and a photo of it.
Below the header are menu items which represent actions on the Order Id. The list of menu actions depend on which target Portlets are on the same page.
The user clicks on a menu item to execute an action.
Another Portlet on the page updates to display the result of that action.
<div class="c2a:source someotherclass">
<span class="c2a:typename" style=“display:none“>
<b
<p class="c2a:header" style="display:none;">
<b><c>This is a sample C2A source</c></b><br>
<b><c>You can add an optional header </c></b>
</p>
</div>
Source
<FORM class="c2a:target” onsubmit=“doSomething(this);return false” action=“javascript:void(0)” style=“display:none”>
<span class="c2a:typename">
<p class="c2a:action-label">Show inbox</p>
<input type=“text” class="c2a:paramname“></input>
</FORM>
Target
WP 6.1Beta
Portal Foundation Architecture

15. Security Enhancements - WebSphere Portal 6.1 Beta
IBM WebSphere Portal
Security Enhancements - WebSphere Portal 6.1 Beta
Remember Me Cookie Support
User can select the website to remember them for delivering personalized content without login
Also provides step-up Authentication Framework for customer authentication levels
Greatly improved Security Configuration
Less steps involved in frequent tasks like switching to LDAP (no disable/enable security required anymore)
Easier to use SSL and Key Management
Predefined Security profiles for WSRP
Easy to Setup and Use Federated User Repositories
SPNEGO support (Windows® Desktop SSO)
Automatically authenticate the user if logged into his desktop
Portal Foundation Architecture

16. Manage Your Portal – WebSphere Portal 6.1Beta
IBM WebSphere Portal
Manage Your Portal – WebSphere Portal 6.1Beta
Improve power of site owners by improved site capabilities.
Portal Page Publication out of the box by a click of a button
Support many daily updates to Page Layouts
Supports publishing of multiple pages
Workflow pluggable
Allow test/friendly users to validate a publish occurred correctly
Go back to previous version (1 level)
New Site Wizard
Easily create new Portal sites in Virtual Portals
Deployment of Themes and Skins
Move Themes/Skins into their own EAR.
Deploy Themes and Skins as normal EARs.
Portlet Resource Monitoring
Monitor Portlet Requests, Response Times, Errors, number of loaded Portlets
Monitor Request Metrics including Portlets
Greatly simplified Security Configuration
SSL support out of the box
WSRP security profiles
IBM Support Assistant
Reduces effort to support WebSphere Portal and Express
Search for Q&A
Easily send logfiles and configuration data to IBM support
Do NOT automatically modify the WAS configuration when a new VP with hostname is created
Per default the virtual host mapping is *, so no configuration is required
If the host mapping has been restricted by a WAS admin, then this restriction should be removed by this WAS admin explicitly, not implicitly by the portal admin UI
Portal Foundation Architecture

17. Install, Migration, Maintenance Improvements
IBM WebSphere Portal
Install, Migration, Maintenance Improvements
Make it easier to get to WebSphere Portal 6.1 and stay current.
Install
Faster OOB Install compared to previous releases (under 1 hour on most of platforms.)
Multiple packaging options (Content, Server)
Multiple installation options (Empty, Admin, Full)
Improved OOB configuration defaults, OOB automation of common tune up steps
Clustering automation to simplify building clusters.
Portal filesystem assets will be split between read-only and read-write (Profiles)
Clearer doc on out of box install, targeted to platform and db
Migration
Migrating from any previous release to 6.1 will see the following improvements:
Simplified procedure (Improved automation for customizations and security)
Automatic redeployment of customer apps
Automatic migration of WAS settings.
Improved documentation
In addition, customers migrating from v6.0 will see these additional enhancements
Near zero downtime migration (Re-use of DBs in place)
Maintenance
FixCentral as a single consolidate place for fix downloads and prereq verificaiton
“two click” full stack upgrade ("1 click" for stack underneath portal and then "1 click" for portal)
SystemApps make upgrade substantially faster for the core service components
No need to repackage wps.ear to keep Theme and Skin customizations
complete upgrade automation
Install
Faster OOB Install compared to previous releases – under 1 hour install on most of platforms.
Multiple packaging options
Content, Server
Multiple installation options
Admin, Full
Improved OOB configuration defaults
OOB automation of common tune up steps
Re-use of clustering automation from Quickr to simplify building clusters.
Portal filesystem assets will be aligned as read-only under the Portal root and read-write under the profile.
Following WAS model
Enable easier Portal farming
Clearer doc on out of box install, targeted to platform and db
Migration
All customers migrating from a previous release to 6.1 will see the following improvements:
Improved documentation
Simplified procedure
Improved automation for customizations and security.
Automatic redeployment of customer apps
Automatic migration of WAS settings.
In addition, customers migrating from v6.0 will see these additional enhancements
Near zero downtime migration
Re-use of DBs in place
Maintenace
“two click” full stack upgrade
"1 click" for stack underneath portal and then "1 click" for portal
usage of SystemApps will make upgrade substantially faster for the core service components
binary replacement vs re-deployment
separation of themes and skins from wps.ear
customers won't have to repackage wps.ear to keep their customizations
complete upgrade automation
no manual steps should be left behind in the documentation
FixCentral as a single consolidate place for fix downloads and prereq verificaiton
WP 6.1Beta
Portal Foundation Architecture