List of Figures

---

Chapter 1: Introduction to Portalizing Domino Applications

Figure 1-1: Horizontal and vertical portals

Figure 1-2: WebSphere Portal architecture

Figure 1-3: Dynamic workplace Example

Figure 1-4: Domino's history- From e-mail only to a mission-critical platform

Figure 1-5: Portal page with several portlets displaying weather, news, and so forth

Figure 1-6: Portlet modes example

Figure 1-7: Example of a workplace with portlet cooperation

Figure 1-8: From Domino applications to portlets and workplaces

Figure 1-9: Factors and dependencies

Figure 1-10: Domino application types

Figure 1-11: Example portlet "Employee Directory"

Figure 1-12: Link type example

Figure 1-13: Display type example

Figure 1-14: Integrated type example

Figure 1-15: Elements of a Portlet

Figure 1-16: News portlet

Figure 1-17: New Documents portlet

Figure 1-18: Portlet with personalization and form display

Figure 1-19: Portal/Domino Infrastructure options - D1, D2 and D3 represent Domino servers

Figure 1-20: Page layout example

Figure 1-21: Basket of integration options

Chapter 2: Integration Techniques

Figure 2-1: The Lotus Notes interface for the Sales Tracking application Sales DB

Figure 2-2: The Lotus Notes interface for the Sales Tracking application Customers DB

Figure 2-3: Example of a customer information workplace

Figure 2-4: Browse for the WAR file

Figure 2-5: Check for the portlets that will be installed

Figure 2-6: Portlet successfully installed

Figure 2-7: Creating a new place

Figure 2-8: Create page options

Figure 2-9: Adding portlets

Figure 2-10: List of portlets

Figure 2-11: Portlets added to the ITSOTester page

Figure 2-12: Portlets displayed on your page

Chapter 3: Using Existing Portlets

Figure 3-1: The QuickLinks portlet in display mode

Figure 3-2: QuickLinks portlet

Figure 3-3: QuickLinks portlet configuration for Quick Browse URLs

Figure 3-4: QuickLinks portlet with example links

Figure 3-5: Result of clicking the first link in Quick Browse

Figure 3-6: Result of clicking the second link in Quick Browse area

Figure 3-7: Result of clicking the third link in Quick Browse area

Figure 3-8: Result of clicking the fourth link in Quick Browse area

Figure 3-9: Web Page portlet before configuration

Figure 3-10: Web Page portlet configuration

Figure 3-11: Configured Web Page portlet

Figure 3-12: Result of clicking the first highlighted link inside of the portlet

Figure 3-13: Web Clipper Portlets page

Figure 3-14: The Web Clipping (administration) portlet

Figure 3-15: Adding a Web clipper- Edit screen 1 options

Figure 3-16: Set title for selected locale page from edit screen 1 options

Figure 3-17: Modify clipping type page from edit screen 1 options

Figure 3-18: Modify firewall options page from edit screen 1 options

Figure 3-19: Modify authentication options page from edit screen 1 options

Figure 3-20: Credential vault options

Figure 3-21: Modify rules for URL writing page from edit screen 1 options

Figure 3-22: Modify security options page from edit screen 1 options

Figure 3-23: Web Clipping portlet edit screen 2 options

Figure 3-24: Close-up of "clipping" using the Web Clipping portlet

Figure 3-25: Result of clicking a highlighted link in the Web Clipped portlet

Figure 3-26: Result of clicking the navigation Next

Figure 3-27: Domino portlets page before configuration

Figure 3-28: Lotus Notes View portlet edit mode- Page one

Figure 3-29: Lotus Notes View portlet edit mode- Page two

Figure 3-30: Result of modifying the Lotus Notes View portlet

Figure 3-31: Result of clicking the first highlighted link in the Lotus Notes View portlet

Figure 3-32: ContactsRSSbyName view

Figure 3-33: Creation of a $$ViewTemplate for the ContactsRSSbyName view

Figure 3-34: CustomersByName view in the Customers database

Figure 3-35: Customers.XSL stylesheet form in the Customers database

Figure 3-36: The Manage Portlets page under Portal Administration

Figure 3-37: Copying the RSS Portlet

Figure 3-38: Prompt for name of the copied portlet

Figure 3-39: Configuration screen for the Customer Contact RSS portlet

Figure 3-40: Edit Parameters section

Figure 3-41: Setting the title for selected locale

Figure 3-42: Configuration screen for Customers XML-XSLT portlet

Figure 3-43: XML portlet page

Figure 3-44: Result of clicking a highlighted link in the RSS portlet

Figure 3-45: Clicking on a highlighted link in the XML/XSL portlet

Figure 3-46: JavaScript Subform in the customer database

