<<

. 39
( 87 .)



>>

tion sharing. It is seamlessly integrated into the WebSphere Portal Server.
Lotus QuickPlace facilitates shared virtual workspaces for sharing and orga-
nizing data, be it ideas, documents, or schedules. Lotus Collaborative Com-
ponents provide a Java API to allow developers to implement customized
portlets making use of features of Lotus Domino, Lotus QuickPlace, and
Lotus Sametime.
The minimal con¬guration for the collaborative features is shown in
Figure 12-1. It is advisable to place the Lotus Domino server and the Same-
time and QuickPlace product on a separate machine, to avoid con¬‚icts be-
tween the Lotus Domino server and the IBM HTTP server used with WAS.
In a production environment with large quantities of users, it would
be more practical to place each product on a separate server (that is, use
three different machines for the Lotus Domino, Sametime, and QuickPlace
products).


Lotus Notes Integration
With Lotus Notes integration, WebSphere Portal Server provides access to
mail, appointments, contacts, and tasks in Lotus. Since these are functions
used extensively by nearly every user, placing them inside the portal in-
creases the use and acceptance of the portal.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




Adding Collaboration and Search Components to Your Portals 225


WebSphere Portal Server provides two different ways for Lotus Notes
integration. On one hand you have the Domino Web Access (iNotes) portlet,
and on the other hand the Notes and Domino portlet.
The former portlet uses Domino™s own iNotes Web access, and conse-
quently it has two distinct disadvantages: It requires browser support from
iFrames, and it does not apply the portal™s theme to the generated pages.
The Lotus and Domino portlet replaces ¬ve different portlets in earlier
versions of the WebSphere Portal Server (for example, version 4.2). This
single portlet can be con¬gured to provide access to the following types of
Notes databases:

NotesMail”To access a Note Mail database
NotesView”To access any view of any Notes database
MyNotesMail”Access to a speci¬c Notes Inbox, based on the login
identity
MyNotesCalendar”Access to a speci¬c Notes Calendar, based on
the login identity
MyNotesToDo”Access to a speci¬c task list, based on the login
identity
NotesTeamRoom”Access views of a Notes TeamRoom
NotesDiscussion”Access to Notes Discussions

The Lotus and Domino portlet supports single sign-on (SSO) to the
Domino server and the Notes database, with an LTPA token. This portlet
has the following con¬guration parameters (accessible through the Manage
Portlet entry in portlet administration), as shown in Figure 12-2.

NotesServer”Host name of the Domino server where the Notes
database resides
NotesDatabase”Filename of the Notes database used as an
information source for the portlet
VAULT_SLOT”Name of the slot in the WebSphere Portal Credential
Vault used for this portlet
NotesView”Name of view to use, default is ($All)
PortletType”One of the values NotesView, NotesMail, MyInbox,
MyCalendar, MyTodo, NotesDiscussion, NotesTeamRoom.

Note that the default portlet type is NotesView, which is the most general
one. While being the most ¬‚exible and powerful type, it also requires the
most tweaking by users.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




226 Chapter 12




Figure 12-2 Con¬guration parameters for NotesView portlet.


Microsoft Exchange Integration
Understandably, WebSphere Portal Server has tight integration with Lotus
products. Even so, it provides means for integration with Microsoft Excha-
nge. Five different portlets are provided for Microsoft Exchange Integration:
Microsoft Exchange Tasks
Microsoft Exchange Notes
Microsoft Exchange Contacts
Microsoft Exchange Calendar
Microsoft Exchange Mail
Each of these portlets provides a respective view into the Microsoft Ex-
change server.
Before using any of these portlets, users need to customize the portlet,
by choosing a credential slot in which their user ID and password shall
be stored, and by entering the details of the exchange server as shown in
Figure 12-3.

Lotus Sametime Integration
Lotus Sametime allows teams to collaborate through instant messaging
and online meetings. WebSphere Portal Server provides a Sametime portlet
which allows users to launch the Sametime connect applet.
The Sametime portlet is shown in Figure 12-4. There are not a lot of
con¬gurable parameters for this portlet, just the host and port number. Once
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




Adding Collaboration and Search Components to Your Portals 227




Figure 12-3 Editing Microsoft Exchange Tasks portlet.


you launch the Sametime connect applet, you need to log in to Sametime
(as shown in Figure 12-5).
An important advantage of using Sametime through the portal is single
sign-on. In other words, users need not log in to Sametime; instead their
session with the portal is extended to Sametime, using the same username.
In order for SSO to take place, you need to con¬gure Sametime, by importing
an LTPA token exported by the WebSphere Application Server.
Once logged into Sametime, users can send instant messages and start
electronic meetings. The Sametime user interface is straightforward, and
resembles most other instant messaging products. Each Sametime user has
a contact list. The contact list typically contains individuals with whom the




