1 / 46

WebSphere Portal Update 2007 / 2008

Stefan Liesche, Rob Will, Uwe Hansman,…. WebSphere Portal Update 2007 / 2008. This Presentation is covering the plan for the Portal Server and WCM. Accelerator plans will be covered in other presentations. Enriched single portal platform and tools.

charlottenelson
Download Presentation

WebSphere Portal Update 2007 / 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Stefan Liesche, Rob Will, Uwe Hansman,… WebSphere Portal Update2007 / 2008

  2. This Presentation is covering the plan for the Portal Server and WCM. Accelerator plans will be covered in other presentations. • Enriched single portal platform and tools Portal Server: Composite application / business mashup framework and advanced tooling to build SOA-based solutions WebSphere Portal Server and Accelerators An expanded approach to offering Portal value to customers Capturing Common Patterns • Five new Portal Accelerators Dashboards Collaboration Self Service Enterprise Suite Content Integrated packages that easily snap-on to WebSphere Portal to deliver rapid time-to-value for specific business challenges

  3. WebSphere Portal - Release Themes • Enable customers to deploy on WAS 6.1 and WAS 7.0** • Continue to simplify the creation, customization and deployment of portal • Improve UI responsiveness • Continue to open Portal up to ‘non-Portlet’ technologies • Web 2.0 (Feeds, ATOM, AJAX,...) • Plain HTML, PHP, etc. • Gadgets and Widgets (iWidgets) • Continue Portal standards ** at or near WAS 7.0 GA

  4. Where we are…. WebSphere Portal 6.1 Beta Google Gadget Portlet WCM 6.0.1.2

  5. WebSphere Portal 6.1 – Open Beta is Live!! https://www14.software.ibm.com/iwm/web/cc/earlyprograms/lotus/wps61beta/

  6. WebSphere Portal 6.1 Beta 1September 2007 • Initial Set of Features • Simpler download/install • New Web 2.0 support to dramatically improve performance of the browser based user experience • New Site management capabilities greatly improve abilty to promote portal applications from test to production • Step-up authentication providing options to extend end user security options • New Theme customizer portlet improves ability to create and manage portal themes • Updated out of box example web sites with new support for preconfigured internet security and virtual portal support • Supports WAS 6.0.2 • Platform coverage • Windows Server 2003 • Linux for System x 86Series • i5/OS V5 OS/400 V5 Forum: http://www.ibm.com/developerworks/forums/dw_forum.jsp?forum=1127&cat=9

  7. WebSphere Portlet Factory Beta 1September 2007 • Initial Set of Features • Improved out of the box experience -- WAS CE as a pre-configured test environment • Support for Lotus Expeditor and Notes 8 Support, • Quickr 8.0 support, REST service builder (including support for Lotus Connections) • Webcharts update • Full installer • Improvements in memory footprint • Improved composite application component interoperability • Fully updated documentation for all new features • Platform coverage • Windows Server 2003 • Windows XP Forum: http://www.ibm.com/developerworks/forums/dw_forum.jsp?forum=1150&cat=9

  8. Google Gadget Integration - Continued Google Gadgets receiving events from Portlets location The event configures the Google Gadget. If needed, the Portlet translates the event to match the Gadget configuration in the IBM Gadget Portlet. http://catalog.lotus.com/portal?NavCode=1WP1001AJ

  9. WCM 6.0.1.2 - Content13 October 2007 • Multi-realm support • User/group selection will be scoped to current realm • Enables WCM to be used in virtual portal environment • Customer requested APIs • New API to retrieve content by author • Avoid post filtering, which is too slow • Multilocale Whitepaper • Outlines a methodology for using WCM to manage multilocale sites • Includes sample code for a basic implementation • Multilocale enablement APIs • APIs required for the sample code in the whitepaper – these are added to improve the performance of the suggested solution, and to provide an additional hook in the UI for extensibility.

  10. What is next….. WebSphere Portal 6.1 Beta 2 WebSphere Portal 6.1 Workplace Web Content Management 6.1

  11. WebSphere Portal 6.1 Beta 2December 2007 • Contributing Tiger Teams (beyond Beta 1) • WAS 6.1 exploitation TT • Standards TT (JSR286, WSRP 2.0) • Web 2.0 TT (JSR286) • Site Management TT (HTML Pages – TechPreview) • Workflow TT (SOA Process Portal Next) • Express TT • WCM Enhancements (Performance, Rich Test Editor, Platform Exploitation) • Extranet Support, Impersonation API, Trusting Groups • Connections Integration • Supporting WAS 6.1 • Platform coverage • Windows Server 2003 • Linux for System x 86Series • i5/OS V5 OS/400 V5

  12. Architecture Overview WebSphere Portal V6.1 Desktop and mobile Browsers, Mashups and offline Clients iWidget Feed Provider J2EE Portlet Container and Services AUTHENTICATION JSR286 Portlet API JCA JMS Page Aggregation Themes and skins Dynamic UI Manager JDBC Web Services Content access Web clipper Portlet Preference Servlet EJB Search Feed Services Collab- oration Page Handler Rules Caching Security AJAX Proxy Single Sign-on Site Admin Credential Vault Portal Model Policy WSRP 1.0 + 2.0 WSRP 1.0 + 2.0 Remote portlet consumer TemplateComposition Application Runtime AUTHORIZATION Workflow Component Handler Enterprise Data, Applications, Internet Content Process Server Remote portlet producer XML Access Portal Script REST / APP User profile Database Portal Database(s) LDAP Directorie(s)

  13. Technical Release Summary • Platform • WAS 6.1 ND included in OOB • WP6.1 supports multiple (independent) installs on the same level of maintenance in a single cell) • WAS 7 toleration built into the GA version already (do not wait for the next FP). • Migration • In-place migration (WAS semantics) is desired but not 100% achieved with WP6.1 • Database schema changes: • Customization DB: can be shared by WP6.0 and WP6.1 installs • Community DB: requires migration (migrate WP data + JCR data in place for Quickr migration) • Release DB: requires migration (XMLAccess export/import) • JCR: InPlace (does not need to be shared between WP6.0 and WP6.1, but no import export • Component Changes: • PDM will be removed from WP (incl Content Accelerator), there will be Quickr. • PDM and MDL portlets will be removed. • Browser plugin used in PDM and Desktop Integration will be removed. • Content repository (fka JCR) continues to be in the base (manage dependencies explicitly) • Stellent filters will stay in the release for use by Search and WCM in WP 6.1 • CMAPI will be provided for WP 6.1, but it will likely be deprecated in this release (discussions ongoing) • LCD runtime might be moved into separate download (not yet contained) • Transcoding might be moved into separate download (not yet contained) *topics in this color are in discussion

  14. RAD 7.5 (Sept 2008) supports WP 6.1 Discussion on single JVM runtime for process portal development [not in plan] Support for portal instances per project (e.g. multiple instances via profiles) [not in plan] New features in RAD 7.5 JSR 286 support ….<tbd> Portlet Factory / Dashboards – with WP GA New Features in PF Visual editor and Designer enhancements (this is a significant update to the developer experience) JSR 286 support (this is already well in progress) Support for WAS portlet container (this is mosttly deployment-related) Web service enhancements LCD (will not be bundled with WP 6.1) DRAFT Related Products - Requirements Server Tools • Notes / Domino: • Improving Composite application support. • Quickr 8.5 (as of 26.07.07) • JCR enhancements mainly in performance and scale • More efficient integration between search and JCR • REST interfaces for access control and AI [not in plan] • In place JCR content migration • URL Stability across major versions • AI performance and reliability enhancements • eBPC • WCM merge • Active Insight • Documents,….(further info coming) • Other Opened Requirements: • Notes: • Quickr requires code changes to run on top of WP6.1 (CAI/TAI APIs have significantly changed) • Accelerators ship independent of Portal Server. • PDM forms integration will no longer work with WP6.1 (new Forms list UI required as the PDM portlet is gone).

  15. More details on WP 6.1

  16. WebSphere Portal 6.1 – Content OverviewGM April 2008, eGA/GA May 2008 • Web 2.0 support • Site Management • WAS 6.1 exploitation • Process Portal enhancements • JSR286 • WSRP 2.0 • Step Up Authentication • WCM Enhancements • Enhanced integration with Lotus Connections

  17. Web 2.0 support • REST Servicesto open up portal for mashup applications – services for server persistence, portlet settings and user profile access to simplify Web 2.0 application development • AJAX Portlet Programming Model Extensionsbased on Dojo+IBM Extensions • Client Side Aggregation and Customization using REST Services for better UX and improved performance • AJAX Client Side Feed Consumption to enable highly efficient integration of information through feeds (Atom and RSS) • Semantic Tagsto allow smart markup to enable value add by portal, e.g. dynamic menus • Client Side C2A/Property Broker and Drag & Dropbased on Semantic Tags integrated with server side property broker and C2A support to enable cross-portlet interaction locally in the browser as well as with server side code • Sample AJAX Portlets with source showcasing the new capabilities to demonstrate and give samples to customers for how to exploit all the above

  18. Details Semantic Tags

  19. <div class="c2a:source someotherclass"> • <span class="c2a:typename" style=“display:none“>http://…datatype#email822</span> • <b class="c2a:value">johndoe@acme.com</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"> http://www.ibm.com/xmlns/prod/datatype#email822</span> • <p class="c2a:action-label">Show inbox</p> • <input type=“text” class="c2a:paramname“></input> </FORM> Target C2A for Standard Portlets – Semantic Tags • Standard Portlet Server-Side Target • 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.

  20. Details REST style Web Services exposing Portal to Mashups • Goals: • Separate portal user experience from portal data • Expose relevant data separately for use by other apps ( Mashups) • Public REST style Web services for • Access toNavigation Node Hierarchy • Access toPage Definitions • Access to User Profiles • Access to genericContent Persistence • Access tomarkup fragments of individual portlets • Mashups can use these services to implement custom applications leveraging portal infrastructure services • WebSphere Portal’s Web 2.0 Client Side Aggregation uses these services as well

  21. Details Web 2.0 Fragment Model • Simple and extensibleWeb 2.0 fragment programming model • Agnostic of how fragments are generated, may be • generated by portlets on WebSphere Portal • generated by PHP code on Web.0 or PHP servers • generated by .NET servers • Canstart simple, with option to grow more sophisticated • Basic fragments – HTML only • Slightly more advanced – add use of Semantic Tags • More advanced – add use of Dojo and custom JavaScript • Fragments can use public JavaScript interfacesto conveniently invoke WebSphere Portal’s REST-style Web services

  22. REST-accessible Markup Fragments Portlets or other Atom / RSS Feeds Gadgets WSRP Services Web 2.0 Client Side Aggregation • Browser-side Aggregation, Navigation and Customization • Renders XML obtained from the server on the browser side • Implemented using AJAX, XML, Dojo, and JavaScript • Accesses and manipulates Portal through REST* services • Superior user experience • Highly reactive and direct user interface • Many actions possible without server roundtrips • Avoids page flickering • Improved performance and scalability through • Reduced server side processing - offloads rendering to browser • Reduced bandwidth requirements between server and browser • Reduced client-side processing – mostly fragment reloads, few page reloads • Improved cachability, all artifacts can be cached independently *REST is the acronym for „Representational State Transfer“It is the architectural model on which the WWW is based

  23. Details AJAX based RSS/Atom Feed Consumption • Allow simple consumption and display of Feeds in portal pages • ATOM or RSS feeds • Implemented using AJAX, Dojo and JavaScript • Gets settings defining the feed to display from portal • Retrieves feeds from origin servers via AJAX proxy • Renders feeds in the browser rather than causing server load

  24. Site ManagementImprove power of site owners by improved site capabilities. • Reduce URL management and improve readability of URLs • Navigation Link: www.ibm.com/wps/myportal/MyPlaces/Welcome • Action Link:www.ibm.com/wps/myportal/MyPlaces/Welcome/!st/04_SB8K8xLLS.. • Enhanced Virtual Portal Support • Allow virtual portal identification by the hostname or a path segment • www.myVP1.ibm.com, www.myVP2.ibm.com • Configurable per VP if identification is encoded as part of the hostname or the path • New Page Type Support • Publish HTML pages and related files for rendering via Portal • Use Portlets on these pages • Portal Site Publication out of the box by a click of a button • Make pages, content and their related artifacts easier to work with • Support many daily updates, and publishing whole sites • Version-able and Archive-able, Workflow pluggable • Be able to go back to previous version very quickly • Allow test/friendly users to validate a publish occurred correctly • Deployment of Themes and Skins • Move Themes/Skins into their own EAR.

  25. Details Friendly URLs • Friendly/Predictable/Readable URLS • Ability to specify a friendly name on pages • When any url is generated by portal, it will use the friendly name if there is one, when generating all urls. • One note: for portlet action urls, they will be friendly up to and including the page name, but after that part, the encoded portlet state will be added. • The URLs that appear in the address bar of the browser will be human readable and modifiable • If a url mapping is used, it takes precedence over friendly urls in our lookup. • New public api will be provided • New config choice to turn on/off friendly urls • Themes could use navigation state apis for generating navigation urls, with option for not generating state, so that clicking on navigation links in the theme, don’t cause state to be added. • Side affect is portlets will be in their initial state on page change

  26. Details New Site Layout Support • Goals: • Allow any normal web designer/developer that knows HTML: • Define page layouts • Define site structures • Use portlet applications in these sites • Let designers use existing web creation tools for defining portal pages • Provide ability to: • Generate portal sites that run close to the same speed of a static web site • Inter-mix, static pages, WCM pages, and portal pages • Use new Web 2.0 features to give a very rich experience • Support any possible layout, CSS configuration • Allow generating sites that support any accessibility compliance guidelines

  27. Site Management UIs Site Management Portlet (run anywhere) $Site Publish <id> <source> <target> $Site Undo <id> <source> <target> $Site Promote <id> <target> $Site Demote <id> <target> >_ Portal Script (JACL support) dummy Syntax

  28. Details Easier Theme Deployment • Move themes and skins out of the WPS.ear • Allows them to be self contained • Existing themes in WPS.ear will still work, so you don’t have to take advantage of this new function • Existing themes/skins will work without changes, when packaged as a WAR. • They can be updated dynamically, without restarting portal. • They can be packaged through tools • Deployable using normal WAS deployment features • If for some reason the theme/skin is not available (not started, restart, etc…), a default theme and/or skin will be used out of the WPS.ear • Separate context path for each theme • Support having multiple theme.war files in the same ear, and also support having multiple ear files • We will also be writing a couple of white papers to cover: • example of WCM based themes • flexible themes using our eclipse extension points in the V6 themes, and policy to customize a theme without having to redeploy artifacts.

  29. WAS 6.1 Exploitation • Enables customers to standardize on/deploy on WAS 6.1 or WAS 7.0 • Improved Scalability, Reliability and Performance of Composite Applications • 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 • SPNEGO support (Windows Desktop SSO) • Easy to Setup and Use Federated User Repositories • Multiple LDAPs supported out of the box on the WAS level • Enhanced Performance and Reliability with JDK 1.5 • Exploitation of new WAS 6.1 Features • Portlet Resource Monitoring • Simplified Portlet Deployment • … • WAS 7 Toleration

  30. Extended SOA Process PortalDefault Task Pages • New My Tasks Portlet • More flexible views and sorting of tasks • Written using Portlet Factory for easier customization • Make it easy to visualize processes defined in WID in portal: • Exploit „task client“ information contained in the task description to allow dispatching to a default task page rendering the human task • Portal provides default task pages for the set of clients supported by WID (i.e. portal, BPC, forms, ...?) • The default task page contains a corresponding portlet capable of rendering the task (BPC explorer portlet, XForms portlet, ...?) • Task List portlet automatically dispatches to matching default task page if no specific page is specified • Benefits: • no need to agree on task page unique names • default task page can be modified in a central place to allow for consistent extension (e.g. adding task history information) • Human tasks can be visualized on portal very easily • Full flexibility with dedicated task pages can still be leveraged if desired

  31. Details JSR 286 (the Java Portlet API) • Java Portlet API (JSR 168 and successors) is the recommended API for building portlets • IBM leads the EG of JSR 286 (V2.0), EG has 29 members • including BEA, Oracle, SAP, Sun, and many open source portals. • Early drafts of V 2.0 are already available, final version is targeted for 2007, IBM is working together with Apache for the RI • Main themes of JSR 286 include • coordination between portlets (events, shared render parameters) • serving resources (AJAX support) • support of WSRP 2.0 • better integration with existing web frameworks, like Struts, JSF, and Webworks • IBM Portlet API is deprecated in WP v6.0. demonstrating IBM commitment towards open standards.

  32. Details WSRP 2.0 • WSRP 2.0 allows to connect and assemble remote UI services • IBM chairs the TC which consists of 18 members, including BEA, Oracle, Sun, Netunity,.. • Final approval of specification expected in 2007 • Features: • Eventing, aka Consumer mediated Coordination • Public Navigational Parameters • Leasing of Resources • Import/Export and Copy portlets • Most of the WSRP 2.0 Features are optional • Consumers and Producers can opt to implement them • WSRP 2.0 adds protocol additions and features without much change to the protocol semantics

  33. Impersonation and Step-up Authentication Strength Certificate(e.g. from SmartCard Reader) Strong Authentication APIs only Username/Password(e.g. HTTP form based login) Remember-meCookie OOB Claim of Identity(e.g. persistent cookie) Help DeskVacation DelegationRole Impersonation APIs only Identity/Role role Teller Alice Bob Clarice

  34. Access to sensitive service or operation,... …requires user authentication… … before access is provided. Step Up AuthenticationThe site recognizes me without login… Customer identification with your Website can increase customer loyalty.

  35. WCM 6.1 • Security • Inherited security support • “User” and “Contributor” roles • Additional virtual users for [Authors], [Owners], [Creators] • Active content filtering (disabled via config option by default) • Performance • Changes to WCM node structure (to remove unnecessary nodes and speed up authoring save time)‏ • Library mode to disable content links (linking a ContentItem to multiple places in the site structure)‏ • Presentation • Improved Rich Text Editor • Authoring tools component enhancements • Authoring template profiling in WCM rendering portlet • Dynamic page sizing and “jump to” paging control • Upgrade Person tag support • Truncation support in WCM tags • New rendering options for base components (relative date formats)‏ • HTML encoding support in WCM tags • WAS 6.1 Exploitation • Authoring and templating • Authoring template enhancements for very simple authoring forms • Insert Link and Insert Image dialogs Ux enhancements • Removal of file transfer applet in teamspace authoring scenarios • New “Short text” component • New remote actions to trigger more Ux function via Urls (in support of inline editing)‏ • Versioning options by content type and template • Additional Workflow action to save a version • Administration • Administration reporting (for long running tasks • Improved library management (delete library administration tasks)‏ • API • Allow users to be assigned by DN • Expose more WCM function through API • Library Service cache scaling improvements (and support for embedded libraries)‏

  36. Details New Public APIs • Public APIs for V6.1 • C2A for standard portlets • Available for standard portlets • Client-side portlet programming model • Available for standard & IBM portlets • Remote access to portlet modes • REST services for the portal models • User profile REST service • Public SPIs for V6.1 • Portal write model • Allow portlets to create new pages, put portlets on pages, … • Available to themes&skins and standard portlets • Login/Logout/Session validation filters • Allow customizing the login/logout/session validation behavior • Step-up authentication • Allow using different levels of authentication • Available to standard & IBM portlets • Public APIs added in V6.0.1 • Search menu tag lib • Allows adding custom search scopes • Available to themes&skins, standard and IBM portlets • Extension to the credential vault service • Support LTPA tokens • Available to themes&skins, standard and IBM portlets • Public SPIs added in V6.0.1 • Portlet Object Model • portal model reaches all the way down to the portlet window • Available to themes&skins and standard portlets • Puma profile now supports external users • Available to themes&skins, standard and IBM portlets • Login service • Allows customers creating their own login portlet • Available for standard portlets • Resource addressability • Lookup of resources • Available to themes&skins, standard and IBM portlets • ATOM SAX API • Parser for ATOM feeds in Java • Standalone component • URL resource service • For managing URL resource definitions in the WAS CM Available for standard portlets

  37. Release Collateral

  38. composite applications Web Content Mgmt Expeditor Web Services role-based REST REST Services process- driven Google Gadgets Feeds in context Remote Portlets IBM WebSphere Portal HTML/PHP Connections Documents WebSphere Portal V6.1 Produce and Consume Clients Services Portlets Web Mobile Devices Critical enabler: Openness • Standards based access to integration and innovation

  39. Why Portal V6.1?Portal V6.1 Business Value on top of what is in Portal V6.0 • Extend the reach of your Portal • Leverage the Internet in context of your business (event enabled Google Gadgets) • Interactive information - Smart markup with Semantic tagging • Integrate non-portal technologies more easily • More Flexible, Productive Administration • Empower the business to manage the Site • Resource Monitoring for Portlets • Improved Performance • Much better user experience with highly-responsive UIs • Less server request  reduced load on portal servers. • Less bandwith required because less markup is transferred. • Composite Application Infrastructure Performance and reliability • Server Startup time • Improved Reliability and Resiliency • Enhanced support for implementing high-performance, scalable, thread-safe applications (JDK 1.5) • Enhanced Web-Services Standards

  40. Why Portal V6.1?Portal V6.1 Business Value on top of what is in Portal V6.0 • More easily adopt SOA stack • WAS currency (WAS 6.1 / 7.0) • Improved Consistency with WAS • Simplified Portlet Deployment and Management • Consistency with WAS management model • Simplified User management deployment and configuration • Simplified Security setup, configuration and integration • Protect Existing Investments • Full support for your existing Applications using Legacy API, JSR168 or WSRP 1 • Interoperability between old and new standard (JSR 168 & JSR 286) • In some cases existing Portlets are automatically improved by new capabilities • Simplified Install and Deployment • Simplified Security Configuration • Fewer server restarts, Federated User Repositories, Multiple Repositories, SSL+KeyMgnt,… • Simplified Webservices configuration • Easier System integration with latest webservice standards (with WAS ws-feature pack) • improved interoperability, easier configuration, reliability

  41. Details Additional Value for Portal Developers New Portlet Standards (JSR 286) • Enhanced developer productivity • Simplified AJAX support (fragment refresh) • Self contained Portlets (no Servlet needed) • Simplified eventing model (without WSDL) Ability to leverage WOA technologies • ATOM, REST, Feeds, PHP... • Enhanced Java Programming Model (JDK1.5) • Enhanced Developer Productivity • For-Each constructs • Auto-boxing / Un-boxing (automatic type cast) • Annotations (Deployment data within the Java Code) • variable list of arguments for functions • Early detection of programming errors (at compile time instead of run time) • Generics (Implement a method once for various types) • TypeSave Enumerations • static import • Reliable Programming and Resilliency • Improved Thread Control and monitoring • attach monitoring at runtime without application re-start • Concurrency Utilities high-performance, scalable, thread-safe applications • Enhanced Libraries • networking • security • internationalization • Enhanced Collection Framework • JAXP support in the JDK

  42. What is next….. • WebSphere Portal for WAS 7 Beta • Accelerator Candidates for 2008…. • Content Accelerator 6.1.1 • Forms Portal Accelerator • Business Process Accelerator • Customer Self Service Accelerator • Citizen Self Service Accelerator • …

  43. Additional WebSphere Portal Accelerator Candidates Business Process Accelerator • Lotus Forms, My Tasks portlet and out of the box business processes defined in Modeler and WID, with corresponding portlets, portal pages and Lotus Forms • My Tasks portlet federates users tasks from Process Server, Filenet and other sources Citizen Self Service Accelerator • Leveraging assets from Portal deployments with Federal, State and Local governments Customer Self Service Accelerator • Leveraging assets from Portal deployments within IBM and our customers that make it easier to build a portal for customer self service

  44. IBM Content Accelerator – What’s New • Replace PDM with Quickr Documents • More capability such as customizable metadata, customizable views, etc • Deployed on its own server and linked to portal server via • My Places Portlet • Feed Portlet • Latest WCM • As described earlier • Plans to refresh in 2H08 with additional capabilities • Tighter integration with Portal, in particular site structure • Grouping of updates for preview and publish • Filenet integration • Web Analytics integration • UI enhancements • JSR 286 portlet support

  45. Thank You !

  46. Some Links • Java Portlet Specification V2.0 (JSR 286) • http://jcp.org/en/jsr/detail?id=286 • Web Services for Remote Portlets Specification v2.0 • http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-spec-pr-03.pdf • Portal Accelerators: • http://www-306.ibm.com/software/info1/websphere/index.jsp?tab=landings/portalbuzz • iWidget Spec • https://w3.webahead.ibm.com/w3ki/download/attachments/643853/iwidget-spec-wd-05.html • Portals in Government • http://w3-103.ibm.com/software/xl/portal/viewcontent?type=doc&srcID=XT&docID=I848962D10246I79

More Related