Portalizing Domino applications : integration with Portal 5.02 and Lotus Workplace 2.0.1 / IBM International Technical Support Organization.

Format:

Book

Author/Creator:

International Business Machines Corporation, International Technical Support Organization Staff, Corporate Author.

Contributor:

International Business Machines Corporation. International Technical Support Organization.

Series:

IBM redbooks.

IBM redbooks

Language:

English

Subjects (All):

Web portals.

Lotus Domino.

Lotus Workplace.

Physical Description:

xviii, 764 p. : ill.

Edition:

1st ed.

Place of Publication:

Poughkeepsie, NY : IBM, c2005.

Language Note:

English

Contents:

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Additional contributors

Become a published author

Comments welcome

Chapter 1. Introduction to portalizing Domino applications

1.1 Overview

1.1.1 Portal and Domino within the context of the IBM Workplace

1.1.2 Structure of this chapter

1.2 The vision supporting IBM Workplace

1.3 Introduction to IBM Workplace

1.3.1 The business value of IBM Workplace

1.3.2 The product families that make up IBM Workplace

1.3.3 The roadmap of Lotus Notes/Domino, WebSphere Portal, and IBM Workplace

1.4 Benefits of Domino and Portal together

1.5 Portal architecture

1.5.1 Introduction to portlets

1.5.2 Presentation services

1.5.3 Layout of the portal page

1.5.4 Customization

1.6 Integrating Domino applications

1.6.1 The portalizing process

1.6.2 The portalizing challenge

1.6.3 Domino applications

1.7 Portlet patterns

1.7.1 Link pattern

1.7.2 Display pattern

1.7.3 Integrated pattern

1.7.4 Migrated pattern

1.7.5 Designing the integration portlet

1.8 The integration architecture

1.8.1 The Portal/Domino server infrastructure

1.9 Authentication

1.9.1 Multi-server session-based authentication

1.9.2 Using Domino LDAP with WebSphere Portal

1.10 Development options

1.10.1 Target audience

1.10.2 Development environments

1.10.3 Development tools

1.10.4 When to use a specific integration approach

1.11 Summary

Chapter 2. Integration techniques

2.1 Choosing an integration technique

2.1.1 Project considerations

2.1.2 Step 1: Pre-project preparation and training

2.1.3 Step 2: Identification of project requirements

2.1.4 Step 3: Selection of an appropriate portlet pattern

2.1.5 Step 4: Selection of an appropriate integration technique.

2.2 Integration techniques and development options

2.2.1 Using existing portlets

2.2.2 Domino JSP tag libraries

2.2.3 Developing Domino portlets using Java

2.2.4 Portlet builders

2.2.5 Integration with Lotus Workplace

2.3 Case study: A simple sales tracking application

2.3.1 Case study overview

2.3.2 Case study objective: Sales Workplace

2.3.3 Case study: Application details

2.4 Deploying the case study portlets

2.4.1 Install portlets

2.4.2 Creating a label

2.4.3 Creating a page

2.4.4 Adding portlets to a page

Chapter 3. Using existing portlets

3.1 Overview

3.1.1 Skills and degree of customization - Pre-packaged portlets

3.1.2 Technologies involved

3.1.3 Software and tools used

3.2 Integration techniques and overview of portlets

3.3 Integration Option 1 - Using the Domino V6.5.1 and Extended Products Portlets: Collaboration the easy way

3.3.1 Portlets that make up Extended Products Portlets

3.3.2 Considerations for the Domino Extended Products Portlets

3.3.3 Implementation details for Extended Products Portlets

3.3.4 Configuring the Document Manager portlet

3.3.5 Configuring the Domino Application portlet

3.3.6 Configuring the Domino Databases (Notes View) portlet

3.4 Integration Option 2 - The Domino Application Portlet

3.4.1 Considerations

3.4.2 Implementation details for the Domino Application Portlet

3.5 Integration Option 3 - using specific Portlets

3.5.1 Integrate using Lotus Notes View Portlet

3.5.2 Integrate using the Domino Web Access (iNotes) portlet

3.5.3 Lotus Web Conferencing (Sametime)

3.5.4 Lotus Instant Messaging Contact List (Sametime Contact List)

3.5.5 My Lotus Team Workplaces (QuickPlace)

3.5.6 People Finder Portlet

3.5.7 Domino.Doc (Document Manager) Portlet

3.6 Reference material.

Chapter 4. Using custom Domino JSP Tag libraries

4.1 Overview

4.1.1 Skills and degree of customization - Domino JSP Tags

4.2 Technologies involved

4.2.1 J2EE overview

4.2.2 JavaServer Pages

4.3 Software and tools used

4.3.1 WebSphere Studio Application Developer V5.1.2

4.3.2 WebSphere Portal Toolkit for WebSphere Studio V5.0.2.2

4.3.3 Lotus Domino Toolkit for WebSphere Studio V1.3

4.4 Integration techniques

4.5 Integration using Domino custom JSP Tag libraries

4.5.1 Overview

4.5.2 Domino custom JSP tag libraries

4.5.3 The Lotus Domino Object architecture

4.5.4 Types of Domino JSP tags

4.5.5 Limitations and considerations

4.5.6 Session management

4.5.7 Object Pooling

4.5.8 Implementation example

4.5.9 Conclusions to the custom Domino tags integration technique

4.6 Integration via Click-to-Action