Figure 12-4 Lotus Sametime portlet.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




228 Chapter 12




Figure 12-5 Lotus Sametime Connect, launched from portlet.


user intends to interact with frequently. Users are able to set their online sta-
tus, to indicate whether they are available. Through the Meeting menu it is
possible to initiate a variety of communication modes: text-based chat, au-
dio, video, whiteboard, or application sharing. Once a meeting is initiated,
other people (either from the contact list or outside of it) may be invited to
join in.


Lotus QuickPlace Integration
Lotus QuickPlace (now known as IBM Lotus Team Workplace) allows teams
to establish a team workplace to facilitate collaboration. Workplaces can
store documents, discussions, plans, tasks, and resources.
QuickPlace provides tools for asynchronous collaboration, in contrast to
the online and synchronous collaboration tools of Sametime.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




Adding Collaboration and Search Components to Your Portals 229




Figure 12-6 Lotus QuickPlace portlet.


WebSphere Portal Server is shipped with two QuickPlace portlets. The
QuickPlace portlet shown in Figure 12-6 is used to direct users to one or
more QuickPlace places. Users may customize the portlet in the edit mode
by specifying up to six different places. For each place the name and URI
need to be speci¬ed. The inline QuickPlace portlet is associated with a
speci¬c place, which launches immediately within the same page.
When new places are created, users sharing the place are speci¬ed along
with their respective access rights.

Microsoft NetMeeting Integration
WebSphere Portal Server includes a portlet for launching a Microsoft Net-
Meeting client. The client is invoked through the NetMeeting Active-X com-
ponent, which can be embedded into a portal page.
The NetMeeting portlet is not installed by default in the portal, and it is
located in the netmeeting.war ¬le. This portlet does not have any con¬g-
uration parameters, as the user pro¬le is entered through the NetMeeting
interface.

People Finder
A prerequisite for any sort of collaboration is ¬nding the people with whom
you want to collaborate with. While that is a nonissue in a small to medium-
sized organization, it is much more dif¬cult within a larger organization.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




230 Chapter 12


WebSphere Portal Server is shipped with the People Finder portlet. It is
not installed by default, but is available in the PeopleFinder.war Web
module.
In order for the People Finder portlet to work, you need to have the Direc-
tory Connector Web application (LDAPConnector.ear) to be installed. This
is automatically done by the Collaboration Center installation program. The
Directory Connectors bridges between the portal server and your LDAP di-
rectory. The Directory Connector uses the data store of the underlying WAS
(be it the default CloudScape, DB2, or Oracle) to store data.
The Directory Connector uses an XML con¬guration ¬le to de¬ne the
LDAP server to which the People Finder portlet connects to. The Collabo-
ration Center installs a sample ¬le PFSampleConnection.xml under the
directory CollabCenter under the portal installation root. You may direct
the Directory Connector to use another XML ¬le by opening it at

http:// yourHostName/PFDirectoryConnector0


Here you can load new XML ¬les, validate them (that is, make sure that
they are well formed), and activate them. The XML ¬le de¬nes the connec-
tion settings, as well as con¬guration data relating to the data stored in the
LDAP server.
The connection settings include the following elements, which must be
set correctly for the People Finder portlet to work:

hostURI”Fully quali¬ed LDAP URI (that is,
ldap:://ldapServer:ldapPort).
baseDN”The starting point for any searches (that is, the topmost
node from which a search will start).
bindDN”Name of user used to access the LDAP server. If empty,
anonymous bind is made.
privateCredentials”Password, if applicable
securityProtocol”none if anonymous binding, or simple if using a
password.

The XML ¬le indicates what LDAP attributes are exposed to the People
Finder portlet. For each exposed attribute a meaningful name can be given.
For example, the ¬rst attribute in the sample ¬le is

<exposedAttribute label="DisplayName">
<description/>
<mappedAttrbiute>displayName</mappedAttribute>
<type>String</type>
</exposedAttribute>
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-12 WY009-BenNatan-v1.cls May 11, 2004 14:49




Adding Collaboration and Search Components to Your Portals 231




Figure 12-7 People Finder portlet.



The label controls the naming of the attribute in the People Finder portlet,
and the mappedAttribute indicates the respective LDAP attribute.

<<

. 39
( 87 .)



>>