• Aucun résultat trouvé

Administration Guide. iplanet Portal Server: Mobile Access Pack 3.0

N/A
N/A
Protected

Academic year: 2022

Partager "Administration Guide. iplanet Portal Server: Mobile Access Pack 3.0"

Copied!
80
0
0

Texte intégral

(1)

Administration Guide

iPlanet Portal Server: Mobile Access Pack

3.0

November 2001

(2)

Copyright © 2001 Sun Microsystems, Inc. All rights reserved.

Sun, Sun Microsystems, the Sun logo, iPlanet and the iPlanet logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

Federal Acquisitions: Commercial Software—Government Users Subject to Standard License Terms and Conditions

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of the product or this document may be reproduced in any form by any means without prior written authorization of Sun Microsystems, Inc. and its licensors, if any.

THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

________________________________________________________________________________________

Copyright © 2001 Sun Microsystems, Inc. Tous droits réservés.

Sun, Sun Microsystems, le logo Sun, iPlanet, et le iPlanet logo sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et d’autre pays.

Le produit décrit dans ce document est distribué selon des conditions de licence qui en restreignent l'utilisation, la copie, la distribution et la décompilation. Aucune partie de ce produit ni de ce document ne peut être reproduite sous quelque forme ou par quelque moyen que ce soit sans l’autorisation écrite préalable de Sun Microsystems, Inc. et, le cas échéant, de ses bailleurs de licence.

CETTE DOCUMENTATION EST FOURNIE “EN L'ÉTAT”, ET TOUTES CONDITIONS EXPRESSES OU IMPLICITES, TOUTES REPRÉSENTATIONS ET TOUTES GARANTIES, Y COMPRIS TOUTE GARANTIE IMPLICITE D'APTITUDE À LA VENTE, OU À UN BUT PARTICULIER OU DE NON CONTREFAÇON SONT EXCLUES, EXCEPTÉ DANS LA MESURE OÙ DE TELLES EXCLUSIONS SERAIENT CONTRAIRES À LA LOI.

(3)

3

Contents

Preface . . . 7

Who Should Use This Book . . . 7

How This Book Is Organized . . . 7

Documentation . . . 8

Typographic Conventions . . . 9

Chapter 1 Overview . . . 11

Mobile Access Pack Software . . . 11

Client Types . . . 11

Client Awareness . . . 12

Providers and Channels . . . 12

The Desktop . . . 14

The Administration Console . . . 15

Chapter 2 Configuring Mobile Clients . . . 17

Understanding Client Attributes . . . 17

Setting Up a Mobile Client Type . . . 18

Editing Client Attributes . . . 20

Adding Client Attributes . . . 21

Changing Client Attributes . . . 21

Removing Client Attributes . . . 22

Removing Support for a Mobile Client . . . 23

Chapter 3 Configuring Authentication . . . 25

Understanding the Authentication Service . . . 25

Enabling Client Detection . . . 26

Adding an Authentication Module . . . 26

Configuring NoPassword Authentication . . . 28

Configuring Authentication Pages . . . 29

(4)

Configuring Single Sign-on . . . 29

Disabling an Authentication Module . . . 34

Chapter 4 Configuring Address Book . . . 35

Enabling Access to Address Book . . . 35

Configuring Channel Display . . . 38

Configuring Channel Layout . . . 39

Chapter 5 Configuring Bookmarks . . . 41

Creating a New Channel . . . 41

Editing Bookmarks for WML Clients . . . 43

Editing Bookmarks for cHTML Clients . . . 43

Chapter 6 Configuring Calendar . . . 45

Configuring Calendar Server . . . 45

Enabling Access to Calendar Provider . . . 46

Configuring Channel Display . . . 47

Configuring Channel Layout . . . 47

Chapter 7 Configuring Mail . . . 51

Configuring Messaging Server . . . 51

Configuring Channel Display . . . 52

Configuring Channel Layout . . . 53

Chapter 8 Configuring Personal Note . . . 57

Chapter 9 Configuring Postit Notes . . . 59

Chapter 10 Configuring URL Scraper . . . 61

Creating a Provider . . . 61

Setting Up a Client-Specific Channel . . . 62

Serving WML Content as a Link . . . 64

Editing Channel Attributes . . . 65

Removing a Provider . . . 66

Chapter 11 Configuring User Information . . . 67

Chapter 12 Configuring XML Content . . . 69

Creating a New Channel . . . 69

Setting Up a Channel . . . 70

(5)

5

Setting Up XSL Template Files . . . 71

Editing Channel Layout . . . 72

Removing a Provider . . . 73

Replacing the XSL Transformation Engine . . . 74

Index . . . 77

(6)
(7)

7

Preface

The iPlanet™ Portal Server: Mobile Access Pack Administration Guide provides overview information and instructions for managing the iPlanet Portal Server:

Mobile Access Pack administration functions.

This guide presents details that you need to provide mobile access to your portal site and to complete ongoing maintenance tasks.

Who Should Use This Book

The iPlanet Portal Server: Mobile Access Pack Administration Guide is for people who use Portal Server ‘s Administration Console to manage mobile access to portal sites. You should already be familiar with the system administration functions of the iPlanet Portal Server 3.0, Service Pack 3a.

If you plan to deliver mail and calendar channels using the Messaging Server and the Calendar Server, you should also be familiar with the following:

• iPlanet Messaging Server 5.1

• iPlanet Calendar Server 5.0p3

Familiarity with basic UNIX system administration and networking is assumed.

How This Book Is Organized

This book contains the following chapters:

Chapter 1, “Overview” provides an overview of the iPlanet Portal Server: Mobile Access Pack software and explains the basics of the Administration Console.

