Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
 
 
 
 
 
Support > Technical Documents > Document Types > Release Bulletin > Release Bulletin Unwired Accelerator 7.0 for Linux...

Release Bulletin Unwired Accelerator 7.0 for Linux on POWER

Documents known problems and changes to installation, functionality, and documentation for Unwired Accelerator 7.0 for Red Hat Enterprise Linux Advanced Server v4.0, SuSE Linux Enterprise Server (SLES) 9.0. See 'Product Summary' for details.
 
RSS Feed
 
 
 

Release Bulletin Unwired Accelerator 7.0 for Linux on POWER

 

Document ID: DC00458-01-0700-02

Last revised: February 16, 2007



Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase Product Manuals Web site.

Accessing release bulletins at the Sybase Product Manuals Web site
  1. Go to Product Manuals.

  2. Select a product and language and click Go.

  3. Select a product version from the Document Set list.

  4. Select the Release Bulletins link.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.



Product summary

Enclosed is Unwired Accelerator, which is compatible with these platform and operating system configurations:

  • Red Hat Enterprise Linux Advanced Server 4.0

  • SuSE Linux Enterprise Server (SLES) 9.0

  • Mobile Web Studio runs on Internet Explorer versions 5.5 + and 6.0+

  • Portal Interface runs on:

    • Internet Explorer version 5.5 Service Pack 2 with patches: Q319182, Q321232, Q328389, Q810847, Q323759, Q824145, Q823980, Q822925, Q312461, Q818529, Q330994

      Internet Explorer version 6.0 Service Pack 1 with patches: Q827667, Q828750, Q330994, Q822925, Q824145, Q824145, Q832894, Q837009, Q831167, Q823353, Q833989

    • Netscape version 7.01+


Version contents

The Unwired Accelerator packaging includes:

  • Media

    • Getting Started with Unwired Accelerator 7.0 CD

    • SyBooks™ CD – Unwired Accelerator

    • SyBooks CD – Adaptive Server™ Enterprise

    • Unwired Accelerator 7.0 CD

    • Adaptive Server Enterprise CD

  • Documentation

    • Unwired Accelerator Installation Guide for Linux on POWER

    • Unwired Accelerator Release Bulletin for Linux on POWER

    • Online help text

The Getting Started with Unwired Accelerator 7.0 CD contains these manuals:

  • The Unwired Accelerator release bulletin (this document) for your platform contains up to date information not documented elsewhere.

  • The Unwired Accelerator installation guide contains installation instructions.

  • The Unwired Accelerator Quick Start Guide shows how to deploy a Web and database application to either a PDA or BlackBerry device.

  • Adaptive Server Enterprise documents – Unwired Accelerator 7.0 includes the ASE database to store system information including security authentication and authorization information.

  • The SyBooks Installation Guide describes how to install SyBooks.

  • jConnect for JDBC Release Bulletin – Unwired Accelerator 7.0 includes the jConnect™ for JDBC™ driver to allow JDBC access to Sybase database servers and gateways.

The Unwired Accelerator SyBooks CD contains these documents:

  • The Mobile Application Development Tutorial provides tutorials that help you get started using Mobile Web Studio to develop and deploy mobile applications.

  • Portal Interface User’s Guide – describes the Portal Interface user interface and how to use Portal Interface to build and manage your content.

  • Unwired Accelerator Developer’s Guide – describes how to develop and deploy applications, portals, and their associated components, such as pages, catalogs, and so on.

  • Unwired Accelerator Administration Guide – provides administration topics for Unwired Accelerator and its components.

  • jConnect for JDBC documents – Unwired Accelerator 7.0 includes the jConnect for JDBC driver to allow JDBC access to Sybase database servers and gateways. The Programmer’s Reference jConnect for JDBC is included on the SyBooks CD.

These manuals are also available online at Product Manuals in PDF and HTML formats.



Special Instructions

describes any special instructions for Unwired Accelerator.


Daylight Saving Time patch

Starting in 2007, the Daylight Saving Time (DST) rules are changing in the United States and Canada. DST now begins on the second Sunday of March and ends on the first Sunday of November. To ensure that your UA installations continue to function correctly, you must install a Java patch.

Installing the Java DST Patch for IBM
  1. Download JTZU as a single .zip package from the IBM developerWorks site http://www-128.ibm.com/developerworks/java/jdk/dst/index.html. Use binary transfer mode where applicable.

    The readme file is http://download.boulder.ibm.com/ibmdl/pub/software/dw/jdk/dst/readme.htm.

  2. Create a directory for the files used to run JTZU. For example, /tmp/jtzu or c:\jtzu.

  3. Unzip the JTZU package into the directory you crated. Use the jar utility where available:

    		jar -xvf <filename>	
    	
  4. On AIX, z/OS, Linux, Solaris, and HP-UX platforms, you must set the executable bit for the utility. At a shell prompt, type:

    		chmod 755 runjtzu.sh	
    	
  5. Set the value of NOGUI in the JTZU Settings file to false. The DISCOVERONLY setting is not used.

  6. Run JTZU by executing runjtzu.cmd on OS/2 platforms, or runjtzu.sh on other platforms.

  7. In response to the prompt, select Interactive mode and click Start.

  8. Enter the location of the JRE in the text box or use the Browse button to select the location.

  9. Click Update to perform the time zone update for the selected JRE.



Changed functionality in this version

This section describes new features, enhancements, and changed functionality in this version.


New features and enhancements

This section discusses new features and enhancements to existing features.

  • SAP support – allows mobile users who have BlackBerry, PocketPC, or Palm devices to access their SAP business applications from their devices in an “always-available” model.

  • BlackBerry server and client improvements, which include:

    • The ability to set up multiple profiles on the BlackBerry device, which allows users to:

      • Define multiple settings

      • Give a logical name to the profile definition

      • Select which sync profile to use when a SyncAll is performed

      • Create new settings, and update and delete existing settings

      • Group available applications based on the profile name

    • The ability to have a mobile portal using the BlackBerry browser on devices connected with an Mobile Data Services (MDS) module residing on the BlackBerry Enterprise Server.

    • Data “chunking” so that users can sync applications larger than 128K as long as the BlackBerry has sufficient available memory.

      Note:To use this functionality, you must ensure that cookies are enabled on the BlackBerry Enterprise Server. See your BlackBerry documentation.

    • Menu enhancements, which include:

      • Search – users can perform searches in all available rows and columns.

      • Logs – users can view the update log to see if the update was successful.

      • Fix Update – if an update request fails, the user can fix the error by highlighting the log record and selecting Fix Update.

      • Sync Update – allows users to sync update changes only. When a form submission is sent to the sever, only the update changes are synced—not the application content.

      • The ability to insert multilevel records on BlackBerry and PDA devices.

  • Introduction of .NET client – the .NET client software enables you to deploy mobile applications from Unwired Accelerator to Windows mobile PDAs. You can customize the client from the PDA, or create a custom client template to download to PDAs, and further customize. The .NET client software requires:

    • NET Compact Framework 1.0 Service Pack 3 – service pack installed to the mobile device’s memory and used with .NET Compact Framework.

    • ASA for CE – database installed on the mobile device used to store mobile applications and system data.

    • Unwired Accelerator 7.0 .NET client – software installed on the mobile device and used to communicate with Unwired Accelerator server.

    The .NET client replaces the M-Business server and client functionality with Unwired Accelerator for Linux on POWER.

  • Capture and playback enhancements, which include:

    • A capture strategy that makes use of the Document Object Model used by many browsers when displaying HTML page content.

    • The ability to use @OP tags as part of the URL to be altered during playback.

    • Improved JSESSION ID handling, which ensures that URLs sent in CCL playback are consistent with the actual JSESSIONID value.

  • Data validation – allows you to enter regular expressions to validate data you enter for tabular data applications.

  • Edit – improved ability to edit applications.

  • Pocket PC – the List/Detail functionality is now available on the Pocket PC.

  • Support for the Windows NT LAN Manager (NTLM) protocol, an authentication protocol used by the Microsoft IIS servers.

  • Graphical user interface installer.

