Skip to Content

This content is outdated.  The updated content has been moved to the SCN Wiki

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


Previously, I posted on the SCN an article on how to setup Introscope Monitoring for the BI Platform.  This article is a replacement to the previous article posted here: A complete guide to setup CA APM Introscope 9 for monitoring SAP BI Platform 4.1 on Windows [PART 1/2]

Due to changes in the new SAP Solution Manager Diagnostic Agent 7.4, there has been a period of time where it was not possible to setup Introscope monitoring for the BI Platform unless you had the full SAP Solution Manager stack in your environment.  After some research, testing, and working with various teams here at SAP, I’m happy to announce that you can once again setup Introscope monitoring for your BI landscape.

This article is applicable to those SAP BusinessObjects customers who:

  • Do not have an SAP Solution Manager system
  • Do not have an SAP Basis team or ABAP / Netweaver experience
  • Would prefer to only implement Introscope Monitoring tools without the full SAP Solution Manager stack


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

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 using AC Tool
  • Step 5:  Validate the installation/configuration is working

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

First, we need to download each piece of software from the Service Marketplace.  The files required for this configuration are part of the SAP Solution Manager files on the Software Download Center.  If your company has a Standard or Enterprise Support contract, you should have usage rights and access to download SAP Solution Manager software. If you find that your S-USER does not have access to download one of these files, 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 (from the File Name column) 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 Details
SAPCAR 7.20 DOWNLOAD SAPCAR is used to extract files from SAR archives (similar to winRAR).  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the SAPCAR version for your specific platform
WILY INTROSCOPE ENTERPRISE MGR 9.5 DOWNLOAD Install media for the CA APM Introscope Enterprise Manager.  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the WIEM version for your specific platform
WILY INTRO EM MGMT MODULES 9.5 SP6 DOWNLOAD Management modules and customizations files which contain SAP instrumentation and BOE dashboards
SWPM 1.0 SP18 for NW higher than 7.0x DOWNLOAD This is the Software Provisioning Manager (replaces the older sapinst).  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the SWPM version for your specific platform
721 UC Kernel for SWPM SP18 DOWNLOAD This is the Kernel file and includes the Diagnostic Agent 7.4.  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the Kernel version for your specific platform
(Right click and save target as)
DOWNLOAD License agreement for CA APM Introscope  (Right click and save target as) DOWNLOAD OSGI Packages required for Introscope Enterprise Manager installation


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.


  1. Copy the Introscope Enterprise Manager 9.5 SP6 media (, Introscope 9.5 SP6 customizations (, eula.txt, and to a temporary folder on the host where you will be installing the Introscope Enterprise Manager/wp-content/uploads/2016/04/1_920661.png 
  2. Extract to a folder WILYISEM06_0-70000324 then move eula.txt and to this folder/wp-content/uploads/2016/04/2_920662.png
  3. Edit the file eula.txt and change “reject” to “accept” to accept the end user license agreement/wp-content/uploads/2016/04/3_920669.png
  4. Edit the file ca-eula.txt and change “reject” to “accept” to accept the end user license agreemen
  5. Edit the file  If you want to change the default install location, update the property USER_INSTALL_DIR. Next, set silentInstallChosenFeatures to All/wp-content/uploads/2016/04/5_920671.png
  6. Double-click on the file introscope9.5.6.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/wp-content/uploads/2016/04/6_920672.png
  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, extract the file to folder WILYISMM06_0-70000299.  Browse to folder WILYISMM06_0-70000299 then select all files and copy them to your clipboard
  9. Browse to the location where you installed CA APM Introscope Enterprise Manager (by default: C:\usr\sap\ccms\apmintroscope) then paste the contents of your clipboard to this folder.  When prompted, check the option Do this for all current items and select Yes to merge the contents./wp-content/uploads/2016/04/9_920675.png 
  10. Next, go to Administrative Tools and restart the Introscope Enterprise Manager service/wp-content/uploads/2016/04/10_920676.png
  11. 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
  12. Open a web browser, then browse to the Introscope WebView.  For example (where wiemhostname is your Introscope Enterprise Manager hostname):  http://wiemhostname:8081/webview
  13. Logon to Introscope using the default credentials.  User: Admin and Password: Admin89/wp-content/uploads/2016/04/admin_923188.png
  14. On the Console tab, click the drop-down menu for Dashboard to choose a dashboard
  15. Confirm that the BOE 4.0 dashboards are installed.  Confirm the Apache Tomcat dashboards are installed/wp-content/uploads/2016/04/dash4_923189.png


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


In this step, we will install the Diagnostic Agent 7.4 on each BI node and Web Application Server node.  If the BI node and Web Application Server node are on the same host (as shown in this example), then you only need to install the Diagnostic Agent once.


  1. Copy SAPCAR*.exe, the SWPM (SWPM10SP18_2-20009707.SAR) and Kernel file ( to a temporary directory on your BI server (in this example C:\media)/wp-content/uploads/2016/04/d1_992969.png 
  2. Extract the contents of to this temporary directory.  The extracted Kernel folder will be named Krnl_7.21_WIN__IA32__IA64__x64__SP11_

  3. Open a command prompt and browse to your temporary directory and run the command:SAPCAR_721-20010453.exe -xvf SWPM10SP18_2-20009707.SAR/wp-content/uploads/2016/04/d3_992971.png
  4. After the files are extracted, execute the commandsapinst.exe SMD_INSTALLATION_SCENARIO=ishub/wp-content/uploads/2016/04/3_920760.png
  5. After the Software Provisioning Manager starts, scroll down to the bottom of available options, expand Generic Options, Diagnostics in SAP Solution Manager, then choose Install – Diagnostics Agent and click Next/wp-content/uploads/2016/04/4_920761.png
  6. Next, under DVDs or Blu-Ray Media click Add then click Browse on the newly added Media Location entry.  Browse to the location where you extracted the Kernel folder Krnl_7.21_WIN__IA32__IA64__x64__SP11_.  Once you have selected the Kernel folder, click Next./wp-content/uploads/2016/04/d4_992972.png
  7. On the next page, confirm that the hostname is correct and click Next./wp-content/uploads/2016/04/7_920798.png
  8. By default, the agent installs to the C:\ drive.  Change the Destination Drive if you prefer the files to land on a different drive.  Click Next./wp-content/uploads/2016/04/9_920799.png
  9. The installer will create 2 user accounts on the localhost for the agent service accounts.  Click Next./wp-content/uploads/2016/04/10_920828.png
  10. Enter in strong passwords (uppercase and lowercase letters, numbers, special chars etc) for each user account being created by the agent installer/wp-content/uploads/2016/04/11_920834.png
  11. You may receive some warnings about the Operating System Version, it is ok to continue on. Click Next then click No./wp-content/uploads/2016/04/12_920835.png
  12. Next, enter a strong password to use for the new account sapadm and click Next./wp-content/uploads/2016/04/13_920836.png
  13. When prompted if we want to add SAPServiceDAA to the trusted users list, choose Yes./wp-content/uploads/2016/04/15_920837.png
  14. You will be prompted to choose an Instance Number, leave this as the default of instance 98 and click Next./wp-content/uploads/2016/04/16_920838.png
  15. When prompted to Choose the SLD destination, select No SLD Destination and click Next./wp-content/uploads/2016/04/18_920839.png
  16. When prompted for the Connection of the Diagnostics Agent to SAP Solution Manager, choose Do not configure connection then click Next.
  17. On the Unpack Archives screen, click Next.
  18. On the Parameter Summary page, click Next and the install will begin.
  19. Once the installation finishes, you are done installing the Solution Manager Diagnostic Agent.


Continue to part 2:  New complete tutorial for setting up Introscope 9.5 Stand-alone Monitoring for SAP BI Platform 4.x (Part 2)

To report this post you need to login first.


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

  1. David Cartwright

    This is great info, but most of the download links are broken now because of SAP retiring the old download basket. If these could be updated for the support launchpad, that would be super helpful.

    1. Toby Johnston Post author

      Hi Dave,
      Long time no talk!  I updated the broken link.  If you still have trouble it means your S-USER does not belong to an account with rights to download SAP Solution Manager.  This can easily be corrected, just send me an email and provide your customer# or an old incident# associated with your company.



Leave a Reply