Following are important concepts for understanding the mobile application playback process in UA.This information is provided to help you troubleshoot problems and advise developers.
Playback is generated in the UA server, and the data is then sent through one of a number of possible routes to the mobile device.
When playback is requested for a mobile application, the SSCA defined on an application can have a significant performance impact, as the full spidered data is generated before the data is returned to the mobile device. Using application caching in conjunction with agents can help improve performance.
The same CCL code is used to retrieve data whether you access the data using a mobile device or using Mobile Web Studio. If there are problems with the data accessed through a PDA, try using Web Studio to view the same data to see if the problem lies with the PDA client side or the playback within UA.
Use personalization to control how a particular application’s content is generated (in cases where content generation can be controlled by parameters).
The Unwired Accelerator client, including the BlackBerry, Symbian/J2ME, and .NET clients, and M-Business Server’s database channels require grid data, and the application must have either a single element, or multiple elements mapped to a virtual grid using labels.
For encoding issues on the PDA client, try adjusting the application encoding setting. In general, the best choice is probably UTF-8.
