Did you ever had problems finding log entries related to a problem you are currently facing?
A really efficient feature within Web Channel Experience Management for everyone who has to deal with error analysis is the Session Logging tool that is part of the so called Administration pages. With this tool you can create a special downloadable log file which contains the entries related to a certain UI step/sequence. Advantages are as follows:
- no need to switch any debug settings with the log configuration tool of Netweaver Administrator, the log level is switched temporarily to level DEBUG during the current session and set back afterwards
- no need to look through huge log files resp. many pages of the log viewer to find the corresponding entries, the file does only contain entries that are produced during the current session
- no need to access any file system to be able to download the log entries within a file, there is a zipped file created which can be downloaded directly
First of all two remarks:
1. The Administration page is protected by security constraints in web.xml and can only be accessed with a UME logon on the Java application server. The user role has to be a role that is maintained as a context parameter in web.xml:
2. Session logging does not always function in a cluster that has more than one server process. To use more than one server process, install an additional instance that contains only one server process to run the Administration page.
The tool can be accessed via
Here a dedicated tab is available where the necessary steps are described:
So after having selected the application you want to create a session log file for, you have several options that are influencing the result:
Depending on what step or process you want to create a log file for, you can start the session logging immediately. According to this decision, there will be an additional button rendered in the next step, which gives you the possibility to start session logging at a later point in time.
In general it is recommended to log only the step in which an error occurred to keep log files from becoming too big, which means to leave the start session logging unchecked.
With the next two check boxes you can explicitly include log entries for categories UI components and resource handling. The tool switches the log level temporarily to DEBUG for all categories. As especially both mentioned categories are producing a large amount of log entries and to enhance the readability of the result, we decided to exclude these categories by default.
After having made these decisions, you can create the Application URL which then will be used to reproduce the steps you want to check:
Please be aware that executing the generated URL within the same browser will destroy the session the tool runs in and thus there will not be any usable result. Thus you have to use a different browser to start the generated URL.
If you have chosen to start session logging immediately, you can now reproduce the behavior you want to check (despite shown in the picture above, there will be no button available to start session logging). Otherwise you have to navigate to one step before the step you want to check, start session logging via the button, and then reproduce the behavior you want to check.
If you are done with the steps, you can stop session logging via the corresponding button and then download the created log file for further investigation.
Hopefully this blog will help you saving some time in error analysis 🙂
Security Guide for WCEM 2.0
(section User Roles on SAP NetWeaver AS Java for more information on assigning security roles to grant access to Administration page)