Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.2.2) for Microsoft Windows Part Number B25474-09 |
|
|
View PDF |
Oracle has released a series of cumulative patches that can be applied to Oracle Collaboration Suite 10.1.2 on platforms other than Windows. These patches were released after the beta release of Oracle Collaboration Suite for Windows 10.1.2. The bug fixes and new features contained in these patches have been included as part of the official 10.1.2.2 Oracle Collaboration Suite for Windows release. This chapter describes these new features and, in some cases, accompanying known limitations.
Note: This document was updated on February 23, 2007. Additional updates and new information can be found in Note 415183.1 on http://metalink.oracle.com. |
Section 2.1, "Oracle Calendar Application System Cumulative Patches"
Section 2.3, "Oracle Collaborative Portlets Cumulative Patches"
Oracle Calendar application system Cumulative Patches include all new features introduced in current and previous 10.1.2.x cumulative patches. The following sections summarize these new features.
Section 2.1.1, "New in Oracle Calendar Application System Patch 10.1.2.2"
Section 2.1.2, "New in Oracle Calendar Application System Patch 10.1.2.1"
This section describes the new features included with Oracle Calendar application system Cumulative Patch 10.1.2.2.
Support for Australian Daylight Saving Time Changes for the Year 2006
The Oracle Calendar application system now supports the changes to Australian daylight savings time that are occurring in Canberra, Melbourne, Sydney, Hobart, Brisbane, and Adelaide for the 2006 Commonwealth Games. For this new feature to work, Oracle Calendar server cumulative patch 10.1.2.2 must also be installed.
New Oracle Mobile Data Sync Devices
The following devices are certified for use with Oracle Mobile Data Sync:
Sony Ericsson 520i
Motorola A1000 and FOMA M1000
Devices using Synthesis client on Windows Mobile 5.0
Nokia 6670
Siemens SK65, SL65
Process Management Changes
Oracle Calendar application system fcgi processes are now managed by the ocasdmn
daemon, and (on Windows only) a service, ocassvc.exe
. (4886465)
The ocasdmn
daemon does the following:
Initially creates the number of ocas.fcgi
processes specified on startup, and one ochecklet.fcgi
.
Restarts the fcgi processes if they terminate unexpectedly.
Terminates the fcgi processes upon orderly shutdown.
The Windows service, ocassvc.exe
, controls starting and stopping of ocas.fcgi
while making sure that the application keeps running after the user has logged out. This single control path integrates management either through Enterprise Manager or a command line. The Windows service can be started and stopped using the traditional ocasctl.bat
command, the Enterprise Manager console, or the Windows XP interface.
These changes to process management mean that the ocasctl
command should now be used as follows:
ocasctl -t ochecklet
is no longer required.
ocasctl -start
will start ocas.fcgi and ochecklet.fcgi.
ocasctl -startall
is now supported and is the same as ocasctl -start
.
ocasctl -registerservice/unregisterservice
is new for Windows only.
See Also: For further information on the behavior ofocasdmn , see Oracle Calendar Administrator's Guide at http://www.oracle.com/pls/cs101/. |
This Cumulative Patch includes the following new parameter for Oracle Mobile Data Sync:
wantsequentialsyncmlmessages=true
When this parameter is set to true
, Oracle Mobile Data Sync discontinues a synchronization session if a client sends synchronization messages in the wrong order. This parameter is to be used on a per-device basis in the [ocst-
device
]
sections of ocst.conf
.
Oracle Calendar server Cumulative Patches include all new features and known issues introduced in current and previous 10.1.2.x patches. The following sections summarize these new features and known issues:
The following feature was added in Oracle Calendar server Cumulative Patch 10.1.2.2:
Time zone adjustments were made to the $ORACLE_HOME/ocal/misc/timezone.ini
file to comply with changes made to end of daylight savings time in some Australian states as a result of the 2006 Commonwealth Games. Existing time zone sections affected by the extension of daylight savings time were modified to reflect the new dates on which the transition will be made to standard time in April, 2006.
Table 2-1 lists existing time zone sections that have been modified in the $ORACLE_HOME/ocal/misc/timezone.ini
file:
Note: Events already scheduled between March 26, 2006 and April 2, 2006 by users in geographic locations described in Table 2-1, may require manual adjustment by the event owner. |
Table 2-1 Modified Australian Time Zone Sections in the timezone.ini File
Section Name | Oracle Time Zone List Description |
---|---|
CST-9:30CDT |
Australia/Adelaide, Australia/Broken_Hill, Australia/South, Australia/Yancowinna |
EST-10EDT |
Australia/Currie, Australia/Melbourne, Australia/Sydney, Australia/ACT, Australia/Canberra, Australia/NSW, Australia/Tasmania, Australia/Victoria |
LHT-10:30LHDT |
Australia/Lord_Howe, Australia/LHI |
TST-10TDT |
Australia/Hobart |
The following features were added in Oracle Calendar server Cumulative Patch 10.1.2.1:
The $ORACLE_HOME/ocal/bin/unioidconf
utility will now prompt for the SYSOP password when used with the -displaydiscovery option.
To help manage Corporate-Wide Service daemon requests, the following new options have been added for use with the $ORACLE_HOME/ocal/bin/unireqdump
utility:
-requeue
Push a request to the end of the queue.
-setcantservice
Set a request to the "can't service" state.
-setnotserviced
Set a request to the "not serviced" state.
EXAMPLES:
Push the request with ID 300, originating from node 10, to the end of the queue:
Push the request with ID 300, originating from node 10, to the end of the queue:
unireqdump -requeue -reqid 300 -n 10
Set the request with ID 400, originating from node 10, to the "can't service" state:
unireqdump -setcantservice -reqid 400 -n 10
Set the request with ID 500, originating from node 10, to the "not serviced" state:
unireqdump -setnotserviced -reqid 500 -n 10
Time zone adjustments were made to the $ORACLE_HOME/ocal/misc/timezone.ini
file to comply with US Energy Bill specifications. New time zone sections were added for regions maintaining existing time change dates. Moreover, existing time zone sections affected by the US Energy Bill were modified to reflect the new dates on which the time will change, beginning in 2007.
Table 2-2 lists new time zone sections have been added to the $ORACLE_HOME/ocal/misc/timezone.ini
file.
Note: To avoid the possibility of incorrect scheduling times, end users in geographic locations described in Table 2-2 should manually change their default time zone settings from an Oracle Calendar client after this patch is applied. |
Table 2-2 New Time Zone Sections in the timezone.ini File.
Section Name | Oracle Time Zone List Description |
---|---|
PST8PDT_CA |
America/Vancouver, America/Dawson_Creek, America/Whitehorse, America/Dawson, Canada/Pacific |
MST7MDT_CA |
America/Edmonton, America/Yellowknife, America/Inuvik, Canada/Mountain |
CST6CDT_CA |
America/Rainy_River, America/Winnipeg, America/Rankin_Inlet, Canada/Central |
EST5EDT_CA |
America/Montreal, America/Toronto, America/Thunder_Bay, America/Nipigon, America/Iqaluit, Canada/Eastern |
AST4ADT_CA |
America/Goose_Bay, America/Halifax, America/Glace_Bay, Atlantic/Bermuda, Canada/Atlantic |
EST5EDT_CU |
America/Havana, Cuba |
EST5EDT_HT |
America/Nassau, America/Santo_Domingo, America/Port-au-Prince, America/Bogota |
PST8PDT_MX |
America/Tijuana, America/Ensenada, Mexico/BajaNorte |
MST7MDT_MX |
America/Chihuahua, America/Hermosillo, America/Mazatlan, Mexico/BajaSur |
CST6CDT_MX |
America/Guatemala- EST5EDT_TC: America/Grand_Turk |
EST5EDT_INDIANA |
America/Indiana/Indianapolis, America/Indiana/Marengo, America/Indiana/Vevay, America/Fort_Wayne, America/Indianapolis, America/Indiana/Knox, America/Knox_IN, US/Indiana-Starke, US/East-Indiana |
Table 2-3 lists existing time zone sections that have been modified in the $ORACLE_HOME/ocal/misc/timezone.ini
file:
Note: Events already scheduled between March 11, 2007 and April 1, 2007 by users in geographic locations described in Table 2-3, may require manual adjustment by the event owner. Furthermore, events already scheduled between the second Sunday in March and the first Sunday in April of every subsequent year may also require manual adjustment by the event owner. |
Table 2-3 Modified Time Zone Sections in the timezone.ini File
Section Name | Oracle Time Zone List Description |
---|---|
PST8PDT |
America/Los_Angeles, US/Pacific-New, US/Pacific |
MST7MDT |
America/Denver, America/Boise, America/Cambridge_Bay, America/Shiprock, Navajo, US/Mountain |
CST6CDT |
America/Chicago, America/North_Dakota/Center, America/Menominee, America/Costa_Rica, America/Managua, US/Central |
EST5EDT |
America/New_York, America/Kentucky/Louisville, America/Kentucky/Monticello, America/Detroit, America/Pangnirtung, America/Louisville, US/Eastern, US/Michigan |
AST4ADT |
America/Thule |
AST10ADT |
America/Adak, America/Atka |
YST9YDT |
Canada/Yukon |
NAST9NADT |
Pacific/Pitcairn, America/Juneau, America/Yakutat, America/Anchorage, America/Nome, US/Alaska |
This section outlines known issues in Oracle Calendar server 10.1.2.1.
Due to changes made in the $ORACLE_HOME/ocal/misc/timezone.ini
file, the $ORACLE_HOME/ocal/bin/unimvuser
utility may return the following error message when trying to move a user to a remote node server after applying this cumulative patch:
Cannot move user <userid>. Attempting to move user <userid> failed due to a time zone inconsistency between the source and destination Oracle Calendar servers. This user's time zone may not exist on the destination server. Update the destination Oracle Calendar server to an equivalent version before trying to move this user again.
This error will only occur when all of the following conditions are met:
There is more than one Oracle Calendar server in your node network.
The Oracle Calendar server Cumulative Patch 10.1.2.1 has been applied to the source server, on which the user currently resides.
The user on the source server has modified their time zone preference to a value in Table 2-2.
Using the unimvuser
utility, the administrator attempts to move the user from the Oracle Calendar server running version 10.1.2.1, to an Oracle Calendar server running an inferior version (excluding Oracle Calendar server 9.0.4.2.12).
In order to workaround this issue, Oracle recommends upgrading the destination server to Oracle Calendar server 10.1.2.1 before attempting to move the user again.
For more information about modifications made to the timezone.ini
file in this cumulative patch, see Section 2.2.1, "New in Oracle Calendar Server Patch 10.1.2.2" and Section 2.2.2, "New in Oracle Calendar Server Patch 10.1.2.1".
The following feature was added in Oracle Collaborative Portlets Cumulative Patch 10.1.2.2:
Enhance the way messages are displayed in the Portlet
This feature provides users with the ability to set the number of messages displayed in the Portlet. Previously, users (and administrators) could only set the portlet to display messages from a given (n) number of days in the past.
Oracle Content Services Cumulative Patches include all new features introduced in current and previous 10.1.2.x patches. The following sections summarize these new features.
The following features were added in Oracle Content Services Cumulative Patch 10.1.2.2.0:
Hardware Retention using EMC Centera Capabilities
Online Help
The following features were added in Oracle Content Services Cumulative Patch 10.1.2.1.1:
Setting Up Basic Authentication with HTTP+SSL (HTTPS)
Note: This must be set up after installing the patch. |
Customers who store end users' user information and passwords in Microsoft Active Directory, and want to allow those end users to be able to use WebDAV (Oracle Drive or Web Folders) will benefit from Enhancement 4760981: Need basic authentication for HTTPS (not HTTP) so Active Directory integration will work.
Customers must follow the steps to integrate Active Directory with Oracle Internet Directory, as described in Chapter 9, "Managing Microsoft Active Directory Integration" of Oracle Collaboration Suite Administrator's Guide. After following those instructions (and independent of this patch), end users will be able to log into the Oracle Content Services Web client using their user name and password from Microsoft Active Directory. By applying this patch, end users will also be able to log into Oracle Content Services using WebDAV (Oracle Drive or Web Folders).
Basic authentication is necessary because the only way for Oracle Internet Directory to authenticate the end user is to pass the plain text password to Active Directory for verification. When basic authentication is not present, digest authentication is used. But with digest authentication, Oracle Internet Directory does not have the plain text password to pass to Active Directory for verification, and therefore, end users cannot be authenticated.
Note: Basic authentication is not supported over HTTP without secure sockets layer (SSL), because the communications channel between the end user and the server would not be encrypted and the end user password would be transmitted similarly unencrypted. |
To set up basic authentication to work with Oracle Content Services using HTTP+SSL (HTTPS):
Note: Due to this new enhancement, there is one additional step beyond those mentioned in the Oracle Collaboration Suite Security Guide. |
Access Oracle Enterprise Manager 10g Application Server Control Console for Collaboration Suite.
Sign in as the ias_admin
user.
On the Oracle Collaboration Suite Home page, click the link corresponding to Oracle Content Services.
Click Domain Properties.
Edit IFS.DOMAIN.APPLICATION.ApplicationPort
to point to the non-WebCache HTTP Server SSL port.
Set IFS.DOMAIN.APPLICATION.ApplicationUseHttps
to TRUE
.
Additional step: Set IFS.DOMAIN.PROTOCOLS.DAV.CleartextAuthenticationEnabled
to TRUE
.
Click Restart Domain to restart the Oracle Content Services domain.
Additional steps are necessary to integrate Active Directory with Oracle Internet Directory.
The following features were added in Oracle Content Services Cumulative Patch 10.1.2.1.0:
With the application of this patch, Oracle Content Services now provides hardware retention capabilities through Network Appliance SnapLock.
Tip: For more information:
|
Additionally, this patch updates the online help for the Oracle Content Services UI and fixes several Oracle Content Services 10.1.2 bugs.
The following feature was added in Oracle Discussions Cumulative Patch 10.1.2.2.0:
Web Services: Oracle Discussions now has web services for building custom applications and integrating Oracle Discussions functionality into existing applications. For more information on web services for Oracle Discussions, see Oracle Discussions Java API Reference (Javadoc) and Oracle Discussions Application Developer's Guide.
Oracle Mail Cumulative Patches include all new features and known issues introduced in current and previous 10.1.2.x patches. The following sections summarize these new features and known issues.
The following features were added in Oracle Mail Cumulative Patch 10.1.2.2:
Display optional name or contact name in system generated messages.
Oracle Mail now supports modification of the From: header in generated auto-reply or Notification messages to optionally allow the use of the friendly Displayname field instead of a simple e-mail address. This feature can be enabled or disabled by completing these steps:
To enable, edit the file esga.sql
. Set g_rule_oid_lookup
to 1
and then run the SQL script as es_mail
on the storage database.
To disable, set g_rule_oid_lookup
back to 0 and then run the SQL script as es_mail
on the storage database.
10g JDBC connection pooling has been implemented.
Shared folders listing performance has been improved.
Quota management enhancements
IMAP support for RFC-2087
SMTP server stops user from sending e-mails over-quota by a configurable limit (orclMailQmNoSend
)
New PL/SQL package generates warning messages for users over multiple soft warning limits (orclMailQmNotifications
)
In Oracle WebMail, Address Lookup (Advanced Search) does not work. (5197400)
The following sections describe important information about Oracle Web Access client Cumulative Patches.
Section 2.7.1, "New in Oracle Web Access Client Patch 10.1.2.2"
Section 2.7.2, "Known Issues in Oracle Web Access Client Patch 10.1.2.2"
The 10.1.2.2 Cumulative Patch of the Oracle Web Access client includes support for the following new functionality:
Mail templates
Public distribution list management
Spell checker
Ability to create tables in HTML-formatted messages
Improved interface for rules management
After applying Cumulative Patch 10.1.2.2 to an Oracle Web Access client installation that has customized skins or menus, the bodies of mail messages may appear to be empty.
To work around this problem, you need to find all the changes done by the Cumulative Patch to the default skin and menu files, and apply similar changes to your customized skin and menu files. The best way to do this is to back up the default skin and menu files before installing the Cumulative Patch, do a diff
between these files and their new versions after installing the Cumulative Patch, then examine these changes and apply them to your customized files.
You must also add and possibly modify new images that correspond to new features.
The process for making these updates is described in the following steps.
Before applying Oracle Web Access client Cumulative Patch 10.1.2.2, make a backup of all menus and skins for comparison; for example:
cd $ORACLE_HOME/ocsclient mkdir skins_menus_10.1.2.1 tar cfv skins_menus_10.1.2.1.tar skins menus gzip skins_menus_10.1.2.1.tar mv skins_menus_10.1.2.1.tar.gz skins_menus_10.1.2.1 cd skins_menus_10.1.2.1 gunzip skins_menus_10.1.2.1.tar.gz tar xfv skins_menus_10.1.2.1.tar
Apply Oracle Web Access client Cumulative Patch 10.1.2.2.
Diff the default skin and menu files as follows:
cd $ORACLE_HOME/ocsclient diff skins_menus_10.1.2.1/skins/Modern/styles.css skins/Modern/styles.css diff skins_menus_10.1.2.1/menus/Simplified.xml menus/Simplified.xml
(You can use a different diff
tool if you prefer.)
For every difference, a corresponding modification should be made to the custom skin's css
file (one file per custom skin) or the custom menu definition. For css
files, some tuning may be required so that the appearance matches the old custom skin, particularly for new features such as Distribution List member listing and management.
There are several new image files in Cumulative Patch 10.1.2.2. For each custom skin, the image must be added as-is or adapted to match the appearance of the custom skin. The images are found in $ORACLE_HOME/ocsclient/skins/Modern/images/
.
FollowUp14_unpadded.gif addcolumn.gif addcolumn_disabled.gif addrow.gif addrow_disabled.gif autolayouttable.gif cellprop.gif cellprop_disabled.gif cellpropbg.gif deletecolumn.gif deletecolumn_disabled.gif deleterow.gif deleterow_disabled.gif high_unpadded.gif icon14_DL_Subscribed.gif icon14_DL_Suspended.gif icon14_DL_Unsubscribed.gif icon16_first.gif icon16_first_disabled.gif icon16_last.gif icon16_last_disabled.gif icon16_spell.gif icon16_sysfolder_template.gif icon16_sysfolder_template_sha.gif inserttable.gif inserttable_disabled.gif low_unpadded.gif mailTemplates_22.gif
The following sections describe new features included with Oracle Workspaces Cumulative Patches.
The following feature is available after applying Oracle Workspaces Cumulative Patch 10.1.2.2.0:
Web Services: Oracle Workspaces now has web services for building custom applications and integrating Oracle Workspaces functionality into existing applications. For more information on web services for Oracle Workspaces, see Oracle Workspaces Java API Reference (Javadoc) and Oracle Workspaces Application Developer's Guide.
This patch improved integration between Oracle Workspaces and Oracle Content Services in three key areas:
Security configurations: Users can now view and edit security configurations for all folders in the library. Access to documents and folders in a workspace can be restricted to a subset of workspace members, or it can be extended to non-workspace members.
Category configurations: In 10.1.2, category configurations were not supported for content in workspace libraries. This is supported in 10.1.2.1. Workspace operations will prompt for required category attributes, as required, and the category configurations can be seen in the folder properties. Modifying category configurations must still be done through the Content Services user interface.
Note: In 10.1.2, Categories were explicitly disabled at the root workspaces container level. When 10.1.2.1 in installed, this restriction will be removed, allowing Categories to be defined on Workspaces content. |
Workflow configurations: In 10.1.2, workflow configurations were unsupported for content in workspace libraries. In 10.1.2.1, Workspaces supports operations that are configured to use an out-of-the-box workflow and will prompt for required attributes as needed, informing users when a workflow request has been generated. However, checking and changing workflow configurations must still be done through the Content Services user interface.
Note: In 10.1.2.1, controlling Workspace library operations with custom workflows has not been certified.In 10.1.2, Workflow was explicitly disabled at the root workspaces container level. When 10.1.2.1 is installed, this restriction will be removed, allowing Workflow to be defined on Workspaces content. |