BEA WebLogic Server User manual

BEA WebLogic Mobility ServerTM
User Guide
Version 3.3
December 2005

Copyright
Copyright © 1995-2005 BEA Systems, Inc. All Rights Reserved.
Restricted Rights Legend
This software is protected by copyright, and may be protected by patent laws. No copying or
other use of this software is permitted unless you have entered into a license agreement with BEA
authorizing such use. This document is protected by copyright and may not be copied
photocopied, reproduced, translated, or reduced to any electronic medium or machine readable
form, in whole or in part, without prior consent, in writing, from BEA Systems, Inc.
Information in this document is subject to change without notice and does not represent a
commitment on the part of BEA Systems. THE DOCUMENTATION IS PROVIDED “AS IS”
WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
FURTHER, BEA SYSTEMS DOES NOT WARRANT, GUARANTEE, OR MAKE ANY
REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE
DOCUMENT IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR
OTHERWISE.
Trademarks and Service Marks
Copyright © 1995-2005 BEA Systems, Inc. All Rights Reserved.BEA, BEA JRockit, BEA
WebLogic Portal, BEA WebLogic Server, BEA WebLogic Workshop, Built on BEA, Jolt,
JoltBeans, SteelThread, Top End, Tuxedo, and WebLogic are registered trademarks of BEA
Systems, Inc. BEA AquaLogic, BEA AquaLogic Data Services Platform, BEA AquaLogic
Enterprise Security, BEA AquaLogic Service Bus, BEA AquaLogic Service Registry, BEA
Builder, BEA Campaign Manager for WebLogic, BEA eLink, BEA Liquid Data for WebLogic,
BEA Manager, BEA MessageQ, BEA WebLogic Commerce Server, BEA WebLogic
Communications Platform, BEA WebLogic Enterprise, BEA WebLogic Enterprise Platform,
BEA WebLogic Enterprise Security, BEA WebLogic Express, BEA WebLogic Integration, BEA
WebLogic Java Adapter for Mainframe, BEA WebLogic JDriver, BEA WebLogic Log Central,
BEA WebLogic Network Gatekeeper, BEA WebLogic Personalization Server, BEA WebLogic
Personal Messaging API, BEA WebLogic Platform, BEA WebLogic Portlets for Groupware
Integration, BEA WebLogic Server Process Edition, BEA WebLogic SIP Server, BEA WebLogic
WorkGroup Edition, Dev2Dev, Liquid Computing, and Think Liquid are trademarks of BEA
Systems, Inc. BEA Mission Critical Support, BEA Mission Critical Support Continuum, and
BEA SOA Self Assessment are service marks of BEA Systems, Inc.
All other names and marks are property of their respective owners.

Contents
Contents
Introduction.......................................................................................................................................1
About this Manual............................................................................................................................................1
Prerequisites ...................................................................................................................................................1
Terminology Used in this Manual....................................................................................................................2
Content Examples...........................................................................................................................................2
Further Reading ..............................................................................................................................................2
Part I Documentation Roadmap.......................................................................................................3
Where Do I Start?............................................................................................................................................3
What Manuals Are Provided? .........................................................................................................................3
Is There a Demonstration Workshop Mobility Project?...................................................................................4
What Authoring Tools Do I Need? ..................................................................................................................4
What Format Do I Use for Marking Up Content?............................................................................................4
How Do I Change the Appearance of Web Content for Mobile Devices? ......................................................5
Where Can I Find More Information on Delivering Images and Other Media to Mobile Devices?.................5
How Do I Tailor Content for Different Devices?..............................................................................................5
How Can I Create Dynamic Content That Accommodates Device Characteristics?......................................5
How Do I Brand or Use Logos on my Device? ...............................................................................................5
How Do I Troubleshoot the Output From WebLogic Mobility Server?............................................................5
How Can I Modify the Basic Start-Up Parameters for WebLogic Mobility Server? ........................................6
How Do I Take Advantage of Access Keys on WML Devices?......................................................................6
How Do I Find Out More About Working with Tables? ...................................................................................6
Part II The Mobility Extension for BEA Workshop.........................................................................7
Summary of the Mobility Extension Features .................................................................................................7
Mobility Menu................................................................................................................................................15
Part III Fundamentals of Mobile Content ......................................................................................16
Overview of the Process...............................................................................................................................16
Introducing the Mobility Tags........................................................................................................................18
The WebLogic Mobility Server JSP Tag Library...........................................................................................21
Optimize Performance with the JSP Tag Library..........................................................................................24
Work with XHTML .........................................................................................................................................27
Organize Content..........................................................................................................................................32
Create Conditional Content...........................................................................................................................43
Part IV Presentation of Mobile Content.........................................................................................53
Organize Content for Handheld Devices ......................................................................................................53
Navigational Menu Styling.............................................................................................................................70
Work with Style Sheets.................................................................................................................................81
BEA WebLogic Mobility Server User Guide - iii

