Skip to Content

Dear Folks,

This blog is just to give an idea about how to enable tracing/logging in BusinessObjects 4.0 environment. Have done this today and I just wanted to share the same to our community.

The default logging path will be <Install directory>/SAP BusinessObjects Enterprise BI 4.0/ Logging and the trace files generated would be of type generic log file (.glf) extension. We can configure the trace logs for the following components

  • Logging Configuration for BOE Servers
  • BOE Web Applications logging

Below will be the various logging levels that we can set at trace log configuration.

Level

Description

Unspecified

Force the use of BO_trace.ini to be used

None

Only critical events such as failures will be logged

Low

Ignores warning and status messages

Medium

Only Status messages with least important will be ignored

High

Includes all the logging messages

1. Configuring tracing for BOE Servers

You can set the traces visually in CMC for a specific server or group of servers as below

/wp-content/uploads/2013/01/1_180568.jpg

/wp-content/uploads/2013/01/2_180584.jpg

Also you can manually set traces in BO_trace.ini file at the following location.

<BO Installation folder>\SAP BusinessObjects Enterprise XI 4.0\conf

/wp-content/uploads/2013/01/3_180586.jpg

2. Configuring tracing for web applications

You can set the traces visually in CMC for a BusinessObjects Application as below

/wp-content/uploads/2013/01/4_180591.jpg

/wp-content/uploads/2013/01/5_180592.jpg

/wp-content/uploads/2013/01/6_180593.jpg

Manually with the BO_trace.ini file

This sample is for BOE application with default Tomcat installation.

C:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\BOE\WEB-INF\TraceLog

               /wp-content/uploads/2013/01/7_180594.jpg

2. Configuring tracing for Client applications

To enable tracing for the BI4.0 client applications, you can refer SAP Note 1586166 – How to enable tracing for BI4.0 client applications

Hope you find this interesting. Keep reading!

To report this post you need to login first.

25 Comments

You must be Logged on to comment or reply to a post.

  1. Ludek Uher

    Hello Manikandan

     

     

    So many thanks for posting this very valuable content. I do believe though, that this would make a better Jive Document as opposed to a blog. As per the description in the document The Difference Between a Discussion, Blog Post, Document and Wiki re, blogs:

     

    Blogs are where you express your point of view or share your thoughts on something.  It’s your soap box to stand on if you want to bring something to the attention of  other community members or just share with them your ideas or experiences.

     

    Whereas a Jive Document:

     

    Documents are to share your articles and procedures.  These are informal, impersonal ‘How-To’ style guides or concise overviews of a topic or product. Other uses include links lists or related assets for a give topic or product, sort of like a resource guide.

     

    I think given the above you’ll agree that your post would make an excellent Document. I mean this as just an FYI. If you want to consider creating a Document out of this blog, that would be great. If not, for the future it would be great if you could consider the best option and go with that .

     

    – Ludek

    SCN Moderator

    (0) 
    1. Manikandan Elumalai Post author

      Ludek,

       

      Thanks for your feedback. I have been blogging in various Social media sites for quite sometime and I have followed the same in SCN as well. Given your comment I will start working out things in Jive document in my following articles. Many Thanks once again for guiding me to the right direction.

       

      Regards,

      Mani

      (0) 
      1. Ludek Uher

        Yeah. I know – I’ve seen your great contribution many times. And I thank you for those as well as your understanding. These doc vs. blog vs. wiki vs. article vs. what ever are confusing. I think it’s nice we have all those avenues, but they do cause confusion.

         

        Again, many thanks for your contributions,

        – Ludek

        (0) 
  2. Richa Pathak

    Hello Manik,

     

    Thanks for sharing this information. I have set up a trace log in CMC as suggested by you for WEBI application server. Could you please let me know the location of trace log files.

     

    Thanks,

    Richa

    (0) 
  3. SAP RON

    Hi Manikandan,

    Thanks for sharing this document.

    Can you advise me if configuring trace logs will help me to capture activities such as audit activities of users based on the event for various applications etc.

    I set up my auditing but not able to see the September logs when refresh the report whereas there is lot of activity happening in sept.

    Can you help me on this, thanks

    (0) 
  4. Skugan Venkatesan

    Hi Manikandan,

     

    Thanks for sharing this step by step document for trace logs. Just have a quick question here. Do we have anything like definite timeline for logs say for for example: after 15 days, the logs will automatically flush out (delete) and new set of logs will be written for every 15 days?. If it is there, then how can we set the timeline for logs?

     

    Thanks,

    Skugan V

    (0) 
    1. SAP RON

      Hi Skugan,

      You can set this value in the CMC, click on auditing and at the bottom set number of days according to your requirement, thanks

      (0) 
      1. Skugan Venkatesan

        Hi Mani,

         

        I have attached the image of the auditing page. You are referring the to the ‘DeleteEvents” parameter? If so, does this parameter set the timeline for APS, Application, CMS logs etc as well…?

         

        /wp-content/uploads/2014/09/logs2_542658.jpg

        (0) 
          1. Skugan Venkatesan

            Hi mani,

             

            Got your point !! But the thing is .. is there any definite time line set in BOE wherein after 60 days automatically the logs (like APS Logs etc..) will get deleted etc. ( not for audit logs) ? Is there any place where we can mention the time line say for example after 15 days these logs should get flushed out automatically? or is it that we have to manually archive the logs periodically as and when which I can assume that there is no parameter like this

            (0) 
  5. Santhosh Sreshta

    Hi

     

    Thanks for the great info.

    Can you please comment the location of where does the trace files been saved in the server.
    I was been encountering WIS 30270 error.

    connection server is been in initializing state.
    please provide soon

     

    thanks,

    Santhosh.

    (0) 
  6. Denis Konovalov

    you are incorrectly specifying that default /logging directory will have webapps trace logs, those will be in SBOP* directories and never in /logging

    (0) 
  7. Pramod Srivatsa

    Hi Manikandan,

     

    Any issues if we keep the trace log as “HIGH” for long time or is it advisable to bring it back to low or unspecified once the purpose is solved. Please advise.

     

    Pramod

    (0) 
    1. Manikandan Elumalai Post author

      It is always recommended to set the trace level to High only when you are investigating a specific service for an issue. If you set the trace level to high it will generate large number of log files. Your maintenance and Housekeeping efforts will increase proportionally. 

      (0) 
  8. Amit Bansal

    Hi Manik,

     

    If we have the Log level set to unspecified on services and BO_trace.ini file renamed to  BO_trace.ini.oriignal, will there be any logs in the lgging directory.

     

    Thanks,
    Amit

    (0) 
  9. Chokri kefi

    Hi ,

     

    and thanks for sharing all this info with us .

    i wanted to know , which level do we need for normal housekeeping ?

     

    Regards

    (0) 

Leave a Reply