4.6.1 Click-to-Action

4.6.2 Considerations

4.6.3 Implementation of the technique

4.7 Integration via people awareness

4.7.1 People awareness

4.7.2 Implementation of the technique

4.8 Reference Material

Chapter 5. Portlet development using Java: Technology review

5.1 Overview

5.1.1 Skills and degree of customization with API integration approach

5.2 Domino Java API

5.2.1 Overview

5.2.2 Domino Java classes

5.3 IBM Portlet API

5.3.1 Overview

5.3.2 Elements of the IBM Portlet API

5.4 JSR 168 Java Portlet Specification

5.4.1 Relationship to servlet API

5.4.2 Comparing common portlet API concepts

5.4.3 Comparing portlet packaging and descriptors

5.5 Struts framework

5.5.1 Basic elements of Struts

5.5.2 Struts support in WebSphere Portal

5.6 JSF framework

5.6.1 JSF application concept

5.6.2 JSF support in WPS

5.7 Other technologies

5.7.1 JSTL

5.7.2 Object pooling

5.7.3 Logging

5.7.4 Domino XML.

5.7.5 Collaborative Services API

5.7.6 Web services

5.7.7 WSRP

5.8 Portal application design guidelines

5.8.1 Introduction to object-oriented design patterns

5.8.2 Design principles

5.9 Additional information

Chapter 6. Portlet development using Java: Integration examples

6.1 WebSphere Studio Application Developer

6.2 Portalization project

6.2.1 Sales Tracking Domino application

6.2.2 Portal application functionality

6.3 Accessing Domino data

6.3.1 DominoAccess project

6.3.2 DominoSessionFactory

6.3.3 CustomerBean

6.3.4 CustomerContactBean

6.3.5 SalesPersonBean

6.3.6 BeanUtils

6.3.7 DominoAccess

6.3.8 Exporting DominoAccess

6.4 Sales Tracking application using IBM Portlet API

6.4.1 SalesTrackingIBMAPI project

6.4.2 CredentialVaultManager

6.4.3 CustomersPortlet

6.4.4 CustomersPortlet JSP files

6.4.5 Testing the application

6.4.6 CustomerDetailsPortlet

6.4.7 CustomerDetailsPortlet JSP files

6.4.8 Testing the application, part two

6.4.9 CustomerContactsPortlet

6.4.10 CustomerContactsPortletView.jsp

6.4.11 Testing the application, part three

6.4.12 Enabling Click-to-Action

6.4.13 Testing the application, part four

6.4.14 Deployment descriptors

6.4.15 Deployment

6.4.16 Summary

6.5 Sales Tracking application using Struts

6.5.1 Adding classes to DominoAccess

6.5.2 SalesTrackingStruts project

6.5.3 Drawing a Struts application

6.5.4 Realizing JSPs and JavaBeans

6.5.5 Realizing actions

6.5.6 Adding global forwards

6.5.7 Testing the application

6.5.8 Deployment descriptors

6.5.9 Deployment

6.5.10 Summary

6.6 Sales Tracking application using JSF

6.6.1 SalesTrackingJSF project

6.6.2 index.jsp

6.6.3 SalesTrackingJSFView.jsp

6.6.4 CustomerDetails.jsp

6.6.5 Deployment descriptors

6.6.6 Deployment.

6.6.7 Summary

6.7 Sales Tracking application using JSR 168

6.7.1 Adding functionality to DominoAccess

6.7.2 SalesTrackingJSR168 project

6.7.3 SalesTrackingJSR168Portlet

6.7.4 JSP files

6.7.5 Test the application

6.7.6 Deployment descriptors

6.7.7 Deployment

6.7.8 Summary

6.8 Summary

Chapter 7. Portlet builders

7.1 IBM Portlet Builder for Domino

7.1.1 Implementation details

7.1.2 Implementation example

7.1.3 Adding People Awareness

7.1.4 Enhancing further with Click-to-Action

7.2 Bowstreet Portlet Factory for WebSphere

7.2.1 Implementation details

7.2.2 Implementation example

7.2.3 Installing the sample application

7.3 CONET Knowledge Director 3.0 for WebSphere Portal

7.3.1 Knowledge Director components

7.3.2 Implementation issues

7.3.3 Portlet creation methodology

7.4 Implementing the Sales Workplace example

7.4.1 Write Access

7.4.2 Summary

Chapter 8. Integration with Lotus Workplace

8.1 Introduction

8.1.1 Skills and degree of customization - Workplace Builder

8.2 Adding Workplace portlets to Domino portlets

8.3 Adding Domino Portlets to Workplace Applications

8.3.1 Applications and templates

8.3.2 Workplace Builder

8.3.3 Using the Workplace Builder

8.4 Working with the Workplace API

8.4.1 Using the JSP Tag Library to enhance a Domino Portlet

8.5 Workplace API and SRI

8.5.1 Collaborative Application Component Interface

8.5.2 Workplace Mail Messaging SPI

8.5.3 Workplace Instant Messaging SPI

8.5.4 Conclusion

Appendix A. General portlet development guidelines

Portlet coding guidelines

Refrain from using instance variables

Pass data to the view (JSP) as a bean in the request object

Use the portlet logging facility

Adopt good code documentation habits.

Use the ContentAccessService to fetch external content if necessary.

Notes:

"April 2005."

Includes bibliographical references and index.

OCLC:

61447351