Contents
Manage Navigation .......................................................................................................................................88
Work with Tables...........................................................................................................................................97
Work with Images........................................................................................................................................105
Work with Character Sets ...........................................................................................................................108
Fine-Tune Mobile Content...........................................................................................................................112
iMode Support.............................................................................................................................................116
Part V The Delivery Context API..................................................................................................120
Overview of the CC/PP Delivery Context API.............................................................................................120
Part VI Diagnostics .......................................................................................................................126
Work with Diagnostics.................................................................................................................................126
Use the Diagnostic Console........................................................................................................................127
Use the Diagnostic CLI................................................................................................................................139
Diagnose Problems.....................................................................................................................................144
Monitor Diagnostic Output...........................................................................................................................148
Exception Handling .....................................................................................................................................153
Part VII Glossary ...........................................................................................................................157
Part VIII Appendixes .....................................................................................................................162
Appendix A – Mobility Tag Reference.........................................................................................................162
Appendix B – Mobility Delivery Context API ...............................................................................................191
Appendix C – Deprecated Items.................................................................................................................198
Appendix D – Use the Generic Log Monitor Facility with Log4J.................................................................200
Appendix E – FAQ.......................................................................................................................................203
iv - BEA WebLogic Mobility Server User Guide

Introduction
Introduction
About this Manual
This manual introduces you to the various features of BEA WebLogic Mobility Server™ and
explains how to create a web site that targets all devices.
The manual is divided into eight parts:
Part I – Documentation Roadmap
This section provides an overview of where to look for information as you develop your
mobilized web applications.
Part II – The Mobility Extension for BEA Workshop
This section introduces the WebLogic Mobility Server mobility tags and describes key
fundamentals behind working with mobile content, including organizing content and creating
conditional content.
Part III – Fundamentals of Mobile Content
This section provides an overview of the process used in creating web applications that target a
variety of devices.
Part IV – Presentation of Mobile Content
This section describes key aspects of content presentation, including layouts and structures,
server-side style sheets, navigation, tables and media.
Part V – The Delivery Context API
This section introduces the delivery context API and explains how to use its methods to obtain
device information from the WebLogic Mobility Server database.
Part VI – Diagnostics
This section describes the WebLogic Mobility Server diagnostic tools that enable developers and
administrators to monitor the HTTP request / response cycle within WebLogic Mobility Server
and to retrieve diagnostic information generated in the process.
Part VII – Glossary
This section provides an explanation of terms and acronyms used in this document.
Part VIII – Appendixes
This section provides a reference guide to the WebLogic Mobility Server mobility tags, a delivery
context API reference guide, a list of deprecated items, and answers to frequently asked
questions.
Prerequisites
This manual assumes that you are familiar with web page design using HTML and XHTML. It
also assumes that you are familiar with basic JSP (or related scripted web page technologies) and
the use of basic Java within such pages to generate dynamic content.
The manual does not teach specific web or site design skills, but will show you how to use
WebLogic Mobility Server to bring mobility into your existing web design workflow.
BEA WebLogic Mobility Server User Guide - 1

