Wily Introscope Agent not visible

Hi,
I have connected my ERP to Solution manager, I could see Introscope agent in green status for two j2ee nodes but the same is not visible from workstation or webview/workstation. Solution manager is 7.0 EHP1. Agent version is ISAGENT.8.1.0.0
I only SAP HostAgent process only in webview/workstation.
If anyone of you come across this situation please let me know.
Regards
KVR

Hi Vikranth (Bro).
Please find the Link to LMServices tools in marketplace.
I have checked in both SPS21,22 and 23..
Downloads>Application by index>click on S>select solution manager>solution manager EHP1-->select the sps 21/22/23 .
LMSERVICE05_0-20004805.SCA SP05 for SOLMANDIAG 7.01    Info  SOLMANDIAG 7.01 # OS independent
In sps 21 u will get sp05 of LMservices.
Regards
Janakiram Reddy

Similar Messages

  • Wily Introscope agent not deploying on PI

    Hi all!
    We have a solution manager 7.0 system, recently upgraded to stack 26. We have several PI landscapes, all connected to solman. Recently, i was able to update the Introscope agent on one PI 7.1 SP3 enh. pack 1 system without any problems, using introscope agent deployment in solman_workcenter -> Root Cause analysis -> Diagnostics Setup -> managed systems -> Introscope agent.
    With a 711 sp4 enh 1 system, i'm struggeling to get the agent deployed/upgraded on the same manner. The errors i'm getting are:
       ISAgent Setup on node: servername - 2352050 - server0
    Operation Failed
       Introscope Agent Configuration
    Remote Operation Failed
       Introscope Agent Extraction
    Remote Operation Succeeded
       Updating Introscope Agent Profiles
    Remote Operation Failed
       ISAgent Profile Generation: IntroscopeAgent.profile
    Remote Operation Succeeded
       Detailed Information
    Failed to get vm parameters from database - com.sap.smdagent.vmmanager.VMManagerException: Failed to get Instance properties - 23520
       Introscope Agent Connector Generation
    Remote Operation Failed
       Detailed Information
    Introscope Agent Connector generation is done using JDK at: null
       Detailed Information
    Failed to create Introscope Agent Connector at: J:\usr\sap\DAA\SMDA97\SMDAgent\applications.config\com.sap.smd.agent.application.wily\BytecodeAgent\ISAGENT.8.2.3.5-2011-01-14\wily\connectors - java.lang.NullPointerException 
    I'm using the same (SAP default) instrumentation profile as on the other PI servers. Also using the same autoprobe directives:
    sap_typical.jar
    sap_ep.jar
    sap_ep_iview.jar
    sap_xi_typical.jar
    I've read several forum posts regarding this issue, none aswered and none giving a clue in what direction i am to look for an answer. The only difference between the systems is patch levels and that the server experiencing the problems has an additional java node. Is it a problem with the autoprobing directives, should something in the instrumentation profile be changed? (if so, is there any available documentation regarding this?)
    If someone is able to point me in the right direction i'd appreciate it.
    Regards!

    Hi Diego,
    The saphostagent version on all the PI sattelite systems is the same, 711, patch 137, since all systems are 711 systems.
    If I check run SMDsetup on solman it shows me diagn. agent version 7.01.2.0.20081119084015. Based on the last long string, this looks kind of old..
    If i check agent administration in SOLMAN i see: 7.01.9.0.20110214073110 for the PI sattelite systems, i'm guessing this is the DAA agent version?
    The wily agent we're trying to deploy is ISAGENT.8.2.3.5-2011-01-14.. So.. Looks like something is to be upgraded on the solution manager side? All these agents and different ways of getting version numers make me dizzy.

  • Wily Introscope Agent does not start

    Hi,
    i am installing Solution Manager Diagnostics on a Solution Manger 7.0 System. At the moment i am on the point to install the Wily Introscop Agent and i have following problem:
    At first i tried the automatic setup and deployed the agent with JSPM and it seemed to work. I see "ISAGENT" on the System Information -> All Compontents over http://0/smd/admin and there is no log directory in the wily directory?
    Does anybody has an idea whats wrong?
    Best Regards,
    Stefan
    Edited by: Stefan on Feb 17, 2009 8:57 AM
    Edited by: Stefan on Feb 17, 2009 9:31 AM

    Hello Stephan,
    1. Wily IS Agent (2 agents) is installed ONLY in SOLMAN system.
    2. Then, with SOLMAN_SETUP Guided procedure, in third phase (Managed System Configuration),
        you deploy the Wily IS Agent to your managed system.
    To summarize :
    1. Install the ISAGENTxxx.SCA in SOLMAN only !
    2. Start the SOLMAN_SETUP guided procedure
    3. Phase I - Initial Configuration
        Phase II - Basis Configuration
        Phase III - Managed System Configuration.
    In Phase III, there are 6 steps :
    1.     Connect Managed system
    2.     Check Prerequisites
    3.     Manual Configuration
    4.     Diagnostics Configuration
    5.     Wily Introscope Configuration
    6.     Create Logical Components
    The Wily IS Agent (2 agents : IS Agent wich monitored JAVA instance and Wily Host-level Agent which a sub-process of the SMD Agent) is configured and STARTED here.
    So, you cannot start / stop by any OS command the Wily IS Agent.
    You start it from SMD.
    Hope it help you.
    Best regards
    Pascal Cuennet

  • Wily Introscope is not running in Solution Manager 7.1

    Hello Experts,
    wily Introscope is not running in solution manager system,
    below error getting in log, solution manager is running on windows server and how to start wily in windows.
    8/23/14 11:58:50.088 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 9.1.0.0 (Build 581006)
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Introscope installation at: D:\usr\sap\CCMS\apmintroscope\.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] CA Introscope(R) Version 9.1
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Copyright (c) 2011 CA. All Rights Reserved.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope(R) is a registered trademark of CA.
    8/23/14 11:58:50.089 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting Introscope Enterprise Manager...
    8/23/14 11:58:50.090 AM IST [INFO] [WrapperSimpleAppMain] [Manager]
    ****** CA Wily Introscope License ******
      type = em-sap
      rev = 30
      cid = sap-ags
      organization = SAP Active Global Support
      reg-id = sap-end-user
      email = none
      sum = 27618b562bc2239e3cf71d9542c76df4
    8/23/14 11:58:50.091 AM IST [INFO] [WrapperSimpleAppMain] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.
    8/23/14 11:58:50.113 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting server...
    8/23/14 11:58:52.343 AM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections are enabled
    8/23/14 11:58:52.343 AM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    8/23/14 11:58:52.412 AM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    8/23/14 11:58:52.628 AM IST [ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Local Users and Groups realm is misconfigured. Error using new settings for Realm: Non existent user "analyst" referenced in "CEM Analyst" group.
    8/23/14 11:58:52.645 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
    8/23/14 11:58:52.655 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 9.1.0.0 (Build 581006)
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Introscope installation at: D:\usr\sap\CCMS\apmintroscope\.
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] CA Introscope(R) Version 9.1
    8/23/14 12:02:31.584 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Copyright (c) 2011 CA. All Rights Reserved.
    8/23/14 12:02:31.585 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope(R) is a registered trademark of CA.
    8/23/14 12:02:31.585 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting Introscope Enterprise Manager...
    8/23/14 12:02:31.585 PM IST [INFO] [WrapperSimpleAppMain] [Manager]
    ****** CA Wily Introscope License ******
      type = em-sap
      rev = 30
      cid = sap-ags
      organization = SAP Active Global Support
      reg-id = sap-end-user
      email = none
      sum = 27618b562bc2239e3cf71d9542c76df4
    8/23/14 12:02:31.586 PM IST [INFO] [WrapperSimpleAppMain] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.
    8/23/14 12:02:31.602 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting server...
    8/23/14 12:02:31.958 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections are enabled
    8/23/14 12:02:31.959 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    8/23/14 12:02:32.030 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    8/23/14 12:02:32.287 PM IST [ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Local Users and Groups realm is misconfigured. Error using new settings for Realm: Non existent user "analyst" referenced in "CEM Analyst" group.
    8/23/14 12:02:32.306 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
    8/23/14 12:02:32.321 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
    8/23/14 12:37:05.225 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 9.1.0.0 (Build 581006)
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.6.0_23" from Sun Microsystems Inc.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Using Introscope installation at: D:\usr\sap\CCMS\apmintroscope\.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] CA Introscope(R) Version 9.1
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Copyright (c) 2011 CA. All Rights Reserved.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope(R) is a registered trademark of CA.
    8/23/14 12:37:05.226 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting Introscope Enterprise Manager...
    8/23/14 12:37:05.227 PM IST [INFO] [WrapperSimpleAppMain] [Manager]
    ****** CA Wily Introscope License ******
      type = em-sap
      rev = 30
      cid = sap-ags
      organization = SAP Active Global Support
      reg-id = sap-end-user
      email = none
      sum = 27618b562bc2239e3cf71d9542c76df4
    8/23/14 12:37:05.228 PM IST [INFO] [WrapperSimpleAppMain] [Manager] The Introscope Enterprise Manager is set to run in StandAlone mode.
    8/23/14 12:37:05.249 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Starting server...
    8/23/14 12:37:05.644 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections are enabled
    8/23/14 12:37:05.644 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    8/23/14 12:37:05.728 PM IST [INFO] [WrapperSimpleAppMain] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    8/23/14 12:37:05.994 PM IST [ERROR] [WrapperSimpleAppMain] [Manager] The EM failed to start. Local Users and Groups realm is misconfigured. Error using new settings for Realm: Non existent user "analyst" referenced in "CEM Analyst" group.
    8/23/14 12:37:06.014 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Shutting down the Isengard server
    8/23/14 12:37:06.028 PM IST [INFO] [WrapperSimpleAppMain] [Manager] Orderly shutdown complete.
    Please assist me on this
    Best Regards
    Hanuman

    Hello Srivastav,
    i am getting below problem in wily introscope log
    9/01/14 11:22:02.675 AM IST [ERROR] [WrapperSimpleAppMain] [Manager.Acceptor] Failed to bind to server socket
    java.net.BindException: Address already in use: bind
      at sun.nio.ch.Net.bind(Native Method)
      at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
      at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
      at com.wily.isengard.postofficehub.link.server.Acceptor.<init>(Acceptor.java:72)
      at com.wily.isengard.postofficehub.link.server.ConnectionListenerFactory.create(ConnectionListenerFactory.java:31)
      at com.wily.isengard.postoffice.server.PostOfficeHubServer.startIncomingConnectionListener(PostOfficeHubServer.java:261)
      at com.wily.isengard.postoffice.server.PostOfficeHubServer.startAllIncomingConnectionListeners(PostOfficeHubServer.java:235)
      at com.wily.isengard.postoffice.server.PostOfficeHubServer.acceptIncomingHubConnections(PostOfficeHubServer.java:103)
      at com.wily.isengard.api.server.IsengardControllerServer.acceptIncomingConnections(IsengardControllerServer.java:207)
      at com.wily.isengard.api.samplemain.SampleMain.acceptIncomingConnections(SampleMain.java:117)
      at com.wily.introscope.server.enterprise.EnterpriseServer.initialize(EnterpriseServer.java:708)
      at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:358)
      at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
      at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:301)
      at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:280)
      at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1444)
      at com.wily.introscope.em.internal.Activator.startEM(Activator.java:116)
      at com.wily.introscope.em.internal.Application.start(Application.java:27)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
      at org.eclipse.core.launcher.Main.main(Main.java:30)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:244)
      at java.lang.Thread.run(Thread.java:662)
    9/01/14 11:22:02.679 AM IST [INFO] [WrapperSimpleAppMain] [Manager.PostOfficeHub] Server listening for incoming default socket connections on port 6001
    9/01/14 11:22:02.682 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Connection Initiator listening...
    9/01/14 11:22:02.684 AM IST [INFO] [WrapperSimpleAppMain] [Manager.MMHotDeployEntity] Will monitor D:\usr\sap\CCMS\apmintroscope\deploy for new files every 60 seconds
    9/01/14 11:22:02.685 AM IST [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager started with management module warnings.
    9/01/14 11:22:42.883 AM IST [INFO] [PO:main Mailman 1] [Manager.LoadBalancer] Loaded loadbalancing.xml
    9/01/14 11:23:31.817 AM IST [INFO] [btpool0-1] [Manager] User "Admin" logged in successfully from host "localhost"
    9/01/14 11:23:31.825 AM IST [INFO] [btpool0-1] [Manager] request.getContextPath() /webview
    9/01/14 11:23:31.826 AM IST [INFO] [btpool0-1] [Manager] Login event Admin 1667ryb11leum 10.1.0.133 true
    9/01/14 11:51:30.061 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409164200000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.063 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409077800000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.064 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409423400000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.066 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409337000000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.067 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1409250600000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.088 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1406831400000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.089 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1408991400000.data seems to be OK - not sure what to do with append inputs
    9/01/14 11:51:30.090 AM IST [INFO] [Carver data management] [Manager] Existing query file data\archive\1408905000000.data seems to be OK - not sure what to do with append inputs
    Please help me to sort this issue,
    Best Regards,
    Hanuman Chinthalwar

  • Wily Introscope agent settings

    Hi,
    After the recent EHP1 upgrade on Solution manager,when we go to introscope agent configuration(Diagnostics Setup->Managed Systems->Introscope Agent)and select the system,it can't able to retrieve the current settings(i.e.,J2ee node).
    {through we have select right Enterprise Manager}
    We have also completed the post installation activities and successfully completed both the Initial and Basic configuration in solman_setup.
    Any inputs??????
    Thanks and Regards,
    Edited by: Venkata Nooney on Jan 28, 2010 5:10 PM

    Hi,
    You will need Enterprise Manager 8.x for Solution manager EHP1 SP3 and up.
    check this Note: 1273028- Introscope 8 release Notes for more details.
    Check if the wily agents on the managed systems are connected to Enterprise manager using the webview
    http://hostname.publix.com:8081/webview
    Thanks,
    Harini

  • Problem Remote Deploy Wily Introscope Agent

    Hi,
    I installed Wily Introscope EM and the Diagnostic Agent on Solution Manager (EhP1).
    Now, if I understand it, I can do a remote deploy of Introscope Agent, for example on Enterprise Portal.
    How can I do?
    Best Regards.
    Diego.

    Hi Diego,
    Do you also install an SMD agent on the portal system which one you want to managed via RCA? Also you need to run the Setup Wizard for Managed Systems for your portal.
    Please check SAP Note 1365123 - Installation of Diagnostics Agents. In this note you will find an attachment Agent_Installation_Strategy.ppt - describe the installation strategy of SMD agents and all agent rules which you need to follow.
    So one part is to get RCA running:
    1. Install a SMD agent per managed host.
    2. Define the technical system in SMSY Normal you have an SLD in your landscape and connect the Solution Manager to it or use the SLD from Solution Manager. After you define the technical system in SMSY or via SOLMAN_SETUP ->Managed System Configuration you go to Diagnostics Setup.
    3. You access this via Diagnostics work center or direct link http://solman_fqdn:<port>/smd
    4. Next go to Managed System -> Setup Wizard -> Select your to managed system <SID> - > check that system is Diagnostics Relevant (if not click on the managed products and set the relevant product for diagnostic u2013 also verify the Landscape setting light are green u2013 this means the technical system is well defined in SMSY)
    5. Click Setup <SID> Button -> on next screen you need to fill out all Java / Abap connection parameters (for the setup of Java systems you need a userid with j2ee admin rights)
    6. Please set the SMD agent in the right table u2013> Click on details arrow and then select the managed systemu2019s SMD agent and click on the set button. The SMD agent will now reboot wait until the agent is back -> Click on the Refresh button to see the status.
    7. Click Next and on the next screen you get a Summary of all setup steps
    8. Click on Setup. After the setup finished (all steps are green)
    9. Click on quit.
    Before your can deploy the IS agent from the Solution Manager you need to deploy the IS agent files via SDM to the Solution Manager. You can download the deployable IS agent from SAP Service Market Place:
    Support Packages and Patches -> Entry by Application Group -> SAP Technology Components -> SAP SOLUTION MANAGER -> SAP SOLUTION MANAGER 7.0 EHP 1 -> Entry by Components -> Agents for managed systems -> select your version for your IS EM and download the deployable agent via SolMan Diagnostics (File name like ISAGENTSMD801_01-10007435.SCA)
    Now you can start with the setup of the Introscope Agent (on the left menu bar under application selection).
    On the selection screen select first your IS Enterprise Manager then the IS Agent settings the relevant system.
    In the table select the J2EE node for which want you setup the agent (this need to be done for each Server node u2013 the IS agent runs inside of the J2EE node per server)
    Then click on Setup Introscope Agent u2026 Button u2013> select the Autoprobe Directives and click the Apply button. If every steps doen you need to reboot your managed JAVA system.
    Now you are ready to use the RCA tools and also see data in the IS Enterprise Manager.

  • Wily Introscope is not running in Solution Manager 7.1 and tech monitoring

    Hi Experts,
    we are able to log in wily introscope, But metrics(values) are not coming in wily
    we re started the solution manager server, that port is working fine now, Please assist me on this to fix issue find log as attachment.
    2)we configure the technical monitoring in our solution manager system but metrics are not coming for dialog response time in dash board. which extractor i need to check how to troubleshoot,
    thanks in advance for you help
    Best Reg

    Hi Srivastav.
    Actually i am new to solution manager, and we have done basic steps of solution manager like
    system preparation,basic configuration,managed system configuration and technical monitoring,
    in tech monitoring system monitoring,and EUEM and we are planing to perform DVM and RBPD,
    my solution manager system is installed on windows 2008 server, version is 7.1 SP 7,
    currently we facing issue in wily introscope and technical monitoring dash boards metrics are not appearing and please tell me how to close the thread ,
    Best Regards,
    Hanuman

  • Wily Introscope does not start

    Hi there,
    I've installed the Wily Introscope Enterprise Manager and when i try to start, the error below happens:
    java.lang.RuntimeException: Application "com.wily.introscope.em.application" could not be found in the registry. The applications available are: org.eclipse.e
    quinox.app.error.
            at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:236)
            at org.eclipse.equinox.internal.app.EclipseAppContainer.start(EclipseAppContainer.java:92)
            at org.eclipse.equinox.internal.app.Activator.addingService(Activator.java:129)
            at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064)
            at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1042)
            at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:967)
            at org.eclipse.osgi.framework.internal.core.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:94)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1224)
            at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
            at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
            at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEventPrivileged(Framework.java:1603)
            at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEvent(Framework.java:1578)
            at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.<init>(ServiceRegistrationImpl.java:103)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.createServiceRegistration(BundleContextImpl.java:657)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:609)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:675)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:359)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
            at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
            at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
            at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
            at org.eclipse.core.launcher.Main.main(Main.java:30)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.zerog.lax.LAX.launch(DashoA8113)
            at com.zerog.lax.LAX.main(DashoA8113)
    Anybody has already seen it?
    Thanks in advance,
    Dany Anderson

    Hi
    I have nearly the same error. May you share your solution?
    Thanks in advance!
    BR, Manuel

  • Wily Introscope Agent

    Guys,
    I have the following question.  In a system which has CI + 5 applications, should  just I install Wily Introscope on CI or CI and on the 5 applications? or just the CI is enough to cover the performance analysis?
    Thank you so much
    Re

    Hello,
    Willy enterprise manager is needed only on Solution Manager I think.
    Willy agents are, if needed, to be installed on all app servers as well. I think whichever host you want to monitor, the agent is needed there.
    Thanks

  • CA Wily Introscope was not found in LMDB

    Hello
    When I setup solution manager 7.1 SP11 ,In Basic Configuration step Configure Automatically, the automatic activity Create Self-Monitoring Scenario is not able to find the Wily Introscope technical system. As note 1820491 ,one error has occoured. Please check the following for detail .
    ERROR
    As note 1820491
    I have perform the following steps manually successfully
    In Landscape Browser UI, open the LMDB Administration - Expert UI
    In the Expert UI, delete following Class Name:CIM Class Name: SAP_IPSERVICEPORT and CIM Refernce String: WLY
    Repeat the same for other CIM Classes like SAP_HTTPSERVICEPORT in case they are displayed in the warning of step Configure Wily Introscope
    Return to Basic Configuration step Configure CA Wily Introscope and use Edit and Save buttons
    But when I perform the following step, one error has occurred:
    When save , one error has occurred:
    TCODE : SLG1
    Technical System not found
    The technical system 'WLY~IS_EM' was not found in the landscape, but the authorization check is posi
    tive. [CX_DIAGST_RETRIEVE_EXCEPTION]
    How to create the WLY IS_EM technical system ?
    Can who help me to solve this ?
    Thanks
    LEO LEE

    Hi
    LMDB->Technical Systems->Create, Display, and Edit Technical Systems->
    Technical System Selection->Type->Wily Introscope Enterprise Manager (Standalone)-> Extended System ID:->WLY->EDIT->Arrtributes

  • Error while installing Wily Introscope

    Hi All,
    I have installed introscope enterprise manager 8 in solution manager 7.0 (SP15). i have follwed the below steps:
    1. Installation and Setup of SAP Solution Manager Server:
                   upgrading SAP Solution Manager Diagnostics (SMD) package
                   running Diagnostic setup wizard
    everything went successful.
    in the next step of wily introscope installation i have followed the below steps:
    2. installing CA Wily Introscope
               I.   Download Third-Party External Component Package from CA Wily
               II.   elected Platform Independent Introscope Installer
               III.  Extracted the Introscope Installer
              IV. Added the External Component Package
              V. Started the Installer
              VI. Verified the Installation
              VII.Installed the SAP Management Modules
             VIII.Ran the Enterprise Manager from OS level (AIX)
              IX. Checked That Introscope Is Running Properly
              X.  Extracted the Introscope Agent
              XI.  Created an AutoProbe Connector
             XII.  Activated the Agent: Setting up Java VM Parameters -
    here I am facing the issue
    in the installation manual it has been given to add the below java parameters to server node:
    -Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector.jar:/usr/sap/ccms/wily/Agent.jar
    -Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.profile
    -Dcom.wily.introscope.agent.agentName=<AgentName>
    i have added the above parameters and resterted the server then the java engine is not coming up. conflicting with the first parameter. once I remove that parameter I am able to up the java engine.
    without being added the above parameters " the agent will not start".
    please help me in this.
    thanks in advance
    Mohan K

    Mohan,
    I have the same problem. That is I set up the SMD on the managed system and completed the Managed system configuration through Solman which Installed Wily Introscope. With Wily enabled , the Java server process does not start.
    If I delete the 3 lines that have wily in it, it starts OK.
    How did you resolve this problem. Please let me know in detail.
    Thank you.
    Ravi

  • Error in Wily Introcope Agent Configuration (ABAP+JAVA)

    Hello,
    When i try to configure the wily introscope agent for a system ABAP+JAVA, i get the error:
    "J9 was detected, Operation bas been aborted because some files are missing, please fill the property com.wily.autoprobe.prependToJVMRuntimePath  in the agelet com.sap.smd.agent.application.wily - com.sap.smd.vm.J9PreprendPathNotFoundException: /opt/IBMJava2-amd64-142/jre/bin/j9vm/jclSC14/classes.zip:/opt/IBMJava2-amd64-142/jre/lib/jclSC14/classes.zip"
    I don't find the classes.zip file in any location...
    Any of you have any idea about this issue?
    Thanks in advance
    Carlos

    Hello,
    When i executed that commadn i get, and java -version, i get:
    servssm:ssmadm 1> whereis java
    java: /usr/bin/java /etc/java /usr/lib/java /usr/share/java /opt/IBMJava2-amd64-142/bin/java
    servssm:ssmadm 2> java -version
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
    IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-20070808 (JIT enabled)
    J9VM - 20070807_1500_LHdSMr
    JIT  - r7_level20070315_1745)
    The question is that there is not classes.zip file in any folder...
    Any idea?
    Thanks in advance
    Carlos

  • Problem Wily Introscope Installation!

    Hi,
    I can not install on the server of the Solution Manager Wily Introscope ENTPR MGR 8 -> AIX 64bit 5.3 - java version "1.4.2"
    Java (TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
    Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20061124 (SR7) (JIT enabled: jitc)
    Used files are:
    SAPISEM8SP01_00-10007374.SAR
    osgiPackages.v1.1.unix.tar
    eula.txt
    Can you help?
    Best Regards.

    Hi,
    I installed the EM as explained Inst.Guide_Introscope Ver.8 for SAP
    using the files:
    SAPISEM8SP01_00-10007374.SAR (introscope8.1.0.0aix64SAP.bin)
    SAPISMM8SP01_00-10007429.SAR (management modules)
    Then I deploy with SDM the ISAGENTSMD801_01-10007435.SCA.
    Then I launched SOLMAN_SETUP:
    Initial Configuration -> ok (green)
    Basic Configuration -> ok (green)
    Managed System Configuration select the stack of hava Solman and click on "Configure System", Diagnostics Prerequisites are ok.
    In step 2 "Manual Configuration":
    -Install Diagnostics Agent (it was previously done by SDM)
    -Assign Diagnostc Agent -> Open URL -> Agent Administrator
    The problem arises at this point if you click on "Show offline agents" list is empty!
    Then I also tried to install the Wily Introscope Agent at hand but might as well not start.
    Can you help?
    My Solution Manager has been upgraded to 'EHP1 on AIX 5L with JVM:
    Java VM version: J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20090307 (SR13) (JIT enabled: jitc)
    Java VM vendor: Classic VM (IBM Corporation)
    java vm type: <default>
    java vm cpu: ppc64
    Regards.
    Diego.

  • Wily host agent

    Hello,
    Could you please advice how is it possible to install and potentionaly configure host agent for Wily EM without using remote installation via SMD? I can see in Wily inst. guide only notice to remove EPAgent and activate hostAgent  via SMD wizard (since SMD SP13). At the moment I can see only data from Introscope java agent and no data from host-level agent like Garbage collection frequency and duration etc...
    Thx a lot in advance

    Dear Julius,
    Yes, both Wily IS Agent have to be deployed using SMD.
    1. You install the ISAgent (ISAGENTSMD8SP01_00-10007435.SCA for example) in Solution Manager ONLY.
        You do not have to install it on any managed systems !
    2. Using SOLMAN_SETUP procedure guided :
        2.1. Initial Configuration is done ...
        2.2. Basic Configuration is done ...
        2.3. Start the Managed System Configuration
        In 3rd phase of the SOLMAN_SETUP guided procedure, you have "Wily Introscope Configuration" steps.
        Here, you have the activity "Configure Wily Introscope Agent".
    When we talk about Wily ISAgent, it includes 2 agents :
    1. Wily Introscope Java Agent which monitors all applictions on JAVA level.
    2. Wily Host-Level Introscope Agent (ABAP)
    Hope it helps ?
    Best regards
    Pascal Cuennet
    Why do we have 2 Wily IS Agent :
    1.

  • Introscope Agent Settings

    Hi folks,
    Quick question this one probably.
    Can anyone tell me where this screenshot was taken from in Solution Manager please?  I've looked and looked and just cannot find it.
    Hopefully someone may recognise it??
    Thanks

    Hi Paul,
    Use this URL
    http://<fqdn>:<port>/webdynpro/dispatcher/sap.com/tc~smd~navigation/StandaloneApp?APP_ID=ADMIN_INTROSCOPE_AGENT
    goto -SOLMAN_SETUP ----- Managed System Configuration, select your managed system and in step 5 select action 'Configure Wily Introscope Agent'
    Divyanshu

Maybe you are looking for

  • A/P Invoice Draft convert to actual A/P Invoice Error

    Hi all, I had a problem as of mention in the Subject header. First of all, I am using SBO 2004.2B and 2004 SDK. I had created a small program to read in text file to create A/P Invoice Draft, no problem up till now. However, when I convert the A/P In

  • Extracting/Setting PDF Table contents using javascript

    Hello, Can you experts please let me know the following? 1. Is there a way to extract PDF table contents? 2. Can I set the row value via java script? Bottom line is I need to implement editable table in PDF. What are the ways I can achieve this feat?

  • PL/SQL Programming

    Hi " I Need Help" I am trying to call a java program from inside a PL/SQL block. I created a java class and compiled it and then loaded that class into ORACLE database using the following method. Step 1: CONNECT System/Manager GRANT CREATE ANY DIRECT

  • How can we give a placeholder to the complex table like "Please Select" in WPF

    How can we give a placeholder to the complex table like "Please Select" in WPF. Actually i have to give a default value like "please select" to the complex table in WPF. I tried with placeholder but its not working. Tags edited by: Michael Appleby

  • Super 10.50 - a J2EE toolkit supporting Weblogic 10

    Acelet has released Super 10.50, supporting Weblogic 10, with Easy EJB, Easy JMS, Easy JMX, Easy Webservice and more: at http://www.acelet.com Thanks.