Skip to Content

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

This article is now outdated.  Please refer to the new article:

New complete tutorial for setting up Introscope 9.5 Stand-alone Monitoring for SAP BI Platform 4.x (Part 1)

The procedure to setup CA APM Introscope 9 (formerly known as Wily Introscope) for SAP BI Platform 4.1 has got a bit easier however, the documentation is still spread out across several locations.  In this article, I will give you a complete step by step example on how to get started monitoring your BI landscape using CA APM Introscope 9.  In this example, I have one host which will run the Introscope Enterprise Manager and another host where I am running SAP BI Platform 4.1 SP2 + default Apache Tomcat deployment.

Here is the workflow we will follow:

  • Step 1:  Download the installation media from the Software Download Centre
  • Step 2:  Install the Introscope Enterprise Manager
  • Step 3:  Install the Diagnostic Agent on each BI node and application server node
  • Step 4:  Configure each BI node and application server node
  • Step 5:  Validate the installation/configuration is working

BEFORE YOU START:  Please be aware, this article is for setting up CA APM Introscope in stand-alone mode (without Solution Manager).  If your goal is to setup Solution Manager for BI, please check the following SAP Notes for instructions:

Step 1:  Download the installation media from the Software Download Centre

First, we need to download each piece of software from the Service Marketplace.  If you find that your S-USER does not have access to download one of these files then open a message under component XX-SER-SWFL and request access to download the file.  If you are installing to an operating system other than Windows x64 or if you are having trouble finding the files by browsing, then use the search option to search for the file names under Support Packages and Patches and locate the version appropriate for your platform.  In the table below, you can copy the file name and paste it into the search box as it is the exact search term that should be used.  Furthermore, if you find that the downloads do not complete successfully using the links below, then instead search for the files in the Software Download Center and add them to your download basket.  Once they have been added to your download basket, you can then download them via the software SAP Download Manager.

File Name Link
Introscope Enterprise Manager 9 SP15 DOWNLOAD
Introscope 9 customizations SP15 (aka Management Modules) DOWNLOAD
Diagnostics Agent 7.3 SP3 Windows 64-bit New version under development.  7.3 is no longer available.  Will update this space soon with updated info.
eula.txt  (right click and save target as) DOWNLOAD (right click and save target as) DOWNLOAD






Step 2:  Install the Introscope Enterprise Manager

SAP provides a read-only version of CA APM Introscope (RTV version) for free as part of your support contract.  This means that you can leverage the monitoring and root cause functionality provided by Introscope, without spending additional money on a full license.  Should you decide that you want to create alerts, customize dashboards, or utilize the Websphere/Weblogic power packs, then I encourage you to contact your account executive about upgrading to the SAP Extended Diagnostics package (SED).

The Introscope Enterprise Manager should be installed on a dedicated server which has 24/7 uptime.  All of the performance metrics are stored in the SmartStor database which is maintained by the Introscope Enterprise Manager.  For best performance, you should install to a dedicated hard disk with plenty of available disk space (300gb or more).  The Introscope Enterprise Manager makes frequent read/writes to this disk and works best if nothing else is reading/writing to this disk in parallel.

