Connection Solution Manager - Wily Enterprise Manager

Hi all,
we want to use SOlutionDiagnostics to monitor our abap and java instances. First, we would like to connect a abap system
to our Enterprise-Manager and watch the results in solution manager.
In transaction http//solutionmanagerhost:port/smd we are able to connect manually to our enterprise manager und log in, but solution manager didn't find the enterprise manager. ( we got the message: all the enterprise manager are offline ).
What could be the reason ?
How is an abap system registered in Enterprise Manager ? For java systems you have to add addiontianl java parameters in configtool. But for abap systems ?
is there any howtoguide, how to connect systems to diagnostic and wathc the results in solman_workcenter für E2E ?
the solution manager diagnostic instance ist already installed and registered over http://>SOLMANHOST>:/smd/go/ADMIN_AGENT
kind regards
andreas

Hello,
Are you using versin 8.0? If not use version 8.0.
Regards,
Paul

Similar Messages

  • 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

  • Wily Enterprise Manager 8 connection to SM Ehp1 failed

    Hi guys ( SM eph1 sps18, x64 jdk_ 17,Wily Enterprise Manager 8 )
    Have installed Wily Enterprise Manager 8 successfully. Its up and running with out errors.
    when i go to Diagnostics Setup -- Managed Systems--Introscope Agent
    Unable  to find the wily enterprise server
    error: Enterprise Manager retrieval
    Operation Failed
    Operations results - java.sql.SQLException: All configured Enterprise Managers are offline - check configuration.
    I have checked multiple times , Enterprise manager is up and running( as windows service)
    any advise how to fix

    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

  • Wily Enterprise Manager Service not Started in Windows 2008 Server

    Hi All,
    Our Solution Manager is in EHP1 SP21 and OS-Windows 2008 Server.
    We installed Wily Enterprise Manager 8.0. and found 1 non-fatal error in the installation log. The service is not starting.
    However it works fine for Windows 2003 Server.
    Can anyone encountered with the same kind of problem?
    This is the latest log file information:
    Summary
    Installation: Successfulwith errors.
    387 Successes
    0 Warnings
    1 NonFatalErrors
    0 FatalErrors
    Action Notes:
    Execute ANT Script:       Script:
                              Status: ERROR
                              Additional Notes: ERROR - E:\usr\sap\ccms\wilyintroscope\install\em.installer.exec.ant15.xml:425: Timeout: killed the sub-process
    Thank you in advance.
    Regards
    Sanjai

    Note 1273028 - Introscope 8 Release Notes resoved this issue.
    Known problems in all Releases 8.x
    2. Windows Server 2008 is not yet officially supported by CA Wily for the Enterprise Manager. If you want to install the Enterprise Manager anyway, set the "Windows 2003 compatibility mode" for the installer before launching it. To activate this mode, right click on the installer.exe file in the Windows Explorer, select tab "Compatibility", activate the check box for compatibility mode and select Windows 2003. If you do not set this, the installer will consider your OS as Unix and install shell scripts (no suffix) instead of batch files (.bat) and leave out some files for Windows Service registration.
    If the windows service still fails to start please check if files ServiceWrapper.jar and ServiceWrapper.dll are present in folder lib. If not download them from attachment of this note.
    The service should start although giving an error message regarding the ServiceWrapper.dll. You can ignore this error.

  • Wily Enterprise Manager not starting

    Hello colleagues,
    After migrating SAP solution manager to a new server (standard sap method R3load based despite same platform in source/target) we find wily Enterprise manager console stops some seconds after start.
    We just copy the whole FS where wily was installed on source system and the log error is:
    !SESSION 2012-02-21 19:21:53.357 -
    eclipse.buildId=M20060629-1905
    java.version=1.4.2.25
    java.vendor=Hewlett-Packard Co.
    BootLoader constants: OS=hpux, ARCH=IA64N, WS=motif, NL=en
    Framework arguments:  -product com.wily.introscope.em.product
    Command-line arguments:  -consolelog -product com.wily.introscope.em.product
    !ENTRY org.eclipse.osgi 4 0 2012-02-21 19:21:57.872
    !MESSAGE Application error
    !STACK 1
    java.lang.RuntimeException: Application "com.wily.introscope.em.application" could not be found in the registry. The applications available are: org.eclipse.
    equinox.app.error.
            at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:236)
            at org.eclipse.equinox.internal.app.EclipseAppContainer.start(EclipseAppContainer.java:92)
            at org.eclipse.equinox.internal.app.Activator.addingService(Activator.java:129)
            at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064)
            at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1042)
            at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:967)
            at org.eclipse.osgi.framework.internal.core.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:94)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1224)
            at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
            at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
            at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEventPrivileged(Framework.java:1603)
            at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEvent(Framework.java:1578)
            at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.<init>(ServiceRegistrationImpl.java:103)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.createServiceRegistration(BundleContextImpl.java:657)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:609)
            at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:675)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:359)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:331)
            at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
            at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
            at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
            at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
            at org.eclipse.core.launcher.Main.main(Main.java:30)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:331)
            at com.zerog.lax.LAX.launch(DashoA8113)
            at com.zerog.lax.LAX.main(DashoA8113)
    !ENTRY org.eclipse.osgi 2 0 2012-02-21 19:21:57.972
    !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
    !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-21 19:21:57.973
    !MESSAGE Bundle update@plugins/com.opensymphony.quartz_1.6.0.jar [7] was not resolved.
    !SUBENTRY 2 com.opensymphony.quartz 2 0 2012-02-21 19:21:57.973
    !MESSAGE Missing Constraint: Bundle-RequiredExecutionEnvironment: J2SE-1.5
    !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-21 19:21:57.974
    !MESSAGE Bundle update@plugins/com.wily.authentication.ldap_8.0.0.jar [8] was not resolved.
    !SUBENTRY 2 com.wily.authentication.ldap 2 0 2012-02-21 19:21:57.974
    !MESSAGE Missing required bundle com.wily.introscope.em_0.0.0.
    !SUBENTRY 2 com.wily.authentication.ldap 2 0 2012-02-21 19:21:57.975
    !MESSAGE Missing required bundle com.wily.introscope.em.client_0.0.0.
    !SUBENTRY 1 org.eclipse.osgi 2 0 2012-02-21 19:21:57.975
    !MESSAGE Bundle update@plugins/com.wily.authentication.local_8.0.0.jar [9] was not resolved.
    Could you kindly help?
    Best Regards!!!!

    Hi,
    have you found any solution for this. If you found any solution please post it back here
    we are also facing the same issue.
    Thanks
    Chaitanya

  • How to connect 10g database through Enterprise manager???

    Hi All,
    I want to connect the database through Enterprise manager.
    My database is on 10g. Version is 10.1
    Please tell me the procedure to connect the database through E.M.
    Thanks and Regards,
    Prathamesh.

    Are you thinking of the Enterprise Manager supplied with Oracle9i? If yes - it doesn't work quite that way ... and the 9i java OEM is not compatible.
    Use the enterprise manager supplied with the 10g database, called the dbconsole (look for a service or start it using 'emctl start dbconsole') and access it using http://{localhost}:5500/em
    If that doesn't satisfy you, load the updated version of the OEM 9i java standalone from the 10g client disk.

  • Entreprise manager versus enterprise manager grid control

    Hello,
    This may seem a dummy question, but wath is the difference between Enterprise Manager and Enterprise manager grid control?
    Thanks

    And the anwser is:
    Check document OEM Concepts page 12-1.
    Thanks
    Gonçalo Ribeiro

  • Connecting to Oracle 10G Enterprise Manager console

    Hi SDNers,
    We've recently successfully upgraded Oracle from 9.2.0.7 to 10G (as part of a Solution Manager 4.0 upgrade) and I'm now interested in getting started with the new Oracle 10G Enterprise Manager (web-based console).
    I'm at the point where I have EM up and running, but it is not connecting to our SAP database because it is trying to connect to port 1521, whilst the database uses 1527.
    Does anyone know how to change the EM configuration so that it points to port 1527 and therefore connects to the SAP database?
    Thanks in advance,
    Arwel.

    Yep!
    Here's a copy of its contents:
    Thanks,
    Arwel.
    tnsnames.ora Network Configuration File: d:\oracle\SOL\102\network\admin\tnsnames.ora
    Generated by Oracle configuration tools.
    SOL.WORLD =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = lvrplsolman)(PORT = 1527))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = SOL)
    EXTPROC_CONNECTION_DATA.PRINCES.CO.UK =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
        (CONNECT_DATA =
          (SID = PLSExtProc)
          (PRESENTATION = RO)

  • 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

  • Memory Requirements for Wily Enterprise Manager

    Hi,
    I am using Wily 8.0 and we are seeing slowness in SOLMAN JAVA stack and in Wily EM. Before throwing memory I am trying to understand following points. I have already gone through installation documents which does not cover following points
    1> I understand Wily EM requires heap memory. Does Wily EM heap memory is same as JAVA heap, I mean both JAVA node and Wily EM access same assigned part of memory OR both JAVA node and Wily EM needs seperate memory? As per this I will throw more memory at box.
    2> Installation guide say "Increase the heap size (u2013Xmx) of the Enterprise Manager if you have more than
    ~10 agents" but how much? I did not see any formula for this.
    3> I am observing Wily EM process at O.S level is keep running continuously since I restarted it last time (which is weeks now). Is it normal?
    Thanks

    Amit,
    Question 1.
    Wily needs JVM Heap memory, which would be different from J2EE Instance HEAP.  Adding additional physical RAM to your server will definitely help.
    Question 2.
    Set the Heap Size parameters to a minimum of 1024 MB
    Initial Java Heap Size (in MB)
    wrapper.java.initmemory=1024
    Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=1024 ((higher the better....)
    Set the Java VM parameter u2013Djava.awt.headless=true for all platforms.
    Otherwise, the Enterprise Manager will need an X server, i.e., the DISPLAY
    environment variable must point to a valid X Windows server.
    The file to maintain the parameterization is EMService.conf available in the
    standard insttallation path /usr/sap/ccms/wilyintroscope
    Please refer to SAP Note 1273028
    Question 3.
    The process should be running for Wily to work (this is my understanding).  We also have this running for months on our server.
    Regards,
    Ravi

  • From Forms Product Management - Using Enterprise Manager

    I have just posted a new viewlet which shows the Enterprise Manager features in 10g. If you have not used EM before its a great high level demo which shows you how yuo can manage your Forms applications from a console. For those already familiar with EM you will be able to check out some of the new work we have done in integrating Forms and EM.
    If you go to http://otn.oracle.com/products/forms you can see the feature on the news list.
    Thanks
    Grant Ronald
    Forms Product Management

    Grant
    I don't think you'll get too many replies. I expect most people here are either committed to using Web Forms already (and so don't need this functionality) or else are still in client-server mode (and so don't understand what you asking).
    We are just in the process of migrating from Forms4.5 to 9i (I'm in the WebUtil beta) and we are still finding out all sorts of non-obvious things about web-deployment - don't get me started on how awful the whole GIF thing is! So I'm not really qualified to have an opinion about Webstart. I only have the vaguest idea what it does and I'm not sure I want to read up about it just so I can tell you whether to go ahead with it.
    What I will say is this:
    (1) Anything that makes 9i Forms more like a client-server experience for the users would be a good thing, bceause it would minimise the shock of transition.
    (2) Choice is a good thing. Your recent experience of developers' spleen over the removal of client-server should tell you that people respond well to being given options and badly to having them removed.
    (3) If I've correctly understood Haris Peco in their second point we could get rid of O9iAS and that would be flipping marvellous for everybody (except possibly the VP in charge of O9iAS Sales :P).
    My tuppence ha'penny worth.
    Cheers, APC

  • Wily Enterprise Manager not found/offline

    I am working on setting up our E2E, I've reached the setup of the managed systems but when I get into it I can't select the Enterpise Manager; it is not an option in the drop down list.
    I've gone through and entered the correct server, port, and log-in information correctly as directed during the setup.
    We have had our Wily setup for a while now and just are getting around to being able to use. The Manager is setup on a different server using a different platform if that makes a difference; don't think it should though.
    Please let me know if you see that I am missing something on this. Thanks for your time.

    Thank you for the suggestion. I did end up upgrading the EM from 7.2.2 to 8.1.0 but it still didn't help populating that drop down field.
    One thing I was not able to do during the installation was the automatic update to the Introscope agent for my Solution Manager system, it is stating that the ISAGENT has either been deployed or is at a later version. The it was last effected was 12/2007 and is still on the 7.2.2 agent. Is there a way to undeploy this to bring in the new one?
    Thanks again.

  • 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

  • CONNECT -TIME FAILOVER ERROR IN ORACLE 10G ENTERPRISE MANAGER

    Hi All,
    Please can anyone explain why I am getting this error and how to fix it?
    I was trying this exercise to create a backup LISTENER to support a connect-time failover in Enterprise manager.The steps were .1)I clicked the Listener's link on Database control page.2)Next I clicked the Net Services Administration link.3)I selected listeners from the Administer drop-down list and clicked Go.
    I received the ERROR message that "Listener administration cannot be performed, as this Oracle Home
    "/opt/oracle/DB10g" is not a server installation.
    Is this normal?
    What can I do to fix it?Please help!
    Thanks

    you are trying to start the listener on the machine that has enterprise manager installed.
    Listener executable is available with oracle database software install( enterprise or otherwise).
    You will have to pick the listener on a database software install box to configure it

Maybe you are looking for