Download Document

®
AD202 Lotus Domino, WebSphere
Portal, and Lotus Workplace
Integration - Part 2: Without
Programming
Peter Janzen – Lotus Product Manager
Objective
 Introduce non-programmatic tools for integrating
Notes/Domino applications into Workplace/Portal
 Understand requirements and skill set for these tools
 Position these tools in the portfolio of integration tools
 Demonstrate these tools in a WebSphere Portal application
3
AD201 – AD204: Lotus Domino, Websphere
Portal, and Lotus Workplace Integration
Session
AD201
AD202
AD203
AD204
4
Topics
Monday 3:15 – 4:30
Dolphin Southern I and II
Domino integration features
and an overview of AD20x series
Monday 5:00 – 6:15
Dolphin Southern I and II
Non-programming components:
Prebuilt portlets, DWAP, and Portlet
Builder for Domino
Tuesday 8:30 – 9:45
Dolphin Southern I and II
The Domino Toolkit:
Creating Domino JSPs using
the Domino JSP tag library
Tuesday 10:30 – 11:45
Dolphin Southern I and II
Portal Java programming concepts
and integrating Domino into your
Portal programs
Agenda
 Domino/Lotus Workplace Application Integration Strategy
 Pre-built Portlets
 Lotus Notes Portlets
 Other portlets
 New Domino Web Application Portlet
 Portlet Builder for Domino
 Summary and Q&A
5
Lotus Workplace Encompasses both Domino and
WebSphere
 Customer and partner investments in Domino applications
are preserved and extended in the Workplace.
 The Domino server plays a key, long term role in the IBM
Lotus Workplace strategy.
 Leverage existing Domino infrastructures and build and deploy new
apps for Portal
 IBM Lotus will provide tools to fully integrate Notes/Domino
applications into a Workplace environment.
 Portalize Domino applications using pre-built portlets, portlet
builders, and toolkits, for example.
 Customers make application choices based on their own
business needs and priorities.
6
Typical Skills/Tools Needed to Build
Portlets…
 A portlet consists of…
 HTML and related technologies – JavaScript, CSS, XML
 Java Server Pages (JSPs) – Start with <% and end with %>
 Java (many things can be done without it, though)
 Skills you will need
 HTML, JSP, CSS, XML and Java
 Portlet development environment
 Debug environment
 Tools you will need
Or use
pre-built portlets
or
portlet builders
 Software development toolkits
 WebSphere Studio is IDE of choice – highly recommended
 Portal server
7
Domino/Workplace Integration Tools
Strategy
Enable different types of users
Optimize tools for the platform
Workplace
Make them all work well together
Business Users/Admins
 Require easy to use, taskoriented tools
Developers
 Require powerful
extensions to the platform
8
Domino
Portal
Different Users Have Different Tools Requirements
Integrated Development Environment
Notes/Domino
Developer
Web Dev
High
Low
Technical
Skill
Administrator
Business
User
Browser
User Experience
9
Java
Developer
Domino/Workplace Integration Tools
Strategy
Enable different types of users
Optimize tools for the platform
Make them all work well together
Workplace
Business Users/Admins
 Notes clients
 Pre-built Portlets
 Portlet Builders
Developers
 Domino Designer
 Domino tools (LEI, Workflow…)
 Domino JSPs & Java API’s
 WebSphere Studio, Rational tools
10
Domino
Portal
Relative Positioning of Integration Tools
Higher
Domino
Designer
w/ JSP or WDO
& add-on
tools
Business User
User
WebSphere
Studio
WebSphere
w/ Java API
Studio
Portlet
Builder
Pre-built
Portlets
Lower
Power and Flexibility
11
Developer
Application Integration Strategy
 Integrating Domino applications into Lotus Workplace
involves portalizing the Domino application
 Portalizing Domino applications raises the following
questions
 What portlet development techniques are available?
 What is the effort required for portlet development?
 What functionalities can be implemented within a portal?
 How can scalability and performance be ensured?
12
Four Main Issues to Consider
Domino
Applications
Integration
Tools
The Challenge
What portlet patterns do we need
and what is the “best” implementation
method
Domino
Portlet Patterns
13
Considerations
Domino Application Characteristics
The following application characteristics need to be understood