Introduction
Terminology Used in this Manual
There are a number of terms used throughout this manual that have a specific meaning within
WebLogic Mobility Server:
•The term content describes the elements that define your service: XHTML mark-up (such as
tables and formatting), JavaScript, JSP code, text, images and so forth.
•Static content refers to web pages that are sent to the requesting browser without changes
made by scripting or code. It is usually information that does not need to change on a regular
basis.
•Dynamic content describes web pages that are generated when accessed by an end-user,
possibly pulling in external content and/or pages customized for the requesting user.
•The term request page refers to the file containing the content that will be transformed.
•The term web application refers to a web-enabled application that consists of static and
dynamic resources, including multiple servlets and JSPs.
•The term device should be taken to refer either to a specific device, such as an iPAQ, or a
device category, such as menu-driven devices or PDAs.
Content Examples
This manual describes the two mobility mark-up tag sets. The code examples in this manual use
either the mmXHTML tags or their equivalent JSP taglib. In most cases the examples can be done
using either set.
Further Reading
In addition to the Getting Started Tutorials, the following documentation set is provided with
WebLogic Mobility Server:
•BEA WebLogic Mobility Server Installation Guide
•Device Repository Guide
•BEA WebLogic Mobility Server Administration Guide
•BEA Sample Workshop Mobility Project Guide
•BEA Sample Mobility Portal Guide
•BEA Mobilize Your Portal Guide
2 - BEA WebLogic Mobility Server User Guide

Part I Documentation Roadmap
Part I Documentation Roadmap
This section provides an overview of where to look for related information as you develop your
mobilized web application.
Where Do I Start?
After installation, we recommend you begin with the Getting Started Tutorials. The tutorial set is
a series of short lessons that introduce the WebLogic Mobility Server mobility tags and the
delivery context API. The lessons are made up of short, working examples that take you through
the process of marking up content in order to create web pages that can be viewed on many
different client devices. You also learn how to use the delivery context API, which lets
developers obtain device attribute information from the Device Repository. This is helpful when
creating dynamic content tailored to the specific requesting device.
What Manuals Are Provided?
All the WebLogic Mobility Server manuals are supplied in Adobe Acrobat format. The following
table describes the manuals available and their purpose:
WebLogic Mobility Server Documentation Set
Document Description
BEA WebLogic Mobility
Server Installation
Guide
Provides instructions for installing and configuring WebLogic Mobility
Server.
Device Repository
Guide This guide explains how to install the Device Repository used by
WebLogic Mobility Server, describes how to update the
mis.properties file to reflect the Device Repository connection details
and outlines how to set up and manage the device profiles stored in
the Repository.
BEA WebLogic Mobility
Server Administration
Guide
Provides information on how to configure WebLogic Mobility Server
after installation.
BEA WebLogic Mobility
Server User Guide
(this guide)
Provides supporting and advanced information on WebLogic Mobility
Server, including:
•The general principles behind organization and transformation of
content.
•Information on using the WebLogic Mobility Server diagnostics
to monitor internal behavior during transactions in development
and production environments.
•An appendix section on the WebLogic Mobility Server mobility
tags and the delivery context API.
BEA Sample Workshop
Mobility Project Guide Provides a step-by-step exercise in mobilizing a sample workshop
application
BEA WebLogic Mobility Server User Guide - 3

Part I Documentation Roadmap
BEA Sample Mobility
Portal Guide Explains the features of the Mobilized BEA Portal Framework using a
sample Mobility Portal
BEA Mobilize Your
Portal Guide Explains how to mobilize a portal and then apply your own “Look &
Feel” to it as required.
Note: In addition, the Getting Started Tutorials provide a series of short lessons designed to teach
the basics of using the WebLogic Mobility Server mobility tags to create multi-channel content
and applications.
Is There a Demonstration Workshop Mobility Project?
Yes, if you have installed BEA WebLogic Mobility Server available from BEA Systems. The
“restaurantWeb” sample Workshop project demonstrates many of the WebLogic Mobility Server
features such as:
•Organizing and tailoring content for different devices
•Previewing content on different devices
•Ensuring the media format being delivered is appropriate to the device making the request
The “restaurantWeb” sample Workshop project has been installed in the <bea installation
directory>\weblogic81\mobility\samples\BEAWorkshop directory. Please see the BEA
WebLogic Mobility Server Installation Guide for instructions on importing the “restaurantWeb”
sample Workshop project into a Workshop application. The BEA Sample Workshop Mobility
Project Guide provides a step by step explanation of how to use the Mobility Extension for BEA
WebLogic Workshop to mobilize “restaurantWeb.” In the same directory as “restaurantWeb” is
an already mobilized version of the sample project called “restaurantWeb_after.”
What Authoring Tools Do I Need?
WebLogic Mobility Server includes the Mobility Extension for BEA WebLogic Workshop. With
the Mobility Extension, the BEA WebLogic Workshop Integrated Development Environment can
be used for creating multi-channel applications and extending existing applications to support
wireless devices. Please see the section “The Mobility Extension for BEA Workshop” for a
description of the functionality provided by the Mobility Extension. The BEA Sample Workshop
Mobility Project Guide provides a hands-on tutorial that uses the Mobility Extension features.
What Format Do I Use for Marking Up Content?
The mobility tags are a set of XML compliant tags that form the essential building blocks for the
development of mobilized web content.
mmXHTML (multi-mode XHTML) is a compact set of tags that begin with the characters mm-
(for example <mm-group>…</mm-group>). The WebLogic Mobility Server JSP tag library is an
equivalent set of tags for developers working with JSP pages. The taglib replicates the
functionality of the mmXHTML tag set. These tags begin with the characters mm: (for example
<mm:group>…</mm:group>). The Mobility Extension for BEA WebLogic Workshop integrates
the JSP tab library into WebLogic Workshop, providing a Mobility Palette and inserts wizards for
drag and drop inclusion of the mobility tags into content.
4 - BEA WebLogic Mobility Server User Guide

