Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

What is it?

The End-To-End trace plugin is used to examine SAP BusinessObjects Business Intelligence Platform End-To-End trace logs, specifically for versions 4.x (4.0 / 4.1 / 4.2).

How do I use it?

  1. Follow KBA 1861180  - Customer instructions and best practice for collecting a BI Platform 4.x end to end trace [Video] to generate an End-To-End trace of a known problematic workflow
  2. Open the folder created as part of the steps, containing the BI Server logs, Web application logs and BusinessTransaction.xml
    Note: All *.glf files and the BusinessTransaction.xml must be located in the same folder, the tool won't load files in different folders.
  3. Drag and drop one of the log files in this folder to the FLR window to open it
  4. Select PLUGIN: BI 4.x GLF Log Parsing and End to End Analysis
  5. If you want to Load multiple .glf files in the directory or if you have an E2E trace folder generated, select:
    Load ALL .glf files in this directory including ones from different Business Objects servers
    This will include all server and web application .glf files and the BusinessTransaction.xml  

    If you want to load .glf files from one particular server, select:
    Load only .glf files from this selected Business Objects server process 

 

What does it do?

Upon opening an E2E trace, the plugin will first grab all relevant .glf files and the BusinessTransaction.xml contained within the folder, it will arrange all of the log entries in chronological order, so that entries from different logs are merged together and arranged by timestamp. 

If a BusinessTransaction.xml file was opened automatically by FLR with the logs, then it will automatically filter the logs for content relating to the action that was traced, it will display only the log entries for the server actions directly relating to the action taken by the user.

For example:

User Action traced using E2E
A user right clicks on a server to display the list of menu items

Information that will be displayed in the logs
SDK queries transformed into SQL queries sent from the web application to the CMS for processing by the CMS against the CMS DB

Like in the SetupEngine log, some tags will automatically be added:

  • Entries from each server will be tagged, allowing users to only display content from a specified server or servers
  • Potential errors including: Fatal, Exceptions, Errors, Warnings, Assert, and Scope
  • Multiple steps within one BusinessTransaction file, allowing a user to examine each step individually

Some content, such as empty lines and log file headers, are automatically tagged and hidden, as they are not relevant for investigation.

Note: The errors flagged by the parser are not always errors which could cause issues during installation, they are flagged for informational purposes. In some cases, errors may be relevant where other errors are not and for this reason, we tag all of them. Use discretion when examining these errors to help determine what is relevant.

Examples of use

Known workflow causes an issue:

  1. Follow the steps under the section 'How do I use it?' above in order to generate an E2E trace of the workflow and open the log in FLR
  2. Look through the workflow for related errors -  xSearch errors to determine relevance to the issue

Screenshots

  • No labels