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

General

The monitoring metrics that are collected by the Diagnostics Agents are sent to the SAP Solution Manager thought the DPC Push. The metrics are collected by the Diagnostics Agents and then pushed to the Solution Manager thought the web service E2E_DPC_PUSH. The default URL of the web service is:

  • http://<solman_host>:<abap_icm_port>/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=<XXX>

The E2E_DPC_PUSH is a web service exposed by the Solution Manager ABAP, the service definition of the system can be found in transaction SOAMANAGER.

The monitoring metrics are collected by the Data Providers in the Diagnostics Agents, these data providers are part of the Diagnostics Agent application com.sap.smd.agent.application.e2emai. The  metrics are triggered regularly according to the period configured in the monitoring templates and then pushed to E2E_DPC_PUSH web service. The user SM_EXTERN_WS created during the first steps of the Solution Manager setup (transaction SOLMAN_SETUP) is used by the Diagnostics Agents to call the web service. The following picture provides an overview of the service architecture.

Configuration

Web Service Basic Configuration

The E2E_DPC_PUSH web service in the Solution Manager ABAP is created by activity 'Create Logical Ports' in the Solution Manager setup. The activity can be found as follows depending the Solution Manager release.

  • Solution Manager 7.20
    • SOLMAN_SETUP → Infrastructure Preparation → Step Enable Connectivity → Activity 'Create Logical Ports'
  • Solution Manager 7.10
    • SOLMAN_SETUP → System Preparation → Enable Web Services → Activity 'Create Logical Ports'

N.B.: If an SAP Web Dispatcher is configured in the SAP Solution Manager, the E2E_DPC_PUSH is also configured with the host and port of the web dispatcher by the activity 'Create Logical Ports'.

The configuration of the E2E_DPC_PUSH is sent to the Diagnostics Agents when activity 'Basic DPC Push Configuration' is performed. The activity can be found as follows depending the Solution Manager release.

  • Solution Manager 7.20
    • SOLMAN_SETUP → Basic Configuration → Step Configure Basic Functions → Activity 'Monitoring - Basic DPC Configuration'
  • Solution Manager 7.10
    • SOLMAN_SETUP → System Preparation → Step Configure Automatically → Activity 'Basic DPC Configuration'

The activity 'Basic DPC Push Configuration' configures the Diagnostics Agents with the user, password and URL that needs to be used to call the web service. The properties 'dcc.url', 'dpc.url', 'e2e.mai.password' and 'e2e.mai.user' are configured in the SMDAgent application 'com.sap.smd.agent.application.global.configuration' by that activity. The following picture shows how to find these settings in the Agent Admininistation:

Metrics Configuration of the Diagnostics Agents