(8)

Documentation

Chapter 2, “Configuring Mobile Clients” describes the data objects involved in defining a mobile client and provides step-by-step instructions for setting up and changing mobile client definitions.

Chapter 3, “Configuring Authentication” describes the authentication service and provides step-by-step instructions for managing authentication tasks.

Chapter 4, “Configuring Address Book” explains how to configure the address book provider and channel, and includes step-by-step procedures for doing so.

Chapter 5, “Configuring Bookmarks” explains how to configure the bookmarks provider and channel, and includes step-by-step procedures for doing so.

Chapter 6, “Configuring Calendar” explains how to configure the calendar provider and channel, and includes step-by-step procedures for doing so.

Chapter 7, “Configuring Mail” explains how to configure the mail provider and channel, and includes step-by-step procedures for doing so.

Chapter 8, “Configuring Personal Note”explains how to set up the personal notes provider and channel, and provides step-by-step procedures for doing so.

Chapter 9, “Configuring Postit Notes” explains how to set up the postit content provider and channel, and provides step-by-step procedures for doing so.

Chapter 10, “Configuring URL Scraper” explains how to create a new URL scraper channel and provides step-by-step procedures for doing so.

Chapter 11, “Configuring User Information” explains how to set up the user information provider and channel, and provides step-by-step procedures for doing so.

Chapter 12, “Configuring XML Content” explains how to create a new XML content channel and provides step-by-step procedures for doing so.

Documentation

Mobile Access Pack documentation includes:

iPlanet Portal Server: Mobile Access Pack Release Notes

iPlanet Portal Server: Mobile Access Pack Installation Guide

iPlanet Portal Server: Mobile Access Pack Administration Guide (this book)

iPlanet Portal Server: Mobile Access Pack Programmer’s Guide

(9)

Typographic Conventions

Preface 9

The release notes, installation guide, administration guide, and programmer’s guide are online in PDF and HTML formats. To find these documents, use this URL:

http://docs.iplanet.com/docs/manuals/wireless.html

The documents are under the heading iPlanet Portal Server: Mobile Access Pack 3.0.

Typographic Conventions

The text in this book uses the following typographic styles:

Typeface or Symbol Meaning Example

AaBbCc123 The names of commands, files, and directories; on-screen computer output

Edit your.login file.

Usels -a to list all files.

AaBbCc123 On-screen computer input Typeexit at the command prompt.

AaBbCc123 Command-line placeholder, to be replaced with a real name or value

To delete a file, typerm filename.

AaBbCc123 Book titles, new words or terms, or words to be emphasized

Read the User’s Guide.

These are called class options.

(10)

Typographic Conventions

(11)

11

Chapter 1

Overview

The iPlanet Portal Server: Mobile Access Pack software leverages the common iPlanet Portal Server components and extends the capabilities of the portal

platform. When you install the Mobile Access Pack software, a number of features are added to Portal Server. These features allow the user to access your portal site using mobile devices.

Mobile Access Pack Software

Understanding the following Mobile Access Pack concepts and how they extend Portal Server’s functions is useful:

• Client Types

• Client Awareness

• Providers and Channels

• The Desktop

• The Administration Console

Client Types

The Mobile Access Pack software supports three types of mobile devices and you can configure your installation to support other mobile devices. The three configured client types are:

• Nokia 7110

• Siemens S35

(12)

Mobile Access Pack Software

• Panasonic P503 i

The Mobile Access Pack uses a client detection module to identify what mobile device a user is using to access the portal site. The module compares the mobile device that is accessing Portal Server with the client types that the portal site supports.

You can configure support for additional client types, such as personal digital assistants and other mobile phones, so that your portal site users can access the site with other mobile devices.

See Chapter 2, “Configuring Mobile Clients,” for more information.

Client Awareness

The Mobile Access Pack software allows your portal site users to use mobile devices to access the same content that they access using an HTML browser.

After the Mobile Access Pack software identifies the mobile device, it delivers portal site content to the mobile device in a format that is compatible with its client type.

Providers and Channels

Mobile Access Pack providers determine what is presented to users in Portal Server channels within the desktop.

Provider content sources can include:

• Content in a file

• Output from an application

• Output from a service

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

The Mobile Access Pack software adds the following providers to those included with the Portal Server software:

Wireless Bookmark Provider WML

Channel name: iwtWirelessBookmarkProviderWML

(13)

Mobile Access Pack Software

Chapter 1 Overview 13

Provider class name:

com.iplanet.portalserver.providers.bookmark.WirelessBookmarkProvider

Wireless Bookmark Provider cHTML

Channel name: iwtWirelessBookmarkProvidercHTML Provider class name:

com.iplanet.portalserver.providers.bookmark.WirelessBookmarkProvider

Wireless URL Scraper Provider

Channel name: the iwtWirelessURLScraperProvider Provider class name:

com.iplanet.portalserver.providers.urlscraper.WirelessURLScraperProvider

Postit Provider

Channel name: iwtPostitProvider Provider class name:

com.iplanet.portalserver.providers.postit.WirelessPostitProvider

User Information Provider

Channel name: iwtUserInfoProvider Provider class name:

com.iplanet.portalserver.providers.userinfo.WirelessUserInfoProvider

In addition, you can use the following Portal Server providers to deliver content to mobile devices:

Address Book Provider

Channel name: iwtAddressBookProvider

Provider class name: com.iplanet.portalserver.providers.ab.AddressBookProvider.

Calendar Provider

Channel name: iwtCalendarProvider

Provider class name: com.iplanet.portalserver.providers.calendar.CalendarProvider