Figure 3-47: CustomerPortletIntegrated view in the Customers database

Figure 3-48: $$ViewTemplate for CustomerPortletIntegrated view

Figure 3-49: Initial blank form

Figure 3-50: Customer Contacts portlet integrated view

Figure 3-51: DisplayViewCategory form for the Customers database

Figure 3-52: DisplayViewCategory form for the Sales database

Figure 3-53: Web clipping through Portal Administration

Figure 3-54: "Clipping" from the URL

Figure 3-55: Web Page portlets need to be configured

Figure 3-56: The integrated portlets page

Figure 3-57: Clicking on After Portal link

Figure 3-58: Clicking Fire Portals Co in Customers portlet launches content in other portlets.

Figure 3-59: Result of clicking on link in the Customer Contact portlet

Figure 3-60: Result of clicking on the first highlighted document link in the Customer Sales Activity portlet

Figure 3-61: Three documents in "edit" mode on the same portlet page

Chapter 4: Using Custom Domino JSP Tag Libraries

Figure 4-1: IBM WebSphere commitments on Open Standards

Figure 4-2: J2EE design

Figure 4-3: Process of serving the first JSP request

Figure 4-4: Stateful interactions using Java components

Figure 4-5: WebSphere Studio internal structure

Figure 4-6: Snapshot of WebSphere Studio Application Developer

Figure 4-7: WebSphere Portal Toolkit for WebSphere Studio

Figure 4-8: Lotus Domino Toolkit for WebSphere Studio 1.0

Figure 4-9: Domino custom JSP tags portlets

Figure 4-10: Customer List portlet

Figure 4-11: Customer Detail portlet

Figure 4-12: Customer Contacts portlet

Figure 4-13: Customer Sales Activities portlet

Figure 4-14: Creating the Portal project

Figure 4-15: Parameters for creating the portlet project

Figure 4-16: Editing the CustomerList.class portlet

Figure 4-17: JSP directory structure

Figure 4-18: Including Domino custom JSP tags on the Web project

Figure 4-19: Inserting Domino custom tag libraries

Figure 4-20: Connecting to the Domino database

Figure 4-21: Connecting to Domino databases through Domino toolkit

Figure 4-22: Reviewing the Customer database

Figure 4-23: Adding the Customers/Customer By Name view to View.jsp

Figure 4-24: Changing the table to include headers

Figure 4-25: Initial portlet JSP

Figure 4-26: Installing the Customer List portlet

Figure 4-27: Successful installation of the portlet

Figure 4-28: Granting access to the Customer List portlet

Figure 4-29: Adding the Customer List portlet to the page

Figure 4-30: Initial portlet with Domino functionality accessed through JSP tags

Figure 4-31: Action interaction in the Customer Details portlet

Figure 4-32: Insert Tag Libraries to the new CustomerDetails.jsp file

Figure 4-33: Customer Detail initial portlet

Figure 4-34: Customer Contacts initial portlet

Figure 4-35: Customer Sales Activities initial portlet

Figure 4-36: Click to Action chained propagation

Figure 4-37: Click to Action sequence diagram

Figure 4-38: Importing the Click to Action tag library

Figure 4-39: Click to Action setting up the web.xml file

Figure 4-40: Click to Action enabled JSP tags portlets

Figure 4-41: Customer Information portlets with people awareness

Chapter 5: Portlet Development using Java: Technology Review

Figure 5-1: Portlet object inheritance structure

Figure 5-2: Portlet life cycle

Figure 5-3: Concrete portlet applications

Figure 5-4: Portlet API common objects

Figure 5-5: Portlet objects and their counterparts in the Servlet API

Figure 5-6: Overview of integration from portlet to Domino data

Figure 5-7: Mechanism of CORBA, stub of object versus real object

Figure 5-8: DIIOP settings in the server document

Figure 5-9: Setting up ACL for DIIOP in server document

Figure 5-10: DIIOP transaction information

Figure 5-11: Domino Object Model

Figure 5-12: Embedding Domino rich text inside of a Portlet

Figure 5-13: Potential firewall issues

Figure 5-14: Rich Text display with reverse proxy and URL re-writing

Figure 5-15: Structure of portlet after cs.ear file has been imported

Figure 5-16: Object pooling process

Figure 5-17: Pool Manager process flow

Figure 5-18: Log4j logging levels

Figure 5-19: Struts structure

Figure 5-20: WebSphere Studio Struts sample diagram

Chapter 6: Portlet Development using Java: Integration Examples

Figure 6-1: Hybrid JSP- Java Customer List portlet

Figure 6-2: Customer List portlet with search capabilities

Figure 6-3: Customer List portlet enabled with search and paging

