Skip to main content


developerWorks  >  WebSphere | Lotus | Sample IT projects | Java technology  >

Build portlet applications to access Domino

Using the Domino custom JSP tags to simplify development

developerWorks

Level: Introductory

Thomas Reske (resket@de.ibm.com), Author, IBM
John Bergland (john_bergland@us.ibm.com), Project Leader, International Technical Support Organization, Cambridge Center

06 Aug 2004

Register now or sign in using your IBM ID and password.

This tutorial explains both the benefits and the methodology for integrating a Domino application into WebSphere Portal utilizing the Domino custom JSP tags. It provides an overview of the JSP technology and outlines the advantages, as well as the limitations of using the Domino custom JSP tag libraries. Finally, it explains both the theoretical background and covers step-by-step instructions on how to build a portlet application that accesses a Domino Journal database leveraging the Lotus Domino Toolkit for WebSphere Studio.

Prerequisites

This tutorial is recommended for Domino developers who want to quickly become productive in enhancing their Web applications by using J2EE technologies. It is also suited for J2EE developers who want to incorporate Domino capabilities without advanced knowledge of the Domino object model. Both developer groups can extend their knowledge about portalizing a Lotus Domino application by using the Domino custom JSP tag libraries. It is recommended that you have some experience with IBM WebSphere Studio Application Developer and Lotus Domino Designer.


System requirements

To complete the steps as demonstrated in the tutorial, you will need to have the following software installed:

  • WebSphere Studio Application Developer version 5.1.2
  • Lotus Domino Designer version 6.5.2
  • Lotus Domino Server version 6.5.1 or higher
  • IBM Portal Toolkit version 5.0.2.2



Duration

Under two hours


Formats

html, pdf


Share this....

digg Digg this story del.icio.us del.icio.us Slashdot Slashdot it!


Back to top


Document options

Document options requiring JavaScript are not displayed


My developerWorks needs you!

Connect to your technical community