Rendering

Using a mobile device, portal site users can access the same content that they would access using any HTML browser. The process that enables this is a translation process called rendering. Rendering allows you to create content once and display it appropriately on a variety of unique mobile devices.

The mobile rendering component detects devices and formats output for display on mobile devices. It consists of four subcomponents:

• Client detection determines the capabilities and characteristics of each mobile device that is used to access the portal. To do this, it uses the composite capability and preference profiles (CC/PP) specification, UAProf, or preconfigured data.

• A rendering filter passes content to the rendering engine and passes translated device-specific content back to the client, using the content type value set in the JavaServer Pages™ (JSP^TM) software template. It is a servlet filter that is applied to all authentication and application JSP software templates.

• The rendering engine converts AML, a device-independent markup language, to whatever device-specific markup language is appropriate for the client.

  When rendered content exceeds the page size of the target device, the rendering engine paginates it and stores the pages in the response buffer.

• The response buffer stores large output streams as separate, smaller responses so that they fit limited device buffers. The authentication, desktop, and mobile application components use the response buffer.

  When a client device makes a request for another page, it responds with the next page.

Mobile Access software supports both native and rendering channels and containers. Native channels are based onJSP technology and templates that are specific to Nokia WML clients. Clients that support HTML, VoiceXML, and WML use templates for a native Portal Desktop.

Rendering channels also use JSP technology. They enable a user to view a Portal Desktop that displays rendered content that is unique to a specific mobile device. This feature is made possible with the use of Abstract Markup Language (AML) templates that are passed through Mobile Access software’s rendering process. Clients that support cHTML, iHTML, JHTML, XHTML, and HDML require AML templates for a rendered Portal Desktop.