Configuring Mobile Access

To 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.

To 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.

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:

• User Information

• Bookmark

• PersonalNotes

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:

• HDML (Handheld Device Markup Language)

• cHTML (compact Hypertext Markup Language)

• iHTML (i-mode Hypertext Markup Language)

• JHTML (J-Sky Hypertext Markup Language)

• XHTML (Extensible Hypertext Markup Language)

• WML(Wireless Markup Language)

• VoiceXML(Voice eXtensible Markup Language) and HTML (Hypertext Markup Language)

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:

• Enable users to bypass the password prompt when logging into the mobile Portal Desktop.

• Enable users to log on as anonymous users.

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

• Container Channels

• Providers

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:

• JSPNativeContainer

• WirelessDesktopDispatcher

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:

• Content in a file

• Output from an application

• Output from a service

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:

• WirelessDesktopDispatcherProvider

• WirelessJSPDesktopProvider

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