Chapter 8 Portal Server Mobile Access Deployment

This chapter describes how to include Portal Server Mobile Access in your Portal Server Deployment.

Portal Server Mobile Access Features

Portal Server Mobile Access software allows users to access your portal service over wireless communications networks. Users access the portal using web browsers on wireless devices such as mobile phones and personal digital assistants. Users who access the portal with Mobile Access can access a variety of portal resources including content, applications, and services.

Mobile Access software provides the following features:

• Delivers existing portal content to wireless mobile devices such as mobile phones, personal digital assistants, and smart phones.

• Supports mobile devices connected to a cellular network or to a wireless network through a LAN or a WAN using HTTP or HTTPS.

• Delivers content and applications through the Portal Server Secure Remote Access server Gateway.

• Provides dynamic personalization and customization for mobile devices.

• Supports customizing the look and feel of the user interface by modifying Portal Server provider templates and provider JSP templates as well as the Mobile Access software application JSP specifications

• Provides Java Server Pages (JSP^TM) software templates for the Nokia 6310i phone.

• Supports writing custom authentication modules and custom content providers

• Incorporates Java Specification Request (JSR) 188 Composite Capability/Preference Profiles Processing (CC/PP) implementation. This facilitates development of device-independent web applications.

• Supports the Wireless Application Protocol (WAP) 2.0 specification for User Agent Profile (UAProf), and extensible hypertext markup language (XHTML).

Introduction to Portal Server Mobile Access Deployment

Mobile Access software is installed when Portal Server software is installed. Like Portal Server, Mobile Access software uses the Sun Java System Access Manager administration console to manage mobile services and users, policy, and access control. Mobile Access administration can be delegated to other users or line-of-business administrators. the various components needed for

People working on a deployment will interact with Mobile Access software to administer, develop, and use a portal site. At times, these distinctions might overlap. For example, a developer might use both the Mobile Access product APIs and the Access Manager administration console to customize and configure availability, content, and layout of a portal site and its providers. Who is involved in each step of the process will vary.

Developing Your Mobile Access Requirements

This section describes how to analyze your organization's needs and develop business and technical requirements for your Mobile Access deployment.

Developing Your Business Requirements

The business goals of providing mobile access affect deployment decisions. If you do not understand your objectives, you can easily make erroneous assumptions that could affect the success of your deployment.

Identify your business objectives by answering the following questions:

• What are the business goals of providing mobile access to your portal? For example, do you want to enhance customer service? Increase employee productivity? Reduce the cost of doing business?

• What are the business goals of providing voice access to your portal?

• Who is your target audience?

• What services or functions will the mobile portal deliver to users?

• How will your target audience benefit from mobile access?

• What are the key priorities for providing mobile access?

• Will you deploy all of your mobile services at one time, or in a phased deployment?

Developing Your Technical Requirements

The reasons you are offering mobile access to your portal have a direct affect on planning your deployment. You must define target population, performance standards, and other factors related to your goals.

Identify your technical objectives by answering the following questions:

• What are the goals of providing mobile access? For example, do you want to deliver a service? Do you want to provide information?

• What applications will the mobile portal deliver? What is your target population?

• What performance standard is necessary? Does it differ from your portal performance?

• What transaction volume do you expect? What transaction volume do you expect during peak use?

• What response time is acceptable during peak use?

• What level of concurrency, the number of users who can be connected at any given time, is necessary?

• Will your mobile portal be deployed in one phase, or many phases? Describe each phase and what will change from phase to phase.

Analyzing User Behavior and Use Patterns

Study the people who will use your mobile portal. Consider factors such as when they will access the portal using a mobile device and how they have used predecessor access methods. If your organization's experience cannot provide these patterns, you can study the experience of other organizations and estimate them.

Analyze your user behavior and use patterns by answering the following questions:

• Is mobile portal use likely to increase over time? Or stay stable?

• How fast will your mobile user base grow?

• How have your users used applications that the mobile portal will deliver to them?

• What mobile portal channels do you expect users to use regularly?

• What expectations about your mobile portal content do your users have? How have they used predecessor Web-based information or other resources that your mobile portal will offer?

Developing Performance and Capacity Requirements

The performance that your portal must deliver directly affects your deployment requirements. Scalability, capacity, and high availability are some of the standards you need to consider.

Develop your performance and capacity requirements by answering the following questions:

• What performance requirements exist?

• What high availability requirements exist?

• What response times are acceptable? How do the response times of your stand-alone systems compare with response time requirements of your portal?

• If you size your portal infrastructure for good response times during regular hours, can you tolerate a possible degradation in performance during peak load times?

• How many concurrent sessions, or connected users, are likely during peak use? (Count only users who are active. Do not include users who are, for example, away on vacation, on leave, or sleeping.)

• What is the above-normal peak time? How does this information affect your peak concurrent user estimate?

• What sort of user activity occurs during peak periods? Logins or reloads?

• How long do you expect the typical user to be connected, or have a valid portal session open? What use statistics do you have for existing applications? Do you have Web traffic analysis figures for an existing portal?

Developing Front-end System Requirements

Analyze the front-end systems that will be used for access to your mobile portal. This enables you to identify how your users will connect to your portal and what kinds of browsers they will use. These factors will affect your deployment decisions.

Develop your front-end system requirements by answering the following questions:

• How will mobile users access your portal?

• How will mobile users access your portal?

• What types of devices will they use?

• What browser features do your users have? Do they have Java applications? Is JavaScript technology enabled? Is cookie support enabled? Are tables supported?

