# Message Logging

WebLogic Workshop writes diagnostic information to files that you can use to track activities of a WebLogic Workshop application. These logging messages originate from two distinct sources: the run-time environment and the Integrated Development Environment (IDE).

- Run-time Environment Logging
- IDE Logging

You can use this information to diagnose unexpected behaviors or monitor the general progress of any WebLogic Workshop application. This topic describes how WebLogic Workshop reports diagnostic information and where it writes the information. This topic also explains how you can configure WebLogic Workshop to report additional information to suit your needs.

## Run-time Environment Logging

The run-time environment refers to events that happen after you click the start button in the IDE and your application begins to run. These run-time events are logged to three files:

- ### workshop.log

- ### workshop_errors.log

- ### workshop_debug.log

These three files are always co-located in the root directory of the domain under which your WebLogic Workshop application runs. For example, if you are running the SamplesApp application that ships with WebLogic Workshop, you can find this file in the <WEBLOGIC_HOME>/samples/domains/workshop/directory. This is because the SamplesApp application runs in the workshop domain.

### workshop.log

WebLogic Workshop automatically writes all internal log messages to workshop.log. If you use log4j to add log messages to your application code, WebLogic Workshop will append those messages to workshop.log as well. For information about adding logging messages to your application code, see workshopLogCfg.xml Configuration File.

### workshop_errors.log

WebLogic Workshop writes all warning and error messages to a file named workshop_errors.log.

### workshop_debug.log

The workshop_debug.log file contains messages that are only useful to internal BEA developers, support representatives, and quality assurance representatives. You can ignore workshop_debug.log.

### Customizing the Way WebLogic Workshop Logs Run-time Messages

You might want to customize the way WebLogic Workshop reports diagnostic information. For instance, you might want to log information to a console or database instead of a file. Perhaps you would like to adjust the way these messages appear in the log file. If you want to have better control over these details, you can do so by editing the workshopLogCfg.xml file. This is WebLogic Workshop's default log configuration file. You can locate workshopLogCfg.xml at <WEBLOGIC_HOME>/common/lib/.

The workshopLogCfg.xml file defines which run-time libraries report information, the type of information they report, the display format of that information, and the log files to which that information is written. You can customize any of these details by editing workshopLogCfg.xml. Alternatively, you can override the settings in workshopLogCfg.xml by providing your own custom configuration file. For guidance on both approaches, see workshopLogCfg.xml Configuration File.

## IDE Logging

WebLogic Workshop also has an IDE logging feature, which logs various events from the IDE, such as events that occur during startup. IDE logging is off by default, but you can turn it on by following the steps in How Do I: Turn On IDE Logging?. These messages can help BEA technical support troubleshoot issues you may encounter when developing applications with WebLogic Workshop. WebLogic Workshop writes IDE-related log messages to a file named ide.log. You can find this file at <WEBLOGIC_HOME>/workshop/.

### Sample

The data shown below is an excerpt from <WEBLOGIC_HOME>/workshop/ide.log.

    DEBUG: extensions=C:\bea\weblogic81\workshop\\extensions
         INFO: Registering extension com.bea.portal.ide.CommonServices
         INFO: Service com.bea.portal.ide.findrefs.FindRefsSvc registered
         INFO: Handler for urn:com-bea-portal-ide:ref-finders registered
         INFO: Registering extension workshop.control.ControlServices
         INFO: Service com.bea.ide.control.ControlSvc registered
    ...
    ...
    DEBUG: WorkspaceLoaded: 11063ms
    DEBUG: *** CompilerProject constructor 1
    DEBUG: getClasspathMapping initiated with 21 item list.
    DEBUG: getClasspathMapping returning 21 item map.
    SourceLoader roots: 16
    DEBUG: Document Panel initialized: 14017ms
    DEBUG: Source Load: 2172
    INFO: Startup Complete
    DEBUG: Loading template file wsrp-producer-project.zip

Because this information is of minimal use to most WebLogic Workshop developers, WebLogic Workshop disables IDE logging by default. If you contact BEA technical support, representatives might ask you to enable logging in order to better diagnose IDE related issues. To learn how to turn on IDE logging see How Do I: Turn On IDE Logging?.

Related Topics

workshopLogCfg.xml Configuration File

How Do I: Turn On IDE Logging?