| Oracle® Calendar Application Developer's Guide 10g Release 1 (10.1.1) Part Number B14477-01 |
|
|
View PDF |
| Oracle® Calendar Application Developer's Guide 10g Release 1 (10.1.1) Part Number B14477-01 |
|
|
View PDF |
This chapter provides an overview of Oracle Calendar Web services and the Web services toolkit.
Related documents:
Internet Calendaring and Scheduling Core Object Specification (iCalendar) http://www.ietf.org/rfc/rfc2445.txt
Web Services Activity http://www.w3.org/2002/ws/
Web Services Description Language (WSDL) http://www.w3.org/TR/wsdl
Simple Object Access Protocol (SOAP) 1.1 http://www.w3.org/TR/SOAP/
Oracle Calendar Web services is a component of the Oracle Calendar application system, which handles application-level services. Web services allows applications to retrieve, through common XML queries, calendar data for display in any portal, client application, or backend server. iCal data is coded in XML, wherein iCal becomes xCal. SOAP is used to encapsulate the messages for delivery. The calendar data Web services SOAP is stored directly on the Oracle Calendar server store. This is in effect the CWSL, or Calendar Web services Language.
This current implementation does not provide any WSDL or UDDI support. However, future versions may provide the ability to publish WSDL to a UDDI registry.
Developers can use the Oracle Calendar Web services toolkit to build Web services applications and create SOAP 1.1 queries. The toolkit contains the functionality to search, create, modify, and delete calendar events, as well as search tasks. It gives SOAP access to the Oracle Calendar server database through a series of Java classes, known as the Calendarlet. This allows developers to use a Java IDE, abstracting the XML structure required to build applications.
Use the Calendarlet to create your own clients and integrate calendar data into your own applications. To integrate calendar data within any portal, client application, or backend server, you need to be able to make an HTTP connection to the Web server hosting Web services, generate SOAP messages and parse the SOAP responses (using any technology that can send and receive HTTP strings), and make use of an existing XML toolkit to generate outgoing and parse incoming HTTP strings with a SOAP client toolkit. The toolkit supports the use of HTTP proxies.