Mail Provider

Channel name: iwtMailProvider

Provider class name: com.iplanet.portalserver.providers.mail.MailProvider

Personal Note Provider

Channel name: iwtWirelessPersonalNoteProvider

(14)

The Desktop

Provider class name:

com.iplanet.portalserver.providers.personalnote.WirelessPersonalNoteProvider

XML Content Provider

Channel name: iwtXMLProvider

Provider class name: com.iplanet.portalserver.providers.xml.XMLProvider

The Desktop

Various sources of content appear in channels on the Portal Server desktop, the page where content is presented to users. On a mobile device, the page where content is presented to users is called the home page.

When you install the Mobile Access Pack software, the Portal Server desktop is changed so that users can use an HTML browser to manage their mobile device home pages themselves. The following features are added to the HTML browser desktop to allow this:

• Mobile Devices tab

The user selects this tab to display the Mobile Devices channel, which allows the user to customize the home page for each mobile device used.

• An Options channel

This allows the user to specify the character set for each mobile device used.

• A Content channel

This displays a list of channels that can be selected for display on the home page of a mobile device.

• A Layout channel

This allows the user to specify the order of channels appearing on the home page of a mobile device.

• An Add/Remove Mobile Devices channel This allows the user to select a mobile device.

The default URL allowing user access to the desktop is:

http://MobileAccessPackServerName:PortalServerPort For example:http://siroe.iplanet.com:8080

(15)

The Administration Console

Chapter 1 Overview 15

The Administration Console

Administrators use the Portal Server’s browser-based Administration Console to complete most ongoing, day-to-day Mobile Access Pack tasks. The features needed to manage mobile access to Portal Server are added to the Administration Console when the Mobile Access Pack software is installed.

The new Administration Console pages allow administrators to:

• Set up client types and define their attributes

• Identify the names and values of client type properties

• Identify which authentication modules are supported for the client type of the user’s mobile devices

• Create new URL scraper channels and assign attributes to them

• Create a new XML provider and new channels and assign attributes to them

• Define the appearance and behavior of other channels on user desktops

• Change the attributes of existing providers and channels The URL for the Administration Console is:

http://MobileAccessPackServerName:PortalServerPort/console For example:http://siroe.iplanet.com:8080/console

Administrators log on to the Administration Console as root.

(16)

The Administration Console

(17)

17

Chapter 2

Configuring Mobile Clients

The iPlanet Portal Server: Mobile Access Pack uses a client detection module to identify what device the user is using to access your portal site. The Mobile Access Pack software uses data objects from the iPlanet Portal Server.

This chapter describes the attributes involved in defining a mobile client and explains the following steps for setting up and changing mobile client definitions:

• Setting Up a Mobile Client Type

• Editing Client Attributes

• Removing Support for a Mobile Client

Understanding Client Attributes

Client attributes in the iPlanet Portal Server profile service provide client-specific information to the Mobile Access Pack server. The following attributes are required:

• Mobile client type. TheclientTypeattribute as an arbitrary string with a list of name-value pairs. Each client type string must be unique.

This attribute serves as an index to the rest of the data for a client.

• User agent for the mobile client. TheuserAgentattribute stores a search string.

The string is compared to the user agent attribute in the HTTP header to determine the mobile client type. The client detection module compares the userAgent string of registered client types to theuserAgent attribute in the HTTP header of the client that is accessing Portal Server. The longest string is matched.

• Content type for the mobile client. ThecontentType attribute contains the HTTP header value and identifies the format of the content.

(18)

Setting Up a Mobile Client Type

If client detection is disabled, the default client type is used.

• File type. ThefileIdentifier attribute indicates what file type is supported by the mobile client.

• Path to mobile client-specific content files. ThefilePath attribute identifies the path to the client-specific data files. These include template files and JSP files.

For client-specific file lookup, the search is based on the mobile client type’s filePath attribute.

• Character set. Thecharset attribute identifies which character sets are supported by the mobile client.

A number of optional attributes are available. They define a mobile client’s behavior and formatting requirements. These include:

counterName, which adds a counter to the URL.

escapeWML, which handles content that contains special characters, such as apostrophes (‘) for clients with a WML contentType.

escapeXML, which handles content that contains special characters, such as apostrophes (‘) for clients with an XML contentType.

ignoreHostHeader, which causes the user’s desktop to ignore the host’s header. This may be required if the client uses HTTP/1.0, because some HTTP/1.0 clients set the host header improperly.

genericHTML, which indicates whether the mobile client accepts HTML.

lineLength, which defines how many character can appear on a single line of a mobile device’s display.

maxSize, which indicates the approximate number of bytes to send to the mobile device.

Setting Up a Mobile Client Type

You must set up a unique client type property for each mobile device that you want to support.

(19)

Setting Up a Mobile Client Type

Chapter 2 Configuring Mobile Clients 19

To set up a new client type, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. Select the Client link to display the Client Profile page.

3. Select Add to display the Add Client Type Data list on the Component Attributes page.

4. From the Add Client Type Data list, select a data object to display it in the Property text box.

5. In the Property text field, provide the appropriate value for the data object.

6. Select Add for each data object.

The newly defined data element appears in the Add Client Type Data list.

7. When your Client Type Data List is complete, select Submit and then select Continue.

8. Select the Manage Domains link from the left frame.

NOTE The Mobile Access Pack software is configured for these client types:

Nokia 7110

Siemens S35

Panasonic P503 i

TIP You must add required data objects. You can add other data elements that are appropriate for the client type in this field also. These data objects are stored as attributes.

Use this format:

data_object=value

For example:

