| Oracle® Beehive Release Notes Release 1 (1.5) Part Number E14829-08 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.5) Part Number E14829-08 |
|
|
View PDF |
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 mobile client applications include language packs and their translation files, which are automatically uploaded during the Oracle Beehive installation process. You can customize the language packs that Oracle Beehive provides as well as others that it does not.
This section contains the following topics related to customizing language packs for mobile client applications:
Mobile Client Application Language Packs Provided by Oracle Beehive
Customizing Language Packs and Translation Files for Oracle Beehive Mobile Client Applications
Oracle Beehive provides the following language packs for its mobile client applications:
Chinese (Simplified)
Chinese (Traditional)
French
German
Italian
Japanese
Korean
Portuguese (Brazilian)
Spanish
To customize the translation files of a language pack, please refer to "Customizing Language Packs and Translation Files for Oracle Beehive Mobile Client Applications".
To customize a language pack, you modify one or more of its translation files. You then upload the customized translation files using one of the following containers:
A patch set: Used for language packs provided by Oracle Beehive. For more information, please refer to "Creating and Uploading a Patch Set for a Language Pack Provided by Oracle Beehive".
A new language pack: Used for language packs that are not provided by Oracle Beehive. For more information, please refer to "Creating, Uploading, and Provisioning a Language Pack Not Provided by Oracle Beehive".
Note:
For the list of language packs that Oracle Beehive provides, please refer to "Mobile Client Application Language Packs Provided by Oracle Beehive".Creating and Uploading a Patch Set for a Language Pack Provided by Oracle Beehive
To customize the translation files for a language pack provided by Oracle Beehive, you create and upload a patch set.
To create and upload a patch set:
Modify the translation file of a supported language pack, as follows:
Access the zip file of the mobile client application, located in the $ORACLE_HOME/beehive/seed/dm directory. For example, the translation files for the Mobile Mail plug-in for Windows Mobile devices appear in pushmail_release.PPC5.0_ARM.element.zip.
From the zip file, open the XLIFF file for one of the languages that Oracle Beehive supports by default. For example, the French translation file for the Mobile Mail plug-in is oracle.ocs.mobileclient.wince.pushmail_fr.xlf.
Modify the translation strings in the file, as needed.
Save the file in UTF-8 encoding. All XLIFF files must be UTF-8 encoded.
Repeat these steps as necessary for the translation files for other languages.
Create a new zip file that contains all customized translation files. Ensure that the new zip file is located in an Oracle Beehive directory that is accessible by the Oracle user.
Create a new metadata.xml to describe the new patch set, as follows:
Access the existing zip file of the mobile client application, located in the $ORACLE_HOME/beehive/seed/dm directory.
From the zip file, open metadata.xml.
Increment the value of the <patchsetnumber> attribute so that it is higher than the current value. All other attributes under the <property> element should remain the same as distributed in the original metadata.xml file.
For example, a metadata.xml for a patch set targeted towards Windows Mobile 5.0 devices and that contains customized French and Japanese translation files will look similar to the following:
<?xml version="1.0" encoding="UTF-8"?>
<application>
<property>
<name> Mobile Mail </name>
<description> MobileMail Client </description>
<os> wince5.0 </os>
<processor>ARM </processor>
<deviceclass> Smartphone </deviceclass>
<language> all </language>
<version> 1.4.0.0.0. </version>
<versionnumber> 4 </versionnumber>
<patchsetnumber> 1 </patchsetnumber>
<vendor> Oracle </vendor>
<isPlatform> false </isPlatform>
</property>
<modules>
<module>
<name> oracle.ocs.mobileclient.wince.pushmail_fr.xlf </name>
<src> . </src>
<dest> %CSIDL_WINDOWS% </dest>
<contenttype> text/xml</contenttype>
</module>
<module>
<name> oracle.ocs.mobileclient.wince.pushmail_ja.xlf </name>
<src> . </src>
<dest> %CSIDL_WINDOWS% </dest>
<contenttype> text/xml</contenttype>
</module>
</modules>
</application>
Save the new metadata.xml.
Add the new metadata.xml to the zip file created in Step 2.
Upload the new patch set, as follows:
Launch the beectl command line utility.
Issue the upload_client_application command, as follows:
beectl> upload_client_application --file <file>
Where <file> represents the absolute path of the zip file that you created in Step 2.
Creating, Uploading, and Provisioning a Language Pack Not Provided by Oracle Beehive
To customize the translation files for a language pack not provided by Oracle Beehive, you create a new language pack based on an existing one. Once created, you can upload and provision the new language pack.
To create, upload, and provision a new language pack:
Modify the translation file of a supported language pack with the strings required in the new language pack, as follows:
Access the zip file of the mobile client application, located in the $ORACLE_HOME/beehive/seed/dm directory. For example, the translation files for the Mobile Mail plug-in for Windows Mobile 5.0 devices appear in pushmail_release.PPC5.0_ARM.element.zip.
From the zip file, open the XLIFF file for one of the languages that Oracle Beehive supports by default. For example, the French translation file for the the Mobile Mail plug-in is oracle.ocs.mobileclient.wince.pushmail_fr.xlf.
Modify the translation strings, as needed.
Modify the target-language attribute to specify the new target language and country. For example, if you modify the French translation file for the Mobile Mail plug-in with Danish strings, change the target-language attribute from "fr-FR" to "dk-DK".
Rename the XLIFF file by replacing the original language code with the new language code and, if appropriate, the new country code.
Note:
XLIFF file naming conventions follow the Java standard, which supports a two-letter lowercase language code (ISO 639) and a two-letter uppercase country code (ISO 3166). For example, if you modify the French translation file for the Mobile Mail plug-in with Danish strings, rename the file and save it in UTF-8 encoding asoracle.ocs.mobileclient.wince.pushmail_dk.xlf. Or, if you create a Canadian French translation file, save it as oracle.ocs.mobileclient.wince.pushmail_fr_CA.xlf.Create a new zip file that contains all customized translation files. Ensure that the new zip file is located in an Oracle Beehive directory that is accessible by the Oracle user.
Create a new metadata.xml to describe the new language pack, as follows:
Access the existing zip file of the mobile client application, located in the $ORACLE_HOME/beehive/seed/dm directory.
From the zip file, open metadata.xml.
Replace the values of the <name> and <description> attributes with the name and description of the new language pack. All other attributes under the <property> element should remain the same as distributed in the original metadata.xml file.
For example, a metadata.xml for a language pack targeted towards Windows Mobile 5.0 devices and that contains customized Danish translation files will look similar to the following:
<?xml version="1.0" encoding="UTF-8"?>
<application>
<property>
<name> Mobile Mail Langugage Pack - DK </name>
<description> MobileMail Client Danish Language Pack</description>
<os> wince5.0 </os>
<processor>ARM </processor>
<deviceclass> Smartphone</deviceclass>
<language> all </language>
<version> 1.4.0.0.0. </version>
<versionnumber> 4 </versionnumber>
<patchsetnumber> 0 </patchsetnumber>
<vendor> Oracle </vendor>
<isPlatform> false </isPlatform>
</property>
<modules>
<module>
<name> oracle.ocs.mobileclient.wince.pushmail_dk.xlf </name>
<src> . </src>
<dest> %CSIDL_WINDOWS% </dest>
<contenttype> text/xml</contenttype>
</module>
</modules>
</application>
Save the new metadata.xml.
Add the new metadata.xml to the zip file created in Step 2.
Upload the new language pack, as follows:
Launch the beectl command line utility.
Issue the upload_client_application command, as follows:
beectl> upload_client_application --file <file>
Where <file> represents the absolute path of the zip file that you created in Step 2.
Provision the new language pack, as follows:
In the beectl command line utility, issue the list_enterprises command to 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.
Issue the add_client_application_provisioning command to provision the language pack to the enterprise:
beectl> add_client_application_provisioning --community <id> --all
Where <id> represents the enterprise identifier
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 SMMP mode when configuring SMS messages for your deployment.
Note:
This issue is resolved in Oracle Beehive Release 1 (1.5.1.1) and later.Bug 8466463. Oracle Beehive Release 1 (1.5.1.0) supports SMS message delivery to users in the United States and Canada only.
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 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 Non-standard 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 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.
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 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-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 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.
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 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.
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.
Bug 8439781. If brackets, that is [ or ], exist in SMS messages that are sent to users through service providers based outside of the United States, they will be replaced by other characters. This will give the appearance that the messages have been corrupted, when, in fact, only the brackets were replaced.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|