Analyzing Your Need for Future Growth

In addition to determining what capacity you need today, assess what capacity you'll need in the future, within a time frame that you can plan for. Growth expectations and changes in how your portal is used are factors you need to accommodate growth.

Develop your growth requirements by answering the following questions:

• What is the projected growth for the portal? How fast will the growth occur?

• Where is your mobile portal available? What are the trends for use of mobile devices in those countries?

• How will your business objectives change in the next two or three years?

• What plans do you have for future content?

Analyzing Your Need for Authentication and Secure Access

Determine whether security is needed for your mobile portal. If so, you must assess what kind is appropriate.

Develop your growth requirements by answering the following questions:

• What are your general security policies?

• Do you use the Identity Server software to provide single sign-on to your portal? Will your single sign-on requirements change for mobile access? Should your mobile portal users be able to sign on automatically?

• Is a gateway needed?

• Is SSL required for authentication to the portal?

• Is SSL required for any other part of the portal?

Analyzing Your Channel Requirements

Your design for mobile access to your portal service is influenced by the content channels that your portal site offers. How your users use mobile devices to use channels and their content are among the factors to define.

Develop your content channel requirements by answering the following questions:

• How many channels are you likely to provide to mobile device users?

• What portal channels do you expect mobile users to use regularly?

• Will you provide new content or re-work existing content

Analyzing Your Quality of Service Needs

To identify and establish quality goals for your Mobile Access software deployment, consider what measures will allow you to deliver the quality that your mobile portal must offer.

Develop your quality of service requirements by answering the following questions:

• Do you want to provide all existing Portal Server software users mobile access to your portal within a certain time frame, such as 12 months?

• Have you completed plans for a test environment that replicates your production environment?

• How much time will you need for various test phases, including unit testing, functional testing, end-to-end testing, user acceptance testing, and the like?

• Will you test each mobile device you plan to support?

• Should you maintain existing mobile portal services during your mobile portal deployment?

• What performance and reliability expectations do you have?

• Have you established baseline measurements that you can track as you move to a production environment?

• What user interface standards do you have for various mobile devices?

• Can you maintain a completely functioning network infrastructure throughout the transition period from your test environment to your production environment?

• Can you eliminate single points of failure for the portal system by developing an architecture that includes redundant portal servers, gateways, and directory replicas and masters at various service layers?

• What change control procedures will you follow?

Developing a Mobile Access Architecture

This section describes specific technology features of Mobile Access to help you determine which technologies are most important for your organization. Review these features while keeping in mind your organizations short-, mid-, and long-term plans.

To assist you in developing a deployment plan in a timely and cost effective manner, this topic describes the following features:

Using Composite Capability and Preference Profiles

Mobile Access software implements the composite capability and preference profiles (CC/PP) specification, also known as JSR 188. Portal Server software can use this implementation to adapt content and pass on delivery context information to channels that adapt their behavior accordingly. This specification provides developers with a standard set of APIs for processing delivery context information compatible with the majority of Web access mechanisms that deliver context negotiations.

Writing device-independent code that can deliver content to a multitude of Web access mechanisms helps reduce costs and avoids proliferating proprietary and potentially incompatible implementations.

Integrating Mobile Access and Portal Secure Remote Access Server

The Mobile Access product integrates with Portal Server Secure Remote Access server, which provides proxy, URL rewriting, and VPN-on-demand capabilities. The Secure Remote Access server gateway sits in the DMZ in front of the corporate firewall and provides security from outside connections to resources available behind the firewall. The gateway provides proxy server and URL rewriting capabilities for content and applications. It also supports URL obfuscation.

Installing and Configuring Portal Mobile Access

Platform-specific directory structures and property files are installed for the Mobile Access software. They are used to store configuration and operational data.

Directory Structure of Mobile Access Configuration Files

The platform-specific directory structures that are installed for Mobile Access software are for application JSP template files and voice files. They include the following:

Directory	Contents
/portal-server-installation-root/SUNportal/web-src/jsp/default	Application JSP templates
/identity-server-installation-root/SUNWam/web-src/services/config/auth/	Authentication JSP specifications in WML and cHTML
Mobile Access software also uses the following Portal Server software directories:
/portal-server-installation-root/opt/SUNportal	Default installation directory
/portal-server-installation-root/opt/SUNportal	Default installation directory for configuration information
/portal-server-installation-root/SUNportal/sdk	Default installation directory for SDK
/usr/tmp	Temporary files
/var/opt/SUNWportal/logs	Log files
/portal-server-installation-root/SUNportal/samples/desktop/dp-org.xml	Container and channel display profile
/portal-server-installation-root/SUNportal/samples/desktop/dp-providers.xml	Provider display profile
/var/opt/SUNportal/portals/portalid/desktop/default/channel_or_provider_name.template	HTML template files
/var/opt/SUNWportal/portals/portalid/desktop/default/JSPchannelname	JSP template files
/portal-server-installation-root/SUNportal/bin/	Command-line utilities
/etc/opt/SUNWportal/dtd/psdp.dtd	Display profile DTD
/portal-server-installation-root/SUNWma/locale	Java properties files

Configuration Files

A Portal Server deployment includes two configuration files with configuration parameters that apply to Mobile Access. These files and their default locations are listed in the following table:

Configuration File	Used For
/etc/opt/SUNWma/config.properties	Installed as a common component, this file has properties that Portal Server software and Access Manager software use.
/etc/opt/SUNportal/MAConfig.properties	Installed as a component of Portal Server, this file has properties specific only to Portal Server.