-
Notifications
You must be signed in to change notification settings - Fork 149
Oracle WebLogic geoportal logging
Marten Hogeweg edited this page Dec 14, 2012
·
1 revision
Weblogic does not pick up the default geoportal logging.properties file in the geoportal classes directory. In order to affect the logging properties, you must edit the main logging.properties for the java executable running WebLogic. Steps below discuss how to enable generating a logfile for the geoportal web application and writing it to an output directory of your choice. For more information, see the Oracle online documentation for WebLogic logging.
- Locate the java executable running weblogic, and within that folder, open its logging.properties file in a text editor. Tip: Sometimes the WebLogic java executable's logging.properties file can be found in the \\bea\jrockit\jre\lib or \\Oracle\Middleware\jdk\jre\lib folder.
- In the logging.properties file, find the java.util.logging.ConsoleHandler.level parameter, and change the setting from the default INFO to FINER.
- In that same file, scroll to the end of the file where the # Facility specific properties are defined. Beneath the example line for the com.xyz.foo.level = SEVERE facility, enter: com.esri.gpt.level = FINER
- Save the logging.properties file.
- The weblogic server scripts by default log all messages to the server's console. To redirect these to a log file, you need to edit the WebLogic Server startup script. Start by navigating to the startWebLogic.cmd file and opening it in a text editor. The startWebLogic file is often found in the \\wlserver_10\samples\domains\wl_server\bin folder, or a similar filepath.
- In the startWebLogic.cmd file, find the line that reads:
- Save the startWebLogic.cmd file.
- Restart the WebLogic service. After the service starts, your geoportal logfiles should be written to the C:\ drive.