test

Sun Java System Portal Server 7.2 Administration Guide

Chapter 12 Managing Portal Server Mobile Access

This chapter provides information about how to configure Mobile Access in Portal Server 7.2, how to mention the change in success URL

The following topics are discussed:

Introduction to Mobile Access

Mobile Access extends the services and capabilities of Sun Java System Portal Server platform to mobile devices, such as mobile phones and personal digital assistants.

Mobile Access software enables portal site users to obtain the same content that they access using browsers that require HyperText Markup Language (HTML). It supports Sun Java System Portal Server Secure Remote Access software and uses Sun Java System Access Manager software's administration console.

The features of the Mobile Access product are integrated seamlessly into Portal Server software. If you know how to administer Portal Server software, understanding how to administer Mobile Access software will not be difficult.

Configuring Mobile Access

ProcedureTo Configure Mobile Access in Portal Server 7.2.

  1. Login to the Portal Server Management Console.

  2. Click the Portals tab.

  3. Click the portal1 portal from the list of available portals.

  4. Select EnterpriseSample from the SelectDNdrop down list.

  5. Change the value of ParentContainer field available in the Desktop Attributes to WirelessDesktopDispatcher.

ProcedureTo Enable Mobile Access Anonymous Desktop

  1. Login to the Portal Server Management Console.

  2. Click the Portals tab.

  3. Click a portal from the list of available portals.

  4. Select TopLevel (Global) from the Select DN list.

  5. Under Valid UIDs for Anonymous Desktop, set the default User DN for anonymous deployment of the portal.

    To enable portal users to access the Enterprise Sample Anonymous Mobile Desktop using a mobile device, set the default User DN to anonymousenterprise.

Procedure To Mention the Change in Success URL

  1. Login to the Access Manager Console.

  2. Select the Service Configuration tab.

  3. Click Core under Authentication Modules.

  4. Edit the property of the Default Success Login URL to /portal/dt.

Mobile Access Software

Knowledge of the following Mobile Access software features and how they extend the functions of Portal Server software are useful:

The Portal Desktop

Your portal site provides a mobile Portal Desktop as well as a standard Portal Desktop. A wireless desktop dispatcher, which is a component of the Mobile Access software, controls them. The Portal Server desktop servlet forwards requests to the wireless desktop dispatcher. The wireless desktop dispatcher uses display profile configuration data to determine which Portal Desktop—standard or mobile—is the appropriate one to route user requests to. Regardless of how the user accesses a portal site, the Portal Desktop is the user's interface for the portal site.

These channels are available and visible by default on the mobile Portal Desktop:

For more details on the mobile Portal Desktop, see Managing the Mobile Portal Desktop

Client Types

Mobile Access software supports virtually every mobile device available. It uses a client profile to identify each mobile device, or client. It assigns each client a unique identifier called client type, based on the device markup language the device's browser uses.

These markup languages include:

Mobile Access software certifies WML support for the Nokia 6310i client and cHTML support for the Handspring Treo 180 client, although users can access portal content with any mobile device that uses one of these markup languages.

The Client Manager, which is part of the administration console of Access Manager, is used for managing client profiles. For details about mobile client type and device detection, see Chapter 2

Mobile Access Authentication Modules

Mobile Access software supports the authentication modules that Portal Server software provides, but it also allows you to:

For details on using these authentication modules, see Configuring Mobile Authentication.

Channels, Containers and Providers

Mobile Access software uses providers, channels, and containers to present content to the mobile Portal Desktop.

This section provides information on:

Channels

Channels display content in the mobile Portal Desktop. A channel consists of the provider object, configuration settings, and data files (such as templates) required to support the channel.

Container Channels

A container, or container channel, is a channel that displays content in the mobile Portal Desktop by aggregating the content of other channels. Mobile Access software adds the following default container channels to those included with Portal Server software:

Providers

Providers are the underlying implementation that present channel content to users on the mobile Portal Desktop. They adapt the interfaces of generic resources.

Provider content sources can include:

Providers, which are Java class files, deliver content in the proper format for each type of mobile device. As a mobile Portal Desktop is created, each provider is queried for the content of its associated channel.

The following new providers are added to the default containers:

For details on using channels, containers, and providers to configure the mobile Portal Desktop, see Managing the Mobile Portal Desktop.