14
Number of Documents
Total number of application users
Number of concurrent users
Application complexity
Single or multiple database application
Notes client based or web enabled application
Domino Portlet Pattern
 Domino portlet pattern defines the portal integration
depth and user interface requirements for the portlet
Used for deciding which integration tool to use
 Use cases influence which portlet patterns are useful
for the application
What is the use case from the user’s perspective?
Does the use case vary with the role of the user?
15
Portlet Patterns
16
Pattern
Description
Link
Provides a link that launches the native
application which can be the Notes client or
web browser
Display
Portlets that only display Domino content;
interaction requires the application be launched
in Notes or web browser
Integrated
Allows user to view content and interact with
application within the portlet
Migrated
Used to replace an application and transform
entire business processes into portlets
Integration Tools
 It is important that the person performing the
integration understand all the various tools at their
disposal
 Various groups of tools
Use pre-built portlets
Use Portlet “Builders”
Modify your Domino application
Use Domino JSP Tag Libraries
Use Lotus Collaborative Components
Use Domino Java classes
17
Choosing an Integration Tool
 Choosing an integration tool is a four step
process
1) Pre-project preparation and training
2) Identify project requirements and considerations
3) Select the appropriate portlet pattern
4) Select the appropriate integration tool
18
Select the Appropriate Portlet Pattern
19
Pattern
Advantages
Disadvantages
Link
Easy
Access existing
applications
No modifications needed
No content or
functionality available
within the portal
framework
Display
Minimal enhancements to
existing application
functionality
Can launch Notes or web
browser
Minimal or no
application functionality
within portal framework
Integrated
Significant functionality
within portlet
Requires more
development time and
skills
Migrated
Full application
functionality within portlet
Requires greatest
development time and
skill
Choosing the Integration Tool
 Identify one or more integration tool that will
support the portlet pattern
 Once a set of integration tools have been selected,
compare each one to the project requirements
 Choose the tool which yields the highest time to
value
20
Agenda
 Domino/Lotus Workplace Application Integration Strategy
 Pre-built Portlets
 Lotus Notes Portlets
 Other portlets
 New Domino Web Application Portlet
 Portlet Builder for Domino
 Summary and Q&A
21
Domino Application Integration Options
End User
Domino
Skills
Java
Skills
 Out of box Notes/Domino Portlets
 Portlet Builder for Domino
Low
 XML access to Domino View data
Development
Effort




Lotus Collaborative Components
Domino JSP Tags
Domino Java API’s
Partner Products
 Bowstreet Portlet Factory
22
High
Notes View Portlet






23
Display user’s Mail, Calendar, To Do…
Display any view in any database
Wizard-like Edit mode helps users define the portlet
Can launch Notes client instead of browser
Built-in People Awareness
Sorting
Notes View Portlet Requirements
 Domino Server
 HTTP & DIIOP
 Portal Server <= 4.2
 Individual Lotus Notes and iNotes portlets
 Portal Server >= 5 & Lotus Workplace
 Portlets consolidated into this single portlet for 5.0
 PortletType parameter determines the type of Notes database
source
 Lotus Notes View portlet
• Values: NotesView, NotesMail, MyInbox, MyCalendar, MyToDo,
NotesDiscussion, NotesTeamroom
 Domino Web Access (iNotes) portlet
• Values: All, Welcome, Mail, Contacts, Calendar, ToDoList,
Notebook
 Requires Lotus Collaborative Components
24
Notes View Portlet
Domino Server
Domino Database
Domino View
Restrict to a category
25
Notes View Portlet
Document
controls
26
View format controls
Web Page Portlet
 Out of the box portlet
 Allows you to leverage Existing Domino WebEnabled Applications
 Uses an iframe to display an existing application
 Plus: no change to the app needed
 Minus:
 light integration
 browser specific
 potential firewall issues
27
Limitations of Current Pre-built Portlets
 Currently available pre-built portlets have issues when working
