Release Notes
Release 8.0
E63139-03
March 2021
This document provides release notes for Oracle Communications Calendar Server Release 8.0:
This section lists the feature enhancements released in Calendar Server 8.0 patch sets.
From patch set 8.0.0.4.0 onwards, Oracle Communications Calendar Server is supported and certified only on Oracle WebLogic Server.
For more information, see:
Calendar Server Installation and Configuration Guide
Calendar Server System Administrator's Guide
Calendar Server Security Guide
A new WCAP parameter is introduced for storing external attachments. See WCAP Developer's Guide for more information.
This section lists the new features released in Calendar Server 8.0.
Calendar Server 8.0 uses a managed bean (MBean) created in Oracle GlassFish Server to collect monitoring data. By using the GlassFish Server's Java Management Extension (JMX) interface, you can then access this data by using a JMX-compliant client. The JMX client connects to the platform's MBeanServer by using a JMX Service URL. Once a client connects to the MBeanServer, it uses the Calendar Server monitoring MBean object name to access the MBean's attributes.
In addition to using monitoring data gathered by the Calendar Server monitoring MBean, you can also check the health of your hosts by using the Calendar Server supplied responsetime script. This script sends a set of basic requests to Calendar Server and measures the amount of time needed to process those requests. When the responsetime script shows a spike or a large increase in response time, this indicates a potential issue with Calendar Server that needs to be addressed.
For more information, see the chapter on monitoring in Calendar Server System Administrator's Guide.
This release of Calendar Server supports the following global inet*status attributes, at the domain, end user, and resource levels:
davcore.ldapattr.inetresourcestatus
davcore.ldapattr.inetuserstatus
The davadmin repair command now includes domain migration support.
This section lists issues fixed in Oracle Communications Calendar Server 8.0.0.0.0.
Note:
For the list of issues that have been fixed in 8.0 patch sets, refer to the patch readme documents on My Oracle Support.Table 1 lists and describes the issues fixed in this release of Calendar Server.
Table 1 Fixes in Calendar Server 8.0
| Bug Number | Customer SR | Notes |
|---|---|---|
|
24696527 |
N/A |
Timezone stripping sometimes removes latest RDATE. |
|
24589802 |
N/A |
Domain caching is not honored. |
|
24492082 |
N/A |
The davadmin passfile create command failed. |
|
24470857 |
3-13130618141 |
An event remains in the invitee agenda after being removed from the owner agenda. |
|
24387135 |
N/A |
Oracle DB incorrectly calculates timestamp due to session timezone. |
|
24319668 |
N/A |
The davadmin command displays erroneous message. |
|
23129149 |
N/A |
Cal:last segment of URI should be made opaque for calendar created by using davadmin command. |
|
22234574 |
N/A |
The davadmin repair command should support moving users between domains. |
|
22112329 |
N/A |
A wcap import fails with error 500 when UID is same for event and todo. |
|
21380910 |
N/A |
The inetuserstatus and inetresourcestatus attributes are not working as expected. |
|
21241796 |
N/A |
The import.wcap response should provide the total count of imported entries. |
|
17310430 |
N/A |
An attachment file should be handled properly if the file name has more than 230 characters. |
This section lists the known problems in Calendar Server 8.0 patch sets.
Patch Set 8.0.0.4.0 onwards
Bug number: 32187735
Configuration of Calendar Server fails only on WebLogic Server 12.2.1.4 but works with WebLogic Server 12.2.1.3.
Workaround: Before configuring Calendar Server on WebLogic Server 12.2.1.4, perform the following steps:
Copy the required mysql-connector-java-5.1.x connector jar version to the lib directory of your WebLogic domain.
For example, if you want to deploy Calendar Server on domain 1, copy the jar to: WebLogic_home/user_projects/domains/domain1/lib/
Note:
The mysql-connector-java-5.1.35-bin.jar file is already available in the installation location of Calendar Server: /opt/sun/comms/davserver/lib/jars. Copy this jar to the lib directory of WebLogic domain.Restart WebLogic Server.
Patch set 8.0.0.3.0 onwards
Bug number: 30031880
This impacts only for GlassFish Server 3.x deployments. These deployments are supported only with Java 7.
Workaround: Before running the davadmin command, set your terminal's JAVA_HOME and PATH environment variables to JDK 1.8.0_update.
Patch set 8.0.0.4.0 onwards
Bug number: 29649135
WebLogic Server deployments do not support the Browse-servlet option of Calendar Server.
Workaround: Use the davadmin CLI Admin tool for all administrative activities.
Patch set: All 8.0 patch sets
Bug number: 30547042
This is applicable only for GlassFish Server 3.x deployments for all releases since 8.0 and patch sets.
Workaround: Use GlassFish Server version 3.1.2.18.
This section lists the known problems in Calendar Server 8.0.
SR number: N/A
Bug number: 24818711
After running the davadmin account repair -D command, due to a user being moved from one domain to another, VALARM still shows the user's old email address.
Additionally, the following other problems are noticed:
If user B subscribes to user A's calendar, and the domain of user A's email address is changed, then the subscribed calendar is not found in the list of user B's subscribed calendars.
If user B grants user A management rights, and the domain of user A's email address is changed, then user B's account properties no longer show that user A has been granted management rights.
SR number: N/A
Bug number: 21487603
If the host that the responsetime script queries is experiencing high load, the script might fail and display the message '207: Response Time request failed.'
SR number: N/A
Bug number: 20427454
Calendar Server cannot create events for, nor can users invite, users whose email address contains double quotation marks, such as "caluser1"@example.com.
SR number: N/A
Bug number: 20606487
The davadmin command accepts incorrect values for the following configuration parameters:
log.dav.commands.loglevel
log.dav.errors.loglevel
log.dav.scan.loglevel
log.dav.scheduling.loglevel
log.dav.telemetry.loglevel
notification.dav.smtpport
If you had inadvertently set an incorrect value on any of these parameters, and then upgrade to the current version of Calendar Server, the server might not start.
Workaround:
To work around this issue:
Stop Calendar Server:
GlassFish_home/bin/asadmin stop-domain domain
Manually edit the davserver.properties file to change any incorrect value of the affected configuration parameters.
Valid log level values are OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL.
Start Calendar Server:
GlassFish_home/bin/asadmin start-domain domain
SR number: N/A
Bug number: N/A
If you create a calendar by using Convergence, and then try to delete the calendar on a device that is on iOS 8, an iOS 8 device, the calendar is not removed from the Calendar Server database. If you create and delete the calendar on iOS 8, it is removed from the Calendar Server database.
This problem occurs because Convergence creates calendars with both VEVENT and VTODO as supported components. The VTODO component instructs the iOS Calendar app that other VTODO applications can use the calendar, and so the iOS Calendar app does not delete it.
SR number: N/A
Bug number: 20050746
Calendar Server is capable of processing a calendar event received in an iCalendar Message-Based Interoperability Protocol (iMIP) message by using the iSchedule protocol. This capability enables "internal" users to automatically process calendar invitations from "external" users. Currently, however, Calendar Server cannot process a calendar invitation email from Yahoo, and the event does not get added to the user's calendar. The problem is that the Yahoo calendar invitation is improperly formatted. As a result, Calendar Server rejects the event.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Communications Calendar Server Release Notes, Release 8.0
E63139-03
Copyright © 2015, 2021, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.