Domino Web Access

 

+
Search Tips   |   Advanced Search

 

Domino Web Access 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 (components):

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

An example of the Domino Web Access portlet appears among the Domino and Extended Products Portlets on the Domino Integration > My Work page of the portal.

There are other portlets that you may prefer to use to access mail and calendar data on a Lotus Domino server. Be sure to read the descriptions of both the Domino Web Access and Common Personal Information Management portlets (Common Mail and Common Calendar) before deciding which ones to deploy in the portal.

Domino Web Access is one of the mail portlets that is configured by default to detect a user's source mail file automatically.

If you are an administrator, you see the command Edit Shared Settings instead of Personalize for Domino Web Access portlet instances. This command works the same as Personalize except that the changes apply to all users of the instance of the portlet whose settings you are editing, up until the time a user decides to personalize the portlet. Use caution when editing shared settings. For more information, see Configuration levels for portlets.

 

What's new

Domino Web Access uses a redirect database to help automatically locate a user's source Notes mail database for the Mail, Calendar, and To Do functional areas of the portlet. A new parameter, DWARedirectDB, supports the use of this redirect database. As the administrator, specify the redirect database on the Lotus Domino messaging/application server.

The width, instanceNumber, and authMethod parameters are unnecessary and no longer used. We can control the portlet's width by modifying the layout of the page on which it appears. Authentication for the portlet is managed by single sign-on (SSO).

 

Use Domino Web Access

By default, the Domino Web Access portlet displays the Welcome component, which provides access to all other functional areas. As portal administrator, we can change the component that displays in the portlet (see information on the PortletType configuration parameter). We can also pre-configure all the other settings users can personalize, such as setting up a reverse proxy server. For more information, see the list of configuration parameters.

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

Users of the Domino Web Access portlet must select an option to enable people awareness (presence) within their Domino Web Access preferences. Instruct users to click the Preferences button within the portlet, click the Other tab, and select Enable Instant messaging.

 

Portlet security

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

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

  • Verify 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. For more information, see Supporting automatic mail detection with an LDAP directory other than Lotus Domino

 

Test assumptions

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

 

Set up the portlet

This portlet is installed automatically as part of the Domino and Extended Products Portlets.

Before we configure the portlet, make sure the WebSphere Portal environment meets the following client and server requirements.

 

Client requirements

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

Minimum requirements for HTML
Markup level HTML 4.01 Transitional
Java applet None
JavaScript 1.30
<iframe> Yes
Style sheets Portal styles only
Software

Accessibility Yes

Awareness in this portlet may be supported in a slightly different set of browsers and client platforms than listed in the table above, because the portlet depends upon the STLinks applet on the Lotus Sametime server. For more information, see People Finder portlet, people awareness, and Person menu problems in Troubleshooting Domino and Extended Products Portlets .

 

Server requirements

The Domino Web Access portlet requires access to a Lotus Domino mail and application server with HTTP support enabled. The Lotus Domino server hosts the Domino Web Access information source. A Lotus Sametime server supports awareness in the portlet.

The portlet is compatible with the specific releases of Domino and Lotus Sametime server software listed in the Supported software for collaboration (optional) table under Software requirements in Supported hardware and software.

The Domino Web Access group calendar feature is available in the portlet only if the Domino server is running release 7.0 or later.

If you want users of the portlet to be able to select the source Notes database file name from a drop-down list, the Lotus 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. For more information, see Allowing users to run Java agents.

If you do not choose to enable DIIOP support, users must personalize the portlet and type a database file name 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
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 component 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 Network protocol to use for the reverse proxy server, if one is specified for the portlet under useReverseProxyString.

Examples: HTTP, HTTPS, or Auto

scrolling This parameter should not be changed. Activates automatic scrolling of portlet information when displayed in view mode.

Auto

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 component 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 Network protocol to use for the reverse proxy server, if one is specified for the portlet under useReverseProxyString.

Examples: HTTP, HTTPS, or Auto

automaticMailFileLookup Specifies whether the portlet uses the user's login identity in the portal to automatically detect the user's Domino Web Access (mail) database. If this parameter is set to No, the portlet allows the user to point to a source Domino Web Access database manually.

The default is Yes.

Example: Yes

InotesUIArgument This parameter allows the administrator to specify a simplified appearance and behavior for the portlet so that it displays more on the portal page when either the All or Welcome component is selected.

Example: inotes_lite

Specify this value to improve performance.

With this parameter set to this value, users cannot collapse the portlet navigation panel.

Example: inotes

Specify this value to return to the default appearance and behavior.

PortalUIArgument This parameter allows the administrator to specify a simplified appearance and behavior for the portlet so that it displays more on the portal page when any one of the following components is selected: Mail, Calendar, Notebook, ToDo, or Contacts.

Example: portal_lite

Specify this value to improve performance.

With this parameter set to this value, users cannot collapse the portlet navigation panel.

Example: portal

Specify this value to return to the default appearance and behavior.

DWARedirectDB This parameter specifies the redirect database on the Lotus Domino messaging/application server that this instance of the portlet should use to locate users' mail files.

Example: dwaredir

There is no need to add the.nsf extension to the value of the parameter.

proxyOnWPSServer Specifies that the reverse proxy server configured for use with WebSphere Portal should be used for this portlet. The default value is the recommended value.

Default:

no

If this parameter is set to Yes, useReverseProxyString should also be set to Yes, and reverseProxyProtocol, reverseProxyPortNumber, and reverseProxyString should be empty.

serverAsJunction Uses the junction name of the Domino server that contains the source iNotes database as the junction name for the reverse proxy server. The default value is the recommended value.

Default:

yes

width This parameter is no longer used.
instanceNumber This parameter is no longer used.
authMethod This parameter is no longer used.

 

Parent topic:

Domino portlets reference

 

Related reference:


Troubleshooting Domino and Extended Products Portlets