When a monitoring scenario that contains a metric (collected by a Diagnostics Agent's data provider) is activated, the metrics to be collected and pushed are defined in the file MetricCollectionDefinition.xml of the related Diagnostics Agent. The file can be accessed as follows:

  • Access the Agent Administration (http://<solman_host>:<java_http_port>/smd/AgentAdmin).
  • Open Application Configuration tab.
  • Select the application 'com.sap.smd.agent.application.e2emai'.
  • Expand the Application Resources.
  • Select 'MAI/MetricCollectionDefinition.xml'.
  • Select the desired Diagnostics Agent via 'Select an Agent'.

The file MetricCollectionDefinition.xml is independent on the Diagnostics Agent, i.e. it is important to always select a Diagnostics Agent in the scope. Furthermore, ensure to not use the file 'MAI/ISMetricCollectionDefinition.xml' which contains the metrics that are pushed by the Introscope Enterprise Manager.

Runtime Status

To check if the DPC Push Service is being performed correctly by the Diagnostics Agent, check the Alerting Framework. The Alerting Framework shows the status of the push performed by the Diagnostics Agents in the same way the standard extractor information is shown. The steps to access the Alerting Framework are as follows:

  • Solution Manager 7.20
    • Transaction SM_WORKCENTER → SAP Solution Manager Administration → Extractors Alerting Administration
  • Solution Manager 7.10
    • Transaction SM_WORKCENTER → SAP Solution Manager Administration → Infrastructure → Framework → Alerting Framework

In the Alerting Framework, check the extractor entries with the name 'DPC PUSH CORE'. Also, in the 'Extended Context' column, filter for the dedicated Diagnostics Agents. The following picture shows an example of the Alerting Framework and the DPC PUSH CORE of four SMDAgents in the Alerting Framework:

Runtime Log

The most releant log information about the monitoring data providers and the DPC Push performed by the Diagnostics Agents can be fouind in the following files:

  • e2emai.log
  • e2emai_saphostcontrol.log
  • e2emai_push_rfc.log

These files are located in the 'log' folder of the Diagnostics Agent:

  • <drive>\usr\sap\<SID>\SMDA<XX>\SMDAgent\log\

The Diagnostics Agent logs can be downloaded from the Agent Administration as described at KBA 2455767.

Troubleshooting

Error 'Configuration XML 7.01.02.<timestamp> likely did not reach the agent . Agent XML: 7.01.02.<timestamp>' in the 'Check Data Collection'

In the System Monitoring or other monitoring applications in the Solution Manager, a metric that is collected by a Diagnostics Agent is gray. In the 'Check Data Collection' feature of the monitoring application, the following error is shown:

Configuration XML 7.01.02.<timestamp> likely did not reach the agent . Agent XML: 7.01.02.<timestamp>
No values reported: data provider GetProcessList, data provider type PUSH_GENERIC
Last measured value was calculated at <date> on <hour>.

The picture below shows the error in the 'Check Data Collection':

Resolution

First of all, check whether the MetricCollectionDefinition.xml has been correctly delivered to the Diagnostics Agent. The error message contains the expected version that needs to be available in the Diagnostics Agent. The steps to check the file are:

  • Access the Agent Administration (http://<solman_host>:<java_http_port>/smd/AgentAdmin).
  • Open the Application Configuration tab.
  • Select application 'com.sap.smd.agent.application.e2emai.
  • Expand the Application Resources.
  • Select 'MAI/MetricCollectionDefinition.xml'.
  • Select a dedicated DIagnostics Agent via 'Select an Agent'.

Compare the version shown in the first line of the XML downloaded using steps above with the version mentioned in the error message. The picture below shows the comparison:

The version shown in the 'Check Data Collection' must be equal to the version of the MetricCollectionDefinition.xml file. The version contains the timestamp of the last XML generation.

  • If the version in the XML file of the Diagnostics Agent does not match the version shown in the error message, check the following:
    • Repeat the monitoring activation and the search for errors in the application log (Tx SLG1) for Object E2E_ALERTING / SubObject DPC_SETUP.

Known bugs related to the XML generation in the DIagnostics Agent are described in the notes below:

2057141 - Error "Configuration XML likely did not reach the agent" with Grey Metrics in Technical Monitoring

2142276 - Grey Metrics in System Monitoring after Agent JVM upgrade
2086000 - Wrong status for Agent Configuration XML Version in Self-Monitoring Overview UI
  • If the version in the XML file of the error message and the file in the Diagnostics Agent are equal, the Diagnostics Agent could not call the E2E_DPC_PUSH web service successfully after the latest XML generation. In this case, check the Diagnostics Agent log file e2email.log and search for errors related to the DPC Push URL:
    • http://<host>:<port>/sap/bc/srt/scs/sap/e2e_dpc_push?sap-client=<XXX>

Examples of the error messages regarding the call of the E2E_DPC_PUSH web service found in log e2email.log are as follows:

Error 1:

[Thread[ExRun:dpc:job_2,5,dpc:job:ExecTG]] Error [DPCServicePushMetricJob.pushSimpleEvents] Error occurred when calling the DPC Push web service.         
Caused by: javax.xml.ws.soap.SOAPFaultException: Permission denied
Caused by: com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 401: Unauthorized

Solution: Refer to KBA 2610006 

Error 2:

Nov 2, 2017 5:48:33 AM [Thread[ExRun:dpc:job_2,5,dpc:job:ExecTG]] Error      [MAIMetricProvider.pushFailed] MAI metric push failed (Exception occurred) with status: DPC_RT_STATUS_ERROR [EXCEPTION] java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy59.e2EDpcPushMetrics(Unknown Source)
at com.sap.smd.dpc.job.DPCServicePushMetricJob.pushSimpleEvents(DPCServicePushMetricJob.java:132)
Caused by: java.lang.reflect.InvocationTargetException
Caused by: com.sun.xml.internal.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html Supported ones are: [application/soap+xml]

Solution: Refer to KBA 2566012

Error 3:

[Thread[ExRun:dpc:job_2,5,dpc:job:ExecTG]] Error [DPCServicePushMetricJob.pushSimpleEvents] Error occurred when calling the DPC Push web service.           [EXCEPTION] java.rmi.RemoteException: Service call exception; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.

Solution: Refer to KBA 1855064 

Error 4:

[MAIMetricProvider.PushFailed] MAI metric push failed with status: DPC_RT_STATUS_ERROR, [DPCServicePushMetricJob.pushSimpleEvents] DPC Web Service call FAILED for metric provider 'MAI_METRIC_PUSH_JOB' with status 99, message: Missing Consumer:  Metric(s) have been rejected, mechanism type: null

Solution: Refer to KBA 2236334

Error 5:

[DPCService.initWSConnection] Error occurred when initializing DPC Web Service client. DPCService is DISABLED. [EXCEPTION] java.rmi.RemoteException: [WSConnectorFactory] DPC url not found in global repository

 Solution: Refer to KBA 2566991

Error 6:

The Self-Monitoring sporadically shows error 'Configuration XML <version> likely did not reach the agent <agent_name>. Agent XML <version>' for some diagnostics agents. This might indicate a timeout in the web services used for the XML configuration.

 Solution: Refer to KBA 2569279

 

 

 

 

 

  • No labels