Page tree
Skip to end of metadata
Go to start of metadata



SAP Solution Manager 7.1 SP1 supports Oracle WebLogic products with End-to-End Root Cause Analysis. This document describes how to setup and configure E2E RCA in the SAP Solution Manager 7.1 SP1 for Oracle WebLogic Server.

This guide is part of a global installation and configuration documentation. You may find more information in the SAP Service Marketplace -> SAP Components -> SAP Solution Manager -> Release 7.1

Diagnostics architectural overview

This section’s goal is to provide a ‘ten thousand foot view’ over the architecture of E2E RCA in Solution Manager 7.1 and to establish basic terminology.

End-to-End Root Cause Analysis in SAP Solution Manager 7.1 is based on different components listed below.

  • SAP Host Agent
  • Solution Manager Diagnostics Agent
  • SAP Solution Landscape Directory (SLD)
  • Landscape Management (LMDB)
  • Wily Introscope Enterprise Manager
  • Wily Introscope Java Agent
Solution Manager Diagnostics Agent

The Solution Manager Diagnostics Agent (Diagnostics Agent) is the remote component of the E2E Root Cause Analysis. It allows to perform a connection between SAP Solution Manager and the satellite system(s) (WebLogic) and then to gather information from the satellite systems and reports them to the Solution Manager system.

SAP Host Agent

SAP Host Agent can be considered as the component responsible for the monitoring of the host/OS. It is installed on the satellite system (WebLogic host). Depending on the SMD agent version, SAP Host Agent must be installed separately or the ‘built-in’ SMD agent instance is used.

Wily Introscope Enterprise Manager

Wily Introscope is an application management solution created to manage Java Application performance. Introscope has three main components: the Enterprise Manager, the Workstation, and agents.

Wily Introscope Java Agent

The Java Agent is the component of Introscope that collects performance data from your applications running on Java Virtual Machines (JVMs), and sends it to the Introscope Enterprise Manager.

SAP Solution Landscape Directory (SLD)

A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, upgrades, and demands on interfaces. The SAP System Landscape Directory (SLD) is a central repository of system landscape information.

Landscape Management (LMDB)

The Landscape Management Database is the repository of system landscape information in SAP Solution Manager.

Overview E2E RCA setup for Oracle WebLogic Server

The following table lists the steps necessary to set up E2E Root Cause Analysis for an Oracle WebLogic system.

Setup Step

To be performed on


Step1:  Install SAP Host Agent

Managed system (host)

Once per WebLogic host

Step2:  Install SMD Agent

Managed system (host)

Once per WebLogic host

Step3:  Create System in Solman Manually

SAP Solution Manager

Once per WebLogic system

Step4:  Install Introscope Java Agent

Managed system (WebLogic)

Once per WebLogic server

Step5:  Run Managed System Setup

SAP Solution Manager

Once per WebLogic system


This guide is part of a global installation and configuration documentation. It focuses on the actions performed in the Solution Manager (like Managed System Setup).  For other setup steps please refer to following documentation in the SAP Service Marketplace:

1. Install SAP Host Agent

Please refer to SAP Note 1031096 Installing Package SAPHOSTAGENT.
As of version 7.3 the Diagnostics Agent installs SAP Host Agent automatically. Please skip this step if you install the Diagnostics Agent with a recent installer (recommended).

2. Install Diagnostics Agent

Please refer to SAP Note 1365123 Installation of Diagnostics Agents.

3. Create System in Solman Manually

SAP Solution Manager depends on the technical system definition in the Landscape Management (LMDB). The WebLogic Server doesn't have sld data supplier yet, manually create the system in Solman is needed.

  1.  Enter SAP Solution Manager Configuration: Managed Systems Configuration, click System Operation->Create System.
  2. Select system type as "Unspecific Cluster System", click next.
  3. Input the System Name, Type and select the host name.
  4. Set the SID for WebLogic System, SID will be used in wily java introscope setup.
  5. Save and close.
  6. In the Technical System Editor, choose  Step 3 "Define Technical Instances", click Add button to add an instance.
  7. Input the Instance Name, type and host name in the popup dialog, click OK to save. The Instance Name will be needed in wily introscope setup.
  8. Choose Step 4 "Define Assigned Software", click Add button to add product instance.
  9. Select and add product "WEBLOGIC" according to your weblogic version.  
  10. (optional) If you installed BI platform 4.x and select WebLogic as Web Application Server. Input "SBOP BI PLATFORM 4.0" and search, check the installed and diagnostics box of product instance "SBOP BI PLATFORM 4.0: BOE WEB APPLICATION JAVA" .
  11. Select the newly added Product Instance, then check the installed boxes for all software components.
  12. Save and close the Technical System Editor.