with documents
 Basic form display
 Browser
 iFrame
 Notes Client is good but its not Portal
 Browser and iFrame do not adhere to Portal rules
 Go directly at the Domino server
 Potential firewall issue
 Bypasses Portal security
 Domino serves up links which point to itself
 Need a portlet that will transform links to Portal links
28
Domino Web Application Portlet
 Designed to allow Domino web apps to be surfaced in a
LWP/Portal environment.
 User experience remains within Portal
 No changes to the Domino application required
 Reverse Proxy – portlet uses a set of rules to map Domino
generated URLs to Workplace/Portal such that all requests
are channeled through Portal server.
 Default set of Domino Rules defined and configured (mail,
discussion, teamroom)
 Rules can be added for support of any Domino web application
29
Architecture
3. The ‘real’ address is
determined and a request is
made to the Domino Server
2. The browser
requests the contents
of the IFRAME
5. The
transforme
d HTML is
returned to
the
browser
DWAP
Servlet
DWAP
Portlet
Domino
Server
4. The retrieved HTML is ‘transformed’
by DWAP to redirect any references to
the Domino server (and other
modifications)
1. The portal just sends down an
IFRAME, with a URL that refers to the
DWAP servlet.
IFRAMES are downloaded as a simple reference, and the
browser then sends another request to get the contents
Browser
30
This also applies to graphics and other embedded
elements
Domino Web Application Portlet
 Single Sign On – supports SSO between
Workplace/Portal and Domino
 SSL – support secure transfer of data between
Workplace/Portal and Domino
 Delivered as iframe first, web clipper in later releases.
 Part of Domino 6.5.1 project, Q1 2004
Download from the Portal catalog
Domino Web Application Portlet
31
Domino Web Application Portlet Requirements
 Domino Server R5 & 6
 Any Server OS supported
 HTTP
 Portal Server 4.1, 4.2 & 5
 Platforms: Win32, AIX, Solaris, Linux
32
Domino Web Application Portlet
Intuitive Configuration
Mode
33
Domino Web Application Portlet –
Discussion
34
Agenda
 Domino/Lotus Workplace Application Integration Strategy
 Pre-built Portlets
 Lotus Notes Portlets
 Other portlets
 New Domino Web Application Portlet
 Portlet Builder for Domino
 Summary and Q&A
35
Portlet Builders
 Available from IBM
 WebSphere Portal Application Integrator (WPAI)

Portlet Builder for Domino
 Available from IBM partners
 Bowstreet, Aptrix, Conet, Sofor
36
WebSphere Portal Application Integrator
(WPAI)
 Made for Business Users - Point-and-Click through the
Portal UI
 Framework for application integration into WebSphere
Portal
 Generic architecture to easily build portlets to access a
variety of Enterprise Applications, for …
 Systems like SAP, PeopleSoft, and Siebel
 RDBMS like DB2, Oracle, SQL Server, or any JDBC database
 …and Domino !!!
 Users of tools need only a basic application knowledge
37
WPAI Architecture
Builder
itself runs
as a
portlet
Power
Users
Portlet Builder
Builder
generates
configuration
data for a
portlet instance
Portlet Config
UI Template
represents
desired user
interaction with
Business Object
UI Template
End
Users
Portlet Instance
Business Object
Adapter
Instance configuration
binds customized UI
Template with a specific
customized Business
Object type obtained
from an Adapter
38
Adapter provides
access to
Business Object
instances
Back-end
Application
Portlet Builder for Domino
 A portlet to build Domino
portlets
Simple Web interface to
create portlets that access /
manipulate data in Domino
No programming required
 Primary roles associated
Builders – those who use the
Domino Builder to create
portlets
Users – those who access
the portlets created with the
Domino Builder
39
 Portlet Builder for
Domino modes
Builder – Build portlets
Run-Time – Access Portlets
•Builder output is a portlet
 Domino document
viewing options
As-is
Generic form
Pre-Use Configuration & Considerations
 Authentication model between Portal and Domino
 Credential Vault
 Predetermined Username and Password
 Single Sign On
 Domino R5 & 6 servers
 Any server OS supported
 Need to know…
 Builder - Domino Username and Password
 Domino server name(s)
 Domino database name(s)
 Domino view / form name(s)
 Portal Security Model
 Only users assigned permissions can use Domino Builder
 Only users assigned permissions can use portlets created
