4 Oracle Calendar Release Notes

4.1.3.1 Multiple Oracle Calendar Server Installations with the Same Infrastructure Tier

When installing the Oracle Calendar server, and pointing to an Infrastructure tier that has already been configured with a previous installation of the Oracle Calendar server, all Oracle Calendar servers must be running before beginning the new installation.

4.1.3.2 SMS Notifications Not Delivered in an SSL Environment

Users will not receive SMS notifications in an SSL environment because the Oracle Calendar notification listener URL was not properly registered. Apply the associated workaround only if SMS notifications are not being delivered from Oracle Calendar server in an SSL environment.

Workaround:

1. Create a back-up copy of the $ORACLE_HOME/ocal/misc/unison.ini file.

2. Open the $ORACLE_HOME/ocal/misc/unison.ini file.

3. Locate the [NOTIFY] section of the file and modify the appropriate parameters to reflect the following values:

   alert_url = x-oracle-calendarNotificationListener://<ApplicationsTierHost>:<WirelessNotificationEngPort>?protocolVersion=2
   alert_sms = TRUE
   alert_sms_auto = FALSE
   alert_url_auto = FALSE
   
   

   
   

   Note: The value for <WirelessNotificationEngPort> can be found by looking for "Wireless PIM Notification Dispatcher port" in the $ORACLE_HOME/install/portlist.ini configuration file on your Applications tier.

   
   

4. Restart the Oracle Calendar server. For more information on restarting the Oracle Calendar server, see "Starting and Stopping the Calendar Server" in Chapter 5 of Oracle Calendar Administrator's Guide.

4.1.3.3 The aut_sasl Plug-in is No Longer Packaged with the Oracle Calendar server

The Oracle Calendar server no longer supports the use of aut_sasl as an ACE plug-in for Kerberos 4 or Kerberos 5 authentication in 10g Release 1 (10.1.1 or later).

Workaround:

Use Kerberos 5 with the aut_gssapi ACE plug-in for authentication. For more information about configuring the Oracle Calendar server for Kerberos 5 authentication see, "Kerberos 5 Authentication with Oracle Calendar" in Chapter 2 of Oracle Collaboration Suite Security Guide.

4.1.3.4 Oracle Workspaces with Web Conferences

See Section 11.3, "Known Limitations and Workarounds in Oracle Workspaces" for information on a Calendar-related issue in Oracle Workspaces.

4.1.3.5 Oracle Calendar Wireless Reminders Configurable on Oracle Mobile Collaboration

Wireless reminders for Oracle Calendar are no longer configurable from the $ORACLE_HOME/ocal/etc/reminder directory on the Applications tier. Oracle Calendar wireless reminders are now configurable from Oracle Mobile Collaboration.

For more information about configuring wireless reminders for Oracle Calendar see "Configuring the Messaging Server for Notifications" in Chapter 2 of Oracle Mobile Collaboration Administrator's Guide.

4.1.3.6 Duplicate Address Book Entries After Upgrade

After upgrading to Oracle Calendar server 10g Release 1, and users' address books have been migrated to the Common Address Book, some address book entries may be duplicated. This applies to Oracle Collaboration Suite deployments only.

When reconciling the Oracle Calendar address book with the Common Address Book, Oracle Calendar server queries the existing contacts based on first name and last name in both the Oracle Calendar address book, and the Common Address Book. If a match is found, the attributes present in both address books entries are compared. If all the attribute values are equivalent, the Oracle Calendar server will merge the two entries. Conversely, if the attribute values differ, to prevent data loss, the Oracle Calendar server will create a new contact, thus creating a duplicate entry.

For more information about the Common Address Book, see "About the Common Address Book (CAB)" in Chapter 6 of Oracle Calendar Administrator's Guide.

4.1.3.7 Oracle Calendar in Arabic

Oracle Calendar does not support Arabic.

4.1.3.8 Oracle Calendar Wireless Notifications

Oracle Calendar wireless notifications are not enabled by default. The XMS center requires the following workaround.

Workaround:

1. Log in to Oracle Enterprise Manager.

2. Click the Applications tier link.

3. Click the Wireless link.

4. Click the Site Administration tab. If the "Component Configuration" section is not expanded, expand it by clicking the "plus sign".

5. Click XMS configuration.

6. Under XMS Center, ensure that Enable XMSC is checked.

7. Go to EM, then Wireless.

8. Select Notification eng.

9. Restart the wireless component.

4.1.3.9 SMS Notifications are No Longer Delivered After Upgrading from Oracle Calendar Server 9.0.3.1

After upgrading from the Oracle Calendar server 9.0.3.1, users who previously received SMS notifications no longer receive SMS notifications on their mobile devices.

Workaround:

All users who are no longer receiving SMS notifications should follow these instructions:

