| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
This module contains the following types of information regarding mobility in Oracle Beehive:
This section contains known limitations and workarounds with mobility in Oracle Beehive, and includes the following topic:
Time Changes May Cause Inaccurate Time-based Data on Sony Ericcson Devices
Uploading Language Packs for Oracle Beehive Mobility Services
Sony Ericsson W580i (JP7) Does Not Support Alphabetic Characters in Phone Numbers
Oracle Beehive Unable to Provision Nokia and Sony-Ericcson Phones Over Non-standard SSL Ports
Byte Size of Messages Twice as Large Through Oracle Beehive Mobile Push Mail Client
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 prior to a 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:
Prior to a 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 prior to returning to your original time zone or before you leave for another time zone.
Language packs for Oracle Beehive mobile clients are not automatically uploaded during installation. These language packs must be uploaded to Oracle Beehive.
To upload language packs for Oracle Beehive Mobility Services:
Navigate to the following directory:
$ORACLE_HOME/beehive/tmp/langpack/langpack/xliff/built-in
Create a ZIP file containing all the files that begin with the following string:
oracle.ocs.mobile.mobileclient
Note:
The ZIP file must have a
.zip extension.Create a metadata.xml file that contains the following text:
<?xml version="1.0" encoding="UTF-8"?>
<application>
<property>
<name> Langpack </name>
<description> Mobile LangPack for 11</description>
<os> wince5.0 </os>
<processor>ARM </processor>
<deviceclass> PPC </deviceclass>
<language> en </language>
<version> R1 </version>
<versionnumber> 1 </versionnumber>
<patchsetnumber> 1 </patchsetnumber>
<vendor> Oracle </vendor>
</property>
<modules>
<module>
<name> <filename> </name>
<src> . </src>
<dest> %CSIDL_WINDOWS% </dest>
<contenttype> text/xml</contenttype>
</module>
</modules>
<configuration>
<param name="pushmailchannel" value="MobileMailServer"/>
<param name="accountname" value="Beehive" />
</configuration>
</application>
Where <filename> represents the name of one of the language pack files added to the ZIP file in Step 2.
Note:
The above text is for Pocket PC devices. Formetadata.xml text specific to Smartphone devices, refer to Step 11.Add a new <module> section for every file that was added to the ZIP file in Step 2. Use the <module> section in the metadata.xml file created in Step 3 as a template: replacing <filename> with the name of each file.
Note:
The<module> sections must be added between the <modules>, and <\modules> tags.Save the metadata.xml file.
Add the metadata.xml file to the ZIP file created in Step 2.
Using the upload_client_application beectl command, upload the language pack to Oracle Beehive:
beectl> upload_client_application --file <file>
Where <file> represents the absolute path of the ZIP file created in Step 2.
Using the list_enterprises beectl command, determine the identifier of the Oracle Beehive enterprise:
beectl> list_enterprises --entity_format id
Take note of the identifier of the enterprise to which the language pack will be provisioned.
Using the add_client_application_provisioning beectl command, provision the language pack to the enterprise:
beectl> add_client_application_provisioning --community <id> --all
Where <id> represents the enterprise identifier noted in Step 9.
Follow Steps 1 through 10 again for the Smartphone devices. Replace the text of the metadata.xml in Step 3 with the following text:
<?xml version="1.0" encoding="UTF-8"?>
<application>
<property>
<name> Langpack </name>
<description> Mobile LangPack for 11</description>
<os> wince5.0 </os>
<processor>ARM </processor>
<deviceclass> Smartphone </deviceclass>
<language> en </language>
<version> R1 </version>
<versionnumber> 1 </versionnumber>
<patchsetnumber> 1 </patchsetnumber>
<vendor> Oracle </vendor>
</property>
<modules>
<module>
<name> <filename> </name>
<src> . </src>
<dest> %CSIDL_WINDOWS% </dest>
<contenttype> text/xml</contenttype>
</module>
</modules>
<configuration>
<param name="pushmailchannel" value="MobileMailServer"/>
<param name="accountname" value="Beehive" />
</configuration>
</application>
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 Integration 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-Ericcson phones if the SSL ports for the IMAP (port 993) and SMTP (port 465) services are non-standard, 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 non-standard 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 non-standard port for your deployment.
To resolve this issue on Sony-Ericcson 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 non-standard 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 non-standard port for your deployment.
Bugs 7130951 and 7216967. Oracle Beehive does not yet support the following mobile devices:
Motorola Razr2 V9
Nokia 6665B (S40)
Sony-Ericcson W580I (JP7)
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.
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 May Incorrectly Synchronize Events to 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 6413555. When an event has previously been synchronized with Oracle Beehive using the Mobile Data Sync Service, and is subsequently modified on Oracle Beehive, if a slow synchronization is performed, the event will no longer appear on the Sony Ericsson device.
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.
Note:
This issue is resolved in Oracle Beehive Release 1 (1.3) and later.Bug 6943834. Users of mobile devices with data stores that contain more than 1,000 items may be unable to synchronize with Oracle Beehive due to premature timeouts.
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.
