Step 1 Acquire a mobile device

Working with Pages Designed for Mobile Devices 9-13 If caching is enabled for the Oracle Portal page you are debugging, do not switch device types while using the OracleAS Wireless debug tool. If you need to switch device types, exit the tool, clear out any cookies, and then log back in to the OracleAS Wireless debug tool and continue your tests. If you do not, the Portal cache may contain contradictory information and this can result in unexpected behavior.

9.9 Troubleshooting Mobile Pages

Page portlets do not display properly on my mobile device. The value of page portlets for mobile portals is somewhat limited. Given that the behavior of page portlets on mobile devices is not intuitive, it is best to avoid the use of page portlets when building mobile portals. I receive a Service Error message If you receive the message while logging in to Oracle Portal, see the section above. If the error occurs at any other time, you will need to investigate the behavior of the OracleAS Wireless server. To start with, determine if any service can be run on the server. For example, can the OracleAS Wireless examples be executed from a mobile device or simulator? If not, then it is likely that there is a configuration problem with the installation in general. If the OracleAS Wireless examples work then review the contents of the sys_ panama.log error log for the OracleAS Wireless server. This log file is located in either ORACLE_HOMEwirelesslogs or vartmp. The log file records information about the response from the services causing problems Oracle Portal in this case and so shows if they are returning error statuses or invalid OracleAS Wireless XML. You can then correlate this information with the access_log of the Oracle HTTP Server process to find which requests are failing for example, a servlet request or a mod_plsql request. Depending on the findings of this research it may be necessary to contact your support representative. I receive the following error message: A Temporary Error Has... This error message is rendered by the Parallel Page Engine PPE. The PPE is sufficiently mobile aware to render error documents of type textvnd.oracle.mobilexml in the event of an error. The PPE is most exposed to errors when it is attempting to fetch the page metadata from the database. There is generally information in the metadata telling the PPE how to handle errors, but if the database’s response to the PPE’s request for metadata is not a valid metadata document, or an explicit error document, then the PPE must act on its own to render an error document for the user. When rendering error documents for standard desktop browsers the PPE simply takes the error document that resulted from the metadata call to the database and passes it to the end user. Desktop browsers can handle numerous content types, and for the content types that they cannot handle they will generally prompt for the document to be saved to disk. However, in the case of a mobile user this is probably not appropriate or even possible. Therefore error documents for mobile requests must be in OracleAS Wireless XML. Thus, if the PPE is servicing a mobile request and the database renders an error document, rather than metadata, that is not valid OracleAS Wireless XML the PPE: ■ Writes the document into the WLS_PORTAL-diagnostic.log MW_HOME\user_ projects\domains\DomainName\servers\WLS_PORTAL\logs.