Documentation Updates

In the topic Configuring Your Environment for SAP, the task omitted path information for these Unwired WorkSpace components.

Workaround: Follow the task documented in Preparing the Unwired Platform Environment for SAP Connections for each respective component.

In the Visual Studio help:

Configuring the Visual Studio Development Environment >Adding a Data Source Connection>Adding an SAP Connection> Configuring Your Environment for SAP

In the Eclipse help:

Configuring the Eclipse Development Environment > Creating a Data Source Connection Profile > Creating an SAP Connection Profile > Configuring Your Environment for SAP

In the topic "Agent Plugin Properties Reference", the agent plugin XML file format is incorrect.

<set-property property="uep.server.list" value="('sup1_cluster_name', 'CDB_user','CDB_password','sup2_home_dir') || ('sup2_cluster_name','CDB_user',' CDB_password', 'sup2_home_dir')" />

Sybase Control Center > Administer > Manage > Unwired Server Lifecycles > Adding Unwired Server to Sybase Control Center > Agent Plugin Properties Reference

In the topic "Push Synchronization," the first bulleted item concerning the SMS gateway and the third bulleted item concerning the Mail gateway are incorrect.

Workaround: Disregard these items. The SMS and Mail gateways are currently not part of the UI.

Sybase Control Center > Administer > Unwired Server > Server Configuration > Configuring Unwired Server Properties > Push Synchronization

In the specified topic, no information was provided as to how the log files are organized and which types of errors are logged in which files.

Workaround: See Unwired Server Logging Reference.

Sybase Control Center > Administer > Unwired Server > Manage > Logs

In the specified topic, no instructions were provided for setting up an Afaria client on a Windows Mobile device.

Workaround: See Setting up an Afaria Client on a Windows Mobile Device.

Sybase Control Center > Administer > Afaria Device Administration > Set Up > Afaria Clients

In Getting Started table on the Sybase Control Center landing page, the "Start Working" cell contains a broken link to Deploying a Package.

Workaround: Follow the path specified for the topic at the right.

Sybase Control Center > Administer > Unwired Server > Manage > Packages

In the specified topic, the following line appears in the code sample:

CSI.loginModule.7.options.AuthenticationSearchBase=UO=users,dc=example,dc=com

Workaround: Change "UO" in that line to "ou" to make the line look like this:

CSI.loginModule.7.options.AuthenticationSearchBase=ou=users,dc=example,dc=com

Configuring an LDAP Provider for Sybase Control Center topic in:

• Sybase Control Center > Configure > Unwired Platform > Configuring Unwired Server > Configuring Unwired Server for a Production Environment > Securing the Unwired Server Environment > Securing Access to Sybase Control Center > Configuring a Deployment Edition LDAP Server
• Sybase Unwired WorkSpace > Configure > Configuring Unwired Server > Configuring Unwired Server for a Production Environment > Securing the Unwired Server Environment > Securing Access to Sybase Control Center > Configuring a Deployment Edition LDAP Server
• Sybase Unwired Platform Installation Guide > Postinstallation Tasks > Configuring an LDAP Provider

Under the specified online help topic, no instructions are provided for creating and deploying a package from the command line in the Sybase Control Center environment.

Workaround: See Creating and Deploying a Package from the Command Line.

Sybase Control Center > Administer > Unwired Server > Manage > Packages

In the specified online help topic, the instructions for setting push sync parameters were not documented.

Workaround: See Configuring Push Sync Settings for Single-Application Use Case and Configuring Push Sync Settings for Single-Application Use Case.

Develop > Developing a Device Application > Viewing a Sample Windows Mobile Application > Configuring Push Settings

In the specified online help topics, the necessary values for RSOE properties are not provided.

Workaround: See Configuring a Relay Server for Afaria.

In addition, under the same parent topic, Sybase Control Center > Configure > Unwired Platform > Configuring Afaria, add the topic linked above to the sections in the following column.

Replace existing Sybase Control Center > Configure > Unwired Platform > Configuring Afaria > Configuring a New Afaria Installation on a Shared Host > Configuring a Relay Server for Afaria with new Configuring a Relay Server for Afaria topic.

Add new Configuring a Relay Server for Afaria topic under:

• Sybase Control Center > Configure > Unwired Platform > Configuring Afaria > Configuring a New Afaria Installation on a Different Host
• Sybase Control Center > Configure > Unwired Platform > Configuring Afaria > Configuring an Existing Afaria Installation

In the specified online help topic, i18n support is not documented.

Workaround: When you are planning for localization, be aware that Sybase Unwired Platform i18n support encompasses the following functionality:

• Sybase Unwired Platform allows entry of international data at runtime for mobile applications.
• Sybase Unwired Platform correctly displays international data.
• Sybase Unwired Platform correctly stores and retrieves international data from data sources.
• All Sybase Unwired Platform user interfaces, graphical or command line, are localizable except the CLIs for Unwired Server.
• Formatting of data (for presentation to the user) is locale sensitive.
• GUI layouts will accommodate localized data so there is no overlap.
• International data is processed correctly by Sybase Unwired Platform. Examples of data processing are sorting and parsing strings.
• Transformation of data is handled correctly by Sybase Unwired Platform. For example, converting characters encoded as cp936 to Unicode UTF-8.
• File input and output correctly handled international data for the contents of files as well as the directory paths to the files.
• All online help content, such as tool tips and cheat sheets, is localizable.
• All data conduits in Sybase Unwired Platform correctly transport international data.

Sybase Unwired WorkSpace > Develop > Developing a Device Application > Localization

For Unwired Server troubleshooting and performance tuning purposes, you need to view the information that is recorded in the log files.

Workaround: Use the instructions below to locate Unwired Server log files.

1. Browse to <Unwired Platform Install>\Servers\UnwiredServer\logs.
2. Open the log files found there: ml.log to check for critical errors; uwp.log to check for unusual Enterprise Information Server interactions.
3. If the ml.log file is displaying too much or too little detail, use Sybase Control Center to increase or decrease the logging level that you want recorded.

Sybase Control Center > Administer > Unwired Server > Manage > Logs

Under the specified online help topic, no instructions are provided for creating and deploying a package from the command line in the Sybase Unwired WorkSpace Eclipse Edition environment.

Workaround: See Creating and Deploying a Package From the Command Line - Sybase Unwired WorkSpace Eclipse Edition.

Sybase Unwired WorkSpace > Develop > Developing a Mobile Business Object > Packaging and Deploying Mobile Business Objects

In the specified online help topic, the instructions for propagating a client's credentials to the backend data source are not provided.

Workaround: Use the following instructions:

Use client credentials to establish enterprise information system (EIS) connections on the client's behalf for all data source types.

To use client credentials, map an EIS connection's username and password properties to system-defined "username" and "password" personalization keys, respectively. This creates a new connection for each client and the connection is established for each request (no connection pooling).

1. During development of the mobile business object (MBO)/operation, from the Authentication Information page, which is available either in the Mobile Business Object Creation wizard or from the Detailed Properties dialog, in the Use Personalization Key section (or HTTP Basic Authentication section for a Web Service MBO), enter the client credentials in the User name and Password fields.
2. During deployment of the package that contains such MBOs, map the design-time connections to the existing or new server connections, but be aware that the user name and password portions for the selected server connection are replaced by the user name and password propagated from the device application.
3. If you select to override the default authentication, either statically or dynamically, for a database data source, you must provide a mapping at deployment time between the client-side connection profile and the JDBC connectivity properties for the server to use.

Develop > Developing a Mobile Business Object > Working with Mobile Business Objects > Binding a Mobile Business Object to a Data Source

In the specified online help topic loop point description is inadequate.

<SOAPResponse>
...
    <GetListBy_Requester_LoginResponse>
      <getListValues>
        <Assignee_Login_Name>Demo</Assignee_Login_Name>
        ...
      </getListValues>
      <getListValues>
        <Assignee_Login_Name>XYZ</Assignee_Login_Name>
        ...
      </getListValues>
    </GetListBy_Requester_LoginResponse>
</SOAPResponse>

Workaround: None

Sybase Unwired WorkSpace > Sybase Unwired WorkSpace > Develop > Developing a Mobile Business Object > Working With Mobile Business Objects > Binding a Mobile Business Object to a Data Source > Binding a Mobile Business Object to a Web Service

The description of how NULL is handled is incorrect in the online help topics. The documentation states:

Passing NULL instead of an empty string tells the server to first try and use personalization, then try with a default value and finally to pass NULL to the back-end system.

Currently, if a parameter is NULL and personalization is not defined, and there is no default value, an error is returned.

Workaround: Do not select NULL as a parameter value.

Configuring Synchronize Action Inputs" (Sybase Unwired WorkSpace > Develop > Developing a Device Application > Designing the Screen for Device Applications > Assigning an Action to a Control > Device Application Designer

Sybase Unwired WorkSpace > Develop > Developing a Device Application > Designing the Screen for Device Applications > Assigning an Action to a Control > Configuring an Operation Action

You can browse to a .jar file containing a new JDBC driver when setting up a connection profile. After the .jar file has been identified, the Database Explorer and Visual SQL features are able to use the driver and connect to the database. However, this .jar file is not available to the JdbcEISOperationImpl or CCLJDBC classes while extracting parameter metadata or doing a preview.

Workaround: Replace that topic with Connecting to a Database Using a JDBC Driver,

Sybase Unwired WorkSpace > Set Up > Creating a Data Source Connection Profile > Creating a Database Connection Profile > Connecting to a Database Using a JDBC Driver

Step 4 of the topic " Configuring CDB Properties" incorrectly states that you can change the DB server and DB server port using the Sybase Control Center console.

Workaround: None. These properties cannot be changed using the Sybase Control Center console.