For details about features, see the Unwired Accelerator Developer’s Guide.


Unsupported features

Some Unwired Accelerator features are not supported in Unwired Accelerator 7.0 for Linux on POWER, either because the features cannot be ported or because comparable features have replaced original features for Linux on POWER.


Summary of features

In summary, these features include:

  • Adaptive Server Anywhere – Unwired Accelerator uses ASA as persistent storage. For Linux on POWER, Adaptive Server Enterprise, Enterprise Edition replaces ASA for persistent storage.

    Note:One exception is that the .NET client configuration deploys ASA on CE for data storage on the mobile device.

  • M-Business Anywhere – M-Business server and client software is used to deploy mobile applications to mobile devices. For Linux on POWER, the .NET Framework and client software is introduced to replace M-Business Anywhere (the BlackBerry server and client remain for deploying mobile applications to BlackBerry devices).

  • Answers Anywhere – Answers Anywhere is a search engine available when Unwired Accelerator is installed on a Windows machine. For Linux on POWER, this feature is not available.

    • On the mobile device, the “AskUA” menu option, which enabled you to search across applications, has been removed from the mobile device client application (you can search within an application with both the BlackBerry and .NET clients). The “Save Question/Answer” and “History” menu options have also been removed.

    • In Mobile Web Studio, the Answers Anywhere option on the Application Properties tab still appears, but is not enabled.

  • EAServer – For Linux on POWER, an EAServer configuration is not available.

Note:The online help, software, and documentation include references to these features. Ignore these references, and substitute comparable features for Linux on POWER, as described in “Documentation and unsupported features”.


Sample databases

