Diagnostics Agent 7.11 vs SMD Agent 7.00

Hello,
In our SAP System environment, most of managed systems are running under SAP NW 7.0 platform.
We are currently installing SMD Agent 7.00. The installation is not finished and I was wondering if we can install Diagnostics Agent 7.11 on managed systems running on SAP NW 7.0 ?
In other terms :
SMD Agent 7.00 have to be installed only on SAP NW 7.00
Diagnostics Agents 7.11 have to be installed only on SAP NW 7.11 or also on SAP NW 7.00 ?
Thanks in advance for your feedback
Best regards
P. Cuennet

Yes you can install diagnostics agent 7.11 for a managed system 7.00
It's even possible for a managed system 6.40
Prerequisite is that your Solution Manager stack verison is 20 or higher (EHP1)
You can find the details in the installation guide for diagnostics agent 7.11 on SAP service marketplace:
[https://service.sap.com/diagnostics]

Similar Messages

  • Error in SMD Agent

    Hello All,
    In order to install Wily Introscope Agent, initially I have installed
    a SMD Agent on managed system host.
    After the installtion of SMD Agent , while starting the SMD agent I am getting below error .
    Starting SMDAgent ...
    Establishing connection to server '[host is empty]' on port [port is
    empty]
    Smd connector is disabled because no SLD association and no credentials
    found.
    Smd connector is disabled because no SLD association and no credentials
    found.
    Waiting for connection ...
    Checking server availability...
    Warning :
    Connecting to SMD server null failed - error counter: 0 -
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: No
    InitialContext can be created because the java.naming.provider.url
    property is no specified in the jndi environment.
    Next try to push instance data in SLD is Tue May 19 14:36:31 CDT 2009
    I have given user SLDAPIUSER in SLDAPICUST transaction. This user
    which is not locked and I have also reconfirmed the password of this
    user.
    Kindly request your suggestion!!!!
    Regards,
    Suhas

    Santosh Asuthkar 
    I am receiving the same error in my SMD agent log:
    Starting SMDAgent ...
    Dec 8, 2009 1:43:48 PM [Thread[main,5,main]] Info       Establishing connection to server '[host is empty]' on port [port is empty]
    Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info       Smd connector is disabled because no SLD association and no cred
    entials found.
    Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info       Smd connector is disabled because no SLD association and no cred
    entials found.
    Dec 8, 2009 1:43:51 PM [Thread[SMDAgent connection thread,5,main]] Info       [null] Waiting for connection ...
    Dec 8, 2009 1:43:52 PM [Thread[SMDAgent connection thread,5,main]] Info       [null] Checking server availability...
    Dec 8, 2009 1:43:53 PM [Thread[SMDAgent connection thread,5,main]] Warning    Connecting to SMD server null failed - error counter: 0 - com.sa
    p.engine.services.jndi.persistent.exceptions.NamingException: No InitialContext can be created because the java.naming.provider.url property i
    s no specified in the jndi environment.
    Dec 8, 2009 1:43:54 PM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is  Wed Dec 09 01:43:54 EST
    2009
    Dec 8, 2009 1:46:52 PM [Thread[SLD-AssocWatcher,1,main]] Info       [SLDManagingConnectionMonitor] Next time to check Managing System Associat
    ion is  Tue Dec 08 14:01:52 EST 2009
    Can you please provide details if you found a solution?
    Thanks!!!!!
    Jeff

  • Not able to find SMD Agent in SMP

    Hi,
    I need to install SMD agent in all the NW2004s servers, but i am not able to find the SMD agent for NW2004s in Service Market Place.
    SMD agent is not available in the below mentioned path:
    service.sap.com/swdc --> Download --> Support Packages and
    Patches --> Entry by Application Group -> SAP Technology Components --> SAP
    SOLUTION MANAGER --> SOLUTION MANAGER 4.0 --> Entry by Component -->
    Agents for Satellite Systems --> SMD AGENT 7.00 --> <choose OS>
    Regards,
    Ranjith

    Hi Shyam,
    Thanks for your reply.
    I already tried downloading the SMD Agent from the OS independent, but after extracting the SAR file, i am unable to see the sapinst in it.
    I have all the monitored systems of version NW2004s SR1/SR2, in this version of installation master, will i be able to install the SMD agent?
    Regards,
    Ranjith

  • SMD Agent application - Explanation

    Hello,
    I have installed SMD. By startind "Agent Administration" from SMD, I get the application list of SMD Agent.
    I am editing a guide to explain each application of this SAP SMD Agent. I get an explanation for 10 of 22 applications.
    But I miss details regarding the other ones :
    Do you have any help or guide which explain me what these SMD applications are used for ?
    1. com.sap.smd.agent.application.e2emai
    2. com.sap.smd.agent.application.eem
    3. com.sap.smd.agent.application.flightrecorderdumpscan
    4. com.sap.smd.agent.application.navigation.links
    5. com.sap.smd.agent.application.remoteos
    6. com.sap.smd.agent.application.runtime
    7. com.sap.smd.agent.application.tracing
    8. com.sap.smd.agent.application.wily
    9. com.sap.smd.agent.application.wily4duet
    10. com.sap.smd.agent.application.wily4java
    11. com.sap.smd.agent.application.wilyem
    12. com.sap.smd.agent.application.wsclient
    Thanks
    Best regards
    PC

    Hello,
    I have finally foudn an explanation for each SMD Agent application :
    1 .com.sap.smd.agent.application.connectors
        Provide P4 or JMX connection to the monitored SAP J2EE engine.
    2. com.sap.smd.agent.application.database
    Access to the DB of the remote system to return table information to the SMD SQL Command Console application.
    3. com.sap.smd.agent.application.datacollector
    Collects XML based data from monitored systems (replaces the tool u201CComponent Analyzeru201D download feature)
    4. com.sap.smd.agent.application.filesystem
    Provides access to the remote file system for the u201CSMD File System Browser applicationu201D, and the Gather/Upload functionality.
    5. com.sap.smd.agent.application.global.configuration
    Global configuration of the SMD Agents.
    6. com.sap.smd.agent.application.ldap
    Provides remote access to connect to a LDAP server for the SMD LDAP browser application.
    7. com.sap.smd.agent.application.logviewer
    Provides an access to the file system of a monitored system. Files can be displayed or downloaded.
    8. com.sap.smd.agent.application.remoteos
    Enables to start remote OS commands console.
    9. com.sap.smd.agent.application.remotesetup
    Enables to setup the J2EE engine of a monitored system for SMD usage, from the smd/admin application.
    10. com.sap.smd.agent.application.telnet
    Provides remote access to the J2EE telnet console for the SMD J2EE command console application.
    11. com.sap.smd.agent.application.tracing
    It is used by the application E2E Trace Analysis (tools of RCA).
    12. com.sap.smd.agent.application.wily
    It is used by the application Introscope Setup.
    13. com.sap.smd.agent.application.wily4duet
    It is used by the application Introscope Setup for managed system running on duet.
    14. com.sap.smd.agent.application.wily4java
    It is used by the application Introscope Setup for managed system running on java.
    15. com.sap.smd.agent.application.wilyem
    It is used to store the data about Introscope Enterprise Manager (EM) for SMD.
    16. com.sap.smd.agent.application.wilyhost
    A: The agent application "com.sap.smd.agent.application.wilyhost" contains the HostAgent.
    HostAgent = Host-Level Introscope Agent.
    The following SMD Agent applications are not for a specific application but for the
    general runtime of Root Cause Analysis :
    - com.sap.smd.agent.application.e2emai
    - com.sap.smd.agent.application.eem
    - com.sap.smd.agent.application.wsclient
    - com.sap.smd.agent.application.flightrecorderdumpscan
    - com.sap.smd.agent.application.runtime
    - com.sap.smd.agent.application.navigation.links
    Best regards
    PCuennet

  • SMD Agent 7.00 or Diagnostics Agent 7.11

    Hello,
    Our managed systems are running on NetWeaver 7.00.
    We are currently implementing SAP Solution Manager Diagnostics using SOLMAN_SETUP guided procedure.
    In https://service.sap.com/swdc -
    Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" Entry by Component" Agents for managed
    there are 2 kinds of Diagnostcis Agents :
    1. SMD Agent 7.00
    2. Diagnostics Agent 7.11
    Question :
    Can we install a Diagnostic Agent 7.11 on our managed systems running on NetWeaver 7.00 or must we install SMD Agent 7.00 ?
    Are Diagnostics Agent 7.11 supported for managed systems running on NW 7.00 ?
    Best regards
    PC

    Hi
    To avoid libraries conflicts it is highly recommended to install a Diagnostics agent which has the same kernel release
    that the SAP systems already installed on the host.
    Refer the doc in this [link|https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_HIER_KEY=701100035871000526434&_OBJECT=002007974700000409092009E&_SCENARIO=01100035870000000112&]  Section 2.3 Managed system page no:8
    Hope this helps you
    regards
    Naveen

  • Solution Manger Diagnostics setup (SMD Agent)

    Hi All
    I have managed to setup Solution Manager Diagnostics and Deploy on of the agents to out DEV BI Server (JAVA), however I keep getting the message:
         "Failed to connect to server: bidevdb - Please make sure SMD Agent is up and running"
    Now I can see in the SAPMSC that the SMD agent is running - so I am not sure why this is the case. Does SMD require SAPCCMS setup as a windoes service on the BI Server?
    Or what else can I check to find out what the issue might be?
    Thanks all in advance (will award points for helpfull answers)

    SMDSystem.x.log
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[SMDSystemLog]/>
    <!PATTERN[SMDSystem.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
    <!ENCODING[Cp1252]/>
    <!FILESET[0, 10, 1000000]/>
    <!PREVIOUSFILE[SMDSystem.9.log]/>
    <!NEXTFILE[SMDSystem.1.log]/>
    <!LOGHEADER[END]/>
    Mar 25, 2010 2:23:08 PM [Thread[main,5,main]] Info       Starting SMDAgent ...
    Mar 25, 2010 2:23:09 PM [Thread[main,5,main]] Info       ===> Establishing connection to server '[host is empty]' on port [port is empty]
    Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
    Mar 25, 2010 2:23:11 PM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
    Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Error      Cannot retrieve saposcol hardware info for SLD data instance.
    [EXCEPTION]
    java.io.IOException: CreateProcess: ..\..\exe\saposcol -b error=2
         at java.lang.ProcessImpl.create(Native Method)
         at java.lang.ProcessImpl.<init>(ProcessImpl.java:85)
         at java.lang.ProcessImpl.start(ProcessImpl.java:30)
         at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
         at java.lang.Runtime.exec(Runtime.java:591)
         at java.lang.Runtime.exec(Runtime.java:429)
         at java.lang.Runtime.exec(Runtime.java:326)
         at com.sap.smd.agent.util.RunExec.exec(RunExec.java:78)
         at com.sap.smd.agent.util.RunExec.exec(RunExec.java:55)
         at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:158)
         at com.sap.smd.agent.util.RunExec.execAndWaitFor(RunExec.java:148)
         at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.getSAPOSColHostInfo(SLDAgentDataBuilder.java:254)
         at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addAgentHostMember(SLDAgentDataBuilder.java:195)
         at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addGroupAgentInstance(SLDAgentDataBuilder.java:132)
         at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.addSLDInfoNodeForAgentRegistration(SLDAgentDataBuilder.java:498)
         at com.sap.smd.agent.connection.sld.SLDAgentDataBuilder.writeAgentInstanceData(SLDAgentDataBuilder.java:597)
         at com.sap.smd.agent.connection.sld.SLDQueryBuilder.registerAgentInstanceData(SLDQueryBuilder.java:604)
         at com.sap.smd.agent.connection.sld.process.SLDReg.run(SLDReg.java:68)
         at java.lang.Thread.run(Thread.java:664)
    Mar 25, 2010 2:23:12 PM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is  Fri Mar 26 02:23:12 GMT 2010
    Could not find the SMDAgentApplication.X.log
    Does that help?

  • Diagnostics - How to patch SMD Agent

    Dear SAP Colleague,
    I will have to install the SMD Agent on all managed system of my SAP landscape.
    Do you know how this agent is patched ?
    I know that both Wily IS Agent (Introscope Java Agent) and Host-level Introscope Agent) are updated from SAP Solution Manager and deployed to all managed systems.
    But how do we patch the SMD Agent (Java instance) ?
    Thanks
    Best regards
    P.C.

    Hello folks,
    Was wondering too if any way to update / patch SMD Host Agentu2019s executable.
    I could not find any SAP document on that.
    Checking our own AIX kernel  that  came with the install e.g. u201Cjstart u2013Vu201D, I saw that the patch # was 37, in the context of kernel 7.11_REL UNICODE, compile time Jun 6 2009.  It to be noticed that in the exe directory there are just some of the u201Cfullu201D kernel folders present (it makes sense, because it is just a Java env.).. In my case there are 79 u201Cfoldersu201D in the exe dir. Please note that one of it, u201Cservicehttpu201D is a directory.
    Thus, my thoughts on a potential way to patch the SMD Host Agent SAP Kernel is to apply that pool of kernel components that matches the SMD Agentu2019s executables.
    Thus, first  download the kernel 7.11 latest patches e.g. from (Entry by Application Group -> Additional Components -> SAP Kernel -> SAP Kernel 64 BIT UNICODE -> SAP Kernel 7.11 64 BIT UNICODE , then uncar these  and rm a script that will copy only the folders  that are present in the installed exe SMD Host Agent exe dir as well. Also, is should be checked to that all the files in the SMD Agent should be part of the updated kernel. If not, then I will not recommend to do it, since SAP may have something special for the SMD SAP Kernel.
    Have not tried yet to perform this procedure, but is very tempting, since for 7.11 AIX the default install is at patch level 37 while today the corresponding 7.11 patch level is 92.
    Please, note that this is just a personal look at this issue and absolute not a SAP recommendation. Maybe the fist question should be u201Cwhatu2019s the need for the SAP SMD Agent u201CSAP Kernel Upgradeu201D?  The more correct and recommended way will be to open a customer message with SAP, e.g. asking to u201Cblessu201D the SMD Agent Kernel upgrade procedure described above.
    Kind regards,
    C.P.

  • SMD agent passowrd issue

    Hi Experts,
                      In our solution manger system, we forgot the SMD agent password. without i can't able to do EWA for java stack. So kindly help me to how to reset the password for this.
    Thanks & Regards,
    Sampath.

    Hi
    when you performed the SMD Setup Wizard in the managing system, created the SMD_ADMIN user and the enter the passowrd
    please reset the password for the smd_admin user in the managing system (satelite system and try)
    else use the section 4.9.2 in the diagnostics setup guide 7.11 on [https://websmp108.sap-ag.de/diagnostics|https://websmp108.sap-ag.de/diagnostics]  > media library as below
    4.9.2 Change the Diagnostics Agent credentials
    This section provides information about how to change the credentials (login and/or password) of the J2EE user used to connect the Diagnostics Agent to the Managing System.
    Prerequisites
    All the Diagnostics Agents must be connected to the Managing System before updating the password of the J2EE user used by these Diagnostics Agents
    Procedure
    1. You can either change the password of the J2EE user used by the agents or create a new J2EE user in User Management.
    2. Open the Agent Administration application
    In the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.
    3. All the agents are disconnected and reconnected with the new credentials
    jansi

  • Does solution manager 4.0  require SMD Agent?

    we have  solman 4.0 abap+java with sp11.we are in the process of configuring sol mananager  diagnostics for sattlite systems.
    for monitoring solution manager   java stack it self from solution manager  do we need to install  SMD AGENT   even thogh solution manger it self has SMD server ? still  solution manger need SMD AGENT ?

    Hi,
    SMD Agents are mandatory to run Diagnostics on sattelite systems.
    Each Agent is connected to SMD Server and is able to run task or collect information from central request (SMD Server).
    If you do not have them, you will not be able to run any tools in Diag.
    SMD Server is one sub-component of Solution Manager 4.0.
    Regards,
    Frederic

  • Preparing Solution Manager for SMD Agents Installation

    Hello everyone
    I have to configure the Solution Manager of QAS to receive new SMD Agents, I looking at the transaction SOLMAN_SETUP.
    Does anybdoy know what do I have to do to prepare the environment for the installation of SMD agents?
    Thank

    Hi Marcelo,
    Check note 1365123 - Installation of Diagnostics Agents, this note shows the agent installation strategy. You must install one SMD agent per host (physical or virtual) . The SMD agent should be installed in all host you want to monitor.
    In order to connect the SMD agent into your Solution check the following WIKI:
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-Connectionoptions
    Also, you can managed the SMD agent in the "Agent Administration", it can be found at:
    - SOLMAN_WORKCENTER
    - Tab Root Cause Analysis
    - "Agent Administration"
    I recommend you to use the "Direct connection to solution manager" for your agents. It is easier than the SLD registration.
    Regards,
    Allam

  • Change the Standard Installation Directory of SMD Agent

    Hi Everyone,
    Standard Installation Directory of SMD Agnet is /usr/sap/SMD which I want to change & Install the SMD Agent
    under /usr/sap/<SID>/SMD directory
    I dont want maintain soft link way
    Is it possible , If yes then How ??
    Thanks in advance
    Regards
    Deepak Gosain

    Dear Deepak Gosain
    Keep in mind that Diagnostics Agent 7.11 is the new version for SAP Solution Manager EHP1 > SP20. Depending on your current version of Solution Manager you might want to start installating the new version.
    The new version has it's own unique SID and acts like a SAP system: for example for stop/start it uses stopsap and startsap commands, instance profiles and SAP JVM instead of OS JVM.
    Structure in new version is /usr/sap/<SID>/SDMA<instance no> where SID needs to be unique (so not your existing SAP system SID).
    Kind regards
    Tom

  • SMD agent communication channel

    Hi All,
    I am configuring SMD for our landscape.
    I have successfully installed Wily Introscope Enterprise Manager 7.2 on our solution manager system.
    from what i understand i need to install SMD agent in satellite system to connect to SMD server in Solman system. fyi, my satellite system reside in different segment of solman system. Whats port do i have to use to connect the SMD agent(satellite) & SMD server(Solman system)? Thanks
    Ridhwan

    The following ports have to be opened up in your firewall prior to End-to-End Diagnostics
    installation. It is recommended to place the SAP Solution Manager within the same subnet or
    DMZ of your managed landscape. In case you are managing systems in different subnets you
    have to adapt your security settings and firewall accordingly.
    Connection established u201CServiceu201D on dest. host / Protocol Service port example /from host(s) Format Src. Host to host
    Dest. Host
    Outside Diagnostics
    Server
    J2EE engine / HTTP
    Ex: 50100 /
    5<InstanceNb>00
    DMZ Diagnostics Server
    ITS / HTTP Default: 8000
    Outside Diagnostics Server
    Introscope Manager/ HTTP
    Default: 8081
    Diagnostics Server
    IGS / HTTP Ex: 41080 /
    4<InstanceNb>80
    ALL Managed systems
    (Diag. Agent)
    Diagnostics Server
    J2EE engine / P4 Ex: 50104 / 5<InstanceNb>04
    ALL Managed
    Diagnostics Server
    Message srv. / HTTP
    Ex: 8101 / 81<InstanceNb>
    Hope this helps,
    Thanks
    Aditya.

  • No option to install SMD Agent Candidates using the SMD

    Dears,
    I want to bind a candidate SMD agent to my managing system. According to the guide I have to select one of the agent candidates and a new frame should appear where I can enter a username and a password.
    The problem is that this frame does not appear.
    Can someone help me out on this one ?
    kind regards
    Davy

    Hi Davy,
    This solution is only applicable for SolMan 7.0
    1. Kindly check if the Maintenance Mode is OFF.
    After selecting the candidate Agent, a new frame will be opened(not a window).
    This frame will be just below the table, from where you have selected your Candidate agent.
    You need to expand it.
    I hope this will help.
    For more details ::
    https://websmp103.sap-ag.de/diagnostics
    End to End Root Cause Analysis > Installation & Configuration > Root Cause Analysis Installation and Upgrade Guide
    Refer to page 22( in pdf page 27 of 49).
    Best Regards,
    Pradeep Bishnoi

  • How to install SMD Agent on a MSCS?

    Hello helpers,
    we have installed a PI 7.1 (double stack) on a MSCS environment. The next step is to connect the PI 7.1 SAP system to our SolMan and to install the diagnostics agent. Unfortunately I wasn't able to find any documentation explaining an installation of the SMD Agent in a MSCS environment.
    Does anybody know what has to be done? Do I have to install 3 agents, one on every MSCS node and one in the SCS/ASCS cluster resource group, or is only one agent needed in the SCS/ASCS cluster resource group?
    Looking forward for any answers,
    Sascha Piotrowsky

    Hi Sascha,
    To distribute a solution to the diagnostics the install path must be verified in TC SMDIAG_WIZARD. To verify the install paths an installed SMD-AGENT is neccessary.
    Yes
    Another point is that we like to monitor the J2EE Servers and Dispatchers from the 2 instances on "nodeA" and "nodeB". So in my opinion at least 2 SMD-Agent should be installed, one on every node. Do you agree?
    No, you need one SMD Agent, this agent can then monitor multiple instances on one virtual host. The connection is only between virtual host and agent, not between instance and agent.
    But what shall I do with the ASCS00/SCS01 instance. Does an SMD-Agent installation bring any effort on "clusterSID" or is it a must?
    It's not a must, only relevant if you want to receive host metrics from this host. As this is only virtual, I would not install one here.
    Best regards
    Michael

  • The SMD Agent 'slcxemw04vu' hasn't been found!

    Hi,
    We are have problem  with SMD agent.
    We are executing Setup wizard ( for managed system ) but getting following message
    The SMD Agent 'slcxemw04vu' hasn't been found!
    Thing is SMD agent is running on host slcxemw04vu but somehow it is not able to detect.
    System Install Path: /usr/sap/<Agent SID>  :Is this correct Path?
    Instance Path:/usr/sap/<Agent SID>/<AgentSID97>Is this correct Path?
    Please let me know if you have any information for message'
    The SMD Agent 'slcxemw04vu' hasn't been found!
    Best Regards,
    Tushar
    Edited by: TusharC Chavan on Oct 21, 2009 5:44 PM

    Hi Rahu,
    Now Remark are "
    Setup data must be entered for  with servers : server0 (running EM Core, Application Server Java) (ITS port number must be provided)"
    Now AS Java system will not have ITS . So entered solution manager ITS info.Then I got
    "with servers : server0 (running EM Core, Application Server Java)
    No setup or configuration steps performed yet"
    By the way I can't find  Diagnostics Administration --> Diagnostics System --> Self Check. Select your Solution and start a Self Check.Can you please explain it in detail.
    Best Regards,
    Tushar

Maybe you are looking for