BEA WebLogic User Manual
  1. Manuals
  2. Brands
  3. BEA Manuals
  4. Server
  5. WebLogic Server
  6. User manual
BEA WebLogic User Manual

BEA WebLogic User Manual

Mobility server
Hide thumbs Also See for WebLogic:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Manual
WebLogic Mobility Server
TM
BEA
User Guide
Version 3.3
December 2005

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the WebLogic and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for BEA WebLogic

Summary of Contents for BEA WebLogic

  • Page 1 WebLogic Mobility Server User Guide Version 3.3 December 2005...

  • Page 2: Trademarks And Service Marks

    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.

  • Page 3: Table Of Contents

    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? ...................
  • Page 4 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...

  • Page 5: Introduction

    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.

  • Page 6: Terminology Used In This Manual

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

  • Page 7: Part I Documentation Roadmap

    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.

  • Page 8: Is There A Demonstration Workshop Mobility Project

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

  • Page 9: How Do I Change The Appearance Of Web Content For Mobile Devices

    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 > and <mm-structure...

  • Page 10: How Can I Modify The Basic Start-Up Parameters For Weblogic Mobility Server

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

  • Page 11: Part Ii The Mobility Extension For Bea Workshop

    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...
  • Page 12 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...
  • Page 13 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...
  • Page 14 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...
  • Page 15 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.
  • Page 16 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 •...
  • Page 17 • 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.
  • Page 18 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...

  • Page 19: 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...

  • Page 20: Part Iii Fundamentals Of Mobile Content

    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.
  • Page 21 WebLogic Mobility Server how to present the content for these smaller devices. For example, one layout for a PDA device might extract and display a company logo, an address group, a phone group and a text group describing the company. Another layout, for a smaller screen, might just extract and display the company logo group and a phone number You can control which groups get sent to the different device types.

  • Page 22: Introducing The Mobility Tags

    A JSP tag library version of the mmXHTML tags is also available for use with JSP files. These tags are almost identical in syntax and function. They are explained further in The WebLogic Mobility Server JSP Tag Library in this manual.
  • Page 23 Used to contain mm-img tags that refer to images of different sizes and formats. WebLogic Mobility Server will select the best image for the requesting device. mm-nl Used with <mm-li> to create easily styled navigation menus for handheld devices.
  • Page 24 <mm-group-ref> <mm-structure> DTD Usage A reference to the DTD must be included in any mmXHTML document processed by WebLogic Mobility Server. When an author is creating an mmXHTML document, the document will require an XML declaration: <?xml version="1.0"?> and a reference to the mmXHTML DTD within which the schema of the mobility tags are defined: <!DOCTYPE html PUBLIC "-//MOBILEAWARE//DTD MMXHTML 1.2//EN"...

  • Page 25: The Weblogic Mobility Server Jsp Tag Library

    PCs. The WebLogic Mobility Server JSP tags reduce the amount of run-time processing that WebLogic Mobility Server is required to do. The tags run within the servlet environment, unneeded tags are stripped off, and the streamlined file is sent on to WebLogic Mobility Server where a minimum of processing is required before it is sent out to the browser.
  • Page 26 For data that should be ignored by the WebLogic Mobility Server parser: <meta name=“MIS-CDATA-Control“ <mm:meta name=“MIS-CDATA-Control“ content=“Unwrap“ /> content=“Unwrap“ /> <![CDATA[...]]> <mm:cdata>...</mm:cdata> For the creation of an Option menu: <meta name=...“ content=“...“ <mm:meta name=“...“ content=“...“ scheme=“mmsection“ /> scheme=“mmsection“ /> 22 - BEA WebLogic Mobility Server User Guide...
  • Page 27 Part III Fundamentals of Mobile Content Examples Here are two versions of a short file that will be transformed by WebLogic Mobility Server. They demonstrate the way in which the mobility tags are placed into a document. The meaning of the tags used in these examples will be explained in later sections.

  • Page 28: Optimize Performance With The Jsp Tag Library

    The required mobility tags for full browser are run and remaining tags stripped off. This allows some of the WebLogic Mobility Server transformation processing (Step 5) to be bypassed.
  • Page 29 Skip Multi-Mode Tag Checking For JSPs that are known to use only the WebLogic Mobility Server JSP tags (and not the WebLogic Mobility Server mmXHTML tags) it is possible to disable multi-mode tag checking. This allows WebLogic Mobility Server to assume JSP tag usage during processing.
  • Page 30 The WebLogic Mobility Server JSP taglib pages that are being requested by any browser will behave as if there are no WebLogic Mobility Server mark-up tags in the content - the taglib will self-process the file and the output sent to the requesting browser without being further processed by WebLogic Mobility Server.

  • Page 31: Work With Xhtml

    Delimit all attributes with double quotation marks: <table width=”100%”> Supply Values for all Attributes All attributes must have explicit values. Attribute minimization is forbidden. For example, the following HTML code has a minimized attribute “checked”: <input type=checkbox checked/> BEA WebLogic Mobility Server User Guide - 27...
  • Page 32 XML Declaration Required The XML declaration declares that the current document conforms to the XML specification. The declaration has three attributes: version, encoding, and standalone. The shortened syntax is as follows: <?xml version="1.0"?> 28 - BEA WebLogic Mobility Server User Guide...
  • Page 33 (for example to reject stand-alone “&” symbols in XHTML attributes). For integration with pre-existing content and frameworks, this strictness can be switched off by setting the Boolean Note: If the value of this property is changed, WebLogic Mobility Server must be restarted for the change to take effect. xsp.strictAttribute: true...
  • Page 34 “&” character within attributes, by allowing for non-strict XML to be parsed. This is to minimize the impact on portal / application integration where the content of attributes may not be strictly legal XML. 30 - BEA WebLogic Mobility Server User Guide...
  • Page 35 Example In the following sample code, the line contains non-strict XML. When <a href …></a> is set to false, WebLogic Mobility Server, as shown in the following xsp.strictAttribute graphic, processes the output from this code. When is set to true, xsp.strictAttribute...

  • Page 36: Organize Content

    ID that can be referenced when deciding which groups of content should be delivered to specific devices. WebLogic Mobility Server introduces the notion of implicit and explicit groups. Implicit groups are created by assigning an to an existing XHTML tag like a form or a table.
  • Page 37 <mm:body id="..." idref=".."> where is the unique identifier you give your body and is the identifier of the heading idref associated this body content. For example, <mm:body id="bd_address" idref="hd_details"> BEA WebLogic Mobility Server User Guide - 33...
  • Page 38 The code example on the next page illustrates how the contact details for an organization (name, address, phone and fax numbers) could be defined as a group. 34 - BEA WebLogic Mobility Server User Guide...
  • Page 39 “Company Details” does not appear on full browser devices. useradded <mm-group id="gp_company_details" title=”Details”> <mm-head id="hd_company_details" useradded="yes"> Company Details </mm-head> <mm-body id="bd_company_details" idref="hd_company_details"> <p>ABC Company Ltd.</p> <p>North Business Park, Circular Road, Dublin, Ireland</p> <p>Phone: 888-000-111</p> <p>Fax: 000-888-111</p> </mm-body> </mm-group> BEA WebLogic Mobility Server User Guide - 35...
  • Page 40 <mm-group id="gp_company_details" title=”Details”> Company Details <p>ABC Company Ltd.</p> <p>North Business Park, Circular Road, Dublin, Ireland</p> <p>Phone: 888-000-111</p> <p>Fax: 000-888-111</p> </mm-group> Using mm-group with No Head or Body Image Courtesy of Openwave Systems Inc 36 - BEA WebLogic Mobility Server User Guide...
  • Page 41 <mm-head id="hd_company_details" useradded="no"> Company Details </mm-head> <p>ABC Company Ltd.</p> <p>North Business Park, Circular Road, Dublin, Ireland</p> <p>Phone: 888-000-111</p> <p>Fax: 000-888-111</p> </mm-group> mm-group with mm-head and no mm-body Image Courtesy of Openwave Systems Inc BEA WebLogic Mobility Server User Guide - 37...
  • Page 42 The reason for this is that the text is interpreted by WebLogic Mobility Server as being logically part of the sub-group rather then as text within the body of the surrounding group.
  • Page 43 Again, the order in which you link definitions together will determine the order in which they are displayed. You could, for example, have the content of the last cell appear before the contents of the middle cell. BEA WebLogic Mobility Server User Guide - 39...
  • Page 44 The following graphic illustrates how the groups, once defined, can be represented for display on a handheld device. Using Groups to Create Content for Mobile Devices 40 - BEA WebLogic Mobility Server User Guide...
  • Page 45 <mm-group> content “Copyright”, and the group has been assigned a group ID of “footer”. <mm-group id="footer" title="Example Footer"> <mm-include where="IsMenuDriven"> <span> -----------------<br/> <b>Copyright</b><br/> -----------------<br/> </span> </mm-include> </mm-group> BEA WebLogic Mobility Server User Guide - 41...
  • Page 46 You can place the header and footer groups anywhere on the page • If more than one mm-structure exists for the same class of device on a page, ensure that the idheader and idfooter attributes exist on the first of these mm-structures 42 - BEA WebLogic Mobility Server User Guide...

  • Page 47: Create Conditional Content

    PDA. Include or Exclude Content WebLogic Mobility Server provides two tags to include or exclude content: <mm-include> <mm-exclude>...
  • Page 48 Device Repository. • Provides support for nested expressions using parentheses. • Provides support for partial string matching (for example startswith, endswith, find). • Provides user-friendly compilation warnings by throwing detailed exceptions. 44 - BEA WebLogic Mobility Server User Guide...
  • Page 49 The logic operators supported include “and”, “or”, and “not”. All of the following expressions are valid: where • where=“UsableWidthPixels < 200 and UsableHeightPixels < 300” • where=“UsableWidthPixels < 200 or UsableHeightPixels < 200” • where=“not IsPortraitPDA” • where=“not MP3Supported” BEA WebLogic Mobility Server User Guide - 45...
  • Page 50 WebLogic Mobility Server Application Server console. If there is more than one reason why an expression is invalid, only the first reason will be reported. In Production Mode, the expression evaluates to false but no warning is sent to the console.
  • Page 51 The following are well-constructed expressions but the device attribute does not exist within the WebLogic Mobility Server system. Note: In the second example, because of the missing single quotes, WebLogic Mobility Server assumes that DeviceName is being compared to another device attribute. This will result in an error.

  • Page 52: Miscellaneous Issues

    Short circuit logic applies. This means that if a syntax error has not been encountered before the outcome of the statement has been determined, there will be no error. WebLogic Mobility Server does not continue to evaluate a statement once a result has been established Use “where”...
  • Page 53 If the where condition returns true, a line of text is included for devices that match a specific device name AND have a attribute of 120. UsableWidthPixels This body text will not appear on a PC browser. BEA WebLogic Mobility Server User Guide - 49...
  • Page 54 And the title tag at the top of the file is changed to: <title>Use of “or”</title> The include text is output on both the M3Gate and full browsers as follows: Example 3 on a full browser and (menu-driven) device 50 - BEA WebLogic Mobility Server User Guide...
  • Page 55 Part III Fundamentals of Mobile Content Example 3 Result on a WML Menu-Driven Device BEA WebLogic Mobility Server User Guide - 51...
  • Page 56 <title>Use of “endswith”</title> then the text inside the tags would be displayed on the Mozilla/4 browser because <mm-include> it ends with 4. Results of Example 4 in PC browser (Mozilla/4) 52 - BEA WebLogic Mobility Server User Guide...

  • Page 57: Part Iv Presentation Of Mobile Content

    It explains how WebLogic Mobility Server transforms a document marked up with the WebLogic Mobility Server mobility tags into the mark-up of the requesting device and introduces the concept of developing a navigational structure for the smaller screen devices.
  • Page 58 However, to deliver content that has simply been translated into the appropriate mark-up for the requesting device would not necessarily produce optimum results. Web Site Arranged for WML Device Image Courtesy of Openwave Systems Inc Web Site Arranged for XHTML-MP Device 54 - BEA WebLogic Mobility Server User Guide...
  • Page 59 WAP content is arranged as a set of menu items (or links) and PC content is presented very similarly to the original mark-up. During this second phase, WebLogic Mobility Server also performs the application of cascading style sheets for devices that cannot support style sheets locally.
  • Page 60 PDAs and phones. Restyle for PDAs WebLogic Mobility Server provides 2 methods for authors to restyle their web content for PDAs. Which method you select depends on the type of content you are presenting. Method 1 is used primarily for smaller documents, which can have the content groups rearranged one above the other.
  • Page 61 The content of the first table cell is grouped and labelled “group1”. The content of the second table cell is grouped and labelled “group2”. These groups are then referenced from the layout file using the tag. <mm_id-ref> BEA WebLogic Mobility Server User Guide - 57...
  • Page 62 PC browser, would appear side by side and places them one on top of the other. Group 1 displays above group 2. The tag <mm:id-ref> uses its attribute to reference IDs of the pre-defined groups. idref 58 - BEA WebLogic Mobility Server User Guide...
  • Page 63 The next illustration shows how this content might be organized using a layout file containing a simplified template, as was seen in the previous example using myFile.jsp. For larger pages, parts of the content will not be visible without scrolling. BEA WebLogic Mobility Server User Guide - 59...
  • Page 64 For smaller amounts of content, this solution works well. For larger amounts of content, pagination works better. The following graphic illustrates how the four content blocks might appear if the content was paginated using the tag. <mm:structure> 60 - BEA WebLogic Mobility Server User Guide...
  • Page 65 <h4><strong>PDA Pagination Demo</strong></h4> <mm:layout src="pagination_layout.jsp" where="IsPDA" /> </head> <body> <table> <tr><td> <mm:group id="groupA" title="Hamlet"> <p>There are more things in heaven and earth, Horatio, than are dreamt of in your philosophy. </p> </mm:group> </td></tr> <tr><td> BEA WebLogic Mobility Server User Guide - 61...
  • Page 66 </p> </mm:group> </td></tr> <tr><td> <mm:group id="groupD" title="Twelfth Night"> <p>Be not afraid of greatness. Some are born great, some achieve greatness, and some have greatness thrust upon 'em. </p> </mm:group> </td></tr> </table> </body></html></mm:page> 62 - BEA WebLogic Mobility Server User Guide...
  • Page 67 { color: gray; font-size: 8pt; } a:link {color: green; } As can be seen on the next page, a navigation section replaces the and only one <mm:structure> group is displayed at a time. BEA WebLogic Mobility Server User Guide - 63...
  • Page 68 Part IV Presentation of Mobile Content Displayed Navigation Section Clicking on a link shows the contents of that group. Content outside the <mm:structure> persistent, meaning it will appear on all pages. 64 - BEA WebLogic Mobility Server User Guide...
  • Page 69 =”normal” (This is the default if this attribute is missing.) For PDA pagination, “normal” type is the only acceptable value for this attribute • =”headings” For PDA pagination, this is the only acceptable value for this attribute display BEA WebLogic Mobility Server User Guide - 65...
  • Page 70 If the same layout file were sent to a menu- <mm:structure>. driven device, the header and footer would not appear. Using the preceding example and changing the where attribute of the <mm:layout> tags to target menu-driven devices: <mm:structure> 66 - BEA WebLogic Mobility Server User Guide...
  • Page 71 Displaying Content of the Group Image Courtesy of Openwave Systems Inc Notice that the header and footer material does not appear. Only the groups referenced from within the structure appear on a menu-driven device. BEA WebLogic Mobility Server User Guide - 67...
  • Page 72 <mm:structure id="pagination_str" where="IsMenuDriven"> <mm:group-ref idref="header" depth="flat" display="all" type="normal" /> <mm:group-ref idref="groupA" depth="0" display="headings" type="normal" /> <mm:group-ref idref="groupB" depth="0" display="headings" type="normal" /> <mm:group-ref idref="groupC" depth="0" display="headings" type="normal" /> <mm:group-ref idref="groupD" depth="0" display="headings" type="normal" /> </mm:structure> 68 - BEA WebLogic Mobility Server User Guide...
  • Page 73 , see “Appendex A – depth display Mobility Tag Reference.” Note: The attribute is used to style the navigation block in this example. This attribute navstyle is covered in detail in the next section. BEA WebLogic Mobility Server User Guide - 69...

  • Page 74: Navigational Menu Styling

    The previous section showed how WebLogic Mobility Server creates navigational structures for PDA and menu-driven devices. This section shows how to style these navigational structures. Without any styling, the navigation created by WebLogic Mobility Server displays as a single column table as can be seen in the following illustration.
  • Page 75 Part IV Presentation of Mobile Content WebLogic Mobility Server allows content authors to customize the navigation. The following types of styling are possible: • Multi-column table with the user able to set the number of columns and rows • List with items separated by <br />...
  • Page 76 Using lists can be helpful when delivering content to devices with vastly different screen widths. WebLogic Mobility Server will retrieve the width of the requesting device from its Device Repository and wrap the list in an appropriate place. Using tables can have undesirable consequences if the screen width can’t accommodate the width of the table.
  • Page 77 <mm:structure> • For a <br /> separated list: navstyle="nav-format: list" • For a space-separated list: navstyle="nav-format: list; nav-list-item-display: inline" • For a pipe-delimited list: navstyle="nav-format: list; nav-list-style-type: pipe" BEA WebLogic Mobility Server User Guide - 73...
  • Page 78 <mm:media-group id="car" navstyle="display:none" alt="*"> <mm:img where="ImgGIFSupported" src="img/car.gif" alt="*"/> <mm:img where="ImgWBMPSupported" src="img/car.wbmp" alt="*"/> </mm:media-group> Navigation Styling with Images Adding images to navigation is done using the attribute in any of the following tags: navstyle 74 - BEA WebLogic Mobility Server User Guide...
  • Page 79 Styling the menus with images and text is done with the style. This can have nav-text-display three values: • inline • none • block Examples The following examples illustrate the use of these values. BEA WebLogic Mobility Server User Guide - 75...
  • Page 80 Example 1: Images with Inline Text Styling. The text displays next to the image (this is the default). <mm:structure id="str1" where="IsPDA" navstyle=”nav-format:list; nav-list-item- display: inline; nav-text-display: inline"> Navigation Styling with Images and Inline Text 76 - BEA WebLogic Mobility Server User Guide...
  • Page 81 Part IV Presentation of Mobile Content Example 2: Images with No Text Styling. Images appear as links by themselves. <mm:structure id="str1" where="IsPDA" navstyle="nav-format:list; nav-list-item- display: inline; nav-text-display: none"> Navigation Styling with Images and No Text BEA WebLogic Mobility Server User Guide - 77...
  • Page 82 Example 3: Images with Block Text Styling. Text displays beneath the images in a table. <mm:structure id="str1" where="IsPDA" navstyle=" nav-format:table; nav-table- rows: 1; nav-text-display: block"> Navigation Styling with Images and No Text 78 - BEA WebLogic Mobility Server User Guide...
  • Page 83 Sometimes, however, you might want to create a navigation list whose items are not based on any pre-defined group. WebLogic Mobility Server provides two tags to let you do this. •...
  • Page 84 As is the case with the where attribute of <mm:structure> where=”IsFullBrowser” is not allowed. Additional styling can be added using external style sheets as described in “Work with Style Sheets.” 80 - BEA WebLogic Mobility Server User Guide...

  • Page 85: Work With Style Sheets

    • Using the default style sheet • An example of SSCSS with the WebLogic Mobility Server sample news file Introduction to Style Sheets A style sheet is a simple mechanism for adding style (for example fonts, colors, spacing) to Web documents.
  • Page 86 A simple example is shown here: body { {font-family: arial, Helvetica, sans-serif; font-size: 1em; text-align: justify} {font-family: arial, sans-serif; font-size: em} {font-family: Courier New, sans-serif; font-size: 1em} .note {background-color: #003333; 82 - BEA WebLogic Mobility Server User Guide...
  • Page 87 Some PDA browsers, however, cannot support CSS. In cases like this, WebLogic Mobility Server will attempt to apply any external or internal styles by translating them into the nearest equivalent in-line style. The server does this translation before the page is delivered to the browser.
  • Page 88 Part IV Presentation of Mobile Content WebLogic Mobility Server CSS Support Not all CSS styles can be supported across all devices. This means that WebLogic Mobility Server will support the elements that are common between CSS1 and the mark-up language of the requesting device.
  • Page 89 | upper-roman | lower-alpha | upper-alpha] height <length> <hr>, <th>, <td>, <img> width <length> | <percentage> <hr>, <table>, <th>, <td>, <img> border <border-width> <table>, <img> padding <length> <table> margin <length> | <percentage> <img> BEA WebLogic Mobility Server User Guide - 85...
  • Page 90 <dl>, <dt>, <dir>, <menu> <pre> <hr> align text-align size height width width <table> align horizontal-align width width border border <caption> align vertical-align <tr> align horizontal-align valign vertical-align <th>, <td> align horizontal-align valign vertical-align 86 - BEA WebLogic Mobility Server User Guide...
  • Page 91 These 16 colors are taken from the Windows VGA palette. You can use any color specification you want, for example, hex, RGB, such as: p{ color: rgb(255,255,255); } or p{ color: rgb(fff);} or p{ color: #ff0000;} BEA WebLogic Mobility Server User Guide - 87...

  • Page 92: Manage Navigation

    Part IV Presentation of Mobile Content Manage Navigation This section describes pagination and Back-to-Top functionality in WebLogic Mobility Server. Pagination Pagination refers to dividing a document into pages. WebLogic Mobility Server provides the following two pagination options: • Automatic pagination Authors need not worry about manipulating pages, cards or decks (groups of cards) because WebLogic Mobility Server automatically handles pagination for targeted devices.
  • Page 93 Authors can set pagination style on all HTML elements and the mmXHTML element <mm- group> in order to alter the default behavior of automatic pagination. The <mm-group> element is used to chunk mmXHTML content into groups. WebLogic Mobility Server does not split groups into separate pages There is no need to set pagination style on the other mmXHTML tags as these do not behave as HTML elements.
  • Page 94 In this example, two page breaks have been suggested. One before paragraph two and one after. The result will be that the page will break after paragraph two. The reason is that WebLogic Mobility Server, after reaching the maximum page size, will search backwards through the content and break at the nearest suggested page break.
  • Page 95 The following example illustrates this. A page break avoid has been applied to elements 1, 2, 3 and 4. WebLogic Mobility Server attempts to keep these elements together. However, the four elements do not fit into the page space of a particular device.
  • Page 96 As you organize content into groups and sub-groups, each with its own head and body, you are effectively creating a hierarchical arrangement of content. WebLogic Mobility Server makes it possible to present this hierarchy as a set of navigation links. It generates these links automatically by compiling a list based on the headings you assigned to groups as you organized your content.
  • Page 97 Part IV Presentation of Mobile Content Create a Navigation Hierarchy for Menu-Driven Devices Earlier in “Organize Content for Handheld Devices”, we described the use of layouts and structures in WebLogic Mobility Server that involves the use of within an <mm-group-ref>...
  • Page 98 Part IV Presentation of Mobile Content • Scheme An identifier for WebLogic Mobility Server, the value should always be "mmsection". The normal XHTML rules applies, that is,, the tag must be located within <meta> <mm:meta> element. <head> Note: The Options menu will not be delivered to XHTML MP devices. This feature only works on WML devices that support the Options menu.
  • Page 99 Continuous usage of the Back to Top link will eventually bring the user to the navigation page for this document, that is, “Welcome to Your Stars”. Selecting “Back To Top” From Top Page In Subgroup BEA WebLogic Mobility Server User Guide - 95...
  • Page 100 This is shown in the following second and third graphics. Selecting "Back To Top"|From “Next” Page Here WebLogic Mobility Server will automatically inline a shortcut underneath the Next>> link. Via this link, the user will be able to navigate directly to the top of the group without having to repeatedly press the “Back”...

  • Page 101: Work With Tables

    Because of smaller screens, tables will often be wider than the viewable width of the device • Some WML devices do not support tables at all Table Meaning Lost on Device Without Table Support Table Support but Small Screen Image Courtesy of Openwave Systems Inc BEA WebLogic Mobility Server User Guide - 97...
  • Page 102 <mm:table-model> they have when delivering tables to handheld devices. It is important to understand how WebLogic Mobility Server interprets the difference between a row-major and a column-major table. Attributes attributes work together to tell WebLogic Mobility Server about...
  • Page 103 Cheese This orientation is important if using the attribute to display only a portion of bodylocation the table. WebLogic Mobility Server will understand which way to split the table so that meaning is not lost. • bodylocation=”…” (optional attribute) This attribute specifies which rows or columns are to be displayed. To display the entire table the value should be set to “*”.
  • Page 104 • tabletype=”normal | group” (required attribute) If the attribute is set to “normal”, WebLogic Mobility Server will attempt to tabletype display the entire table. If the table is bigger than what can fit onto a “card”, the page will be broken into multiple cards.
  • Page 105 <table border=”1”> <mm:table-model major=”row” headlocation=”1” bodylocation=”1 4” tabletype=”normal” where=”UAProf.BrowserUA.TablesCapable” /> <mm:table-model major=”row” headlocation=”1” bodylocation=”1 4” tabletype=”normal” sdtransform=”base-transform” where=” not UAProf.BrowserUA.TablesCapable” /> <tr><td>Fruit</td> <td>Vegetables</td> <td>Meat</td><td>Dairy</td></tr> <tr><td>Apple</td> <td>Carrots</td> <td>Beef</td> <td>Milk</td></tr> … BEA WebLogic Mobility Server User Guide - 101...
  • Page 106 Part IV Presentation of Mobile Content </table> Note: The use of where=”IsFullBrowser” is not allowed. WebLogic Mobility Server identifies which devices do not support tables and “flattens” the data being delivered to that device. Delivery to Device Supporting Tables 102 - BEA WebLogic Mobility Server User Guide...
  • Page 107 Flattened Table Image Courtesy of Openwave Systems Inc Note: When multiple table-model tags are present, WebLogic Mobility Server uses the first one who’s where clause conditions match the requesting device. An example of a more complex where condition can be seen in the following code block where the table will be flattened even if the requesting device supports tables if the screen width is less that 200 pixels wide.
  • Page 108 Reference this style from within the <table> tag: <table class="myclass"> And remember to link the style sheet to the document containing the table. <html> <head> <title>Tables</title> <link rel="stylesheet" href="mystyles.css" type="text/css"/> </head> 104 - BEA WebLogic Mobility Server User Guide...

  • Page 109: Work With Images

    GIF and JPEG, whereas some WML devices are restricted to the WBMP format. WebLogic Mobility Server provides a set of tags that manage graphic delivery to a variety of client devices. These tags allow you to specify the correct image format for the requesting device type.
  • Page 110 /> <mm-img where="ImgWBMPSupported" src="sm_dog.wbmp" height="30" width="30" alt="Chihuahua" /> </mm-media-group> WebLogic Mobility Server will select the first image that satisfies the where clause. In the preceding example, any full browser will match the first condition and will receive a <mm-img>...
  • Page 111 <mm:logo> deliver color images to these devices whilst delivering monochrome images to others. For instance: <mm:logo displaymode="once" period="3"> <mm:media-group alt=""> <mm:img where="ImgGIFSupported" src="myimage.gif" alt="Logo" /> <mm:img where="ImgWBMPSupported" src="myimage.wbmp" alt="Logo" /> </mm:media-group> </mm:logo> BEA WebLogic Mobility Server User Guide - 107...

  • Page 112: Work With Character Sets

    In XML, the XML declaration can contain the document encoding: <?xml version=”1.0” encoding=”ISO-8859-1”?> • In HTML, a <meta> tag can be used to define the document encoding <meta http-equiv=”Content-Type” content=”text/ html; charset=ISO-8859-1” /> 108 - BEA WebLogic Mobility Server User Guide...
  • Page 113 Configuring an application server to use a particular encoding depends on the individual server. For example, if you are using the Apache server, you can add a file named .htaccess to any directory to set the Content-Type of files in that directory and any sub-directories. BEA WebLogic Mobility Server User Guide - 109...
  • Page 114 5. Next, WebLogic Mobility Server checks the HTTP protocol to see if the Content-type response header has been defined. 6. If not, WebLogic Mobility Server checks the XML declaration and if this doesn’t exist, the HTML meta tag is checked.
  • Page 115 Part IV Presentation of Mobile Content Character encoding flow BEA WebLogic Mobility Server User Guide - 111...

  • Page 116: Fine-Tune Mobile Content

    Part IV Presentation of Mobile Content Influence the Character Encoding Delivered to the Device WebLogic Mobility Server selects the best encoding in which to deliver transformed content to a device based, in part, on the list of preferred encodings supplied by the device.
  • Page 117 <p>ABC Company Ltd.</p> <p>North Business Park, Circular Road, Dublin, Ireland</p> <p>Phone: 888-000-111</p> <p>Fax: 000-888-111</p> <form action="gotothis.htm" method="get"> <textarea name="thetext"> First line of initial text. Second line of initial text. </textarea> </form> </mm-body> </mm-group> BEA WebLogic Mobility Server User Guide - 113...
  • Page 118 Part IV Presentation of Mobile Content Use of <textarea> Tag 114 - BEA WebLogic Mobility Server User Guide...
  • Page 119 URL with shortened tokens. These shortened tokens are used by WebLogic Mobility Server to map a request generated from the replacement URL back to the original URL. Examples The following is an example of a URL of 359 characters produced by BEA WebLogic Portal: /avitekfinancial/application?namespace=tracking&origin=searchResults.jsp& event=link.clickContent&com.bea.event.type=com.bea.content.click.event&...

  • Page 120: Imode Support

    HTML is a subset of HTML dealing primarily with text and simple graphics. WebLogic Mobility Server supports this emerging technology. Content for iMode devices should be structured according to the general authoring guidelines for small devices as described in this manual.
  • Page 121 In most cases, it is not necessary to be this granular. Using IsMenuDriven should suffice. Access Key Support WebLogic Mobility Server supports the use of access keys on iMode phones. They work in virtually the same way as other devices that support access keys EXCEPT the attributes are not supported.
  • Page 122 3; This would apply the alphanumeric input mode to your textbox. Phone Number Dialing and CTI WebLogic Mobility Server supports the phone number dialing capabilities of iMode devices. The mobility tag has a new attribute which mimics the cHTML attribute <mm:phone-number>...
  • Page 123 It will wait for user key input once the receiving end picks up. • After key input, it will wait 2 seconds before dialing the extension "538#”. Phones that do not support the attribute will use the value of the attribute and dial +35312410500. BEA WebLogic Mobility Server User Guide - 119...

  • Page 124: Part V The Delivery Context Api

    In this way, WebLogic Mobility Server can tailor the presentation and delivery to each client device. Each device profile, or set of attributes defining the presentation and delivery capabilities of a device, is known as the delivery context.
  • Page 125 • IsMenuDriven • ImgWBMPSupported For further information on the full set of attributes, see the BEA WebLogic Mobility Server Administration Guide. Access CC/PP Device Profile Information CC/PP and UAProf Attributes JSR188 is a standard set of APIs developed by the Java Community to access delivery context information.
  • Page 126 <body> <mm:group id="gp1" title="API"> <mm:head id="hd1"useradded="no"><b>DC API</b></mm:head> <mm:body id="bd1" idref="hd1"> <p><strong>Optimal screen size: </strong> <%= screenSizeStr %> pixels.</p> <p><strong>Supported image types: </strong> <%= imgFormatsStr%></p> <p><strong>Table Support: </strong><%= tablesStr%></p> </mm:body> </mm:group> </body></html> </mm:page> 122 - BEA WebLogic Mobility Server User Guide...
  • Page 127 Part V The Delivery Context API Results Device Information on Desktop Browser BEA WebLogic Mobility Server User Guide - 123...
  • Page 128 Part V The Delivery Context API Device Information on Desktop Browser Device Information on WML Device Image Courtesy of Openwave Systems Inc 124 - BEA WebLogic Mobility Server User Guide...

  • Page 129: Additional Information

    JSR188 replaces the Mobility Delivery Context API. These methods are, however, still supported and must be used to access Mobility proprietary attributes. For additional details on using the Mobility Delivery Context API, see “Appendix B – Mobility Delivery Context API”. BEA WebLogic Mobility Server User Guide - 125...

  • Page 130: Part Vi Diagnostics

    You can use it to simulate device requests by manually creating HTTP requests or you can use it as a proxy between the device (or device emulator) and WebLogic Mobility Server to monitor the request / response cycle.

  • Page 131: Use The Diagnostic Console

    <url-pattern>/Diagnostics/*</url-pattern> </servlet-mapping> About the Diagnostics Server When connecting to BEA WebLogic Server, the CLI uses t3 (jndi protocol) to transport diagnostic messages. This is enabled when the web.xml file is configured for diagnostics. Start the Diagnostic Console The startup file for the Diagnostic Console (DiagnosticsConsole.exe) is located in the <bea installation directory>\weblogic81\mobility\applications directory...
  • Page 132 The address of the server that the Diagnostic Console is to connect with. For example, developer.myserver.com Port The port number of WebLogic Mobility Server. For example, 7001 or 8080. Listen Port The port number where the Diagnostic console should listen for new device/browser-based requests when it is configured in interception mode.
  • Page 133 These settings are saved when closing the Diagnostic Console and restored when the Console is restarted. Note: When the settings on the Settings Preference tab are altered, the log files are cleared. BEA WebLogic Mobility Server User Guide - 129...
  • Page 134 URL Request field: /news/index.jsp WebLogic Mobility Server concatenates the Server and Port values provided earlier with the request field to generate the target URL: http://server:port/news/index.jsp The other parts of the full URL will be taken directly from the other input boxes in the panel or derived from their contents.
  • Page 135 Part VI Diagnostics The Diagnostics Console Insert a Query String Use the Query String field to insert queries of the form: ?name=tonks. Do not use the “?” as this is inserted automatically. BEA WebLogic Mobility Server User Guide - 131...
  • Page 136 Name area, and no-cache to the Value area. The maximum number of name-value pairs that can be added is 20. Note: There is no need to enter a "Host:" header, as the WebLogic Mobility Server Application Server console generates this automatically.
  • Page 137 Request Method is POST; otherwise it is ignored. Specify the Target Device Use the Device Header field to specify the device being targeted. This ensures WebLogic Mobility Server generates the appropriate response to any HTTP requests coming from the Device Console.
  • Page 138 Part VI Diagnostics Issue an HTTP Request Press the Issue Request button to send the HTTP request to WebLogic Mobility Server. The response will appear in the Response Panel. The Issue Request button is disabled when a request is sent. When the request/response cycle is completed, the button is enabled again.
  • Page 139 Part VI Diagnostics Response content Save the Response Content You can save the response content as a text file. Click Save and provide the filename and location when requested. BEA WebLogic Mobility Server User Guide - 135...
  • Page 140 This will be useful for the user in that the content can be observed before (pre- transformed) and after (response) transformation. Note that when a large browser device requests a WebLogic Mobility Server JSP taglib page, the content delivered to the pre-transformed content panel is the response from the application server rather than the source of the taglib page.
  • Page 141 Click Save and provide the filename and location when requested. Work with Diagnostics You can control the type and amount of diagnostic information generated from WebLogic Mobility Server. These settings are saved when you exit the application and are restored when you restart it.
  • Page 142 Diagnostics panel. Standard Attributes Provided with Diagnostic Output Attribute Description Incoming URL This is the URL of the incoming request to WebLogic Mobility Server. For example, 199.168.5.30:7001/login.jsp Device Pattern This is the matched device pattern. For example root^WML^ericssonr380 Device This is the identified device.

  • Page 143: Use The Diagnostic Cli

    As you monitor WebLogic Mobility Server, it is likely that you will create a suite of diagnostic tests, each with its own set of parameters. The CLI supports the use of parameter files — text files containing a list of parameters —...
  • Page 144 The installed and configured CLI can be invoked either locally at the server's console or from a remote telnet client. Note: For the initialization of WebLogic, at least one HTTP request must have been issued to WebLogic Mobility Server before invoking the Diagnostic CLI, otherwise WebLogic will generate errors relating to the absence of a JNDI tree.
  • Page 145 To get help on a specific option, type: DiagnosticsTextUI -usage [option] Example: DiagnosticsTextUI -usage paraminfile Specify the Connection You need to specify a number of connection parameters in order to connect WebLogic Mobility Server with the diagnostic messaging: Connection Parameters Option Description...
  • Page 146 Specify, at the end of the command line, the diagnostic messages (topics) you want to listen to. Additionally, you can specify whether you want normal or verbose output. A full list of topics is described in the section. Example: MIS.Client verbose 142 - BEA WebLogic Mobility Server User Guide...

  • Page 147: Example Usage

    -username adminName -host Server1 -port 7001 -jndiprotocol t3 MIS.General.FlowOfControl verbose Example 3: Get Help on the Filter Parameter The following example displays the options available for the filter parameter: DiagnosticsTextUI –usage filter BEA WebLogic Mobility Server User Guide - 143...

  • Page 148: Diagnose Problems

    WebLogic Mobility Server generates an error page when it is unable to retrieve content or encounters problems when it is transforming content. Problems Retrieving Content WebLogic Mobility Server generates an error page if it is unable to retrieve the content. This occurs in the following circumstances: •...
  • Page 149 Part VI Diagnostics Resolve Badly Formed Content / Faulty JSP Code WebLogic Mobility Server generates an error page when it receives a page that contains poorly formed content. Typically, the error message will indicate missing elements or attributes, such as a missing “/”...
  • Page 150 Part VI Diagnostics The Diagnostic Console Properties Window 146 - BEA WebLogic Mobility Server User Guide...
  • Page 151 Part VI Diagnostics Resolve Database Errors WebLogic Mobility Server generates an error page when it has problems connecting to the Device Repository. It requires this database in order to recognize the requesting device and decide how to transform the content to match the device’s hardware and software capabilities.

  • Page 152: Monitor Diagnostic Output

    About Diagnostic Topics The diagnostic output can be broken down into a series of “topics”, where each topic relates to a different area within WebLogic Mobility Server, such as session management, cookie handling, device management or the transformation engine. Each topic has an associated set of messages that indicate the actions being taken and the conditions encountered as the requests and responses progress through WebLogic Mobility Server.
  • Page 153 DeliveryContext API — Monitors processing related to the use of DeliveryContext API methods • Flow Of Control — Monitors the general progress of WebLogic Mobility Server as it progresses through the request / response cycle Monitor Client Transactions Selecting Client Transaction topics will generate messages relating to headers, parameters, sessions, and cookies.
  • Page 154 Interpret Device Repository-related Messages Device messages relating to the database will indicate that a device is being looked up in the database, whether it exists (“found”) or not, and any attributes that are being retrieved. 150 - BEA WebLogic Mobility Server User Guide...
  • Page 155 MIS.FormPagination Interpret Pagination-Related Messages Since WML devices have a limited capacity to store and display content, WebLogic Mobility Server breaks the content into sub-pages, creates the appropriate links between the pages to ensure a seamless delivery, and caches the sub-pages so that they are ready for delivery when the WML device makes a subsequent request.
  • Page 156 Monitor Flow of Control Monitoring general activity turns on messages that indicate the flow of control, including the start-up sequence, as WebLogic Mobility Server processes requests and responses, requests received and finished events. It also provides cookies and header related information.

  • Page 157: Exception Handling

    Log4J. A GenericLogMonitor facility has been provided to enable output of diagnostic messages to a tool such as Log4J. For or details on using Log4J to monitor WebLogic Mobility Server Diagnostic output, see “Appendix D - Use the Generic Log Monitor Facility with Log4J”.
  • Page 158 Part VI Diagnostics Note: The console screen message states that WebLogic Mobility Server does not support the useragents attribute. <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//MOBILEAWARE//DTD MMXHTML 1.2//EN" "http://www.mobileaware.com/DTD/mmxhtml_1.2.dtd"> <html> <head> <title>Project 2.1 - Hello World</title></head> <mm-structure useragents="smallbrowser/wml" id="structure_1" where="IsMenuDriven"> <mm-group-ref idref="gp_101" type="normal" depth="0" display="all" />...
  • Page 159 Part VI Diagnostics Production Mode In production mode WebLogic Mobility Server provides error messages only. Warnings are not provided. Hello World Example The “Hello World” example illustrates that in production mode, no errors are produced in the console. The output is shown here:...
  • Page 160 Part VI Diagnostics Console Output in Development Mode Emulator Output in Development Mode 156 - BEA WebLogic Mobility Server User Guide...

  • Page 161: Part Vii Glossary

    (which have a name beginning with UAProf), the JSR188 API can be used. For accessing both the Mobility proprietary attributes and the CC/PP attributes, the WebLogic Mobility Server Delivery Context API can be used. This is a development package that provides a list of public access JSP methods to the Device Repository.
  • Page 162 WebLogic Mobility Server. It contains the various properties that are used to manage the behavior of WebLogic Mobility Server. The file can be edited in any text editor. Some of these properties will have been set during the install process, while others can be configured later to further tailor the behavior of WebLogic Mobility Server.
  • Page 163 DTD The mmXHTML DTD (Document Type Definition) is a file that defines the mmXHTML extensions to XHTML. The mmXHTML DTD is used by WebLogic Mobility Server to validate mmXHTML documents. WebLogic Mobility Server WebLogic Mobility Server is a modular, extensible, carrier-grade platform for creating and delivering multi-channel data, content and applications.
  • Page 164 URL into fragments (query parameters) and replacing the fragments in the URL with shortened tokens. These shortened tokens are used by WebLogic Mobility Server to map a request generated from the replacement URL back to the original URL.
  • Page 165 XML document that uses the formatting vocabulary. It is left to the specific output device, to decide how the formatted result is best translated into pixels, speech, or vectors. BEA WebLogic Mobility Server User Guide - 161...

  • Page 166: Part Viii Appendixes

    Description This tag is placed inside the document's <head> element. It has two WebLogic Mobility Server- specific uses: It can be used to create a shortcut link on the Options menu of WML devices that support such a menu.
  • Page 167 • content="Unwrap | NoUnwrap" If set to “Unwrap”, WebLogic Mobility Server will not parse the content that is wrapped by any CDATA section on the page (unless the CDATA tag itself has contradicting instructions), but will remove the CDATA tags when delivering the page so that the wrapped content will be interpreted by the client browser.
  • Page 168 Part VIII Appendixes See Also mm:cdata 164 - BEA WebLogic Mobility Server User Guide...
  • Page 169 <!-- Note the next paragraph will only be included on full browser devices - -> <p>This is paragraph 2</p> <!–- Note the body is linked to the previous body --> <mm-body id="bd_2" idref="bd_1"> <p>This is paragraph 3</p> </mm-body> </mm-group> See also mm-group, mm-head BEA WebLogic Mobility Server User Guide - 165...
  • Page 170 WebLogic Mobility Server transformation. In mmXHTML files, the <![CDATA[…]]> tag can be used in conjunction with the <meta…/> tag to protect such content from being analyzed or transformed by WebLogic Mobility Server, and yet still have this content delivered to the device.
  • Page 171 (var1 <= var2) then { function compareIt(var1,var2) { return 0 if (var1 <= var2) then { return 0 else { return 1 else { return 1 ]]> </script> </mm:cdata> </script> See also meta BEA WebLogic Mobility Server User Guide - 167...
  • Page 172 “and”, “or” and “not” operators from Python. Note: The “where” clause quoted string must not contain line breaks. WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching. Restrictions: •...
  • Page 173 <!-- This example illustrates the use of the mm-group, mm-head and mm-body elements. --> <mm-group id="gp_company_details" title="Company Details"> <mm-head id="hd_company_details">Company Details</mm-head> <mm-body id="bd_company_details" idref="hd_company_details"> <p>ABC Company Ltd.</p> </mm-body> </mm-group> See Also mm-head, mm-body, mm-group-ref, mm-id-ref, mm-structure BEA WebLogic Mobility Server User Guide - 169...
  • Page 174 Displays a collection of links to the group, its subgroups and its subgroup's subgroups. Displays that group, both heading and body and a collection of links to its subgroups if any. 170 - BEA WebLogic Mobility Server User Guide...
  • Page 175 Displays the heading of the group and any links that occur in the body of that group See Also mm-group, mm-structure BEA WebLogic Mobility Server User Guide - 171...
  • Page 176 <!-- This example illustrates the use of the mm-group, mm-head and mm-body elements --> <mm-group id="gp_company_details"> <mm-head id="hd_company_details"> Company Details </mm-head> <mm-body id="bd_company_details" idref="hd_company_details"> <p>ABC Company Ltd.</p> </mm-body> </mm-group> See Also mm-group, mm-body, mm-group-ref 172 - BEA WebLogic Mobility Server User Guide...
  • Page 177 Description This element causes WebLogic Mobility Server to place an instance of the referenced content at the point of insertion. This element is used in layout files. This is an empty tag, so it requires a slash (/) before the final angle bracket (>).
  • Page 178 “and”, “or” and “not” operators from Python. Note: The “where” clause quoted string must not contain line breaks. WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching. Restrictions: •...
  • Page 179 Part VIII Appendixes See Also mm-media-group, mm-logo BEA WebLogic Mobility Server User Guide - 175...
  • Page 180 “and”, “or” and “not” operators from Python. Note: The “where” clause quoted string must not contain line breaks. WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching. Restrictions: •...
  • Page 181 Part VIII Appendixes See Also mm-exclude BEA WebLogic Mobility Server User Guide - 177...
  • Page 182 “and”, “or” and “not” operators from Python. • WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching. Restrictions •...
  • Page 183 Part VIII Appendixes See Also mm-id-ref, mm-group-ref BEA WebLogic Mobility Server User Guide - 179...
  • Page 184 <!-- This example creates a styled navigation list with 4 elements.--> <div style="border: 1px solid"> <mm:nl navstyle="nav-format: list; nav-list-item-display: block”> <mm:li navstyle=”nav-image: url(dog.gif)” href="dogs.htm>Dogs</mm:li> <mm:li navstyle=”nav-image: url(fish.gif)” href="fish.htm">Fish</mm:li> <mm:li navstyle=”nav-image: url(cat.gif)” href="cat.htm">Cats</mm:li> <mm:li navstyle=”nav-image: url(fish.gif)” href="fish.htm">Fish</mm:li> </mm:nl> </div> See Also mm:nl 180 - BEA WebLogic Mobility Server User Guide...
  • Page 185 <mm-logo id="logo" displaymode="once" period="2"> <mm-media-group alt="Logo Image"> <mm-img where="ImgGIFSupported" src="/companylogo.gif" alt="ABC Company Ltd." /> <mm-img where="ImgWBMPSupported" src="/companylogo.wbmp" alt="ABC Company Ltd." /> </mm-media-group> </mm-logo> See Also mm-img BEA WebLogic Mobility Server User Guide - 181...
  • Page 186 Contains the <mm:img> elements that specify alternative media to deliver when a specific device is targeted. WebLogic Mobility Server will select an image from a media-group depending on the graphic support of the requesting device. If the device matches more than one where clause, it will receive the image from the first one that it matches.
  • Page 187 “and”, “or” and “not” operators from Python • WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching Restrictions •...
  • Page 188 Description This is a required tag for content that uses the WebLogic Mobility Server JSP taglib. The <mm:page> tag wraps the page content. Setting attributes in this tag can enhance the performance of JSP page processing by allowing the author the choice of bypassing the WebLogic Mobility Server transformation engine and/or of turning off the mixed-mode tag checking feature.
  • Page 189 If the phone is an iMode device, it will use the value of the cti attribute. After dialing the number, once the receiving end has picked up, it will pause for 2 seconds before dialing the extension 538#. --> <mm:phone-number num=”+ 35312410500" cti="+35312410500/,,538#"> Call Julia. </mm:phone-number> BEA WebLogic Mobility Server User Guide - 185...
  • Page 190 “and”, “or” and “not” operators from Python • WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching. Restrictions •...
  • Page 191 Groups referenced from within this mm-structure element will be displayed on menu-driven browsers. --> <mm-structure id="structure_1" where="IsMenuDriven"> <mm-group-ref idref="group_1" type="normal" depth="flat" display="all" /> <mm-group-ref idref="group_2" type="normal" depth="0" display="headings" /> </mm-structure> See Also mm-group-ref, mm-group BEA WebLogic Mobility Server User Guide - 187...
  • Page 192 If the required attribute tabletype is set to normal, WebLogic Mobility Server will attempt to display the entire table. If the table is too big for WebLogic Mobility Server to fit onto a “card”, the page will be broken into multiple cards when necessary.
  • Page 193 “and”, “or” and “not” operators from Python • WebLogic Mobility Server also supports use of the Python .endswith( ), .startswith( ) and .find( ) methods for partial matching. Restrictions •...
  • Page 194 Part VIII Appendixes <tr><td>Swimming</td> <td>Kayaking</td> <td>Rock Climbing</td> </tr> </table> 190 - BEA WebLogic Mobility Server User Guide...

  • Page 195: Appendix B - Mobility Delivery Context Api

    Retrieve a delivery context for the device currently interacting with the application by passing in the associated http request object. These are referred to In-session Queries because WebLogic Mobility Server automatically maintains a delivery context for the current device in the session.
  • Page 196 } catch(Throwable e) { out.println("<p>Problem creating delivery context.</p>"); %> </mm:group> </body> </html> </mm:page> The results when accessing Mobility attributes of a WML emulator are shown here. Results Image Courtesy of Openwave Systems Inc 192 - BEA WebLogic Mobility Server User Guide...
  • Page 197 For example, an alternative way to retrieve a delivery context for the Sony Ericsson P900 would be: DeliveryContext deliveryContext = DeliveryContextFactory.getDeliveryContext(deliveryContextStore, “DeviceUniqueName==’root^xhtmlmp^ericsson(xhtml)^sonyericssonp900’”) Note: If more than one device matches the indicated criteria, the first device that matched will be returned. BEA WebLogic Mobility Server User Guide - 193...
  • Page 198 //Gets the matching device whose Unique Name is root^wml DeliveryContext deliveryContext1 = DeliveryContextFactory.getDeliveryContext( deliveryContextStore, "DeviceUniqueName", "root^xhtmlmp^ericsson(xhtml)^sonyericssonp900"); System.out.println("DeviceUniqueName: " + deliveryContext1.getAttribute("DeviceUniqueName")); System.out.println("ImgGIFSupported: " + deliveryContext1.getAttribute("ImgGIFSupported")); System.out.println("IsPDA: " + deliveryContext1.getAttribute("IsPDA")); System.out.println("CharsetSupported: " + deliveryContext1.getAttribute("UAProf.SoftwarePlatform.CcppAccept-Charset")); 194 - BEA WebLogic Mobility Server User Guide...
  • Page 199 The following JSP example demonstrates the recommended practice of storing this within the scope of the servlet application. DeliveryContextStore deliveryContextStore = (DeliveryContextStore) application.getAttribute("DeliveryContextStore"); if(deliveryContextStore==null) { deliveryContextStore = DeliveryContextStoreFactory.getDeliveryContextDBStore( "jdbc:mysql://cleantest-dev/dbHEAD-G?user=root&password=", "org.gjt.mm.mysql.Driver"); application.setAttribute("DeliveryContextStore",deliveryContextStore); BEA WebLogic Mobility Server User Guide - 195...
  • Page 200 There are four exceptions that can be thrown when using the methods listed in the preceding table. It is considered good practice to place try – catch blocks around these method calls. 196 - BEA WebLogic Mobility Server User Guide...
  • Page 201 Thrown when an attribute name is requested and that attribute does not exist. This is different from the attribute existing and not having a value defined for the requesting device. AttributeValueUndefinedException Thrown when an attribute name is requested but the attribute value does not exist. BEA WebLogic Mobility Server User Guide - 197...

  • Page 202: Appendix C - Deprecated Items

    Part VIII Appendixes Appendix C – Deprecated Items This section describes the deprecated items in this version of WebLogic Mobility Server and the features that replace those items. The Device Repository has adopted the Composite Capabilities / Preferences Profile (CC/PP) standard.
  • Page 203 Part VIII Appendixes FoundationProfile1xSupported UAProf.SoftwarePlatform.JavaPlatform CLDC1xSupported UAProf.SoftwarePlatform.JavaPlatform CDC1xSupported UAProf.SoftwarePlatform.JavaPlatform JavaPhone1xSupported UAProf.SoftwarePlatform.JavaPlatform MIDP1xSupported UAProf.SoftwarePlatform.JavaPlatform PersonalJava1xSupported UAProf.SoftwarePlatform.JavaPlatform WAPVersion UAProf.WapCharacteristics.WapVersion MIDP2xSupported UAProf.SoftwarePlatform.JavaPlatform WTAIMakePhoneCallSupported UAProf.WapCharacteristics.WtaiLibraries WTAIAddPhoneBookEntrySupported UAProf.WapCharacteristics.WtaiLibraries WAPPushSISupported UAProf.PushCharacteristics.Push-Accept WAPPushSLSupported UAProf.PushCharacteristics.Push-Accept WAPPushSupported UAProf.PushCharacteristics.Push-Accept ViewableHeight UAProf.HardwarePlatform.Screensize ViewableWidth UAProf.HardwarePlatform.Screensize BEA WebLogic Mobility Server User Guide - 199...

  • Page 204: Appendix D - Use The Generic Log Monitor Facility With Log4J

    In order to use the GenericLogMonitor facility with Log4J it is necessary to: • Create a class that implements this interface - this is the class that will intercept WebLogic Mobility Server Exceptions, Warnings and Diagnostics. •...
  • Page 205 You must configure log4j with appropriate settings based on the desired format of the captured logs. An example log4j.properties file that will log WebLogic Mobility Server messages as Log4J messages to both the console and a file in a specified format is shown below: log4j.rootLogger=DEBUG, A1...
  • Page 206 The Session ID of the user's current session if applicable deviceName The device making the request (null until the device is recognized) username localServerIP Server IP serverPort Server Port localServerHostname Server Hostname requestRemoteHost Remote Hostname requestRemoteAddr Remote IP Address 202 - BEA WebLogic Mobility Server User Guide...

  • Page 207: Appendix E - Faq

    1252 -> utf-8 in the case of WML transformation. If you haven't specified the correct encoding in the file, there is the possibility that WebLogic Mobility Server may fail to correctly detect the encoding of the file. As a result, certain characters will be translated into the incorrect byte representation for the target encoding.
  • Page 208 Part VIII Appendixes Question 4 When I request a page from WebLogic Mobility Server, I receive a short message on my web browser indicating that the following error occurred: Internal error [40010u] In addition, the following error message displays on the Server Console window: *[MIS.FatalException] content processing exception building idocument...
  • Page 209 I have created a HTML page and have inserted some mmXHTML (<mm-exclude>) tags to exclude content from a "full browser". When I request the page, it seems that WebLogic Mobility Server has not processed the page at all. In addition, there is no output on the WebLogic Mobility Server Application Server console window.
  • Page 210 JSP/servlet authoring guide for more details of encodeURL(). Question 8 All of my WAP clients use cookies, but WebLogic Mobility Server still puts a session ID into “next” links, and so on, on the first page accessed in a session, resulting in some very long links.
  • Page 211 This can result from either the host/port configuration in the Settings Dialog being configured incorrectly or the web server / application server being unavailable. Correct this by changing the host/port combination, by starting up the server or by deploying the web application. BEA WebLogic Mobility Server User Guide - 207...

This manual is also suitable for:

Weblogic mobility server

Table of Contents