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.

Similar Messages

  • 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

  • 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

  • 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]

  • How to find installed SMD Agent version?

    Hi,
    Please let me know how to find the installed SMD agent version in managed system.
    Thanks,
    Kavitha Rajan.

    Hello,
    Something really easy to differentiate the agents installed:
    -     7.01-> /usr/sap/SMD/JXX
    -     7.11 or 7.20 -> /usr/sap/DAA/SMDAXX
    Regards,
    Allam

  • 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?

  • Connection between SMD Agent and SMD server via SAProuter

    In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it?
    Hope someone can give us your precious advices on this issue.
    Karl

    Perfect; and thanks for your response. I found this help page for developers to implement P4 support over SAP router: http://help.sap.com/saphelp_nw73/helpdata/en/48/2992d7ad8758d7e10000000a421937/content.htm
    But in the SM Diagnostics Setup options I can set up only a direct HTTP adresses and have no options to set up connections over a sap router to P4 ports directly. I can at the moment only solve my problems with NAT or firewall rules.
    And also the diagnostic agent setup has no options to config a proxy or sap router. I found yesterday a blog on sdn side with screenshots of the setup with all available connection opetions to SLD... sry I can not post this link today.
    This is an official statment of SAP from the current version of SMD guide; it is also possible but why not from the beginning???:
    In some network conficurations, the Diagnostics agent has to connect to the Managing system though a SAP router.
    This feature will be fully supported in Solution Manager 7 Ehp2 (7.02).
    In order to enable this feature in Ehp1, please contact the Diagnostics Agent support team to get information on how to
    setup the agent and on which patch level you can perform the installation.
    This thread were a long time not answared; proxy and routing connections are mostly stepmotherly handled by SAP; this is also a problem by set up of automatic RFC generations in SMSY; why there are in the setup assitents no options to set up the router string.
    I have absolutly no comprehension for this in year 2011. All this technics are good known and long time tested.
    In this case the f**k has provoked an answare to this thread and this is what I expected; but sorry for my style You are right I could also writh why the heck
    FAQ:
    SMD root side on SDN: http://service.sap.com/diagnostics
    SM FAQ: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4e49dbea-0c01-0010-91bd-f0b61388c9ae
    SM Setup Home: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
    SM Diagnostic Troubleshooting Guide: https://websmp201.sap-ag.de/~sapdownload/002007974700000409092009E/DiagAgent_TroubleShooting.pdf
    SMD Candidate Setup: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

  • 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

  • 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

  • How to install diagnostic agent  for nw 7.0sp17, with solman ehp1- sp25

    Hi Gurus,
    we are using NW 7.0 Enterprise portal  at SP17, want to configure E2E.  So installed solution manager 7.0 EHP1 SPS 25.
    Ran the Guided procedure solman_setup successfully. with  intitial config, basic config  and pending at managed system config.
    Here my question is:
    do i need to install smd agent on solman? or solman itself comes with agent. i cannot see any agent in mmc on solution manager.
    What is SOLMANDIAG and SOLMAN AGENT, SMD Agent and Host agent.
    The guide (https://websmp207.sap-ag.de/~sapidb/011000358700000952852009E)  says before install SMD agent, install host agent, diagnostics agents are available 7.11 on wards, while installing smd agent sapinst asking  SAP Unicode Kernel 711 , but currently my NW Portal system is using kernel 7.0..
    Any guide, how to proceed for E2E on nw7.0 SP17 with solman ehp1 sp25( highest availale spack)
    Thanks in advance.
    Regards
    Balaji

    Hi Balaji,
    As per the SMD agent 7.11 installation guide (https://service.sap.com/~sapidb/011000358700000952852009E) , Page 6 and 8, you would need to download the standard NW 7.11 DVDSs( usually kernel and Installation master) and SMD agent installation packages from the SMP. Location is mentioned in the guide as well.
    For your query that Portal is based in i386, these are two different things. The SMD Agent will be installed with its own kernel and also 7.11 kernel is not support edon 32bit. However the SMD agent will use its own 7.11 64bit kernel and Portal will use its i386 kernel. Hopefully your hardware is able to support both. I recommend to proceed with x86_64 7.11 kernel for your SMD installation. Incase the hardwar does not support this, go for alower release of SMD Agent wherein the kernel supports 32 bit hardware.
    Best Regards,
    Srikishan

  • Standalone SMD Agent for EEM won't connect to SLD

    I have installed a standalone SMD agent, which was configured properly (logs verify this) and starts up successfully, but I don't ever see it register in the SLD. Does anyone know of a guide which tells how to manage a standalone SMD agent? I want to get it connected to the SLD in Solution Manager so that I can use it as an EEM robot, but the connectivity so far is not working.
    For instance, if there is a way to get something like SM59 in an ABAP system on my SMD agent to change and test connectivity parameters, this may help.
    Cheers,
    David.

    OK, thanks for the reference to the troubleshooting guide, I had not seen that before. Using it, I found the following procedure:
    How to check if the Diagnostics agent is registered in SLD?
    ␣ Go in SLD with the url: http://sldhostname:port/sld
    ␣ Logon with a J2EE user having the role SAP_SLD_ADMINISTRATOR
    ␣ Go in the section u2018Administrationu2019
    ␣ Click on link u2018Content Maintenanceu2019
    ␣ Select the subset u2018All with Instances and class u2018Diagnostics Agent Instanceu2019
    If the class u2018Diagnostics Agent Instanceu2019 does not appear in drop down list, No Diagnostics agent is registered
    ␣ In column Name of table, check if the Diagnostics agent is present.
    This procedure verified that my diagnostics agent is in fact in contact with the SLD, but for some reason, the agent does not show up in the SLD when I go to Home > Technical Systems, nor does it show up when I go to the EEM Administration screen > Robots > Check Agents.
    So I'll have to keep researching.
    Cheers,
    David.

  • SMD Agent 7.4* and SAPHOSTAGENT

    Hi All,
    Thanks for looking in to this.
    I have installed the latest SMD agent (7.41) on the managed system. I managed to read somewhere that the latest smd agents have an option to update host agents automatically. can some one help me in telling me how this can be done?  i know of the old procedure by keeping the latest host agent in $DIR_EXECUTABLE. But I assume there is a new procedure in updating host agents with SMD. i couldnt find sap notes on this. Could anyone help me on this?
    thanks in advance..

    Hi Jim,
    Below notes may be helpful for queries ,
    1365123 - Installation of Diagnostics Agents( check the attachment )
    Diagnostics Agent Release Characteristics - pg 22
    1473974 - Using the SAP Host Agent Auto Upgrade Feature( check the attachment )
    https://websmp204.sap-ag.de/~sapidb/012003146900000135752013E/SAP_Host_Agent_129.pdf
    Rg,
    Karthik

  • SMD Agent Metrics/BOE native code metrics Missing in wily Enterprise Manager

    SMD Agent and BOE native code metrics are not updated to wily EM. Previously the metrics were written to Wily EM. This is standalone setup of Wily Ent Manager without Solution Manager.
    Environment:
    Standalone Wily introscope Eterprise Manager - Introscope Enterprise Manager 9 SP15
    DIAGNOSTICS AGENT 7.3 SP03 (incl. HostAgent)
    BI 4.0 SP6 Patch 6, Windows 2008, Clustered/Distributed.
    Logs:
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Initialization done.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Service provider initialized.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Agent Applications started.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Smd connector has been disabled
    Apr 25, 2014 3:54:35 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from INITIAL to CONNECTING
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to DISABLED
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Fatal      com.sap.smd.wily.hostagent.WilyHostService - init(...): Failed to start Agent!
    [EXCEPTION]
    java.rmi.RemoteException: WilyHostAgent start failed; nested exception is:
      com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:122)
      at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
      at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
      at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
      at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
      at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
      at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
      at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
      at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:111)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:154)
      at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:733)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:495)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:354)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:311)
      at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:1016)
      at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:933)
      at com.sap.smd.agent.connection.SMDConnectionTask.startOffline(SMDConnectionTask.java:862)
      at com.sap.smd.agent.connection.SMDConnectionTask.internalAttemptConnection(SMDConnectionTask.java:549)
      at com.sap.smd.agent.connection.SMDConnectionTask$1.run(SMDConnectionTask.java:107)
      at com.sap.smd.agent.connection.P4JNDIContextHelper.executeInSecurityContext(P4JNDIContextHelper.java:148)
      at com.sap.smd.agent.connection.SMDConnectionTask.attemptConnection(SMDConnectionTask.java:102)
      at com.sap.smd.agent.connection.SMDConnectionTask.run(SMDConnectionTask.java:1282)
      at java.lang.Thread.run(Thread.java:743)
    Caused by: com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
      at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:510)
      at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:99)
      at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
      ... 26 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
      at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
      at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
      ... 29 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1782)
      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
      at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2857)
      at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:235)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
      at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
      at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
      at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
      ... 31 more

    Hello Gopal,
    Please refer to section Wily Introscope setup for BOE 4.0 of this wiki:
    Managed System Setup of BOE 4.0 system in Solman 7.1 - SAP Solution Manager Setup - SCN Wiki
    You may also found interesting
    Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
    https://service.sap.com/sap/support/notes/1722874
    https://service.sap.com/sap/support/notes/1357901
    Best Regards.
    Luis Roel

  • SMD agent not connecting to the SMD server!!!!

    Hi
    We are tring to set up the Solution manager diagnostics. We are on SP13 NW04s.
    We finished installing the Wily 7.2, Diagnostics System Wizard,
    and then finished installing the SMD agent on the remote server without any error.
    Our Diagnostic system server(solution manager) in on i5/OS and the our SMD agents are spread across windows servers & i5/OS servers.
    The SMD agents from the i5/OS server got connected to the Diagnostic server(solution manager) within minutes.
    But the ones from windows(X64) do not get connected to the Diagnostic server(solution manager) . We waited and waited, tried rebooting the agent, but to no help. The status it shows is "in process"
    When we checked the logs in the SMD agent system on windows, we found out that it is complaining about some  application which failed to unzip as shown:
    Mar 18, 2008 8:04:47 PM [Thread[SMDAgent connection thread,5,main]] Info       [SMDConnector.reset] in progress ...
    Mar 18, 2008 8:04:47 PM [Thread[SMDAgent connection thread,5,main]] Info       Stopping Applications ...
    Mar 18, 2008 8:04:47 PM [Thread[SMDAgent connection thread,5,main]] Info       [SMDConnector.reset] Done.
    Mar 18, 2008 8:04:52 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Waiting for connection ...
    Mar 18, 2008 8:04:52 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Checking server availability...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Authentication in progress ...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Connection established .
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       [sapms://<SMD_SERVER_NAME>:8145] Registering agent on server ...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       Reading JStartup environment...
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       'SAPLOCALHOST' found, The value 'srvlctemp01' will be used to determine the Agent name.
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       InetAddress Resolving for 'srvlctemp01' - FQN: srvlctemp01 SQN: srvlctemp01 IP: 10.10.16.89
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       InetAddress Resolving for localhost - FQN: srvlctemp01 SQN: srvlctemp01 IP: 10.10.16.89
    Mar 18, 2008 8:04:53 PM [Thread[SMDAgent connection thread,5,main]] Info       Agent handle : srvlctemp01_SMD_J66/srvlctemp01 created.
    Mar 18, 2008 8:04:53 PM [Thread[Thread-620,5,main]] Info       Overriding runtime property from server configuration, name= 'runtime.states.initial', value='core.startup,core.patch.enabled'.
    Mar 18, 2008 8:04:56 PM [Thread[Thread-616,5,main]] Info       [AgentContext.offlineDeployApplicationConfiguration] ENTERING
    Mar 18, 2008 8:04:56 PM [Thread[Thread-616,5,main]] Error      Deploy application configuration failed.
    [EXCEPTION]
    com.sap.smd.agent.deploy.DeploymentException: Cannot expand zip entry.
         at com.sap.smd.agent.deploy.DeploymentManager.extractCompressedStream(DeploymentManager.java:258)
         at com.sap.smd.agent.deploy.DeploymentManager.installAppConfiguration(DeploymentManager.java:780)
         at com.sap.smd.agent.AgentContext.offlineDeployApplicationConfiguration(AgentContext.java:597)
         at com.sap.smd.agent.AgentContextp4_Skel.dispatch(AgentContextp4_Skel.java:189)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
         at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:710)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.util.zip.ZipException: invalid entry CRC (expected 0x0 but got 0x1b3304ba)
         at java.util.zip.ZipInputStream.read(ZipInputStream.java:164)
         at com.sap.smd.agent.deploy.DeploymentManager.extractZipEntry(DeploymentManager.java:321)
         at com.sap.smd.agent.deploy.DeploymentManager.extractCompressedStream(DeploymentManager.java:251)
    Has anyone experieced any kind of errors related to this?
    Thanks

    Hi Folks,
    Can u give me the steps and best practices to be follow to configure & Install the WILY Interoscope with solution manager.
    Please share your experience also with WILY Interoscope.
    Documents would be highly appreciated with reward points.
    Regards,
    Akshay

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

    Dear,
    I have already upgrade the Solution Manager 7.0 EHP1 . I have a problem with my SMD  error The SMD Agent 'BASAPI02' hasn't been found!
    I want to setup E2E Root Cause Analysis for ERP 6.0 Stack Java system.
    So I configured SMSY, I've already installed SMD Agent in managed system successfully also.
    When I run the Diagnostics Setup -> Managed System -> Setup WIzard,
    in the Setup Parameter Step , it said that " No SMD Agent is currently available (ie not assigned). Please install an agent for BASAPI02 or unassign an existing agent in Agent Administration Why is that so ?
    In the Agent Administration ( DIagnostics Administration -> Managed SYstem -> Agent Administration) found that the agent is online.
    does anyone know why this happens and how to resolve
    Thanks in advance,
    Antonio

    Hello Antonio
    The agent name registration or agent registration on it's own depends on the version of your diagnostics agent.
    From diagnostics agent 7.20 and higher if you have installed it using default connection setting in sapinst then you don't need to seperately register the diagnostics agent in the agent candidate management.
    Once the agent is known you should see it in the agent administration list. If you don't see the agent in the agent administration list it would mean it is not yet known and you have to go through the agent candidate management first.
    The server name assignment is normally done through the managed system setup. After selecting your SAP system to be configured and pushing the setup button you get a screen in which you have to fill in the hostname, user+pass and so on at the left side bar. On the right side you should see one or more lines that represent your SAP system.
    You have to expand that line and then select the appropriate agent from the list. After selecting the correct agent from the list your diagnostics agent will get the hostname assignment and you will be prompted to wait and refresh because the agent is then automatically restarted.
    Kind regards
    Tom

Maybe you are looking for