Diagnostics Agent Installation in MCOD enabled systems

Hi Experts,
We are connecting MCOD anabled managed systems to Solution Mamager 7.1 SPS10.
But little confused with Dagnostics agent strategy; whether Agent-On-the-fly feature can be used in this case or not?
I am following SAP Note 1365123 - Installation of Diagnostics Agents.
Our MCOD structure is as below:
All Development systems on one physical host
All Quality systems on one physical host and
no MCOD enabled for Productive systems.
Thanks in advance,
Rahul

Hi Alexander,
Thank you for the quick reply. Can you clarify below:
MCOD database host is having 3 DB instances (of development systems) and all the 3 instances are connecting to single solution Manager system.
Does each DB instance require seperate Diag. agent or single Diag. agent will work for all the 3 instance to connect with solution manager?
Thanks in advance,
Regards,
Rahul

Similar Messages

  • Diagnostics Agent installation - which SID for the systems in your landscap

    Hi,
    I have a question in regads to installing the Diagnostics Agent on the systems in your landscape: ie. I want to install the Diagnostics Agent on all systems, and SAP suggests the system ID "DAA" as standard sid. From my experience there are no errors or exceptions when I use the system id DAA for a few or all systems.
    However, will I run into problems later on (for example, when using root cause analysis, etc.)? Can I use the standard system id DAA for several systems/hosts, or should I use a seperate system ID (DAA, DAB, DAC, etc.) for each Diagnostics Agent?
    thanks,
    Walter

    Hi,
    We have used same SIDs (the default DAA) for a few hosts in our landscape and this did not cause a problem.
    But in my opinion best to use DAA, DAB, DAC etc in order to remove any room for confusion for both the humans and the systems
    Regards,
    Srikishan

  • Unicode Kernel Diagnostics Agent  install on non_unicode kernel System.

    We have some ECC 6.0  ABAP systems that do not have a unicode kernel. The diagnostics agent setup guide for Netweaver 7.0 says you should have a unicode kernel DVD for the diagnostics agent install.   I was hesitant about using a unicode kernel for the SMD agent and a non-unicode kernel on the ECC 6.0 instance.  I tried installing the agent with the non-unicode kernel DVD and got an error that would not let me continue. Anybody have experience with this?

    Carl,
    David is Right, SMD is itself an SAP Instance(to be considered a seperate system-SAP Note:1365123) with its own exe. So it shouldn't be a problem.
    Regards,
    Jagan

  • Diagnostics Agent 711 - SAP Host Agent - Installation on a cluster environm

    Dear all,
    We have the following architecture in our productive environment :
    1. Cluster 01 is composed of 2 nodes.
       On Cluster 01, only "Database" and "Central Services" are running
       for 5 productive SAP systems.
    2. Cluster 02 is composed of 6 nodes.
       On Cluster 02, only "Central Instance" and "Application Server"
       are running for 5 productive SAP systems
    As read in "Diagnostics Agents installation Strategy", rules #4, slide 12 :
    ===================================================================
    - Do not install a Diagnostics Agent on host that only run Database
      or SAP Central Services.
    - Install a Agent on EACH host running a Central Instance (CI)
      and / or a Dialog Instance
    ===================================================================
    For our productive environment, we do have to install Diagnostics Agents 7.11 on cluster 02 where we have CI + AS running.
    Questions :
    1. How do we monitor "database" and "central services" data on cluster 01 (DB + CS) as far as no "Diagnostics Agents"
       are installed ?
    2. Do we have to install the new "SAP HOST AGENT" in our cluster 01 ?
    3. As written in "Downloading and Installing Package SAPHOSTAGENT"
       guide, "you only need to install the host agent host taht not have
       an SAP Component". Does it mean that the new "SAP HOST AGENT"
       will have to be installed on our cluster 01 to monitor "DB+CS" data ?
    4. What are for SAP a host that not have SAP Component ... ?
        "Database" and "Central Service" running for a SAP system should be consider as SAP Component or not ... ?
    5. What is the difference between the new "SAP HOST AGENT" delivered by SAP today 23.11.2009
        and the "Wily Host-Level Introscope Agent"
       delivered by CA ?
    Best regards
    PC

    Yes, it has to be installed.

  • Diagnostics Agent 7.11 on iSeries

    I"ve gone and got the installation master DVD and the Kernel DVD but cannot find the standalone Diagnostics Agent. Following You can download Diagnostics Agent installation DVDs from SAP Service Marketplace at: http://service.sap.com/swdc Download SAP Support Packages Entry by Application Group SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.0 EHP1 Entry by Component Agents for Managed systems DIAGNOSTICS AGENT 7.11 <choose operating system of managed> gets me to the area but I'm not seeing it for our system.
    Am I missing it or has it not been released for the iSeries yet? If not, then how is anyone else getting this installed if no agent is available?
    Thanks.

    Hi Ryan,
    the Diagnostics Agent Installation based on SAP NetWeaver 7.1 EhP1 is supporter for OS400. Unfortunately, the standalone SMD only installation kit was not release for the OS400 platform and therefore is necessary to use the standalone option found in the SAP NetWeaver 7.1 EhP1 installation media. You can follow the 711_Diag_Agent_Setup_Guide.pdf file attached in SAP note 1234387 to find the right components needed for this install.
    Best regards,
    Luis Gonzalez

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

  • FAM 8.0, Tomcat J2EE agent installation problem

    Hello:
    I was able to install FAM 8.0 in Tomcat 6.0.14 on Ubuntu (7.04) Linux. Everything seems fine. In the end, the applications I want to use with OpenSSO also make use of Tomcat 6.0.14. I noticed on the opensso users email list that the Tomcat 3.0 agent won't be available until early next year; but that the 2.2 agents should work with FAM 8.0. So, I got the the J2EE agent for Tomcat - SJS_Tomcat_Server_55_agent_2.2-01.tar.gz. The documentation makes no references to Tomcat 6, and I'm hoping this is due to the fact that Tomcat 6 was not available when the documentation was written.
    Does this agent work with Tomcat 6? I have this problem when installing the agent (agentadmin --install):
    $CATALINA_HOME environment variable is the root of the tomcat
    installation.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
    Invalid directory specified for the $CATALINA_HOME environment variable
    Invalid CATALINA_HOME directory :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14I can see in debug/agentadmin.log the following:
    [05/24/2008 13:06:37:684 PDT] FileSystemValidator : Is directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? true
    [05/24/2008 13:06:37:686 PDT] HomeDirValidator : Is $CATALINA_HOME directory /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? false
    [05/24/2008 13:06:37:686 PDT] Invalid CATALINA_HOME directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14This directory does indeed exist, and is accessible by the user I'm logged in as. It appears FileSystemValidator agrees with me, but HomeDirValidator has a problem. I tried this on both Ubuntu 6.04 and Mac OS X 10.5.2. Does this indicate that Tomcat 6 is not supported? Or is it indicative that neither OS on which I've tried to install the agent is officially supported?
    Thanks!
    Jeff

    Hi Denis:
    Before being redirected to another short term task, I did indeed get the Tomcat 6 agent to work. I probably won't be able to look at OpenSSO again seriously for another couple of months. :(
    I have the OpenSSO server running on Tomcat 6.0.14 on Ubuntu 6.x Linux running in a virtual machine on my Mac. I was not able to get the server to run directly on the Mac, and I cannot remember the reason at this time.
    But, as far as the agent goes, I run it again using Tomcat 6.0.14 on my Mac (Mac OS X 10.5.2), using the 1.5 JRE. I do have the agentapp war deployed as well as the agentsample web application to play with. In my catalina.out file:
    Jun 18, 2008 10:07:20 AM org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
    Jun 18, 2008 10:07:20 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive agentapp.war
    Jun 18, 2008 10:07:21 AM org.apache.catalina.startup.HostConfig deployWAR
    INFO: Deploying web application archive agentsample.war
    Jun 18, 2008 10:07:22 AM org.apache.coyote.http11.Http11Protocol start
    INFO: Starting Coyote HTTP/1.1 on http-8090
    Jun 18, 2008 10:07:22 AM org.apache.jk.common.ChannelSocket init
    INFO: JK: ajp13 listening on /0.0.0.0:8011
    Jun 18, 2008 10:07:22 AM org.apache.jk.server.JkMain start
    INFO: Jk running ID=0 time=0/16  config=nullI have no error messages is any Tomcat log file.
    I checked out the source code for the Tomcat v6 agent (2.2) on May 27, so I don't know how that compares to yours or what's been checked into CVS since my build. I also don't know what the OpenSSO NamingService is.
    I assume you used fully qualified domain names to specify the web application to be protected by agent as well as the OpenSSO server itself. The following is the output of the conversation when I run the agent installer script on my system. It has been redacted a bit (domain name and encryption key) to protect my client, but otherwise this is what I supplied to the installer:
    Enter the complete path to the directory which is used by Tomcat Server to
    store its configuration Files. This directory uniquely identifies the
    Tomcat Server instance that is secured by this Agent.
    [ ? : Help, ! : Exit ]
    Enter the Tomcat Server Config Directory Path
    [/opt/apache-tomcat-6.0.14/conf]: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
    Enter the fully qualified host name of the server where Access Manager
    Services are installed.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services Host: login.opensso.example.com
    Enter the port number of the Server that runs Access Manager Services.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services port [80]: 8080
    Enter http/https to specify the protocol used by the Server that runs Access
    Manager services.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services Protocol [http]:
    Enter the Deployment URI for Access Manager Services.
    [ ? : Help, < : Back, ! : Exit ]
    Access Manager Services Deployment URI [/amserver]: /opensso
    Enter the fully qualified host name on which the Application Server
    protected by the agent is installed.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Agent Host name: analysis.opensso.example.com
    $CATALINA_HOME environment variable is the root of the tomcat
    installation.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
    Choose yes to deploy the policy agent in the global web.xml file.
    [ ? : Help, < : Back, ! : Exit ]
    Install agent filter in global web.xml ? [true]:
    Enter the preferred port number on which the application server provides its
    services.                          
    [ ? : Help, < : Back, ! : Exit ]
    Enter the port number for Application Server instance [80]: 8090
    Select http or https to specify the protocol used by the Application server
    instance that will be protected by Access Manager Policy Agent.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Preferred Protocol for Application Server instance [http]:
    Enter the deployment URI for the Agent Application. This Application is used
    by the agent for internal housekeeping.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Deployment URI for the Agent Application [/agentapp]:
    Enter a valid Encryption Key.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Encryption Key [XXmyencryptionkeyXX]:
    Enter a valid Agent profile name. Before proceeding with the agent
    installation, please ensure that a valid Agent profile exists in Access
    Manager.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the Agent Profile name: testagent1
    Enter the path to a file that contains the password to be used for identifying
    the Agent.
    [ ? : Help, < : Back, ! : Exit ]
    Enter the path to the password file: /Users/jas/Development/opensso/tryout/agent_password
    SUMMARY OF YOUR RESPONSES
    Tomcat Server Config Directory :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
    Access Manager Services Host : login.opensso.example.com
    Access Manager Services Port : 8080
    Access Manager Services Protocol : http
    Access Manager Services Deployment URI : /opensso
    Agent Host name : analysis.opensso.example.com
    $CATALINA_HOME environment variable :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
    Tomcat global web.xml filter install : true
    Application Server Instance Port number : 8090
    Protocol for Application Server instance : http
    Deployment URI for the Agent Application : /agentapp
    Encryption Key : XXmyencryptionkeyXX
    Agent Profile name : testagent1
    Agent Profile Password file name :
    /Users/jas/Development/opensso/tryout/agent_password
    Verify your settings above and decide from the choices below.
    1. Continue with Installation
    2. Back to the last interaction
    3. Start Over
    4. Exit
    Please make your selection [1]: 1
    Updating the
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/bin/setclasspath.sh
    script with the Agent classpath ...DONE.
    Creating directory layout and configuring Agent file for Agent_001
    instance ...DONE.
    Reading data from file
    /Users/jas/Development/opensso/tryout/agent_password and encrypting
    it ...DONE.
    Generating audit log file name ...DONE.
    Creating tag swapped AMAgent.properties file for instance Agent_001 ...DONE.
    Creating a backup for file
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
    ...DONE.
    Creating a backup for file
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
    ...DONE.
    Adding SJS Tomcat Agent Realm to Server XML file :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
    ...DONE.
    Adding filter to Global deployment descriptor file :
    /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
    ...DONE.
    Adding SJS Tomcat Agent Filter and Form login authentication to selected Web
    applications ...DONE.
    SUMMARY OF AGENT INSTALLATION
    Agent instance name: Agent_001
    Agent Configuration file location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/config/AMAgent.properties
    Agent Audit directory location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/audit
    Agent Debug directory location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/debug
    Install log file location:
    /Users/jas/Development/opensso/tryout/tomcat_v6_agent/logs/audit/install.log
    Thank you for using Access Manager Policy Agent
    [jaslap:tryout/tomcat_v6_agent/bin] jas% Can you post the exception details you're getting. That might help someone diagnose the problem.
    Take it easy,
    Jeff

  • Diagnostics agent in managed systems

    Hi Gurus,
    We are trying to set up RCA in solution manager.
    For this, we need to install diagnostics agents in managed systems.
    But, i think those agents are already installed in out systems and am not sure of it. Can anyone please let me know how can i find if diagnostic agent is installed in managed system.
    Please do clarify one more thing, we need Solution manager diagnostics in solman system and solution manager diagnostics agents in managed systems. Am i correct??
    Please help me out on this.
    Regards,
    Ram.

    Hi
    I have gone through all the documents that specified earlier itself.
    Our OS is IBM iSeries, so we have multiple SAP systems installed in a single LPAR.
    So all the diagnostics agents for all those systems installed in that LPAR should exist in that LPAR itself.
    In that way, we have DAA folder in usr/sap of that LPAR. In that DAA folder, we have mutliple folder called ADMA97, ADMA98 etc. So these ADMnn folders represent agents for each system right?. So, how to idenfify that particular agent is for which system? All i could make out is from SYS/profile folder in that DAA folder. I have checked the profiles and identified the host name related to a paricular SAP system.
    As per SAP document, these diagnostic agents are automatically installed with system installation as of SAP Web AS 7.0 SR3. All our systems are above that level and i still see some diagnostic agents are not installes for some SAP systems. Is there any possibility like this? SO if i again install the missing diagnostic agents, will they be created under the same /usr/sap/DAA folder or will it create a new folder??
    Hope am clear...
    Awaiting your inputs and thanksin advance.
    Regards,

  • Managed System Configuration step Assign Diagnostics Agent

    Dear Experts,
    We've newly instaled solution manager system 7.0 Ehp1 via latest sp stack 25 on aix 6.1, we've completed initial and basic configuraiton successfully via solman_setup, and instaled wily introscpe on same host with solution manager system,
    Now i am trying to managed system configuration for solution manager system via solman_setup step Assign Diagnostics Agent as demo link below
    https://service.sap.com/~sapidb/011000358700001735062008E
    I opend http://>SOLMANHOST>:<SOLMANPORT>/smd/go/ADMIN_AGENT
    >> Agent Candidates Management
    >>  Connection Parameters
    >> Custom SLD Parameters > Aply and the selected the SMD instance then trying to attached via password SMD_ADMIN
    But agent registration is waiting, SMD_ADMIN user is creating when i execute intial configuration, after i change the intial password, password is correct, so why the agent state is waitng status, i also push sld Setting for all from SMD view tab,
    I've also try to restart SMD agent, /usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log file after restart
    Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
    Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       ===> Establishing connection to server 'ms://ccisolman:8101/P4
    Oct 28, 2010 11:07:28 AM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
    Oct 28, 2010 11:07:32 AM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is  Thu Oct 28 23:07:32 EEST 2010     
    Best Regards

    hi
    pls chk again your sld parameters and check the correct user name, password entered in agent connection management under CUSTOM SLD(in agent candidates management)
    jansi

  • Assign an Diagnostics Agent to two System Types

    On my system I have installed SAP using a C-name but the database which is on the same server uses the physical server name.  The server has the diagnostics agent installed but when I go to managed system configuration I am only able to assign that agent to one of the system types.  Is there a way I can assign the agent to both the ABAP and the database systems?

    Hi Mary,
    Install a new diagnostic agent on your physical host.
    Regards,

  • CCMS agent installation

    Hi Experts,
    I am doing SAP CCMS agent installation to monitor a non-SAP system which will be monitored by a Central monitoring system.
    I have followed all the steps as:
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/adf7409b9d8531e10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e2/eff640fa4b8631e10000000a1550b0/frameset.htm
    1. communication user CSMREG in Central monitoring system.
    Created the CSMCONF start file for CCMS agents in monitoring system.
    2. CCMAGENT.SAR , SAPOSCOL.SAR ,  INSTALL_WIN.SAR
    And done the configurations required in the monitored system.
    3. Register the CCMS agent with CEN and start the agent. By following this step:
    <hostname>\saploc\prfclog\sapccmsr.exe -R*
    while registering the CCMS agent ,
    I ma getting this...
    This CCMS agent program sapccmsr is able to actively report alert data into the monitoring system[CEN], which is the central monitoring system.
    to enable this feature, you have to setup the user CSMREG in [CEN].
    After entering the RFC logon info for the user,
    client:001
    user:CSMREG
    language:EN
    host name:
    load balancing:n
    system number:01
    router sting :optionla
    trace lavel:0
    password for CSMREG user:********
    Its showing this error:
    ERROR: RFC error during logon: 105 DESTINATION_NOT_EXIST
    How to solve this?
    Do I have to do any RFC configuration in the Central monitoring system(as I want to monitor a non-SAP system)?
    urgently required.
    Any help will be appreaciated.
    Regards
    Manisha

    Hi Manisha,
    Yes you will have to create a RFC and a suitable RFC user in the Central Monitoring System (CEN) via txn RZ21 to monitor these remote systems.
    Please follow this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/a8/adf7409b9d8531e10000000a1550b0/frameset.htm
    Please award suitably if helpful.
    Regards, Dibya

  • Introscope Agent Installation

    Hi
    I am installing the Wily Introscope Enterprise Manager and one Agent according to the "Introscope Version 7.0 Installation Guide for SAP"
    I got stuck with the installation instruction Below .. Can any one help me how to do the below
    Agent Name
    You should assign a unique name to each SAP J2EE node that is Introscope-enabled. This so-called agent name is assigned by an additional Java VM option (referred to as <agentName> below). SAP suggests the following naming convention for the agent name:
    <agentName>=SID_Product_Nodename
    Where the placeholder mean the following:
    Placeholder Explanation Example
    <b>SID</b> SystemID EPP, EPQ, EPD
    Product Identifier for product usage EP, XI, IPC
    <b>Nodename</b> J2EE node name / directory server0
    Note: It is not necessary to integrate the host name into the agent name, since the host name is assigned automatically to the agent.
    Using a unique naming convention for all agent installations helps to group agents that belong to the same installation together.
    Please help me
    Thanks

    Hi,
    The instructions on Introscope Installation Guide suggests a naming convention for the agent name to identify this agent in Introscope.
    The SID is the system identifier of the host, where you have installed the agent.
    The Product depends on the product installed in this server (Enterprise Portal- EP, Process Integration - XI...).
    For the Nodename, you have to specify on which node you have installed the agent. As introscope agent has to be installed on each nodes if you have several nodes on your engine.
    So if you have a J2EE engine with two servers nodes with Enterprise Portal product, and you install an agent on each nodes, you will have two agents named EPP_EP_server0 and EPP_EP_server1.
    Hope it helps,
    Regards,
    Paula

  • Daa agent installation for solman7.1

    HI
      I uninstalled the Diagnostics Agent in my solution manger 7.1 system  with  swpm , but iam uanble to install the DAA  again .
    the thing is if i click the sapinst , it  shows the hostagent installation , then it asks the kernal  folder . i located the kernal folder , i got a message
    installation completed. but  Daa icon is not in my sapmmc, and  no content  D:\usr\sap\DAA\SMDA98\work. can  any one guide me how to install the
    DAA For latest level. solman7.1 mssql and windows2008 is my environment
    regards
    vreddy

    Hi
      i restart the server , now DAA IS Visible in sapmmc , but sad thing it is not updated, it SHOWS The previous patchlevel. i am attaching the log file
    These are The Log File Content:
    trc file: "dev_smdagent", trc level: 1, release: "720"
    sysno      98
    sid        DAA
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    D:\usr\sap\DAA\SYS\profile\DAA_SMDA98_ACPSOLMAN
    pid        2672
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Fri Mar 14 11:12:55 2014
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : D:\usr\sap\DAA\SMDA98\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=0
      arg[ 3] : pf=D:\usr\sap\DAA\SYS\profile\DAA_SMDA98_ACPSOLMAN
      arg[ 4] : -hostvm
      arg[ 5] : -nodeName=smdagent
      arg[ 6] : -file=D:\usr\sap\DAA\SMDA98\SMDAgent\smdagent.properties
      arg[ 7] : -jvmFile=D:\usr\sap\DAA\SMDA98\work\jstart.jvm
      arg[ 8] : -traceFile=D:\usr\sap\DAA\SMDA98\work\dev_smdagent
      arg[ 9] : -javaOutFile=D:\usr\sap\DAA\SMDA98\work\jvm_smdagent.out
    F 
    F Fri Mar 14 11:12:55 2014
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : D:\usr\sap\DAA\SMDA98\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_26
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.036 1.6-b03
    F    jvm library name  : jvm.dll
    F    library path      : D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin\server;D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin
    F    executable path   : D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 3532] MtxInit: 10000 0 2
    M  [Thr 3532] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 3532] CCMS: alert/disable_j2ee_monitoring set. CCMS Monitoring of J2EE Engine switched off.
    F 
    F Fri Mar 14 11:12:55 2014
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 114, changelist 1291253, NTAMD64, optU (Dec  1 2011, 23:12:00)
    F    arg[ 6] = -DSAPSTARTUP=1
    F    arg[ 7] = -DSAPSYSTEM=98
    F    arg[ 8] = -DSAPSYSTEMNAME=DAA
    F    arg[ 9] = -DSAPMYNAME=ACPSOLMAN_DAA_98
    F    arg[10] = -DSAPDBHOST=
    F    arg[11] = -DSAPINFO=DAA_98_smdagent
    F    arg[12] = -Dj2ee.dbhost=
    F    arg[13] = -Dsun.java.launcher=jstart
    F    arg[14] = -Dsun.java.command=com.sap.smd.agent.launcher.SMDAgentLauncher run jcontrol
    F    arg[15] = -Djstartup.mode=JSTART
    F    arg[16] = -Djstartup.whoami=java
    F    arg[17] = -Djstartup.ownProcessId=2672
    F    arg[18] = -Djstartup.ownHardwareId=T0176246063
    F    arg[19] = -Djstartup.debuggable=yes
    F    arg[20] = -DLoadBalanceRestricted=false
    F    arg[21] = -XdebugPortRange:59821-59821
    F    arg[22] = -Denv.class.path=
    F    arg[23] = -Dsys.global.dir=D:\usr\sap\DAA\SYS\global
    F    arg[24] = -Dapplication.home=D:\usr\sap\DAA\SMDA98\exe
    F    arg[25] = -Djava.class.path=D:\usr\sap\DAA\SMDA98\exe\jstart71.jar;D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\jvmx.jar;D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\jvmx_tools.jar;D:\usr\sap\DAA\SMDA98\exe\jre\lib\iqlib.jar;D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\tools.jar;lib\iaik\iaik_jce.jar;lib\iaik\iaik_jsse.jar;lib\iaik\iaik_smime.jar;lib\iaik\iaik_ssl.jar;lib\iaik\w3c_http.jar;..\exe\jstartupapi.jar;..\exe\jstartupimpl.jar;lib\patch_7.10.1.0.20110706111553\launcher\smdagentlauncher.jar;..\exe\jperflib.jar
    F    arg[26] = -Djava.library.path=D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin\server;D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin;D:\usr\sap\DAA\SMDA98\j2ee\os_libs;D:\usr\sap\DAA\SMDA98\exe\sapjvm_6\bin;D:\usr\sap\DAA\SMDA98\exe;\Windows\System32;C:\usr\sap\saprouter;C:\Windows\System32;C:\j2sdk1.4.2_42-x64\bin;C:\Windows\System32\xcopy.exe;D:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll;D:\usr\sap\DAA\SYS\exe\uc\NTAMD64
    F    arg[27] = -DP4ClassLoad=P4Connection
    F    arg[28] = -Xmx256m
    F    arg[29] = -Xms256m
    F    arg[30] = -XX:MaxPermSize=128m
    F    arg[31] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    F  [Thr 4420] *** LOG => SfCJavaVm: Java VM started.
    F  ********************************************************************************
    F  Main method call:
    F  com/sap/smd/agent/launcher/SMDAgentLauncher.main()
    F    arg[ 0] = run
    F    arg[ 1] = jcontrol
    F  ********************************************************************************
    F 
    F [Thr 4420] Fri Mar 14 11:12:56 2014
    F  [Thr 4420] *** LOG => State changed from 0 (Initial) to 1 (Waiting to start).
    F  [Thr 4420] *** LOG    state real time: 2.078 CPU time: 0.140 sys, 1.921 usr
    F  [Thr 4420] *** LOG    total real time: 2.078 CPU time: 0.140 sys, 1.921 usr
    F  [Thr 4420]
    F 
    F [Thr 4420] Fri Mar 14 11:13:19 2014
    F  [Thr 4420] *** LOG => State changed from 1 (Waiting to start) to 2 (Starting framework).
    F  [Thr 4420] *** LOG    state real time: 23.346 CPU time: 0.156 sys, 2.109 usr
    F  [Thr 4420] *** LOG    total real time: 25.424 CPU time: 0.296 sys, 4.031 usr
    F  [Thr 4420]
    F  [Thr 4420] *** LOG => State changed from 2 (Starting framework) to 3 (Running).
    F  [Thr 4420] *** LOG    state real time: 0.031 CPU time: 0.000 sys, 0.046 usr
    F  [Thr 4420] *** LOG    total real time: 25.456 CPU time: 0.296 sys, 4.078 usr
    F  [Thr 4420]
    F 
    F [Thr 4228] Fri Mar 14 11:13:28 2014
    F  [Thr 4228] *** LOG => State changed from 3 (Running) to 23 (Disconnected).
    F  [Thr 4228] *** LOG    state real time: 8.437 CPU time: 0.031 sys, 0.156 usr
    F  [Thr 4228] *** LOG    total real time: 33.893 CPU time: 0.328 sys, 4.234 usr
    F  [Thr 4228]
    F  [Thr 4228] *** LOG => State changed from 23 (Disconnected) to 10 (Starting apps).
    F  [Thr 4228] *** LOG    state real time: 0.000 CPU time: 0.000 sys, 0.000 usr
    F  [Thr 4228] *** LOG    total real time: 33.893 CPU time: 0.328 sys, 4.234 usr
    F  [Thr 4228]
    F  [Thr 4228] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
    F  [Thr 4228] *** LOG    state real time: 0.421 CPU time: 0.031 sys, 0.718 usr
    F  [Thr 4228] *** LOG    total real time: 34.315 CPU time: 0.359 sys, 4.953 usr
    F  [Thr 4228]
    F 
    F [Thr 4228] Fri Mar 14 11:14:03 2014
    F  [Thr 4228] *** LOG => State changed from 3 (Running) to 23 (Disconnected).
    F  [Thr 4228] *** LOG    state real time: 35.234 CPU time: 0.000 sys, 0.203 usr
    F  [Thr 4228] *** LOG    total real time: 69.549 CPU time: 0.359 sys, 5.156 usr
    F  [Thr 4228]
    so my question is how to update the patch level to 167.
    regards
    vreddy

  • Which version Diagnotics Agent to install for ERP6 systems using SM 7.1 ?

    Hi,
    I have a recently installed Solution Manager 7.1 system and would now like to add our managed systems for monitoring.
    Our managed systems are all running NW EHP2 / ERP6 EHP5 and I have installed the latest SAPHostagent 7.2 on each of these systems. These systems are non unicode running on Suse Linux Enterprise 10.
    I'm confused as to which version Diagnostic Agent to install for this setup. Under Solution Manager 7.1 in SWDC the managing agents are for a 7.3 installation only and the prerequisites require Suse Linux Enterprise 11. I'm not sure whether I can use agents located under older Solution Manager systems.
    With the above information in mind can you help ?
    Thanks.
    Regards,
    Nelis

    Hi,
    Please look in the table provided in below link.
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-Whichagentversionshouldbeused%3F
    Regards
    Vivek

  • Diagnostics agent not getting registered in Solution Manager

    Hello SAP Experts,
    I am using Solution Manager 7.1 SP Stack 12. I installed diagnostics agent on one of the managed systems and fired the command below for registering it in Solution manager (since I did not do this during diag agent installation):
    /usr/sap/DAA/SMDA<instance no>/script/smdsetup.sh managingconf hostname:"sapms://<FQDN of Solman>" port:"81<instance no of Solman>" user:"smd_admin" pwd:"<password"
    This command returned successful message. However, when I login to Solution manager and go to Agent administration, I am unable to see the above managed system diagnostics agent. Please help.
    Thanks & Regards,
    Kunal.

    Hi Adi,
    Thanks for the reply. I found the below SMDSystem.7.log at location /usr/sap/DAA/SMDA98/SMDAgent/log
    Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: smd_admin
    Apr 24, 2014 1:21:05 PM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server ms://<hostname>/P4 failed - error counter: 1690 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: there are no access points for service: P4 registered on the message server]
    Regards,
    Kunal.

Maybe you are looking for