Introscope Enterprise Manager

Hi,
IEM takes lot of space & is growing. which files can i delete to free space.
Thanks in advance..
Edited by: Kobby bryant on Aug 19, 2008 6:44 PM

Each agent can generate 500mb data in the ../traces and ../data directories if this fills up the file system, in case of emergency when can delete the contents of
/usr/sap/ccms/wilyintroscope/traces
/usr/sap/ccms/wilyintroscope/data
Then restart the EM
To reduce the required space open the ./config/IntroscopeEnterpriseManager.properties file, and you can find the entries as below:
introscope.enterprisemanager.transactionevents.storage.max.data.age=N
#The trace files under "traces" folder will be deleted after N days.
introscope.enterprisemanager.smartstor.tier3.age=N
#The historical files under "data" folder will finally be deleted after N days
introscope.enterprisemanager.transactionevents.storage.optimize.time offsethour
#It's only about the time to run the "house keeping".
Please adjust the settings accordingly. These changes will not have a immediate effect to the current situation. The simplest way to solve the problem is just to delete the whole "data" and "traces" folder. EM will automatically re-create these new folders when restarting. But please be aware that the historical data will be lost, so we suggest backing up the historical files first. From then on, the "house keeping" work will run in the new way as we have modified.
Alternately one can put the /data directory on a different disk drive / disk controller. For this purpose, change
the following properties in the file config/IntroscopeEnterpriseManager.properties:
introscope.enterprisemanager.smartstor.directory=/your/separate/drive/data
introscope.enterprisemanager.smartstor.directory.archive=/your/separate/drive/archive
introscope.enterprisemanager.smartstor.dedicatedcontroller=true