Part I Documentation Roadmap
How Do I Change the Appearance of Web Content for Mobile
Devices?
WebLogic Mobility Server uses the concepts of layouts and structures to control the organization
and transformation of content requested by mobile devices. The <mm-structure>and <mm-
layout> tags are responsible for restructuring a single source of web content for presentation on a
variety of handheld devices that require special consideration because of screen size and memory
limitations. The <mm-layout> tag allows the user to specify a file that contains alternate,
simplified templates for PDA and menu-driven devices. The <mm-structure> tag is used to
redisplay the content for smaller devices. It gives the author the power to control the navigation
flow between pages, which is often needed to present content clearly on these smaller devices.
Where Can I Find More Information on Delivering Images and
Other Media to Mobile Devices?
WebLogic Mobility Server provides the <mm-media-group> and <mm-img> tags to ensure the
appropriate image, in terms of size, quality and suitability, is delivered to a device. There is also
an <mm-logo> tag that is used to flash an image on WML devices for a short time before
presenting the rest of the content.
How Do I Tailor Content for Different Devices?
In addition to allowing the creation of specific layouts for targeted device groups, WebLogic
Mobility Server provides the <mm-include> and <mm-exclude> tags to conditionally include and
exclude parts of the content depending on either the type of device making the request or specific
device profile attributes.
How Can I Create Dynamic Content That Accommodates Device
Characteristics?
You can use JSP to output WebLogic Mobility Server mark-up that accommodates different
devices. For example, you might want to change the number of columns in a table depending on
the width of the device’s screen. To do this, you would need specific information from the Device
Repository. By using the delivery context API, you could retrieve the required device attributes,
which could then be placed in the JSP to dynamically change what is delivered to the device.
How Do I Brand or Use Logos on my Device?
For targeting WML devices, you can take advantage of a feature that displays a logo for a short
period of time before rendering the rest of the content. Use the <mm-logo> tag for this purpose.
How Do I Troubleshoot the Output From WebLogic Mobility
Server?
WebLogic Mobility Server provides diagnostic tools to monitor a range of system messages,
which allows you to troubleshoot different phases of the transformation process. The diagnostic
messages show the content before and after it is transformed, as well as the processing that occurs
in-between. You can select a variety of diagnostic “topics” in order to target specific areas to
monitor.
BEA WebLogic Mobility Server User Guide - 5

Part I Documentation Roadmap
How Can I Modify the Basic Start-Up Parameters for WebLogic
Mobility Server?
Configuration settings for WebLogic Mobility Server are stored in the /WEB-
INF/classes/mis.properties file. This file contains settings that enable WebLogic Mobility Server
to communicate with the Device Repository as well as updating log files and other transaction-
related activity. The BEA WebLogic Mobility Server Administration Guide describes the settings
in this file.
How Do I Take Advantage of Access Keys on WML Devices?
Access keys provide a shortcut for navigating content delivered to menu-driven devices that
support this feature.
How Do I Find Out More About Working with Tables?
Mobile devices differ in their ability to handle tables. WebLogic Mobility Server supplies the
mobility tag <mm-table-model> for managing the transformation of tables. See the section “Work
with Tables” for additional information.
6 - BEA WebLogic Mobility Server User Guide