40
Pre-Use Configuration & Considerations
 Java APIs used to communicate with Domino
 Requires HTTP & DIIOP on Domino
 Domino security model 100% respected
 Domino ACL Considerations
• Explicit / Implicit user access
• Maximum Internet Username and Password is Reader or higher
 Click-to-action required to leverage Extra Features
 SameTime required for built in Presence Awareness
41
Steps to Build a Portlet
1.
2.
3.
4.
5.
42
Select the Domino server and database
Select view(s) and form(s) to include in the portlet
Configure view(s) and form(s)
Configure extra settings
Select Authentication and Form display options
Step 1 - Select the Domino Server and
Database
Enter a new portlet name
Connect to Domino server
Select the Domino database
and retrieve forms / views list
43
Step 2 - Select View(s) and Form(s)
 Select from list of forms/views
 Adding elements to the portlet
 Portlets can contain multiple
forms/views
Sort by Design Element
Sort By Element Type
Select multiple elements
Page Through Elements
44
Step 3 - Configure View(s) and Form(s)
Select markup
Configure
Authentication and Form Display Options
45
Step 3 - Configure View(s) and Form(s)
Configure View Column Display Options
Selected Display info Search info C2A Extra
Control View Column Order
Move Down
Move Up
46
Step 4 - Configure Extra Settings
Form options
Field types
Display options
View Column options
Presence Awareness
View Column Formulas
Links
Images
47
Step 5 - Select Authentication and Form Display
Options
 User Authentication Options
 Single Sign On
 Explicit
 Implicit
 Credential Vault
Form display options
Use Data Form
Use Inline Frame
48
Completed Portlet from Portlet Builder
View
Switcher
Create
New Doc
Search
Read Doc
View
49
Tools Comparison
Tool
Protocol
Skill Set
Performance
(minimum)
Notes View Portlet HTTP, DIIOP
PA
OK – no session
management
PA; Domino
App/Dev, XML,
JavaScript
OK – no session
PA; Domino
App/Dev
OK – no session
HTTP
PA
Good – caching,
fast html parser
DIIOP
(for remote)
PA, Domino
App/Dev, JSP
Better – limited
HTTP, DIIOP
(for remote)
PA, Domino
App/Dev, JSP,
Java
Best – Session
Helper Portlets
(XML, RSS)
HTTP
Portlet Builder for
Domino
HTTP, DIIOP
Domino Web
Access Portlet
Domino JSP Tags
LCC API &
Domino Objects
for Java
PA = Portal Admin (all tools require this skill set)
50
management
management
session management
management, object
pooling
Summary
 It’s easy to integrate Domino collaborative
applications from Lotus Workplace & WebSphere
Portal
 IBM provides tools that cover the spectrum from
business users to developers
 Start with out of the box portlets or Domino Portlet Builder to
surface data in your portlet
 Use Domino Web Application portlet for an integrated solution
 Leverage your investment in Domino - start
integrating today!
51
Resources
 Go to the Application Development lab (tutorials & info)!!
 Lotus Education has courses addressing Workplace, Portal, and
J2EE
 Tutorials (http://www.ibm.com/developerworks/training/)
 Build custom portlets for Domino: Portlet Builder for Domino simplifies
development
 Building Lotus Domino Portlets: Bowstreet Portlet Factory for WebSphere
streamlines the process
 Simplified JSP page development for Lotus Domino
 Article: Introduction to Lotus Domino Toolkit for WebSphere Studio

52
http://www7b.software.ibm.com/wsdd/library/techarticles/0304_schum
acher/schumacher.html
Questions?
 Resources Cont’d
 Redbooks
 Portalizing Domino Applications for WebSphere Portal (sg247004)
 WebSphere Portal 4.12 Collaboration Services (redpaper)
 Developer Sites
 Portal Zone: www.software.ibm.com/wssd/zones/portal
 Lotus Developer Domain: www-10.lotus.com/ldd
53