Managing Mobile Devices

Sun Java System Portal Server Mobile Access 7.2 software uses Sun Java System Access Manager client detection module to identify and manage the various clients, or mobile devices, that portal site users employ to access a portal site.

This section provides information on the following topics:

Understanding Client Detection

Client detection determines the capabilities and characteristics of each mobile device that is used to access the portal site. To do this, it uses the composite capability and preference profiles (CC/PP) specification, UAProf, or preconfigured data. Mobile Access software requires that three properties be defined for every client. They are:

Mobile Access software also uses conditional properties to store and retrieve specific property values for client types. One example is the desktopContainer conditional property. The wireless desktop dispatcher reads this property to determine what the desktop container is for the requested client type.

Mobile Access software imports client type data from the file /var/opt/SUNWam/config/ldif/sunAMClient_data.ldif into the LDAP directory and uses Access Manager software APIs to identify clientType property matches. Matches are determined in the following order:

  1. An exactmatch

  2. A partialmatch

  3. A keywordmatch

You can also dynamically apply UAProf profile against your base profile. Users need to retain FEDIClientDetector and do one of the following:

Note –

To configure the proxy server to selectively access the public internet:

The JVM provides an option to specify proxy server details for an external connection from the web container using an external proxy. The JVM also allows you to specify the hosts that should not use the specified proxy. You can configure the Mobile Access system JVM to use a proxy server to access the public Internet.

Use the following JVM options in the web container:

Dhttp.proxyHost=your-proxy-server-host

Dhttp.proxyPort=your-proxy-server-port

Use the following option for bypassing proxy server for certain domains and hosts: Dhttp.nonProxyHosts="*.domain-name|hostname|localhost"

Using the Client Manager

The Access Manager administration console provides a Client Manager that enables you to manage properties for mobile devices.

This section explains the following types of information that the Client Manager provides about client types:

This section also explains how to create and customize the client type:

Markup Languages

Mobile Access software supports these markup languages used by mobile client browsers:

Styles

A Style is a set of properties for an associated group of devices for a markup language. For example, a Nokia Style is applied to all WML devices manufactured by Nokia.

At least one Style exists for each markup language. Some markup languages have multiple styles.

You cannot override Style properties. If you use an existing client as a template for a new devices when you create it, the new client inherits the existing client's Style properties.

Device Information

Device information is device-specific client type data that you can update.

When you change the device information for a default client type, you create a new and separate version of the default client type. This custom information is stored in the external library, while the default device information remains in the internal library. Two asterisks are added to the client type name of each custom device to differentiate it from devices in the internal library.

Filter Option

The Filter option is a search field that enables you to find and list groups of specific client types assigned to a specific Style.

Client Editor

The Client Editor enables you to create and customize a client type, and to manage client properties.

The Client Editor organizes properties in the following groups:

ProcedureTo Launch the Client Manager

  1. Log in to the Access Manager administration console as the administrator. By default, Identity Management is selected in the Header frame (the top horizontal frame) and Organizations is selected in the Navigation frame (the left vertical frame).

  2. Click the Service Configuration tab.

  3. From the Service Configuration frame on the left, under the Access Manager Configuration heading, click the arrow for Client Detection. The Client Detection global preferences appear in the Data frame on the right.

  4. Click the Edit link following the Client Types label. The Client Manager interface appears. Details about HTML devices are displayed by default.

ProcedureTo View Style Properties

  1. Log in to the Access Manager administration console as the administrator. By default, Identity Management is selected in the Header frame (the top horizontal frame) and Organizations is selected in the Navigation frame (the left vertical frame). 2. 3. 4.5 6. 7. 8.

  2. Click the Service Configuration tab.

  3. From the Service Configuration frame on the left, under the Access Manager Configuration heading, click the arrow for Client Detection. The Client Detection global preferences appear in the Data frame on the right.

  4. Click the Edit link following the Client Types label. The Client Manager interface appears. Details about HTML devices are displayed by default.

  5. .From the tabs at the top, click the markup language for the device whose properties you want to examine (for example, WML). If client types using the markup language you selected are in the database, they appear in alphabetical order.

  6. From the Style pull-down menu, pick the style that you want (for example, Nokia). The list of client types already in the database appears for the selected style.

  7. Click the Current style properties link. The Edit style page appears. The Styles for General properties are displayed by default.

  8. From the Properties pull-down menu, click the properties type that you want to view (for example: Software Platform).

    Note –

    Properties type choices include General, Hardware Platform, Software Platform, Network Characteristics, BrowserUA, WapCharacteristics, PushCharacteristicsNames, and Additional Properties.

  9. To return to the Client Manager page, click Cancel.

