4.1 Overview of the Domino custom JSP Tag option

< Day Day Up >

In the previous chapter we reviewed some simple methods of integrating Lotus Domino applications with WebSphere Portal, and found limitations in those methods that need to be lifted for real world implementations. Some of the limitations are addressed in this chapter as we explore the benefits available from technologies like J2EE and tools like WebSphere Studio Application Developer.

One of the most common situations when integrating Lotus Domino applications is that you are faced with a growing number of J2EE applications that should interact with Lotus Domino applications. A basic knowledge of the capabilities J2EE brings to a Lotus Domino developer is important in the current marketplace.

Combining J2EE technology with Lotus Domino in a portal environment helps overcome several challenges, like the ones outlined in the first chapter. For example, with J2EE there is access to transactional services and personalization services that will extend your current Lotus Domino application.

Exposing your current Lotus Domino applications through WebSphere Portal will lift some of the weight that Lotus Domino has to handle as a Web application server.

Integrating Lotus Domino applications with JSP Tag libraries yields shorter development time than that for a custom Java development option. The technology comes with some limitations, especially regarding performance. These limitations are discussed as we explore each integration technique.

You will probably choose this integration option if the functionality of prepackaged portlets isn't enough to fulfill your integration needs, and if there is an underlying motivation to understand what Java technologies bring to Lotus Domino when developing WebSphere Portal applications.

< Day Day Up >