Solution Manager Diagnostic agent (SMD)

[Former Member]

I hope this isn't too stupid a question but I'm having problems finding the answer. Am I right in thinking that the solman diagnostic agent is for ABAP and java systems and can be installed on systems that are ABAP only for diagnostics or is it just for java?

Edited by: Chris Soden on Jul 30, 2009 9:28 AM

[Former Member]

My understanding is that Solution Manager Diagnostics is for Java apps. However in Solution Manager 7 E2E Root Cause Analysis combines both Java and ABAP analysis tools so thinkgs like thread dump analysis, wily introscope workstation are java stuff whilst work load analysys tools such as SM35, SM50, SM66, some ST0* help in workload and trace analysis on the ABAP side

hope this helps

[prakhar_saxena]

Thanks.

In addition to above

https://websmp105.sap-ag.de/~sapdownload/011000358700000737542007E/#A5

Does SAP recommend to use End-to-End Root Cause Analysis also if the customer is using SAP solutions based on Web AS ABAP only?

Up to SAP Solution Manager 7.0 SP9, the main use case of Root Cause Analysis scenario of SAP Solution Manager was non-ABAP support. However as of SAP Solution Manager 7.0 SP10, End-to-End Root Cause Analysis also brings benefit to the table for all web based scenarios that run purely on Web AS such as application written in WebDynpro for ABAP or Business Server Pages (e.g. CRM Customer Interaction Center).

Hope ur problem is completely resolved now.

Regards

Prakhar

[prakhar_saxena]

Hi,

You can monitor Java components of your solutions, with Solution Manager Diagnostics. The SAP Solution Manager passes the solution data to the Solution Manager Diagnostics.

http://help.sap.com/saphelp_sm40/helpdata/en/43/259ae072634e86e10000000a422035/content.htm

Check these links..

How to perform a complete HTTP trace for SAP Enterprise Portal application? Try SAP Solution Manager Diagnostics

/people/zhaogang.li/blog/2005/08/29/how-to-perform-a-complete-http-trace-for-sap-enterprise-portal-application-try-sap-solution-manager-diagnostics

You need to config solman diagnostics.....

https://websmp105.sap-ag.de/diagnostics

http://help.sap.com/saphelp_nw04/helpdata/en/2c/525e3c1852d733e10000000a114084/frameset.htm

/people/luisfelipe.lanz/blog/2006/02/07/installing-a-solution-manager-diagnostics-the-easy-way

Root Cause Analysis for SAP MDM 5.5 SP06 with SAP Solution Manager Diagnostics

/people/detlef.thoms/blog/2008/04/15/root-cause-analysis-for-sap-mdm-55-sp06-with-sap-solution-manager-diagnostics

Hope it solves ur query

Regards

Prakhar

[Former Member]

So its not used for ABAP only systems?

[Former Member]

Hi Chris,

SMD is not used for ABAP only systems.Among other things SMD is used to generate EarlyWatch Alerts for Java systems.

Please visit the links mentioned by Prakhar to get more info.

Thanks,

Shashank

[prakhar_saxena]

Hi

SMD is a tool used for Root cause analysis and perform more than normal root cause analysis or actually pro-active monitoring part.

so inshort it is used for both ABAP & JAVA because ur gng for end to end root cause analysis.

Check the link & Q11

Customers that just run an ABAP stack and access it via SAPGUI can still be supported not leveraging End-to-End Root Cause Analysis capabilities. However with use of alternative type of accesses such as Web Access, access through mobile devices or office clients (Duet) or with using other server technology than Web AS ABAP, End-to-End Root Cause Analysis is key for efficient support. End-to-End Root Cause Analysis is a new level of diagnostics which aims at isolating a problematic component in a distributed heterogeneous customer landscape. It does not replace the component diagnostics on Web AS ABAP or Java, but complements them by providing capabilities to provide a systematic top down u201Ccriminal searchu201D. End-to-End Root Cause Analysis is provided through SAP Solution Manager while component root cause analysis is still available out of the box with the installation of the component.

https://websmp105.sap-ag.de/~sapdownload/011000358700000737542007E/#A3

Is there a difference between Diagnostics and Root Cause Analysis?

Diagnostics is more than Root Cause Analysis. It also includes Proactive Monitoring and Alerting (both on system and business process level) as well as Service Level Reporting (meaning all aspects of IT analytics). Root Cause Analysis provides the basis of data for Alerting and Service Level Reporting. Once Root Cause Analysis is setup, the next natural step of Diagnostics adoption is Proactive Monitoring and Alerting as well as Service Level Reporting. Proactive Monitoring refers both to System Monitoring and Business Process Monitoring.

Hope it helps

Regards

Prakhar