This chapter explains how to administer the calendar service in Oracle Communications Convergence.
See "Enabling Core Services for Convergence" for information about enabling services.
To configure CalDAV Service with Convergence, you must have the CalDAV server installed and configured.
To enable Convergence to work with CalDAV, perform the following steps:
Enable the following CalDAV related parameters in Convergence:
caldav.enable - Set this parameter to true to enable the search service.
iwcadmin -o caldav.enable -v true
caldav.host - Set this parameter to the host name on which the CalDAV server installed.
iwcadmin -o caldav.host -v siroe.com
caldav.port - Set this parameter to the web component port number on which CalDAV is deployed. This should be same as the port number specified for Server Instance HTTP Port in the GlassFish Server Configuration Details panel during the Calendar Server Initial Configuration.
iwcadmin -o caldav.port -v port_number
caldav.proxyadminid - Set this parameter to the proxy admin id on which CalDAV is deployed. This should be same as the Administrator User Id specified during Calendar Server 7 Initial Configuration.
iwcadmin -o caldav.proxyadminid -v proxy_admin_id
caldav.proxyadminpwd - Set this parameter to the proxy admin password on which CalDAV is deployed. This should be same as the Administrator password specified during Calendar Server Initial Configuration.
iwcadmin -o caldav.proxyadminpwd -v proxy_admin_pwd
caldav.serviceuri - Set this parameter to the serviceuri on which CalDAV is deployed. This should be same as the URI Path where the Calendar Server is deployed and should be suffixed with /wcap. For example, if the URI path where Calendar Server is deployed is /caldav, then this parameter should be set to /caldav/wcap.
iwcadmin -o caldav.serviceuri -v service_uri
Note:
Convergence can be configured to enable calendar service using both CS 6.x and CalDAV back-end servers and it is called co-existence mode. In this mode of configuration some users may be using CS 6.x server and others might have been migrated to CalDAV server. You need to set the caldav.davuserattr parameter to an LDAP attribute used in the user entry to indicate that the user has been migrated to CalDAV. The default value of this attribute is davStore (defined as part of davEntity ObjectClass). If this attribute is not present in user LDAP entry then it indicates that you are a CS 6.x user and not a CalDAV user.
iwcadmin -o caldav.davuserattr -v user_attribute
Restart the GlassFish server.
You can configure Convergence to send you SMS notifications of your calendar events.
When a user sets up calendar event reminder SMS notifications in the Convergence UI, Calendar Server generates the notifications as specially formatted messages with SMS addresses as recipients; they are then submitted to Messaging Server for processing. Within Messaging Server, the SMS channel processes the notification messages. The messages are submitted to an SMSC provider (through an SMPP protocol) to be delivered as SMS messages to SMS addresses.
SMS addresses, which are added by end users to the Convergence UI, should be of the form +subscriber_number@sms.your_domain, where subscriber_number is usually a phone number where a user expects to receive SMS notifications. The format of each subscriber_number is specific to the SMSC provider. For example, some providers might require an international format with the country code. The portion @sms.your_domain represents a site-specific domain name and is the same name that is used in the Messaging Server's SMS channel configuration.
To enable SMS calendar notifications in Convergence:
Set up and configure an SMS channel in Messaging Server. See Messaging Server System Administrator's Guide for more information.
Enable SMS notifications for calendar events in Convergence server:
iwcadmin -o user.cal.enablesmsnotify -v true
Convergence users can now enable SMS calendar notifications in Convergence in the Convergence Options tab.