Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

CA Introscope integration to SAP FRUN

Running the Simple System Integration (SSI) for the CA Introscope Enterprise Manager the file

<EM_HOME>/sap/<FRUN_SID>_srsm.e2emai.properties has to be created to enable the Introscope Push service (see SAP Note 1751225).

Accordingly the user sapadm running the Diagnostics Agent assigned to the Enterprise Manager host has to have read/write permissions to the above listed folder.

 

Since FRUN does not yet support an Introscope EM cluster a workaround must be applied to connect a MoM as a "faked" Standalone EM to Focused Run. To do so the property com.sap.sldds.override.type=EnterpriseManager has to be added in file <EM_HOME>/config/IntroscopeEnterpriseManager.properties. As a result the MoM appears as Standalone EM in LMDB,

.

 

CA Introscope integration to SAP Solution Manager

This page summarizes information on CA Introscope setup steps within Solution Manager.

You may also see for information about CA Introscope.

 

Solution Manager Basic Configuration => Configure CA Introscope

In this Solution Manager setup step, you connect existing CA Introscope Enterprise Managers to SAP Solution Manager.

When discovering EMs these are made known to Solution Manager.

For this setup action some files of Enterprise Manager have to be read:

  • <EM_HOME>/Introscope_Enterprise_Manager.lax
  • <EM_HOME>/config/IntroscopeEnterpriseManager.properties
  • <EM_HOME>/config/users.xml
  • <EM_HOME>/config/domains.xml
  • <EM_HOME>/product/enterprisemanager/plugins/com.wily.introscope.em_<version>.jar
  • <EM_HOME>/bin/EMService.conf (Windows only)

Also some files of the Enterprise Manager get edited by different Solution Manager setup steps:

  • <EM_HOME>/config/IntroscopeEnterpriseManager.properties (Basic Configuration => Configure CA Introscope => Discover Introscope EM)
  • <EM_HOME>/config/users.xml (Basic Configuration => Configure CA Introscope => User Management)
  • <EM_HOME>/config/domains.xml (Basic Configuration => Configure CA Introscope => User Management)
  • <EM_HOME>/sap/<SolMan_SID>.e2emai.properties (Basic Configuration => Configure Automatically => Push DPC Configuration to CA Introscope)
  • <EM_HOME>/config/agentcluster.xml (Managed Systems Configuration => Configure Automatically => Generate System-level Metrics)

Accordingly the user running the Diagnostics Agent assigned to the Enterprise Manager host has to have read/write permissons to the above listed folders and files.

Basic Configuration => Configure Automatically => Push DPC Configuration to CA Introscope

In this automatic activity, you send the Data Provider Connector configuration to the CA Introscope Enterprise Managers. This information is required to enable CA Introscope Enterprise Managers to send data via the DPC push functionality to the SAP Solution Manager system. In other words the Enterprise Manger then knows to which Solution Manager(s) it has to send metrics to Monitoring and Alerting Infrastructure.

You may also see SAP Note  1751225 Introscope Push.

If the Diagnostics Agent assigned to the Enterprise Manager host got changed this activity has to be executed again.

 

Managed Systems Configuration => Enter System Parameters => Common Parameters

In this step you can choose the Enterprise Manager which will be used by the managed system agents to report performance data.

The Enterprise Managers of type MoM (Manager of Managers) and Standalone are available to be chosen. The Enterprise Managers defined as Collectors will not be shown in this step. If a MoM scenario is configured, it is required to choose the MoM EM. In this case, the agents will connect firstly to the MoM EM and then they will be automatically redirected to a collector node.

 

Managed Systems Configuration => Configure Automatically => Generate System-level Metrics

In this automatic activity, you enable CA Introscope Enterprise Manager to aggregate performance metrics on system and instance level. System and instance level aggregates of selected metrics are used in system monitoring.

Introscope agents report metrics per Java node to the Enterprise Manager. By adapting the agentclusters.xml file, the Enterprise Manager is enabled to build instance and system level aggregates for selected metrics.

  • No labels

4 Comments

  1. Former Member

    Hi Jens,

     

    Thanks for this good blog.

     

    In our environment, we have 1 EM MOM and 2 EM collectors running on a seperate hosts. The solution manager instance is running on a separate box altogether. Now, we want to integrate Solman with EM.

    Could you please give us some insight regarding the steps that we need to follow to achieve it.

     

    Regards,

    Aniket

  2. Dear Aniket

    It`s actually the other way around. You integrate EM(s) into SolMan. How to do that is explained in the setup step itself. For an EM cluster you start with the MoM and afterwards discover the collectors.

    Regards

    Juergen

  3. Former Member

    Hi,

    we had some undiscovered performance issues on the wily, and this gave us a really hard time until we discovered, that wily EM was the root cause of all our problems throughout the landscape.

    IMHO there should be a) a managed System setup for the Wily Introscope EM and b) a technical Monitoring for the Application Wily Introscope.

    But I can't find neither a) nor templates for b) in technical monitoring.

     

    SAP is pushing the Solution Manager as a central monitoring tool for any SAP landscape, and there are some poor guys outside who really believe in this SAP setup. But IMHO all this will fail if there is no monitoring for wily introscope that should gather all the performance data.

    Any objections? Are there any tools to monitor the logfile and trigger ALERTS inside Technical monitoring when there are Memory problems or warnings/errors inside the logfiles?

     

  4. Hi Ralf,

    thanks for your input. In general I do not understand how the "Introscope EM could be the root cause for all problems throughout your landscape". Only Solution Manager is consuming data from Introscope, so I would expect that only Solution Manager applications are impacted by any Introscope EM Problems - probably mainly System Monitoring.

    You are right: There must be monitoring of the Introscope EM and also alerting about problems - simply because Introscope is part of the monitoring infrastructure. And fortunately this is available: All Enterprise Managers connected to a Solution Manager via the "Configure CA Introscope" step mentioned above are automatically registered to Solution Manager Self Monitoring. In the Self Monitoring application (work center "Solution Manager Administration" -> self Monitoring) then contains a node for every Enterprise Manager. For each of the EMs we Monitor

    • EM availability (via URL ping to the /webview application)
    • EM Overall Performance (by looking at the central KPI "Overall Capacity (%)")

    If any of these metrics indicate problems you should get an alert. For example, Memory Problems contribute to the "Overall Capacity" KPI and thus should trigger an alert.

    If I understand correctly the templates for self monitoring are more or less hardwired, so it is not easily possible to adjust the template for Introscope EM, e.g. by adding log file monitoring. I personally also have doubts that it is a good approach to report any ERROR / WARN entry from the EM logs - this would be too much "noise" of minor things that you do not want to care about. What do you have in mind as log file filter?

    If there is more to discuss you are also welcome to open a ticket on component SV-SMG-DIA-WLY-EM. I might be the one taking it (smile)

    regards

    Jens Claussen