Activate Logging in E Commerce Administration

Question

Hi All
Could anyone please advise how to activate Logging in E Commerce 5.0. I have gone through the steps given in Note 1090753. But then also I cannot see anything in Logging in the ECommerce administration.
when I go to http://host:port/b2c/admin/index.html
Click on Logging still the error is
"Logging is now configured centrally in the J2EE Engine Visual Administrator (server service: Log Configurator) "
I shall be grateful for the help..
Thanks
Gaurav Sahai
Edited by: Gaurav Sahai on Apr 4, 2008 1:15 AM

Answer 1

Hi Nelson
Thanks very much for the reply. But as I mentioned I have already gone through and performed the steps mentioned in the note...1090753.
But in the note there is one more thing mentioned ---
Once you complete the steps in note, and if you go to E Commerce Admin, you will see 2 tabs...
One is Log Configuration, and second is Session Tracing...
I am not able to see those tabs, in E Commerce Administration.
Could you please help me out with that. Points gurenteed.
Thanks
Gaurav Sahai.
Here is the text taken over from the NOTE.
Accessing the logging
For example:http://localhost/b2b/admin/index.jsp
3. J2EE administrator login
User: Administrator
Password: ('Your password'. Default: 'blank')
4. Choose the 'Logging' link.
a page with two tabs 'Log Configuration' and 'Session Tracing' is displayed.
Tab Log Configuration
Here can be the default log for a special location configured. The location is usually your Java package.
It is also possible to set a general log for a location like com.sap.isa.catalog. In this case a log is written only for catalog classes.
The logs configured here is session independent. That means everything from every client / user dependent on the severity is written into the log.
Create Configuration
A new log configuration can be created with this link.
The following options can be set:
EffectiveSeverity
The severity of the entries in the log file.
Path
The path where the log file shall be written to.
Limit
The maximum size of the log file.
Count
The number of files are written in this location.
Formatter Type
Each type of log destination can print the messages in different formats.
Currently, there are three major types of formatter:
TraceFormatter
Human readable format. This is very likely to be the most commonly used formatter when users want to quickly understand what is going on with the application.
Please use this formatter when sending logs to SAP Support!
XMLFormatter
Suitable for file transfer to be further processed in other applications
ListFormatter
Output in this format serves like a router to send the data to be processed further by another application, e.g. a log viewer, instead of being read directly by an end-user
Formatter Pattern
The pattern that shall be used to write the logs. This option is only visible if the TraceFormatter is used.
Here a few placeholders:
%d = timestamp in readable form
%l = the location of origin (eg: com.sap.FooClass.fooMethod)
%c = the log controller the message was issued through (eg: com.sap.FooClass)
%t = the thread that emitted the message
%s = the message severity
%m = the formatted message text
%I = the message id
%p = the time stamp in milliseconds since January 1, 1970 00:00:00 GMT
%g = the group identification