Knowledgebase: Oracle
Meeting Requests Originating on Device Are Not Sent to Recipients
Posted by - NA - on 06 July 2009 11:06 AM

Prior to Oracle version 10.1.2.4.0, a meeting request originating on a device is not sent to the recipient, nor is the event created on the recipient's calendar.  Meeting requests, however, originating on the server and sent to a device synchronize as expected on the device.


Meeting invitations from the device are fully supported, however, against Oracle 10.1.2.4.0 once the following configuration change is made:


To enable meeting requests from the device, follow the steps below to apply the ocst-notifylink.conf file.

Purpose – Explain how to create a device profile for NotifyLink Enterprise Server in the Oracle ocst.conf configuration file.  By doing this, users will be able to set configurations for SyncML synchronization such as the ability to set meeting attendees from the device.

 

Server Requirements – Oracle Calendar version 10.1.2.4

 

Prerequisite - Obtain the ocst-notifylink.conf file from Notify Technology Corporation.

 

Procedure

  1. Place the ocst-notifylink.conf file in the $ORACLE_HOME/ocas/conf/ocst_profiles directory on the Oracle Calendar server.

 

  1. Open the ocst.conf file for editing on the Oracle Calendar server. This file is located in the $ORACLE_HOME/ocas/conf directory.

 

  1. Locate the list of devices in ocst.conf.  This is a series of lines formatted as “devicexx=DeviceName” where “xx” is two digits.  At the end of the list add the following line:

device<n>=notifylink

where “<n>” is one more than the last number listed. For example, “device93=notifylink”.

 

  1. Scroll to the very end of ocst.conf and add the NotifyLink profile:

#------------------------------------------------------------------------------
# NotifyLink Enterprise Server specific configuration settings
#------------------------------------------------------------------------------
[ocst-notifylink]
man=Notify Technology
mod=
swv=
devinfver=1.1
profile=ocst-notifylink.conf
uncertified=true

 

  1. Save and exit the ocst.conf file.

 

  1. Restart the Oracle Calendar server.

[ocst-settings]
#------------------------------------------------------------------------------
# NotifyLink specific configuration settings
#------------------------------------------------------------------------------
 
# Email configuration settings
#outboxfolder=outbox
#clientfolders=inbox,Drafts,Sent Items
#moveemailsupport=false
#wantnokiaemailfolder=false
#wantnokiaemailread=false
#supportclientsentfolder=true
#supporturiclientsentfolder=true
#clientsentfolder=Sent
#wantremoveincomingemaildate=true
#wantrfc2822folding=true
 
 
# Configuration options that can be changed
#syncrangeback=7
#syncrangeforward=60
maxsyncrangeback=735
maxsyncrangeforward=735
#wantrefusedentries=false
#deloutofrange=true
#confresolution=1
clientsupportsattendeesync=true
#wantattendanceintitle=true
#wantownershipintitle=true
#wantlocationintitle=false
#webconferenceindetails=full
#attendeesindetails=no
#wantnoattendees=false
#maxattendees=10
#wantpersonalnotes=true
 
# The following options should not be altered
#disablecontactmappings=false
#wanthacksummary=false
#wantshortdescription=true
#maxdescriptionlength=2048
#wantshortlocation=true
#maxlocationlength=256
#wantshortsummary=true
#maxsummarylength=256
#
#wantapplymaxlengthtopropvalues=false
#wantshortvcardcomment=false
#maxvcardcommentlength=0
#wantshortvcardtitle=false
#maxvcardtitlelength=0
#wantmapadrtolabel=false
#
#wantmapstatustopercentcomplete=true
#wantpriority=false
#wantutc=false
#wantalarmondayevents=false
#wantignoreincomingutc=true
#wantfixbrokenrruleuntil=false
#wantfixbrokenexdates=false
#wantfixbrokenlinefolding=true
#wantconvertmidnighttasks=true
#wantconvertmidnightevents=true
#wantepoceventmapping=true
#wantsendalldayastimed=false
 
 
 
#wantlinefolding=true
#wantnokiacategorymapping=false
#wantsiemenscategorymapping=false
#clientsupportsconfidential=false
#clientsupportsvtododtstart=false
#clientsupportsvtododue=true
#clientsupportsvtodocompleted=false
#vtodopriorityequivalencevalues=1=1,2=2,3=3,4=4,5=5,6=6,7=7,8=8,9=9
#vtodoclassequivalencevalues=CONFIDENTIAL=PRIVATE
#veventclassequivalencevalues=CONFIDENTIAL=PRIVATE
#recurrencelevelsupport=0
#wantuseserverprefcontenttypes=false
#ignorecommandcontenttype=true
#wantforceoutgoingtaskduedate=false
#wantremovevcalvtododtstart=true
#wantservertimezonesupport=true
#disabledayevents=false
#clientsupportsmultiday=true
#ismultidayexclusivein=true
#ismultidayexclusiveout=true
#wantstripfalseduedate=false
#wantfixbrokenvcalendaralarms=false
#
#wantusechecksumforreplacevevent=true
#veventchecksumpropertyvalues=CLASS,DESCRIPTION,DTEND,DTSTART,LOCATION,PRIORITY,RRULE,STATUS
#,SUMMARY,DUE
#
#wantusechecksumforreplacevtodo=true
#vtodochecksumpropertyvalues=CLASS,DESCRIPTION,DTEND,PRIORITY,STATUS,SUMMARY,DUE,COMPLETED
#
#wantmapstatus=true
#statusequivalencevalues=CONFIRMED=TENTATIVE
 
 
 
 
[contact-settings]
 
