Part III Fundamentals of Mobile Content
Optimize Full Browser Performance
Here are the configuration options that can be used to optimize performance when delivering to
full browser devices.
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.
Configuration
mis.jsptaglib.passthrough: true | false
Note: the default is true.
When content is being delivered to a full browser, setting this property in the mis.properties file
to true causes the multi-mode content check and the WebLogic Mobility Server transformation to
be skipped. This is advantageous for JSP files that are known to have only mm: tags marking up
the content (for example, they only use the WebLogic Mobility Server JSP tags). The JSP taglib
will perform the processing needed. For content being requested for devices other than a full
browser, the content check and transformation is still performed by WebLogic Mobility Server.
Skip Multi-Mode Tag Checking for Specific Files in an Application
It is also possible to skip multi-mode tag checking for individual files known to use only the
WebLogic Mobility Server JSP tags.
Configuration
mis.passthrough.patterns: /patterns/*
Setting this property results in significant performance benefits for the files that match the pattern
specified in this the WebLogic Mobility Server property. For example, setting the pattern to *.jsp
would result in all files with the .jsp extension bypassing the buffer setup, content check, and the
WebLogic Mobility Server transformation when the requesting device is a full browser. This is
advantageous if it is known, for example, that all .jsp pages in a web application exclusively use
the WebLogic Mobility Server JSP mark-up.
Flag a Page for Optimization
Content authors can also flag a given page as only using the WebLogic Mobility Server JSP tags.
WebLogic Mobility Server will process the page the first time it is accessed, and then add the
URL to an internal JSP-only list. Subsequent requests will result in the same performance
benefits of setting the
property above.
mis.passthrough.patterns
Configuration
<mm:page bypass="true">
Skip Device Recognition
It is possible to skip device recognition completely if a JSP will only ever be accessed from full
browser devices as in the scenario where multiple app servers are used with some dedicated to PC
access.
BEA WebLogic Mobility Server User Guide - 25
Need help?
Do you have a question about the WebLogic and is the answer not in the manual?