Oracle Mobile Data Sync

Task priority mappings

Devices differ in how they handle priority levels for tasks; for instance, Palm devices using the Synthesis SyncML client support priority levels one through five, while the Sony Ericsson T series of devices uses priority levels High, Normal and Low and the calendar server supports priority levels one through nine.

With all these different priority levels, further complicated by the use of different desktop clients, it is difficult to keep track of how priority levels are mapped to each other when synchronization occurs. The following tables document how task priorities are mapped from clients to the server, and vice versa.

Alarm behavior

Alarm settings on mobile devices are preserved. If you change an existing event's reminder settings on the server, the modification does not get propagated to your device the next time you synchronize, and vice versa.

Class mapping support

Devices that do not support the vCalendar or iCalendar CLASS property value of CONFIDENTIAL are supported as best as possible. For example, CONFIDENTIAL will be mapped to PRIVATE when an event is sent to a device that lacks this support, such as with Nokia, Ericsson and Sony Ericsson products. Also, CONFIDENTIAL events will remain confidential on the calendar server even when a device attempts to change them to PRIVATE.

Long summary and description support

Ericsson and Sony Ericsson devices now support 160 character event and task titles and the Nokia 9210, 9290 and 9500 devices support 200 character event and task titles. Ericsson and Sony Ericsson devices also support LOCATION and DESCRIPTION properties for events and, in the case of the T68i, tasks. There is a 32 character limit on the LOCATION field of all tested Ericsson and Sony Ericsson phones.

Working with tasks and events

Some devices allow you to separately specify whether or not you want to synchronize events and tasks. For example, to synchronize tasks and events on the Sony Ericsson T68i, select 8 - Connect , 4 - Synchronization, 3 - Options, 1 - Remote Settings, 2 - Applications, 2 - Calendar, then enter the following URIs:

    ./Calendar/Events
    ./Calendar/Tasks

The next time you synchronize with the server, both tasks and events will be synchronized. If you leave the field blank, neither tasks nor events will be synchronized.

Devices that do not allow you to synchronize events and tasks separately only have one Calendar URI field, in which you enter:

    ./Calendar

The Ericsson R520m, T39 and T68 do not support task synchronization; for these devices, you must enter:

    ./Calendar/Events

Events will be synchronized, but tasks will not.

Specifying date ranges

When you synchronize your device with Oracle Mobile Data Sync, events and tasks that are outside of the server-defined, device-specific, date range (for example, seven days in the past to 30 days ahead), are not sent to the device, by default. Accordingly, any events or tasks outside of this range that are synchronized to the server by the device are archived on the server and deleted from the device. Both of these behaviors can be overridden with device settings.

To override the server's date range with your device, append /dr(-x,y) to the Calendar URI on your device, with x being the number of days in the past, and y being the number of days in the future. For example:

• ./Calendar?/dr(-7,14): Synchronizes events and tasks seven days in the past to 14 days in the future.

• ./Calendar/Events?/dr(-30,60): Synchronizes events 30 days in the past to 60 days in the future.

• ./Calendar/Tasks?/dr(0,7): Synchronizes tasks from today to seven days in the future.

To control whether or not entries outside this range are removed from the device, append the text /del(x) to the Calendar URI on your device, with x being true or false. For example:

• ./Calendar/Tasks?/dr(-30,60)/del(false): Synchronizes tasks from 30 days in the past to 60 days in the future, but does not remove tasks outside this range from the device.

• ./Calendar/Events?/dr(-30,60)/del(true): Synchronizes events 30 days in the past to 60 days in the future, and removes events outside this range from the device.

Working with contact categories

Normally, to synchronize all contacts with the server, you must enter ./contacts into the appropriate URI field in your device. However, you may want to save space on your device by selecting specific categories to synchronize. While most devices do not actually support contact categories, it is possible to choose which categories you want to synchronize from the server to the device. To do this, simply append the category name or names to the URI; for example:

    ./contacts/business
    ./contacts/business+personal

All contacts in those categories on the server will be synchronized to your device.