# The following directives are the supported type parameters
# supported for the adr, tel, url, and email properties of
# this device. If a device supports the label property,
# use the parameter types from the converted labe to adr property.
# There should be one directive per property type. Thus, if there
# are properties with the same parameter types, there should be
# multiple directives for this.
# The syntax is XXXparamtype<num>=TYPE1,TYPE2,....
# where XXX is either adr,tel,url, or email.
# TYPE1,TYPE2,... are VCARD property paramter values
# for the type parameter.
# TYPE1,TYPE2,... are order sensitive.
# When XXXparamtype<num> is empty, means that there are no parameter
# property types.
 
 
 
 
#Home Address
#adrparamtype1=HOME
#Work Address
#adrparamtype2=WORK
 
 
#URL
#urlparamtype1=WORK
 
# The P910 profile is identical to the P-series profile, except the P910
# contains an extra telephone field: Pager
 
# This device sends and recvs with different parameters.
# The one exception is Mobile/CELL.
# type[1-3,5,6] are for sendings, and type[7-11] are for recieving
# type[4] is the same for sending and receiving
# This device also keeps lists for Home and Work tels.
# Also, it only supports additions from the server for these
# lists. Thus, these numbers will be erratic on the server
# and the device. ie. If we left these on, any changes on the
# server will append to the lists.
# Support for these lists have been commented out.
#
# August 23, 2006
# After many discussions, it has been decided to uncomment all commented
# fields.  This is an attempt to not produce any "regressions" coming from
# 10.1.2.3.2.
 
#Home
#telparamtype1=HOME
#Home 2
#telparamtype2=HOME
#Business Fax
#telparamtype3=FAX
#Mobile
#telparamtype4=CELL
#Business
#telparamtype5=WORK
#Business 2
#telparamtype6=WORK
 
 
#Home
#telparamtype7=X-SYNCMLREF1,HOME
#Home 2
#telparamtype8=X-SYNCMLREF2,HOME
#Business Fax
#telparamtype9=FAX,WORK
#Business
#telparamtype10=X-SYNCMLREF1,WORK
#Business 2
#telparamtype11=X-SYNCMLREF2,WORK
 
#Pager
#telparamtype12=PAGER
 
#Work Email
#emailparamtype1=WORK,INTERNET
#emailparamtype2=WORK,INTERNET,X-SYNCMLREF1
#emailparamtype3=WORK,INTERNET,X-SYNCMLREF2
 
#Home Email
#emailparamtype4=HOME,INTERNET
#emailparamtype5=HOME,INTERNET,X-SYNCMLREF1
#emailparamtype6=HOME,INTERNET,X-SYNCMLREF2
 
#The Remaining E-mail
#emailparamtype7=HOME,INTERNET,X-SYNCMLREF3
#emailparamtype8=WORK,INTERNET,X-SYNCMLREF3
 
 
 
 
 
 
 
[contact-mappings]
 
# The following is a list of all the supported mappings
# between OCFO and this device.
# The syntax is XXXparammapping=XXXparamtype,XXXparamtype
# where XXX is either adr,tel,url, or email.
# The first paramtype is associated with the server
# and the latter is the client.  ie. (server,client)
# The ordering of the mappings should match the reverse ordering
# as received by the device and the normal ordering as sent by
# the server. Ordering only matters when there are properties
# sharing the same paramters. Generally, there is some sort of
# logic to the ordering so that mappings may be applied uniquely.
# You can prepend to the mapping flags of either I,O,E, and/or D.
# eg. XXXparamapping=IE,XXXparamtype1,XXXparamtype1
# I=incoming, O=outgoing, E=expanded type parameter,
# and D=don't add deletes for missing mappings.
# Expanded type parameters means that TYPE=X;TYPE=Y
# is sent to the device instead of TYPE=X,Y.
# By default, not specifying I or O will force IO.
# E and D are off by default.
 
 
 
 
 
#adrparammapping1=adrparamtype1,adrparamtype1
#adrparammapping2=adrparamtype2,adrparamtype2
 
#emailparammapping1=I,emailparamtype1,emailparamtype1
#emailparammapping2=I,emailparamtype1,emailparamtype2
#emailparammapping3=I,emailparamtype1,emailparamtype3
#emailparammapping4=I,emailparamtype3,emailparamtype4
#emailparammapping5=I,emailparamtype3,emailparamtype5
#emailparammapping6=I,emailparamtype3,emailparamtype6
#emailparammapping7=O,emailparamtype1,emailparamtype2
#emailparammapping8=O,emailparamtype3,emailparamtype6
#emailparammapping9=I,emailparamtype2,emailparamtype7
#emailparammapping10=I,emailparamtype2,emailparamtype8
#emailparammapping11=O,emailparamtype2,emailparamtype8
 
#telparammapping1=O,telparamtype4,telparamtype2
#telparammapping2=O,telparamtype3,telparamtype1
#telparammapping3=O,telparamtype5,telparamtype3
#telparammapping4=IO,telparamtype6,telparamtype4
#telparammapping5=O,telparamtype10,telparamtype6
#telparammapping6=O,telparamtype9,telparamtype5
 
#telparammapping7=I,telparamtype4,telparamtype8
#telparammapping8=I,telparamtype3,telparamtype7
#telparammapping9=I,telparamtype5,telparamtype9
#telparammapping10=I,telparamtype9,telparamtype10
#telparammapping11=I,telparamtype10,telparamtype11
#telparammapping12=IO,telparamtype16,telparamtype12
 
#urlparammapping1=urlparamtype1,urlparamtype1