Wily Introscope H/W migration details

Hi,
We are going for the hardware migration for our solution manager system. In solution manager host already wily introscope is installed. What steps need to be taken care during the migration so that wily is also migrated to new hardware box.
Thanks,
Rohan

Hello Rohan,
If your operational system is Windows NT:
Simple copy is not recommended on Windows NT system, however you can give it a try.
Copy the directory of /usr/sap/ccms/wilyintroscope to the new box, run script "RegisterEMService.bat" under the directory, goto service.msc to see if Introscope service is there, if so, start the EM service to see if EM is up and running.
If your operational system is UNIX/AIX:
Please install a new Wily EM and perform the necessary configuration such as the Java heap size and etc.. Then, please copy the contents under the directory /trace and /data to the corresponding directories of the new Wily EM. As the procedure is similar with the procedure of upgrading from 7.0 to 8.0 EM, please refer to the document 'Wily Installation and Upgrade Guide'.
You can follow the UNIX steps for Windows NT as well, as it will migrate all the historical data from one box to another.
Best rgeards,
Guilherme Balbinot

Similar Messages

  • 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

  • Wily Introscope for SOLMAN 7.1

    Hi All,
    We are configuring SAP Solution Manager 7.1
    I have few doubts regarding Wily Introscope.
    1. Is it necessary to install Wily Introscope on SAP SOLMAN 7.1?
    2. Is it installed already with SOLMAN or need to be installed manually?
    3. I need details about licensing policy of Wily Introscope.
    4. If it is necessary to install please provide suitable link for installing it.
    and I have one more question.
    We getting waring message for Single Sign On and WEB Services Logical Port Creation in Managed System Configuration Step No. 8 Configure Automatically.
    Shall we proceed with warning. or it needs to be fully performed without warning.
    Please guide us.
    Thanks & Regards,
    Ishan

    Ishan trying to answer all your doubts:
    1. Is it necessary to install Wily Introscope on SAP SOLMAN 7.1?
    If you need to implement RCA then only Wily Introscope is required.
    2. Is it installed already with SOLMAN or need to be installed manually?
    It has to be installed manually..Just follow the standard guide..
    3. I need details about licensing policy of Wily Introscope.
    Good Question..I think there should be someone in your orgnisation who looks after the licencing..Ask him to give  a call to SAP..
    4. If it is necessary to install please provide suitable link for installing it.
    Follow this link :
    http://www.scribd.com/doc/36673011/Wily-Intro-Scope-8-Installation-Guide
    Thanks & Regards,
    Joydeep

  • Wily Introscope Enterprise Manager Can't be accessed

    Hi Experts,
    I installed Solution Manager 7.0 EHP1 and executed basic configuration. And I followed the instruction to install wily EM 8.0. But after installation, the web pages http://emhost:8081/workstation and http://emhost:8081/webview cannot be accessed. Error msg is "404 Not Found The requested resource does not exist."
    I've checked the wily log and found no errors. How to solve the problem?

    Hi ,
    Check if the installation of EM 8.0 was successful or not.
    For the same, please check <Introscopehome>/install/Introscopeinstall.log.
    I am hoping your installation is successful. Then please perform some other checks.
    Please start your Introscope Enterprise Manager service from Windows Services [ for other OS please refer to guide]
    Check the <IntroscopeHome>/log/IntroscopeEnterpriseManager.log
    file for an Error entry.. there may be a possibility that the Port 8081 [or 8080] is already in use.
    Similar format to error message :::
    "EM Web Server did not start.  Port already in use: 8080  To change the Web Server port, modify the EM property: introscope.enterprisemanager.webserver.port "
    If yes, then please modify the \conf\EnterpriseManager.properties file
    introscope.enterprisemanager.webserver.port=8080            
    OR
    introscope.enterprisemanager.webserver.port=any other open port
    For more details about changing port please refer to Thread
    Wily Introscope Enterprise Manager 7.2 is not starting on SolMan system
    I hope the provided information will be helpful.
    Best Regards,
    ~~ Pradeep Bishnoi ~~

  • Wily Introscope issue

    Hi All,
    We are unable to start Wily Introscope manager.Once start generating Java heap dump and went to down status.Please find the Log file details below and give your suggestion to resolve this issue.
    Module=/usr/sap//wilyintroscope/jre/bin/libj9jit23.so
    Module_base_address=0900000004620000
    Target=2_30_20071004_14218_BHdSMr (AIX 6.1)
    CPU=ppc64 (16 logical CPUs) (0x980000000 RAM)
    JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
    JVMDUMP007I JVM Requesting System Dump using '/usr/sap/<SID>/wilyintroscope/core.20140724.183547.26476614.dmp'
    JVMDUMP010I System Dump written to /usr/sap/<SID>/wilyintroscope/core.20140724.183547.26476614.dmp
    JVMDUMP007I JVM Requesting Snap Dump using '/usr/sap/<SID>/wilyintroscope/Snap0002.20140724.183547.26476614.trc'
    JVMDUMP010I Snap Dump written to /usr/sap/<SID>/wilyintroscope/Snap0002.20140724.183547.26476614.trc
    JVMDUMP007I JVM Requesting Java Dump using '/usr/sap/<SID>/wilyintroscope/javacore.20140724.183547.26476614.txt'
    JVMDUMP012E Error in Java Dump: /usr/sap/<SID>/wilyintroscope/javacore.20140724.183547.26476614.txt
    JVMDUMP013I Processed Dump Event "gpf", detail "".
    JVMJ9GC028E Option too large: '-Xmx4096m'
    JVMJ9VM015W Initialization error for library j9gc23(2): Failed to initialize; unable to parse command line
    Could not create the Java virtual machine.
    Regards,
    MK

    Hi,
    Plz find the java core details below.
    NULL           ------------------------------------------------------------------------
    0SECTION       TITLE subcomponent dump routine
    NULL           ===============================
    1TISIGINFO     Dump Event "gpf" (00002000) received
    1TIDATETIME    Date:                 2014/07/24 at 18:36:07
    1TIFILENAME    Javacore filename:    /usr/sap/<SID>/wilyintroscope/javacore.20140724.183547.26476614.txt
    NULL           ------------------------------------------------------------------------
    0SECTION       GPINFO subcomponent dump routine
    NULL           ================================
    2XHOSLEVEL     OS Level         : AIX 6.1
    2XHCPUS        Processors -
    3XHCPUARCH       Architecture   : ppc64
    3XHNUMCPUS       How Many       : 16
    NULL
    1XHEXCPCODE    J9Generic_Signal_Number: 0000000000000004
    1XHEXCPCODE    Signal_Number: 000000000000000B
    1XHEXCPCODE    Error_Value: 0000000000000000
    1XHEXCPCODE    Signal_Code: 0000000000000033
    1XHEXCPCODE    Handler1: 09001000A0C39D58
    1XHEXCPCODE    Handler2: 09001000A0C31E38
    NULL
    1XHEXCPMODULE  Module: /usr/sap/<SID>/wilyintroscope/jre/bin/libj9jit23.so
    1XHEXCPMODULE  Module_base_address: 0900000004620000
    NULL
    1XHREGISTERS   Registers:
    2XHREGISTER      R0:0000000000000002
    2XHREGISTER      R1:0FFFFFFFFFFFE150
    2XHREGISTER      R2:0000000000000002
    2XHREGISTER      R3:0000000000000002
    2XHREGISTER      R4:0000000000000002
    2XHREGISTER      R5:07000000002982C8
    2XHREGISTER      R6:0000000115E80F09
    2XHREGISTER      R7:0000000000000018
    2XHREGISTER      R8:0000000115F565B0
    2XHREGISTER      R9:0000000115D1B089
    2XHREGISTER      R10:FFFFFFFFFFFFFFFF
    2XHREGISTER      R11:0900000004654EB0
    2XHREGISTER      R12:000000011A1B7E9F
    2XHREGISTER      R13:0000000110011200
    0SECTION       ENVINFO subcomponent dump routine
    NULL           =================================
    1CIJAVAVERSION J2RE 5.0 IBM J9 2.3 AIX ppc64-64 build j9vmap6423-20071007
    1CIVMVERSION   VM build 20071004_14218_BHdSMr
    1CIJITVERSION  JIT enabled - 20070820_1846ifx1_r8
    1CIRUNNINGAS   Running as a standalone JVM
    1CICMDLINE     ./jre/bin/java -Xms512m -Xmx4096m -Djava.awt.headless=true -Dsun.java2d.noddraw=true -Dorg.osgi.framework.bootdelegation=org.apache.xpath com.zerog.lax.L
    AX /usr/sap/<SID>/wilyintroscope/bin/../Introscope_Enterprise_Manager.lax /tmp/env.properties.26476614
    1CIJAVAHOMEDIR Java Home Dir:   /usr/sap/<SID>/wilyintroscope/jre
    1CIJAVADLLDIR  Java DLL Dir:    /usr/sap/<SID>/wilyintroscope/jre/bin
    1CISYSCP       Sys Classpath:   /usr/sap/<SID>/wilyintroscope/jre/lib/vm.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/core.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/charsets.jar
    ;/usr/sap/<SID>/wilyintroscope/jre/lib/graphics.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/security.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmpkcs.jar;/usr/sap/<SID>/wilyintr
    oscope/jre/lib/ibmorb.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmcfw.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmorbapi.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmjcefw.
    jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmjgssprovider.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmjsseprovider2.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/ibmjaaslm.jar;/
    usr/sap/<SID>/wilyintroscope/jre/lib/ibmcertpathprovider.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/server.jar;/usr/sap/<SID>/wilyintroscope/jre/lib/xml.jar;
    1CIUSERARGS    UserArgs:
    2CIUSERARG               -Xmx256M
    2CIUSERARG               -Xj9
    2CIUSERARG               -Xjcl:jclscar_23
    2CIUSERARG               -Dcom.ibm.oti.vm.bootstrap.library.path=/usr/sap/<SID>/wilyintroscope/jre/bin
    2CIUSERARG               -Dsun.boot.library.path=/usr/sap/<SID>/wilyintroscope/jre/bin
    2CIUSERARG               -Djava.library.path=/usr/sap/<SID>/wilyintroscope/jre/bin:/usr/sap/<SID>/wilyintroscope/jre/bin:/usr/sap/<SID>/wilyintroscope/jre/bin/classic:/usr/sa
    p/<SID>/wilyintroscope/jre/bin:/usr/sap/<SID>/SYS/exe/run:/usr/sap/<SID>/wilyintroscope/jre/bin/j9vm:/usr/lib
    2CIUSERARG               -Djava.home=/usr/sap/<SID>/wilyintroscope/jre
    2CIUSERARG               -Djava.ext.dirs=/usr/sap/<SID>/wilyintroscope/jre/lib/ext
    2CIUSERARG               -Duser.dir=/usr/sap/<SID>/wilyintroscope
    2CIUSERARG               _j2se_j9=70912 0x09001000A048F3E8
    2CIUSERARG               vfprintf 0x0000000110001910
    2CIUSERARG               -Xms512m
    2CIUSERARG               -Xmx4096m
    2CIUSERARG               -Djava.awt.headless=true
    2CIUSERARG               -Dsun.java2d.noddraw=true
    2CIUSERARG               -Dorg.osgi.framework.bootdelegation=org.apache.xpath
    2CIUSERARG               -Dinvokedviajava
    2CIUSERARG               -Djava.class.path=/usr/sap/<SID>/wilyintroscope/bin/../launcher.jar:/usr/sap/<SID>/wilyintroscope/bin/../lax.jar:
    2CIUSERARG               vfprintf
    2CIUSERARG               _port_library 0x09001000A048FDF0
    2CIUSERARG               -Xdump
    Regards,
    MK

  • Wily Introscope Version for Solution Manager 7 SPS 17

    Hi
    We have a solution manager 4 (now 7) running on an ABAP stack only, this was recently upgraded from Solution Manager 3.2 which was installed 3 years ago as ABAP stack only, this server was never powerful enough to have the Java stack added and the project did not require it.
    I am now looking to migrate this ABAP Solution Manager 7 to a new server, using ABAP & JAVA so I can make use of Solution Managaer tools like Diagnostics, RCA, WILY etc.
    On a sandpit copy I have migrated the ABAP instance to a more powerful server and added the Java Instance from the Solution Manager 4 Installation Master, so I now have a dual stack SM 4, I have patched this to SP17.
    I am looking to install Wily Introscope for monitoring, I have read Note 797147 - Wily Introscope Installation for SAP Customers, where it says you should always use the latest version of Wily, which is 8.0.2, but looking at the note, the downloads for Introscope Enterprise Manager and Introscope Workstation are from SAP SOLUTION MANAGER 7.0 EHP 1, but I am not running Solution Manager on EHP1, I am on SP Stack 17.
    Looking in the SWDC there are downloads in  SAP SOLUTION MANAGER 7.0 -> Entry by Component -> Solution Manager JAVA Stack -> WILY INTROSCOPE ENTPR MGR 8
    Is this what I should be using for my SP Stack 17, or should I use the EHP1 version?
    Also, setting up the Solution Manager Diagnostics, is there a setup PDF for Solution Manager 7 SP17 ? I cannot find a setup guide for this release, most are for EHP1, I would rather not have to implement EHP1 as part of this migration !
    Thanks for any help.
    Paul.

    Hi Bhudev
    Thanks for the reply, I presumed it was the Wily introscope 8 without the EHP1 I required.
    As for installation guide, I have think you have misunderstood my question, I already have the wily installation guide from the note location, I wanted to know if there is any Solution Manager Diagnostics setup guides for SP17 ?
    When I use transaction SOLMAN_WORKCENNTER --> System Monitoring --> Solution Manager Diagnostics --> Diagnostics System --> Diagnostics Setup --> Setup Wizard
    the first 2 (of 23) setups are failing :
    SSO The value of profile parameter login/accept_sso2_ticket could not be checked
    BI Cannot invoke CCMSBISETUP on host localhost
    Warning :
    User(BI) Role SAP_BI_E2E does not exist
    Then it says :
    To complete the Diagnostics Setup, you should perform the following operations as documented in Diagnostics Setup Guide
    I cannot find this Diagnostics Setup Guide for SP17 ?
    The installation guides are mainly for EHP1, media library under sap-ag.de/diagnostics does not show this setup guide, Master Installation guide does not mention it, so was wondering if anyone could point me in the right direction for this guide ?
    Thanks,
    Paul.

  • Wily Introscope on two server nodes - are there two connectors necessary?

    Dear all,
    we' ve installed Wily Introscope on our portal which has two java server nodes. As I' ve read in SDN every Wily agent on a server has his own name, here ABC_Portal_server0 and ABC_Portal_server1.
    In section 4 of the Wily Introscope installation manual the creation of the AutoProbe connector is described. Do we have to create two AutoProbe connector files (one for each agent) or only one for both agents?
    Thank you for your suggestions.
    Best regards
    Martin Röhr

    Hi Achim,
    According to my knowledge, there are no known problems with a "required Extended Protection" / "Always On" / "Livelink Server" combination.
    Extended Protection helps to prevent an authentication relay attack by using service binding and channel binding. We need to note that when Extended Protection is set to
    Required, only connections from protected applications on protected operating systems are accepted. This setting is the most secure but connections from operating systems or applications that do not support Extended Protection will not be able
    to connect to SQL Server. For more details, please review the following article.
    Connect to the Database Engine Using Extended Protection
    https://msdn.microsoft.com/en-us/library/ff487261(v=sql.110).aspx
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.
    Lydia Zhang
    TechNet Community Support

  • J2ee Can't start after JDK upgrade on system with Wily Introscope

    Hello All,
    For one of our portal server java patching is done from java 1.4.2.22 to java 1.4.2.25. And on this server Wily Introscope is installed.As per SAP when ever we upgrade java we need to re-create "AutoProbeConnector.jar" and update the JAVA VM parameters in configtool.
    I know the procedure to re-create "AutoProbeConnector.jar" if the Introscope agent is installed manually .
    Below are the steps to be followed to re-create if it is manual type.
    i)Re-create the AutoProbeConnector.jar file
    >wily>connector
    java -jar CreateAutoProbeConnector.jar -jvm /opt/java1.4 -output
    AutoProbeConnector.jar
    Output file AutoProbeConnector.jar created.
    ii)Setting Java vm parameters through configtool.
    Xbootclasspath/p:/usr/sap/ccms/wily/connectors/AutoProbeConnector.jar:/usr/sap/ccms/wily/Agent.jar
    Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.profile
    -Dcom.wily.introscope.agent.agentName=<AgentName>
    But my systems Introscope agent is created automatically by SDM agent.if this is the case we need to re-execute the Introscope agent setup again to re-create the AutoProbeConnector.jar file.
    Can you any one tell me the procedure to do this activity, if possible with steps and the paths to be followed.
    Classpath parameter file which says it is installed automatically.
    ID27689350.JavaParameters=-Xbootclasspath/p:/usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.7.2.3.0-2008-08-11/wily/connec
    tors/AutoProbeConnector.jar:/usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.7.2.3.0-2008-08-11/wily/Agent.jar -Dcom.wily.i
    ntroscope.agent.agentName=BPD_JC02_server0 -Dcom.wily.introscope.agentProfile=/usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAG
    ENT.7.2.3.0-2008-08-11/wily/IntroscopeAgent.profile -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORB
    Proxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco
    .jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:+UseParNewGC -Xms2048M -X
    X:NewSize=320M -XX:NewSize=320M -XX:HandlePromotionFailure -XX:PrintClassHistogram -XX:HeapDumpOnOutOfMemoryError -XX:DisableExplicitGC -XX:MaxPermSize=256M -XX:PermSize=256
    M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=/oracle/BPD/920_64/jdbc/lib/classes12.jar -Dsys.global.dir=/usr/sap/BPD/SYS/global/

    Hello Jansi,
    Thanks for the update.
    I have gone through the document, and currently i require to update the Introscope Agent via SMD.
    In the document it is mentioned as the navigation
    Launch the Introscope Setup application: Diagnostics Setup > Managed Systems>Introscope Agent.
    These are the below doubts i have.
    1>How should i enter to "Launch the Introscope setup application"
    2>and then followed by Diagnostics setup.
    Kindly help me in detailed navigation, for example to which server i need to login(is it the Enterprise Manager server ?)
    Awaiting your reply.
    best Regards
    Rakesh

  • 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

  • SOLMAN SMD Wily Introscope

    Hi!
    Has some one experience working with Wily Introscope 8.0?
    I use currently the version 7.2 and would like to upgrade this version to Wily Introscope 8.0.
    When I do so I cannot install and run Wily Introscope 8.0.
    Any helpful information will be very appreciated!
    regards
    Axel Schulze

    Hi Axel
    I am planning to un-install my current wily 7.2 and plannign to install 8.0, can you let me know if you have already completed upgrading and also can you send me details on the upgrade.
    Thanks
    Reddy

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

  • SAPISMM*.SAR - SAP Management Modules Wily Introscope

    Hi there,
    I've installed Wily Introscope 8.1.0 on AIX 6.1 64 Bit. The installation was successful, there are no errors or warnings. Now I have to extract the file SAPISMM*.SAR in /usr/sap/ccms/wilyintroscope, but I can't find it in SAP-Marketplace. I'm a bit hopeless
    Can you help me??
    Best regards,
    Andreas

    Are your installation of Wily Introscope at AIX 6.1 successful and the Wily runs?
    We get a error on start:
    Running Enterprise Manager with IHOME=.
    Running Enterprise Manager with JAVAPATH=/usr/sap/ccms/wilyintroscope/jre
    java version "1.5.0"
    Java(TM) 2 Runtime Environment, Standard Edition (build pap64devifx-20071025 (SR6b))
    IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20071007 (JIT enabled)
    J9VM - 20071004_14218_BHdSMr
    JIT  - 20070820_1846ifx1_r8
    GC   - 200708_10)
    JCL  - 20071025
    Unhandled exception
    Type=Segmentation error vmState=0x00000000
    J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
    Handler1=09001000A26B3D58 Handler2=09001000A26ABE38
    R0=0000000000000002 R1=0FFFFFFFFFFFE7E0 R2=0000000000000002 R3=0000000000000002
    R4=0000000000000002 R5=07000000002652B0 R6=0000000111C944D3 R7=0000000111C944C8
    R8=0000000111C944D0 R9=0000000111C943E0 R10=FFFFFFFFFFFFFFFF R11=09000000176FFEB0
    R12=FFFFFFFFDBC17BC1 R13=0000000110011200 R14=0000000111C94468 R15=000000011009C300
    R16=00000001111783B0 R17=0000000111D6F1F8 R18=09001000A26B75F0 R19=0000000000000185
    R20=0000000111D6F1D8 R21=0000000111C944F0 R22=000000011009C380 R23=0000000000000000
    R24=BADC0FFEE0DDF00D R25=0000000000000000 R26=000000011009C300 R27=0000000110018F50
    R28=0000000000000000 R29=09001000A26A0DF0 R30=0FFFFFFFFFFFED80 R31=07000000002652B0
    IAR=09000000176FFEB0 LR=00000001109539DC MSR=A00000000000D032 CTR=09000000176FFEB0
    CR=2258582420000002 FPSCR=8202200000000000 XER=2000000282022000
    FPR0 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR2 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR3 c530000000000000 (f: 0.000000, d: -1.934281e+25)
    FPR4 3f30000000000000 (f: 0.000000, d: 2.441406e-04)
    FPR5 4330000000000000 (f: 0.000000, d: 4.503600e+15)
    FPR6 3fb9999999999999 (f: 2576980480.000000, d: 1.000000e-01)
    FPR7 3c63333333333333 (f: 858993472.000000, d: 8.326673e-18)
    FPR8 0000000082024000 (f: 2181185536.000000, d: 1.077649e-314)
    FPR9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR10 4330000000000000 (f: 0.000000, d: 4.503600e+15)
    FPR11 4000000000000000 (f: 0.000000, d: 2.000000e+00)
    FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
    FPR13 3ff8000000000000 (f: 0.000000, d: 1.500000e+00)
    FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
    Module=/usr/sap/ccms/wilyintroscope/jre/bin/libj9jit23.so
    Module_base_address=09000000176CB000
    Target=2_30_20071004_14218_BHdSMr (AIX 6.1)
    CPU=ppc64 (16 logical CPUs) (0x400000000 RAM)
    JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
    JVMDUMP007I JVM Requesting System Dump using '/usr/sap/ccms/wilyintroscope/core.20110503.085037.12910716.dmp'
    JVMDUMP010I System Dump written to /usr/sap/ccms/wilyintroscope/core.20110503.085037.12910716.dmp
    JVMDUMP007I JVM Requesting Snap Dump using '/usr/sap/ccms/wilyintroscope/Snap0002.20110503.085037.12910716.trc'
    JVMDUMP010I Snap Dump written to /usr/sap/ccms/wilyintroscope/Snap0002.20110503.085037.12910716.trc
    JVMDUMP007I JVM Requesting Java Dump using '/usr/sap/ccms/wilyintroscope/javacore.20110503.085037.12910716.txt'
    JVMDUMP012E Error in Java Dump: /usr/sap/ccms/wilyintroscope/javacore.20110503.085037.12910716.txt
    JVMDUMP013I Processed Dump Event "gpf", detail "".

  • 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 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 8.2.2 - No License for Wrapper service

    Hi All,
    I've installed the Wily Introscope Manager 8.2.2. When starting the EM service, I get the following error message in the log file:
    STATUS | wrapper  | 2010/09/20 15:10:47 | --> Wrapper Started as Service
    STATUS | wrapper  | 2010/09/20 15:10:47 | Java Service Wrapper Standard Edition 32-bit 3.3.6
    STATUS | wrapper  | 2010/09/20 15:10:47 |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights Reserved.
    STATUS | wrapper  | 2010/09/20 15:10:47 |     http://wrapper.tanukisoftware.org
    STATUS | wrapper  | 2010/09/20 15:10:47 |
    ERROR  | wrapper  | 2010/09/20 15:10:47 | License Error:
    ERROR  | wrapper  | 2010/09/20 15:10:47 | A valid license was not found in the Wrapper configuration file.
    ERROR  | wrapper  | 2010/09/20 15:10:47 |
    ERROR  | wrapper  | 2010/09/20 15:10:47 | A license can be obtained from the Java Service Wrapper site:
    ERROR  | wrapper  | 2010/09/20 15:10:47 |   http://wrapper.tanukisoftware.org/doc/english/purchase.html
    I believe that Wily is licensed as part of the Solution Manager Enterprise edition. So why do I need to buy an additional license?
    Regards,
    Masoud

    Hi 
    For the Wily Introscope Enterprise Manager 8.2 the error you described
    occurs if the em-include.conf file is missing in the EM' installation.
    This file is included into the SAP managed modules SAPISMM02_0*.SAR
    file.
    Note that for Wily Introscope EM 8.2.2 you need to install the SAP
    management modules after the installation of the EM 8.2.2 AND before
    you attempt to start the service
    Please refer to the Node 797147 for the documentation about the
    the SAPISMM02_0*.SAR - management modules to be installed on top of
    Enterprise Manager.
    Please consider additionally the Note 1273028
    - The Enterprise Manager can only be launched as Windows Service
    after the latest management module package (SAPISMM) has been
    installed. The SAPISMM package contains a file em-include.conf
    which is required.
    I would like to ask you to implement the Note 1273028 and to retest the
    issue.
    Best Regards
    Jai Wardhan

Maybe you are looking for