Documentation Issues and Updates for Unwired Platform Runtime 2.1 ESD #3 Patch 02

Read about updates, corrections, and clarifications to the documentation released with Sybase Unwired Platform Runtime 2.1 ESD #3 Patch 02.

Issue NumberDescription
N/A
Security configuration does not require LDAP provider to authenticate logins

In the first paragraph of the NTProxy Security Provider topic in Security, this second sentence is incorrect and should be disregarded:

Add an LDAP provider to a security configuration to authenticate administrator logins (on the "admin" security configuration on the "default" domain) or device user logins (any custom security configuration for that purpose).

NTProxy Security Provider is found in:
  • Security > Server Security > Enabling Authentication and RBAC for User Logins > Authentication in Unwired Platform > Built-in Security Providers for User Authentication and Authorization
N/A
Domain names are case insensitive

The Creating and Enabling a New Domain topic in System Administration should state that domain names are case insensitive.

To read the note in context, see Creating and Enabling a New Domain.

RTC-366
Missing info in Update Properties (updateprops.bat) Utility topic
Two notes were added to Update Properties (updateprops.bat) Utility, located in System Administration:
  • Unless documented otherwise, use Sybase Control Center to change most properties in the runtime to avoid unnecessary complication.
  • The -r, -x, and -f options are reserved for internal product use only. While these options are supported by the command line, they are not intended for administrator use.

You can read an updated version of the topic in this release bulletin. See Update Properties (updateprops.bat) Utility.

CR 736637
Cannot add custom JCO properties

You cannot add custom JCO connection properties. See http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01332.0213/doc/html/dst1255703078075.html for more information about SAP Java Connector Properties.

CR 717585
Binary Personalisation parameter has limits on data size

In Sybase Unwired Workspace - Mobile Business Object Development > Develop > Working with Mobile Business Objects > Mobile Business Object Data Properties > Managing Persionalization Keys > Personalization Key Guidelines and Limitations there is additional information:

When assigning a personalization key that uses a binary datatype to an operation argument or load argument with BIGBINARY type, if the data in the personalization key exceeds 35K, the server throws exceptions during synchronization:

[LNSupController+Finalize.m:61] Send data ExceptionSUPPersistenceException: SUPPersistenceException from synchronize: -- SUPSynchronizeException: loginFail,Sync failed: -1497 (ERROR) %1:4 %2:4000

When a binary personalization is assigned to an operation argument or a load argument, its size cannot exceed 35K. Additionally it is not recommended to map a personalization key to big object types such as BIGSTRING or BIGBINARY.