Part II The Mobility Extension for BEA Workshop
Part II The Mobility Extension for BEA Workshop
Note: This section is only applicable if you have installed WebLogic Mobility Server available
from BEA Systems.
After installing WebLogic Mobility Server including the Mobility Extension for BEA WebLogic
Workshop (see the BEA WebLogic Mobility Server Installation Guide), the BEA WebLogic
Workshop Integrated Development Environment can be used for creating multi-channel
applications and extending existing applications to wireless.
Summary of the Mobility Extension Features
This section provides an overview of the Mobility Extension features, including:
•Enable Multi-Channel for new or existing projects
•Mobility Palette, for easy Access to Mobility Tags
•Mobility Toolbar, including:
•Design Preview icons for the different device classes
•Emulator Launch icons for the different device classes
•Launch Mobility Tools icon
•IDE Properties additions, including:
•Mobility Pane, for setup and configuration
•Emulators Pane, for configuring Device Emulators
•Mobility Menu under Tools, including:
•Launch Emulator options
•Launch Mobility tools
These features are described in more detail in the “Enable Multi-Channel” section.
Note: The large xml-format device repository file may cause problems when a project is opened
in WebLogic Workshop. Please use the compressed madr-format repository to avoid these
problems. The Enable Multi-Channel function automatically adds the ".madr" version of the file
to your project.
BEA WebLogic Mobility Server User Guide - 7

Part II The Mobility Extension for BEA Workshop
Enable Multi-Channel
Any application project can be configured for multi-channel delivery by selecting the “Enable
multi-channel” option for the highlighted project. Selecting this option configures the application
project to deploy and use WebLogic Mobility Server.
Enable multi-channel
8 - BEA WebLogic Mobility Server User Guide

Part II The Mobility Extension for BEA Workshop
Mobility Palette
Using a “drag & drop” technique, mobility meta-data can be applied to any NetUI-defined
interface to enable delivery to mobile devices. This includes support for wizard-based generation
of layouts for different device categories, click-to-dial for embedding telephony commands in
applications, multi-device image handling, and device-category styling.
The Mobility Palette
BEA WebLogic Mobility Server User Guide - 9

Part II The Mobility Extension for BEA Workshop
Mobility Toolbar
This is a toolbar extension that enables launching of device emulators for smart phones and PDAs
in addition to the Workshop test browser. The Mobility Toolbar also provides a diagnostics
application that enables the simulation of advanced mobile requirements for detailed testing of
applications.
The Mobility Toolbar features
The Mobility Toolbar additionally provides the capability to manage target devices from within
Workshop, enabling addition/removal of devices in the Device Repository and device profile
configuration for optimization of NetUI for different device types.
View Content with Emulators
The Mobility Extension installation adds a toolbar to Workshop that makes it easy to view and
troubleshoot mobilized content. Once your emulators have been configured as described in the
installation instructions, you will have an extra toolbar in Workshop, the Mobility Toolbar.
The Mobility Toolbar
The first icon simplifies the management of groups of content that have been created on the page
that is open in the Edit Pane.
Manage Groups
The next four icons allow you to see the mark-up for a particular device. Content groups that have
been excluded for a particular device will not appear in the window when that device’s button is
pressed. The groups that are to be delivered to the device will be expanded so that you can see
approximately how they would look.
10 - BEA WebLogic Mobility Server User Guide

Part II The Mobility Extension for BEA Workshop
These four icons are as follows:
Preview WAP Content
Preview PDA Content
Preview Full Browser (PC) Content
View All Contents and Mobility Mark-up
The next four icons let you launch the particular device emulator to see the results of the mobility
markup, as it would appear in the actual device.
They are, in order:
Launch Configured WAP 1.x Emulator
Launch Configured WAP 2.x Emulator
Launch Configured PDA Emulator
Launch Other Configured Emulators / Browsers
The sample project, when viewed in a menu-driven (for example smart phones) or a PDA device,
demonstrates the types of issues that can arise when sending PC web content to handheld devices.
As the code is mobilized, you will be able to see how WebLogic Mobility Server can manipulate
the content to make it look good on all types of devices.
Note: Openwave 6.2.2 will sometimes pause or freeze when launched from Workshop. In order
to stop this behavior, follow these instructions:
1. Edit the Openwave startup batch file (for example C:\Program Files\Openwave\SDK
6.2.2\program\OSDK62http.bat) or create a copy and edit as follows:
2. Change: cd http to cd /d %~dp0\http.
3. Change: start osdk62http.exe -pho OPWV-SDK-62.pho to
start osdk62http.exe "%*" -pho OPWV-SDK-62.pho.
4. In Workshop, choose Tools →IDE Properties →Emulators, configure to start the edited
.bat file instead of the .exe (the bat file is one directory above .exe in the tree).
BEA WebLogic Mobility Server User Guide - 11