The sample database (sampledb), which is used in many of the tutorials in the Mobile Application Development Tutorial has been ported to Linux on POWER. However, some stored procedures, specifically those associated with ASA but not used with Unwired Accelerator, have not been ported. You may see evidence of the stored procedures in the software, but they are not available [CR #423206-1].

Other sample databases, such as mpharma and msales, have not been ported to Linux on POWER. In the documentation, you may see screen shots that include these other sample databases, or references to them in the text, but they are not available. The tutorials in the Mobile Application Development Tutorial do not use these sample databases [CR #423206-1].


Change in import/export functionality

In earlier versions, you could deploy a JSP application into an EAR file that contained multiple WAR files and application definition files using Import/Export. This functionality is no longer available. To deploy a JSP application into an EAR file, you must now use the application server.

Deploying a JSP application into an EAR file
  1. Export the JSP applications to an XML file.

  2. Create a separate WAR file for each JSP application.

  3. Import the XML file.

  4. Deploy the WAR file to the application server (Tomcat).



Known problems

See the latest release bulletin for Unwired Accelerator 7.0 for additional known problems. You can find the latest release bulletin at the Sybase Product Manuals Web site.


Installer

This section describes known problems for the Unwired Accelerator installer.


Installation fails if there is not enough space in the temporary directory

[CR #414509] The installer does not verify that enough space is available in the temporary directory. If there is not enough space, the installer does not launch.

Workaround: Free up space in the temporary directory.


Re-installation problems after deleting Unwired Accelerator files

Sybase provides an Uninstaller for cleanly removing Unwired Accelerator from Linux on POWER. If you remove Unwired Accelerator by deleting the installation directory instead, and then reinstall Unwired Accelerator, you will encounter problems with the reinstallation.

Workaround: If you encounter problems with the reinstallation, you must remove the vpd.properties file to clean up the machine.

WARNING! Deleting the vpd.properties is a last resort and not recommended, since you will lose all information about any previous InstallShield installations performed on the machine.

  1. Uninstall Unwired Accelerator again using instructions in the Unwired Accelerator Installation Guide.

  2. Remove the vpd.properties file located in:

    ~<user id>/InstallShield/Universal/common/Gen1/_vpddb

  3. Try the installation again using instructions in the Unwired Accelerator Installation Guide.


Adaptive Server Enterprise

This section describes known problems for using Adaptive Server Enterprise with Unwired Accelerator.


Adaptive Server Enterprise performance tuning

[CR #428851] While stress testing Unwired Accelerator for Linux on POWER at 1000 users, testers noted Adaptive Server Enterprise consuming 100% CPU. Making changes to several configuration settings alleviated the problem.

Workaround: If you note high CPU usage, try the following to improve Adaptive Server Enterprise performance:

  • Modify configuration parameters:

    • sp_cacheconfig – increase the default data cache to 200MB:

      sp_cacheconfig "default data cache", "200M"

    • sp_configure – lower the runnable process search count from 2000 to 3:

      sp_configure "runnable process search count", 3

  • The following sp_configure changes may yield additional, minor performance improvements:

    • Increase the procedure cache by about 1/2 MB per user, maybe a little less:

      sp_configure "procedure cache", 150000

    • Increase the number of CPUs with which Adaptive Server Enterprise starts up, to 2 or more: sp_configure "number of engines at startup", 2

  • The following sp_configure changes were not tested in this situation, but may also improve Adaptive Server Enterprise performance when used with Unwired Accelerator for Linux on POWER:

    sp_configure "max parallel degree, 2" sp_configure "max scan parallel degree", 2 sp_configure "sort buffers", 5000 sp_configure "stack size", 393216 sp_configure "number of open objects", 2000 sp_configure "user logs cache size", 8192

See the Adaptive Server Enterprise documentation on the Getting Started CD for more information about Adaptive Server Enterprise commands and performance tuning.


Mobile Web Studio

This section describes known problems with Mobile Web Studio.


Advanced Navigation does not work

[CR #421265] The Advanced Navigation option in the New Web Element window, which enhances the ability to capture Active-X, is not supported on Linux for POWER.

Workaround: None.


DOM format does not work

[CR #405306] The DOM format option in the New Web Element window does not work. This option is used with the Advanced Navigation option, which is not supported on Linux on POWER.

Workaround: None.


Chart application does not display correctly

[CR #406252] Chart applications do not display on Windows browsers.

Workaround:

  1. Open a new terminal window, and log in to the Linux machine that is running Unwired Accelerator.

  2. Set the DISPLAY environment variable to any of the Windows machines by entering (where <machine name> is the name of the Windows machine):

    		setenv DISPLAY <machine name>:0.0	
    	
  3. Restart the application server (Tomcat).


Charting problems in Linux on POWER

[CR #422932] Charting does not work properly on Linux machines that do not have X11 installed.

Workaround: Modify the starttomcat.sh script.

  1. Navigate to $SYBASE.

  2. Use a text editor to open starttomcat.sh.

  3. Add the following lines to the file:

    		CATALINA_OPTS=-Djava.awt.headless=true export CATALINA_OPTS	
    	
  4. Save the file and close it.

  5. Restart the application server (Tomcat).


List/Detail view does not display properly after syncing to offline BlackBerry client

[CR #393332] When creating a database application, then syncing to the BlackBerry offline client, the List/Detail view does not display properly.

Workaround: Edit the application properties in List/Detail view and specify the width for all the columns to a desired value in the List Text window.


Authorization fails if you are assigned more than 20 roles

[CR #371033] You cannot access any Mobile Web Studio objects if you are assigned more than 20 Mobile Web Studio roles. This limitation is caused by the user’s database table. The column that holds all assigned roles to a user is limited to 255 bytes.

Workaround: None.


Changes not propagated to the device during sync

[CR #371766] When you create a Web application and capture links and text on a page, then sync the application to your BlackBerry device, the device shows the links along with the text of the captured content. When you edit the List/Detail property for the application to display only the text, then sync the application, the changes are not propagated to the device–the links still display.

Workaround: Specify the width setting in the List/Detail pane for each field.


“500 exception” error received during SMS registration

[CR #374529] If too many simultaneous registration attempts are made, you may receive a “500 exception” error during Short Message Service (SMS) registration.

Workaround: Try registering again.


Double-byte character sets display incorrectly if there is an @OP tag in the URL

[CR #371799] When performing a capture from a source with an @OP tag in the URL, double-byte character sets do not display correctly.

Workaround: None.


Set charset to UTF-8 if content contains special characters

[CR #361553] When the contents of an application grid contain special characters like ® or ’, the XML breaks.

Workaround: Set the charset of applications to UTF-8 if the contents contain special characters.


Data is sorted by default when displaying mobile applications on PalmOne Zire72

[CR #361561] When displaying mobile applications on a PalmOne Zire72 in offline mode, by default the data on the table is sorted alphanumerically using the first field in the table, and the table layout of the original content is not maintained. For example, this:

Table 1: Expected result

Emp name

Salary

Ann

500

Karen

300

Val

450

Total

1250

displays like this:

Table 2: Actual result

Ann

500

Emp name

Salary

Karen

300

Total

1250

Val

450

Workaround: None.


You can define only one event in applications with multiple elements

[CR #361645] If an application includes more than one element you can define events only on one of the elements. You can select each element for event definition, but only the last event defined is saved and used.

Workaround: None.


Alert messages that use SMS support not sent if size limit is exceeded

[CR #361562] When you select the Include Message box from Agent Builder | Add | Notify | SMS and enter a message in the field that displays, if the message exceeds the size limit, the message is not sent. This is expected behavior.

Workaround: When you enter a message for an alert that uses Short Message Service (SMS) support, do not exceed the size limit of 110 characters.


Multilayered XML content does not display correctly

[CR #360262] The content for multilayered XML applications does not display correctly. For example, if the Symbol value is “AFRT” and the Name is “American Fire Re,” the application displays some numerical values for both fields.

Workaround: Customize a content XSLT template to filter out the Web service response. The customized template can be used for the Web services response with one layer of XML content since you are mapping the XML structure to a grid structure.

The content XSLT should ensure that the output XML is in this format:

<data><Record><Field op_label="col1" op_position="1">Data11</Field><Field op_label="col2" op_position="2">Data12</Field></Record><Record><Field op_label="col1" op_position="1">Data21</Field><Field op_label="col2" op_position="2">Data22</Field></Record></data>

Users created in LDAP server must activate their profile

[CR #359766] When a user is created in the LDAP server, the user’s profile is not created until the user logs in to Portal Interface. The user’s information cannot be changed or saved from Web Studio Manage | Portal | Users.

Workaround: The user must log in to Portal Interface.


Join Now link displays on some Smartphones

[CR #360133] When you are working in connected mode on some Smartphones and the session expires, you may see Join Now links even though self-registration is not applicable. The browser on these devices may have a limitation where old session IDs are cached too long.

Workaround: Ignore these links, restart the browser, and go to the login page again.


HTTPS not supported on Smartphones

[CR #360928] Cannot access the portal using HTTPS from Smartphones. For example, the following does not work:

https://<hostname>.sybase.com:8443/onepage/mp.jsp?rid=1 .

Workaround: Use HTTP for accessing applications on Smartphones. For example:

http://<hostname>.sybase.com:4040/onepage/mp.jsp


Secure applications do not function properly on Smartphones

[CR #360934] Secure applications do not function as expected on Smartphones. For example, the user is not prompted for a password.

Workaround: None.


Raw XML data displays when saving XSL

[CR #335024] When you create a document element with an XML file, then select an XSL file, save it, and preview it, it displays with raw XML data. No transformation occurs.

Workaround: Use the embedded XSL directive in your XML file and the browser to perform the transformation.


When deleting applications, dependencies on agents are not checked

[CR #356299] When an application is deleted, it checks for dependencies on pages, page groups, catalogs, and applications, but it does not check for dependencies on agents. Therefore, you can delete applications with dependencies on agents without getting a warning, and the agent containing the application continues to run and send alerts to users.

Workaround: The administrator must remove the application from the agent’s rule and action.


XML validation must be turned off for the import and export functionality to work

[CR #355835] If XML validation is turned on in global.properties.xml, when you export only applications, or all entities, then perform an import, you receive a connection error: java.lang.NullPointerException.

Workaround:

  1. Open global.properties.xml in a text editor. If you are using Tomcat, the default location of this file is $SYBASE/tomcat/webapps/onepage/config.

  2. Find <Property name=”XmlValidation”> and verify that the value is set to “off.” If not, change it.

  3. Save the file and close the text editor.

  4. Restart the application server.


Updating pages and page groups

[CR #346402] Pages and page groups do not update correctly.

Workaround: Using any text editor, open the global.properties.xml file. If you are using Tomcat, the file is located in $SYBASE/onepage/config/global.properties.xml.

Search for “deferupdate,” and change the value to “on” so it looks like this:

Property name=“deferupdate” value=“on” description=“on/off”

Save and close the file.


Server-side click-across application does not display correctly

[CR #361665] When an application with server-side click-across is linked to an application with two database elements, the server-side click-across application does not display correctly.

Workaround: To use server-side click-across, the linked application must be a single-element application.


Error message does not display when entering wrong information

[CR #386173] If you preview a linked application in Application Builder with PDA selected as DeviceType, then click the New button to add a record, then make a wrong entry in the text box, no error message displays to inform you of the error.

Workaround: None.


JPEG charts do not work properly on WAP phones if the chart application takes CGI parameters

[CR #361753] On a JPEG chart application, when you input the value to the CGI parameter field and press OK on Smartphone devices, the request is not submitted. This functionality is not supported on Smartphones.

Workaround: Make the CGI parameter invisible by setting the Default Value, setting the Display Type to “None,” and unselecting the Required check box.


Search uses alphanumeric search

[CR #361787] When you create a database application from sampledb, then sync the application to a PDA device and search, the search uses an alphanumeric search. For example, if you search with emp_id<180, the records return 3-digit emp_ids less than 180, but also returns records with 4-digit emp_ids that are less than 180 with the last digit truncated, such as 129, 102, 105, 1021, 1039, and so on.

Workaround: None.


URL pattern cannot be generalized when continuous capture is defined

[CR #370036] When you create an application with continuous capture defined, one or more URL patterns are associated with a CCL command, which is used to extract features from the page that are reached by clicking on a link that matches the URL pattern. When defining continuous capture, sometimes the same features on a page are captured with different CCL definitions, so that the URL pattern cannot be generalized.

Workaround: Edit the continuous capture URL mappings manually to generalize URL pattern.


Creating a new DataPool for the “home” DataSource causes a NullPointerException error

[CR #374904] By default, the “home” DatabaseService in global.properties.xml points to op_portal_asa, the DataPool also shared by the other DatabaseServices. Creating a new DataPool for the “home” DataSource causes a NullPointerException when saving an application in Mobile Web Studio.

Workaround: None.


& character causes problems with XML parsing

[CR #381866] The & character in a SQL query causes a problem in the XML parsing of the result set, and you receive an error instead of results for the query.

Workaround: None.


Cannot transpose rows and columns

[CR #426528] Server-side click-across links fail in mobile applications, if you choose to transpose rows and columns when building the application in Mobile Web Studio. The transpose feature is intended for Enterprise Portal.

Workaround: None.


Template causes error messages on device

[CR #422046] When you assign a template to an application, without selecting the device type first, the application does not display, even if the device type matches the template. In addition, attempts to fix the problem by selecting the device type and then re-assigning the template fail.

Workaround: When creating the application, first select the device type “Portal,” and assign the default template for the Portal device type. Next, verify that the application displays properly, and save the application. Then re-assign the template by selecting the device type first and assigning the template.


Portal Interface

This section describes known problems with the Portal Interface.


After self-registering through a shared page, the user cannot access the shared page

[CR #358226] When an unregistered user receives a shared page, the user can self-register by clicking the “Join Now” link, but is then unable to get the shared page.

Workaround: To get the shared page, the user must log in to Portal Interface again using the link in the shared page e-mail.


Using Netscape to access an application with an alert enabled permanently removes the alert icon for all users

[CR #361000] If you use Netscape to access an application with an alert enabled, the alert icon is permanently removed from the application for everyone, even those who have already added the application to their portal using Internet Explorer.

Workaround: Do not use Netscape to access alert-enabled applications.


“Access granted” problems appear unless the PortalUser role is selected during self-registration

[CR #316267] If the PortalUser role is not selected when you self-register in Portal Interface, “access granted” problems appear.

Workaround: Select the PortalUser role when self-registering in Portal Interface.


Page group names have a 25-character limit

[CR #361432] Page group names have a 25-character limit. Once you enter 25 characters for the page group name, no more input is accepted.

For Japanese characters, 64 bytes are allocated for the page group name in the database table, so only 21 of the Japanese characters are saved for the group name, as each Japanese character requires 3 bytes in a UTF-8 database. This truncation gives no warning.

Workaround: Do not exceed the character limit when assigning names to page groups.


Tomcat server

This section describes known problems with Unwired Accelerator and the Tomcat server.


User must have the manager role before deploying a WAR application

[CR #315390] The Tomcat server requires a user to be assigned the manager role before he or she can deploy a WAR application using Mobile Web Studio.

The masuper user name is case sensitive and the password of m8super is assigned the manager role by default. The manager role is also included in the global.properties.xml property registration.userJ2EEroles. This causes the manager role to appear in the list of available roles when users self-register using the Join Now link in the login application.

You can also assign the manager role to existing users. Security-conscious advisors can remove the manager role after creating a user who can deploy WAR applications.

Workaround: Assign the manager role to users to enable them to deploy WAR applications using Mobile Web Studio.


Mobile Data Service (MDS)

This section describes known problems with Unwired Accelerator and RIM MDS.


Syncing a large UA application to BlackBerry

When syncing large applications to BlackBerry, change the Mobile Data Service default HTTP connection timeout setting in the rimpublic.property file located in the Mobile Data Service configuration folder from 2 minutes to a greater number to avoid receiving timeout errors. See your BlackBerry documentation for more information about changing this property.


BlackBerry

This section describes known problems with Unwired Accelerator and RIM BlackBerry.


Incorrect sorting results when using a mixture of uppercase and lowercase letters

[CR #376648] The sorting feature on the BlackBerry client does not handle a mixture of uppercase and lowercase letters correctly, so sorting results can display incorrectly.

Workaround: None.


Sync update log is not detailed

[CR #386470] When a user creates update applications on BlackBerry, then performs a Sync Update and looks at the Sync Update log, it is not possible to tell which message in the log corresponds to which application, as there is insufficient detail in the log.

Workaround: None.


When concurrent updates to records are made, users are not notified

[CR #374598] Unwired Accelerator uses optimistic concurrency control to prevent conflicts when multiple users make updates to the same record. For example, if four users make updates to the same record and sync, only the first user’s sync is executed. The subsequent users are not notified that their updates did not take effect.

Workaround: None.


Database portlet without data causes error

[CR #421880] Any mobile database application without data cannot be opened from the BlackBerry client, making users unable to insert or update data. The following message displays on the BlackBerry client:

application <application name> has no data to view

Workaround: None.


Home link does not access the correct home page

[CR #421888] User authentication returns a failed login when you attempt to access the Home link of a non-grid data application from the UA client. This is because a NULL value is passed on the resource identifier.

Workaround: None.


SAP

This section describes known problems with Unwired Accelerator and SAP.


Internet Explorer stops responding when creating or editing a SAP application

[CR #389896] When you are creating or editing SAP applications using a machine with low memory, Internet Explorer (IE) may stop responding in the Application Builder window.

Workaround: Close IE and restart it.


Internet Explorer stops responding with multiple edits

[CR #393334] Making multiple edits to a large SAP application can cause IE to stop responding.

Workaround: Restart IE.


Some RFC input parameters do not work with English key words

[CR #385736] From UA, some RFC input parameters do not work when using English keywords as the RFC is looking for the German keyword.

Workaround: Try using the German keyword.


If edit of filter rules fails, user does not receive an error message

[CR #393335] When editing Exclude and Include filter rules on a SAP application, the user sees a blank window with no error message indicating the edit failed.

Workaround: Define Insert Record and Edit Record rules prior to the Exclude and Include filter rules.


Security

This section describes known problems for security.


Users who log in to Mobile Web Studio cannot access objects

[CR #356085] Mobile Web Studio users created from LDAP with all roles cannot access objects the first time they log in because the user’s information is not yet in the user’s table.

Workaround: Log out and log in again.


LDAP users cannot edit or save account information in Mobile Web Studio

[CR #391501] Users created in LDAP cannot edit or change their account information in Mobile Web Studio.

Workaround: The user must click Join Now in Portal Interface and create an account with their information in Portal Interface.


When StudioAdmin role is removed from LDAP user, Mobile Web Studio operations are still visible to the user

[CR #386843] When the StudioAdmin role is removed from an LDAP user, the user still sees the StudioAdmin role operations in Mobile Web Studio.

Workaround: None.



Documentation updates and clarifications

This section provides new documentation for the .NET client, and provides documentation changes for Unwired Accelerator for Linux on POWER.


Documentation and unsupported features

As described in “Unsupported features”, some features are either not supported in Unwired Accelerator for Linux on POWER, or have been replaced with comparable features. The online help, software, and product documentation continue to refer to these unsupported features (such as Adaptive Server Anywhere, M-Business Anywhere, EAServer, and Answers Anywhere) [CR #422731].

When using the documentation, make these substitutions:

  • Adaptive Server Anywhere – substitute Adaptive Server Enterprise, Enterprise Edition, which is used for data storage in Unwired Accelerator Linux on POWER. Ignore the ASA procedure, and use the comparable ASE procedure. See the Adaptive Server Enterprise documentation for details on the Getting Started CD.

  • M-Business Anywhere – substitute .NET client, which is used to deploy mobile applications to PDAs. See the Unwired Accelerator Installation Guide for .NET client installation procedures; and see “Using the .NET client” and “Customizing the .NET client” for .NET client user procedures.

  • EAServer – ignore references to EAServer; Unwired Accelerator for Linux on POWER uses the Tomcat application server.

  • Answers Anywhere – ignore references to Answers Anywhere (or to AskUA), which is not available on Linux for POWER.


Using the .NET client

Unwired Accelerator includes client software for the mobile device that communicates with the Unwired Accelerator server. This enables you to download mobile applications to the mobile device, and to synchronize data between the Unwired Accelerator server and client. This section describes how to use the .NET client. Tasks include:

This section assumes the .NET client configuration is in place. If not, see the Unwired Accelerator Installation Guide for information and procedures.


Starting and stopping the .NET client

This section describes how to start the .NET client and the ASA for CE database server on the mobile device.

Starting the .NET client application
  1. On your mobile device, open the Start menu and select Programs.

  2. Locate the Unwired Accelerator icon, and tap it once. The ASA for CE database is loaded, and then the Unwired Accelerator 7.0 .NET client runs. You need to select a user profile to work with mobile applications.

Stopping the .NET client application
  1. On the applications window, click the Menu.

  2. Select Exit. The .NET client shuts down, followed by the ASA for CE database server.


Managing .NET user profiles

This section describes how to manage .NET client user profiles. Topics include:

  • Setting up the .NET user

  • Editing the .NET user

  • Deleting the .NET user

Setting up a .NET user profile

The .NET user profile must correspond to a profile on the Unwired Accelerator 7.0 server. Either set up the user account in advance through Mobile Web Studio as a system administrator, or have the user log in to Portal Interface and use Join Now to set up an account. Once the account is set up, the user can set up a .NET user profile from the mobile device.

  1. Click the Menu in the lower left corner of the screen.

  2. Click Profiles to view the Profiles Manager screen. Initially, no profiles are listed on the screen.

  3. Click Menu and select New Profile to open the Profile Editor screen.

  4. Enter the details for the Unwired Accelerator 7.0 server to which you will be connecting.

    • Profile Name – the profile name for the account, such as myUAserver.

    • User Name – the user name for the profile, such as masuper.

    • Password – the password for the profile, such as m8super.

    • Server – the server and domain on which the Unwired Accelerator server is running, such as lab2k.sybase.com.

    • Port – the port used to access the Unwired Accelerator server, such as 4040.

    • RID – the default resource identifier (RID) for the account, such as 21 for Unwired Accelerator.

  5. Click the Menu and select Save. The Profile Manager screen displays. The new profile is listed on the screen.

  6. Click OK in the upper right corner of the screen.

Editing a .NET user profile
  1. Select the profile to edit. You can either:

    • Click once on the profile to edit to highlight it, then select Menu | Edit Profile. The Profile Editor screen appears.

    • Tap and hold the Profile to edit to highlight it, then select Edit Profile from the context menu. The Profile Editor screen appears.

  2. In Profile Editor, edit profile values for the account.

    • Profile Name – the profile name for the account, such as myUAserver.

    • User Name – the user name for the profile, such as masuper.

    • Password – the password for the profile, such as m8super.

    • Server – the server and domain on which the Unwired Accelerator server is running, such as lab2k.sybase.com.

    • Port – the port used to access the Unwired Accelerator server, such as 4040.

    • RID – the default resource identifier (RID) for the account, such as 21 for Unwired Accelerator.

  3. Select Menu | Save to save the changes, or select Menu | Close to cancel the changes, and return to the main screen.

Deleting a .NET user profile
  1. Select the profile to delete. You can either:

    • Click once on the profile to delete to highlight it, then select Menu | Delete Profile. You are prompted to confirm the deletion request.

    • Tap and hold the Profile to delete to highlight it, then select Delete Profile from the context menu. You are prompted to confirm the deletion request.

  2. Select Yes to confirm.


Working with mobile applications

This section describes how to work with applications once they are deployed on .NET client on the mobile device. Topics include:


Synchronizing applications from the device

This section describes how to synchronize mobile applications between Unwired Accelerator server and the .NET client on the mobile device. The applications to which you have access depends on the profile you use. You can select one or more applications from the available applications.

The speed of your network determines how fast you can synchronize. An ActiveSync shared internet connection is typically faster then a GPRS connection.

Synchronizing mobile applications on you device
  1. From the Applications screen, select a profile from the drop-down list. The applications to which you have access depend on the profile you select.

    If no profiles exist, see “Managing .NET user profiles” for information about setting up .NET client user profiles.

  2. Select Menu | Synchronize. In a few moments, depending on the speed of your network connection, a list of applications available on the Unwired Accelerator server displays.

  3. Select one or more applications to sync by tapping on them. Selected applications are highlighted. Tap a highlighted application to deselect it.

  4. After highlighting all the applications you wish to synchronize, select Menu | Synchronize. During synchronization, the Progress screen reflects the progress of the synchronization. After synchronization completes, the Applications screen displays.

    Note:During synchronization, you can click the Cancel button to cancel the process. Applications that have been downloaded and saved are already committed to the local database, and are not rolled back. Applications that are in the process of being downloaded and saved are rolled back.


Opening and closing applications

This section describes how to open synchronized mobile applications on your mobile device. Applications are of two types:

  • Non-grid applications – these are applications that do not contain grid data, such as non-gridified HTML web content. The Unwired Accelerator 7.0 .NET client launches Pocket Internet Explorer, and loads the Unwired Accelerator application into the browser.

  • Grid applications – these are applications that contain grid data. The Unwired Accelerator 7.0 .NET client displays data in an interactive grid, which enables you to resize columns and rows, follow hyper-links, and drill-down to detailed views, as described in “Working with grid applications”.

Opening and closing mobile applications on your device
  1. From the Applications screen, select the application to open. You can either:

    • Click once on the application you wish to open to highlight it, then click the Menu.

    • Tap and hold on the application you wish to open. After a moment it is highlighted and a context menu appears.

  2. Select Open. The application opens.

    To close the application, select Menu | Close, or click OK in the upper right corner of the screen.


Working with grid applications

This section provides guidelines for working with grid applications:

  • Resizing columns and rows – resize the columns and rows by tapping and dragging the dividers in the header row and column.

  • Following drill-down links – for applications with a server-side click-across events, tap the blue link in the data grid, or anywhere in the cell, to drill down to the next level. Drill-down data is displayed.

    To go back up a level, select Menu | Back, or click the Back arrow at the top of the screen. The previous data set displays.

  • Switching to detail view – for applications with detail view, select the row to view, either by clicking on a cell in the row that does not contain a server-side click-across event, or click the row header on the far left of the screen. After the row is highlighted, select Menu | Detail View.

    To return to the List View, select Menu | Back.


Sorting application data

This section provides guidelines for sorting application data:

  • Sorting in List View – you can sort application data by a particular column. To do so, select Menu | Sort, and tap once on the column name by which to sort.

  • Sort order – the first time you select a column to sort, the sort is in ascending order. A subsequent selection of that same column results in descending order.

  • Sorting numbers – all application data is treated as string data, so all sorts are in alphabetical order. If a particular column contains numeric values, they are sorted in alphabetic order from the left most characters first. For example, the numbers 1, 9 and 20 would be sorted as 1, 20, 9 in ascending order, and 9, 20, 1 in descending order.

  • Scroll arrows – if there are too many column names to display at once, scroll arrows appear at the top and bottom of the menu.


Searching application data

This section provides guidelines for searching application data:

  • Searching in List View – you can search application data for specific values. To search for a particular matching value, select Menu | Search | Search. The next screen that appears lets you select the column you want to search and enter the value for which to search. To run the search select Menu | Search.

  • Removing search filtering from the data – select Menu | Search | Show All.

  • Multiple searches – searching is not cumulative. If you perform one search and then perform a second, the second search is executed against the full data set and not just the results of the first search.


Deleting an application from the device

This section describes how to remove an application from your mobile device. You can also remove all applications for a profile.

Deleting mobile applications from your device
  1. From the Applications screen, select the application to remove. You can either:

    • Click once on the application you wish to remove to highlight it, then click the Menu.

      Select Menu | Delete | Delete Application. You are prompted to confirm the deletion request.

    • Tap and hold on the application you wish to open. After a moment it is highlighted and a context menu appears.

      Select Delete Application. You are prompted to confirm the deletion request.

  2. Select Yes to confirm. The application is removed from the list.

Note:To delete all applications in the profile, select Menu | Delete | Delete All. You are prompted to confirm the deletion request.


Working with records on the device

This section describes how to insert a new record and update an existing record. New and updated records are sent to the data source when you synchronize the application.

Note:Currently, you cannot delete a record from the mobile device using the .NET client.

Inserting a record
  1. Select the application to open as described in “Opening and closing applications”.

  2. Select Open from the menu.

  3. Select New from the menu.

  4. Fill in the fields to create a new record. The fields available depend on the mobile application.

  5. Select Save from the menu.

  6. Click Menu | Sync Update to update the data source.

Modifying a record
  1. Select the application to open as described in “Opening and closing applications”.

  2. Select Open from the menu.

  3. Select the record to change.

  4. Select Update from the menu.

  5. Change one or more fields to modify the record.

  6. Select Save from the menu.

  7. Click Menu | Sync Update to update the data source.


Creating mobile applications for .NET client

You can create mobile applications for .NET client using instructions in the Unwired Accelerator documentation. In the current version, these parameter types are supported for new and updated records: text box, drop-down list, Calendar, password, and text area.


Customizing the .NET client

You can customize the Unwired Accelerator client software on your mobile device without recompiling software. You can customize:

  • Language

  • Message text

  • Interface strings

  • Graphics

  • Icons

Perform customization on the mobile device after you deploy the .NET client to the mobile device. Each user can customize the .NET client to individual preference by modifying default files. Alternatively, acting as system administrator, you can customize the default files for your users, who in turn can download the files to mobile devices, and further modify the files.

This section assumes the .NET client configuration is in place. If not, see the Unwired Accelerator Installation Guide for installation information and procedures.


Customization overview

This section provides information and procedures for customizing the .NET client. Modify the Strings.xml file to customize the .NET client.

Note:Typically, modifications to the Strings.xml file are performed by each user on the mobile device. Alternatively, you can copy the Strings.xml file to a PC and use a UTF-8-capable text editor to edit the strings. Then, copy the Strings.xml file back to the PDA, and restart the .NET client to see the changes on the mobile device.

You may need to develop procedures for deploying updated Strings.xml files to mobile device users. You may want to consider using a remote device management tool, such as Afaria, to place new images and files on PDAs.


Customizing language

To customize language for the .NET client:

  • Obtain the proper language files and related font files, and download the files to your mobile device.

  • Obtain or create localized user interface graphics, logos, and icons, using the sizes recommended for your device. Download the files to your mobile device.

  • Modify the Strings.xml file on your mobile device:

    • Specify the appropriate language-related resource values, such as language, font, and text orientation.

    • Translate message strings to the language, such as error and validation messages.

    • Translate user interface strings to the language, especially user profile fields and prompts.

    • Update the user interface graphics, logos, and icons file names.

    See “Understanding the Strings.xml file” for information before you start.

When you restart the application, the.NET client:

  1. Checks the device’s regional settings for the current language code and country code. For example, a PDA set to “Dutch (Belgium)” would be “nl-BE.”

  2. Checks for the string localization file that matches the language and country code; in this case, Strings.nl-BE.xml for Dutch Belgium.

    If the file does not exist, the client looks for an alternative file that contains the language code, but no country code (for example, Strings.nl.xml, a generic Dutch localization file).

    If that is not found, the client defaults to the Strings.xml file with default English strings.

Localizing the .NET client

This procedure assumes you have changed the regional setting, downloaded any necessary fonts or character sets, and moved localized graphics files to the mobile device.

  1. Navigate to the Strings.xml file.

  2. Make a copy of the Strings.xml file, and include the language and country code in the new file name. For example:

    Strings.nl-BE.xml for Dutch Belgium Strings.fr-CA.xml for French Canadian Strings.fr-FR.xml for French

  3. Modify the new file on your mobile device:

    • Specify the appropriate language-related resource values, such as language, font, and text orientation. See Table 3 for information about the resource values.

    • Translate message strings to the language, such as error and validation messages. See “Messages in Strings.xml” for default messages.

    • Translate user interface strings to the language, especially user profile fields and prompts. See “Strings in Strings.xml” for default strings.

    • Update the user interface graphics, logos, and icons file names. See “Images in Strings.xml” for information about graphics.

    See “Understanding the Strings.xml file” for information about working with the Strings.xml file (or the localized version of the file).

  4. Save the file and close it.

  5. You can also localize the template files, as described in “Understanding the device template files”. The template files include some language strings.

  6. Restart the application. The .NET client should detect the regional language and country codes, locate the localized Strings.xml file, and present the localized interface.

    Note:Any reference to the Strings.xml file extends to your localized version of the file, such as Strings.nl-BE.xml.


Customizing messages

The Strings.xml file includes a section of messages that can be localized to a different language, or that can be customized to use terms and phrasing more meaningful for a business setting, or for an individual user. See “Messages in Strings.xml” for message text.


Customizing graphics

The Strings.xml file includes a section of graphics. You can obtain or create localized graphics, and replace the defaults included with the .NET client. After the .NET client is installed, replace the images on the device with new images, and update the graphic file names in Strings.xml. See “Images in Strings.xml” for graphics file names.


Customizing the user interface

The Strings.xml file includes sections for changing Unwired Accelerator strings and icons that appear on the mobile device user interface.

  • For user interface strings, such as “Menu,” customize the default text that comes with the .NET client. See “Strings in Strings.xml” for string text.

    Note:Additional user interface strings appear in the template files. You can customize or localize these strings. See “Understanding the device template files” for information.

  • For icons, such as buttons, you can obtain or create custom graphics, and replace the defaults included with the .NET client. After the .NET client is installed, replace the default icons on the device with new icons, and update the icon file names in Strings.xml. See “Images in Strings.xml” for icon file names.


Understanding the Strings.xml file

The Strings.xml file is used to control what is printed on the device, including user interface labels, messages, logos, icons, and other graphics. This is the primary file used to customize the Unwired Accelerator .NET client. Resource names and values in the file equate to text or visual cues displayed on the screen.

Figure 1 shows several resource names and values, and the equivalent PDA screen representation.

Figure 1: Resource names and PDA screen equivalents

Following is a partial, sample Strings.xml file, with key resource names highlighted. See Table 3 for descriptions of these resource names.

<?xml version="1.0" encoding="utf-8" ?><root><Resource Name="TITLE_APPLICATION" Value="Unwired Accelerator" /><Resource Name="FORMAT_DISPLAY_TEXT_RTL" Value="false" /><Resource Name="FORMAT_FONT" Value="Arial" /><Resource Name="FORMAT_LAST_DOWNLOAD_DATE_FORMAT" Value="yyyy-MM-dd hh:mm:ss" /><Resource Name="FORMAT_LIST_VIEW_ROW_HEIGHT_FOR_DPI_96" Value="16" /><Resource Name="FORMAT_LIST_VIEW_ROW_HEIGHT_FOR_DPI_192" Value="32" />...<Resource Name="MESSAGE_ASA_NOT_FOUND" Value="Adaptive Server Anywhere for Windows CE could not be found. This application will now exit." /><Resource Name="MESSAGE_CAN_NOT_ACCESS_APPLICATION_DATA" Value="Unable to access Application data." /><Resource Name="MESSAGE_CAN_NOT_CREATE_NEW_APPLICATION" Value="Can not create new Application." /><Resource Name="MESSAGE_CAN_NOT_READ_PROFILE" Value="Can not read Profile." />...<Resource Name="STRING_ABORT" Value="Abort" /><Resource Name="STRING_*ALL_COLUMNS*" Value="ALL COLUMNS" /><Resource Name="STRING_APPLICATIONS" Value="Applications" />...<Resource Name="IMAGE_ADD_MOUSEUP_24" Value="add_white_24.bmp" /><Resource Name="IMAGE_ADD_MOUSEDOWN_24" Value="add_black_24.bmp" /><Resource Name="IMAGE_ADD_DISABLED_24" Value="add_disabled_24.bmp" />...</Root>
Table 3: Resource names in Strings.xml

Resource name

Description

Default value

encoding

Character encoding for Unicode. The default, UTF-8, is ideal for mobile device applications.

utf-8

TITLE_APPLICATION

The default application name for Unwired Accelerator that displays on the mobile device.

Unwired Accelerator

FORMAT_DISPLAY_TEXT_RTL

Indicates whether application text displays right to left on the mobile device. False indicates text displays left to right; true indicates text displays right to left.

false

FORMAT_FONT

The default application font used on the mobile device.

Arial

FORMAT_LAST_DOWNLOAD_DATE_ FORMAT

The date-time format used on the mobile device.

yyyy-MM-dd hh:mm:ss

FORMAT_LIST_VIEW_ROW_HEIGHT_FOR_DPI_96

The row height in pixels for 96 dots-per-inch (DPI).

16

FORMAT_LIST_VIEW_ROW_HEIGHT_FOR_DPI_192

The row height in pixels for 192 DPI.

32

MESSAGE_message_text

Message text, such as “Can not read Profile.” You can modify or localize each message.

See Table 4 for additional information about the messages.

STRING_string_text

Application labels, such as “Profile Name.” You can modify or localize each message. See Figure 1 for several string examples.

See Table 5 for additional information about the user interface strings.

IMAGE_image_name

Application images, such as buttons, graphics, and logos. Many images are provided in normal, selected, or unavailable style, and multiple sizes of images are available, depending on the mobile device window dimensions.

See Table 6 for additional information about images.


Messages in Strings.xml

Table 4 provides the message resources and their default values. You can change the default values, either by localizing the text or modifying it for your environment.

Some messages include variables, or placeholders, that are populated depending on the circumstances. For example, the message Delete {0}? includes one variable ( {0} ). During execution, the variable is replaced with another message or number, for example, the message might read Delete Stock?. Do not change the placeholder, just the text

Table 4: Messages in Strings.xml

Message resource

Default value

MESSAGE_ASA_NOT_FOUND

Adaptive Server Anywhere for Windows CE could not be found. This application will now exit.

MESSAGE_CAN_NOT_ACCESS_APPLICATION_DATA

Unable to access Application data.

MESSAGE_CAN_NOT_CREATE_NEW_ APPLICATION

Can not create new Application.

MESSAGE_CAN_NOT_READ_PROFILE

Can not read Profile.

MESSAGE_DELETE_ALL_APPLICATIONS?

Delete all Applications?

MESSAGE_DELETE_APPLICATION_X?

Delete {0}?

MESSAGE_DELETE_ALL_LOGS?

Delete all Logs?

MESSAGE_DELETE_LOG?

Delete the selected Log?

MESSAGE_DELETE_PROFILE_X?

Delete {0}? This will also delete all Applications related to this profile.

MESSAGE_ERROR_GETTING_SCREEN_ ORIENTATION_X

Error getting screen orientation: {0}

MESSAGE_ERROR_SETTING_SCREEN_ ORIENTATION_X

Error setting screen orientation: {0}

MESSAGE_HTTP_ERROR_X

HTTP Error: {0}

MESSAGE_INVALID_HTTP_RESPONSE

Invalid HTTP response.

MESSAGE_INVALID_LINKED_UA_ APPLICATION

The Unwired Accelerator linked application is invalid. Please notify your system administrator about this message and include the name of the application your are trying to synchronize.

MESSAGE_INVALID_PROFILE_KEY

Invalid Profile Key.

MESSAGE_INVALID_PROFILE_NAME

The profile name is empty.

MESSAGE_INVALID_PROFILE_PASSWORD

The profile password is empty.

MESSAGE_INVALID_PROFILE_PORT

The profile port number is invalid.

MESSAGE_INVALID_PROFILE_RID

The profile RID number is invalid.

MESSAGE_INVALID_PROFILE_SERVER

The profile server is empty.

MESSAGE_INVALID_PROFILE_USERNAME

The profile username is empty.

MESSAGE_INVALID_UA_VERSION_CANNOT_ SYNC_APP_X

The Unwired Accelerator server you are trying to synchronize with is not a version 7.0 server. The application {0} can not be synchronized.

MESSAGE_INVALID_VALUE_FOR_X

Invalid value for '{0}'.

MESSAGE_NETCF_1.0SP3_NOT_FOUND

This application requires that the .NET Compact Framework 1.0 Service Pack 3 be installed. This application will now exit.

MESSAGE_NO_RESX_STRING_FOR_X

No resource found for {0}.

MESSAGE_NO_APPLICATIONS_AVAILABLE

No Applications are available for download.

MESSAGE_PROFILE_NAME_NOT_UNIQUE

Another Profile already has this name. Please enter a unique name for this Profile.

MESSAGE_UA_AUTHENTICATION_FAILED

Unable to authenticate your username and password with the Unwired Accelerator server.

MESSAGE_UA_CONNECTION_FAILED

Unable to connect to the Unwired Accelerator server.

MESSAGE_UNABLE_TO_CONNECT_WITH_UA_SERVER

Unable to connect with the Unwired Accelerator server. Please check and verify your network access and coverage.

MESSAGE_UNABLE_TO_CREATE_LINKED_ APPLICATION

Unable to create the linked Application. Please notify your system administrator about this message and include the name of the application you are trying to synchronize.

MESSAGE_UNABLE_TO_FIND_TEMPLATE_X

Unable to find the template named: {0}

MESSAGE_UNKNOWN_UA_SERVER_ERROR

There was an unknown error on the Unwired Accelerator server. Please notify your system administrator.


Strings in Strings.xml

Table 5 provides the user interface string names found in Strings.xml. These are the labels, menu options, and so forth that appear on the application user interface. You can change the default values, either by localizing the text or modifying it for your environment.

Some messages include variables, or placeholders, that are populated depending on the circumstances. For example, the message Saving Record {0} of {1} includes two variables ( {0} and {1}). During execution, the variables are replaced with other messages, for example, the message might read Saving Record 20 of 25. Do not change the placeholder, just the text.

Table 5: User interface string names in Strings.xml

User interface string name

Default

STRING_ABORT

Abort

STRING_*ALL_COLUMNS*

ALL COLUMNS

STRING_APPLICATIONS

Applications

STRING_BACK

Back

STRING_BUILD_DATE:_X

Build Date: {0}

STRING_CANCEL

Cancel

STRING_CANCELLED

Cancelled

STRING_CONFIRM

Confirm

STRING_CURRENT_PROFILE

Current Profile

STRING_DELETE

Delete

STRING_DELETE_ALL

Delete All

STRING_DELETE_APPLICATION

Delete Application

STRING_DELETE_LOG

Delete Log

STRING_DELETE_PROFILE

Delete Profile

STRING_DELETING_LOGS

Deleting Logs

STRING_DESELECT_ALL

Deselect All

STRING_DETAIL

Detail

STRING_DETAIL_VIEW

Detail View

STRING_DOWNLOADING

Downloading

STRING_EDIT

Edit

STRING_EDIT_PROFILE

Edit Profile

STRING_EQUALS

Equals

STRING_ERROR

Error

STRING_EXIT

Exit

STRING_FAILED

Failed

STRING_IGNORE

Ignore

STRING_INSERT

Insert

STRING_INVERT_SELECTION

Invert Selection

STRING_LIKE

Like

STRING_LOG_DETAILS

Log Details

STRING_LOG

Log

STRING_LOGS

Logs

STRING_MENU

Menu

STRING_MESSAGE

Message

STRING_NEW

New

STRING_NEW_PROFILE

New Profile

STRING_NO

No

STRING_OK

OK

STRING_OPEN

Open

STRING_OVERALL_PROGRESS

Overall Progress

STRING_PASSWORD:

Password :

STRING_PORT:

Port :

STRING_PROFILE

Profile

STRING_PROFILE_NAME:

Profile Name :

STRING_PROFILES

Profiles

STRING_PROGRESS

Progress

STRING_REQUIREMENT_MISSING

Requirement Missing

STRING_RETRY

Retry

STRING_RID:

RID :

STRING_SAVE

Save

STRING_SAVED

Saved

STRING_SAVING

Saving

STRING_SAVING_RECORD_X_OF_Y

Saving Record {0} of {1}

STRING_SEARCH

Search

STRING_SEARCH_FOR:

Search For :

STRING_SEARCH_IN:

Search In :

STRING_SEARCH_TYPE:

Search Type :

STRING_SELECT_ALL

Select All

STRING_SENDING_UPDATES

Sending Updates

STRING_SERVER:

Server :

STRING_SHOW_ALL

Show All

STRING_SORT

Sort

STRING_STATUS

Status

STRING_STATUS:

Status:

STRING_SYNCHRONIZE_ALL

All

STRING_SYNCHRONIZE_SELECTED

Selected

STRING_SYNCHRONIZE

Synchronize

STRING_SYNCHRONIZE_UPDATES

Sync Updates

STRING_SYNCHRONIZATION_CANCELLED

Synchronization Cancelled

STRING_SYNCHRONIZING

Synchronizing

STRING_TIMESTAMP

Timestamp

STRING_TYPE

Type

STRING_USER_NAME:

User Name :

STRING_VALIDATION_FAILED

Validation Failed

STRING_VERSION:_X

Version: {0}

STRING_X/Y

{0}/{1}

STRING_YES

Yes


Images in Strings.xml

Table 6 provides image file names found in the Strings.xml file. You can change these images. To change an image, you actually need six images; for example:

  • Each button has three states (mouse up, mouse down, and disabled). The default buttons use a black background when selected, and a gray background when disabled, as a cue to the user.

  • Each button must be set to the proper size for both high (48x48 pixels) and low (24x24 pixels) resolution screens.

Files with the BMP extension work best.

Table 6: Image file names in Strings.xml

Image file name

Default

IMAGE_ADD_MOUSEUP_dpi_value

add_white_xx.bmp

IMAGE_ADD_MOUSEDOWN_dpi_value

add_black_xx.bmp

IMAGE_ADD_DISABLED_dpi_value

add_disabled_xx.bmp

IMAGE_BACK_MOUSEUP_dpi_value

back_white_xx.bmp

IMAGE_BACK_MOUSEDOWN_dpi_value

back_black_xx.bmp

IMAGE_BACK_DISABLED_dpi_value

back_disabled_xx.bmp

IMAGE_DELETE_MOUSEUP_dpi_value

delete_white_xx.bmp

IMAGE_DELETE_MOUSEDOWN_dpi_value

delete_black_xx.bmp

IMAGE_DELETE_DISABLED_dpi_value

delete_disabled_xx.bmp

IMAGE_EDIT_MOUSEUP_dpi_value

edit_white_xx.bmp

IMAGE_EDIT_MOUSEDOWN_dpi_value

edit_black_xx.bmp

IMAGE_EDIT_DISABLED_dpi_value

edit_disabled_xx.bmp

IMAGE_OPEN_MOUSEUP_dpi_value

folder_white_xx.bmp

IMAGE_OPEN_MOUSEDOWN_dpi_value

folder_black_xx.bmp

IMAGE_OPEN_DISABLED_dpi_value

folder_disabled_xx.bmp

IMAGE_SAVE_MOUSEUP_dpi_value

ave_white_xx.bmp

IMAGE_SAVE_MOUSEDOWN_dpi_value

save_black_xx.bmp

IMAGE_SAVE_DISABLED_dpi_value

save_disabled_xx.bmp

IMAGE_SYNC_MOUSEUP_dpi_value

sync_white_xx.bmp

IMAGE_SYNC_MOUSEDOWN_dpi_value

sync_black_xx.bmp

IMAGE_SYNC_DISABLED_dpi_value

sync_disabled_xx.bmp


Understanding the device template files

The template files are used to define visual aspects of the mobile device screen, for example, the color of the heading row, and the color of a row when it is selected and when it is not. Template files contain a few strings that can be customized or localized, and settings for font type and size, and encoding.

Template files are provided for mobile device dimensions, orientation (portrait and landscape), and resolution. When you modify template files for a particular screen size and configuration, modify similar values in all files.

When modifying the template files, keep in mind the following guidelines:

  • You can edit any strings that are English language strings, such as Application [Last Downloaded] in this property:

    <Property Name="CellSource" Value="&quot;Application [Last Downloaded]&quot;" />

    Note that the &quot; XML entities identify this as a human language value, which can be translated and localized. Be sure to leave the XML entities intact [including the ampersand (&) and semicolon (;)], otherwise the XML document will be invalid, causing the XML parser to fail, and making the .NET client unable to load the templates.

  • Do not edit any variables, such as APPLICATION_NAME in this property:

    <Property Name="CellSource" Value="APPLICATION_NAME" />

    APPLICATION_NAME is a special variable flag that is replaced by the name of the application. If you edit this value, no application name will appear, even for other languages.

    Template values like APPLICATION_NAME that are not surrounded by the &quot; XML entity should not be edited. They serve as variable flags that are replaced by the client application when there is data to display on the screen.

  • Do not modify any coordinate values, such as:

    <Property Name="Location" Value="0,28" />

  • Templates should not be edited on the device. Instead, they should be transferred to the PC (which can be done using the ActiveSync File Explorer), and edited on a text editor that supports UTF-8. After editing the files, move them back to the device, and restart the application to see the changes.

    As with the Strings.xml file, you may need to develop procedures for deploying updated template files to mobile device users. You may want to consider using a remote device management tool, such as Afaria, to place new images and files on PDAs.

  • For localization, you can edit the default template files to something other then English, or you can add multiple language support by creating copies of the templates using the same naming technique used for the Strings.xml file (described in “Customizing language”). For example, with a 240x320 device set to Belgian Dutch, the client would look for templates in this order:

    1. Template.Applications.240x320.nl-BE.XML

    2. Template.Applications.240x320.nl.XML

    3. Template.Applications.240x320.XML

Customizing the device template files
  1. Identify the dimensions of your mobile device screen, for example, 240 x 320 pixels.

  2. Identify the templates available for the screen dimensions, for example:

    • Template.Applications.240x320

    • Template.ApplicationDataDetailView.240x320

    • Template.ApplicationDataListView.240x320

    • Template.ApplicationsSyncList.240x320

    • Template.DataEdit.240x320

    • Template.InsertDataForm.240x320

    • Template.InsertDataGrid.240x320

    • Template.LogsListView.240x320

    • Template.LogsDetailView.240x320

    • Template.ProfileManager.240x320

    • Template.ProfileEditor.240x320

  3. On the mobile device, navigate to the template files.

  4. Transfer the files to the PC (which can be done using the ActiveSync File Explorer).

  5. Using a text editor that supports UTF-8, search each template for properties, and update the values for your environment. Keep in mind the guidelines provided above. Typical properties to customize include:

    • Font (or TextFont)

    • Colors (BackColor, ForeColor, AlternateForeGround, SelectionBackColor, ActiveColor, VisitedColor, GridColor, and so forth)

    • Encoding (such as UTF-8)

    • English language string values (such as the profile labels used when you set up a user profile, found in Template.ProfileEditor.240x320)

  6. Save each file and close it.

  7. Move the template files back to the device.

  8. Restart the application to view the changes.



Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.



Other sources of information

Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:

  • The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.

  • The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format.

    Some documentation may be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the PDF files, you need Adobe Acrobat Reader.

    Refer to the SyBooks Installation Guide on the Getting Started CD, or the README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.

  • The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.

    To access the Sybase Product Manuals Web site, go to Product Manuals.


Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications
  1. Point your Web browser to Technical Documents.

  2. Click Certification Report.

  3. In the Certification Report filter select a product, platform, and timeframe and then click Go.

  4. Click a Certification Report title to display the report.

Finding the latest information on component certifications
  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance
  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.


 

DOCUMENT ATTRIBUTES
Last Revised: Mar 02, 2007
Part Number: DC00458-01-0700-02
Product: Unwired Accelerator
Technical Topics: XML, Java, LDAP, Security, Troubleshooting, Wireless Server, Application Servers, UltraLite Deployment, Application Deployment, Transaction Processing, Application Development
  
Business or Technical: Technical
Content Id: 1050596
Infotype: Release Bulletin
 
 
 

© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics