Level: Intermediate Benson Chen (bensonc@us.ibm.com), Advisory Software Engineer, IBM
Vijay Dheap (vdheap@us.ibm.com), Staff Software Engineer, IBM
21 Sep 2005
Updated 21 Dec 2005 This tutorial provides a step-by-step approach to creating a portlet service that can be invoked by either an IBM portlet or a JSR 168 portlet. With this knowledge, portlet developers can create new portlet services that can be accessed by either the IBM Portlet API or the JSR 168 Portlet API. You can also update older portlet services to support new JSR 168 portlets. Finally, you see how to enhance the performance of portlet services by making use of the Command Cache. Includes a download.
Objectives - Create the portlet service
- Create an IBM portlet which accesses the service
- Create a JSR 168 portlet which accesses the service
- Configure the Command Cache
- Revise existing portlet services to be accessible from JSR 168 portlets
Prerequisites
You should have these basics skills:
- Familiarity with Rational Application Developer
- Understand portlet development concepts
- Basic Java™ coding skill
System requirements
You need the following software installed to work through the scenario in this tutorial.
- IBM® Rational® Application Developer for Rational Software Development Platform V6.0
- IBM WebSphere® Portal V5.1.x
- IBM WebSphere Application Server 5.1.x
See Product trial downloads for currently available trial software.
Duration
2 hours
Languages English
Formats pdf
Summary
IBM WebSphere Portal Version 5.x supports the JSR 168 Portlet API in addition to the IBM Portlet API. The portlet service construct plays an important role in the development of maintainable portlet applications. Knowing how to create a portlet service which can be accessed by either an IBM portlet or a JSR 168 portlet enables portlet developers to create flexible, maintainable applications. You can also apply what you learn in this tutorial to update older portlet services to support JSR 168 portlets. Finally, you see how to enhance the performance of portlet services by making use of the WebSphere Command Cache.
| 