1. Login to Oracle Mobile Collaboration Preferences page with an effected user account by accessing the following URL:

   http://<ApplicationsTier>:<port>/ocsmobile/welcome.uix

   
   

   Note: Specify the appropriate Applications tier, and port for your deployment.

   
   

2. Verify that the Mobile Access Account ID field contains the correct information. If the information is incorrect, modify the field with the appropriate information.

   Click the Apply button.

3. Click the Advanced button. Verify the On the Go radio button is selected from the list of rules in the My Contact Rules table. If it is not selected, choose the On The Go radio button, then click the Apply button.

4. With the On The Go radio button selected, click the Edit button at the top of the My Contact Rules table.

   Verify that My Mobile Phone is selected from the Messages drop-down list, and that Messages is selected from the Notification Channel drop-down list.

   If either, or both of these options are incorrectly configured, correct the appropriate option in the relevant drop-down list.

   Click the Ok button.

5. Select the My Mobile Phone radio button from the My Communication Devices table, then click the Edit button at the top of the table.

   Verify that the My Mobile Phone field contains the correct information. A plus symbol (+) should appear in front of the telephone number. If the field contains incorrect information, update it with the appropriate changes.

   Click the Ok button.

6. Click Logout at the top right side of the browser.

7. Login to the Oracle Calendar Web client with the same effected user account by accessing the following URL:

   http://<ApplicationsTier>:<port>/ocas-bin/ocas.fcgi?sub=web

   
   

   Note: Specify the appropriate Applications tier, and port for your deployment.

   
   

8. Click Preferences at the top right corner of the browser, then click the Wireless tab.

9. Deselect the Enable wireless services and Automatically notify when Entries are created or modified check boxes.

10. Click the OK button.

11. Click Preferences at the top right corner of the browser again, then click the Wireless tab.

12. Select the Enable wireless services and Automatically notify when Entries are created or modified check boxes.

13. Click the OK button.

SMS notifications should now be delivered.

4.4.1.1 Resolved Issues in the Oracle Calendar Application System

Table 4-6 lists resolved issues common to the Oracle Calendar application system as a whole.

4.4.1.2 Known Limitations and Workarounds in the Oracle Calendar Application System

The followins sections describe known limitations and workarounds in the Oracle Calendar application system.

• Section 4.4.1.2.1, "Arabic Not Supported"

• Section 4.4.1.2.2, "Configuring Components on Systems Where the Oracle Calendar Server Is Not Configured"

$ORACLE_HOME/jdk/bin/java -classpath $ORACLE_HOME/ocal/jlib/ocal_clnt.jar:$ORACLE_HOME/jlib/ojmisc.jar:$ORACLE_HOME /lib/xmlparserv2.jar:$ORACLE_HOME/jlib/ldapjclnt10.jar oracle.calendar.server.configuration.OCalGConf -path $ORACLE_HOME -DSmgrp Password_of_DSmgrdn -DSmgrdn cn=orcladmin

4.4.1.3 Known Issues in the Oracle Calendar Application System

The following table lists known issues common to the Oracle Calendar application system as a whole.

4.4.2.1 New in the Oracle Calendar Web Client

Searching

• Search capability has been improved, and the new "Advanced Search" feature provides an even more accurate and specific way of searching for users.

Preferences

• More details are displayed in the Agenda views, and you can customize the level of detail you want printed and displayed.

• Under Preferences, printouts can now be set to include your entries in a detailed, tabular list.

• You can now choose a default Calendar view under Preferences.

• You can set default start and due times for tasks, under Preferences.

Scheduling

• Various improvements have been made to the Scheduler: Tool tips have been improved, the Scheduler grid now automatically gets populated with the most recent resource search results, user and resource names can be clicked for more information, and time slots can be clicked to see the entries they contain.

• Icons can now be clicked to show more details about entries or to change the reply status for events.

• The Daily List and Daily Planner are now referred to as the "List Mode" and "Planner Mode" of the Daily View. The same change applies to the Weekly List and Weekly Planner.

• The Date Control Bar now includes a link to today's date.

• Day Events and Daily Notes can span multiple days.

  
  

  Note: This feature is available only with version 10.1.1 or later of the Oracle Calendar server.

  
  

• When you book a resource, you can choose to automatically fill in the "Location" field of the meeting with the name of the resource.

Per-instance possibilities

• You can create personal notes - information only you or a designate can see - in an entry, or in selected instances of a repeating entry.

• You can attach a file to an instance of a repeating event.

Other

• Longer names for resources, event titles, and locations are supported.

• Administrators can now configure whether or not to highlight remote users with an indicator (such as 'R' in English).

• Download of Microsoft Powerpoint (PPT) and Adobe Acrobat (PDF) attachments is now supported.

4.4.2.2 Resolved Issues in the Oracle Calendar Web Client

Table 4-8 lists resolved issues in the Oracle Calendar Web client.

OH$/OCS1011/ocas/htdocs/ocas//stylesheet/swcada.css
14  0.02% File does not exist:

4.4.2.3 Known Limitations and Workarounds in the Oracle Calendar Web Client

In some secure configurations of the Oracle Calendar Web client, attachments may not be cached on the client's disk (for security and privacy reasons). Due to a bug in Internet Explorer, this prevents users from opening attachments inline using that browser. For example, opening a text attachment from an entry may fail (the default text editor application for the user will launch, and then generate an error that the file could not be found). (4704943)

If you have deployed SSL, attempting to download attachments to disk may also fail.

Documentation of the details of this Microsoft Internet Explorer bug can be found in the following Microsoft Knowledge Base articles:

• "Internet Explorer Cannot Download" Error Message When You Use an HTTPS URL to Open an Office Document or PDF File:

  http://support.microsoft.com/default.aspx?scid=kb;en-us;812935

• INFO: Prevent Caching When You Download Active Documents over SSL:

  http://support.microsoft.com/default.aspx?scid=kb;en-us;815313

• Internet Explorer file downloads over SSL do not work with the cache control headers:

  http://support.microsoft.com/default.aspx?scid=kb;en-us;323308

There are two workarounds available for this issue; you can use a different browser, or, you can relax caching settings. For detailed instructions for relaxing caching settings, see "Security Issues Related to Microsoft Internet Explorer" in Chapter 2 of Oracle Collaboration Suite Security Guide.

4.4.2.4 Known Issues in the Oracle Calendar Web Client

The following table lists known issues in the Oracle Calendar Web client.

4.4.2.5 Globalization Issues in the Oracle Calendar Web Client

The following table lists globalization issues in the Oracle Calendar Web client.

4.4.2.6 Documentation Issues in the Oracle Calendar Web Client

Localized versions of the Oracle Calendar Web client help do not mention that a Web conference key will be generated if one is not specified by the user. (4367351)

4.4.3.1 New in Oracle Calendar Web Services

This section describes new features in Oracle Calendar Web services:

• Proxy authentication has been fully documented.

• The Summary SOAP operation has been added.

• Ultra Search capabilities have been added to the Search SOAP operation.

• The following optional properties have been added to the Search SOAP operation:

  • x-oracle-limitattendees

  • x-oracle-overlap

• Oracle Real-Time Collaboration xCal properties have been added to the XML data format of Calendar data. You can now create Web conferences, for instance.

• Additional modules and error codes have been added.

4.4.3.2 Resolved Issues in Oracle Calendar Web Services

No resolved issues have been documented for Oracle Calendar Web services at this time. For updates, check the latest version of Oracle Collaboration Suite Release Notes at http://www.oracle.com/pls/cs101/install.

4.4.3.3 Known Issues in Oracle Calendar Web Services

The following table lists known issues in Oracle Calendar Web services:

4.4.4.1 New in Oracle Mobile Data Sync

This section describes new features in Oracle Mobile Data Sync.

New device certification

• Nokia 6020, 6021, 6230i, 6260, 6680, 6822, 7260, 7270, 7610, 9300

• Siemens C65, CX65, S65, S66, SX1

• Sony Ericsson K700i, K750i, S700i, S710a, Z600, Z500, Z800i

• Blackberry 6200, 7200

Support for per-instance details and personal notes

Oracle Mobile Data Sync now features the ability to add per-instance meeting details. When you create a recurring meeting, you can now customize the details per instance, such as a meeting agenda. You can also now add personal notes to meetings that you do not own, which will be maintained on your device, even when you next synchronize with the Oracle Calendar server.

Consistent display of multi-day events across Oracle Calendar clients

Multi-day events scheduled in Oracle Connector for Outlook will now display correctly in all Oracle Calendar clients, so that they will not appear to block off time in invitees' agendas. Note that this feature is based on device capability.

New Authentication Method

With previous versions of Oracle Mobile Data Sync (formerly known as Oracle Sync Server), users authenticated themselves using their Single Sign-On passwords. With the release of Oracle Mobile Data Sync 10.1.1, authentication using the Oracle Mobile Collaboration wireless numerical PIN is supported. Users can create this PIN on the Oracle Mobile Collaboration Wireless Preferences page.

When upgrading to Oracle Collaboration Suite 10gR1, Single Sign-On authentication remains in place. Fresh Oracle Collaboration Suite 10gR1 installations use PIN authentication by default. Administrators can change between the two authentication methods by editing the syncml_authcredlabel parameter in the Oracle Calendar server unison.ini file. For information on the syncml_authcredlabel parameter, see "Controlling server behavior" in the Oracle Calendar Reference Manual.

4.4.4.2 Resolved Issues in Oracle Mobile Data Sync

Table 4-12 lists resolved issues in Oracle Mobile Data Sync.

4.4.4.3 Known Issues in Oracle Mobile Data Sync

The following table lists known issues in Oracle Mobile Data Sync.