For additional information regarding Introscope installation process, refer to the CA APM Introscope 9.1.5 installation guide.

  1. Copy the Introscope Enterprise Manager 9 SP15 media, Introscope 9 customizations SP15, SAPCAR*.exe, eula.txt, and to a temporary folder on the host where you will be installing the Introscope Enterprise Manager


  2. Open a command prompt and extract the contents of WILY_IS_EM15_0-20007498.SAR using the sapcar -xvf command


  3. Edit the file eula.txt and change “reject” to “accept” to accept the end user license agreement


  4. Edit the file ca-eula.txt and change “reject” to “accept” to accept the end user license agreement


  5. Edit the file and update the properties USER_INSTALL_DIR and silentInstallChosenFeatures


  6. Double-click on the file introscope9.1.5.0windowsAMD64SAP.exe to launch the silent installer.  Wait about 2 minutes and check the install directory for failed log files.  If no failed log is generated then the install worked.  Confirm the install worked by checking your start menu


  7. Next, we need to turn up the Max Java heap setting for Introscope Enterprise Manager.  Browse to your Introscope install bin directory and edit the file C:\usr\sap\ccms\apmintroscope\bin\EMService.conf.  Change the Maximum Java Heap Size to 2048


  8. Next, copy the file WILY_IS_MM15_0-10010973.SAR and SAPCAR.exe to the root directory of your Introscope Enterprise Manager install.  Then extract the contents to this directory


  9. Next, go to Administrative Tools and restart the Introscope Enterprise Manager service


  10. Copy the files SAP_BOBJ.jar and SAP_Apache_Tomcat_Basis.jar from <DRIVE>:\usr\sap\ccms\apmintroscope\sap\extra_modules to <DRIVE>:\usr\sap\ccms\apmintroscope\deploy. 
    Copy the file SAP_Host.jar from <DRIVE>:\usr\sap\ccms\apmintroscope\config\modules to <DRIVE>:\usr\sap\ccms\apmintroscope\deploy
  11. Go to start, programs, CA APM, then click on Introscope Workstation Webstart or browse to http://introscopehost:8081/workstation  (note, you need to Java 6 x64 JRE installed).  If prompted with a security warning, check the box that you want to accept the risks and click run.


  12. Logon to Introscope using user Admin and password Admin89


  13. Click Workstation, New Console.


  14. Confirm that the BOE 4.0 dashboards are installed.  Confirm the Apache Tomcat dashboards are installed


Step 3:  Install the Diagnostic Agent on each BI node and application server node

The SAP Solution Manager Diagnostic Agent provides a framework from which the BI Platform 4.x c++ based processes can be monitored.  These servers connect to the agent listener port and collect/push Introscope metrics via the NCS libary (ncs.dll).  Additionally, the Diagnostics Agent also includes the SAP Host Agent which monitors operating system metrics via the SAPOSCOL.exe program.  It is recommended to install a Diagnostics Agent on each BI Platform node and also each node hosting a Java application server.  If you have a node that is hosting both the BI components and the application server components then only one Diagnostics Agent installation is needed.

For information on installing the SMD Agent on Unix/Linux refer to the Diagnostics Agent 7.3 SP3 Setup Guide

NEW!!  Tutorial for installing SMD Agent in stand-alone mode using silent installer on Linux

It is a requirement that you use a local administrator or root account to execute this installation.  Be aware, the sapinst installer will create three local accounts on the system and these accounts will be used to run the agent services.  The user accounts created are:

SAPServiceDAA  (where DAA is the system id for this agent)

The following user rights will be assigned to the user running the installation and to daaadm account:

•  Act as part of the operating system

•  Adjust memory quotas for a process

