Appendix E - Faq - BEA WebLogic User Manual

Appendix E – FAQ
Question 1
On the first request, I am presented with the following error message in the Application Server
Console:
"There is a problem with the database connection. This may be due to a network fault or an
incorrect database setting in the WebLogic Mobility Server configuration file".
What is causing this problem?
Solution
Ensure that the Application Server on which WebLogic Mobility Server is running and the
Database Server is both running and connected to the network.
The most likely cause for a database problem is incorrect database settings in the WebLogic
Mobility Server configuration file. This file is called mis.properties and is found in the /WEB-
INF/classes/ folder in the webapps directory containing the file you are requesting.
Ensure that:
•
the deviceDB.url is set to a valid URL for that database server
•
the deviceDB.driver has a correct driver (and correctly spelled) specific to the database server
you are using
•
the devceDB.username and deviceDB.password are correct
If this does not solve the problem, then please contact your Database Administrator to ascertain if
the problem is with the Database Server.
Question 2
Why do my error pages not appear on WAP?
Solution
WAP Gateways/Phones often catch the HTTP status and turn it into a generic message. This can
happen also in IE/Opera if you enable "friendly HTTP error pages" - a setting enabled by default
in both of these browsers.
Question 3
Why are there are incorrect or missing characters in the delivered content?
Solution
You may not have specified the correct content encoding in the source file. Sometimes
WebLogic Mobility Server will translate the page during transformation, for example windows-
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. Specify the encoding in either: (a) the HTTP header (b) the
XML declaration in the marked up file or (c) the <meta> tag in the marked up file. See also
"Work with Character Sets" on page 108 in this manual.
BEA WebLogic Mobility Server User Guide - 203
Part VIII Appendixes