Thank you for choosing the Oracle Calendar API (CAPI). These release notes contain known limitations and problems with the product. For installation instructions, see the Readme file.
Contents of this file
- System requirements
- How to report problems
- What's new in version 2.5
- Resolved limitations since version 2.5.1
- Resolved limitations since version 2.5
- Limitations, caveats and known problems with this release
System requirements
One of the following Oracle calendar servers:Please note that older calendar server versions may not be able to take advantage of all CAPI functionality.
- CorporateTime Server 5.4 or greater
- Oracle Calendar server 5.5 or greater
Version 2.5 of CAPI is certified against the following platforms:
- SPARC Solaris 2.6 (using Sun's recommended patches from 21 February 2001 and Sun Workshop 5.0)
- HP-UX 10.20 (using cc version A.10.32.30 and aCC version A.01.23)
- IBM AIX 4.3.3 (using VisualAge C++ 5.0)
- Red Hat Linux 6.1 (using egcs-2.91.66 19990314/Linux (ecgs-1.1.2 release) compiler)
- Microsoft Windows NT 4.0 (using MSVC 6.0)
How to report problems
Contact Oracle Support at support@steltor.com or call (514) 733-8500.
What's new in version 2.5
Version 2.5 of CAPI provides all the features and functionality of the previous 2.0.1 release under the Oracle banner, and will also provide the basis for all future upgrades. Version 2.5 includes the following changes:
- Thread-safe: Multi-threaded applications can call CAPI functions simultaneously through multiple threads.
- Web connections: CAPI can now connect to the calendar server using the same connection mechanism as the Web client, through new CAL_ClientIdentify attributes.
- Web authentication: The Web authentication plug-in (aut_web) is now supported when connecting to a master node.
- Excluding event types: New CAPI_Flag constants exclude holidays, day events, daily notes and meetings when fetching events.
- SYSOP logins: CAPI now allows signons as SYSOP, if enabled by the
unison.ini [ENG] allowsysoplogon_capiparameter on the server side.- CAPI_SetIdentity enhancements: The CAPI_SetIdentity function now allows the SYSOP to assume the identity of any other user.
- CAPI_CreateFileStream enhancements: The CAPI_CreateFileStream function now accepts file names instead of file handles.
- VTIMEZONES support: CAPI now supports the use of VTIMEZONES with recurrence rules.
- Notification and reminder improvements: A number of behavioural changes have been made to notifications and reminders, including:
- E-mail notification subject fields now include the event title instead of the sender's name.
- E-mail notification of repeating meetings only lists changed instances.
Resolved limitations since version 2.5.1
The 2.5.2 patch, available only for the IBM AIX 4.3.3 platform, includes the following changes:
- Memory leaks: Memory leaks no longer occur when using the flags CAPI_FLAG_FETCH_NO_FIELDHOLDERS or CAPI_LOGOFF_STAY_CONNECTED. (Ref: #2745455.)
- CAPI_LOGOFF_STAY_CONNECTED: Using CAPI_LOGOFF_STAY_CONNECTED while logged in as SYSOP no longer causes the system to crash. Instead, an error is returned by CAPI_Logoff. NOTE: If you want to change identities while logged in as SYSOP, just use the CAPI_SetIdentity function. (Ref: #2745477.)
- CAPI_StoreEvent(CAPI_STORE_REPLACE):
In this mode, when an event's DTSTART or RRULE is changed, the event's obsolete instances are now removed from the server. (Ref: #2745491.)
Resolved limitations since version 2.5
The 2.5.1 patch, available for all certified platforms, includes the following change:
- SYSOP logon: You can now log on to the Calendar server using CAPI_AuthenticateAsSysop(). Previously, the logon would fail with the status CAPI_STAT_SECUR_LOGON_LOCKED_SYSOP, even if the server was configured to allow this type of logon. (Ref: #2748125, 2748126, 2748144, 2748147, 2748148.)
Limitations, caveats, and known problems with this release
Solaris C++ compiler
For binary compatibility with Oracle's standard shared calendar libraries, users with Solaris platforms must have the native Sun C++ compiler installed.