•  Replace a process level token

  1. Copy the files SAPCAR*.exe and the diagnostic agent installer DIAGAGT73SP03_0-20006981.SAR to a temporary folder on each BI node and application server node
  2. Open a command prompt, then unpack the Diagnostic Agent installation media using the SAPCAR -xvf command


  3. Browse to the extracted folder SMD730_IM_WINDOWS_X86_64


  4. Execute the Diagnostic Agent installer in stand-alone mode using the command sapinst SMD_INSTALLATION_SCENARIO=ishub

  5. Expand Solution Manager Diagnostic Agent–>SAP Systems–>Standalone Engines–>Diagnostics agent in SAP Solution Manager then select Diagnostics Agent and click Next


  6. You may be prompted that SAPinst needs to log you off in order to reliably continue the installation.  Click OK


  7. Log back on again and the installation continues automatically.  On the next screen, confirm that the hostname where you are installing the agent is correct then click Next.  If you are installing to a machine with multiple virtual hosts, specify the hostname of the virtual host where you would like to install the agent to.


  8. Next, specify the Diagnostics Agent System ID and the drive where you would like to install the agent to then click NextThe agent will always be installed to the path <DRIVE>:/usr/sap/<SID>/. 

  9. The Diagnostic Agent will create 3 user accounts which are needed to run the SMD Agent services.  Selecting local domain will have the installer create the user accounts locally on this host.  Alternatively, you can also use domain accounts which have already been created on the domain (for example: SAPServiceDAA, sapadm, daaadm). Select a domain model and click Next

  10. Next, you need to specify a password for the new user acccounts.  It is recommended to use the same password for all three user accounts and it is required that you use a strong password containing both upper-case and lower-case letters and numbers (9 or more characters).  After you have entered in both passwords, click Next

  11. You will be prompted to add the service account user to the trusted users list.  Click Yes

  12. Next, select a free instance number for this Diagnostics Agent.  If you do not have any other agents running on this host, choose the default instance number of 97.  Otherwise, enter another available instance number and click Next


  13. On the Unpack Archives screen there are no changes needed here, click Next
  14. On the Parameter Summary screen, click Next to start the installer


  15. When the installation completes, you will be prompted.  Click OK


  16. Open a command prompt, browse to <DRIVE>:\usr\sap\DAA\SMDA97\script then execute the following command to configure the agent to point to your Introscope Enterprise Manager:

    smdsetup.bat hostagentconf emhost:”IEMHOSTNAME” emport:”6001″


  17. Next, run the following command to enable the host agent

    smdsetup.bat hostagent state:on


  18. Download the attached SapAgentConfig.xml, copy it to <DRIVE>:\usr\sap\DAA\SMDA97\SMDAgent\applications.config\ and overwrite the existing SapAgentConfig.xml.  This file specifies the TCP port on which the agent listens for incoming metrics from BOE (NCS/c++ based) services.  By default, this port number is 59818
  19. Go to Control Panel–>Administrative Tools–>Services and restart the SAPHostExec and SAPDAA_97 services (where my system id is DAA and instance number is 97)
  20. Repeat the steps in this section for each BI and application server node

Continue to next part:  A complete guide to setup CA APM Introscope 9 for monitoring SAP BI Platform 4.1 on Windows [PART 2/2]

