Oracle WebCenter Content Service for Windows Files 10.3.0 - released November 2008

These release notes cover all releases of Oracle WebCenter Content Service for Windows Files 10.3.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to http://download.oracle.com/docs/cd/E13158_01/alui/integration/windowsfilescs/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 Windows Files 10.3.0 supports the following:

• Operating Systems/Application Servers: Microsoft IIS 6.0, .NET 1.1 SP1 supported on Windows 2003 Server SP1
• 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 Windows Files 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/windowsfilescs/docs103/index.html.

• If you edit the data source credentials after the upgrade, you must update the credentials in any existing content sources. (Issue #36853)
• ASP.NET user has to have domain administrative rights on remote server where Oracle WebCenter Content Service for Windows Files runs. (Issue #47072)
  
• On certain Windows shares, a crawl job may fail to crawl in many of the documents and the job log will indicate that these files could not be found. (Issue #29052)
  
  Workaround: Giving the data source user administrative rights on the machine where the share is located will resolve this problem.
• It is possible for crawl jobs that handle a very large number of documents to fail as a result of a session having timed out. (Issue #28548)
  
  Cause: When a crawl job is run, there are two sessions that are created, one for crawling folders and one for crawling documents. When one of those sessions has been inactive for a long time, it will time-out; and when the portal attempts to hit this session that has timed out, the job will fail. The default IIS session timeout is eighty minutes. This scenario may occur when crawling a folder with a very large number of documents. The folder session times out after eighty minutes as the document connection is crawling in all the documents for that folder. Workaround: Increasing the IIS Session Timeout resolves this issue. To increase the timeout value, edit the web.config file in the Oracle WebCenter Content Service for Windows Files installation directory and change the sessionstate timeout attribute. You will also have to change the timeout value on the IIS virtual directory for the ntcws. To avoid having a large timeout setting, modify your directory structure such that there are no folders that have a large number of documents in them.
• In Plumtree Portal 5.0.x, in the Data Source wizard, under Main Settings, if the option: "Uses the Gateway to open documents" is selected, then you must choose the "Use default settings for serving documents" option on the Advanced Settings page. If you select "Does not use the Gateway to open documents" on the Main Settings page, then you must select "Use remote web server to serve documents" on the Advanced Settings page. (Issue #34427)
  
  Workaround: Always use the "Uses the Gateway to open documents" option with the "Use default settings for serving documents" option, and use the "Does not use the Gateway to open documents" option with the "Use remote web server to serve documents" option.
• Asian character documents downloaded using Netscape on an English system will be named ____________.<ext>. This is a known Netscape bug. (Issue #35344)
  
  Workaround: Use Netscape on a Japanese system to have downloaded files named properly.