Managing Client Type Data

You use the Client Manager in the administration console to manage client type data.

You can change client type properties, create new client types to accommodate new devices, set up client types with names and other properties that are customized for your site, and remove custom client types.

If you choose to create a new device based on an existing device, a process called inheriting, you must base the new device on either the styles or the properties of the existing device. Examine your new device and the existing device to decide which option—styles or properties—is preferable. Both choices require you to customize device definitions.

Note –

The client type database consists of internal and external libraries. When you change or add to default client type information in the internal library, your updates are stored in the external library. Two asterisks added to the client type name indicate that it is a customized client type.

This section provides instructions for completing the following tasks:

ProcedureTo Edit Client Types

  1. Log in to the Access Manager administration console as the administrator. By default, Identity Management is selected in the Header frame (the top horizontal frame) and Organizations is selected in the Navigation frame (the left vertical frame).

  2. Click the Service Configuration tab.

  3. From the Service Configuration frame on the left, under the Access Manager Configuration heading, click the arrow for Client Detection. The Client Detection global preferences appear appear in the Data frame on the right.

  4. Click the Edit link following the Client Types label. The Client Manager interface appears. Details about HTML devices are displayed by default.

  5. From the tabs at the top, click the markup language for the device you want to edit (for example, WML). If client types using the markup language you selected are in the database, they appear in alphabetical order.

  6. From the Style pull-down menu, pick the Style that you want (for example, Nokia). The list of client types already in the database appears for the selected style.

  7. From the Client Type list, scroll down to find the client that you want to edit (for example, Nokia6310i_1.0).

    Clients are listed in alphabetical order.

  8. To go directly to a specific client type, or to a group of client types, use the Filter option. In the Filter text box, type in the first character or first few characters of the client type you want to view and then click the Filter button. (For example: To find client types that start with the letter S, type in S*.)

  9. To go to specific pages, scroll to the bottom and use the arrows or the Go option.

  10. Click the Edit link in the Actions column for the client that you want to edit. The Edit client-type page is displayed. The General properties are displayed by default.

  11. From the Properties pull-down menu, select the type of properties you want to change (for example, Software Platform).

  12. Change or add values for each property you want to alter.

    Tip –

    To clear your changes and start over, click Reset. To return to the display of client types without making any changes, click Cancel.

  13. Click Save to make these changes.

    If you do not click Save, your changes are not made. You must change one property type at a time and save those changes before you change another property type.

    The properties for this device are now changed, and the list of client types for this style appears.

  14. To verify that its properties are changed, find your client type in the Client Type list. Two asterisks added to the client type name indicate that you have customized this client type.

    Note –

    Whenever you change a default client type, a Default link is added to the Actions column. The Default link points to the internal library.

    To remove your changes and reset the client type's properties to their default values, click this link. A prompt asking whether you want to complete this action is not provided.

