Oracle Audio Technologies 9i ユーザーズマニュアル
Transaction Logging
Logging
4-5
4.3 Service Designer Logging
By default, the Service Designer writes error information to the log directory of the
Service Designer home directory. You can modify this setting, and the log naming
pattern, in the preferences.xml file. The file is in the WE_
HOME/tools/ServiceDesigner/resources directory.
Service Designer home directory. You can modify this setting, and the log naming
pattern, in the preferences.xml file. The file is in the WE_
HOME/tools/ServiceDesigner/resources directory.
4.4 Server Logging
The Wireless Edition writes server error information to the files and directory
specified in the System.properties file. You can open the log files directly, or view
them from the Wireless Edition Runtime Information and Management interface
(the Probe interface) at port 8090. Click the "Files" link.
specified in the System.properties file. You can open the log files directly, or view
them from the Wireless Edition Runtime Information and Management interface
(the Probe interface) at port 8090. Click the "Files" link.
The Wireless Edition specifies these types of errors:
Table 4–3
Server Error Information
In addition to error messages, the Wireless Edition provides extensive runtime
exception logging. When fatal exceptions occur, the Wireless Edition logs the
exceptions and stack traces in the global log file. If you need to contact Oracle
Support Services, you should have the log information available.
exception logging. When fatal exceptions occur, the Wireless Edition logs the
exceptions and stack traces in the global log file. If you need to contact Oracle
Support Services, you should have the log information available.
4.5 Transaction Logging
The transaction log is a log file on the Wireless Edition server that provides
information regarding user access. To enable transaction logging, you must include
transaction logging as a log level in the System.properties file. For example:
information regarding user access. To enable transaction logging, you must include
transaction logging as a log level in the System.properties file. For example:
log.level=Warning, Error, Notify, Transaction
Error
Value
ERR_SERVICE_UNAVAILABLE
PTG-001
ERR_SERVICE_ERROR
PTG-002
ERR_SERVICE_NOT_FOUND
PTG-003
ERR_CONFIGURATION_ERROR
PTG-004
ERR_INTERNAL_ERROR
PTG-005
ERR_DATABASE_ERROR
PTG-006