This content has been updated and moved to the SCN Wiki

CA APM Introscope Monitoring Setup Guide for BI Platform 4.x (Windows)

 

This article is a continuation of: New complete tutorial for setting up Introscope 9.5 Stand-alone Monitoring for SAP BI Platform 4.x (Part 1)

 

 

Step 4:  Configure each BI node and Application Server node using ACTool

 

ACTool is a free program which automates the BI / Tomcat server configurations for Introscope Monitoring.  In this step, we will configure our BI / Tomcat node using the ACTool program.  For detailed information about ACTool, refer to the ACTool User Guide.pdf under the docs directory of the ACTool download.

 

  1. Browse to SAP Note 2137275 and click on link provided in the Solution section under Get the tool:/wp-content/uploads/2016/04/1_920845.png
  2. Download the zip file sap_actool-2.xx.x-bin.zip and copy it to a temporary directory on your BI / Tomcat servers (in this example, C:\actool)/wp-content/uploads/2016/04/2_920855.png
  3. Extract the contents of sap_actool-2.xx.x-bin.zip to your temporary directory./wp-content/uploads/2016/04/3_920856.png
  4. Browse into the <actool>\conf directory.  Delete the file products.xml and rename the file products_bolight.xml to products.xml (we are replacing the original products.xml).  Then, edit the file boe.properties with a text editor 
  5. Enter values for the following properties then save the changes to boe.properties: 
    Property Name Example Value Description
    boe.system mycmsname This is your CMS server name that you used to logon to the CMS (don’t use the @clustername)
    boe.user administrator This is your CMS administrator user account
    boe.password Password123 The CMS administrator password
    boe.cmc.introscope.host wiemhostname This is the hostname of your Introscope Enterprise Manager
    boe.cmc.introscope.port 6001 This is the port number of your Introscope Enterprise Manager
    tomcat.service.name BOEXI40Tomcat This is the service name of the Apache Tomcat server on this host
    tomcat.service.port 8080 This is the http port number of the Apache Tomcat server
    wily.EM.host wiemhostname This is the hostname of your Introscope Enterprise Manager (same as boe.cmc.introscope.host)
    wily.EM.port 6001 This is the port number of your Introscope Enterprise Manager (same as boe.cmc.introscope.port)
    smdagent.path C:\usr\sap\DAA\SMDA98 This is the path where you installed the Diagnostic Agent (up to the SMDAxx folder).  In this example, I installed the Diagnostic Agent to the C:\ drive using system DAA and instance 98

     

     

  6. In the folder where you extracted ACTool, double click run_actool.bat.  Type 2 and enter to choose the option SAP BI PLATFORM 4.x then type 1 and press enter for the option to Execute./wp-content/uploads/2016/04/4_920857.png
  7. Next, press enter to start all the configurations or refer to the selective options below: 

    SELECTIVE OPTIONS:

     

    – If this host does not have Apache Tomcat, you can enter 2,3,4,8,9,19 to skip the Apache Tomcat setup

    – If this host does not have BI components but only Apache Tomcat, enter options 4,12,14,15 to only setup Apache Tomcat and SAP Host Agent (or if you didn’t install the Diagnostic Agent choose options 12,14,15)


    /wp-content/uploads/2016/04/6_920864.png

     

  8. When the script is completed, you can close it by typing ‘quit’ and press enter.  Step 19 may report a failure, this indicates that the SMD Agent must be restarted manually.  Restart the services, SAPDAA_98, and SAPHostControlSAP_DAA.png
  9. Finally, restart the SIA and Apache Tomcat on this server./wp-content/uploads/2016/04/7_920866.png

