Oracle WebCenter Content Service for Lotus Notes 10.3.0 - released November 2008
These release notes cover all releases of Oracle WebCenter Content Service
for Lotus Notes 10.3.
Release notes are occasionally updated after the release date. For the most
up-to-date release notes, go to the http://download.oracle.com/docs/cd/E13158_01/alui/integration/notescs/docs103/index.html.
Refer to the Interoperability page in the Product Center at one.bea.com/support
for the latest information on supported operating systems, application servers, and browsers.
At the time of release, Oracle WebCenter Content Service for Lotus Notes
10.3.0 supports the following:
- Operating Systems/Application Servers: Microsoft IIS 6.0 (in 5.0 compatibility
mode), .NET 1.1 SP1 supported on Windows 2003 Server SP1
- Lotus Notes Domino Servers and Clients: Domino 6.5, Domino 7.0, Lotus Notes
Client 6.5.1, Lotus Notes Client 7.0
- Browsers: Firefox 1.0, 1.5, 2.0; Internet Explorer 6.0, 7.0; Netscape 7.2, 8.0; Safari 1.3, 2.0
Refer to the Interoperability page in the Product Center at one.bea.com/support
for the latest information on supported Oracle products.
At the time of release, Oracle WebCenter Content Service for Lotus Notes
10.3.0 supports the following:
- Oracle WebCenter Interaction 10.3.0
The following product documentation is available on http://download.oracle.com/docs/cd/E13158_01/alui/integration/notescs/docs103/index.html.
Document |
Document Description |
Oracle WebCenter Content Service for Lotus Notes Installation and Upgrade Guide
| Describes how to install and upgrade the components of Oracle WebCenter Content Service for Lotus Notes. |
Deployment
- The HTTP Task must be enabled and running on the Lotus Domino Server for
browser click-through to function properly. (Issue #33962)
- Oracle WebCenter Content Service for Lotus Notes is not supported when a Lotus Domino
Server is running on the remote server. (Issue #34926)
- If you change the Notes ID file on the remote server you need to cycle IIS
on the remote server and update the new password in your content source(s). (Issue #35012)
- The ASPNET user is not created by the .NET framework runtime installation
process if the remote server is a domain controller. The Oracle WebCenter Content Service for Lotus Notes
is not supported when running on a domain controller. (Issue #35136)
- When you are using document click-through with a Lotus Notes client
version 5.x or earlier you must have the client open for click-through to work
properly. With Lotus Notes client 6.x and up the client will open
automatically. (Issue #37431)
- Error messages from the Domino Server will be displayed in the default language
of the Domino Server. For example, if you running an English portal against
a Japanese Domino Server, some error messages may appear in Japanese. (Issue
#37879)
- Running the Lotus Notes client on the remote server when trying to access
Oracle WebCenter Content Service for Lotus Notes will cause an error. If you need to run
the Lotus Notes client on the remote server, stop IIS first to ensure that
the Oracle WebCenter Content Service for Lotus Notes application is not running. (Issue #38012)
- McAfee 8.0i Lotus Notes E-mail Scan causes the web service to hang. If you
are running McAfee 8.0i on the remote server you must uninstall the
Lotus Notes E-mail Scan feature. (Issue #38361)
Web Service
- Lotus Notes content web services do not support mirroring the source
folder structure. (Issue #32629)
- On a 4.5WS Portal, the radio button on the properties page of the crawler
may not display the saved value correctly. (Issue #33274)
- Special characters such as "?" may produce unexpected results when used
in a text constraint string. Refer to Lotus Notes help ("Refining a search
query using operators" page) for other special characters. (Issue #33455)
- If you are using browser click-through with incorrect credentials, the first
click-through will request your login and password and may result in an error
when finding the document.
Workaround
Put the correct Notes credentials in the user preferences of the web service
or click-through a second time after logging in on the first click-through.
(Issue #38571)
- The Gateway URL prefix of the web service needs to match the Deployment_Location
setting in the web.config file. If these do not match, you may get a Request
Not Gatewayed exception when setting the user preferences for the web service.
(Issue #38660)