| Oracle® Beehive Release Notes Release 2 (2.0) for Linux, Windows, and Solaris Operating System (SPARC 64-Bit) Part Number E16640-11 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Release Notes Release 2 (2.0) for Linux, Windows, and Solaris Operating System (SPARC 64-Bit) Part Number E16640-11 |
|
|
PDF · Mobi · ePub |
This module contains the following types of information regarding mobility in Oracle Beehive:
This section contains general information about Oracle Beehive and its support of mobile devices, and includes the following topic:
Oracle Beehive Release 1 (1.5) supports XMS mode and SMPP mode for configuring SMS messages. However, future releases of Oracle Beehive will not support XMS mode. Therefore, Oracle recommends that you use SMPP mode when configuring SMS messages for your deployment.
This section contains known limitations and workarounds with mobility in Oracle Beehive, and includes the following topic:
ASK Service Unresponsive When Fetching Large Numbers of Offline Messages
Time Changes May Cause Inaccurate Time-based Data on Sony Ericsson Devices
Sony Ericsson W580i (JP7) Does Not Support Alphabetic Characters in Phone Numbers
Oracle Beehive Unable to Provision Nokia and Sony-Ericsson Phones Over Nonstandard SSL Ports
Byte Size of Messages Twice as Large Through Oracle Beehive Mobile Push Mail Client
Oracle Beehive Does Not Differentiate Between Required and Optional Attendees in Windows Mobile
Upgrading Oracle Beehive Overrides Custom Mobile Device Profile Settings
Bug 9932026. Fetching a large number of offline messages using the ASK service results in a DB socket timeout after 5 minutes. This results in a thread block for 5 minutes whenever the ASK service queries for offline messages.
Bug 6919722. Sony Ericsson Java Platform devices do not correctly adjust for Daylight Savings time changes and changes between time zones. As a result, time-based data, such as meeting times, may differ by one hour after you change your clock to or from Daylight Savings time, or after you travel to a new time zone. To avoid this limitation, you should delete all calendar entries before the time change and fully refresh your device after the change, as described by the following procedure.
Note:
The steps described in the following procedure may differ slightly depending on the model name and number of your Sony Ericsson device.To ensure that your Sony Ericsson device displays the correct time and time-based data, complete the following steps:
Before the Daylight Savings time change or traveling to a new time zone, synchronize your mobile device.
From the Organizer menu on your device, select Calendar, then Advanced, and 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 occurs, or after you enter a new time zone, check 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 before returning to your original time zone or before you leave for another time zone.
Bug 7114363. The Sony Ericsson W580i (JP7) mobile device does not support alphabetic characters in phone numbers. For example, the phone number "1800SAFEWAY" is not supported. This is a known device limitation.
This limitation is relevant to Oracle Beehive in cases where users enter alphabetic characters in phone numbers through their desktop clients, such as for contacts in Oracle Beehive Extensions for Outlook, and subsequently synchronize their Sony Ericsson W580i (JP7) devices. In these cases, any alphabetic characters in phone numbers will not synchronize to the mobile devices and only numeric characters will appear. For example, if a user enters "1800SAFEWAY" in an Oracle Beehive client and synchronizes to the Sony Ericsson W580i (JP7) device, only "1800" will appear on the device.
Bug 6966867. Oracle Beehive cannot provision Nokia and Sony-Ericsson phones if the SSL ports for the IMAP (port 993) and SMTP (port 465) services are nonstandard, that is, if the SSL ports for these services are different than the expected default settings.
To resolve this issue on Nokia phones, complete the following steps:
Configure the phone's IMAP setting by navigating through the following menu options: Mailbox>Options>E-mail settings>Connection Settings>Incoming E-mail>Security (Ports). In the Security (Ports) screen, select SSL/TLS and enter the number of the nonstandard port for your deployment.
Configure the phone's SMTP setting by navigating through the following menu options: Mailbox>Options>E-mail settings>Connection Settings>Outgoing E-mail>Security (Ports). In the Security (Ports) screen, select SSL/TLS and enter the number of the nonstandard port for your deployment.
To resolve this issue on Sony-Ericsson phones, complete the following steps:
Configure the phone's IMAP setting by navigating through the following menu options: Messaging>Email>Settings>Account Settings>Beehive>More>Edit Account. In Edit Account screen, scroll down to Encryption and select Incoming Server. In the Incoming Server screen, select SSL and enter the number of the nonstandard port for your deployment.
Configure the phone's SMTP setting by navigating through the following menu options: Messaging>Email>Settings>Account Settings>Beehive>More>Edit Account. In Edit Account screen, scroll down to Encryption and select Outgoing Server. In the Outgoing Server screen, select SSL and enter the number of the nonstandard port for your deployment.
Bug 7353473. The Oracle Beehive Mobile Push Mail client uses Unicode to display messages on users' mobile devices. Therefore, in terms of the size measured in total bytes, messages displayed by the Oracle Beehive Mobile Push Mail client will typically be twice as large as those displayed by other supported Oracle Beehive clients.
When viewed through Microsoft Windows Mobile software on supported mobile devices, meeting or event attendees will appear as "required", even if they were designated as "optional" when the meeting was created. This limitation applies to all supported versions of Microsoft Windows Mobile when used with Oracle Beehive.
Bugs 8556534, 8556595, and 8571953. Upgrading to a subsequent release of Oracle Beehive overrides any custom settings that are present in the mobile device profiles for your deployment. If this occurs, reload those settings after the upgrade process concludes.
This section contains known issues with mobility-related services, features, and functionality, and includes the following topics:
Mobile Data Sync Service May Convert an All-Day Meeting to a Day Event in Sony Ericsson Devices
Mobile Data Sync Service Does Not Synchronize Day Event Reminders to Oracle Beehive
Synchronization Limited to One-Way on Nokia 40 Series Mobile Devices
Bug 6414080. When synchronized with Sony Ericsson Symbian devices, the Mobile Data Sync Service may convert an All-Day meeting that to a Day event. All-day meetings have a start time of 12:00 a.m. on one day and an end time of 12:00 a.m. on the following day.
Bug 6367501 and 6315167. The Mobile Data Sync Service does not synchronize reminders on Day events created on mobile devices. If a reminder exists on a Day event created on the device, the reminder will be lost after synchronization.
Bug 6912769. Currently, Nokia 40 Series phones deployed with Oracle Beehive only support one-way synchronization (from server to device). Two-way synchronization cannot presently be supported as the Nokia OMA-DS client begins to falsely report modifications after repeated use.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
