Oracle Mobile Data Sync takes advantage of the OMA-DS (Open Mobile Alliance - Data Synchronization) protocol (formerly known as the SyncML protocol) to deliver true remote synchronization of data with a wide range of OMA-DS-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 Mobile Data Sync 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 OMA-DS-compliant devices with Internet access. With Oracle Mobile Data Sync you are no longer tied to your desktop for synchronization.
With previous versions of Oracle Mobile Data Sync (formerly known as Oracle Sync Server), authentication required using a Single Sign-On password. With this release of Oracle Mobile Data Sync, authentication using the Oracle Mobile Collaboration wireless numerical PIN is supported. You can create this PIN on the Oracle Mobile Collaboration Wireless Preferences page. However, for standalone installations of Oracle Mobile Data Sync (as part of the Oracle Calendar application system), you cannot use PIN authentication. You must sign in with your Oracle Calendar server password.
The behavior of OMA-DS devices is largely dependent on the device model and the wireless carrier you are using. This page contains important information about the OMA-DS devices supported by Oracle Mobile Data Sync.
The following tables list OMA-DS-compliant devices and operating systemsthat are supported for use with Oracle Mobile Data Sync.
Caution: Ideally, you should synchronize with Oracle Mobile Data Sync using Secure Sockets Layer (SSL) connections (for example, https://mobile_data_sync_host:port/ocst-bin/ocas.fcgi). Without SSL, your data could, in theory, be intercepted whenever you synchronize your device. Use the Notes column of the following table to determine if your device supports SSL. If Oracle Mobile Data Sync is configured to accept secure connections and you are using a compatible device, you should synchronize using a secure connection.
Table 1-1 Oracle Mobile Data Sync Certified Devices
| Brand | Models | Notes |
|---|---|---|
|
Nokia |
3650, 6600, 6020, 6021, 6260, 6230i, 6620, 6630, 6670, 6680, 6682, 6800, 6810, 6820, 6822, 7250, 7260, 7610, 7260, 92xx, 9300, 9300i, 9500, E50, E51, E60, E61, E61i, E62, E65, E70, E90,N70, N73, N80, N90, E51i, N81, N95, 6131 NFC |
The Nokia 6600, 6620, 6260, 6630, 6670, 6680, 6682, 7610, 92xx series, 9300, 9300i, 9500 and N90 support synchronization over secure (SSL) connections. |
|
Ericsson |
R520m, T39, T68 |
These devices all support synchronization over secure (SSL) connections. |
|
Sony Ericsson |
T610, T616, T630, T637, T68i, P800, P900, 910a, 910i, P990i, M600i, P1i, W960, S700i, S710a, SK65, SL65, K700i, K550i, K610i, K750i, k790a, K800i, W800i, W810i, W880i, K850i, Z500, Z520a, Z520i, Z600, Z800i, W850, W910i, W960 |
The Sony Ericsson P900 requires firmware R4A06. See Updating P900, P910a, and P910i firmware for more information. All of these devices support synchronization over secure (SSL) connections, with the exception of the Z520a, Z520i and W800i. |
|
Siemens/BenQ-Siemens |
M55, S55, C65, CX65, S65, S66, S68, SK65, SL65, SX1 |
The following Siemens devices support synchronization over secure (SSL) connections: Siemens SL65, SK65 and BenQ-Siemens S68. |
Table 1-2 Oracle Mobile Data Sync Certified Operating Systems
| Brand | Sample Devices | Notes |
|---|---|---|
|
Palm |
Tungsten C, Tungsten T3, Tungsten W, Sony Clie TG50, Palm Treo 600, Palm Treo 650, Palm Treo 680, Palm Treo 680p, Palm Treo 755p |
Palm devices must be running Palm OS 3.5 or higher, have 4 MB of RAM and use version 2.5.0.46 (PRO or Standard) of the Synthesis SyncML client to work with Oracle Mobile Data Sync. The devices listed here have been tested and certified by Oracle, but all Palm devices using the Synthesis SyncML 2.5.0.46 client should work with Oracle Mobile Data Sync. Devices supported by the Synthesis SyncML clients are listed on Synthesis's Web site at Only the Tungsten T3 and Palm Treo 650 running Palm OS 5.2.1 or higher and using the Synthesis SyncML client 2.5.0.46 (PRO or Standard) support synchronization over secure (SSL) connections. |
|
Windows Mobile 2003 |
Dell Axim X5 (Windows Mobile 2002 and 2003 versions), HP IPAQ Hx2755, H5550, and H6340, Siemens SX56 |
Windows Mobile 2003 devices require version 2.5.0.46 (PRO or Standard) of the Synthesis SyncML client to work with Oracle Mobile Data Sync. The devices listed here have been tested and certified by Oracle, but all Windows Mobile devices with the required version of the Synthesis client should work with Oracle Mobile Data Sync. Devices supported by the Synthesis SyncML clients are listed on Synthesis's Web site at Windows Mobile devices must be able to connect to the Internet through a cradle, modem or mobile phone. |
|
Smartphone 2003 |
I-Mate Sp31, I-Mate JAM, Motorola MPx220 |
Smartphone 2003 devices require version 2.5.0.46 (PRO or Standard) of the Synthesis SyncML client to work with Oracle Mobile Data Sync. The devices listed here have been tested and certified by Oracle, but all Smartphone 2003 devices with the required version of the Synthesis client should work with Oracle Mobile Data Sync. Devices supported by the Synthesis SyncML clients are listed on Synthesis's Web site at Smartphone 2003 devices must be able to connect to the Internet through a cradle, modem or mobile phone. Note: Oracle Mobile Data Sync does not support the Microsoft Smartphone 2002 edition. |
|
Windows Mobile 5.0 |
I-Mate Windows Mobile PU10, QTEK 9100 |
Windows Mobile 5.0 devices require version 2.5.0.46 (PRO or Standard) of the Synthesis SyncML client to work with Oracle Mobile Data Sync. The devices listed here have been tested and certified by Oracle, but all Windows Mobile 5.0 devices with the required version of the Synthesis client should work with Oracle Mobile Data Sync. Devices supported by the Synthesis SyncML clients are listed on Synthesis's Web site at Windows Mobile 5.0 devices must be able to connect to the Internet through a cradle, modem or mobile phone. |
| Blackberry |
You can back up your Palm device locally using HotSync.
Caution: Oracle does not recommend attempting to back up your Windows Mobile using ActiveSync if you use Oracle Connector for Outlook. Doing so may result in unexpected behavior, including loss of data.
Installing HotSync
Run the Palm Desktop installation program.
Select Palm Desktop as your Personal Information Manager.
Enter your Username.
Select your connection method and click Install.
When the installation is completed, you will be instructed to press the HotSync button on your cradle.
At this point, you must reset your Palm.
Using HotSync to back up your data
Start Palm Desktop.
Right-click the HotSync icon in the Taskbar and select Custom.
Set the Action for the Date Book, Address Book and To Do List conduits to Handheld overwrites Desktop. This ensures that changes made to the Desktop data will be replaced by the data on your Palm device.
When you are ready to back up your data, place the Palm device in the cradle and press the HotSync button. The contents of your device will overwrite what was previously on the Desktop.
Restoring your data
If you need to restore the backed up data to your Palm device, follow these steps.
Start Palm Desktop.
Right-click the HotSync icon in the Taskbar and select Custom.
Set the Action for the Date Book, Address Book and To Do List conduits to Desktop overwrites Handheld by clicking the Change button and selecting the appropriate options. Do not set this as your default.
Place your Palm device in the cradle and press the HotSync button. The contents of the Palm Desktop will overwrite what was previously on your device.
This section describes common configuration issues for devices used with Oracle Mobile Data Sync. 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:
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.
Table 1-3 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 |
Normal |
5 |
|
Sony Ericsson P series |
1 through 9 |
1 through 9 |
|
Synthesis client for Palm |
1 through 5 |
1 through 5 |
|
Synthesis client for Windows Mobile |
High / Normal / Low |
1 / 5 / 9 |
Table 1-4 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 - 7 / 8 - 9 |
High / Normal / Low |
|
Oracle Calendar desktop clients and Web client |
1 through 9 |
1 through 9 |
|
Nokia |
1 - 3 / 4 - 7 / 8 - 9 |
High / Normal / Low Note: Priority levels synched from the server are read-only.
|
|
Siemens |
1 - 5 / 6 - 9 |
1 - 5 / 5 |
|
Sony Ericsson T series |
1 - 3 / 4 - 7 / 8 - 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 Windows Mobile |
1 - 3 / 4 - 7 / 8 - 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 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.
This section describes how to customize the way your device synchronizes information. Because OMA-DS 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
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.
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.
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 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).
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:
Delete any duplicate or erroneous data from your Nokia device.
Click Desk on the keypad.
Open Tools, then Synchronization.
Highlight the desired synchronization profile and click Menu on the keypad.
Delete your calendar data.
Select File, then select Synchronization, then Slow Sync.
Click Continue. A normal two-way sync will automatically be executed during the next synchronization.
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.
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.
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.
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.
./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 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.
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:
Synchronize your device.
Delete your calendar data.
After traveling to the new time zone, verify that your device is set to the correct time.
Use an Oracle Calendar client to set your calendar account to the new time zone.
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.
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.
Synchronize your device before you travel, or before a Daylight Savings clock change occurs.
From the Organizer menu on your device, select Calendar, then Advanced, then 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 traveled 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: 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.
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, then Organizer, then 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 traveled 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 synchronization 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.
This section includes the following topics:
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.
From the Organizer menu on your device, select Calendar, then Advanced, then 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.
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.
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:
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, 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:
This section describes the method for to deleting all events from Palm devices and performing 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 perform a slow synchronization.
Caution: If you delete data from the device and then perform a regular synchronization instead of a slow synchronization, data will be deleted from your calendar account on the server. You must be sure to perform a slow synchronization after deleting data on your device, as described below.
Delete all events from a Palm device and replace them with data from your server account as follows.
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 Reload Device from the drop-down menu.
Synchronize your device.
A warning alert will ask you if you want all data on the device replaced by server data. Select Yes.
The data on your device will be deleted, then a slow synchronization will occur. Data is synchronized from your account on the calendar server to your device.
Note: If you have incorrect task or contact entries, you must delete them manually.
To perform 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.
This section describes how to delete all events from PocketPC devices and perform a slow synchronization in one step.
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 perform a slow synchronization after deleting data on your device, as described in this section.
Delete all data from a PocketPC device and replace it with data from your server account as follows.
Run the Synthesis SyncML Client.
Select Extras, then select Profile Settings.
Select the Organizer tab.
Select reload device for the Sync Mode for Contacts, Events, and Tasks.
Synchronize your device.
A warning alert will ask you if you want all data on the device replaced by server data. Select Yes.
The data on your device will be deleted first, then a slow synchronization will occur. 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.
Note: The steps that describe how to delete data from your device are only necessary if you have extraneous or incorrect information on your device. If you are simply missing information on your device, proceed to step 6 and perform a slow synchronization.
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.
Synchronize the device.
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 perform a slow synchronization, as described in the preceding step.
Follow this procedure to reset data on Sony Ericsson P series (except P910i) and M series devices.
Note: The steps that describe how to delete data from your device are only necessary if you have extraneous or incorrect information on your device. If you are simply missing information on your device, perform a slow synchronization.
On your device, select Menu, select Tools, then select Remote Sync .
Select your sync profile .
For each sync task, select the sync task and change the sync type to Restore.
Click Save.
Synchronize the device.
Caution: If you delete data from the device and then do a regular synchronization instead of a reset, data will be deleted from your calendar account on the server. You must be sure to configure your device to perform a reset, as described in the preceding step.
This section describes issues encountered by Oracle Mobile Data Sync due to the OMA-DS 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 1-6 Nokia OMA-DS Behavior Issues
| Issue | 3650 | 6600/6260/6630/6670/6680/ 6682/7610 | 6020/6021/6230i/ 6800/6810/6820/6822/7250/7260/7270 | 7650 | 92xx | 9300/9300i//9500 | E90/E70/E50/E60/ E61/E61i/E62/E65/N73/N80/N90 |
|---|---|---|---|---|---|---|---|
|
Some Nokia devices do not support traveling across time zones. For details, see Devices that do not support time change. |
Applies |
Applies |
Applies |
Applies |
Applies |
Does not apply |
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 Oracle Mobile Data Sync administrator, as described in Safely resetting data on your device. |
Applies |
Applies |
Applies |
Applies |
Applies |
Does not apply |
Applies |
|
Some Nokia devices do not support SSL (HTTPS) connections. These devices therefore cannot be used with Oracle Mobile Data Sync if it is set up to only accept SSL connections. |
Applies |
Does not apply |
Applies |
Applies |
Does not apply |
Does not apply |
Does not apply |
|
The OMA-DS 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 |
Applies |
|
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 |
Applies |
Applies |
Does not apply |
Does not apply |
Does not apply |
Does not apply |
applies |
|
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 |
Applies |
Applies |
Does not apply |
|
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 |
Applies |
Does not apply |
Does not apply |
|
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 |
Applies |
Applies |
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 |
Applies |
Applies |
Applies |
Does not apply |
|
Modifying a Birthday or a Call on the server could result in irregular behavior and should be avoided. |
Does not apply |
Does not apply |
Applies |
Does not apply |
Does not apply |
Does not apply |
Does not apply |
|
Unable to synchronize with the Nokia 9210 and 9290 devices when |
Does not apply |
Does not apply |
Does not apply |
Does not apply |
Applies |
Does not apply |
Does not apply |
|
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 |
Applies |
Does not apply |
Does not apply |
|
Previously, certain Nokia devices did not support multi-field addresses. When this was the case, information would be synchronized from the server to the device, but not from the device to the server, due to incompatibility with the multi-field address format supported by Oracle Mobile Data Sync. Now, addresses are synchronized both ways. If the address is entered on the server and is not changed on the device, the multi-field address is preserved on the server. If the address is entered first on the device or is changed on the device, it will be synchronized to the "street" address field on the server. |
Does not apply |
Does not apply |
Applies |
Applies |
Does not apply |
Does not apply |
Does not apply |
| When adding ?/reset (true) to contact URI. The contacts duplicate at each sync. The same is, in parft true of ./Contact?/reset(true). In that case in the newer Nokia, you don't get the "System" Error!" dialing boxes. Instead the phones keep sending the contacts at every sync and the contacts duplicate at every sync which is still broken. | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Applies | |
| Adding URI such as ?/dr(0,7) doesn't work on Nokia E Series phones. The phone pops up a "feature not supported" error message. | 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 1-7 Ericsson and Sony Ericsson OMA-DS Behavior Issues
| Issue | R520m | T39/T68 | T68i | P800/P900/P910a/P910i /P990i/M600i/P1i/W960 | T610/T616/T630/T637 S700i/K700i/S710a/K550i/K610i/K750i/K800i/W800i/K850i/Z500/Z520a/Z520i/Z600/Z800i/ W850/W910i |
|---|---|---|---|---|---|
|
You must install firmware R4A06 or later (for example, R4B03) before you can use the P900 with Oracle Mobile Data Sync. For details, see Updating P900, P910a, and P910i firmware. |
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 |
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 |
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 |
Applies |
Does not apply |
|
Missing resource names: When the |
Applies |
Applies |
Applies |
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 |
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 |
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 |
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 |
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 |
Applies |
Does not apply |
Does not apply |
|
Task synchronization is not supported. |
Applies |
Applies |
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 |
Applies |
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 |
|
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 |
Applies |
Does not apply |
Does not apply |
The following table summarizes known issues of Motorola devices that use Symbian operating system.
Table 1-8 Motorola devices using the Symbian operating system
| Issue | A1000 / FOMA M1000 | A1200 |
|---|---|---|
|
These devices do not fully support time change due to travel or Daylight Savings. For details, see Devices that partially support time change. |
Does not apply |
Does not apply |
|
These devices do not support traveling across time zones. For details, see Devices that do not support time change. |
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, carefully follow the instructions described in Triggering a slow synchronization. |
Applies |
Applies |
|
Missing resource names: When the |
Does not apply |
Does not apply |
|
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. |
Does not apply |
Does not apply |
|
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. |
Does not apply |
Does not apply |
|
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. |
Does not apply |
Does not apply |
|
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. |
Does not apply |
Does not apply |
|
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 |
|
Task synchronization is not supported. |
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. |
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 |
| If you create a meeting on the server and attach an alarm for say 15 minutes, before the meeting the alarm will get synced to the device, but it would actually be 1 day early (24hr before the beginning of the meeting). | Does not apply | Applies |
The following are known issues of the OMA-DS software on Siemens/BenQ-Siemens C65, CX65, M55, S65, S55, S66, S68 Windows Mobile devices:
Most Siemens devices do not support the use of OMA-DS through SSL (HTTPS) connections. These Siemens devices therefore cannot be used with Oracle Mobile Data Sync if it is set up to accept SSL connections only. Siemens devices that do support SSL with OMA-DS are the Siemens SL65, SK65 and BenQ-Siemens S68.
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).
Contact categories are not synchronized.
Home fax numbers are synchronized to the device as home phone numbers.
Day Events are disabled on all Siemens devices except Windows Mobiles.
Start times for tasks is supported on the following models only: C65, CX65, S65, S66, SL65, SK65, M55, S55, S68 and Windows Mobiles.
If a Contact is modified on the BenQ-Siemens S68 or the OMA-DS server, both the original and the modified Contacts will be synchronized on the device and on the server the next time the device and the server are synchronized.
Tasks that are modified on the server do not synchronize with the Siemens SL65 or the BenQ-Siemens S68.
The following are known issues of devices using Synthesis SyncML clients:
PalmOS, Windows Mobile, Smartphone 2003 and Windows Mobile 5.0 devices with version 2.5.0.46 or later (PRO or STD) of the Synthesis SyncML client support secure (SSL) connections. However, Palm devices with PalmOS before Version 5.2 may not support secure connections depending on the model. Palm devices with PalmOS before Version 5.0 never support secure connections.
Palm devices require either a wireless Internet connection to your computer or a USB cable with third party software that can bridge the connection to your computer (such as Softick PPP).
Windows Mobile and Smartphone 2003 devices do not synchronize the field Show Time As, which is used to display a user's availability.
The Synthesis SyncML client prior to version 2.5.0.59 does not support devices that use the Windows Mobile 5.0 operating system.
Palm devices do not support traveling across time zones. For details, see Devices that do not support time change.
Some devices do not fully support resetting data using slow synchronization. For details, see Devices that require workarounds to reset data.
Task Categories do not synchronize from, or to, Palm devices. Synchronizing Content Categories requires Synthesis SyncML client for Palm version 2.5.0.46 or later.
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 Mobile Data Sync 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 if the events were created in Oracle Connector for Outlook.
Synchronization of daily recurring weekdays is not supported.
E-mail addresses and phone numbers synchronized to Windows Mobile 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.
The following are known issues of devices using SyncJe clients:
Home Phone 2 and Business Phone 2 are not synchronized by SynceJe for Blackberry.
This section contains instructions on how to configure the following OMA-DS clients.
With previous versions of Oracle Mobile Data Sync (formerly known as Oracle Sync Server), users authenticated themselves using their Single Sign-On passwords. With the release of Oracle Mobile Data Sync 10.1.1, authentication using the Oracle Mobile Collaboration wireless numerical PIN is supported. Users can create this PIN on the Oracle Mobile Collaboration Wireless Preferences page.
When upgrading to Oracle Mobile Data Sync 10.1.1, Single Sign-On authentication remains in place. Fresh Oracle Mobile Data Sync 10.1.1 installations use PIN authentication by default. Administrators can change between the two authentication methods, so check with your administrator if you are not sure which one you should be using.
Note: Standalone installations of Oracle Mobile Data Sync (as part of the Oracle Calendar application system) do not use PIN authentication. Users must sign in with their Oracle Calendar server passwords.
Nokia E50 / E51/ E51i / E60 / E61 / E61i / E62 / E65 / E70 / N81 / E90 / N80 / N95
Siemens M55 / S55 / C65 / CX65 / S65 / S66 / SK65 /SL65 or BenQ-Siemens S68
Sony Ericsson P800 / P900, P910a, P910i, P990i, M600i, P1i, W960
Sony Ericsson T610 / T616 / T630 / T637 / W800i / Z500 / Z520a / Z520i / Z600
Sony Ericsson K550i, K610i, K750i, K790a, K800i, W810i, W880i
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: your profile name
Bearer type: Internet
Access point: select a valid Internet access point
Mobile Data Sync host address; for example,http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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 this field empty
HTTP password: leave this field empty
Press the Menu button for the main menu.
Select the RemoteSync icon, press Options and select Open.
Select your name from the profile list.
Press Options, then select Sync to begin the synchronization.
Note: Some 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, 6620, 6630, 6680 or 6682 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: your profile name
Access point: select a valid access point
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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 twice.
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: Some 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 E50, E51, E51i, E60, E61, E61i,E62, E65, E70, E90, N80, N81, N95 device.
Press the Menu button for the main menu, then Sync.
Select Options, then select New Sync Profile. If the Copy Values From dialog box appears, select No.
Enter the following details:
Sync profile name: your profile name, then click OK.
Highlight Applications, then click Options and select Edit sync profile.
Highlight Contacts, then click Options and select Edit sysnc profile.
Enter the following details:
Included in sync: Yes/No
Remote database: ./Contacts
Synchronization type: Normal
Click Back
Highlight Calendar, then click Options and select Edit sysnc profile.
Enter the following details:
Included in sync: Yes/No
Remote database: ./Calendar
Synchronization type: Normal
Click the Back button twice
Enter the following details:
Server version:1.2
Server ID: Leave blank.
Data bearer: Internet
Access point: Select a valid access point
Host address: For example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Port: 80
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Allow sync requests: No
Accept all sync reqs.: No
Network authentic: No
Press the Menu button for the main menu, then Sync.
Highlight your sync profile.
Click Options and select Synchronize.
Note: Some 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 6260, 6670, 7610, N70 and N90 device.
your profile name, then click OK
Data bearer: Web
Access point: In most cases, the setup required to access the Internet is already configured. If this is not the case, contact your wireless provider.
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Port: 80
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Allow sync requests: No
Accept all sync requests: No
Enter the following information in the second tab:
Calendar: Yes
Remote Database: ./Calendar
Synchronization type: Normal
Contacts: Yes
Remote Contacts: ./Contacts
Synchronization type: Normal
Notes: No
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.
You can change which of the 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: your profile name
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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.
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.
You can change which of the 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: your profile 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.
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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: Some 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 6020, 6021, 6230i, 6822, 7260 or 7270 device.
From the main menu, go to Settings, then Configuration Settings.
Select Personal configuration settings, then Add New.
Select Synchronization, then enter the following details:
Account Name: your profile name
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Contacts Database
Database Address: ./Contacts
User Name: leave this field empty
Password: leave this field empty
Notes: leave this field empty
Calendar Database
Database Address: ./Calendar
User Name: leave this field empty
Password: leave this field empty
Notes: leave this field empty
Access Point Settings: select a valid Internet Access Point
Proxy: Disable
Data bearer: GPRS
Authentication type: Normal
Return to the Configuration Settings menu.
Select Default Configuration Settings.
Highlight Personal config. then click Options.
Select Set as default.
Return to the main menu and select Organiser.
Select Synchronization, then Server Sync, then Sync Settings.
Return to the Server Sync menu.
Go to Data to be synchronized.
Check the contacts and/or calendar.
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: Some 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 9210, 9210i or 9290 device.
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: your profile name
Use: Internet
Internet access: PPP
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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.
Note: Some 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 9300, 9300i, 9500 and N73 device.
The OMA-DS client is called Synchronization and is located in the Tools folder.
Press the Desk key.
Select Tools.
Select Synchronization.
Press the Menu key.
Select New to create Synchronization profiles using the Sync Profile Wizard.
Provide a name for the synchronization profile and click Next.
Select the connection type and access point and click Next.
Enter the Internet server settings then click Next:
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Select the content types that will be used and click Next.
If Contacts were selected, enter the following and click Next:
Local database: C:\System\Data\Contacts.cdb
Remote database: ./Contacts
Sync type: Normal
If Calendar was selected, enter the following and click Next:
Local database: C:\System\Data\Calendar
Remote database: ./Calendar
Sync type: Normal
Select whether or not the profile should be used as the default synchronization profile and click Next.
Click Finish.
Press the Desk key.
Select Tools, then Synchronization.
Highlight the desired synchronization profile and select Sync to synchronize with the server.
Note: Some 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 6131 NFC device.
Configuring RemoteSync for Nokia 6131 NFC.
Press the Menu button for the main menu.
Select Settings, Configuration, then Personal Config. Settings.
Click Options, select Add New, then select Synchronisation.
Enter the following details:
Account name, click ok
Server Address, click ok
User name, click ok
Password, click ok
Contacts Database: ./contacts, click ok, then back
Calendar Database: ./calendar, click ok, then back
If you have more than one Personal Account, then select Settings from main menu .
Select Configuration, then Configuration, then Personal Config. Settings.
Highlight the account that you would like to Synchronise, click Options, then select Activate
Click Back twice.
The following sections describe the steps for configuring and synchronizing your 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 Mobile Data Sync.
Press No once to return to the Remote Login screen.
Select Sync Server and press Yes.
Enter your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Enter the Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
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, 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 Siemens M55, S55, C65, CX65, S65, S66, S68, SK65, SL65 or BenQ- Siemens S68 device.
Note: Most Siemens devices do not support the use of OMA-DS through SSL (HTTPS) connections. These Siemens devices therefore cannot be used with Oracle Mobile Data Sync if it is set up to only accept SSL connections. Siemens devices that do support SSL with OMA-DS are the Siemens SL65, SK65 and BenQ-Siemens S68.
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 Edit button.
You can change which of the five profiles is active by selecting the profile and pressing the Select button. After choosing a profile, press the Edit button.
Enter the following details:
Provider: In most cases, the setup required to access the Internet is already configured. If this is not the case, contact your wireless provider. Your provider can give you the information required to perform the necessary configuration.
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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 Sync button to begin synchronization.
|
Notes:
|
The following sections describe how to configure and synchronize your Siemens SX1 device.
Note: Siemens devices do not support the use of OMA-DS through SSL (HTTPS) connections. Siemens devices therefore cannot be used with Oracle Mobile Data Sync if it is set up to only accept SSL connections.
From the main menu go to Organizer.
Select the Sync menu and press the Select button.
Choose one of the available profiles and press Options.
Select the Edit Sync Profile option and press the Select button.
Select the Server sett. menu option and press the Select button.
Enter the following details:
Access Point: select a valid Internet access point
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Calendar path: ./Calendar/Events
Contacts path: ./Contacts
Task Path: ./Calendar/Tasks
HTTP Authent: No
Press the Save button.
Ensure that Calendar, Contacts and Tasks have Yes below them. Use the Change button to update the options.
The following sections describe how to configure and synchronize your Sony Ericsson P800 or P900 device. This section contains the following topics:
Applying the time zone patch for Sony Ericsson P800, P900, P910a, and P910i
Synchronizing the Sony Ericsson P800, P900, P910a, P910i, P990i, M600i, W960 and P1i
The Sony Ericsson P900 series must have firmware R4A06 or later to work with Oracle Mobile Data Sync.
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 Organizer and see the numbers below it. The firmware version is the second number; for example:
Organizer:
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/spg.jsp?cc=global&lc=en&ver=4001&template=ps1_1_3_2&zone=ps&lm=ps1_1&pid=10101
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 Oracle Mobile Data Sync 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 P800-P900-P910_SyncMLFix patch is available from http://download.oracle.com/otn/nt/cs/9042/P800-P900-P910_SyncMLFix.zip. 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:
Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
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 Oracle Mobile Data Sync.
Press No once to return to the Remote Login screen.
Select Sync Server and press Yes.
Enter your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Enter the Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
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, T630, T637 , W800i, Z500, Z520a, Z520i or Z600 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 Oracle Mobile Data Sync.
Press the Return key (return arrow symbol) once to return to the Remote Login screen.
Select Sync Server and press Select.
Enter your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Enter the Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
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 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:
|
The following sections describe the steps for configuring and synchronizing your Sony Ericsson K700i, S700i, S710a or Z800i device.
From the main menu, select Connect then Select.
Select Synchronization and press Select.
Select New Account and press Add.
Enter the account name.
Enter the Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Enter your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Select Connection, then WAP profile and press Select.
Select Applications.
Check Phonebook, Appointments and Tasks, and press OK.
Select Application Setting.
Select Phone book, then press Select.
In the Database field, enter: ./Contacts (leave the User ID and PWD fields blank).
Press Save to return to the Applications screen.
Select Calendar and press Select.
Select Appointments and press Select.
In the Database field, enter: ./Calendar/Events (leave the User ID and PWD fields blank).
Select Tasks and press Select.
In the Database field, enter ./Calendar/Tasks (leave the User ID and PWD fields blank)
Press Select to return to the Calendar screen.
Return to Accounts and press Select to save the options.
Press the Return key (the return arrow symbol) until you have returned to the main menu. The synchronization client is now configured and ready for use.
The following sections describe the steps for configuring and synchronizing your Sony Ericsson K550i, K610i, K750i, K790a, K800i, W810i, W880i devices.
From the main menu, select Organizer then Select.
Select Synchronization and press Select.
Select New Account and press Add.
Enter the account name, then press Continue.
Enter the Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Enter your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Select Connection, then WAP profile or your connection profile and press Select.
Select Applications.
Check Contacts, Calendar and Tasks, and press OK.
Select Application Setting.
Select Contacts, then press Select.
In the Database field, enter: ./Contacts (leave the User ID and PWD fields blank).
Press OK to return to the Application Settings screen.
Select Calendar and press Select.
In the Database field, enter: ./Calendar/Events (leave the User ID and PWD fields blank). Press OK.
Select Tasks and press Select.
In the Database field, enter ./Calendar/Tasks (leave the User ID and PWD fields blank). Press OK.
Press the Return Key (the return arrow symbol), then press Save.
Press the Return key (the return arrow symbol) until you have returned to the main menu. The synchronization client is now configured and ready for use.
The following sections describe the steps for configuring and synchronizing your Sony Ericsson K850i, W850, and W910i devices.
From the main menu, select Organizer.
Select Synchronization .
Select New Account and press Add.
Select SycML account type.
Enter the account name, then press Continue.
http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi, then press OK. Enter your Username and Password (see About Passwords for more about Mobile Data Sync authentication), then press OK.
Highlight Advanced Tab, then select Connection.
Select Connection, then WAP profile or your connection profile and press Select.
Press Back button, then press Yes to save.
Select Applications Tab.
Check Contacts, Calendar and Tasks as desired, then press OK.
Highlight Contacts Tab, then press Select.
Select Contacts, then press Select.
In the Database field, enter: ./Contacts (leave the User ID and PWD fields blank). Press OK.
Press the Back button to return to the Application Settings screen.
Highlight Calendar and press Select.
In the Database field, enter: ./Calendar/events (leave the User ID and PWD fields blank). Press OK.
Press the Backbutton to return to the Application Settings screen.
Highlight Tasks and press Select.
In the Database field, enter ./Calendar/tasks (leave the User ID and PWD fields blank). Press OK.
Press Back button, then press Yes to save.
Press Back button until you return to the main menu.
From Main Menu, select Organizer.
Select Synchronization.
Select the account you wish to Synchronize, then press Start.
The following sections describe the steps for configuring and synchronizing your Synthesis Smartphone 2003. Synthesis Smartphone 2003, Windows Mobile 5 and Windows Mobile 6.
Select Menu, then New Profile.
Enter the following details:
The Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Enter the following details:
Contacts Server Path = ./Contacts
Events Server Path = ./Calendar/Events
Tasks Server Path = ./Calendar/Tasks
The following sections describe how to configure your Palm device to synchronize with Oracle Mobile Data Sync using the Synthesis SyncML client. Oracle Mobile Data Sync is certified for the Synthesis SyncML client for Palm version 2.5.0.46.
Select Edit Profile Settings... from the main menu.
Enter the following details:
The Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Enter the following details:
Contacts Server Path = ./Contacts
Events Server Path = ./Calendar/Events
Tasks Server Path = ./Calendar/Tasks
The following sections describe how to configure your Windows Mobile device to synchronize with Oracle Mobile Data Sync using the Synthesis SyncML client. Oracle Mobile Data Sync is certified for the Synthesis SyncML client for Windows Mobile version 2.5.0.46 and 3.0.x.
Select Extras, then Profile Settings... from the main menu.
Select the General tab and enter the following details:
The Mobile Data Sync host address; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Select the Organizer tab and enter the following details:
Contacts Server Path = ./Contacts
Events Server Path = ./Calendar/Events
Tasks Server Path = ./Calendar/Tasks
Occasionally, you may experience unexpected behavior when synchronizing your Windows Mobile device using the Synthesis SyncML client. For example, you may receive a "server db error" and synchronization may not complete successfully. To resolve this, try using the Windows Mobile Reload Device feature, as described in the following steps:
Update your Synthesis Windows Mobile client to version 2.5.0.46. Ensure that you update to the correct version, Standard or PRO, depending on your current version. The Oracle version is the "Standard" version.
Perform a soft reset of the Windows Mobile by rebooting it. This does not require reloading any other applications and it will not affect your e-mail configuration if you are using P-IMAP.
Once the device has rebooted, open the Synthesis application.
In Profile Settings, select the Organizer tab at the bottom of the screen.
Under Events, set the Sync Mode to Reload Device.
Select the General tab at the bottom of the screen and press OK.
Initiate the synchronization.
Note: The Synthesis client will automatically return to "Normal" sync mode once the reload has completed.
The following sections describe how to configure your Blackberry device to synchronize with Oracle Mobile Data Sync using the Nexthaus SyncJe client. Oracle Mobile Data Sync is certified for the Nexthaus SyncJe client for Blackberry version 2.34.
Install and register the SyncJe client for Blackberry version 2.34.
Select SyncJe Client , then Settings... from the main menu.
Enter the following details:
The Server URL; for example, http://mobile_data_sync_host:port/ocst-bin/ocas.fcgi
Your Username and Password (see About Passwords for more about Mobile Data Sync authentication)
Contacts Foldername = ./Contacts
Calendar Foldername= ./Calendar/Events
ToDo Foldername= ./Calendar/Tasks
Select the correct communication protocol: WAP, MDS or BIS.
The following sections describe the steps for configuring and synchronizing your Motorola A1200, KRZR, or ROKR device.
Press the Menu button for main menu, then select Sync.
Click Options, then select SyncML OTA Setup.
Check Contacts, Calendar, and Tasks as desired.
Select Contacts, then enter the following details:
./Contacts
Select Calendar, then enter the following details:
./Calendar/events
Select Tasks, then enter the following details:
./Calendar/tasks
Select Server Name, then enter your desired Connection information. For example: http://syncmdc.oracle.com/ocst-bin/ocas-fcgi.
Select User Name: Enter your User Name
Select Password: Enter your Password
Select Re-enter Password: Enter your Password
Select Data Connection: Enter your desired data connection
Click Save.
Press the Menu button for the main menu, then select Sync
Select OTA.
The following sections describe the steps for configuring and synchronizing your Motorola KRZR device.
Go to Main Menu, select WebAccess, select Web Sessions, then select New Entry.
Fill out the necessary GPRS information .
Once saved, click Options on the Web Sessions profile and choose it as default.
Go to Main Menu, select Connection, select MOTOSYNC, select Sync, then select New Entry.
Enter nter the following details:
Name: Your profile name
URL: URL server
User Name: Your User Name
Password: Your Password
Note: This device does not support Tasks.
Go to Main Menu, select Connection, select MOTOSYNC, select Sync, then select Your Profile.
The following sections describe the steps for configuring and synchronizing your Motorola ROKR device.
Go to Main Menu, Setings, Connections, then select Data Connection.
Select Add a New Connection.
Select Create New.
Fill out the necessary GPRS information.
Click Next.
Contine to fill out the necessary GPRS information.
Click Done.
Click Back to get back to the Main Menu.
Select Office Tools from Main Menu
Select MOTOSYNC, then Options.
Select Edit Profile,select Create a Profile, then select Create New.
Go to Main Menu, then select Office Tools.
Select MOTOSYNC.
In the second box choose the profile you just created.
Select Options, then Set as Default.
Click Synchronize Now.
"Motorola devices support attendees in the meetings but do not support synchronizing the
attendees."
For troubleshooting information and answers to frequently asked questions, click here.