ProcedureTo Create a New Device by Inheriting Styles

  1. Log in to the Access Manager administration console as the administrator. By default, Identity Management is selected in the Header frame (the top horizontal frame) and Organizations is selected in the Navigation frame (the left vertical frame).

  2. Click the Service Configuration tab.

  3. From the Service Configuration frame on the left, under the Access Manager Configuration heading, click the arrow for Client Detection. The Client Detection global preferences appear in the Data frame on the right.

  4. Click the Edit link following the Client Types label. The Client Manager interface appears. Details about HTML devices are displayed by default.

  5. From the tabs at the top, click the markup language for the device you want to set up (for example, WML). If client types using the markup language you selected are in the database, they appear in alphabetical order.

  6. From the Style pull-down menu, pick the Style that you want (for example, Nokia). The list of client types already in the database appears for the selected style.

  7. Click the New Device button to display the Create New Device page.

  8. Type in the Device User Agent value.

  9. Click Next. The Device User Agent value you provided appears in the Client TypeName and The HTTP user-agent string fields.

    If appropriate, change these values.

  10. Click OK to save these properties. Your new device is now defined, and the Edit Style page appears. Displayed here are default properties inherited from the parent Style you assigned.

  11. From the Properties pull-down menu, select the properties type that youwant to modify (for example: Software Platform).

    Note –

    Properties type choices includeGeneral,Hardware Platform, Software Platform, Network Characteristics, BrowserUA, WapCharacteristics, PushCharacteristicsNames, and Additional Properties.

  12. Click Save to save your changes to these values.

    Tip –

    To clear your changes and start over, click Reset. To return to the display of client types without making any changes, click Cancel.

  13. Search the Client Type list to verify that your client type is available. Two asterisks added to the client type name indicate that you have customized this client type.

    Note –

    Whenever you add a new client type, a Delete link is added to the Actions column. The Delete link points to the external library.

  14. To remove your new client type, click this link. A prompt asking whether you want to complete this action is not provided.

ProcedureTo Create a New Device by Inheriting Properties

  1. Log in to the Access Manager administration console as the administrator. By default, Identity Management is selected in the Header frame and Organizations is selected in the Navigation frame.

  2. Click the Service Configuration tab.

  3. From the Service Configuration frame on the left, under the Access Manager Configuration heading, click the arrow for Client Detection. The Client Detection global preferences appear in the Data frame on the right.

  4. Click the Edit link following the Client Types label. The Client Manager interface appears. Details about HTML devices are displayed by default.

  5. From the tabs at the top, click the markup language for the device you want to copy (for example, WML). If client types using the markup language you selected are in the database, they appear in alphabetical order.

  6. From the Style pull-down menu, pick the default Style that you want (for example, Nokia). The list of client types already in the database appears for the selected style.

  7. From the Client Type list, scroll down to find the specific client that you want to use as a template for a new client type (for example, Nokia6310i_1.0).

    Tip –

    Clients are listed in alphabetical order.

  8. To go directly to a specific client type, or to a group of client types, use the Filter option. In the Filter text box, type in the first character or first few characters of the client type you want to view and then click the Filter button. (For example: To find a client type that starts with the letter S, type in S*.)

  9. To go directly to specific pages, scroll to the bottom and use the arrows or the Go option.

  10. Click the Duplicate link in the Actions column for the client type that you want to use as a template for a new client type. The Duplicate Device page is displayed. The Client Type and Device User Agent properties for the device you are copying are displayed, with the prefix Copy_of_ added to its name. (For example, Copy_of_Nokia6310i_1.0)

  11. If appropriate, type in new names for these properties.

  12. Click Duplicate to make these changes. The Edit client-type page is displayed. The General properties are displayed by default. The values for all properties views available here are inherited from the client type that you used as the master for this new client type.

    Tip –

    To return to the display of client types without making any changes, click Cancel. From the Properties pull-down menu, select which type of properties you want to change (for example, Software Platform).

  13. Change or add values for each property you want to alter.

    Tip –

    To clear your values and start over, click Reset. To return to the display of client types without making any changes, click Cancel.

  14. Click Save to make these changes.

    Note –

    If you do not click Save, your changes are not made. You must change one property type at a time and save those changes before you change another property type. The properties for this device are now changed, and the list of client types for this style appears.

  15. Search the Client Type list to verify that your client type duplicate is available. Two asterisks added to the client type name indicate that you have customized this client type. (For example, Copy_of_Nokia6310i_1.0 **)

    Note –

    Whenever you add a new client type, a Delete link is added to the Actions column. The Delete link points to the external library.

  16. To remove your new client type, click this link. A prompt asking whether you want to complete this action is not provided.

ProcedureTo Remove a Custom Device