fileIdentifier=wml

The client type value must be unique across all client types. This example uses a mobile device name and model number to create a unique client type:

clientType=nokia_7110

(20)

Editing Client Attributes

9. Select the link for your server’s domain.

10. Select the icon next to the Applications heading to display the Applications list.

11. Select the Desktop link to display the profile for the desktop.

12. Select Show Advanced Options.

13. In the Client Specific Available Providers text box, specify the client type and list the channels that are to be available to the user of this mobile device.

14. Select Add to include the information in the Client Specific Available Providers list.

15. In the Client Specific Selected Providers text box, specify the client type and list the channels that are to be displayed by default the first time the user accesses the portal site using the specified mobile device.

16. Select Add to include the information in the Client Specific Selected Providers list.

17. Select Submit and then Continue.

Editing Client Attributes

You can add, change or delete the attributes that define mobile client behavior.

TIP Use this format:

clientType|channel

For example:

wml|iwtXMLProvider;iwtWirelessBookmarkProvider To specify multiple channels, use a semicolon.

TIP Use this format:

clientType|channel

For example:

wml|iwtUserInfoProvider

To specify multiple channels, use a semicolon.

(21)

Editing Client Attributes

Chapter 2 Configuring Mobile Clients 21

Adding Client Attributes

To add an attribute to an existing client type, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. Select the Client link to display the Client Profile page.

3. From the Configured Client Types list, select the client type you want to add data to.

Your selection is highlighted and appears in the Client Type text field.

4. Select Edit to display client type data on the Component Attributes page.

5. In the Property text field, specify the data property you want to add.

6. Select Add.

The new data objects appears in the Modify Client Type Data list.

7. Select Submit and then select Continue.

Changing Client Attributes

To modify an attribute for a client type, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. Select the Client link to display the Client Profile page.

3. From the Configured Client Types list, select the client type you want to change.

Your selection is highlighted and appears in the Client Type text field.

TIP Use this format:

data_object=value For example:

fileIdentifier=chtml

(22)

Editing Client Attributes

4. Select Edit to display client type data on the Component Attributes page.

5. From the Modify Client Type Data list, select the data object to modify.

6. In the Property text field, modify the data property.

7. Select Edit.

The new data objects appears in the Modify Client Type Data list.

8. Select Submit and then select Continue.

Removing Client Attributes

To delete an attribute from an existing client type, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. Select the Client link to display the Client Profile page.

3. From the Configured Client Types list, select the client type you want to change.

Your selection is highlighted and appears in the Client Type text field.

4. Select Edit to display the Modify Client Type Data list.

5. From the Modify Client Type Data list, select the data object you want to remove.

6. Select Delete.

7. Select Submit and then select Continue.

TIP Use this format:

data_object=value For example:

fileIdentifier=chtml

(23)

Removing Support for a Mobile Client

Chapter 2 Configuring Mobile Clients 23

Removing Support for a Mobile Client

You can delete a mobile device from the list of configured client types. This step is irreversible, and performing it can make it impossible to use that mobile device to access your portal site.

To remove a mobile device from the list of configured clients, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. From the Configured Client Types list, select the client you want to remove.

The selected client is highlighted and appears in the Client Type text field.

3. Select Delete.

4. Select Submit and then select Continue.

5. Select the Manage Domains link from the left frame.

6. Select the link for your server’s domain.

7. Select the icon next to the Applications heading to display the Applications list.

8. Select the Desktop link to display the profile for the desktop.

9. Select Show Advanced Options.

10. From the Client Specific Available Providers list, select the client you want to remove.

11. The selected client is highlighted and appears in the Client Type text field.

12. Select Delete.

13. From the Client Specific Selected Providers list, select the client you want to remove.

14. Select Delete.

15. Select Submit and then select Continue.

(24)

Removing Support for a Mobile Client

(25)

25

Chapter 3

Configuring Authentication

The iPlanet Portal Server: Mobile Access Pack authentication service verifies the user’s identity. A specific authentication module controls the authentication process.

This chapter describes the authentication service and explains the following administrative tasks for setting up and maintaining authentication:

• Enabling Client Detection

• Adding an Authentication Module

• Configuring NoPassword Authentication

• Configuring Authentication Pages

• Configuring Single Sign-on

• Disabling an Authentication Module

Understanding the Authentication Service

The Mobile Access Pack authentication service:

• Invokes a client detection module, which identifies the client type of the user’s mobile device

• Saves the client type information in the Portal Server session

• Determines the appropriate authentication module to invoke for that client type

The authentication service uses the client type information stored in the session to generate the appropriate content for the user’s mobile device.

(26)

Enabling Client Detection

Depending upon the client type, the end user sees a login page with:

• A menu of authentication modules available for the client type of the user’s mobile device

• A specific login module

Enabling Client Detection

The Mobile Access Pack client detection module determines the client type and makes it accessible to other Portal Server software.

To set up client detection, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. Select the Authentication link to display the component profile page.

3. Select Show Advanced Options to display the component attributes.

4. Select the Client Detection Enabled check box.

5. In the Client Detector Class text field, specify the client detector class.

6. Select Submit and then Continue.

Adding an Authentication Module

The Mobile Access Pack software is configured to support LDAP authentication.

You can add other authentication modules, such as RADIUS and UNIX, that Portal Server supports.

TIP By default, this attribute is enabled so that the authentication service can attempt to detect client type values for mobile devices.

NOTE For more information about the client detection module, see the “Client Detection Module Attributes” section in Chapter 8, “Attributes and Schemas,” of the iPlanet Portal Server: Mobile Access Pack Programmer’s Guide.

