Preface
This guide describes how to use the Web Calendar Access Protocol 7.0 (WCAPbis) with Oracle Communications Calendar Server. You use the WCAP commands to access calendar services and data.
Audience
This guide is intended for developers who want to write custom calendar clients that integrate with Calendar Server. This guide assumes you are familiar with the following topics:
-
Basic administrative procedures for your platform operating system
-
Oracle GlassFish Server and Oracle WebLogic Server
-
Lightweight Directory Access Protocol (LDAP), if you plan to use an LDAP directory server to store user information
-
Directory Server
-
System administration and networking
-
General deployment architectures
-
Calendaring concepts
-
Calendaring Standards as described in RFC 5545, RFC 2446, RFC 2447, available on the IETF website at:
Related Documents
For more information, see the following documents in the Calendar Server documentation set:
-
Calendar Server System Administrator's Guide: Provides instructions for administering Calendar Server.
-
Calendar Server Concepts: Provides an overview of Calendar Server.
-
Calendar Server Installation and Configuration Guide: Provides instructions for installing and configuring Calendar Server.
-
Calendar Server Release Notes: Describes the new features, fixes, known issues, troubleshooting tips, and required third-party products and licensing.
-
Calendar Server Security Guide: Provides guidelines and recommendations for setting up Calendar Server in a secure configuration.
Nomenclature
The following nomenclature is used throughout the document.
| Convention | Meaning |
|---|---|
|
Application Server |
The term Application Server or application server is used in this document to refer to either GlassFish Server or WebLogic Server. Supported Application Server: Oracle Communications Calendar Server 8.0.0.3.0 and previous releases were deployed on GlassFish Server, which is no longer supported by Oracle. For that reason, Calendar Server 8.0.0.4.0 and beyond are only supported on Oracle WebLogic Server. Oracle strongly recommends that you upgrade your Calendar Server environments to release 8.0.0.4.0 or higher and migrate to WebLogic Server to receive full Oracle support. |
| Directory Server | The term Directory Server or directory server is used in this document to refer to either Oracle Unified Directory Server (OUD) or Oracle Directory Server Enterprise Edition (ODSEE). Oracle strongly recommends that you migrate from ODSEE to OUD to receive full Oracle support. |
Note:
Calendar Server release 8.0.0.6.0 and above support Oracle Unified Directory Server 12.2.1.4. For Oracle Unified Directory support, you need to install and run DS setup 6.4.0.30.0. For more information, see the appendices "rundssetup Reference" and "ODSEE to OUD Migration" in Oracle Communications Calendar Server Installation and Configuration Guide. ODSEE is not supported from 8.0.0.8.20250424.
Calendar Server 8.0.0.8.20250424 supports MySQL Server 8.4. Calendar Server 8.0.0.6.0 and above support MySQL Server 8.0 in addition to MySQL Server 5.7.x. Calendar Server 8.0.0.6.0 and above does not support MySQL Server 5.5.x.
Documentation Accessibility
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.
Access to Oracle Support
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.
Diversity and Inclusion
Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.