If you specify categories to be synchronized, keep in mind the following the next time you synchronize with the server:

• For devices that do not support contact categories — which at this time includes all devices except the Windows Mobile with Synthesis SyncML — contacts you create on the device are stored on the server using the first category specified in the URI. For example, if ./contacts/business+personal is specified on the device, a new contact created on the device will be stored on the server in the category "business."

• For devices that do support contact categories — at this time, only the Windows Mobile with Synthesis SyncML — contacts in the categories specified in the URI are synchronized, while contacts in all other categories are stored on the server under the appropriate category, and removed from the device.

• The calendar server can store multiple categories for a contact; these will be maintained even if you make changes to the contact on your device (for example, if you change the contact's telephone number). The server will store the new information while maintaining its list of categories for the contact.

• If you change the categories to be synchronized, a full synchronization will occur. Also, any contacts previously synchronized between the device and the server that are not in the new list of categories will be deleted from the device (but maintained on the server).

Triggering a slow synchronization

Occasionally, you may want to do a slow synchronization after deleting or cleaning up data on your device, as described later in this document in Safely resetting data on your device. As it is not easy to trigger a slow synchronization on some devices, Oracle Mobile Data Sync is designed to recognize a "reset" parameter that you can enter into the Calendar URI of your device.

To trigger a slow synchronization, add the text /reset(true) to the URI for which you want to reset data. After you synchronize, make sure to set the parameter to false so that a slow synchronization does not occur every time you synchronize.

Some examples of use:

• ./Calendar?/reset(true): Forces a slow synchronization the next time you synchronize. All calendar data on the client will be refreshed.

• ./Calendar/Events?/reset(true): Forces a slow synchronization the next time you synchronize. All events on the client will be refreshed.

• ./Calendar/Tasks?/reset(true): Forces a slow synchronization the next time you synchronize. All tasks on the client will be refreshed.

• ./Contacts?/reset(true): Forces a slow synchronization the next time you synchronize. All contacts on the client will be refreshed.

  The Nokia 9500 Communicator has built-in support for slow synchronization.

  To perform a slow synchronization with the Nokia 9500 Communicator:

  1. Delete any duplicate or erroneous data from your Nokia device.

  2. Click Desk on the keypad.

  3. Open Tools, then Synchronization.

  4. Highlight the desired synchronization profile and click Menu on the keypad.

  5. Delete your calendar data.

  6. Select File, then select Synchronization, then Slow Sync.

  7. Click Continue. A normal two-way sync will automatically be executed during the next synchronization.

Setting a maximum message size

Devices synchronize data by breaking it up into pieces and transmitting these pieces to the server. The size of these pieces of data is determined by the device's default setting. Occasionally, phone carriers will halt synchronization if these pieces of data exceed their predetermined limits. To avoid this, you can set a custom limit, known as a "maximum message size," on pieces of information to synchronize. The device will break data up into manageable pieces that do not exceed this size limit.

To set the maximum message size, append the text /msgsize(x) to the Mobile Data Sync URL on the device, where x is the maximum message size in bytes.

The following table lists some default message sizes and suggested alternatives to avoid problems.

Overriding the maximum number of deletions

To safeguard your data on the server, there is a server-side default that limits the number of deletions that can be initiated by your device during one synchronization. However, you can override the server-side default.

To override the maximum number of deletions allowed by the server, append /maxdel(x) to the appropriate URI, where x is the maximum number of deletions you want to allow. Any other deletions will be blocked. For example:

• ./Calendar?/maxdel(5): Allows up to five event and task deletions coming from the client per synchronization session.

• ./Calendar?/maxdel(-1): Allows all event and task deletions coming from the client per synchronization session.

• ./Calendar/Events?/maxdel(5): Allows up to five event deletions coming from the client per synchronization session.

• ./Calendar/Tasks?/maxdel(5): Allows up to five task deletions coming from the client per synchronization session.

• ./Contacts?/maxdel(5): Allows up to five contact deletions coming from the client per synchronization session.

Deleted records that exceed this limit are archived on the server and deleted from the device. These records will only be synchronized back to the device if they are modified by another client, such as a desktop client or the Web client.

Accepting and declining invitations directly on your device

Your device uses several symbols to display the status of meetings. To change your status for a meeting, edit the meeting by changing the symbols listed below, then synchronize your device. Remember that once you decline a meeting and synchronize your device with the server, the declined meeting will be removed from your device.

[*]: This symbol may precede the ?, + and - symbols on your device and indicates a meeting you did not create. This symbol will not appear next to meetings you have created yourself.

[?]: This symbol indicates a meeting you have not accepted or declined.

[+]: This symbol indicates a meeting you have accepted.

[-]: This symbol indicates a meeting you have declined.

Synchronizing refused entries

By default, refused entries are not synchronized to devices. However, you may want to see refused entries on your device and have the option to attend an event that was previously declined. To do this, append the text /ref(x) to the Calendar URI on your device, where x is true or false. For example:

• ./Calendar?/ref(true): Synchronizes all events (including refused events) and tasks.

• ./Calendar?/dr(-7,14)/ref(true): Synchronizes all events (including refused events) and tasks seven days in the past and 14 days in the future.

• ./Calendar/Events?/ref(false): Synchronizes only accepted and unconfirmed events.

Customizing conflict resolution

By default, if an entry has been modified on both the server and the device, the server entry overwrites the device entry. To configure your device to overwrite an entry on the server in the case of a conflict, append the text /cr(x) to the appropriate URI on your device. Set x to 2 to have the entry on the device prevail, or set x to 1 to have the entry on the server prevail. For example:

• ./Calendar?/cr(2): Modified events or tasks on the device overwrite modified events or tasks on the server.

• ./Calendar/Events?/cr(1): Modified events on the server overwrite modified events on the device.

• ./Calendar/Tasks?/cr(2): Modified tasks on the device overwrite modified tasks on the server.

• ./Contacts?/cr(2): Modified contacts on the device overwrite modified contacts on the server.

Devices that support time change

All Windows Mobile and Blackberry devices

These devices fully support time change. If you travel to a different time zone, your device displays your events in that time zone and synchronizes data properly. You do not need to make any special configuration changes. Daylight Savings clock changes are supported.

Devices that do not support time change

All Nokia and Palm devices, Sony Ericsson devices that use Symbian OS (P800 and P900 series), Motorola A1000 and FOMA M1000

These devices do not support traveling across time zones. However, the following procedure can be used as a workaround:

1. Synchronize your device.

2. Delete your calendar data.

3. After traveling to the new time zone, verify that your device is set to the correct time.

4. Use an Oracle Calendar client to set your calendar account to the new time zone.

5. Follow the instructions in the Triggering a slow synchronization section to perform a full synchronization of your data. After synchronization, your events will be displayed in the new time zone.

These devices do support Daylight Savings clock changes.

Devices that partially support time change

Ericsson R520m, T39 and T68, Sony Ericsson T68i and T610/616/630, Siemens M55 and S55

These devices do not fully support time zone or Daylight Savings change. The workarounds for this are documented here, but they are not simple and should only be done if absolutely necessary. You must synchronize the device, delete all Calendar data from the device, then do a full synchronization in the new time zone, or after the clock change.

Use the appropriate workaround for your device, as described in the following procedures.

Workaround for Ericsson R520m, T39 and T68, Sony Ericsson T68i, T610/616/630

Follow this procedure to synchronize data correctly in a different time zone or after a Daylight Savings clock change. These steps may differ slightly from model to model. You must start this procedure before you travel or before the time change occurs.

1. Synchronize your device before you travel, or before a Daylight Savings clock change occurs.

2. From the Organizer menu on your device, select Calendar, then Advanced, then Delete all.

3. Select Yes to confirm. This will delete all Calendar data from your device and force a full synchronization the next time you synchronize.

4. After the Daylight Savings clock change has occurred, or after you have traveled to a different time zone, check that the time on the device is correct. If it is not, set the correct time.

5. If you are traveling, use an Oracle Calendar client to set your calendar account to the new time zone.

6. From the Settings menu on your device, select Time and Date, then select Advanced.

7. Set the following options:

   • Time Zone: Select the correct time zone for your location; for example:

     • Pacific time: GMT-8.00h

     • Eastern time: GMT-5.00h

     • Most of Europe: GMT+1.00h

   • Daylight-saving: For most parts of North America, this should be set to 1h summertime. This depends on how Daylight Savings is observed in your geographic area.

   • Auto time zone: Set this to Off.

8. Check once more that the time on the device is correct. If it is not, set the correct time.

9. Synchronize your device.

10. If you are traveling, repeat this procedure when it is time to return, or when you leave for another time zone.

Workaround for Siemens M55 and S55

Follow this procedure to synchronize data correctly in a different time zone or after a Daylight Savings clock change. These steps may differ slightly from model to model. You must start this procedure before you travel or before the time change occurs.

1. Synchronize your device.

2. On your device, select Menu, then Organizer, then Appointments.

3. Highlight an entry and select Options.

4. Select Delete all.

5. Select Yes to confirm. This will delete all appointments from your device.

6. Repeat steps 2 to 5, but select Tasks instead of Appointments. This will delete all tasks from your device.

7. If you are traveling, use an Oracle Calendar client to set your calendar account to the new time zone.

8. After the Daylight Savings clock change has occurred, or after you have traveled to a different time zone, select Menu on your device, then select Setup, Clock, and Time zones.

9. Set the appropriate option:

   • If you are traveling, choose the appropriate time zone and select Set.

   • If a Daylight Savings clock change has occurred, select your time zone, select Options, select DST, then select Change.

10. On your device, select Menu, select Extras, select Remote sync, then select Setup.

11. Select the account you are using, then select Options.

12. Select Change sett, then select Server sett.

13. Set Sync mode to Slow, then select Save. This means your device will do a slow (full) synchronization the next time you synchronize.

14. Synchronize the device.

15. If you are traveling, repeat this procedure when it is time to return, or when you leave for another time zone.

Devices that fully support resetting data

Ericsson R520m, T39 and T68, Sony Ericsson T68i and T610/616/630

It is easy to reset data on these devices. These steps may differ slightly from model to model.

1. From the Organizer menu on your device, select Calendar, then Advanced, then Delete all.

2. Select Yes to confirm. This will delete all Calendar data from your device and force a full synchronization the next time you synchronize.

3. Repeat steps 1 to 2 and select Phonebook to delete all contact information from the device. This also forces a full synchronization the next time you synchronize.

4. Synchronize your device. Data is synchronized from your account on the calendar server to your device.

Note: Data you delete from your device will not be deleted from your calendar account on the server when you synchronize.

Devices that do not support resetting data

All Nokia devices, Sony Ericsson (Motorola A1000, FOMA M1000 and P910i) devices.

Caution: Do not try to manually delete data and perform a manual slow synchronization with these devices. If you do, data you have deleted from the device will be deleted from your account on the calendar server.

If you absolutely must reset data on one of these devices, do the following:

1. Configure the device to force a slow synchronization with the server, as described in Triggering a slow synchronization.

2. Delete duplicate or incorrect data from your device.

3. Synchronize. A slow synchronization occurs, and your data is reset.

4. Re-configure the device so that it does not force another slow synchronization, as described in Triggering a slow synchronization.

Devices that require workarounds to reset data

Palm, Windows Mobile, Siemens M55 and S55, Sony Ericsson P series and M series.

You can reset the data on these devices, but you must do so carefully, using the instructions described in this section.

This section contains the following topics:

• Resetting data on Palm devices

• Resetting data on Windows Mobile devices

• Resetting data on Siemens devices

• Resetting data on Sony Ericsson P series and M series

Nokia

The following table summarizes known issues of Nokia devices. The word "Applies" indicates that an issue applies to the model listed in the corresponding column heading.

Ericsson and Sony Ericsson

The following table summarizes known issues of Ericsson and Sony Ericsson devices. The word "Applies" indicates that the issue applies to the model listed in the corresponding column heading.