(27)

Adding an Authentication Module

Chapter 3 Configuring Authentication 27

The authentication service identifies which authentication modules are configured for the client type of the user’s mobile device, and it presents to the user a menu of those authentication modules.

To permit the use of an authentication module with a particular device, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platform Settings link from the left frame to display the Portal Server Platform Settings page.

2. Select the Authentication link to display the component profile page.

3. Select Show Advanced Options.

4. From the Supported Auth Modules for Clients list, select the client you want to add an authentication module to.

The selected entry appears in the Supported Auth Modules for Clients text field.

5. In the Supported Auth Modules for Clients text field, add the authentication module to the desired entry.

6. Select Add to include the modified entry in the Supported Auth Modules for Clients list.

7. Select Delete to remove the original version of the method from the Supported Auth Modules for Clients list.

8. Scroll to the bottom of the page and select Submit and then Continue.

NOTE If you support only one authentication module, the menu is bypassed. The user is sent directly to the authentication page.

TIP To add NoPassword to a WML client, for example, complete these steps:

1. From the Supported AuthModules for Clients list, select the entry that begins withWML|.

2. Add NoPassword to the authentication methods listed.

For example:

WML|Ldap;NoPassword

(28)

Configuring NoPassword Authentication

9. Restart Portal Server by entering the following command in a terminal window:

/opt/SUNWips/bin/ipsserver start

10. Create a template file to display the appropriate menu to the mobile device.

Configuring NoPassword Authentication

If your site specifications require it, you can allow the user to log in without being prompted for userID and password.

To allow users to establish a Portal Server session without supplying a userID and password, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Domains link from the left frame.

2. Select the link for your server’s domain name.

3. Select the Authentication link to display the domain profile.

4. From the authentication menu, select the NoPassword option.

5. Scroll to the bottom of the page and select Submit and then Continue.

NoPassword authentication is most useful in conjunction with non-interactive authentication. Use this URL to make the authentication service non-interactive:

http://server:port/login/NoPassword?domain=/domain&page=1&TOKEN0=us erid

NOTE See Chapter 2, “Authentication Template Files,” in the iPlanet Portal Server:

Mobile Access Pack Programmer’s Guide for information.

NOTE If you bypass authentication, the login page is not displayed. The user is sent directly to the home page.

TIP Replaceserver with the name of your Mobile Access Pack server,port with this server’s port number,domainwith the name of the user’s domain, anduserid with the user’s user ID.

(29)

Configuring Authentication Pages

Chapter 3 Configuring Authentication 29

Configuring Authentication Pages

You can deliver a login page that is specific to each mobile device you have configured for the user. The WirelessLoginWorker class uses properties files and template files to produce login pages.

To set up an authentication page for a client, complete the following steps:

1. From the left frame, select Manage Platform Settings link to display the Portal Server platform settings.

2. Select Authentication to display the authentication profile.

3. Select the Show Advanced Options button to display the attributes for configuring authentication.

4. In the Pluggable Authentication page generator classes for clients text field, specify the pluggable authentication page generator class.

5. In the Pluggable Authentication page generator classes for clients text field, specify the client type and the class.

6. Select Add.

7. Select Submit and Continue.

Configuring Single Sign-on

By default, the Mobile Access Pack software allows you to set up single sign-on for these providers:

• Mail

• Calendar

• Address book

To access backend services, these applications access the Portal Server profile service for required credentials. To accomplish backend authentication, the Portal Server profile service uses information such as passwords and server names, which you provide when you set up single sign-on for these applications.

TIP For information about these files, see Chapter 2, “Authentication Template Files” in the iPlanet Portal Server: Mobile Access Pack Programmer’s Guide.

(30)

Configuring Single Sign-on

The user must provide a user ID and a password for these applications.

Single sign-on is most useful in conjunction with an external LDAP server. The following Mail Provider attributes can be mapped in a Mobile Access Pack installation:

• iwtMailProvider-IMAPServerName

• iwtMailProvider-IMAPPassword

• iwtMailProvider-IMAPUserId

These Address Book Provider attributes can be mapped in a Mobile Access Pack installation:

• iwtAddressBookProvider-IMAPServerName

• iwtAddressBookProvider-IMAPUserId

• iwtAddressBookProvider-IMAPPassword

These Calendar Provider attributes can be mapped in a Mobile Access Pack installation:

• iwtCalendar-calendarServerName

• iwtCalendar-calendarUserName

• iwtCalendar-calendarUserPassword

Setting Up Single Sign-on for Mail

To set up single sign-on for mail, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains from the left frame.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the applications list.

4. Select the Desktop link to display the domain attributes.

5. From the Available Channels list, select iwtMailProvider.

6. Select Edit Channel to display the mail provider attribute values.

TIP See the iPlanet Portal Server 3.0 Release Notes for information about external LDAP server configuration.

(31)

Configuring Single Sign-on

Chapter 3 Configuring Authentication 31

7. Select Show Advanced Options to display additional attributes.

8. In the Client URL text field, type in the URL of the mail server.

9. Select Add to include the URL in the Client URL list.

10. In the Client Port text field, type in the port number of the mail server.

11. Select Submit and then select Continue.

12. Select the Manage Domains link from the left frame.

13. Select the link for your server’s domain.

14. Under the Profiles heading, select the User link to display the user’s profile.

15. In the IMAP Server text field, type in the name of the user’s IMAP server.

16. In the SMTP Server text field, type in the name of the user’s SMTP server.

17. Select Submit and then Continue.

18. Instruct the user to specify a user name and password for the mail server in the Edit Mail page from the desktop’s Mail channel.