4. Install Introscope Java Agent

  1. Download the latest Java Agent installation file from SAP Service Marketplace: -> Support Packages and Patches -> Browse Our Download Catalog--> SAP Technology Components -> SAP SOLUTION MANAGER -> SAP SOLUTION MANAGER 7.1  -> Entry by Component -> Agents for managed systems -> Wily Intro AGT 9 MIN J5 -> # OS independent 
  2.  Edit the IntroscopeAgent_weblogic.profile under the wily folder, usually in usr/sap/ccms/wily/core/config. There are three places need to be modified.
    1. (optional) If you installed BI Platform 4.x and select WebLogic as the Web Application Server, change the directives from "introscope.autoprobe.directivesFile=sap_typical.jar,sap_weblogic_typical.jar,hotdeploy,sap_boenterprise.jar" to "introscope.autoprobe.directivesFile=sap_typical.jar,sap_weblogic_typical.jar,hotdeploy,sap_boe_webapp.jar".
    2. Add your Wily Enterprise Manager host full qualified address, for this example, from "" to "".
    3. Change the Custom Process Name, from "introscope.agent.customProcessName=SAP Netweaver" to "introscope.agent.customProcessName=Weblogic".
      Then save and close the file. 
    4. Always check the note 1565954 for the latest wily agent update.
  3.  Edit the WebLogic Stratup VM parameters. For windows, modify the setDomainEnv.bat under WebLogic bin folder,for example, C:\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.bat. For this example, add one sentence "set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:C:\usr\sap\CCMS\wily\Agent.jar -Dcom.wily.introscope.agentProfile=C:\usr\sap\CCMS\wily\core\config\IntroscopeAgent_weblogic.profile -Dcom.wily.introscope.agent.agentName=WEB_WEBLOGIC" in the end of the file. It contains three VM parameters and you need to change according to your settings.
    • -javaagent:C:\usr\sap\CCMS\wily\Agent.jar (You shall change according to your wily agent installation location)
    • -Dcom.wily.introscope.agentProfile=C:\usr\sap\CCMS\wily\core\config\IntroscopeAgent_weblogic.profile (You shall change according to your weblogic profile's location) 
    • -Dcom.wily.introscope.agent.agentName=WEB_WEBLOGIC (The format is <SID>_<INSTANCE>, you shall change according to your SID and Instance name)
  4. Restart WebLogic Server.

5. Run Managed System Configuration

Managed System Configuration makes your WebLogic system known to the SAP Solution Manager
The Managed System Configuration activity is performed in the SAP Solution Manager Configuration Work Center.

Start the “Managed System Setup” wizard for the IBM WebSphere Application Server system.

  1. Start the Open the Configuration Work Center -> Managed System Configuration -> Technical Systems.
  2. Select the WebLogic system from the list.
  3. Click on "Configure System". "Managed System Setup" wizard will be opened in a separate window.

Perform “Managed System Configuration” wizard

Step 1 Select Product
Just click Edit button into edit mode and click next, because system is already created in LMDB

Step 2 Check Prerequisites
Click "Execute All" button and check the results. "Managed system XXX fulfills Diagnostics prerequisites" must be green. "Solution manager does not fulfills Diagnostics prerequisites" means the solman needs upgrade for some components, click Details button to see the root cause. In the example, the solman is not up to date but it isn't a big problem.

Step 3 Assign Diagnostics Agent
If a diagnostics agent is installed on the WebLogic host and already assigned to this solman in the installation qart, then click "Assign" button to find and assign it. Else, click "SLD Agent Candidates" tab to connect a agent installed on the same host. The connect process may take several minutes. Finally, Step 3 must be green.

Step 4 Enter System Parameters
Select the Introscope EM and input the hostname and port of the WebLogic server. Click Save and Next.

  • "Introscope EM" - the Introscope Enterprise Manager’s host and port to which Wily Java Agent on the WebLogic server reports to.
  • "Integrated Solutions Console Host" – the host name there the WebLogic's Admin UI (Administration Console) is installed
  • "Integrated Solutions Console Port" – the WebLogic's Admin UI Https port.
  • "HTTPs" checkbox – whether HTTPS protocol should be used
    Step 5 Enter Landscape Parameters
    Enter the installation path for WebLogic Instance. Save and Next.

    Step 6 Configure Automatically
    Click "Execute All" button, after the job execution, check the result, especially on "Extractors Setup" and "Introscope Host Setup", these two are important and must be green.

    Step 7 Configure Manually
    Skip this step.
    Step 8 Create Logical Components
    It shall be green already, click Next.

    Step 9 Check Configuration
    Click "Execute All". Check the result, if everything is right, it shall be green and click Next. Otherwise check the detail to see which step is wrong previously.

    Step 10 Complete
    Click "Finish" and complete the managed system setup.

Additional information



SAP Solution Manager Setup Wiki

Root Cause Analysis Wiki > SAP Components > SAP Solution Manager > Release 7.1 

Solution Manager Installation Guides

  • No labels


  1. Dear author

    while the guide is quite clear it does not show how to manually create the product instances. If you do not know how you are blocked. I would recommend update the guide to at least explain. 

    Otherwise it very clear and well written

    thank you



      well, how to create product instance is described in step 8 and 9... not quite sure about your question..

  2. Hello Kobe

    Thanks for getting back to us. However it does not show you how to create the product instance it shows how to add them if they are already there. The WEBLOGIC product instances are not there magically. You can see that they are manually created as they are not part of the CR content and also there is no SLD registration for weblogic. If you search for these product instances in the LMDB they are not there. Looking at the screenshot you can see that are manually created. 



    1. Hello David,


      The whole chapter 3 tells you how to create weblogic product manually in solution manager. Since we don't have any data supplier for weblogic, we will not have weblogic in SLD.

      We define the weblogic as unspecific cluster system in solman, and add the product instance manually. if you mean we can't find or select weblogic in step3.9, please update your solman CR content. if you still don't understand, maybe we could have a meeting i will show you.


      Best Regards,


  3. Former Member


    Can I use the same zip file:  for Wily Introscope Agent 9? Or should I use different zip file? If yes, please let me know which oss notes containing that zip file. Your help is greatly appreciated.


    Christina Halim