Enabling Management Center client-side logging and tracing
A Site Administrator can enable logging and tracing for the Management Center to troubleshoot problems that a business user might have while using the Management Center. Client-side logging and tracing refers to tracking all the actions that a business user completes while using the Management Center user interface.
Before you begin
- Log and trace information is stored in a log file on the WebSphere Commerce Server. If you plan to do this, then you must first configure logging in the WebSphere Application Server Administrator's Console, specifying the Management Center (com.ibm.commerce.lobtools) trace component.
- By default the OpenLaszlo debugger
window is enabled. To disable the OpenLaszlo debugger
window that displays when using the Management Center user
interface, complete the following steps:
- Open WebSphere Commerce Developer and switch to the Package Explorer view.
- Right-click LOBTools and click Properties. Select OpenLaszlo Settings.
- Clear the Enable the debug console check box. Click Apply.
Procedure
Example
Alternatively, you can also enable logging and tracing using URL parameters by accessing the following Web address in your browser: https://host_name:8000/lobtools?logger.display=true, and appending the following parameter names and valid values:
Parameter Name | Description |
---|---|
logger.display | If logger.display=true , upon
logging into theManagement Center,
the Logging and Tracing option
displays in the Management Center menu.
Select Logging and Tracing to open the Logging
and Tracing dialog. |
logger.enabled | Specify logger.enabled=true to enable logging and tracing. |
logger.level | Specify the type of information and level of
detail you want to log and trace. Available options are:
|
logger.bufferSize | Specify the logging and tracing buffer size, defined by the number of messages that the buffer can retrain. The minimum buffer size is 100 messages and the maximum is 5000 messages. For example, specify logger.bufferSize=1000 to display 1000 messages in the buffer. |
logger.flushInterval | Specify the frequency, in seconds, that logging and tracing messages in the message buffer should be sent to the target (that is, to the server or the OpenLaszlo debugger window). The location of the messages depends on the value you specify for the logger.target parameter. The minimum send frequency is every 10 seconds and the maximum is every 600 seconds. For example, specify logger.flushInterval=100 to record information every 100 seconds. |
logger.components | Specify logger.components=component_name to
log and trace new components. These new components will be displayed
in the Component Log Levels list,
in addition to the default WebSphere Commerce components
list. Use a comma (,) to separate component names, if you have multiple components. For exxample, logger.components=com.company.component1,com.company.component2,com.company.component3. |
All parameters are optional. Separate each parameter name
and value pair with an ampersand (&). Here is an example of enabling
logging and tracing using the URL and parameters method: https://host_name:8000/lobtools?logger.display=true&logger.enabled=true&logger.bufferSize=500&logger.Interval=30&logger.level=ALL&logger.components=com.company.component1,com.company.component2