TIP This field is optional. If you do not specify a client URL, Mobile Access Pack creates one from the IMAP Server name and Client Port number that you provide.

To specify the URL, use this format:

genericHTML|server:port

Replaceserverwith the complete URL of your mail server andportwith the port number of your mail server.

For example:

genericHTML|http://siroe.iplanet.com:80 Include all of the parameters in the URL.

TIP This field is optional if you specify a URL in the Client URL text field.

(32)

Configuring Single Sign-on

Setting Up Single Sign-on for the Address Book

To set up single sign-on for the address book, complete the following steps:

1. As root, log into the Administration Console and select Manage Domains from the left frame.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the profile for the desktop with all the attributes.

5. From the Available Channels list, select the iwtAddressBookProvider.

6. Select Edit Channel to display the address book provider attributes.

7. In the IMAP ServerName To Authenticate Against text field, specify the name of the IMAP server that is to be used to authenticate the user.

8. In the Address Book LDAP Server text field, specify the name of the address book’s LDAP server.

9. In the Address Book LDAP Server Port text field, specify the port number of the address book’s LDAP server.

10. In the Client URL text field, type in the URL of the address book server.

11. Select Add to include the URL in the Client URL list.

TIP This field is optional. If you do not specify a client URL, Mobile Access Pack creates one from the IMAP Server Name To Authenticate Against that you specify and from the mail channel’s Client Port attribute.

To specify the URL, use this format:

genericHTML|server:port

Replaceserver with the complete URL of your address book server and port with the port number of your address book server.

For example:

genericHTML|http://siroe.iplanet.com:80 Include all of the parameters in the URL.

(33)

Configuring Single Sign-on

Chapter 3 Configuring Authentication 33

12. In the Address Book Admin User DN field, specify the address book administrator’s name.

This user name is used to bind to the server.

13. In the Address Book Admin User Password text field, specify the address book administrator’s password.

This password is used to bind to the server.

14. Select Add.

15. Select Submit and then select Continue.

16. Instruct the user to specify one of the following:

a. An IMAP user name and password for the address book in the Edit Address Book page from the desktop’s address book channel, if the address book is set up to share the server with the mail server.

b. An address book user name and password for the address book in the Edit Address Book page from the desktop’s address book channel, if the address book is set up as a separate server.

Setting Up Single Sign-on for the Calendar

To set up single sign-on for the calendar:

1. As root, log in to the Administration Console and select Manage Domains from the left frame.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the desktop attributes.

5. From the Available Channels list, select the iwtCalendarProvider.

6. Select the Edit Channel button to display the calendar provider attributes.

7. In the Calendar Server Name text field, specify the name of the calendar server.

8. In the Calendar Server Port text field, specify the port number of the calendar server.

9. Select Show Advanced Options to display additional attributes.

10. Select Submit and then select Continue.

(34)

Disabling an Authentication Module

11. Instruct the user to specify a user name and password for the calendar server in the Edit Calendar page from the desktop’s calendar channel.

Disabling an Authentication Module

You can remove an authentication module for a mobile device by disabling it.

To disable an authentication module, complete the following steps:

1. As root, log in to the Administration Console and select the Manage Platforms link from the left frame.

2. Select the Authentication link to display the component profile page.

3. Select Show Advanced Options to display the component attributes.

4. From the Authentication Modules list, select the client type you want to change.

5. Remove the authentication method from the definition.

6. Select Add to include the revised definition in the Authentication Modules list.

7. From the Authentication Modules list, select the original item.

8. Select Delete to remove it from the Authentication Modules list.

9. Select Submit and then select Continue.

TIP For example, to disable NoPassword authentication in this definition:

nokia_7110|Ldap;NoPassword;Radius Revise the definition by removing NoPassword:

nokia_7110|Ldap;Radius

(35)

35

Chapter 4

Configuring Address Book

The Mobile Access Pack address book provider allows you to set up an address book channel that displays summary address book entries with links that launch the iPlanet Messaging Server’s Messenger Express client, allowing the user to control the address book.

This chapter discusses how to use the Administration Console to configure the address book channel for your mobile device user. It explains the following tasks:

• Enabling Access to Address Book

• Configuring Channel Display

• Configuring Channel Layout

Enabling Access to Address Book

You must set up the address book channel before the user can use the address book channel.

To enable access to the address book, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains from the left frame.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

NOTE If you previously installed and uninstalled the Mobile Access Pack software, address book settings from your previous installation were not removed. Be sure that you review all of your settings when you set up the address book for your mobile device users.

(36)

Enabling Access to Address Book

4. Select the Desktop link to display the profile for the desktop.

5. From the Available Channels list, select iwtAddressBookProvider.

6. Select Edit Channel to display address book provider attributes.

7. In the Client URL text field, specify the base URL of the address book client.

8. Select Add.

9. In the IMAP Server Name To Authenticate Against text field, specify the name of the IMAP server to authenticate against.

10. In the Address Book LDAP Server text field, specify the LDAP server name where the address book is stored.

11. In the Address Book LDAP Server Port text field, specify the port number where the address book LDAP server is running. Its default value is set to 389.

12. In the Address Book Admin User DN field, specify the address book administrator’s name.

This user name is used to bind to the server.

TIP This field is optional. If you do not specify a client URL, Mobile Access Pack creates one from the IMAP Server Name To Authenticate Against that you specify and from the mail channel’s Client Port attribute.

To specify the URL, use this format:

genericHTML|server_name:port

Replaceserver_namewith the complete URL of your address book server andport with the port number of your address book server.

For example:

genericHTML|http://siroe.iplanet.com:80 Include all of the parameters in the URL.