Similar Messages

  • Wily Introscope Enterprise Manager fails to start due to Java Heap

    Hello All,
    I just installed Wily Introscope for the first time. I have successfully installed it from the log below:
    Summary
    Installation: Successfulwith errors.
    396 Successes
    0 Warnings
    1 NonFatalErrors
    0 FatalErrors
    I also confirm that the Introscope Enterprise Manager is started as a service.
    However, when i try to launch enterprise by following the path All Programs > CA Wily > Introscope 8.2.3.5 > Introscope Enterprise Manager....
    I get the error below:
    3/29/11 07:11:46 PM PDT [ERROR] [Manager.Bootstrap] Load all Management Modules FAILED.
    3/29/11 07:11:46 PM PDT [ERROR] [Manager] The EM failed to start. Java heap space
    I have also adapted my Java Heap from 512 to 1024 in EMService.conf file but I still get same error. This was the recommendation in this related forum post - Wily Introscope - EM failed to start
    Please help!!!!

    Hello,
    Like I said, I have increased the value to 1024MB and still not starting.
    The corresponding section of the EMService is pasted below:
    Wrapper Properties
    Java Application
    wrapper.java.command=jre
    bin
    java.exe
    wrapper.working.dir=.\
    Java Main class
    wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
    Java Classpath (include wrapper.jar)  Add class path elements as
    needed starting from 1
    wrapper.native_library=ServiceWrapper32
    wrapper.java.classpath.1=./lib/ServiceWrapper32.jar
    wrapper.java.classpath.2=./launcher.jar
    #wrapper.java.classpath.3=
    Java Library Path (location of Wrapper.DLL or libwrapper.so)
    wrapper.java.library.path.1=./lib
    Java Additional Parameters
    Note: On 64-bit Windows only, the first additional parameter must be: -Xrs
    #wrapper.java.additional.1=
    wrapper.java.additional.1=-Xrs
    wrapper.java.additional.2=-Djava.awt.headless=false
    Initial Java Heap Size (in MB)
    wrapper.java.initmemory=512
    Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024
    Application parameters.  Add parameters as needed starting from 1
    wrapper.app.parameter.1=org.eclipse.core.launcher.Main
    wrapper.app.parameter.2=-consolelog
    wrapper.app.parameter.3=-noExit
    wrapper.app.parameter.4=-product
    wrapper.app.parameter.5=com.wily.introscope.em.product
    wrapper.app.parameter.6=-install
    wrapper.app.parameter.7=./product/enterprisemanager
    wrapper.app.parameter.8=-configuration
    wrapper.app.parameter.9=./product/enterprisemanager/configuration
    Number of seconds to allow between the time that the Wrapper launches
    the JVM process and the time that the JVM side of the Wrapper responds
    that the application has started. 0 means never time out. Defaults to 30 seconds.
    wrapper.startup.timeout=300
    Please help

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

  • Error executing Introscope Enterprise Manager

    Hello,
    I am configuring the Wily Introscope 7.1 as a step for configure the SMD, and I have a problem starting the Enterprise Manager with the command: <i>nohup ./Introscope_Enterprise_Manager&</i>
    It append an output to 'nohup.out', which display the following error:
    <i>java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.</i>
    I have done every step described in the "Introscope Version 7.1Installation Guide For SAP".
    What could be the problem?
    Regards,
    MY

    Hi Miguel,
    I see  two explanations:
    (1) The DISPLAY environment variable is not correctly defined on the remote server; and / or
    (2) The computer from which the rsh command is executed does not allow the display of a "frame" from another host.
    In the first case, one could try on the remote computer:
    set DISPLAY=localComputer:0
    export DISPLAY.
    (depends on the shell may be
    setenv DISPLAY systemname:0.0
    where systemname is the name of your workstation, or some remote system where you want the display directed to).
    In the second case, one could try on the local computer:
    xhost+
    if it helpful reward points are appreciated

  • Wilyhost Agent could connect to the Enterprise Manager

    Hi Gurus,
    I'm trying to setup Diagnostic for Solman 7.0. I'd installed Wily Introscope and SDM Agent in Solution Manager. The Agent was configured for this server. The Application Agent in Diagnostic Setup -> Managed system was OK, but when I try to run the Setup Wizard for Self-Monitoring, every steps are in green (OK) but the first was in red with this error:
    Step Wilyhost Agent Details
    Created destination SM1_DVEBMGS00_server0
    Created destination SM1|qfmasr003_SM1_00
    Created action SAP GC|SM1_DVEBMGS00_server0 - SAP GC|SM1_DVEBMGS00_server0
    Created action SM1 - SM1 AbapSystem
    Created action SM1|qfmasr003_SM1_00 - SM1|qfmasr003_SM1_00 AbapInstance
    Created 3 action(s).
    0 Wilyhost Agent(s) and 0 EP Agent(s) from host qfmasr003 are connected to the EM.
    Wilyhost Agent configuration finished without errors, but on Enterprise Manager (qfmasr003.xxxxxxxx.com:6000) no Wilyhost Agent was detected from host qfmasr003. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
    The file jvm_smdagent.out  said this:
    LoadBalanceRestricted=no
    P4ClassLoad=P4Connection
    SAPDBHOST=
    SAPINFO=SMD_98_server
    SAPMYNAME=qfmasr003_SMD_98
    SAPSTARTUP=1
    SAPSYSTEM=98
    SAPSYSTEMNAME=SMD
    application.home=/usr/sap/SMD/exe
    file.encoding=UTF-8
    file.encoding.pkg=sun.io
    file.separator=/
    j2ee.dbhost=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/usr/sap/SMD/exe/jstartup.jar:/usr/sap/SMD/exe/jvmx.jar:../../exe/jstartupapi.jar:../../exe/jstartupimpl.jar:lib/patch_7.00.15.20080806065909/launcher/smdagentlauncher.jar
    java.class.version=48.0
    java.endorsed.dirs=/j2sdk1.4.2_17/jre/lib/endorsed
    java.ext.dirs=/j2sdk1.4.2_17/jre/lib/ext
    java.home=/j2sdk1.4.2_17/jre
    java.io.tmpdir=/tmp
    java.library.path=/j2sdk1.4.2_17/jre/lib/i386/server:/j2sdk1.4.2_17/jre/lib/i386:/j2sdk1.4.2_17/jre/../lib/i386:/usr/sap/SMD/exe:/tmp/sapinst_exe.18845.1222346568:/usr/sap/SMD/exe:/usr/sap/SMD/exe:/usr/sap/SMD/exe
    java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version=1.4.2_17-b06
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.4
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor=Sun Microsystems Inc.
    java.vendor.url=http://java.sun.com/
    java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
    java.version=1.4.2_17
    java.vm.info=mixed mode
    java.vm.name=Java HotSpot(TM) Server VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=Sun Microsystems Inc.
    java.vm.version=1.4.2_17-b06
    jstartup.debuggable=yes
    jstartup.mode=JCONTROL
    jstartup.ownHardwareId=G1082288837
    jstartup.ownProcessId=1666
    jstartup.whoami=server
    line.separator=
    memory.manager=128M
    os.arch=i386
    os.name=Linux
    os.version=2.6.9-5.ELsmp
    path.separator=:
    sun.arch.data.model=32
    sun.boot.class.path=/j2sdk1.4.2_17/jre/lib/rt.jar:/j2sdk1.4.2_17/jre/lib/i18n.jar:/j2sdk1.4.2_17/jre/lib/sunrsasign.jar:/j2sdk1.4.2_17/jre/lib/jsse.jar:/j2sdk1.4.2_17/jre/lib/jce.jar:/j2sdk1.4.2_17/jre/lib/charsets.jar:/j2sdk1.4.2_17/jre/classes
    sun.boot.library.path=/j2sdk1.4.2_17/jre/lib/i386
    sun.cpu.endian=little
    sun.cpu.isalist=
    sun.io.unicode.encoding=UnicodeLittle
    sun.java2d.fontpath=
    sun.os.patch.level=unknown
    sys.global.dir=/usr/sap/SMD/SYS/global
    user.country=US
    user.dir=/usr/sap/SMD/J98/SMDAgent
    user.home=/home/smdadm
    user.language=en
    user.name=smdadm
    user.timezone=
    Running SMD Agent ...
    [Runtime] START
    ==> Loading application com.sap.smd.agent.application.runtime : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.global.configuration : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.connectors : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.wily : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.filesystem : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.tracing : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.remotesetup : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.wilyhost : 7.0015.20080806065229.0000
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent Release 7.2.0.0 (Build 540138)
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) Server VM 1.4.2_17" from Sun Microsystems Inc.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Trying to load file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Loaded file from ./applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set.  No extensions will be loaded.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Introscope Agent startup complete.               
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Property "com.wily.introscope.agent.agentName".
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
    10/14/08 01:13:55 PM ARST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
    10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at qfmasr003.quickfood.com.ar:6000,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "qfmasr003", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
    10/14/08 01:13:57 PM ARST [INFO] [IntroscopeAgent] Remote Agent Configuration Service is enabled
    ==> Loading application com.sap.smd.agent.application.logviewer : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.flightrecorderdumpscan : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.telnet : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.database : 7.0015.20080806065229.0000
    ==> Loading application com.sap.smd.agent.application.datacollector : 7.0015.20080806065229.0000
    Initialization done.
    [ms://qfmasr003.xxxxxxxxxxxxxxxxxx:8101/P4] Agent ready.
    ==> Loading application com.sap.smd.agent.application.remoteos : 7.0015.20080806065229.0000
    only Initial Configuration files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only file configuration information will be considered
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    only Abap configuration will be considered
    only Abap configuration will be considered
    only file version information will be considered
    only End2End log files will be considered
    only software change logs will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    10/15/08 01:16:17 PM ARST [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly.  Keeping the connection alive.
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only file configuration information will be considered
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ClusterManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ServiceManager.properties][J2EE] has already been defined with another alias.
    Warning: ConfigStore [cfg/kernel/ThreadManager.properties][J2EE] has already been defined with another alias.
    only Abap configuration will be considered
    only Abap configuration will be considered
    only file version information will be considered
    only End2End log files will be considered
    only software change logs will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only End2End log files will be considered
    only Initial Configuration files will be considered
    This error is the same, when I try to connecto other system for Diagnostics,
    Any comments, suggestions, recomendations.... anythings.....
    Thanks in advice,
    Sergio Mazzeo.

    Hi Sergio,
    did you already stop and start your SMD agent on OS level ? It is not enough to restart it from the SMD.
    kind regards
    Davy

  • SSO from Solution Manager to Wily Enterprise Manager issue

    Hi,
    We are facing problem in SSO from Solution Manager to Wily Enterprise Manager. We have done the configuration as per the Wily Enterprise Guide- "Introscope Version 8 Installation Guide For SAP" Page 38.
    Our Solution Manager system is running on AIX platform and Wily Enterprise Manager is on Windows 2008.
    This is what we are trying
    SOLMAN Production Client --> SOLMAN_WORKCENTER --> INTROSCOPE WORKSTATION --> this opens a new browser page and from there we click on Start Introscope -->
    Result --> SSO doesn't work, still we get login window.
    Introscope Enterprise Manager logs says -->
    9/12/11 10:47:17 PM BST [WARN] [Manager] Single sign on failed: No SAP single sign on ticket was found in the request header.
    Note: Another Solution Manager system in our landscape (on windows 2008 platform) is connected to same Wily Enterprise Manager (windows 2008) and from this solution manager SSO to Wily Enterprise Manager is working.
    Please help me with your expertise to solve this problem.
    Best Regards
    Davinder

    Hello Singh,
    Could you check if you have maintained these parameters in instacne profile ?
    From SCN post -> http://scn.sap.com/thread/969538
    Hi Hector,
    To configure SSO as per initial setup guide, please check your profile parameters in your Solution Manager as below:
    You have set up SSO, see also:
    SAP Note 817529: Checking the SSO Configuration
    Installation Guide and Security Guide for SAP Solution Manager
    Create the following profile parameters in the instance profile:
    login/create_sso2_ticket = 2
    login/accept_sso2_ticket = 1
    icm/host_name_full = fully qualified server name
    This parameter must be attributed to the fully qualified server name (for example wdfd002568.wdf.sap). The name must contain at least two periods. See also SAP Note 434918.
    Hope this helps,
    Regards,
    -Rohan
    BR,
    kamil

  • Wiley Enterprise manager offline issue

    Hello All,
    The Wiley Enterprise Manager which was running smoothly went offline.
    It is not getting started when i try to start. Am pasting the contents from log file 'IntroscopeEnterpriseManager.log' below,
    Introscope Enterprise Manager failed to start because:
    An error occurred while trying to start Isengard.
    Press 'Enter' to acknowledge....
    nager.Authentication] Introscope WebView connections will be assigned the name "WilyWebView"
    12/07/11 05:42:15 PM GMT+05:30 [INFO] [Manager.Authentication] Configured the Manager of Managers user using private key internal/server/EM.private
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Started hot config polling.  Polling interval set to 60 seconds
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager.ServerSocketFactory] Created Server Socket Factory: com.wily.jip.server.ext.DefaultServerSocketFactory
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Using data directory: /usr/sap/ccms/wilyintroscope_sd2/data
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] The system will store non-counter zero values.
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] The system will shut down if there are Disk I/O errors in 5 continuous timeslices.
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Using archive directory /usr/sap/ccms/wilyintroscope_sd2/data/archive
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Reading Smartstor Metadata
    12/07/11 05:42:16 PM GMT+05:30 [INFO] [Manager] Loading metadata file: data/metrics.metadata
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Finished reading Smartstor Metadata
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Thread priority set at 1
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Data tier 1 configured at collection frequency 15 seconds for 1 day
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Data tier 2 configured at collection frequency 60 seconds for 7 days
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Data tier 3 configured at collection frequency 300 seconds for 23 days
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] SmartStor Tiering time offset configured to 0:00
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] SmartStor conversion of Spool to Data time offset configured to 0 minute
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Configured EM Global Live Metric count limit at 500000
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Configured per-agent metric count limit at 50000
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Configured EM Global Historical Metric count limit at 1200000
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Available processors is 8
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.ConnectionTicket] Agent connection tickets = 8
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.Agent] Agent automatic unmount delay configured to 60 minute(s).
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.TransactionTracer] Storage directory configured to /usr/sap/ccms/wilyintroscope_sd2/traces
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager.TransactionTracer] Configured introscope.enterprisemanager.transactionevents.storage.queue.limit to 1000
    12/07/11 05:42:17 PM GMT+05:30 [ERROR] [Manager] The EM failed to start. Unable to open the Perst backing store: /usr/sap/ccms/wilyintroscope_sd2/traces/traces_20111119.db
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Shutting down data persistence subsystem
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Shutting down the Isengard server
    12/07/11 05:42:17 PM GMT+05:30 [INFO] [Manager] Orderly shutdown complete.
    Kindly advice,
    Thank You,
    Regards,
    Hasan

    Hello,
    The new problem is that sometimes this historical trace and data might got corrupted due to abnormal termination of EM.
    In this case please take following steps:
    1. check if there is enough space in the directories /traces and /data.
    2. use the script IndexRebuilder.sh in EM installation folder to try to rebuild the data corrupted.
    3. If there is any error appearing during executing the script, that means the historical data got corrupted and cannot be rebuilt. Proceed to next item (4).
    4. As mentioned in the section 2.17 "Enterprise Manager Corrupted Data Files" in the IntroscopeFAQ.pdf attached in the NOTE 797147, the solution is to delete the directories /traces and /data and restart your  EM to re-generate these directories. The side effect is that you will lose all historical data that is stored in the Enterprise Manager.
    Best regards,
    Guilherme

  • How to access introscope enetrprise manager in solution manager

    Hello All,
    I have installed Introscope enterprise manager on Solution manager system  in windows successfully
    Now when I am executing  introscope enetrprise manager,just a command prompt opens and nothing happens.
    Any ideas?
    Also How can I access introscope enetrprise manager?are there any different ways to do it?
    Rohit

    Hi Rohit,
    If your Enterprise Manager is setup and running. You can access it via wily webview or Workstation.
    These are the standard GUIs avaialble for accessing data in EM.
    1) Webview is a webbased tool, and you can access it through browser - http://<hostname>:8081/webview
    2) Workstation- you have to install this in your PC and connect it to EM, Its more powerful tool than webview and you need to hava pre-requisite java version installed.
    but, by which mehtod you are trying to open EM??.. EM contains only logs.
    When you say setup is complete, is the EM's services running?..
    Also, while performing the Basic Configuration- You have to map the EM data to solution manager and perform the Diagnostics setup step. Then you can launch the webview from workcenter -Root cause Analysis.
    Hope this helps.
    Thanks,
    Jagan
    Edited by: jagadheeshan govindasamy on Sep 4, 2009 5:18 PM

  • Wily Instroscope Agent connection problem to Enterprise Manager

    Hello!
    Perhapse some of you guys deal with this problem before and can give me an hint?
    I install the Wily Introscope Enterprise Manager and one Agent according to the "Introscope Version 7.0 Installation Guide for SAP" but if i try to start the agent i get the Warning: [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at <server>:6001, com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (1)
    I checked if the server is reachable with ping and also if the port is open via telnet from the system where i have installed the Agent.
    Any ideas?
    King regards, Stefan

    Hi Jens, thank you for your answer, yes i tried to use the ip adress instead, with the same result.
    Very strange from my  point of view is the thing that i can't get a telnet connection if i try to connect to from the enterprise manager server to the agent server. This look like a network issue to me, dosen't it? in the other direction there is no problem and on the enterprise manager server i see that listening on 6001 is on. If I check this on the agent machine, i can't see anybody listening on this port. But from my point of view it should?
    Webview isn't in place right yet, i thougt i should finish the "normal" configuration first?
    Regards, Stefan

  • Wily Enterprise Manager fails to start up

    Hi Gurus:
    While starting up Wily EM I get the below.  Can anyone point me in the right direction with this?
    ======================================================================
    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 pap64dev-20060511 (SR2))
    IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423-20060504 (JIT enabled)
    J9VM - 20060501_06428_BHdSMr
    JIT  - 20060428_1800_r8
    GC   - 20060501_AA)
    JCL  - 20060511a
    Introscope Enterprise Manager failed to start because:
    An error occurred while trying to start Isengard.
    Press 'Enter' to acknowledge....
    ====================================================================
    Thank you v much, Viji

    Hi David:
    It worked fine previously.  This has been installed  a while ago ( a couple of years). We did have a couple of problems recently with corrupt data files.  Deleting the concerned datafile and restarting Wily solved the problem.  However I haven't a clue on how to get this going.
    thanks , Viji

  • SMD Agent Metrics/BOE native code metrics Missing in wily Enterprise Manager

    SMD Agent and BOE native code metrics are not updated to wily EM. Previously the metrics were written to Wily EM. This is standalone setup of Wily Ent Manager without Solution Manager.
    Environment:
    Standalone Wily introscope Eterprise Manager - Introscope Enterprise Manager 9 SP15
    DIAGNOSTICS AGENT 7.3 SP03 (incl. HostAgent)
    BI 4.0 SP6 Patch 6, Windows 2008, Clustered/Distributed.
    Logs:
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Initialization done.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Service provider initialized.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Agent Applications started.
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Smd connector has been disabled
    Apr 25, 2014 3:54:35 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from INITIAL to CONNECTING
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to DISABLED
    Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Fatal      com.sap.smd.wily.hostagent.WilyHostService - init(...): Failed to start Agent!
    [EXCEPTION]
    java.rmi.RemoteException: WilyHostAgent start failed; nested exception is:
      com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:122)
      at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
      at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
      at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
      at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
      at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
      at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
      at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
      at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
      at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:111)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:154)
      at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:733)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:495)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:354)
      at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:311)
      at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:1016)
      at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:933)
      at com.sap.smd.agent.connection.SMDConnectionTask.startOffline(SMDConnectionTask.java:862)
      at com.sap.smd.agent.connection.SMDConnectionTask.internalAttemptConnection(SMDConnectionTask.java:549)
      at com.sap.smd.agent.connection.SMDConnectionTask$1.run(SMDConnectionTask.java:107)
      at com.sap.smd.agent.connection.P4JNDIContextHelper.executeInSecurityContext(P4JNDIContextHelper.java:148)
      at com.sap.smd.agent.connection.SMDConnectionTask.attemptConnection(SMDConnectionTask.java:102)
      at com.sap.smd.agent.connection.SMDConnectionTask.run(SMDConnectionTask.java:1282)
      at java.lang.Thread.run(Thread.java:743)
    Caused by: com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
      at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:510)
      at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:99)
      at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
      ... 26 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
      at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
      at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
      ... 29 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1782)
      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
      at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
      at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
      at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2857)
      at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:235)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
      at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
      at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
      at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
      at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
      ... 31 more

    Hello Gopal,
    Please refer to section Wily Introscope setup for BOE 4.0 of this wiki:
    Managed System Setup of BOE 4.0 system in Solman 7.1 - SAP Solution Manager Setup - SCN Wiki
    You may also found interesting
    Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
    https://service.sap.com/sap/support/notes/1722874
    https://service.sap.com/sap/support/notes/1357901
    Best Regards.
    Luis Roel

  • Hostname change option in Willy Enterprise Manager

    Hi,
         We are facing one problem during configuration of Introscope agent with
    Wily enterprise manager (In Solution Manager 7.1).
    Scenario:
    Wily EM installed on Solution Manager Server (unxa0275) but introscope
    agents for managed system are not able to connect to the EM in solution
    manager.
    Issue:
    There are 2 host name for (unxs0275 and unxa0275) for solution manager
    server. Unxa0275 is the actual host name and unxs0275 is the virtual
    host name for the same server (solution Manager).
    When I installed EM (Enterprise manager) on solution manager server it
    get installed with host name as unxa0275 and that is not accessible by
    the other server ( managed system).
    Option:
    1.Is it possible to change the Wily EM host after installation? If yes
    then where I need to make changes.
    2.Or weather I need to install the EM again? And then in that case how
    to set the host variable so the installation
    script u201C./introscope7.1solaris.SAPEndUser.binu201D will take the host name
    unxs0275 rather then unxa0275.
    I need to change the hostname from Unxa0275 to UnxS0275??During the Installation of EM hostname option is not coming.Please guide me.

    Hi,
    you can change to hostname of wily introscope enterprise manager within the solution manager to a virtual hostname as follow:
    call SICF an activate Service WD_SISE_ADMIN
    call transaction SOLMAN_SETUP_ADMIN
    Choose Generic Storage Admin UI
    Configurtaion ID: EM_CONFIG_ID-EM_CONFIG_ID
    change values CLIENT_HOST, EM_FQN, EM_IP, LMDB_SERVEERNAME, SERVERNAME, SERVER_HOST --> save and check the new values in SOLMAN_SETUP -> Basic Configuration --> Configure CA Wily Introscope (virtual host should now be displayed)
    afterwards you have to supply all managed systems with the new configuration Managed System Configuration
    Enter System Parameter (Check Introscope Host "edit and save")
    Configure Automatically (Run "Introscope Host Adapter" and "Byte Code Adapter Installation")
    Regards, Christoph

  • Error loading Management Modules of Enterprise Manager 8.2.3.5

    Hi all,
    actually we have installed the Wily Enterprise Manager 8.2.3.5 on Linux x64.
    Starting the manager we get the following errors in the IntroscopeEnterpriseManager.log
    2/23/11 03:41:09 PM CET [INFO] [Manager.ManagementModule] Loading Management Module "MSFT .NET - Duet"
    2/23/11 03:41:09 PM CET [INFO] [Manager.ManagementModule] Loading Management Module "SAP J2EE - Duet"
    2/23/11 03:41:09 PM CET [INFO] [Manager.ManagementModule] Loading Management Module "SAP J2EE - NetWeaver PI(XI)"
    2/23/11 03:41:09 PM CET [INFO] [Manager.ManagementModule] Loading Management Module "SAP Navigation"
    2/23/11 03:41:09 PM CET [INFO] [Manager.ManagementModule] Loading Management Module "SAP Host"
    2/23/11 03:41:09 PM CET [INFO] [Manager.ManagementModule] Loading Management Module "SAP Business Objects"
    2/23/11 03:41:10 PM CET [ERROR] [Manager]
    2/23/11 03:41:10 PM CET [ERROR] [Manager]
    2/23/11 03:41:10 PM CET [ERROR] [Manager]
    2/23/11 03:41:13 PM CET [ERROR] [Manager]
    The error indicates a problem during the load of the Management Modules.
    Also we observed problems calling dashboards from the Console in the wily Introscope Webview.
    For e.g. the dashboard J2EE CPU and memory Detail
    Calling this dashbord ends in the following error:
    An error occurred fetching this dashboard from the Enterprise Manager: null
    What could be the problem for the errors during the Management Modul load ?
    Thanks in advance for your help.
    Kind regards
    Anton

    Hello Anton,
    Please download the SAP Management Modules from the marketplace.
    Check note 797147 and note  1579474 about Management Modules usage.
    Best regards,
    Guilherme Balbinot

  • Solution Manager Diagnostics Self Check Error with Enterprise Manager

    I'm trying to get the Solution Manager Self Diagnostics Self Check running,
    but I'm always getting the follwing Error:
    The Enterprise Manager on host 'hdeas81' and port '6443' cannot be reached.
    The Log File of the Introscope Manager shows the following line:
    6/29/09 01:15:36 PM CEST [INFO] [Manager.PostOfficeHub] Server listening for incoming ssl socket connections on port 6443
    Netstat -a is also showing that Port 6443 is open and Listening.
    The Port is also reachable via telnet.
    any suggestions what might be the problem?
    Thanks in advance
    Marco

    thanks, but i'm trying to get a ssl connection on port 6443.
    I have also another error in the diagnostics check (maybe related)
    An unexpected error occured
    in Detail i get the error:
    java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Connection refused: connect
         at org.w3c.www.protocol.http.HttpURLConnection.error(Unknown Source)
         at org.w3c.www.protocol.http.HttpURLConnection.checkReply(Unknown Source)
         at org.w3c.www.protocol.http.HttpURLConnection.getResponseCode(Unknown Source)
         at com.sap.sup.admin.selfcheck.checks.helper.HttpHelper.getHttpResponseCode(HttpHelper.java:48)
         at com.sap.sup.admin.selfcheck.checks.wily.em.UICheck.process(UICheck.java:78)
         at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165)
         at sun.reflect.GeneratedMethodAccessor541.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
         at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
         at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274)
         at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
         at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
         at java.lang.Thread.run(Thread.java:534)

  • I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

    I can not make a "Byte Code Adapter Installation"
    When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
    Please help to resolve a number of questions that might help me complete the setup :
    1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
    I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
    2 . Why Server Node is empty detail settings ?
    JDK Location: 
    Enterprise Manager Host: 
    Enterprise Manager Port: 
    Introscope Agent Name: 
    Introscope Agent Profile: 
    Autoprobe Directives: 
    Wily Version: 
    Introscope Agent Version: 
    Introscope Agent Log Location:
    3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
    And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
    Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
    there is such an item:
    2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
    However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

    The problem was resolved a small manipulation - on stage Basic Configuration,
    point 3 "Configure CA Introscope"
    I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
    Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
    Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

Maybe you are looking for