If you set up a custom device incorrectly and do not want to modify it, you can use these steps to remove it entirely.

  1. Log in to the Access Manager administration console as the administrator. By default, Identity Management is selected in the Header frame (the top horizontal frame) and Organizations is selected in the Navigation frame (the left vertical frame).

  2. Click the Service Configuration tab.

  3. From the Service Configuration frame on the left, under the Access Manager Configuration heading, click the arrow for Client Detection. The Client Detection global preferences appear in the Data frame on the right.

  4. Click the Edit link following the Client Types label. The Client Manager interface appears. Details about HTML devices are displayed by default.

  5. From the tabs at the top, click the markup language for the device you want to delete (for example, WML). If client types using the markup language you selected are in the database, they appear in alphabetical order.

  6. From the Style pull-down menu, pick the Style that you want (for example, Nokia). The list of client types already in the database appears for the selected style.

  7. From the Client Type list, scroll down to find the customized client that you want to remove (for example, Copy_of_Nokia6310i_1.0).

    Tip –

    Clients are listed in alphabetical order

  8. To go directly to a specific client type, or to a group of client types, use the Filter option. In the Filter text box, type in the first character or first few characters of the client type you want to view and then click the Filter button. (For example: To find a client type that starts with the letter S, type in S*.)

  9. To go directly to specific pages, scroll to the bottom and use the arrows or the Go option.

  10. In the Actions column for the customized client that you want to remove, click the Delete link. The revised list of client types for this style is displayed.

  11. Search the Client Type list to verify that your client type is no longer available.

ProcedureTo Identify Selected Client Types for a Portal User From the Portal Server Console

  1. Log in to Portal Server administration console as the administrator. By default, the Common Tasks tab is selected and the Common Administrative Tasks page is displayed.

  2. Click the Portals tab. The Portals page is displayed. The available portals are displayed in the Portals table.

  3. Click on the name of the portal, which you want to manage. The Desktop Tasks and Attributes page is displayed. This page lists the Portal Server desktop tasks and attributes that you can edit.

  4. From the SelectDNoptions, choose the username (User) DN. If the username (User)DNoption is not available, you need to add this DN to the SelectDNlist. Follow the steps to add the username (User)DN.

    1. Click the Add DNs button. The Add to DNs list window appears.

    2. From the Search for options, choose the User option.

    3. Type the user name in the text box after the User option.

    4. Click Search. If the user name is available, it will be displayed in the Found table.

    5. Select the check box preceding to the user name you want to add and click Add The username (User)DN is added to the SelectDNoptions.

  5. From the list of Tasks, click the Manage Containers & Channels. The Manage Containers & Channels: Portal name page is displayed. The left frame in this page displays the available View Types and the right frame displays the properties of the selected View Type.

  6. From the ViewType options, choose the WirelessDesktopDispatcher option. The WirelessDesktopDispatcher Tasks and Properties are displayed in the right frame.

  7. In the Properties table, select the check box preceding to the selectedClients property.

  8. Click the Table Preferences button if you need to change the client type and locale settings. Client type settings are necessary to set a client type for the portal, and the locale settings are necessary to set the language attributes.

    The Table Preferences box appears at the top of the Properties table.

  9. In the Client Type and Locale fields, type the appropriate client type and locale information.

  10. Click OK.

  11. Click Save.

    The client type is added in the Value column.

Configuring Mobile Authentication

Portal Server Mobile Access software supports the authentication modules provided by Sun Java System Portal Server software. This chapter describes three authentication modules that can be useful to portal sites offering mobile access:

NoPassword Authentication

If your site specifications require it, you can allow users to log in to the mobile PortalDesktop without being prompted for a userID.

ProcedureTo Enable the NoPassword Module From the Access Manager Console

  1. Log in to the Sun Java System Access Manager administration console as the administrator. By default, Access Control tab is selected and the Realms page is displayed. You can see the available Realm Names in the Realms table.

  2. Click the india realm. The india?Properties page is displayed under which the Realm Attributes of india realm are listed.

  3. Click the Authentication tab. The india?Authentication properties are displayed. Check whether the NoPasswordModule Instance is available under the Module Instances table.

  4. Click the ldapService Authentication Chaining in the Authentication Chaining table. The ldapService?Properties page is displayed. The available Instances are displayed.

    Note –

    If you does not have the ldapService as the Default Authentication Chain or the Administrator Authentication Chain, then you would not be enforced for NoPassword Authentication. If NoPassword authentication is required, then add the NoPassword to the respective configured Authentication Chain. For Default Authentication Chain, add the NoPassword to the respective configured Authentication Chain. In the default installation scenario both will be configured for ldapService.

  5. Choose the NoPassword instance.

  6. Click the Add button. The NoPassword instance is added to the Instance list.

  7. Click the Save button. You will get the information that the authentication chain properties were updated.

  8. Click the Logout button.

  9. Try to login again to the Sun Java System Access Manager administration console. You will get a message that This server uses NoPassword Authentication.

