Domino Web Access (iNotes) V5.1

 

+
Search Tips   |   Advanced Search

 

 

Overview

Domino Web Access (iNotes) V5.1 allows the user to view and work in a Notes mail database that has a Domino Web Access design, optimized for access using a Web browser. The user can set up the portlet to display any or all of the following functional areas:

  • Welcome (default)
  • Mail
  • Contacts
  • Calendar
  • To Do
  • Notebook

Instances of this portlet appear in the Collaboration Center on the My Workplace --> Mail, My Workplace --> Mail --> Calendar, and My Workplace --> Mail --> Address Book pages. These three instances of the portlet are configured to display the Mail, Calendar, and Contacts functional areas of the portlet.

 

Using Domino Web Access

By default, the Domino Web Access portlet displays the Welcome area, which provides access to all other functional areas. As portal administrator, you can change the area that displays in the portlet (see information on the PortletType configuration parameter). You can also pre-configure all the other settings users can modify in edit mode, such as setting up a reverse proxy server, and specifying an instance number for the portlet when the current portal page contains more than one instance of Domino Web Access.

The Domino Web Access portlet works with Notes mail databases that have the Domino Web Access (iNotes) design.

 

 

Portlet security

Authentication for the Domino Web access portlet is determined by the value specified in the authMethod configuration parameter.

For the best results with user authentication for the Domino Web Access portlet, follow these recommendations:

  • Configure the Portal Server LDAP server and the Domino LDAP server that hosts Domino Web Access information to share the same LTPA token.

  • Make sure that all user identities (pairs of names and passwords) are the same on both LDAP servers.

    Having uniform user identities in directories for both LDAP servers will prevent successive authentication challenges when users open the portlet.

  • If portal users have the same user names but different passwords for WebSphere Portal authentication and Domino Web Access authentication, you'll need to specify the UsePW (use password) value in the authMethod configuration parameter.

    Note Single sign-on is supported, although this portlet can also be set up to request a name and password from users.

 

Test assumptions

The Domino Web Access portlet has been tested on and is compatible with all supported WebSphere Portal platforms, as listed in Supported hardware and software.

 

Set up Domino Web Access

For Domino Web Access, make sure your portal environment meets the following client and server requirements.

 

 

Client requirements

The Domino Web Access portlet supports browsers and devices capable of rendering HTML markup. The following table provides detailed information.

>>Minimum requirements for HTML
Markup level
HTML 4.0 Transitional
Java applet
1.1 applets
JavaScript
1.40
<iframe>
Yes
Style sheets
Inline CSS2
Software
This portlet has been tested on the following browsers:

  • Internet Explorer V6.0 with the following Java software:

    • Sun JVM 1.4.1
    • IBM JDK 1.4.1 or IBM JDK/JRE 1.4.1
    • Microsoft JVM 1.1.8
  • Mozilla 1.41 on Linux with the following Java software:

    • Sun JVM 1.4.1
Accessibility
No

 

 

Server requirements

The Domino Web Access portlet requires access to a Domino mail and appserver with HTTP support enabled. The Domino server hosts the Domino Web Access information source.

The portlet is compatible with the following versions of Domino:

  • 6.5.1, 6.5.2, and 6.5.3
  • 5.0.12

If you want users of the portlet to be able to select the source Notes database file name from a drop-down list, the Domino server must have DIIOP support enabled, and on the Server document Internet Protocols - HTTP tab, the option "Allow HTTP clients to browse databases" must be set to Yes.

If you do not choose to enable DIIOP support, users must edit the portlet properties and type a database filename to specify the information source.

 

 

Deployment/Installation

This portlet is installed automatically as part of WebSphere Portal installation.

This portlet is not supported as a remote WSRP service.

 

 

Configuration parameters

The following configuration parameters are available in this portlet.

Parameter Value
width
This parameter should not be changed.
The value specifies the width of the portlet when displayed in view mode.
100%
authMethod
Specifies what the portlet uses for authentication - the SSO token shared by WebSphere Portal LDAP and the Domino LDAP server for Domino Web Access sources, or the user password for Domino Web Access sources (when the portal authenticates users attempting to access a Domino Web Access information source).

Example: UsePW (default)

Specify this value if users have passwords for Domino Web Access sources that are different from the passwords they use to log in to the portal. The UsePW method enforces authentication of users with their Domino Web Access passwords whenever they attempt to open the portlet; it prevents repeated authentication prompts every time users open the portlet. However, when users try to open other portlets or go to other pages in the portal, they will be prompted to re-enter their portal user name and password; this portal authentication challenge occurs for other portlets and portal pages because the users' Domino Web Access LDAP passwords are in effect and take precedence over their WebSphere Portal LDAP passwords.

Example: SSO

Specify this value if you have configured WebSphere Portal LDAP and the Domino LDAP for Domino Web Access sources with a shared LTPA token, and portal users have the same credentials (user name and password pairs) in both LDAP directories. This is the recommended configuration for SSO-enabled LDAP and Domino Web Access portlet authentication within WebSphere Portal.

reverseProxyPortNumber
This parameter is required if the value for useReverseProxyString is Yes.
Specifies the server port for the (optional) reverse proxy server for the portlet. A reverse proxy server provides additional security for data sent to the Domino Web Access source.
Examples: 80, 3128
PortletType
Specifies the Domino Web Access area that displays when users view the portlet. Enter one of the following values:

  • All
  • Welcome
  • Mail
  • Contacts
  • Calendar
  • ToDoList
  • Notebook
useReverseProxyString
This parameter is optional.
Specifies whether to use a reverse proxy server for the portlet.
Example: Yes
reverseProxyProtocol
Specifies the network protocol to use for the reverse proxy server, if one is specified for the portlet under useReverseProxySting.
Examples: HTTP, HTTPS, or Auto
scrolling
This parameter should not be changed.
Activates automatic scrolling of portlet information when displayed in view mode.
Auto
InstanceNumber
Specifies a number for this instance of the portlet when the current page of WebSphere Portal contains multiple instances.
Example: 0 (default)
reverseProxyString
This parameter is required if the value for useReverseProxyString is Yes.
Specifies the URL of the reverse proxy server.
Example: proxy.acme.com
portNumber
Specifies the server port for the portlet when automaticMailFileLookup is set to No.
Examples: 80, 3128
pimApplication
Specifies the Domino Web Access area that displays by default when users first view the portlet and PortletType is set to All. Specify one of the following values:

  • Welcome
  • Mail
  • Contacts
  • Calendar
  • ToDoList
  • Notebook

height
This parameter should not be changed.
Specifies the height of the portlet when displayed in view mode.
300
protocol
Specifies the network protocol to use for the reverse proxy server, if one is specified for the portlet under useReverseProxySting.
Examples: HTTP, HTTPS, or Auto
automaticMailFileLookup
Specifies whether the portlet uses the user's identity to locate the Domino Web Access (mail) database, or allows the user to point to a source Domino Web Access. The default is Yes.
Example: Yes

 

 

Display the correct view

If you change the default Welcome view by making the following changes...

  1. Edit the "portletType" parameter in the Configure mode of the portlet by setting its value to "All".

  2. Edit the "pimApplication" parameter in the Configure mode to reflect one of the functional areas mentioned above.

The portlet still might not display any other view than the default view.

To fix, the portlet must be placed in "Edit" mode rather than "Configure" mode, and the drop-down list for "Functional Area" must be changed to reflect the value of the "pimApplication" parameter.

To correctly configure the DWA portlet to point to different functional areas than the default view, the Admin needs to perform the following steps:

  1. Edit the value of the parameter "portletType" and change the value to "All".

  2. Change the "pimApplication" parameter to the Functional Area that should be displayed (Welcome, Mail, Contacts, Calendar, ToDoList, Notebook).

  3. Place the portlet in Edit mode from the page that the portlet is displayed on, and change the functional area to match the value of the "pimApplication" parameter.

 

 

See also

Home |

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.