Part II The Mobility Extension for BEA Workshop
The final icon on the toolbar gives access to additional WebLogic Mobility Server tools:
•Admin Console for managing devices and their attributes
•Diagnostics Console for diagnostic output and troubleshooting
•Device Repository Manager for managing the Device Repository
WebLogic Mobility Server Tools
Clicking on this icon will open the Mobility Tools Launcher dialog box for these tools (see the
following graphic). The tools can also be launched directly from the Mobility Menu.
Mobility Tools Launcher
12 - BEA WebLogic Mobility Server User Guide

Part II The Mobility Extension for BEA Workshop
IDE Properties Additions
Two additional panes have been added to the IDE Properties dialog:
•Mobility pane
•Emulators pane
Mobility Pane
The “Mobility” pane allows the user to set the WebLogic Mobility Server Install Location
property.
Additions to IDE Properties Dialog
The “Device Classes” section provides a drop down list of configured device classes when using
the Mobility Tags. Developers can specify frequently used “where” expressions for inclusion in
the drop down list.
To add a new item to the drop down list, insert the frequently used expression in the “Expression”
column and an easily identifiable “Display Name” to be associated with it. Subsequent usage of
the Mobility Tags will allow the user to select this “Display Name” resulting in the automatic
insertion of the defined “Expression”.
Emulators Pane
The “Emulators” pane enables configuration of different emulators for testing the application
appearance and flow on a range of devices.
BEA WebLogic Mobility Server User Guide - 13

Part II The Mobility Extension for BEA Workshop
Emulators Pane
For more information on configuring these emulators, see the section “Configuring the Device
Emulators” in the BEA WebLogic Mobility Server Installation Guide.
14 - BEA WebLogic Mobility Server User Guide

Part II The Mobility Extension for BEA Workshop
Mobility Menu
The Mobility Menu contains links to the following:
•Launch WAP 1.x emulator
•Launch WAP 2.x emulator
•Launch PDA emulator
•Launch other emulators/browsers
•Launch Mobility Tools
Mobility Menu
BEA WebLogic Mobility Server User Guide - 15

Part III Fundamentals of Mobile Content
Part III Fundamentals of Mobile Content
Overview of the Process
This section provides an overview of the process used in creating web applications that target a
variety of devices.
Three Steps to Creating and Delivering your Service
There are three basic steps in preparing content so that it can be displayed on multiple devices:
•Creating your content in XHTML format.
•Organizing the page content into logical divisions.
•Deciding how you want your content to be presented on different devices.
Create your content in XHTML format
All documents that are processed by WebLogic Mobility Server must follow XHTML 1.0
standards. XHTML has stricter mark-up standards than HTML. All tags, for example, must
terminate correctly, either with a closing tag, or, for empty tags, by putting a closing slash before
the final angle bracket.
All documents that are processed by WebLogic Mobility Server must follow XHTML 1.0
standards. XHTML has stricter mark-up standards than HTML. All tags, for example, must
terminate correctly, either with a closing tag, or, for empty tags, by putting a closing slash before
the final angle bracket.
If you are converting legacy content containing HTML mark-up, there are a number of tools
available to automate the process of converting HTML to XHTML. The Developer Toolkit on
CD2 includes HTML Tidy, a popular tool for converting HTML files to XHMTL. Dreamweaver
MX also provides built-in XHTML clean-up and conversion utilities.
You can use any authoring environment to develop your XHTML content. This content can be
either static, where the page does not change, or dynamic, where you use JSP to dynamically
generate content.
Organize the page content into logical divisions
Since the amount of content you can display depends on screen size, you will want to divide your
content into logical units called groups. This will give you more flexibility in deciding what gets
displayed on specific devices. You can take advantage of the natural divisions in your document
(such as tables and forms) or you can explicitly create your own groups. For example, you might
arrange a news page into national, regional and local news groups.
16 - BEA WebLogic Mobility Server User Guide