Anonymous Authentication

If you want a user to access your portal site to explore what the experience of an authenticated user is, you can allow users to log in to the mobile Portal Desktop as anonymous users. This feature presents a snapshot of the mobile and voice Portal Desktop of a user with an authenticated session.

Note –

Anonymous users cannot change, store, or alter the content or configuration of channels with stateful data. If you support anonymous authentication, make sure that these channels are not available to these users.

To implement anonymous authentication, see the Sun JavaTM System Portal Server 7.1 Administration Guide.

The Portal Desktop for anonymous authentication uses the WirelessDesktopDispatcher as well as device-specific containers for both JavaServer PagesTM (JSPTM) software and templates. All channels to be displayed to the anonymous user must be included in these containers, just as they are for authenticated users.

ProcedureTo support a new device that may need a client-specific mobile or voice PortalDesktop for an anonymous user.

  1. Create the appropriate device-specific container.

  2. Alter the WirelessDesktopDispatcher in the anonymous user?s display profile to use the new container for that particular device type.

MSISDN Authentication

The users of an organization can be configured to authenticate using MSISDN-Mobile Station ISDN, a standard international telephone number used to identify a given subscriber. This allows the users to log into the mobile portal desktop without the user passing authentication credentials. This feature limits the format of the login URL. The following format for the URL is recommended:

http://access-manager-host:port/service-deploy-URI/UI/Login?module-MSISDN&org-name

To implement MSISDN authentication and how to configure it, see the Sun Java System Access Manager 7 2005Q4 Administration Guide.

Managing the Mobile Portal Desktop

Portal Server Mobile Access software uses the Portal Server administration console to manage the mobile Portal Desktop.

Note –

In order to understand the information provided in this chapter and manage the mobile Portal desktop, you need to know the Portal Server administration console.

This section discusses the following topics:

Understanding the Wireless Desktop Dispatcher

Once you install Mobile Access software, your Portal Server site provides a mobile 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—is the appropriate one to route user requests to.

The wireless desktop dispatcher:

The default channel for the mobile Portal Desktop is the WirelessDesktopDispatcher. Follow the steps to edit the WirelessDesktopDispatcher container from the Portal Server 7.2 administration console to support other containers for particular devices.

ProcedureTo Edit the Parent Container in Portal Server 7.2 Administration Console

  1. Log in to the Portal Server 7.2 Administration Console as administrator.

  2. Click the Portals tab. The available Portals are displayed.

  3. Click on the name of the Portal, which you want to manage.

  4. Choose the Org option from the SelectDN drop down list box. The Desktop Tasks and Attributes page is displayed. The Parent Container attribute is available under the Desktop Attributes. The top level container value in the display profile for the selectedDN is displayed in the Parent Container text box.

  5. Edit the value in the Parent Container text box to support other containers for particular devices.

  6. Click Save.

Wireless Desktop Dispatcher Properties

This section describes the properties listed for the WirelessDesktopDispatcher container.

The wireless desktop dispatcher properties include:

This property is also used to display a list of devices on the Mobile Devices edit page in the standard Portal Desktop. Individual users can view what devices they have used, and they can add to the list simply by logging into the mobile Portal Desktop with other devices.

ProcedureTo Navigate To the WirelesDesktopDispatcher Container Properties Page

  1. Log in to the Portal Server 7.1 Administration Console as administrator. The Common Administrative Tasks page appears.

  2. Under Configuration, click the Manage Channels & Containers button. The Data Collection pop up window appears.

  3. From the Select Portals drop down list box, choose the Portal you want to manage.

  4. From the SelectDNdrop down list box, choose the DN.

  5. Click OK. The WirelessDesktopDispatcher container tasks and properties are listed in the right frame. You can modify the values of these properties in this page.

  6. Edit the value in the editContainerName text box, to suit the appropriate device.

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.

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

client=Nokia —> desktopContainer=JSPNativeContainer

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 . They allow an end user to display only a channels title bar on a mobile PortalDesktop instead of loading a channels content inline.

Note –

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: