Skip to Content

Continued from:  A complete guide to setup CA APM Introscope 9 for monitoring SAP BI Platform 4.1 on Windows [PART 1/2]

Step 4: Configure each BI node and application server node

In this step, we need to enable monitoring on each Apache Tomcat and BI Platform node. In this example, Apache Tomcat is installed by the SAP BI Platform installer. If you have a stand-alone install of Apache Tomcat or another Java application server you can copy the wily folder from the BI node to the Java application server node and complete the configuration as shown below.

  1. On the BI / Java application server node, browse to <INSTALL_ROOT>:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp then edit the file IntroscopeAgent_tomcat.profile with a text editor
  2. Search for $IntroscopeAgentEnterpriseManagerHost and replace this with the hostname of your Introscope Enterprise Manager
  3. Search for $IntroscopeAgentEnterpriseManagerPort and replace this with the agent communication port number of your Introscope Enterprise Manager

    /wp-content/uploads/2014/01/settings_377439.png

  4. Save the changes to IntroscopeAgent_tomcat.profile
  5. Launch the Apache Tomcat configuration editor (START–>Programs–>Tomcat–>Tomcat Configuration) then click on the Java tab
  6. Add the following Java properties under Java Options

    -Dintroscope.agent.name=TOMCAT_<PORT>
    -javaagent:<Path_To_Agent.jar>
    -Dcom.wily.introscope.agentProfile=<Path_To_IntroscopeAgent_tomcat.profile>

    Example:

    -Dintroscope.agent.name=TOMCAT_8080
    -javaagent:C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\Agent.jar
    -Dcom.wily.introscope.agentProfile=C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile

    /wp-content/uploads/2014/01/javatab_377441.png

  7. Click the Apply button, then click OK.

    generalTab.png
                       
                         

  8. Restart the Apache Tomcat service. If the Apache Tomcat service fails to start, check that you entered the Java properties correctly in the previous steps and that the files exist in the specified locations
  9. Next, launch the Central Management Console, logon as Administrator, choose Servers. Under nodes, right click on an SIA node and click Placeholders

    /wp-content/uploads/2014/01/plachol_377443.png

                           

  10. Edit the following Placeholder values:
    Placeholder Value Description
    %IntroscopeAgentEnableInstrumentation% true Enables or disables Introscope instrumentation on BOE Java based servers (APS, AJS, etc)
    %IntroscopeAgentEnterpriseManagerHost% IEMHOSTNAME Hostname of your Introscope Enterprise Manager
    %IntroscopeAgentEnterpriseManagerPort% 6001 Agent listening port of your Introscope Enterprise Manager
    %NCSInstrumentLevelThreshold% 10 Set the instrumentation level to 10
    %SMDAgentHost% localhost This property should always be set to localhost
    %SMDAgentPort% 6404 This port should match the port set in SapAgentConfig.xml

    /wp-content/uploads/2014/01/placeholders_676152.png
            

  11. Restart the Server Intelligence Agent and repeat steps 9 and 10 for each additional SIA node

Step 5: Validate the installation/configuration is working

In this step, we will make sure that the metrics are working correctly. Before you start this step, go ahead and refresh some Web Intelligence documents, Crystal Reports, Dashboards, etc to generate some performance data in the Introscope Enterprise Manager

  1. Go to start, programs, CA APM, then click on Introscope Workstation Webstart or browse to http://iemhost:8081/workstation
  2. Logon to Introscope using user Admin and password Admin89
  3. Click Workstation,New Investigator
  4. Expand SuperDomain, then locate and expand your BI / Java application server node
  5. Verify that you see the following:

    /wp-content/uploads/2014/01/nodes_377451.png

                    

  6. Next, click Workstation, New Console and validate that the Apache Tomcat and BOE 4.0 dashboards are returning data according to the products you are using in your BI landscape

    /wp-content/uploads/2014/01/boedash_377452.png

Congratulations, your BI landscape is now being monitored by CA APM Introscope.  Should you face a roadblock in the configuration, you can request help from SAP by submitting an incident to component BI-BIP-DEP.  Stay tuned to this space for forthcoming BI Introscope diagnostics and monitoring blogs coming soon!

Please don’t forget to rate this blog if you found this tutorial helpful.

To report this post you need to login first.

27 Comments

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

  1. Raj k

    Toby,

    As usual  thank you for this.

    I have deployed it and it works very well.

    Somehow I could not  see Apache Tomcat under dashboard.

    I could  see BO 4 and other things.

    Please help.

    Thanks!
    Raj

    (0) 
    1. Toby Johnston Post author

      Hi Raj,

      Do you mean, you can’t see Apache Tomcat dashboard?  Or do you mean you don’t see metrics under this dashboard?

      Thanks

      Toby

      (0) 
      1. Shiva Vishnubatla

        I think I know why this didn’t work. Theres a small typo with this path during java options.

        C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile

        Its best to ensure all these paths are checked in explorer according to your system to ensure success.

        Thanks
        Shiva

        (0) 
          1. Shiva Vishnubatla

            Hi Toby,
            In Step.6, Add the following Java properties under Java Options

            -Dcom.wily.introscope.agentProfile=C:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile

            there should be a space between Files and (x86). I copy pasted the paths direct and Tomcat didn’t show up first. But later I checked all the paths and found this one was a little bit off

            thanks,
            Shiva

            (0) 
  2. Missy Mazzola

    Hi Toby – quick [stupid] question, since I can’t get Tomcat to show up via the investigator under SuperDomain… when you say at the very top of Step 4:

    “In this step, we need to enable monitoring on each Apache Tomcat and BI Platform node. In this example, Apache Tomcat is installed by the SAP BI Platform installer. If you have a stand-alone install of Apache Tomcat or another Java application server you can copy the wily folder from the BI node to the Java application server node and complete the configuration as shown below.”

    Where should we copy the wily folder to? Tomcat7.0/<where?>

    Thanks,

    Missy

    (0) 
    1. Toby Johnston Post author

      Hi Missy, the default location is C:\usr\sap\wily however, you can put it anywhere you want.  I would just avoid having spaces in the path if possible.

      (0) 
  3. Peter Han

    Hello Toby,

    My customer update BI4.1 from SP5 to patch5.2. After that they found below error from SIA log, the error is repeating every minute.

    Failed to read file /sap/sap_bobj/enterprise_xi40/java/wily/dsl_slproxy_pdb.config

    It seems the system is reading wrong config because the correct one should be dsl_slproxy_pbd.config. But I didn’t see any place that we can input this value. Do you have any idea on where the issue could come from?

    Thanks,

    Peter

    (0) 
  4. Priya K

    Hi Toby,

    The hyperlinks in the Console is not working. No action occurs when clicked. Attached screenshot. I have done the configurations as per the document. Could you please help where should I be checking to resolve this?

    Thanks

    PriyaScreenshot1.png

    (0) 
      1. Priya K

        Hi Toby ,

        Thanks 🙂 It worked.

        With respect to tomcat dashboards, i don’t see any data for Apache Tomcat CPU, Apache Tomcat Http Sessions. Data is retrieved for other Tomcat Dashboards. Could this be due to any configuration issues?

        Also , with the standalone version, I suppose alerts can only be viewed in the workstation and cannot be customized. Please correct me if my understanding is wrong.

        Thanks

        Priya   

        (0) 
        1. Toby Johnston Post author

          Hi Priya,

          On the Tomcat server, are you using the IntroscopeAgent_tomcat.profile as suggested in this article?  This one has the probe builder directives needed to include the Apache JVM metrics.

          Regarding the alerts, yes with the standalone version (Right To View mode) it is read only.  You would need the full version of CA Introscope to edit the alerts (management modules). 

          Thanks

          Toby

          (0) 
          1. Priya K

            Hi Toby,

            Thank you for the response. I have re-checked the IntroscopeAgent_tomcat.profile and it has been configured as in the article. But still some metrics are not showing any data in few dashboards. To be precise, below are the metrics for which there is no data:

            Apache Tomcat CPU :  Apache Tomcat Host CPU Usage%, Apache Tomcat CPU used by Process%,Apache Tomcat Process CPU Time%

            Apache Tomcat Hibernate Details: Hibernate – Queries – Average Method Invocation Time, Hibernate – Sessions- Average Method Invocation Time, Hibernate – Cahce Concurrency – Method Invocations Per Interval

            Apache Tomcat Http Sessions:Apache Tomcat Active Http Session Count,Apache Tomcat Expired Http Session Count, Apache Tomcat Http Session Counter

            Apache Tomcat Servlets: Apache Tomcat Servlets Request Count

            Apache Tomcat Thread Pool Details: Apache Tomcat Acceptor Thread Count,Apache Tomcat Pooler Thread Count,Apache Tomcat Current Thread Count,Apache Tomcat Current Thread Busy Count,Apache Tomcat Send File Thread Count

            Apache Tomcat Threads: Apache Tomcat Max Thread Count

            Thanks

            Priya

            (0) 
            1. Toby Johnston Post author

              Hi Priya,

              On your Tomcat server, in the directory C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\logs there should be some logs if you search on *Tomcat*.log.   This may give clues to why the metrics aren’t working.

              Also, please provide the profile you are using for this.

              You can upload the logs and .profile here:  https://mdocs.sap.com/mcm/browser/v1/open?rep=share&obj=Ursgw-Vs5s4SZQLpP0MhHvQ4JFdbGt_TNpXUSibp8nA

              I’ll have a look

              thanks

              Toby

              (0) 
              1. Priya K

                Hi Toby,

                Thank you for the response.  Could you please provide me another link to upload the logs and the profile ? I am not able to upload using the current one. I will also check if I can find any clues from the logs.

                Thanks

                Priya

                (0) 
                    1. Toby Johnston Post author

                      Hi Priya,

                      The logs don’t seem to indicate a problem.  I see it reading in the Tomcat pbd(s) so technically the Tomcat metrics should be working.  It might be a good idea to download the latest version of the Introscope Java Agent and try this instead of the default agent that ships with BOE.  What version of the Introscope Enterprise Manager are you using?

                      Thanks

                      Toby

                      (0) 

Leave a Reply