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

Similar Messages

  • Configure com.sap.smd.agent.application.portalactivityreport

    Hi,
    I am trying to use the solution manager diagnostics and the portal activity reports to gather some information about our portal utilization. I have my portal system connected using SMD agent, I am able to run other monitoring application within SMD but when I try to execute the portal activity report I get the following error:
    Portal Activity Reporting - Form
    Could invoke portal activity report web service properly, please check the configuration
    On the configuration of the application there are not parameters to configure, and the agent application seems to be running and deployed:
    com.sap.smd.agent.application.portalactivityreport 7.0010.20061020144811.0000 7.0010.20061020144811.0000 Running
    If somebody has implemented this functionality or have had the same problem let me know with any idea of pointer.
    Thanks in advance for the help,
    Zareh Vazquez

    Hello,
    You have to follow the SAP Note 893101 to set the security zone to Everyone on the Portal Activity Report web service on the portal.
    And you need to restart the service com.sap.portal.activity.report.core.
    Best regards,
    Paula

  • SR3 SMD Agent on SP15

    Hi
    Our Solution Manager is on SP14 and Managed System is on SP15. I want to install the SMD Agent. As per the note 1126895 it is possible and suported. LMSERVICE is SP14.
    I used note 1170855 to install it and it was successfull but the status is "in Progress" in http:////<hostname>:<port>/smd page. It says "DEPLOYING APPLICATION". It never finishes.
    I checked the log file jvm_SMDAgent.out and it says that
    Starting SMDAgent ...
    Running SMD Agent ...
    Establishing connection to server 'ms://<hostname>:8177/P4
    [ms://<hostname>:8177/P4] Waiting for connection ...
    [ms://<hostname>:8177/P4] Checking server availability...
    [ms://<hostname>:8177/P4] Authentication in progress ...
    [ms://<hostname>:8177/P4] Connection established .
    [ms://<hostname>:8177/P4] Registering agent on server ...
    Exception occured. Please check log files.[Exception ID:1219178405804 ]
    [ms://<hostname>:8177/P4] Waiting for connection ...
    [ms://<hostname>:8177/P4] Checking server availability...
    [ms://<hostname>:8177/P4] Authentication in progress ...
    [ms://<hostname>:8177/P4] Connection established .
    [ms://<hostname>:8177/P4] Registering agent on server ...
    It never finishes.
    It is failing at deployment application.
    The log file SMDSystem.0.log states following -
    Aug 19, 2008 4:30:04 PM [Thread[Thread-2,5,main]] Info
    [AgentContext.offlineDeployApplication] ENTERING - deploying file
    com.sap.smd.agent.application.runtime_7.0014.20080429115048.0000.war
    Aug 19, 2008 4:40:05 PM [Thread[SMDAgent connection thread,5,main]]
    Error [Exception ID: 1219178405804 ] java.rmi.RemoteException -
    error counter: 1
    [EXCEPTION]
    java.rmi.RemoteException: Agent Registration failed: Time out occurred
    when calling method 'offlineDeployApplication' on object
    [com.sap.smd.api.IAgentContext_Stub@1de64fc2] after 600000 ms.
    possible cause: com.sap.smd.server.util.concurrent.TimeoutException
    at com.sap.smd.SMDServerHandle.internalRegisterAgent
    Anybody has experienced it.
    Please let me know.
    Regards.
    SS

    Hello,
    Would you kindly share the solution?
    Think I run into a similar issue.
    Many Thanks,
    Jan

  • SMD agent not starting correctly FAIL: NIECONN_REFUSED (Connection refused)

    I am getting the following message when I start the agent.  I don't see any errors except for this, and when I try to connect it in agent_adminstration, it never connects.  Just eventually times out after 30 mins.
    FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.
    cat jvm_SMDAgent.out
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=ssmsap_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    com.ibm.cpu.endian=little
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20080922_1143
    com.ibm.oti.vm.bootstrap.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    com.ibm.oti.vm.library.version=23
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    file.encoding=UTF-8
    file.separator=/
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    j2ee.dbhost=
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.compiler=j9jit23
    java.ext.dirs=/opt/IBMJava2-amd64-142/jre/lib/ext
    java.fullversion=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.home=/opt/IBMJava2-amd64-142/jre
    java.io.tmpdir=/tmp
    java.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=2.3
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=IBM Corporation
    java.vendor.url=http://www.ibm.com/
    java.version=1.4.2
    java.vm.info=J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    J9VM - 20080922_23329_LHdSMr
    JIT  - 20080815_1845_r8
    GC   - 200809_04
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.3
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=F2143454721
    jstartup.ownProcessId=17393
    jstartup.whoami=server
    jxe.current.romimage.version=9
    jxe.lowest.romimage.version=9
    line.separator=
    memory.manager=256M
    os.arch=amd64
    os.name=Linux
    os.version=2.6.9-89.ELsmp
    path.separator=:
    sun.boot.class.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/core.jar:/opt/IBMJava2-amd64-142/jre/lib/charsets.jar:/opt/IBMJava2-amd64-142/jre/lib/graphics.jar:/opt/IBMJava2-amd64-142/jre/lib/security.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmpkcs.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorb.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmorbapi.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjcefw.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjssefips.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjgssprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjsseprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmjaaslm.jar:/opt/IBMJava2-amd64-142/jre/lib/ibmcertpathprovider.jar:/opt/IBMJava2-amd64-142/jre/lib/server.jar:/opt/IBMJava2-amd64-142/jre/lib/xml.jar
    sun.boot.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    user.variant=
    Running SMD Agent ...
    [p4://ssmsap:50004] Agent ready.
    Initialization done.

    cat dev_SMDAgent
    trc file: "/usr/sap/SMD/J98/work/dev_SMDAgent", trc level: 1, release: "701"
    node name   : smdagent
    pid         : 17393
    system name : SMD
    system nr.  : 98
    started at  : Wed Oct  7 08:56:32 2009
    arguments         :
              arg[00] : /usr/sap/SMD/J98/../exe/jlaunch
              arg[01] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
              arg[02] : -DSAPINFO=SMD_98_server
              arg[03] : pf=/usr/sap/SMD/J98/../SYS/profile/SMD_J98_ssmsap
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SMD/J98/profile/smd.properties]
    -> ms host    :
    -> ms port    : 36
    -> OS libs    : /usr/sap/SMD/exe
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SMD/J98/profile/smd.properties
    Instance properties
    -> ms host    :
    -> ms port    : 36
    -> os libs    : /usr/sap/SMD/exe
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    Worker nodes
    -> [00] smdagent             : /usr/sap/SMD/J98/profile/smd.properties
    [Thr 182894174624] Wed Oct  7 08:56:32 2009
    [Thr 182894174624] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182894174624] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1085282656] WaitSyncSemThread: Thread 1085282656 started as semaphore monitor thread.
    [Thr 182894174624] SigISetDefaultAction : default handling for signal 17
    [Thr 182894174624] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182894174624] CPIC (version=701.2009.01.26)
    [Thr 182894174624] [Node: SMDAgent] java home is set by profile parameter
            Java Home: /opt/IBMJava2-amd64-142
    [Thr 182894174624] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SMD/J98/../exe/jvmx.jar
    JStartupIReadSection: read node properties [smdagent]
    -> node name          : SMDAgent
    -> node type          : server
    -> node id            : 1
    -> node execute       : yes
    -> java path          : /opt/IBMJava2-amd64-142
    -> java parameters    : -DP4ClassLoad=P4Connection -Xj9 -Xmn50m -Xgcpolicy:gencon
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 256M
    -> init heap size     : 256M
    -> root path          : ../SMDAgent
    -> class path         : ../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> OS libs path       : /usr/sap/SMD/exe
    -> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar
    -> parameters         : run jcontrol
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 58981
    -> shutdown timeout   : 20000
    [Thr 182894174624] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1086335328] JLaunchIStartFunc: Thread 1086335328 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -DP4ClassLoad=P4Connection
    -> arg[  4]: -Xj9
    -> arg[  5]: -Xmn50m
    -> arg[  6]: -Xgcpolicy:gencon
    -> arg[  7]: -Dsys.global.dir=/usr/sap/SMD/SYS/global
    -> arg[  8]: -Dapplication.home=/usr/sap/SMD/exe
    -> arg[  9]: -Djava.class.path=/usr/sap/SMD/J98/../exe/jstartup.jar:/usr/sap/SMD/J98/../exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.01.3.0.20090224123938/launcher/smdagentlauncher.jar
    -> arg[ 10]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SMD/exe:/usr/lib:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    -> arg[ 11]: -Dmemory.manager=256M
    -> arg[ 12]: -Xmx256M
    -> arg[ 13]: -Xms256M
    -> arg[ 14]: -DLoadBalanceRestricted=no
    -> arg[ 15]: -Djstartup.mode=JCONTROL
    -> arg[ 16]: -Djstartup.ownProcessId=17393
    -> arg[ 17]: -Djstartup.ownHardwareId=F2143454721
    -> arg[ 18]: -Djstartup.whoami=server
    -> arg[ 19]: -Djstartup.debuggable=yes
    -> arg[ 20]: -DSAPINFO=SMD_98_server
    -> arg[ 21]: -DSAPSTARTUP=1
    -> arg[ 22]: -DSAPSYSTEM=98
    -> arg[ 23]: -DSAPSYSTEMNAME=SMD
    -> arg[ 24]: -DSAPMYNAME=ssmsap_SMD_98
    -> arg[ 25]: -DSAPDBHOST=
    -> arg[ 26]: -Dj2ee.dbhost=
    [Thr 1086335328] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
    -> arg[  0]: run
    -> arg[  1]: jcontrol
    [Thr 1086335328] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1086335328] Wed Oct  7 08:56:35 2009
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
    [Thr 1086335328] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1086335328] Wed Oct  7 08:56:38 2009
    [Thr 1086335328] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 1086335328] JLaunchISetState: change state from [Starting (2)] to [Running (3)]
    [Thr 1101334880] Wed Oct  7 08:56:43 2009
    [Thr 1101334880] JLaunchISetState: change state from [Running (3)] to [Starting applications (10)]
    [Thr 1101334880] Wed Oct  7 08:56:48 2009
    [Thr 1101334880] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]

  • 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

  • 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

  • Monitoring SMD Agent with CCMS

    Hi gurues, I need to know if there is any way to monitor SMD Agent installed in an application server via CCMS CEN system on a Solution Manager.
    Right now we have CEN Monitoring define on Solution Manager, and several SMD Agents over the whole landscape, and it is critical for us to get alerted when this SMD goes down, so we are thinking about monitoring through Solutin Manager, isthat possible or we must do it in another way?
    Regards
    Gustavo

    It's so typical SAP; I was looking for exactly the same question. SAP changed from 7.1 the OSCOL to run by the host agent instance and will not install the OSCOL to the SAP instance. You also will not be able to download OSCOL separatly.
    But OSCOL is needed to monitor processes on host side. If the host agent don't starts also the OSCOL will not start (on LINUX side) and so you are not be able to monitor the SMD process.
    The only chance is to start the SMD via init script.
    A better way would be to implement a GRMG availability monitoring; this can be implemented in the CEN system independent from the monitored host. In the first solution the host has to be create itself the basis to monitor itself... that's nonsense.
    I absolutly don't understand why SAP always and everywhere ignore his own design concept and reinvent the wheel. It would be so easy to design and implement the availability moniroring on SAP development side but they don't have a focus on that. It is the same with SAP router connection via host agent to the CEN system. It was implemented as very last feature after a lot of disgruntled customers (administrators).

  • 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

  • SMD agents goes offline in agent administration

    Hi,
    In my landscape all the SMD agents are directly registered to Solman SPS27.
    Each time my solman is restarted, all teh agents in agent administration goes offline. but in actual its runing at OS lvl.
    After we take seperate Java stack restart of solman, agents come online in agent admin. This scenario is confusing
    Any idea as to how can we overcome this issue ?
    Regards,
    Shyam

    Thanks Guilherme for this very good clearification!
    I have a simular problem at the moment and can confirm that the agent connection get disabled because they are not able to authentificate. I will try to implement the workaround with the telnet command to bring the agents in MM... This should help to solve the issue.
    Anyway what I don´t understand is that not all agents get disconnected!
    For example:
    SMDsystem.log of Agent which is offline:
    Aug 20, 2011 1:01:15 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Checking server availability...
    Aug 20, 2011 1:01:16 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Authentication in progress ...
    Aug 20, 2011 1:02:07 AM [Thread[Connector,5,main]] Error      Failed to connect to SMD server - user: SMD_ADMIN
    Aug 20, 2011 1:02:07 AM [Thread[Connector,5,main]] Error      Connecting to SMD server ms://jusmp00:8104/P4 failed
    com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
    Aug 20, 2011 1:02:08 AM [Thread[Connector,5,main]] Warning    Access denied occurs during the registration, smd connector has been disabled (waiting new SLD GUID).
    Aug 20, 2011 1:43:20 AM [Thread[SLD-Registration,1,main]] Info       Next try to push instance data in SLD is  Sat Aug 20 13:43:06 AST 2011
    SMDsystem.log of Agent which is online:
    Aug 20, 2011 1:01:12 AM [Thread[Connector,5,main]] Error      ms://jusmp00:8104/P4 Ping failed : com.sap.smd.server.exec.asio.TimeOutError - null
    Time out occurred when calling method 'ping' on object com.sap.smd.api.ISMDServerHandle_Stub@54bf219b after 30001 ms.
    possible cause: com.sap.smd.server.util.concurrent.TimeoutException
         at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:130)
         at $Proxy1.ping(Unknown Source)
         at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.updateConnectionStatus(SMDConnector.java:230)
         at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.run(SMDConnector.java:189)
         at java.lang.Thread.run(Thread.java:664)
    Caused by: com.sap.smd.server.util.concurrent.TimeoutException
         at com.sap.smd.server.util.concurrent.FutureResult.timedGet(FutureResult.java:159)
         at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:122)
         ... 4 more
    Aug 20, 2011 1:01:12 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Checking server availability...
    Aug 20, 2011 1:40:27 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Authentication in progress ...
    Aug 20, 2011 1:40:29 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Connection established .
    Aug 20, 2011 1:40:30 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Registering agent on server ...
    So you see that the secound agents waits the 40 minutes and start the authentication process after than.
    Both agents are 7.11 and application version 7.01.7.3.20110311130810.
    Any idea about that?

  • 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

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

  • SMD and SMD-agent - network load

    We have a SolMan with SMD, monitoring a portal (with SMD agent).
    The network people tell us there is a lot of communications going on between the 2 servers - approx. 10 GB/day.
    Could this possibly be the communication between SMD agent and SMD?
    (Or the comminication between the Introscope agent and the Introscope EM?)
    If so, could it be reduced by configuration of the agent (configuring the level of detail of the information it sends across)?
    Where can I find the documentation? The documentation I have found so far is about set-up - making it work - not about fine-tuning.

    Thank you for your reply.
    Are you sure that those 2 servers are dealing with this much # of data?
    That's what the network people see in their tool.
    Basically, how come you can arrive at a decision that SMD agents is using this much load..there can be any other processes too, which are causing this traffic of data...
    The reasoning is, that this is the only functional relationship. The only application on server A that has a need to communicate with anything on server B is SMD. This assumes that the application manager has not overlooked any interactions.
    On the other hand, we are now looking at port numbers and checking what's listening on those port numbers.

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

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

Maybe you are looking for