Step 5:  Validate the installation/configuration is working

 

  1. First, logon to your BI Launchpad and refresh some Webi / Crystal / Dashboard documents to generate metrics.
  2. Next, open the Introscope WebView in a web browser (for example http://wiemhostname:8081/webview )
  3. Enter the default logon information (user: Admin password: Admin89)/wp-content/uploads/2016/04/admin_923172.png
  4. Click on Investigator, then expand *SuperDomain* and expand the hostname you just configured./wp-content/uploads/2016/04/webview_923167.png
  5. Confim that this host has the SAP HostAgent Process, SBOP ENTERPRISE\HOST, and Tomcat nodes under the host name.Note:
    If there is no Tomcat instance on this node, then only check for SAP HostAgent Process and SBOP ENTERPRISE/HOST
    If there is no SIA on this node then only check for SAP HostAgent Process and Tomcat or if you didn’t install the Diagnostic Agent, only check for Tomcat
  6. Next, in the WebView, click on the Console tab, and confirm that metrics appear under dashboards Apache Tomcat Memory, BOE 4.0 PLATFORM, and BOE 4.0 WEBI SERVER DETAIL

 

/wp-content/uploads/2016/04/dash0_923183.png

/wp-content/uploads/2016/04/dash1_923184.png

/wp-content/uploads/2016/04/dash2_923185.png

To report this post you need to login first.

7 Comments

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

  1. Kim Matthews

    Thank you for this blog.

    Question Please – how to clean up bad install?  EM registered node twice.

    The Host name is registered twice in the Super Domain.

    Host_1 has SMD and SBOP Enterprise – CSJNI processes, and DuplicateHost_2 has SBOP . 

    Attempted a cleanup/uninstall using ControlPanel to remove the Agent, MMC  SnapIn , manually deleted the folders sapinst_instdir and usr folders.

    Reran the install (using the same instance #).  Ran AcTool, confirmed CSJNI and cs.cfg file update configurations are in place.  Restarted all services including IEM – but registered a duplicate host.

    What’s the clean way to remove the duplicated Node? Expected the duplicate node to be removed when the profile files were removed from  c:\use\sap\DAA\SYS\profile entries.

    Thank you Kim

    /wp-content/uploads/2016/06/qa3w_1_973844.png

    (0) 
    1. Toby Johnston Post author

      Hey Kim,

      On the server browse to:

      <INSTALL_DIR>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily

      Edit the file IntroscopeAgent.template and change the value for property introscope.agent.hostName to lower case.  Then restart the SIA and this should merge them into one host in the Introscope Investigator.

      Regards

      Toby

      (0) 
      1. Kim Matthews

        Hey Thanks Toby! Yeah I found the issue was that and having mistakenly brought over a copy of introscopeAgent.CSJNI.profile from another node. It was a tedious find but also good lesson in understanding the many steps in the AcTool.  Thanks Toby the blogs are a huge help. 

        Kim

        (0) 
  2. Alan Chiwaridzo

    Great Article Toby. I successfully installed my Willy Introscope. Many Thanks.

    is there an article that can help us interpret the values from the dashboards.

    (1) 
    1. Toby Johnston Post author

      Hi Alan,

      Great, thanks for letting me know of your success with this.

      Check this document under chapter 12 for a nice breakdown of the BI dashboards

      Solman Root Cause Analysis Features for BI Platform 4.x

      I also developed some tutorial content for this Open SAP web course, check out week 4 Unit 4

      https://open.sap.com/courses/bifour1-1

      You can also find more docs and posts here: BI Platform Root Cause Analysis Wiki – Business Intelligence (BusinessObjects) – SCN Wiki

      Regards

      Toby

      (0) 
  3. Atul Divekar

    Hello Toby,

    I am unable to see host under SuperDomain but when i extract Custom Metric Host==> Custom Metric Process==>Custom Metric Agent==> Enterprise Manager==>Host i am able to see host name where i have installed ACTool and other related tools. I am using single node.

    *SuperDomain*|Custom Metric Host (Virtual)|Custom Metric Process (Virtual)|Custom Metric Agent (Virtual)|Enterprise Manager:Host = HostName

    (0) 

Leave a Reply