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

Similar Messages

  • Monitoring Multiple RFCs with CCMS

    Hi,
    I have created a Z data collection method as per NOTE 1069130,mapped it to the standard MTE Class "
    "Availability_RFC_Destinations" But i dont see the data in RZ20 monitor  Plese help me with this

    Hello Chris,
    just played around on my test system...
    > Also MTE_CLASS, which is left blank.
    If MTE_CLASS is used but left blank the MTE will be created with an MTE class "Availability_RFC_Destinations_MA_Class" (I assume this is the case in your system).
    If the MTE_CLASS parameter does not exist in the method definition, the data collector will use "<name of data collection method>_MA_Class" as MTE class.
    > I tried removing MTE_CLASS
    That's a good idea but at first you will have to delete the MTEs directly from rz20 using "Option 4" when the popup regarding how to delete the MTE comes up. This way the information about the MTE and the assigned MTE class is deleted from the monitoring shared memory. After you have deleted the MTEs you can reset the monitoring segment into warm-up status again (now using the data collection methods without MTE_CLASS parameter). This way the MTEs should be created using their individual MTE class.
    Regards, Michael

  • SMD Agent 13 - With LMSERVICE 12.4?

    Good day,
    I am running SolMan Diag 12.4, I see there is a SMD Agent 13(2007/08/20   Support Package 13 of SMD AGENT 7.00, note 1086460) available for download.
    The note does not exist? Can I run the agent on 13 on my satellite systems, or must I stay with 12? Does your SMDAGENT version and LMSERVICE versions need to be the same?
    Anyone running version 13 of the agent?
    Both notes  1049867 and 1086460 in /swdc do not exist.
    Thanks,
    Derek

    Hi Derek,
    Please, don't use a SMD agent with a version upper than LMService.
    LMService / Agents and Notes SPS13 will be released this week.
    Regards,
    Xavier

  • Adapter Monitoring with CCMS

    Hi,
    is there anybody who already set up an adapter monitoring  with CCMS using the alert framework of Runtime Workbench ?
    Background:
    When using the existing MTE's in CCMS (J2EE Monitor Templates - All Systems - <SID> - J2EE Applications - SAP XI Adapter Engine) only rare monitoring information related to XI messages are posted.
    What I would like to see are information about the adapters provided in the logfiles of each adapter.
    For example as soon there's a permission problem for a directory in File Adapter an alert in CCMS should be raised.
    I already checked SAP notes 870232, 913858 and 824039.
    Any feedback appreciated.
    Cheers,
      Juergen

    Hi,
      You can configure the CCMS as per the following two blogs,
    Part 1: /people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
    Part 2: /people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
    Configure the Alert Framework with the below Blog as reference,
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
    Then forward the Alerts created in the CCMS to Alert Frame work, the required steps are given in the below help links.
    http://help.sap.com/saphelp_nw04/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/30/62e77b2f4865488a866d4103923a93/frameset.htm
    Then any alerts that gets generated in CCMS can be passed to the Alert Category kept configured in the Alert Framework.
    Hope this helps you

  • RFC monitor with CCMS

    Hello,
    I'm implementing RFC monitor with CCMS and I have a problem.
    I was able to implement the method with an auto-reaction method of send mail.
    It is working fine but it doesn't repeat the alert!  Let's say, imagine that the RFC isn't working since 3am... we are now at 13pm and the alert is not triggered anymore. In fact, in RZ20 I just see 1 Alert triggered at 3am.
    Is there any way to set this alert to trigger every period of time?
    thanks.
    regards,
    Filipe Vasconcelos

    Hello,
    first it would be good to clarify which monitor are you implementing - there are multiple RFC monitors - for example:
    Availability and Performance Overview Monitor :
    http://help.sap.com/saphelp_nw70/Helpdata/en/ae/cd823bd26a5c42e10000000a114084/frameset.htm
    Transactional RFC and Queued RFC Monitor
    http://help.sap.com/saphelp_nw70/Helpdata/en/8b/ceea3b31aac554e10000000a114084/frameset.htm
    Best to type the name of monitor as displayed in RZ20.
    Based on the type of monitor you might find the answer here:
    http://help.sap.com/saphelp_nw70/Helpdata/en/f6/c55c3bab977239e10000000a114084/frameset.htm
    (for example for status monitor you can set option "When should a message trigger an alert?" to "Always (at every message)")
    Anyway I am afraid that in case you are using performance monitor there is not much you can do. Possibility can be to check if data collection method (for example function) has parameter that can do this (but I am skeptical about this) - if not then you would have to adjust data collection method or implement the monitoring in another way.
    Possibility can be to use some kind of "switch". You can activate option "Display All-Clears in Alert Browser" - this will generate green alerts. Then you can program your own autoreaction method that will perform the "switch operation" (simple insert/update/delete into some Z-table you will create - based on status of alert - red/yellow/green.) Then you can have batch job running another Z-program that is reading this value and constantly reminding use via email.
    If you program this in a good way (abstract autoreaction method) - you can reuse this solution for other monitors as well and easily buid you own email notification functionality.
    I hope it helps.
    Best regards.

  • 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

  • Smd agent problem

    I ve got problem with registering agent in solution manager diagnostic. The following message is in the log:
    registering agent on server......
    Exception - Registering agent on server <hostname>:50104 failed Time out occured when calling method 'configure' on object com.sap.smd.api.IAgentContext_Stub@6eb2c1 possible com.sap.smd.server.util.concurrent.TimeoutException. And this situation is going to repeat all the time

    Hello Damian,
    Please check your SMD patch?  LMSERVICE SP 9 patch 4 or SP10 patch 1.
    (See SAP note: 999138)
    Also ensure your SMD agent is running, stop it and start it at OS Level on the monitored system.
    Hope this helps,
    Dolores

  • 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

  • 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

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

  • Help required regarding Integrating Conversion Agent with SAP-XI

    I want to run a simple File to File scenario which involves integrating conversion
    agent. I gone through a webblog:Integrate SAP Conversion Agent by Itemfield with SAP XI
    I deployed the module and I configured the channel in the same way what was specified in the webblog.
    But when I run my scenario I found CM_TRANSFORMATION_ERROR as the error in communication channel monitoring.
    Can u please provide me the solution for correcting the above error, this would be a great help for me..

    HI,
    see the below links
    http://help.sap.com/saphelp_nw04/helpdata/en/43/6f1f39a08e6fcae10000000a1553f6/CMSUserGd.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/c9f0b4925af54cb17c454788d8e466/frameset.htm - cc
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm - fcc cOUNTER
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/da1e7c16-0c01-0010-278a-eaed5eae5a5f - conversion agent
    with item fiels.
    Regards
    Chilla

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

  • Start of SMD agent fails!

    Hi!
    After the installation of SMD AGENT 7.00 SP09 we've got some problems starting the agent.
    The errorlog says: (/usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log)
    Oct 11, 2006 2:11:26 PM [Thread[SMDAgent connection thread,5,main]] Error      Exception ID: 1160572286256
    Registering agent on server myhost.de:50004failed:
    com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
            java.lang.reflect.InvocationTargetException
    java.lang.reflect.InvocationTargetException
    However, the manual setup of the agent succeeds:
    ./smdsetup.sh /usr/java14_64 myhost.de 50004 j2ee_admin PASSWORD
    SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG
    SMD Agent Setup is in process ...
    - STEP 1: checking JDK location
    JDK location is consistent: /usr/java14_64/bin
    - STEP 2: checking JDK Version
    JDK Version is correct: 1.4.2
    - STEP 3: checking Connection to SMD Server
    SMD Server check completed successfully
    - STEP 4: generating Runtime Properties
    runtime.properties has been created.
    - STEP 5: generating Launcher
    smdagent.bat has been created.
    smdagent.sh has been created.
    - STEP 6: generating SecStore
    secstore.properties: has been created.
    secstore.properties: user has been set.
    secstore.properties generation completed successfully.
    - STEP 7: checking P4 Connection and SMD Agent Registration
    SMD Agent Registration succeeded
    SMD Agent Setup completed successfully
    During the start process of the agent, the agent appears in the agent administration tab in SMD/admin, but it disappears after the erroneous shutdown.
    What can we do?
    Thanks for all hints solving our problem!
    Greetz,
    André Richter

    Hi Rahul,
    please try SMD Agent 7.00 SP10! We had no problems with this version!
    Also make sure that the OSUser has enough privileges. We use the "sidadm" to start the agent.
    Regards
    André

  • SMD Agent doesn't work

    Hello,
    I have been trying to install SMD Agent in my BI system but Solution Manager can't check it, this is the message in Solman_setup
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    Step Wilyhost Agent Details
    Created destination QBB|svs978_QBB_01
    Created action QBB - QBB AbapSystem
    Created action QBB|svs978_QBB_01 - QBB|svs978_QBB_01 AbapInstance
    Created 2 action(s).
    0 Wilyhost Agent(s) from host svs978 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapl917.intra.banesco.com:6001) no Wilyhost Agent was detected from host svs978. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    do you know something??? i restarted the agent but nothing happens
    Thanks!!!!

    Hello...
    For JAVA
    Software Components 
    Vendor  Name  Version  Provider  Location  Applied 
    sap.com  ADSSAP  7.01 SP4 (1000.7.01.4.0.20090417021200)  SAP AG  SAP AG  20091103161136 
    sap.com  BASETABLES  7.01 SP4 (1000.7.01.4.0.20090417015900)  SAP AG  SAP AG  20091103153957 
    sap.com  BI_MMR  7.01 SP4 (1000.7.01.4.0.20090417021807)  SAP AG  SAP AG  20091103161215 
    sap.com  BI_UDI  7.01 SP4 (1000.7.01.4.0.20090416221700)  SAP AG  SAP AG  20091103162333 
    sap.com  CAF  7.01 SP4 (1000.7.01.4.0.20090417194106)  SAP AG  MAIN_NW701P04_C  20091103163937 
    sap.com  CAF-UM  7.01 SP4 (1000.7.01.4.0.20090417194111)  SAP AG  MAIN_NW701P04_C  20091103161325 
    sap.com  CORE-TOOLS  7.01 SP4 (1000.7.01.4.0.20090417021948)  SAP AG  SAP AG  20091103154019 
    sap.com  ISAGENT  8.1 SP0 (8.1.0.0.20090605095817)  SAP AG  SAP AG  20091210142716 
    sap.com  JLOGVIEW  7.01 SP4 (1000.7.01.4.0.20090417020000)  SAP AG  SAP AG  20091103154104 
    sap.com  JSPM  7.01 SP4 (1000.7.01.4.2.20090918151100)  SAP AG  SAP AG  20091201201543 
    sap.com  KM-KW_JIKS  7.01 SP4 (1000.7.01.4.0.20090514115300)  SAP AG  SAP AG  20091103161349 
    sap.com  LM-SERVICE  7.01 SP5 (1000.7.01.5.2.20091211060559)  SAP AG  SAP AG  20091224192630 
    sap.com  LM-TOOLS  7.01 SP5 (1000.7.01.5.3.20091208123420)  SAP AG  MAIN_NW701P05_C  20091228135344 
    sap.com  SAP-JEE  7.01 SP4 (1000.7.01.4.1.20090612152648)  SAP AG  SAP AG  20091103154150 
    sap.com  SAP-JEECOR  7.01 SP4 (1000.7.01.4.0.20090417015900)  SAP AG  SAP AG  20091103154414 
    sap.com  SAP_JTECHF  7.01 SP4 (1000.7.01.4.2.20090612144700)  SAP AG  SAP AG  20091103154520 
    sap.com  SAP_JTECHS  7.01 SP4 (1000.7.01.4.2.20090612152905)  SAP AG  SAP AG  20091103162132 
    sap.com  SWLIFECYCL  7.01 SP4 (1000.7.01.4.0.20090511115334)  SAP AG  MAIN_NW701P04_C  20091103151458 
    sap.com  UMEADMIN  7.01 SP4 (1000.7.01.4.0.20090417195012)  SAP AG  MAIN_NW701P04_C  20091103165828 
    For ABAP
    SAP_BASIS     701     0004     SAPKB70104
    SAP_ABA     701     0004     SAPKA70104
    ST-PI     2008_1_700     0001     SAPKITLRD1
    PI_BASIS     701     0004     SAPK-70104INPIBASIS
    CRMUIF     500     0003     SAPK-50003INCRMUIF
    SAP_BW     701     0004     SAPKW70104
    SAP_AP     700     0016     SAPKNA7016
    BBPCRM     500     0015     SAPKU50015
    CPRXRPM     400     0015     SAPK-40015INCPRXRPM
    ST     400     0021     SAPKITL431
    BI_CONT     704     0004     SAPK-70404INBICONT
    ST-A/PI     01L_CRM570     0000          -
    ST-ICO     150_700     0022     SAPK-1507MINSTPL
    ST-SER     701_2008_2     0005     SAPKITLOQ5
    LM Components were updated for EHP1 SPS21, I installed SMD Agents in DEV and some QA servers and they work, but this one specially works as a fail over for a PRD cluster enviroment, and for that reason I'm using logical name, in SMSY it is configure with the same name, do you have any ideas?
    Thanks!!!

  • 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

Maybe you are looking for