Figure 6-4: First screen of the Portlet Application project wizard

Figure 6-5: Second screen of the Portlet application project wizard

Figure 6-6: Third screen of the Portlet application project wizard

Figure 6-7: Skeleton of the portlet

Figure 6-8: Added ncso.jar

Figure 6-9: Exporting portlet from Application Developer

Figure 6-10: HelloWorldFromDominoServer in action

Figure 6-11: HelloWorldFromDominoServer in action reusing a session

Figure 6-12: Creating a JavaBean

Figure 6-13: Creating a JSP file

Figure 6-14: ACLBrowser portlet creates list of databases in Domino and lists ACL entries.

Figure 6-15: Creating log4j.properties file

Figure 6-16: Structure of portlet in second logging sample

Figure 6-17: Creating DominoSessionPool project

Figure 6-18: Creating DominoSessionPool project- Adding Libraries

Figure 6-19: Creating the DominoSessionFactory

Figure 6-20: Creating the ClientPoolTester class

Figure 6-21: Results from the pooled approach

Figure 6-22: Results from the non-pooled approach

Figure 6-23: Performance comparison- Pooled and non-pooled

Chapter 7: Portlet Builders

Figure 7-1: Installing the BOBuilderPortlet.WAR for IBM Portlet Builder

Figure 7-2: Installing the DominoStruts.WAR for IBM Portlet Builder

Figure 7-3: Adding the Portlet Builder for Domino portlet to a page

Figure 7-4: Accessing the Portlet Builder for Domino portlet

Figure 7-5: Configuring the Portlet Builder for Domino- Enter portlet name and server name

Figure 7-6: Configuring the Portlet Builder for Domino- Enter username and password

Figure 7-7: Configuring the Portlet Builder for Domino- Select a database

Figure 7-8: Configuring the Portlet Builder for Domino- Select the forms and views

Figure 7-9: Configuring the Portlet Builder for Domino- Form and view options configuration page

Figure 7-10: Configuring the Portlet Builder for Domino- Configuring the Customers\By Name view

Figure 7-11: Configuring the Portlet Builder for Domino- Ordering the Customers\By Name columns

Figure 7-12: Configuring the Portlet Builder for Domino- Authentication and form display options

Figure 7-13: Configuring the Portlet Builder for Domino- Completed portlet configuration

Figure 7-14: Configuring the Portlet Builder for Domino- Adding the newly created portlet to a page

Figure 7-15: The Customers/By Name view as rendered by IBM Portlet Builder for Domino

Figure 7-16: Bowstreet Portlet Factory for WebSphere code execution architecture

Figure 7-17: Launching the Bowstreet Designer from WebSphere Studio

Figure 7-18: Creating a new Bowstreet model- Selecting model type

Figure 7-19: Creating a new Bowstreet model- Saving .model file

Figure 7-20: Adding a Bowstreet builder to a model file

Figure 7-21: Bowstreet Builder Palette window

Figure 7-22: Bowstreet Domino View & Form Builder- Configuration window part 1

Figure 7-23: Bowstreet Domino View & Form Builder- Configuration window part 2

Figure 7-24: Java code generated from the Bowstreet Domino View & Form builder

Figure 7-25: Test run of a model based on the Bowstreet Domino View & Form builder

Figure 7-26: Bowstreet WPS Portlet Adapter builder configuration window

Figure 7-27: Bowstreet Portlet Creator portlet

Figure 7-28: Bowstreet WPS Event Declaration builder configuration window

Figure 7-29: Bowstreet Event Handler builder configuration window

Figure 7-30: Bowstreet Action List builder configuration window

Figure 7-31: Bowstreet Link builder configuration window

Figure 7-32: Bowstreet Action List builder configuration window

Figure 7-33: Bowstreet implementation of Sales Tracking case study

Figure 7-34: Portlet Factory definition repository

Figure 7-35: CONET Portlet Factory architecture

Figure 7-36: CONET Portlet Factory component architecture

Figure 7-37: Portlet Factory deployment options

Figure 7-38: Portlet to Notes view comparison

Figure 7-39: Element containment hierarchy

Figure 7-40: The output result for the previous code example

Figure 7-41: Database definition

Figure 7-42: Selection definition

Figure 7-43: Layout definition

Figure 7-44: Query definition Basics tab

Figure 7-45: Query definition Layout tab

Figure 7-46: Portlet definition

Figure 7-47: Automatic portlet creation

Figure 7-48: The resulting Portlet

Figure 7-49: Sofor Interactive Portlet for Lotus Domino in our Scenario, retrieving data from the customer database

Figure 7-50: Example portal page created wth Aprtix Portlet Connector

Figure 7-51: Aptrix Portlet Connector configuration interface

---