Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Portal Server Mobile Access 7 Administration Guide 

Chapter 4
Managing the Mobile Portal Desktop

Portal Server Mobile Acess software uses the Access Manager software’s administration console and portal administration console to manage the mobile Portal Desktop.

This chapter provides the following topics:

Understanding the Wireless Desktop Dispatcher

Once you install Mobile Access software, your Portal Server site provides a mobile Portal Desktop and a voice Portal Desktop as well as a standard Portal Desktop. At the time a user logs in to Portal Server, the wireless desktop dispatcher, which is a component of Mobile Access software, determines which Portal Desktop is the appropriate one to route user requests to.

The wireless desktop dispatcher uses an XML Display Profile configuration to determine which Portal Desktop—standard, mobile, or voice—is the appropriate one to route user requests to. The wireless desktop dispatcher:

The default channel for the mobile Portal Desktop is the WirelessDesktopDispatcher. You can edit the WirelessDesktopDispatcher container to support other containers for particular devices.

Wireless Desktop Dispatcher Properties

The wireless desktop dispatcher properties include:

Conditional Properties

Conditional properties for client types enable administrators to specify properties for a channel or container channel that are specific to a client type. Conditional properties for client types can also be hierarchical, just as client data is hierarchical.

The syntax for a conditional property is client=clientType. For example, client=WML is the name of the conditional property for WML client types.

The desktopContainer property for the wireless desktop dispatcher is an example of a client conditional property for the client type client=WML. By default the definition for this property is desktopContainer=JSPRenderingContainer.

Here is a hierarchical representation of the default desktopContainer property for Nokia devices:

client=WML -> desktopContainer=JSPRenderingContainer

       client=Nokia -> desktopContainer=JSPNativeContainer

Devices within the WML client style use the JSPRenderingContainer. The subset of WML clients defined by the Nokia client style use a different desktopContainer definition, however. They use the JSPNativeContainer.

Channel State Properties

These properties indicate the state of a channel to both the JSPNativeContainer and the JSPRenderingContainer. They allow an end user to display only a channel s title bar on a mobile Portal Desktop instead of loading a channel s content inline.


On the standard Portal Desktop, you can provide buttons on a channel so that the user can minimize or maximize its content. This is not currently supported with the mobile Portal Desktop.

These properties include:

These properties determine whether the Load Channels with desktop check box is to be displayed on the user’s Mobile Devices edit page in the standard Portal Desktop. The default value of both properties is true. The check box thus is displayed. If either property is false, the check box is not displayed.


To display the Load Channels with desktop check box, both values must be true. If either is false, the check box is not displayed.

JSPRenderingContainer Properties

Two advanced properties for the JSPRenderingContainer specify how error pages and edit pages are displayed. These properties are:

Previous      Contents      Index      Next     

Part No: 819-5305.   Copyright 2006 Sun Microsystems, Inc. All rights reserved.