It’s not supported, but that shouldn’t stop every BI4 Administrator from benefiting from the wonderful insight it can provide. Too often customers feel they don’t understand what the Web Intelligence server is doing; some see it as a bit of a black box. No more. The webiadmintool is a sophisticated bit of kit and worth spending a good few hours to understand how it can help you.

Here’s a summary:

  1. The Profiling Dashboard will break down a single action, such as ‘opening a document’, into a large number of methods and for each its duration. Around 15 methods are shown for opening a document. This can help you identify which individual method is problematic: CMS communication, document cache, or generation of charts etc.
  2. The Service LifeCycle Information shows which ‘objects’ have been left in memory and yet to be cleaned up, potentially highlighting a memory issue.
  3. The Adaptive Processing Server Relationship shows, by user and document, which Web Intelligence server is using which other dependent service, like the Visualisation engine (for charts) or DSL Bridge (for the new Dimensional Semantic Layer). This means you can see inside the cluster to which user is consuming which bits of your cluster. This could be helpful to resolving a performance issue.
  4. The plugins perspective allows you to “Remove a session” or “Remove all sessions using a particular document” or “Remove all session used a particular user id” should you wish to eliminate processing that is consuming too many resources.
  5. The Profiling Perspective and Analysis enables you to compare two workflows with each other at a very detailed level. For example, you can compare the workflow of one user opening and interacting with a document, with the workflow for a different user. This might be helpful to isolate a performance issue, when one user ID performs slower than another.
  6. The monitoring perspective enables you to visually see load (sessions, users, documents, memory usage) over time in a graph. This is ideal to validate a load test; or help you identity characteristics on the usage of your server.
  7. The scheduling perspective shows you the internal tasks performed by the server, for self-maintenance and clean-up.
  8. The Failover/Recovery status will help you identify the server name, user id, or document name that is frequently failing and causing a recovery to occur. Thus allowing you to take remedial steps

I’ve written a detailed wiki on the tool which I hope provides enough information for how to use the tool and the benefits for using it.

Please visit and bookmark the wiki: http://wiki.scn.sap.com/wiki/x/e5hxFw

Your feedback is, as always, most welcome. Please comment here or contact me on Twitter.

Matthew Shaw

(Twitter: @MattShaw_on_BI)

To report this post you need to login first.

9 Comments

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

  1. Matthew Shaw Post author

    Thanks for your comments.

    Providing an overview of the tool is one thing but really I think customers want to see task centric instructions. Am I right?  Well, if so you may like what I’ve written here. Here I explain how to use the tool when there is a problem opening documents to isolate the cause: Using WebiAdminTool to identify problematic method for opening documents – Business Intelligence (BusinessObjects) – SCN…

    Feedback welcome!

    (0) 
  2. Kashif Ansari

    This sounds great. We are about to migrate to 4.1 and look forward to exploring the above tool. A quick question : Does this tool need enabling tracing at DEBUG level (Highest level) ?

    (0) 
    1. Matthew Shaw Post author

      You do not need to specifically enable tracing to use the tool. You can use the tool without any form of tracing enabled. Regards, Matthew

      (0) 
  3. Sascha Jaekel

    Hi Matt,

    in your wiki blog you mentioned to run the application locally. I’d like to know which of the .jar files I need to use. As customers running BI on non-Windows, they would also profit from this.

    cheers,

    Sascha 

    (0) 
    1. Matthew Shaw Post author

      Thank you Sascha.

      I suggest you copy them all from the folder “C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\apps\WebiAdminTool”. You’ll need to make sure this folder is in your CLASSPATH. (take a note of the ReleaseNotes.txt in the folder too)

      If those are not enough then throw in all the jars from the “C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib” folder

      Let us all know how you get on.

      Many thanks for trying and exploring the Webi Admin tool.

      Regards Matthew

      (0) 
      1. Sascha Jaekel

        Thanks Matthew,

        I had to put in all of the jar files from the …\lib  (really not sure which jar file was missing, had no time to debug). After doint this, the application runs fine in local mode.

        Thx!

        (0) 

Leave a Reply