NOTE Authentication of the user against the IMAP server specified here is used to validate the user’s credentials.

(37)

Enabling Access to Address Book

Chapter 4 Configuring Address Book 37

13. In the Address Book Admin User Password text field, specify the address book administrator’s password.

This password is used to bind to the server.

14. In the Directory Searchbase text field, specify the address book search origin.

TIP To obtain the address book admin DN, perform the following steps:

1. As root, log in to the iPlanet Messaging Server 5.1 server machine.

2. Issue a command of the form:

/install_directory/server5/msg-hostname/configutil | grep local.service.pab.ldapbinddn

Replaceinstall_directory with Messaging Server’s installation directory andhostname with the name of Messaging Server.

This returns the address book admin DN.

TIP To obtain the address book password, perform the following steps:

1. As root, log in to the iPlanet Messaging Server 5.1 server machine.

2. Issue a command of the form:

/install_directory/server5/msg-hostname/configutil | grep local.service.pab.ldappasswd

Replaceinstall_directory with Messaging Server’s installation directory andhostname with the name of Messaging Server.

This returns the address book admin password.

TIP To obtain the directory search base, perform the following steps:

1. As root, log in to the iPlanet Messaging Server 5.1 server machine.

2. Issue a command of the form:

/install_directory/server5/msg-hostname/configutil | grep local.ugldapbasedn

Replaceinstall_directory with the Messaging Server installation directory andhostname with the name of Messaging Server.

This returns the directory search base.

(38)

Configuring Channel Display

15. Select Submit and then select Continue.

Configuring Channel Display

You can control the appearance of entries in the address book channel by

specifying number of entries and default sorting criteria, in addition to specifying whether to turn display on or off.

To configure the display of the entries in the address book channel, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the profile for the desktop.

5. From the list of available channels, select iwtAddressBookProvider.

6. Select Edit Channel to display the address book provider attributes.

7. In the Display Entries text field, specify whether to display the entries.

8. In the Number Of Entries text field, specify the number of entries to display in the address book channel.

9. In the Maximum Number Of Entries text field, specify the maximum number of entries that the user can set in the Number of Entries text field.

10. In the Sort Order text field, specify what order to sort the entries.

TIP The values are:

true, to display entries in the channel

false, to prevent display

(39)

Configuring Channel Layout

Chapter 4 Configuring Address Book 39

11. In the Sort On Given Field text field, specify what field to use for sorting address book entries.

12. Select Submit and then select Continue.

Configuring Channel Layout

You can control the layout of entries in the address book channel by specifying name, background color, width and refresh time, in addition to specifying other channel layout attributes.

To configure the layout of the address book channel, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the link to your server’s domain name.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the profile for the desktop.

5. From the list of available channels, select iwtAddressBookProvider.

6. Select Edit Channel to display the address book provider attributes.

7. Select Show Advanced Options to display additional attributes.

TIP The values are:

up, to sort in ascending order

down, to sort in descending order

none, to leave entries unsorted

By default, entries are sorted in ascending order.

TIP The values are:

ln, to sort by last name

fn, to sort by first name

none, to leave entries unsorted By default, entries are sorted by last name.

(40)

Configuring Channel Layout

8. In the Title text field, specify a name for the channel.

The specified address book channel content is displayed with this name.

9. In the Background Color text field, specify a background color for the channel.

10. From the Width list, select the channel width.

11. Select the Detached check box to detach the channel from the desktop, if desired.

12. Select the Minimized check box to minimize the channel in the desktop, if desired.

13. In the Refresh Time text field, specify the frequency for updating or refreshing content in the channel.

14. Select the Framed check box to frame the channel in the desktop, if desired.

15. In the Column text field, specify the number of columns in the channel.

16. In the Row text field, specify the number of rows in the channel.

17. From the Number of AB Lines to Display Via JSP list, select the mobile device that you want to configure.

18. In the Number of AB Lines to Display Via JSP text box, specify the number of lines to display in this mobile device’s address book.

19. Select Submit and then Continue.

TIP The channel can be thin, thick, full top, or full bottom.

TIP Use this format to specify the line count:

clientType|number For example:

pana_p503i|8

(41)

41

Chapter 5

Configuring Bookmarks

The Mobile Access Pack WML and cHTML bookmark providers allow you to deliver a bookmark channel that display links to the Internet or intranet on the user’s mobile device. Links appear in the order they were created.

You can also create multiple channels to support device-dependent bookmark lists.

For example, you can create a channel for the Nokia 7110 device and a channel for the Siemens S35 device, with each displaying a different set of bookmark lists.

This chapter discusses how to use the Administration Console to make a new bookmark channel available and to edit bookmark channels for your mobile device user. It explains the following tasks:

• Creating a New Channel

• Editing Bookmarks for WML Clients

• Editing Bookmarks for cHTML Clients

Creating a New Channel

When you create a new channel — to deliver content to a new client type, for example — you must use the Administration Console to add the channel to the list of channels that are available for delivering content to your mobile user.

(42)

Creating a New Channel

To add a new channel to the Available Channel list, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the profile for the desktop.

5. In the Channel Name text box, specify the name of the new channel.

6. In the Provider Class Name text box, specify the provider name of the new channel.

7. Select Add to include the channel name in the Available Channel list.

8. Select Submit and then select Continue.

NOTE Before you start this task, complete the following steps:

1. Create the XML for the channel content.

2. Set up the properties file.

3. Import the XML file in Portal Server.

See the iPlanet Portal Server: Mobile Access Pack Programmer’s Guide for information.

TIP If your new channel name is iplanetcomBookmarkChannel, for example, enter:

iplanetcombookmarkchannel

TIP The provider class name for all wireless bookmark channels is

com.iplanet.portalserver.providers.bookmark.WirelessBoo kmarkProvider.

(43)

Editing Bookmarks for WML Clients

Chapter 5 Configuring Bookmarks 43

Editing Bookmarks for WML Clients

The Mobile Access Pack software provides a bookmark channel for mobile devices that display content in WML. You can change the attributes of this channel.

To modify the bookmark channel for WML client types, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the domain and expand the Applications list.

3. Select the Desktop link to display the profile for the desktop.

4. From the Available Channels list, select iwtWirelessBookmarkProviderWML.

5. Select Edit Channel to display the bookmark provider attributes.

6. Select Show Advanced Options to display additional attributes.

7. Change the attribute values you want to modify.

8. Select Submit and then select Continue.

Editing Bookmarks for cHTML Clients

The Mobile Access Pack software provides a bookmark channel for mobile devices that display content in cHTML. You can change the attributes of this channel.

To modify the bookmark channel for cHTML client types, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the domain and expand the Applications list.

3. Select the Desktop link to display the profile for the desktop.

4. From the Available Channels list, select iwtWirelessBookmarkProvidercHTML.

5. Select Edit Channel to display the bookmark provider attributes.

6. Select Show Advanced Options to display additional attributes.

7. Change the attribute values you want to modify.

8. Select Submit and then select Continue.

(44)

Editing Bookmarks for cHTML Clients

(45)

45

Chapter 6

Configuring Calendar

The Mobile Access Pack calendar provider allows you to set up a calendar channel that displays summary calendar events with links that launch the allow the user to use the calendar.

This chapter discusses how to use the Administration Console to configure the calendar channel for your mobile device user. It explains the following tasks:

• Configuring Calendar Server

• Enabling Access to Calendar Provider

• Configuring Channel Display

• Configuring Channel Layout

Configuring Calendar Server

Calendar Server verifies the IP address of the host where the browser requests a login session ID. If the IP address differs from the host IP address where the session ID is issued, Calendar Server rejects the session with asession time out message.

You must change the value of the parameter that enables and disables an IP security check to allow the user to access mail using a mobile device. The parameter, which specifies whether to restrict session access to the login IP address, isservice.http.ipsecurity.

NOTE If you previously installed and uninstalled the Mobile Access Pack software, calendar settings from your previous installation were not removed. Be sure that you review all of your settings when you set up the calendar for your mobile device users.

(46)

Enabling Access to Calendar Provider

To make this change, complete the following steps from the command line on the machine running Calendar Server:

1. Change to root using thesu root command.

2. Use thecd command to change to the

/install_directory/SUNWics5/cal/bin/config directory.

3. Edit theics.conffile to change the value ofservice.http.ipsecurityto no (for example:service.http.ipsecurity=no).

4. Save the file.

5. Stop Calendar Server using this command:

/install_directory/SUNWics5/cal/bin/stop-cal

6. Start Calendar Server using this command:

/install_directory/SUNWics5/cal/bin/start-cal

Enabling Access to Calendar Provider

You must set up the calendar provider before the user can use the calendar channel.

To enable access to the calendar provider, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the profile for the desktop.

5. From the Available Channels list, select iwtCalendarProvider.

6. Select Edit Channel to display the calendar provider attributes.

7. In the Calendar Server Name text field, specify the name of the Calendar Server.

TIP Replaceinstall_directory with Calendar Server’s installation directory.

(47)

Configuring Channel Display

Chapter 6 Configuring Calendar 47

8. In the Calendar Server Port text field, specify the Calendar Server’s port number.

9. Select Add.

10. Select Submit and then select Continue.

Configuring Channel Display

You can control the appearance of events in the calendar channel by specifying what time period to display.

To configure the display of the events in the calendar channel, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the link for your server’s domain.

3. Select the icon next to the Applications heading to display the Applications list.

4. Select the Desktop link to display the profile for the desktop.

5. From the Available Channels list, select iwtCalendarProvider.

6. Select Edit Channel to display the calendar provider attributes.

7. Select the Day View check box to display entries for today.

8. Select the Week View check box to display entries for a week.

9. Select Submit and then select Continue.

Configuring Channel Layout

You can control the layout of the calendar channel by specifying name,

background color, width and refresh time, in addition to specifying other channel layout attributes.

To configure the layout of the calendar channel, complete the following steps:

1. As root, log in to the Administration Console and select Manage Domains.

2. Select the domain and expand the Applications list.

3. Select the Desktop link to display the profile for the desktop.

Références

Documents relatifs

The server MUST send this extension in the ServerHello if it wishes to issue a new ticket to the client using the NewSessionTicket handshake message.. The server MUST NOT

When multiple ENABLE commands are issued, each corresponding ENABLED response SHOULD only contain extensions enabled by the corresponding ENABLE command.. There are no

During the second phase of negotiation, client and TTLS server use the secure TLS record layer channel established by the TLS handshake as a tunnel to exchange

The Registration Request message is sent by the Proxy Mobility Agent to the Home Agent in order to set up a mobility binding entry for a mobile device3. The message

The client is discouraged from combining multiple independent locking ranges that happen to be adjacent into a single request since the server may not support sub-range

The extensions are designed to be backwards compatible, meaning that the handshake protocol supplemental data messages will only contain authorization information of a particular

In most scenarios, at least one of these credentials will be issued to the public key of the transmitter of the credentials, i.e., said public key will appear in

In order to supply options for the DHCP server to send to the client, the relay agent sends an RSOO in the Relay-Forward message...