You must be Logged on to comment or reply to a post.
  • Hi Toby,

    As usual Great Article from you - Many Thanks.

    Just wondering is there a Dashboard similar to BO and Tomcat for Weblogic?

    if not can we use any of TC or Websphere's Dashboards?

    Kind Regards


    • Yes, there is a set of Weblogic specific dashboards.  This is included in the Weblogic Power Packs.  You would need to purchase the Weblogic Power Packs from CA or you can upgrade to the SAP Extended Diagnostics package (SED) and this will also provide you with the Weblogic dashboards.

      Unfortunately the Tomcat dashboards only work with Tomcat

  • Toby - are there other system requirements (or minimums) for install of the manager - for CPU and Memory?

    Altogether I think I would have one install of the manager and then I guess up to 15 nodes install the agent on if I account for each node and application servers across our 3 environments (dev, test, and prod).



  • Toby - I couldn't download the Introscope tool, so I reached to SAP Support for access. This is what they told us...

    "Introscope is a separate product you must own a license for this it is not bundled with solution manager. So to answer your question yes this can be run on its own without solution manager since it is a separate product and you must be licensed for it."

    Can you point me direction that would convince them and give me access to the tool? The incident number is 892310/2014 or better yet you can reach out to support for us.. Any guidance will be really helpful.

    May be my understanding is wrong about being free with your platform... I thought you had also told me in BI Elite class.



  • Hi Toby,

         Thanks for such a great article.  I was able to install Introscope Workstation and install the Diagnostic Agent on my BOBJ 4 server.  I'm able to see data in the Management Modules for all things except CPU utilization.

    Can you offer me some insight into troubleshooting this issue?

    I was able to determine that the CPU utilization is currently linked to -> BOE 4.0 PROCESS CPU in Management Modules Editor but no data is being collected there.

    I did notice correct data for SAP OS CPU - Utilization in the Management Module Editor but can't adjust the Dashboard to link to that information.

    Any help would be greatly appreciated.


    • Hi Brian,

      CPU utilization metrics (and other OS metrics) are collected by the SAP Host Agent (which is part of the Diagnostic Agent).  Check this screen for the path in Introscope Investigator 

      • Thanks for the response Toby.

        I  am able to see data being gathered for the CPU by following your example image.

        However, the BOE 4.0 TRIAGE Manage Module has CPU utilization linked to BOE 4.0 PROCESS CPU instead of SAP OS CPU - Utilization.

        Is there a way to adjust that potion of the module to display different data or a way to have the BOE 4.0 PROCESS CPU metric display data?



        • Sure, you can change it to whatever you want using the Management Module editor.  However, in order to use the MM editor you need to have either a full licensed version of CA APM Introscope (from CA) or you can also purchase the SAP Extended Diagnostics package from SAP via your Sales person.

          Once you have the full version, go into MM Editor then make a copy of the BOBJ management modules.  Then you can freely edit the copy of BOBJ MM.



  • Toby,

    Thanks for this.. it is going to be great help for us.

    As per your instructions, while running the following command

    smsetup.bat hostagentconf emhost:"XXXX" emport:"6001"

    getting the following error


    !! Error!! Cannot find directory of the host agent resources. (C:\usr\sap\DAA|\SMDA97\SMAgent\smd.config)


    Instead of this file, I see other files such etc.

    This file does not exists in that folder.

    Do you know how this file gets generated ?

    I tried same setup on two systems, getting the same error.

    Thanks in Advance


    • Toby,

      The issue is fixed. Instead of using SMD_INSTALLATION_SCENARIO, SAP_INSTALLATION_SCNEARIO was used.

      Thanks again!

      Keep  creating innnovation in BO admin area.

      • I'm getting this error trying to get this set up, but can't figure out what the SMD_INSTALLATION_SCENARIO refers to in order to see if it applies to my issue.

        Any further guidance?

  • Hi Toby,

         I opened an Incident in an attempt to gain help with an issue I'm having but it has yet to gain traction.  (Incident # 0001001020)

    I followed your fantastic guide, like I did with a single BOBJ 4.1 SP3 server once before, but this time for a distributed BOBJ 4.1 SP4 environment.

    1 Web Tier (Tomcat from BOBJ)

    2 Intelligence and Processing Tier

    1 Explorer Server

    Each of the server are reporting data to the Introscope Enterprise Manager correct except the Tomcat server.

    Tomcat is only showing Memory and GC information.  It seems that Tomcat isn't sending any WAS or SDK information.

    i.e. no Logon Avg Response Time, no Open Document Avg Response Time, etc.

    Any idea why this would occur?

    Are distributed environments not supported in Introscope

    Any help would be greatly appreciated!

    And once again, GREAT JOB on posting this Guide.

    • Yes, distributed environments are supported

      This would occur if:

      • Your introscope profile is not configured correctly
      • Your Tomcat java properties are not defined correctly
      • You aren't using the right Java Agent or are missing files in the Java Agent directory

      Can you post your Tomcat agent logs (in wily/logs directory on Tomcat server)?  Also if you can provide the above info I can provide suggestions



      • Hi Toby,

             I gathered the information and zipped it but I don't see a way to attach it to this post.

        I can paste my Tomcat Settings but the Introscope_tomcat.profile and Tomcat logs are a bit large.




        -Djava.library.path=C:\Windows\SysWOW64\;D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\

        -Dcatalina.base=D:\Program Files (x86)\SAP BusinessObjects\tomcat\

        -Dcatalina.home=D:\Program Files (x86)\SAP BusinessObjects\tomcat\

        -Djava.endorsed.dirs=D:\Program Files (x86)\SAP BusinessObjects\tomcat\common\endorsed\

        -Dbobj.enterprise.home=D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\





        -Xloggc:D:\Program Files (x86)\SAP BusinessObjects\tomcat\logs\tomcat.gc.log



        -javaagent:D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\Agent.jar

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

        -Xloggc:D:\Program Files (x86)\SAP BusinessObjects\tomcat\logs\gcTomcat.gc




        -Djava.util.logging.config.file=D:\Program Files (x86)\SAP BusinessObjects\tomcat\conf\

        Is there a way to send you a zipfile?


        • I see the problem.  It’s loading the default profile because it can’t find your tomcat specific profile

          10/16/14 02:02:30 PM EDT [INFO] [IntroscopeAgent.Agent] Trying to load file from D:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile

          10/16/14 02:02:30 PM EDT [INFO] [IntroscopeAgent.Agent] Unable to load D:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile because of: D:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile (The system cannot find the path specified)

          10/16/14 02:02:30 PM EDT [INFO] [IntroscopeAgent.Agent] Trying to load agent profile from resource from the class path based on system property "com.wily.introscope.agentResource"

          10/16/14 02:02:30 PM EDT [INFO] [IntroscopeAgent.Agent] Unable to load agent profile because the system property could not be found

          10/16/14 02:02:30 PM EDT [INFO] [IntroscopeAgent.Agent] Trying to load agent profile based on the working directory at: D:\Program Files (x86)\SAP BusinessObjects\tomcat\wily\IntroscopeAgent.profile

          10/16/14 02:02:30 PM EDT [INFO] [IntroscopeAgent.Agent] Loaded IntroscopeAgent.profile from D:\Program Files (x86)\SAP BusinessObjects\tomcat\wily\IntroscopeAgent.profile

          You need to make sure it can load this one:  D:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile

  • Hi Toby,

    Step 11 above says Java6 is needed... is that still the case? It looks like we have a more current version of Java installed on the machine I am trying to set this up on and it Introscope doesn't seem to like that... is Java 6 really required?



      • Hi again,

        Getting back into trying to figure my issue out where I cant get webstart to launch... and I noticed in the SAP Software Download Center there is a WILY INTROSCOPE ENTPR MGR 9.5 patch? Do we need this too? It looks like it was just recently added...


        • No, you don't need the 9.5 patch.

          If you have JRE 1.7 on the client where you want to run the Workstation webstart, there is a problem which is discussed in the release notes for Introscope 9

          • Workstation Web Start client fails to start with Java 7 Update 45 (Java 1.7.0_45) and newer due to security related changes.
            CA describes workarounds in the attached Techical Advisory (CA APM Technical Advisory - WebStart Workstation Issue_v5.pdf). SAP recommends following Option 1, which requires the modification of a single file in the file system (workstation.jsp) without the need for a restart of the Enterprise Manager.
          • With Java 7 Update 51 additional security changes get introduced causing the Workstation to fail again. As Workaround launch the Java Control Panel (Start->All Programs->Java->Configure Java). On the Security tab leave the Security Level as “High” and add the WebStart URL to the “Exception Site List”
            Example for WebStart URL:   http://xxxxx.yyy.corp:8081

          Try the workarounds suggested to solve the problem, or install JRE 1.6 on your client.



          • Missy,

            I followed the same steps mentioned by Toby above. It worked for me with version with Firefox, but not with IE 9.0. Let me know your observation with IE.

          • Toby - Thanks - I couldn't find the pdf you referenced, but I think I found a web version, 2 actually...  ( and the newer one says to set Security to Medium for update 51, which is what we have.  Once I did that, I got further, but not much as it now just hangs.... the logon screen never pops up, so I'm not sure what that is about.

            Jawahar - I am using IE 9.0 as well.  I don't have access to Firefox on the box I'm installing this on, so I can't try it. And as noted, I am using

          • Running from the command line gives me the same results... I get the security warning prompt, a prompt to block or not block, and then nothing.

            Trying to get jre 6x64 so I can see if that makes a difference or not... easier said than done in our environment 🙂


          • Actually, I can't... keep getting an error when I try to upload as if it is blocked... not sure what that's about, but to describe it in a little more detail... I basically get 2 security warnings...

            The first one, I figured is what you note in step2.11, asking 'Do you want to run this application' and that I have to select the box to accept the risk.  After I do that, I also get a message that asks whether or not I want to block potentially unsafe components from being run and am given the option to Block or Don't Block.

            I click on Don't Block, the message goes away, but nothing happens after that... I don't see any processes running, the Starting application goes away, etc.

            Having said that, we did get it to work from the command line with installing update 40 for java 7 now, but hopefully we/someone can figure out what is going on with update 51...?



  • Hi Toby,

    can you help on this ?

    We have host name with 14 characters and wily agent installation is complaining that it cannot be installed as host name  is more than 13 chararcters.

    Can you let me know if there is any alternate option ?

    These are all production systems,changing host name will create lot of additional tasks for us and also it is very complicated.



    • Hi Raj,

      Sorry for the delay, I've been out of office alot lately due to family.   I'm not aware of a workaround for this.  Maybe we could have a quick chat about this problem?



  • Hi Toby

    I tried installing Wily Introscope by downloading the files listed on this website, Two things.

    1). After installation i didnot get the folder 'deploy' described in step 10, so i manually created the folder and placed the requied .Jar files that you described in step 10 and 11.

    2). I am able to login using webview but not throught workstation. When ever i hit http://solmanhost:8081/workstation  url , its prompting me to download a workstation.jnlp file. I download the file & not sure where to place it. Please let me know if you can help.


    Arun Chanda

    • 1.  That's odd.  You should have definitely got a deploy folder.

      2.  The workstation requires Java 6.  Install Java 6 on the host where you will run the workstation and your client OS will recognize the jnlp extension (this is a Java extension)

      Also, please note this article is for Introscope monitoring without Solution Manager server (diagnostic agent is installed in standalone mode)  Just thought I would mention this since your host is named solmanhost.



      • Thanks for your quick response Toby.

        I have installed Java 6 (JDK6u45 & JRE6u45) on the server where i installed Introscope.

        What do i need to do with the jnlp extension after downloading, do i need to place it in any specific folder location, any ideas ?

        Is there any other specific documentation that describes Introscope with Solution Manager server, we have Solution Manager installed and trying to monitor the Business Obejcts servers using Solution Manager ?


        Arun Chanda

  • Do we really have to install a Java version that has been out of support for 2 years? Due to security reasons we only have the option to use Java 7u78/79 or Java 8u45. Will this be a showstopper for using CA Introscope 9.1.5?


    Niels de Jong / Tony Gusich

      • Toby,

        I'm still unclear where to find the download for the diagnostic agent, either for these directions or the new Introscope EM 9.5 directions. Are we in a holding pattern until a new version is available?


        Dallas Marks

        • Hi Dallas,

          Unfortunately, we are in a holding pattern waiting for an update to the Diagnostic agent.  However, you can still setup Introscope for the BI web applications and also the Java based BI services (APS, AJS, WACS, etc).  For this, follow my instructions for WIEM 9.5 and also make sure you use the latest version of Java 9 agent for the Web Application Server.

          I will follow up again when I have more information on the new diagnostic agent.  Sorry for any inconvenience this may be causing everyone.



          • Hey Ahsan,

            I'm afraid I've been busy on other projects.  I hope to make some progress on this in Q1 2016.  In the meantime, you can find the diagnostic agent on the BI Platform 4.0 install media under collaterals.



  • Hi Toby,

    Thanks for sharing this informative document,
    It has been very helpful indeed.

    We seem to be having issues with the SMD Agents installation, would really appreciate suggestions from the experts here.

    I am performing the 16th step under the SMD agent installation mentioned here,basically trying to connect the SMD agents to the EM using the cmd "smdsetup.bat hostagentconf emhost: "****" emport:"***"

    Receive the error" Cannot find directory of the host agent resources".

    On checking the logs from SMDSystem.0 I see the following warnings-

    -Connecting to SMD server ms://******:8101/P4 failed,NAming Exception "Exception while trying to get Initial Context:there are no access points for service:P4 registered on the message server.

    Has anyone seen this ?