System Administration

The following issues were identified in this document. These issues could not be corrected in time for publication.

Title	Summary
Setting Up Data Tier Nodes	Step three in the Setting Up Data Tier Nodes topic refers to the 1.5.2 Installation Guide topic, Installing the Data Tier on a Separate Host for a Deployment Installation. This topic is now called Installing the Data Tier on its Own Host for a Deployment Installation. Note: For cluster setup information, see 1.5.5 System Administration starting with the topic Implementing an N+2-node Cluster for Optimal Redundancy.
Backing Up System Data	Default locations for Unwired Server and Sybase Control Center database and transaction log files have been added to Backing Up System Data. This information would also be useful for: System Administration > Introduction to Sybase Unwired Platform > Platform Components > Runtime Databases System Administration > Systems Maintenance and Monitoring > Backup and Recovery > Backing Up System Data > Backing Up a SQL Anywhere Database > Validating and Backing Up Platform Data
Managing Backup Transaction Logs	Sybase recommends that you manage the size of transaction logs as part of your backup and restore policy. See Managing Transaction Logs for information.
Server Performance Tuning	A new property was added to support messaging performance. The message size limitation can be changed by modifying an internal Unwired Server property, sub.msg.mzx_content_size. If you feel the 20KB value should be changed, work with your Sybase representative. The current message size limit for Unwired Server is 20KB. In general, enlarging the message size results in a lower number of messages, and higher efficiency. Performance also depends on the device environment. A message that is too large stresses the device, and negates efficiency. Device factors include memory and size of the object graph being sent. In some cases, a larger message size terminates message processing. When the Unwired Server message size exceeds the limit, the message is immediately sent to the client side.
Apple Provisioning for iOS	A new 2048-bit Entrust certificate needed for Apple Push Notification Service (APNS) push to work, because APNS push functionality stops working on 22 December 2010. Apple now uses a 2048-bit root certificate from Entrust, which provides a more secure connection between Unwired Server and APNS. This certificate comes with the Windows OS, and is upgraded automatically with Windows Update, if it is enabled. This information is not part of the procedure that documents APNS support. If Windows Update is disabled, you must manually download and install the certificate. Go to: https://www.entrust.net/downloads/binary/entrust_2048_ca.cer. For help on installing the certificate, see http://www.entrust.net/knowledge-base/technote.cfm?tn=8282.