| Oracle® Calendar Resource Kit, Release 2 (9.0.4.2) Part Number B10894-04 |
|
|
View PDF |
| Oracle® Calendar Resource Kit, Release 2 (9.0.4.2) Part Number B10894-04 |
|
|
View PDF |
Oracle Sync Server takes advantage of the SyncML protocol to deliver true remote synchronization of data with a wide range of SyncML-enabled devices. This alternative to the Desktop-to-PDA synchronization allows you the freedom to be anywhere while having the most up-to-the-second information.
Oracle Sync Server offers direct two-way synchronization with Oracle Calendar server over any standard Hypertext Transfer Protocol (HTTP) connection. This means that you have access to the calendar infrastructure from a variety of SyncML-compliant devices with Internet access. With Oracle Sync Server you are no longer tied to your desktop for synchronization.
The behavior of SyncML devices is largely dependent on the device model and the wireless carrier you are using. Because of this, many different situations can arise when synchronizing your device, and it is therefore important to understand as much as possible about your device and how it works with Oracle Sync Server. This chapter explains important information about the SyncML devices that Oracle supports.
This chapter contains the following topics:
This section contains the following topics:
The following SyncML-compliant devices are supported for use with Oracle Sync Server:
Nokia 3650, 6600, 6800, 6810, 6820, 7250, 7650, 92xx
Ericsson R520m, T39, T68
Sony Ericsson T68i, P800, P900 (with firmware R4A06), T610/T616, T630
Siemens M55, S55
This release provides support for version 2.1.0.x of the Synthesis SyncML clients used on Palm and PocketPC devices with Oracle Sync Server.
|
Note: Devices supported by the Synthesis SyncML clients are listed on Synthesis's Web site athttp://www.synthesis.ch. |
To certify Synthesis SyncML clients, Oracle tested the following devices:
PocketPC:
HP IPAQ H5550
Dell Axim X5 (PocketPC 2002 and 2003 versions)
Siemens SX56
Palm:
Sony Clie TG50
Palm Tungsten W
Palm Tungsten T3
This release also provides support for Blackberry devices used with Oracle Sync Server and Consilient's Consilient2 wireless solution.
Ideally, you should synchronize over secure (SSL) connections (for example, https://sync_server_host_address). Otherwise, you risk having your data intercepted whenever you synchronize. Of the devices supported by Oracle Sync Server, only the following support secure connections. If Oracle Sync Server is configured to accept secure connections and you are using one of these devices, you should synchronize using a secure connection.
Nokia 3650, 6600, 92xx
All Ericsson devices
All Sony Ericsson devices
All PocketPC devices with version 2.1.0.1 PRO of the Synthesis SyncML client
Palm Tungsten T3 devices with version 2.1.0.3 PRO of the Synthesis SyncML client
This section describes common configuration issues for devices used with Oracle Sync Server. Please see the Customizing synchronization, Traveling across time zones and working with Daylight Savings, Safely resetting data on your device and Device-specific considerations sections for other behaviors you should be aware of.
This section contains the following topics:
Before you try to synchronize your device with Oracle Sync Server, make sure that you have:
The necessary software to connect to a SyncML server: Your device may already include SyncML software, or you may have to install it from the manufacture's CD or by downloading it from the Internet. For example, on the Nokia 3650, 7650 and 92xx, you may need to download and install an appropriate version of the software, "Remote Sync."
An appropriate network connection set up on your device: Depending on your organization, you may be able to connect to the Sync Server through, for example, a GPRS Internet connection, or you may have to dial in to a corporate intranet behind a firewall. You may need to configure your SyncML software to use the right connection.
Your sign-in information: You will need your Calendar user name, password and Sync Server URL and port number. You must configure your device's SyncML software with this information in order to sign in to your account.
|
Note: If Oracle Sync Server is configured to accept secure connections and you are using a device that supports this, you should synchronize using a secure (HTTPS) connection. For more information, see Devices that support secure connections. |
The appropriate patch and firmware for Sony Ericsson P800 and P900 devices: Limitations with the Sony Ericsson P800 and P900 can result in discrepancies between the Calendar server and your device, including meetings that are shifted, duplicated, or incorrectly reported as deleted. To prevent this from happening, make sure you have the appropriate firmware installed on your Sony Ericsson P900 device, and the proper patch installed on your P800 or P900 device, before you set up your device for use with Oracle Sync Server.
For instructions on upgrading your firmware and installing the patch, see the Sony Ericsson P800 / P900 section of Configuring devices for Oracle Sync Server.
For more device configuration information, see the Configuring devices for Oracle Sync Server section or consult the documentation included with your device.
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. Meanwhile, 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.
Table 5-1 Task priority mappings from clients to the Calendar server
| Client / device | Device priority levels | Mapped values to store on Calendar server |
|---|---|---|
| Oracle Connector for Outlook | High / Normal / Low | 1 / 5 / 9 |
| Oracle Calendar desktop clients and Web client | 1 through 9 | 1 through 9 |
| Nokia | High / Normal / Low | 1 / 5 / 9 |
| Siemens | 1 through 5 | 1 through 5 |
| Sony Ericsson T series | High / Normal / Low | 1 / 5 / 9 |
| Sony Ericsson P series | 1 through 9 | 1 through 9 |
| Synthesis client for Palm | 1 through 5 | 1 through 5 |
| Synthesis client for PocketPC | High / Normal / Low | 1 / 5 / 9 |
Table 5-2 Task priority mappings from the Calendar server to clients
| Client / device | Server priority levels | Mapped values to store on device |
|---|---|---|
| Oracle Connector for Outlook | 1 - 3 / 4 - 6 / 7 - 9 | High / Normal / Low |
| Oracle Calendar desktop clients and Web client | 1 through 9 | 1 through 9 |
| Nokia | 1 - 3 / 4 - 6 / 7 - 9 | High / Normal / Low |
| Siemens | 1 - 5 / 6 - 9 | 1 - 5 / 5 |
| Sony Ericsson T series | 1 - 3 / 4 - 6 / 7 - 9 | High / Normal / Low |
| Sony Ericsson P series | 1 through 9 | 1 through 9 |
| Synthesis client for Palm | 1 - 5 / 6 - 9 | 1 - 5 / 5 |
| Synthesis client for PocketPC | 1 - 3 / 4 - 6 / 7 - 9 | High / Normal / Low |
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.
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.
Ericsson, Sony Ericsson, Nokia 9210 and 9290 devices now support 160 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.
This section describes how to customize the way your device synchronizes information. Because SyncML is a new, developing technology, there is not as of yet a "user-friendly," standardized graphical interface for making changes like this on your device. Unless otherwise specified, make these customizations by appending ? to the appropriate URL or URI field in your device, followed by the parameters or settings you want to add. If you want to add multiple parameters to these fields, the ? need only appear once, followed by all parameters collectively.
|
Note: Whenever you make changes to any URI field on a device, a slow synchronization occurs the next time you synchronize. |
This section contains the following topics:
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
Devices that do not allow you to synchronize events and tasks separately only have one Calendar URI field, in which you simply enter:
./Calendar
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.
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.
When you synchronize your device with Oracle Sync Server, 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.
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.
|
Notes:
|
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 PocketPC 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 PocketPC 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).
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. Since it is not easy to trigger a slow synchronization on some devices, Oracle Sync Server 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.
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 Sync Server URL on the device, where x is the maximum message size in bytes. For example:
http://sync_server_host_address?/msgsize(4000)
The following table lists some default message sizes and suggested alternatives to avoid problems.
If a large number of data has been deleted from your device, and you do not want this data to be deleted from the server when you synchronize, you can set a limit at which to safeguard your server data. This is particularly useful for the Sony Ericsson P900, which sometimes flags records as deleted even though they are not. In fact, as a general rule for all devices, it is a good idea to limit the number of deletions on the server that can be initiated by the device during one synchronization.
To set the maximum number of deletions, append /maxdel(x) to the appropriate URI, where x is the maximum number of deletes you want to allow. Any other deletes 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.
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.
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.
./Calendar/Contacts?/cr(2): Modified contacts on the device overwrite modified contacts on the server.
Synchronizing mobile devices across time zones can be a complex and tricky process. This section explains important information on what to do, and not do, with your device when traveling across time zones or when a Daylight Savings clock change occurs.
This section includes the following topics:
All PocketPC 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.
All Nokia and Palm devices, Sony Ericsson P800 and P900
These devices do not support traveling across time zones. When you travel, you must view your events in your usual time zone. For example, if you live in New York and travel to Paris, an event scheduled for 3 p.m. New York time still appears as occurring at 3 p.m., even though in Paris it is 9 p.m. when the event occurs.
When traveling, do not attempt to change the time zone on these devices or on the Calendar server. You must keep both the device and server set to your regular time zone in order to synchronize. If you change the time zone on your device or on the server, do not synchronize.
These devices do support Daylight Savings clock changes.
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 and T610/616
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.
Synchronize your device before you travel, or before a Daylight Savings clock change occurs.
From the Organizer menu on your device, select Calendar, select Advanced, then select Delete all.
Select Yes to confirm. This will delete all Calendar data from your device and force a full synchronization the next time you synchronize.
After the Daylight Savings clock change has occurred, or after you have travelled to a different time zone, check that the time on the device is correct. If it is not, set the correct time.
If you are traveling, use an Oracle Calendar client to set your Calendar account to the new time zone.
From the Settings menu on your device, select Time and Date, then select Advanced.
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: You must set this to Off.
Check once more that the time on the device is correct. If it is not, set the correct time.
Synchronize your device. A full synchronization occurs. Your events are set to the correct time.
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.
Synchronize your device.
On your device, select Menu, select Organizer, then select Appointments.
Highlight an entry and select Options.
Select Delete all.
Select Yes to confirm. This will delete all appointments from your device.
Repeat steps 2 to 5, but select Tasks instead of Appointments. This will delete all tasks from your device.
If you are traveling, use an Oracle Calendar client to set your Calendar account to the new time zone.
After the Daylight Savings clock change has occurred, or after you have travelled to a different time zone, select Menu on your device, then select Setup, Clock, and Time zones.
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.
On your device, select Menu, select Extras, select Remote sync, then select Setup.
Select the account you are using, then select Options.
Select Change sett, then select Server sett.
Set Sync mode to Slow, then select Save. This means your device will do a slow (full) synchronization the next time you synchronize.
Synchronize the device.
If you are traveling, repeat this procedure when it is time to return, or when you leave for another time zone.
Occasionally, data on your device may become lost, duplicated, or corrupt. This can happen if a slow sync is interrupted, or if you have traveled and returned from a different time zone without following the instructions described in Traveling across time zones and working with Daylight Savings. To return your device to a "clean" state, you must carry out two basic steps:
If there is extraneous or incorrect data on your device, you must delete it; in some cases, it is easier just to clear all data from the device. If, however, you are simply missing some information, deleting data from the device is not necessary.
Perform a "slow" synchronization with the server. A slow synchronization differs from a regular synchronization in that, instead of synchronizing only those records marked as changed, all records are synchronized. This returns device data to a "clean" state.
While the preceding steps might seem simple at first glance, they can actually be quite tricky. If they are not done properly, severe problems — such as data loss — can occur, so it is very important to follow the instructions described in this section, based on the type of device you use.
This section includes the following topics:
Ericsson R520m, T39 and T68, Sony Ericsson T68i and T610/616
It is easy to reset data on these devices. These steps may differ slightly from model to model.
From the Organizer menu on your device, select Calendar, select Advanced, then select Delete all.
Select Yes to confirm. This will delete all Calendar data from your device and force a full synchronization the next time you synchronize.
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.
|
Note: Data you delete from your device will not be deleted from your Calendar account on the server when you synchronize. |
Synchronize your device. A slow synchronization occurs. Data is synchronized from your account on the Calendar server to your device.
All Nokia devices, Sony Ericsson P800 and P900
|
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:
Configure the device to force a slow synchronization with the server, as described in Triggering a slow synchronization.
Delete duplicate or incorrect data from your device.
Synchronize. A slow synchronization occurs, and your data is reset.
Re-configure the device so that it does not force another slow synchronization, as described in Triggering a slow synchronization.
Palm, PocketPC, Siemens M55 and S55
You can reset the data on these devices, but you must do so very carefully, using the instructions described in this section.
This section contains the following topics:
This section describes how to delete all events from Palm devices, then do a slow synchronization.
|
Note: If your device is simply missing information, you do not need to delete data. Proceed to the steps describing how to do a slow synchronization. |
|
Caution: If you delete data from the device and then do a regular synchronization instead of a slow synchronization, data will be deleted from your Calendar account on the server. You must be sure to do a slow synchronization after deleting data on your device, as described in this section. |
Delete all events from a Palm device as follows.
Go to your Palm "Home."
Select All to view all applications, then select Prefs.
Under Set Date, change the date to a date far in the future.
Open the Date Book.
Open the menu and select Record, then select Purge.
Under Delete events older than, select 1 Week.
Clear the Save archive copy on PC check box.
Select OK.
Repeat steps 1 to 3, setting the date back to today's date.
|
Note: If you have incorrect task or contact entries, you must delete them manually. |
To do a slow synchronization with a Palm device:
Run the Synthesis SyncML Client.
Go to your Palm "Home."
Select All to view all applications, then select SyncML.
Open the menu and select Options, then select Profile Settings.
Select the uppermost More button.
Next to Contacts, Events and Tasks, select Slow from the drop-down menu.
Synchronize your device. A slow synchronization occurs. Data is synchronized from your account on the Calendar server to your device.
To reset PocketPC devices, you must manually delete all incorrect data from the device, then do a slow synchronization.
|
Note: If your device is simply missing information, you do not need to delete data. Just perform a slow synchronization, as described in the following procedure. |
|
Caution: If you delete data from the device and then do a regular synchronization instead of a slow synchronization, data will be deleted from your Calendar account on the server. You must be sure to do a slow synchronization after deleting data on your device, as described in this section. |
After you have manually deleted incorrect data from your PocketPC, do a slow synchronization as follows:
Run the Synthesis SyncML Client.
Select Extras, then select Profile Settings.
Select the Organizer tab.
Select Slow for the Sync Mode for Contacts, Events, and Tasks.
Synchronize your device. A slow synchronization occurs. Data is synchronized from your account on the Calendar server to your device.
Follow this procedure to reset data on Siemens M55 and S55 devices.
On your device, select Menu, select Organizer, then select Appointments.
Highlight an entry and select Options.
Select Delete all.
Select Yes to confirm. This will delete all appointments from your device.
Repeat steps 2 to 5 for Tasks and Contacts. This will delete all tasks and contacts from your device.
On your device, select Menu, select Extras, select Remote sync, then select Setup.
Select the account you are using, then select Options.
Select Change sett, then select Server sett.
Set Sync mode to Slow, then select Save. This means your device will do a slow synchronization the next time you synchronize.
|
Caution: If you delete data from the device and then do a regular synchronization instead of a slow synchronization, data will be deleted from your Calendar account on the server. You must be sure to configure your device to do a slow synchronization, as described in the preceding step. |
Synchronize the device.
This section describes issues encountered by Oracle Sync Server due to the SyncML behavior of the following devices:
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.
Table 5-4 Nokia SyncML Behavior Issues
| Issue | 3650 | 6600 | 6800 / 6810 / 6820 | 7250 | 7650 | 92xx |
|---|---|---|---|---|---|---|
| Nokia devices do not support traveling across time zones. For details, see Devices that do not support time change. | Applies | Applies | Applies | Applies | Applies | Applies |
| Do not try to manually delete data and perform a manual slow synchronization with these devices. If you must reset data on one of these devices, contact your Sync Server administrator, as described in Safely resetting data on your device. | Applies | Applies | Applies | Applies | Applies | Applies |
| Some Nokia devices do not support SSL (HTTPS) connections. These devices therefore cannot be used with Oracle Sync Server if it is set up to only accept SSL connections. | Does not apply | Does not apply | Applies | Applies | Applies | Does not apply |
| The SyncML client always assigns a due date for tasks. When tasks with no due date on the server are synchronized to the device, they will be given the current date as the due date. | Applies | Applies | Does not apply | Does not apply | Does not apply | Does not apply |
Tasks created using the Oracle Calendar desktop client may not synchronize with the phone device. Phones that synchronize tasks and events using the same phone database MUST use ./Calendar as the server URI. However, phones that synchronize them separately MUST use ./Calendar/Events and ./Calendar/Tasks as the respective URIs for the device's events and tasks databases. |
Applies | Applies | Does not apply | Does not apply | Does not apply | Does not apply |
| Changes to an entry's Access Level on the server are not synchronized to the device. However, a new entry's Access Level will be correctly synchronized from the server to the device the first time. | Applies | Does not apply | Does not apply | Does not apply | Does not apply | Applies |
| Business and Home addresses cannot be synchronized from the Oracle Calendar desktop client to the phone device. | Applies | Does not apply | Does not apply | Does not apply | Does not apply | Applies |
| E-mail addresses synchronized from the server to the device get reversed; that is, E-mail address 1 becomes E-mail Address 2, and vice versa. | Applies | Applies | Does not apply | Does not apply | Does not apply | Applies |
| The "completed" property for tasks is not supported. Tasks marked as completed on the server cannot be marked as completed on the device. | Applies | Does not apply | Does not apply | Does not apply | Applies | Applies |
| Modifying a "BDAY" and then synchronizing causes device failure. | Does not apply | Does not apply | Applies | Applies | Does not apply | Does not apply |
Unable to synchronize with the Nokia 9210 and 9290 devices when KeepAlive is set to ON in in httpd.conf or apache.conf. (This is the default Collaboration Suite installation value.) To solve this problem, turn KeepAlive off, or upgrade to the 9210i RemoteSync client. This upgrade can be done on either device. To download the upgrade, go to http://www.nokia.com and open the product page for the 9210i. Open the Software page, select More Software, and look for "SyncML." |
Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Applies |
| After synchronizing your Address Book with the Nokia 9290 phone device, invalid characters are inserted in the Company and Department fields. | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Applies |
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.
Table 5-5 Ericsson and Sony Ericsson SyncML Behavior Issues
| Issue | R520m | T39 | T68 | T68i | P800 | P900 | T610 / T616 / T630 |
|---|---|---|---|---|---|---|---|
| You must install firmware R4A06 or later (for example, R4B03) before you can use the P900 with Oracle Sync Server. For details, see Updating firmware (P900 devices only). | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Applies | Does not apply |
| These devices do not fully support time change due to travel or Daylight Savings. For details, see Devices that partially support time change. | Applies | Applies | Applies | Applies | Does not apply | Does not apply | Applies |
| These devices do not support traveling across time zones. For details, see Devices that do not support time change. | Does not apply | Does not apply | Does not apply | Does not apply | Applies | Applies | Does not apply |
| Do not try to manually delete data and perform a manual slow synchronization with these devices. If you must reset data on one of these devices, carefully follow the instructions described in Triggering a slow synchronization. | Does not apply | Does not apply | Does not apply | Does not apply | Applies | Applies | Does not apply |
Missing resource names: When the attendeesindetails parameter on the server is set to "short," resource names and statuses in event details are not synchronized to a device. This is because truncated resource names are not meaningful to users. Resources are only added to event details when attendeesindetails is set to full. |
Applies | Applies | Applies | Applies | Does not apply | Does not apply | Applies |
| Missing dash in phone number: The device does not store formatted phone numbers. All non-numeric characters other than "#" are removed when phone numbers are stored on the device. | Applies | Applies | Applies | Applies | Does not apply | Does not apply | Applies |
| Missing or modified e-mail addresses: The device can store one e-mail address for a contact, while the server can store two. If a contact's e-mail address is modified on the device and synchronized to the server, it is possible that the wrong address on the server will be updated. This is because there is no way at this time for the server to detect which address is supposed to be updated. | Applies | Applies | Applies | Applies | Does not apply | Does not apply | Applies |
| Missing organization field: The device can store one organization field for a contact, while the server can store two. If a contact's organization field is modified on the device and synchronized to the server, the information in both server fields is discarded in favor of the field synchronized from the device. | Applies | Applies | Applies | Applies | Does not apply | Does not apply | Applies |
| Contact's full name becomes a last name: The correct way to enter contact names on the device is "Lastname, Firstname". Names entered on, or synchronized to, the device without a comma will be stored on the device as last names only. | Applies | Applies | Applies | Applies | Does not apply | Does not apply | Applies |
| The "completed" property for tasks is not supported. Tasks marked as completed on the server cannot be marked as completed on the device. | Does not apply | Does not apply | Does not apply | Applies | Does not apply | Does not apply | Does not apply |
| Task synchronization is not supported. | Applies | Applies | Applies | Does not apply | Does not apply | Does not apply | Does not apply |
The Ericsson r520m has a limit of 150 characters in its event details field. Attendee information that exceeds 150 characters is not added to the details field. It is best to use the default server parameter of AddAttendeesInDetails = short with this device. |
Applies | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply |
| When you create an untimed event using the device, the Daylight Savings time change can cause it to be displayed as a Meeting with a duration of 1 minute on the Oracle Calendar desktop client. | Applies | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply |
| When a contact's e-mail address is modified using the phone device and contains special characters, it appears to be corrupt on the Oracle Calendar desktop client. This occurs because the phone device does not return the EMAIL vcard property in the appropriate format. | Does not apply | Does not apply | Does not apply | Applies | Does not apply | Does not apply | Does not apply |
The following are known issues of the SyncML software on Siemens M55 and S55 devices.
Siemens devices do not support the use of SyncML through SSL (HTTPS) connections. Siemens devices therefore cannot be used with Oracle Sync Server if it is set up to only accept SSL connections.
These devices do not fully support time change due to travel or Daylight Savings. For details, see Devices that partially support time change.
These devices do not fully support resetting data using slow synchronization. For details, see Devices that require workarounds to reset data.
Memos created on the device synchronize as Daily Notes on the server. (Other phone devices synchronize Memos as Day Events.)
Yearly recurring events created on the phone are not synchronized to the server.
Contact categories are not synchronized.
Home fax numbers are synchronized to the device as home phone numbers.
The following are known issues of devices using Synthesis SyncML clients.
Only PocketPC devices with version 2.1.0.1 PRO of the Synthesis SyncML client support secure (SSL) connections. All Palm devices, and any devices using the standard version of the Synthesis SyncML client, do not support secure connections.
Palm devices do not support traveling across time zones. For details, see Devices that do not support time change.
These devices do not fully support resetting data using slow synchronization. For details, see Devices that require workarounds to reset data.
Categories do not synchronize from or to Palm devices.
Contact addresses synchronize from the server to Palm devices, but not from Palm devices to the server.
Fax numbers synchronize from the server to Palm devices as "Other", and not at all from Palm devices to the server.
Some new fields supported by Palm devices and Oracle Sync Server are not yet supported by Synthesis and do not get synchronized. Specifically, "Home Address," "Web Site," and "Birthday" are not synchronized.
Synchronization of monthly and yearly recurring events is not supported.
E-mail addresses and phone numbers synchronized to PocketPC devices may get reversed; for example, E-mail address 1 may become E-mail address 2, Phone number 1 may become Phone number 2, and vice versa.
This section contains instructions on how to configure the following SyncML clients:
The following sections describe the steps for configuring and synchronizing your Nokia 3650 or 7650 device.
Press the Menu button for the main menu.
Select the RemoteSync icon, press Options and select Open.
Select Options, then select New Sync Profile. If the Copy Values From dialog box appears, select No.
Enter the following details:
Profile Name: My_Profile_Name
Bearer type: Internet
Access point: [select a valid Internet Access Point]
Host Address
Port: 8090
Username
Password
Calendar: Yes
Calendar File: c:\System\Data\Calendar
Remote Calendar: ./Calendar
Contacts: Yes
Contacts File: c:\System\Data\Contacts.cdb
Remote Contacts: ./Contacts
HTTP authentication: No
HTTP username: <leave blank>
HTTP password: <leave blank>
Press the Menu button for the main menu.
Select the RemoteSync icon, press Options and select Open.
Select My_Profile_Name from the profile list.
Press Options, then select Sync to begin the synchronization.
|
Note: Nokia devices do not support traveling across time zones. For details, see Devices that do not support time change. |
The following sections describe the steps for configuring and synchronizing your Nokia 6600 device.
Press the Menu button for the main menu.
Select the Connect icon.
Select the Sync icon.
Select the Options menu item and select New Sync Profile.
Enter the following details in the first tab:
Sync profile name
Access point
Host address: http://calsync.oracle.com/syncml
Port: 80
User name
Password
Data to be synchronized:
Press Select.
Select the Contacts menu item and press Mark (if it is already marked, the button will be called Unmark and nothing needs to be done).
Select the Calendar menu item and press Mark.
Press Done.
Enter the following details in the second tab:
Select Contacts
Click Yes
Remote database: ./Contacts
Synchronization Type: Normal
Click Back.
Select Calendar.
Click Yes.
Remote database: ./Calendar
Synchronization Type: Normal
Click Back.
Click Back.
Press the Menu button for the main menu.
Select the Connect. icon.
Select the Sync icon.
Select the Options menu item and select Synchronize.
|
Note: Nokia devices do not support traveling across time zones. For details, see Devices that do not support time change. |
The following section describes the steps for configuring and synchronizing your Nokia 6800 or 7250 device.
Press the Menu button for the main menu.
Select the Extras icon (Connectivity on the 6800) and press Select.
Select the Synchronize menu item and press Select.
Select the Settings menu item and press Select.
The Nokia 7250 can have up to four different profiles stored for synchronization. You can change which of the four profiles is active by selecting the Active Internet sync. Settings menu item and pressing the Select button. After choosing a profile, select the Edit active Internet sync settings menu item and press the Select button.
Enter the following details:
Settings Name: My_Profile_Name
Data to be synchronized:
Press Select.
Select the Phone book menu item and press Mark (if it is already marked, the button will be called Unmark and nothing needs to be done).
Select the Calendar menu item and press Mark.
Press Done.
When the Save Changes? dialog box appears, press Yes.
Database address:
Press Select.
Select the Phone book database menu item and press Select.
Enter the following information: ./Contacts
Press OK.
Select the Calendar database menu item and press Select.
Enter the following information: ./Calendar
Press OK.
Press Back.
Username:
Password:
Synchronization server:
Press Back when all of the settings have been made.
Press the Menu button for the main menu.
Select the Extras icon and press Select.
Select the Synchronize menu item and press Select.
Select the Synchronize menu item (there should be both Synchronize and Settings menu options from this menu) and press Select.
When the Synchronize selected data dialog box appears, press OK to begin synchronizing.
|
Notes:
|
The following sections describe the steps for configuring and synchronizing your Nokia 6810 or 6820 device.
Press the Menu button for the main menu.
Select the Organizer icon and press Select.
Select the Synchronization menu item and press Select.
Select the Settings menu item and press Select.
The Nokia 6820 can have up to 10 different profiles stored for synchronization. You can change which of the 10 profiles is active by selecting the Active Internet sync. Settings menu item and pressing the Select button. After choosing a profile, select the Custom. active Internet sync settings menu item and press the Select button.
Enter the following details:
Settings Name: My_Settings_Name
Data to be synchronized:
Press Select
Select the Contacts menu item and press Mark (if it is already marked, the button will be called Unmark and nothing needs to be done).
Select the Calendar menu item and press Mark.
Press Done.
Database address:
Press Select.
Select the Contacts database menu item and press Select.
Enter the following information: ./Contacts
Press OK.
Select the Calendar database menu item and press Select.
Enter the following information: ./Calendar
Press OK.
Press Back.
User name:
Password:
Synchronization server: http://calsync.oracle.com/syncml
Connection Settings
Press Back when all of the settings have been made.
Press the Menu button for the main menu.
Select the Organizer icon and press Select.
Select the Synchronization menu item and press Select.
Select the Synchronize menu item (there should be both Synchronize and Settings menu options in this menu) and press Select.
When the Synchronize selected data dialog appears, press OK to begin synchronizing.
|
Note: Nokia devices do not support traveling across time zones. For details, see Devices that do not support time change. |
The SyncML client is called RemoteSync and is located in the Extras folder.
Download RemoteSync1.10_9210dev.sis (Remote Synchronization Software) to your desktop.
Double-click RemoteSync1.10_9210dev.sis to install it on the device.
Press the Extras key.
Select RemoteSync.
Select Profile settings.
Select New to create Synchronization profiles.
Select the General tab in Sync profile settings and enter the following details:
Default profile: Yes
Profile Name: My_Profile_Name
Use: Internet
Internet access: PPP
Host address:
Port:
Username:
Password:
HTTP authentication: No
Select the Data tab in Sync profile settings and enter the following:
Calendar: Yes
Select Calendar.
Select Settings.
For Calendar synchronization settings, enter the following details:
Calendar file: C:\System\Data\Calendar
Remote calendar: ./Calendar/Events
Select Close.
For Contact synchronization settings, enter the following details:
Contacts: Yes
Remote Contacts: ./Contacts
Click Close.
Press the Extras button on the device.
Select the icon labeled RemoteSync and press Open.
Press Sync to synchronize with the sync server.
|
Note: Nokia devices do not support traveling across time zones. For details, see Devices that do not support time change. |
The following sections describe the steps for configuring and synchronizing your Siemens M55 or S55 device.
|
Note: Siemens devices do not support the use of SyncML through SSL (HTTPS) connections. Siemens devices therefore cannot be used with Oracle Sync Server if it is set up to only accept SSL connections. |
Press the Menu button for the main menu.
Select the Extras icon and press the Select button.
Select the Remote sync. menu item and press the Select button.
Press the Setup button.
The Siemens M55/S55 can have up to five different profiles stored for synchronization. You can change which of the five profiles is active by selecting the profile and pressing the Activate button. After choosing a profile, press the Options button.
Select the Change sett. menu option and press the Select button.
Select the Server sett. menu option and press the Select button.
Enter the following details:
Sync mode: Slow (Note that subsequent synchronization sessions will automatically use the Fast Sync mode.)
Provider:
Homepage:
Port:
Login Name:
Password:
Calendar path: ./Calendar/Events
Contacts path: ./Contacts
Task Path: ./Calendar/Tasks
HTTP Authent: No
Press the Save button.
Make sure that Calendar, Contacts and Tasks have check marks next to them. Use the Change button to update these options.
Press the Menu button for the main menu.
Select the Extras icon and press the Select button.
Select the Remote sync. menu item and press the Select button.
Press the Start button to begin synchronization.
|
Notes:
|
The following sections describe the steps for configuring and synchronizing your Sony Ericsson T39m device.
From the main menu, select Extras and press Yes.
Select Synchronization and press Yes.
Select Server settings and press Yes.
Select WAP profile and press Yes.
Select Remote login and press Yes.
Select WAP profile and press Yes.
Select Select, press Yes and select the appropriate WAP profile to connect to the sync server.
Press No once to return to the Remote Login screen.
Select Sync Server and press Yes.
Enter your calendar server user name and password.
Enter the host URL.
Select Save? and press Yes when finished.
Press No once to return to the Remote Settings screen.
Select Applications and press Yes.
Select Phone book and press Yes.
Enter ./Contacts in the Database: field.
Leave the User ID and PWD fields blank and select Save? and press Yes.
Select Calendar and press Yes.
Select Appointments and press Yes.
Enter ./Calendar/Events in the Database field.
Leave the User ID and PWD fields blank and select Save? and press Yes.
Select Tasks and press Yes.
Enter ./Calendar/Tasks in the Database field.
Leave the User ID and PWD fields blank and select Save? and press Yes.
Press No until you have returned to the main menu. The synchronization client is now configured and ready for use.
Press No four times to return to the Synchronization menu.
Select RemoteSync and press Yes.
Select Applications and press Yes.
To toggle a selection, select either Phone book or Calendar and press the * (asterisk) key to enable or disable either option.
Press No. If you have made changes, the Changes made. Save? dialog box will appear. Press Yes to save the changes.
Press No until you have returned to the main menu. The synchronization client is now configured and ready for use.
|
Notes:
|
The following sections describe how to configure and synchronize your Sony Ericsson P800 or P900 device. This section contains the following topics:
The Sony Ericsson P900 must have firmware R4A06 or later (for example, R4B03) installed to work with Oracle Sync Server.
To check which firmware version you have:
Click Applications in the top right corner of the device screen.
On the P800, select View; on the P900, select Edit.
Select System Information.
Use the arrows to browse to Organiser and see the numbers below it. The firmware version is the second number; for example:
Organiser: CXC162021 R1AO5
(R1A05 is the firmware version.)
If your firmware is not up to date, browse to the CDA version and write it down. You will need it when you upgrade your firmware, as described in the next procedure.
If the device does not have up-to-date firmware, you must upgrade it as follows:
Open a browser on your computer and go to:
http://www.sonyericsson.com/updateservice/P900/frameset.htm
Click Get started now.
Select Manual verification mode (recommended) and click Next.
Enter your CDA version and click Next.
Click Next.
Check each requirements point and then click Next.
Click Yes on the "Backup or synchronize your device" page.
Select I want to make a backup.
|
Note: If you do not perform a backup, you will lose any applications you have installed (such as the time zone patch) and all data (including GPRS and Sync Server settings). Even by performing a backup, you will still lose some information, such as voice commands. The Sony Ericsson Web page contains more information on what data will be lost. |
These devices require a patch to avoid time offset problems. Without this patch, event times may be incorrectly shifted whenever you synchronize. Installing this patch ensures that event times in your device match event times in your calendar. The "Sony Ericsson P800 and P900 SyncML Client Patch" is available from http://otn.oracle.com on the Client Download page. Install it as you would other device software, using the Sony Ericsson CD that came with your device. For the P900, make sure you have the proper firmware version installed before installing this patch.
Press the Menu button for the main menu.
Select the RemoteSync application.
Select the Preferences option from the Edit menu.
Enter the following details:
Server Address:
Username:
Password:
Press Done.
Select the Calendar item under Sync Task and enter the following information:
Enable task (this item should have a check mark next to it)
Task Name: Calendar
Server database: ./Calendar
Press Done.
Select the Contacts item under Sync Task and enter the following information:
Enable task (this item should have a check mark next to it)
Task Name: Contacts
Server database: ./Contacts
Click Done.
Press the Menu button for the main menu.
Select the RemoteSync application.
Press the Sync button in the lower left hand corner.
|
Notes:
|
The following sections describe the steps for configuring and synchronizing your Sony Ericsson T68 or T68i device.
From the main menu, select Connect and press Yes.
Select Synchronization and press Yes.
Select Options and press Yes.
Select Remote Settings and press Yes.
Select Remote login and press Yes.
Select WAP profile and press Yes.
Select Select, press Yes and select the appropriate WAP profile to connect to the sync server.
Press No once to return to the Remote Login screen.
Select Sync Server and press Yes.
Enter your calendar server user name and password.
Enter the host URL.
Select Save? and press Yes.
Press No twice to return to the Remote Settings screen.
Select Applications and press Yes.
Select Phone book and press Yes.
Enter ./Contacts in the Database: field.
Leave the User ID and PWD fields blank and select Save? and press Yes.
Select Calendar and press Yes.
Select Appointments and press Yes.
Enter ./Calendar/Events in the Database field.
Leave the User ID and PWD fields blank and select Save? and press Yes.
Select Tasks and press Yes.
Enter ./Calendar/Tasks in the Database field.
Leave the User ID and PWD fields blank and select Save? and press Yes.
Press No four times to return to the Synchronization menu.
Select RemoteSync and press Yes.
Select Applications and press Yes.
To toggle a selection, select either Phone book or Calendar and press the * (asterisk) key to enable or disable either option.
Press No. If you have made changes, the Changes made. Save? dialog box will appear. Press Yes to save the changes.
Press No until you have returned to the main menu. The synchronization client is now configured and ready for use.
|
Notes:
|
The following sections describe the steps for configuring and synchronizing your Sony Ericsson T610, T616 or T630 device.
From the main menu, select Connect (Connectivity on the T630) and press Select.
Select Synchronization and press Select.
Select Options and press Select.
Select Remote Settings and press Select.
Select Remote login and press Select.
Select WAP profile and press Select.
Select the Select menu option, press Select and select the appropriate WAP profile to connect to the Sync Server.
Press the Return key (return arrow symbol) once to return to the Remote Login screen.
Select Sync Server and press Select.
Enter your calendar server user name and SSO password.
Enter http://calsync.oracle.com/syncml as the URL.
Press Select to save the options and return to the Remote Login screen.
Press the Return key (return arrow symbol) once to return to the Remote Settings screen.
Select Applications and press Select.
Select Phone book and press Select.
Enter ./Contacts in the Database: field.
Leave the user id and pwd fields blank and press Save to return to the Applications screen.
Select Calendar and press Select.
Select Appointments and press Select.
Enter ./Calendar/Events in the Database field.
Leave the user id and pwd fields blank and press Select to return to the Calendar screen.
Select Tasks and press Select.
Enter ./Calendar/Tasks in the Database field.
Leave the user id and pwd fields blank and press Select to return to the Calendar screen.
Press the Return key (return arrow symbol) four times to return to the Synchronization screen.
Select Remote sync. and press Select.
Select Applications and press Select.
To toggle a selection, select either Phone book or Calendar and press the * (asterisk) key to enable or disable either option.
Press Save to return to the Remote Sync. screen.
Press the Return key (return arrow symbol) until you have returned to the main menu. The synchronization client is now configured and ready for use.
To perform a normal synchronization once the phone has been configured, follow these steps:
From the main menu, select Connect (Connectivity on the T630) and press Select.
Select Synchronization and press Select.
Select Remote Sync. and press Select.
Select Start and press Select.
The synchronization session will now start. When it is complete, the Remote Sync. will return.
|
Notes:
|
Oracle Sync Server is certified for the Synthesis SyncML client for Palm version 2.1.0.1.
Select Edit Profile Settings... from the menu.
SyncML Server URL = http://<host>:<port>/ocst-bin/ocas.fcgi
User = <userID>
Passwd = <password>
Click more... next to the Address, Calendar, ToDo
Addresses Server Path = ./Contacts
Calendar Server Path = ./Calendar/Events
ToDo Server Path = ./Calendar/Tasks
|
Note: Palm devices do not support traveling across time zones. For details, see Devices that do not support time change. |
Oracle Sync Server is certified for the Synthesis SyncML client for PocketPC version 2.1.0.1.
Select Extras, then Profile Settings... from the menu.
Select the General tab and enter the following details:
SyncML Server Address (URL) = http://<host>:<port>/ocst-bin/ocas.fcgi
Username = <userID>
Password = <password>
Select the Organizer tab and enter the following details:
Contacts Server Path = ./Contacts
Events Server Path = ./Calendar/Events
Tasks Server Path = ./Calendar/Tasks
This section contains the following topics:
Is your device SyncML-enabled?
In order to synchronize with Oracle Sync Server, you must have a SyncML-enabled device running a standard SyncML client. For a list of supported devices, see Supported devices. If you are using a Palm or PocketPC device, make sure you install the appropriate Synthesis SyncML client. If you are synchronizing wirelessly, you will need to subscribe to data services from your wireless service provider.
Are you using a certified device?
Oracle has a list of certified SyncML devices that have been tested and certified to work with Oracle Sync Server. These devices are listed in the Supported devices section.
Other devices that are SyncML-compliant and adhere faithfully to the SyncML standard may work with Oracle Sync Server, but Oracle cannot guarantee this, nor can Oracle offer support for these devices at this time.
If you are synchronizing wirelessly, is your device data-enabled, and does your wireless account support this?
In order to perform wireless synchronizations using a SyncML-compliant device, your wireless account must support the exchange of data (in other words, Web pages) through wireless HTTP. Your device must also be configured to support this — this is commonly referred to as being "data-enabled," "data-capable," "Web-enabled" or something similar. Note that this is not always the case by default, nor is it the same as simply setting up a Web-browsing profile on your device. You must specifically configure the device to be capable of exchanging HTTP data. See Configuring devices for Oracle Sync Server for information on setting up your device. For further details, consult the device manufacturer, your wireless provider and any relevant documentation.
Can you access Web pages with your device?
Through wireless connections: Once your device is data-enabled, you need to configure at least one account or profile for using wireless HTTP to connect to your wireless provider's server and view Web pages. Your wireless provider can give you the information needed to do this, such as user name, password, server address and setup instructions. This account or profile will be used by your device to connect to the SyncML server and perform synchronizations. This can be done on GSM or GPRS networks.
Through non-wireless connections: Like wireless devices, your device must be configured to exchange HTTP data. See Configuring devices for Oracle Sync Server for more information. For Palm devices that use a computer's Internet connection to exchange information with Oracle Sync Server, you must download and install connection software that establishes a PPP connection through the USB cable of your Palm; for example, Softick PPP, available at http://www.softick.com/ppp/.
If you are synchronizing wirelessly, are you using a valid connection profile?
When you configure wireless SyncML settings on your device, you must choose a valid connection profile through which to synchronize your data (as described in the preceding issue). Many wireless devices support multiple connection profiles, which is convenient if you travel often and need different ways to connect. Wherever you are, make sure your SyncML settings specify an appropriate working profile to use to synchronize data wirelessly.
Are your SyncML Settings correct?
Make sure you have the correct settings to connect to the SyncML server. You will need to enter the SyncML server's URL and port number in the device, along with your Calendar user name and password. The administrator of the SyncML server should be able to provide this information for you. For more instructions on setting up SyncML on your device, see the Configuring devices for Oracle Sync Server section, or consult the manufacturer's documentation.
Why would I choose Oracle Sync Server instead of Oracle Calendar Sync?
Does my device require special certification or special software?
Do I need to subscribe to a special service or special operator?
What is SyncML?
SyncML is the protocol for synchronizing devices and applications over the Internet. SyncML is based on the Extensible Markup Language (XML) protocol, employing standards such as iCal, vCal and vCard for data representation. The first data types supported for remote synchronization were calendar, task and contact data, but SyncML will soon support the synchronization of files, e-mail and other enterprise data.
What is Oracle Sync Server?
Oracle Sync Server, incorporated into Oracle's Collaboration Suite product portfolio, delivers remote synchronization of data stored in Oracle Collaboration Suite — including Calendar events, tasks and contacts — with any SyncML-enabled device or application. Users connect their device to Oracle Sync Server through the Internet, using any standard Hypertext Transfer Protocol (HTTP) connection. This can be done with a device cradle or by using wireless technologies such as GPRS, Bluetooth and WiFi, depending on the device.
What are the benefits of using Oracle Sync Server?
With Oracle Sync Server, there are no more desktop dependencies for synchronization; mobile workers simply connect to the Internet to synchronize with corporate networks, enabling greater efficiency with anywhere, anytime access to information that is always up-to-date. Users no longer require conduits from PDAs to PCs, and corporations need no longer worry about device-specific or platform-specific software installations on devices or PCs. Dependencies on connections to the data server over a Local Area Network (LAN) or Virtual Private Network (VPN) are also no longer necessary. End-users maintain the flexibility to choose the SyncML-compliant device that best suits their needs, with the assurance that they will not lose any synchronization functionality. For calendar users, Sync Server is a complete solution, offering full two-way synchronization of events, tasks and contacts, including meeting recurrence rules and respect of meeting ownership.
Why would I choose Oracle Sync Server instead of Oracle Calendar Sync?
Although they both use the same synchronization engine, Oracle Sync Server and Oracle Calendar Sync differ in their transportability. Oracle Calendar Sync requires a physical connection from the cradle to your corporate network, while Oracle Sync Server has no dependency on wired connections or corporate networks. Oracle Calendar Sync desktop PDA software replaces your device's sync conduits, allowing you to synchronize your PDA with the Calendar server through a physical connection to a LAN or VPN network. Oracle Sync Server synchronizes over any HTTP connection, removing dependency on physical connections and allowing full synchronization wherever an HTTP connection is available — whether physical or wireless. If you are a very mobile worker and would benefit from anywhere, anytime synchronization, Oracle Sync Server may be your preferred option.
What kind of device do I need to access Sync Server?
You must have a SyncML-enabled device running a standard SyncML client. For a list of supported devices, see Supported devices. You will also need to subscribe to data services from your wireless service provider.
Do I need a wireless device?
No. Synchronizing with Sync Server can be achieved through any connection to the Internet — whether wireless or physical. This means non-wireless PDA users can connect to Sync Server using a device cradle and an established Internet connection, as long as they are running a SyncML client on the device.
Does my device require special certification or special software?
Oracle has a list of certified SyncML devices that it supports, as described in Supported devices. Many of these devices have supported SyncML software built in, but in the case of legacy PDAs like Palm and PocketPC, you must install the appropriate Synthesis SyncML client.
Can I use my Palm or PocketPC with Sync Server?
Yes. Users of legacy PDAs can take advantage of Sync Server by installing the appropriate Synthesis SyncML client on their Palm or PocketPC devices. With this third-party SyncML client, Palm and PocketPC users can now use Sync Server synchronization alongside the newer crop of SyncML-enabled devices. Even non-wireless Palm and PocketPC devices can be used, as long as they can connect to the Internet through a device cradle. In the case of Palm devices, you will need software to establish a PPP connection through your USB cable, as Palm does not support this capability "out of the box."
Do I need to subscribe to a special service or special operator?
Once you have a SyncML-enabled device running a standard SyncML client, or have installed SyncML client software from a third-party vendor (in the case of Palm and PocketPC users), you must then ensure that you are subscribed to data services from your wireless service provider. In the case of legacy PDAs that allow you to connect to the Internet through a cradle, wireless data services are not required.
Do I need to modify my device settings?
To set up your device and configure it to work with Sync Server, read the Configuring devices for Oracle Sync Server section of this document. As an emerging technology, SyncML today can sometimes lead to a variety of minor frustrations that can take away from its benefits. These limitations are generally caused by inconsistent and problematic implementations of SyncML clients by device manufacturers, or by limitations in data representation. Reviewing this Resource Kit will help you avoid these issues and get the most out of Sync Server.
What data types can I synchronize with Sync Server?
Today, Sync Server supports synchronization of Calendar events, tasks and contacts.
Can I synchronize my e-mail?
Not yet. Support for e-mail synchronization and other key business data types beyond calendar and contact data will follow with the release of SyncML 1.2 specifications, scheduled for Fall 2004.
Is Sync Server secure?
Oracle Sync Server can be deployed to accept secure (SSL) connections. This means all your connections are encrypted, providing secure transmission of data from your device to the Sync Server. Without SSL, meetings, contacts and tasks can be intercepted and read. To see which devices support secure synchronization, see Devices that support secure connections.
What if I have more questions?
Please subscribe and address questions to syncml_help_ww@oracle.com.
