Management Center: Enabling Management Center client-side logging and tracing

Administer > Manage WebSphere Commerce features > Management Center

Enable Management Center client-side logging and tracing

Overview

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.
Log and trace information is stored in a log file on the WebSphere Commerce Server. If you plan to do this, then first configure logging in the WAS Admin Console, specifying the Management Center trace component...

com.ibm.commerce.lobtools

OpenLaszlo debugger window

By default the OpenLaszlo debugger window is enabled. To disable the OpenLaszlo debugger window that displays when using the Management Center user interface...

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.

Enable Management Center client-side logging and tracing

Access the following Web address in the browser:

https://host:8000/lobtools?logger.display=true

Log onto the Management Center:

Option Description
User Name Type the WebSphere Commerce user name.
Password Type the WebSphere Commerce logon password for this user name.

Click Log On.

Within the Management Center, from the Management Center menu, select Logging and Tracing.

From the Logging and Tracing dialog, expand Log Level Options and provide the following information:

Option Description
Default Log Level Select the type of information and level of detail to log and trace:

OFF
SEVERE
WARNING
INFO
CONFIG
FINE
FINER
FINEST
ALL

The default log level is INFO to track informational details only.
For detailed definitions about the log levels, refer to the WebSphere Application Server information center.
Component Log Levels For each WebSphere Commerce component listed, select the type of information and level of detail to log and trace. Here are the default components you can track:

com.ibm.commerce.lobtools.foundation.view
com.ibm.commerce.lobtools.foundation.model
com.ibm.commerce.lobtools.foundation.service
com.ibm.commerce.lobtools.foundation.util
com.ibm.commerce.lobtools.foundation.shell

The supported log levels are the same as the ones defined for Default Log Level.
The default log level for each component is INFO, to track informational details only.

From the Logging and Tracing dialog, expand Log Target Options and provide the following information:

Option Description
Message Buffer Size Select the logging and tracing buffer size, defined by the number of messages that the buffer can retain. The minimum buffer size is 100 messages and the maximum is 5000 messages. The default is 1000 messages.
Send Frequency Select the frequency, in seconds, that logging and tracing information should be recorded. The location of the information depends on whether you specified to send the information to the WebSphere Commerce Server, or to the OpenLaszlo debugger window. The minimum send frequency is every 10 seconds and the maximum is every 600 seconds. The default is every 20 seconds.

Click Enable to start recording logging and tracing information, using the settings specified in the Logging and Tracing dialog. When to stop recording the information, click Disable.

Optional: Click Send Now to log and trace information immediately, without waiting for the next scheduled send interval. For example, you might want to monitor an activity at a specific moment, such as immediately after a user saves an object using the Management Center.
The logging and tracing information is sent to a log file on the WebSphere Commerce Server located in this directory:

WC_PROFILE/logs/server1

WCDE_INSTALLwasprofile/logs/server1

Depending on the send frequency you specify within this dialog, the information is sent to the server at specified intervals.

Example

Alternatively, you can also enable logging and tracing using URL parameters by accessing the following Web address in the 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 Log 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 to log and trace. Available options are:

logger.level=OFF
logger.level=SEVERE
logger.level=WARNING
logger.level=INFO
logger.level=CONFIG
logger.level=FINE
logger.level=FINER
logger.level=FINEST
logger.level=ALL

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, to display 1000 messages in the buffer...

logger.bufferSize=1000

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, to record information every 100 seconds, specify...

logger.flushInterval=100

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

Related reference

Troubleshoot: Management Center

+
Search Tips | Advanced Search

Option	Description
User Name	Type the WebSphere Commerce user name.
Password	Type the WebSphere Commerce logon password for this user name.

Option	Description
Message Buffer Size	Select the logging and tracing buffer size, defined by the number of messages that the buffer can retain. The minimum buffer size is 100 messages and the maximum is 5000 messages. The default is 1000 messages.
Send Frequency	Select the frequency, in seconds, that logging and tracing information should be recorded. The location of the information depends on whether you specified to send the information to the WebSphere Commerce Server, or to the OpenLaszlo debugger window. The minimum send frequency is every 10 seconds and the maximum is every 600 seconds. The default is every 20 seconds.

Parameter Name	Description
logger.display	If logger.display=true, upon logging into theManagement Center, the Log 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 to log and trace. Available options are: logger.level=OFF logger.level=SEVERE logger.level=WARNING logger.level=INFO logger.level=CONFIG logger.level=FINE logger.level=FINER logger.level=FINEST logger.level=ALL
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, to display 1000 messages in the buffer... logger.bufferSize=1000
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, to record information every 100 seconds, specify... logger.flushInterval=100
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.