Applying to Develop to the Scheduling API
Developers wishing to use the Scheduling API with a third party calendaring or groupware application need to apply to receive the Scheduling API Developers Guide and License to enable the feature.
Developers need to;
Developers will need Cisco Telepresence products for development and testing their application.
It is recommended the following be purchased for the developers lab;
1) Cisco Telepresence Commercial Express Bundle (CTS-COMM-EXP1.7-K9) which includes a MCS Server using VMware to support CTS Manager, CTS Multipoint Switch, and CTS Recording Server.
2) Cisco Communications Manager 7.1.3 or higher enterprise edition.
3) Cisco Telepresence endpoints are not required, but recommended. The CTS-500 series is best for testing. If you don't have CTS endpoints, you can create in Communications Manager phantom endpoints which will allow for scheduling in your goupware application.
4) An LDAP Active Directory Server.
Registering as a Cisco Developer will allow for purchase of Cisco lab equipment at not for resell discounts.
The Scheduling API feature is licensed. Developers after going through the appoval steps detailed above will receive a Cisco Software License PAK via shipment. This document PAK number and License MAC address for the CTS-Manager then needs to be registered at http://cisco.com/go/license to receive the license file. Once the licensing file is received via email after registration, upload the license file to CTS-Manager to enable the Scheduling API.
LDAP Active Directory Requirements
CTS Manager and the scheduling API requires LDAP for user authenication. An Active Directory server is recommended as the LDAP Source.
During first time setup of CTS Manager administrator needs to provide LDAP server information. All TelePresence rooms and schedulers should be part of this LDAP server. The API will retrieve scheduler display name and room display name from this LDAP server.
LDAP administrator should create a new user account in LDAP server. This account would represent the ECA. When ECA invokes the API it will use this account to authenticate itself to CTS Manager. During first time setup of CTS Manager, this account should be specified on ECA configuration page.
The API would work in most SOAP development environments but has been tested in this release with Apache Axis2. Documentation provides examples in Java. The Java examples are based on Apache Axis2 (1.3) and JDK 5.0 (Java 2 Platform Standard Edition Development Kit 5.0). For more information about Apache Axis 2, go to http://ws.apache.org/axis2/.
Note: Different development platforms vary in their specification implementations. Implementation differences might prevent access to some or all of the features in the API.
ECA as API Client
ECA is a client to CTS Manager server. It has following roles and characteristics:
1. ECA is a web services client.
2. It can generate calendaring data in RFC 2445 (iCalendar specification) and RFC 2446 format.
3. It has some kind of data store to persist calendaring data.
There is only one ECA that communicates with CTS Manager.