Documentation Issues and Updates for Runtime

N/A – BlackBerry provisioning without Relay Server

For targeting BlackBerry devices with Sybase Unwired Platform 2.1, instead of Relay Server, use a BES service to connect to Unwired Server on the enterprise network. The BES service securely manages messages between Sybase Unwired Platform and devices. Communication from Sybase Unwired Platform to BlackBerry devices is coordinated through the BES and the RIM Network Operating Center (NOC).

696989 – Changing Unwired Server Host Name

In Changing Unwired Server Host Name in both Troubleshooting and System Administration, step 5 is not required for upgrading from Sybase Unwired Platform 2.0 to Sybase Unwired Platform 2.1.

Workaround: Disregard this step when upgrading from Sybase Unwired Platform 2.0 to Sybase Unwired Platform 2.1.

696314 – Troubleshooting: Exception During Upgrade if EA Server and Sybase Unwired Platform Are Installed on Same Machine

When upgrading, an unhandled exception ('System.MissingMethodException') occurred in JMSBridge.exe [8320] is received.

This only occurs if an EA Server installation and a Sybase Unwired Platform installation coexist on the same machine. If there are different versions of the com.sybase.iiop.net.dll files on the system, it causes the exception.

Workaround: Ensure that your environment path includes only the Sybase Unwired Platform com.sybase.iiop.net.dll assembly, if you have EA Server installed on the same machine:

Use a strings command (using UNIX tools for Windows) to check if SetTrustAllCertificates exists on the assembly file that jmsbridge.exe loaded. From a command prompt, enter:
```
>strings -a com.sybase.iiop.net.dll | grep SetTrustAllCertificates 
```
The command reports back with SetTrustAllCertificates if it exists within the assembly.
Remove the EAServer installed com.sybase.iiop.net.dll from the global assembly cache (GAC).

695982 – Clarification Regarding Default SUP Roles

While five roles are available by default for the 'admin' security configuration, only three roles are necessary for enabling role-based access to administrative and DCN interfaces.

Default roles include:

SUP Administrator – The platform administrator for the runtime and mobile artifacts. A required role for the "admin" security configuration. See SUP Administrator and SUP Domain Administrator.
SUP Domain Administrator – The administrator assigned to a domain. A required role for the "admin" security configuration. See SUP Administrator and SUP Domain Administrator.
SUP DCN User – The administrative user for DCNs. A required role for the "admin" security configuration. This role must be mapped in *every* security configuration assigned to deployed MBO packages that receive DCN requests. See SUP DCN User Role.
SUP User, SUP Developer – Sample logical roles that have no impact on administration. Do not map these roles or you may expose administration privileges inadvertently to non-administration users.

Workaround: None.

686207 – Sybase Control Center online help

Setting General Application Properties – in the opening paragraph, the last sentence is not correct and should be removed: "Optionally you can assign an application connection template as well, or you can assign it later."
Retrieving Error Logs – note that error logging is always on, and any error that occurs for any application activity is logged.

685632 – Cannot access remote Unwired Server node in Sybase Control Center

Solution 2 described in Sybase Control Center for Sybase Unwired Platform, "Starting or Restarting a Remote Server from Sybase Control Center Fails" is incorrect. Instead, use this procedure for Solution 2:

On each Unwired Server host, edit the hosts file, located at:
C:\WINDOWS\system32\drivers\etc
Add entries to identify the IP address and fully qualified network name of every other node in the Unwired Server cluster.

674889 – Apple Push Notification Service (APNS) Works on iPad Devices.

These topics incorrectly state that APNS cannot be used with iPad devices:

Apple Provisioning for iOS in System Administration
Apple Push Notification Service Configuration in OData SDK Developer Guide

647034 – Limitation lifted for DOE-C Packet Drop Size property

In the Sybase Control Center topic SAP DOE-C Properties, the Packet Drop Size property value no longer has an upper limit. Disregard the statement about the "2097152 (2MB)" upper limit.