EWA For EP System

Hi All,
I want to generate EWA report for my Enterprise Portal system which is JAVA Based.
I had read the document attached in note 976054. As per this note data will be collected using SMD.
Now I want to know that from where can I start SMD? Is the any configuration require for SMD?
My current solution manager level is Solution Manager 7.0 with EHP1 with SP19. So any new patch installation is require?
All configuration will require at solman side only? No any configuration will require at Enterprise Portal side?
Please guide me how can I generate EWA?
Regards,
Nisit
Edited by: Nisit  Patel on Aug 10, 2010 7:30 AM

Hi Nishit,
Install SMD server on Solution manager system which will common for all portal system which is done once.
Install SMD system on Portal system  with sapinst. now a days it come automatically installed during Installation of system.
Instally Wilyintro-scope on Portal system .
All system shuold be registered successfully in your SLD of lanscape for EWA generation.
Thanks
Manas Behra

Similar Messages

  • EWA for Java system / portal

    Hi,
    We have configured EWA for ABAP systems, help required to configure EWA for Java / portal systems
    Ours is  solman EHP1 - support pack level 6
    Regards

    Hello,
    For Java systems you need to perform a managed system setup, then schedule in solman_ewa_admin.
    Regards,
    Paul

  • Activate EWA for satellite system in 3.2

    Hello,
    We have solution manager 3.2 with all the latest patches, and have included the satellite system in the landscape and generated the RFC's. Need to activate EWA for the system. Have defined a Solution. Need to how do you include a system in the solution because when i click on Solution directory --> setup EWA, it gives a message,
    "NO system found in landscape"
    Any suggestions / inputs are appreciated.
    Thanks and cheers,
    Chetan

    HI ,
    Kindly follow the below steps for the EWA activation:
    1)go to transaction SMSY enter your system details and check the system data is updating with the SLD (check this option in SMSY_SETUP)
    2)then define logical component fo rthis system then define this logical component under solution
    3)you will be having a option under that EWA configuration click on EWA active (check )
    and check the Send to SAP if you want the EWA repor thas to reach SAP once the Report is Red after analysis done in Solman by the Job SMS*
    4)then go to SDCCN in the solman then trigger the activation of session data for the particular sysytem if the RFC SM_SIDCLNT<CLNT>_back exists then task created in the satelite system for the session data to Solamn
    5)then check the EWA report and do processing in the operation for that solution
    Best Regards,
    Srekantha Reddy.M

  • EWA for Java Systems

    Dear All,
    we had configured some java instances on our solution manager (Ehp1 sp 7).
    But if we try to add the systems to the solution and schedule the ewa report the solution try to connect to sdccn.
    Based on what i was able to read in other posts the pure java systems doesn't use sdccn (of course they don't have abap).
    In the smsy configuration for the java systems we have as product version Netweaver 7.0 and as relevant product instance selection these four line:
    Adobe Document Services
    Application Server Java
    EP Core
    Enterprise Portal
    all with instance sid as technical system and java as system type.
    Do i need to do something else to let the Solution understand that these systems are pure java so solution will not try to launch the sdccn transaction?
    (Diagnostic agent is already getting data and bi content is active).
    Thanks and regards
    Federico Pancucci

    Hi Federico,
    It should be described in the attachment of SAP Note 976054.
    As well, please take a look at the following two URL's which have more documentation on this. 
    If you still need more help, please tell me what is the exact issue that you are facing, such as getting a certain error after the session (ewa) is created in DSWP or getting red flagged?
    http://service.sap.com/diagnostics
    http://service.sap.com/ewa
    Thanks,
    Mark

  • Metrics of EWA for managed system are in gray

    Dear All,
    We have solman7.1, system configuration and basic configuration are all successfully, we have a managed system, the Managed system configuration are successfully, in system monitoring, we see all EWA metrics are in gray.
    but EWA report was generated successfully.
    Could you please advise what could be the cause and how can i fix this gray issue?  Thanks.

    Hi,
    Please bear in mind that EWA metrics are collected only once per week ususally on a Monday so you could check today and see if the metrics are being collected? If not you could check if the data provider delivers data or not using the E2E_DPC_GET_DATA_CHECK program.
    Kind regards,
    Roland

  • Configuration of EWA reports for java systems.

    Hello,
    I am facing a problem with configuration of EWA reports for SAP NW Portal.
    I have already configured EWA for abap systems, and those are running good on weekly basis. but i have problem with configuration of reports for java systems.
    So far, i have installed an SMD agent and CA on my EP-satellite system. I have also configured and SMD server on my Sollution Manager and registered the SMD agent on SMD server and installed Willy Introscope on SMD server.
    I  am using a central SLD which is running on different host as Solution Manager. I did all the configuration (smsy_setup, configuration of sld_data_supplier etc... )
    I have also created the system in SMSY, matched the smsy with SLD and assigned Logical component to java system.
    So far, so good according to manuals but when i  want do define data collection in the SMD for Gargage Collection  (task in scheduler) i cannot see host of my portal system.
    I can see only the hosts (scheduler tasks ) of all abap system for which the EWA reports have already been  generated.
    Am i missing something?
    Some configuration in SMD?
    My solution manager is running on Sap NW 7.0, SPS16,
    Sattelite system  NW 7.0 EP, SPS 6 (planning to SPS 19)
    Thank you for your advices!!!

    Hi Suveer,
    I did the configuration before. I forgot to mention it.
    I found this errors in Diagnostic Setup, maybe this could be the cause of the issue.
    Step BI Details
    Cannot invoke CCMSBISETUP on host localhost
    !! Exception : An exception occured during the execution of this function 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC'.(cause=com.sap.sup.admin.abap.rfc.exception.RfcExecutionException The function named 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC' doesn't exist!)
    Exceptions
    com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: An exception occured during the execution of this function 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC'.
    at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:92)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.setupBIConfiguration_ccmsBiSetup(AbapSysRfcAdapter.java:743)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.setupBIConfiguration_ccmsBiSetup(AbapSysRfcAdapter.java:727)
    at com.sap.sup.admin.setup.ManagingServices.startCcmsBiSetup(ManagingServices.java:2686)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:334)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:378)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
    at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:278)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: The function named 'CCMSBI_RUN_SIMPLE_SETUP_IN_BTC' doesn't exist!
    at com.sap.sup.admin.abap.rfc.function.RfcFunction.execute(RfcFunction.java:62)
    ... 37 more
    And also this one>>
    Step RFC Details
    Failed to create TCP/IP RFC on ABAP side (SM59)
    !! Exception :      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE
    Exceptions
    com.sap.aii.proxy.framework.core.BaseProxyException:      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE
    at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
    at com.sap.sup.admin.setup.abapproxy.tcpiprfc.TcpIpRfcProxy_PortType.inst_Create_Tcpip_Rfcdest(TcpIpRfcProxy_PortType.java:16)
    at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:663)
    at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:637)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:300)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:378)
    at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
    at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:278)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    And in the troubleshooting setup for managed systems, i can see that no initial upload was found form the SMD agent which is running on Java System.
    Thanks a lot for your remarks

  • EWA for non-ABAP systems

    Hi,
    We are planing to implement EWA for Java systems. Currently EWA is active for all ABAP systems. Do we need Wily Introscope in order to setup the EWA for non-ABAP systems? Or just we can use the SMD to generate EWA reports for Java systems?
    Any idea?
    Thanks,
    Kris

    Thanks Paul
    We are on SM 7.0 EhP1. But I see following info in note 976054. It says data sources for EWA are different on 7.0 EhP1, does it mean we don't need wily from 7.0 EhP1 onwards?
    Data sources in Solution Manager Diagnostics up to SP17 used for EWA for non-ABAP components analysis are:
                          - Introscope (SAP Note 797147),
                          - Garbage Collection (SAP Note 1079125) and
                          - Portal Activity Reporting (SAP Notes 936612 to know how to activate PAR and 914791, 1075276 to configure SQL           
                            Command Console).
    Starting with Solution Manager 7.0 EHP1 (SP18) the data sources are:
                          - Solution Manager BI for performance data
                          - Configuration and Change DB(CCDB) for configuration data
    Thanks,
    Kris

  • EWA for non-productive Systems

    Hi all,
    is there a possibility to get Early Watch Alerts for Systems in a Solution, which are not marked as productive.
    I don't want to create many solutions.
    The same problem i have with the monitoring, I only see the productive in the monitoring overview.
    Regards
    Tobias

    >
    Schlosser Tobias wrote:
    > I have added Systems to the Solution XY. The Leading Role of this solution is "productive Systems"
    >
    > I have add System PR1 (Productive) and System DE1 (Development).  But I can only see the EWA for the Productive.
    > If I want to see the EWA for the Development I have to delete the log. components and switch the leading role to "Development Systems".
    >
    > That's very inconvenient.
    >
    > I wan't one Solution with all my Systems, and EWAs for every System in it. Is this possible?
    Yes, it's possible to have all systems (Prod, Dev, QA, ...) within one solution and to have EWA activated.
    You need to choose "Put in Solution" from the context menu. See screen shots attached.
    Regards,
    Ruediger

  • EWA Report not being sent for two systems

    Hi Experts,
    We are having one issue in EWA Report in solution manager. Searched hard but could not find solution.
    Our solution manager is configured to provide EWA for 4 systems- ECC, BW, PI and Solution manager itself.
    The configurations are in place to the extend that we are able to view the weekly reports in Solution manager.
    Issue is -
    1. We are able to recieve mail notification for Solution Manager and ECC but not able to get for BW and PI.
    2. The ECC report is coming ok, but Solution manager report is blank.
    The places I checked the configuration -
    1. SDCCN for all systems.
    2. SOLMAN_EWA_ADMIN - all systems active and chcked for EWA
    3. Background Jobs for all systems -Maintenance Package, Refresh Session, Earlywatch Alert for Solution Manager
    4. Background Jobs related to the task including SM:EXEC SERVICES
    Later on I deleted and rescheduled the job SM:EXEC SERVICES to make sure it covers all systems.
    Data is visible in Solution Manager but report is not being sent over mail for two systems- BW and PI.
    Solution manager report is being sent but empty.
    Please suggest.
    Regards,
    Sabita

    Hi,
    what is your ST verison? check this note applicable or not
    [https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1496931|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1496931]
    and chek the version of your service updated ST_SER too, patch this also solve the issue
    refer this [Note 1482818 - Service updates ST-SER 701_2010_1|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001482818&nlang=E]
    Jansi

  • EWA for Java only systems

    Hi,
    I'm searching for a guide to set up EWAs for Java only instances. Currently I have my Java instances in SMSY as system components, but how do I set up the EWAs as only ABAP instances are selectable. I'm using the latest SP, so this functionality should be available finally. I can't find a document about that anywhere, just some very bad documented snippets in SPRO...
    Regards,
    Pascal

    Hi Pascal,
    EWA for Java systems is currently in a pilot phase. It will be released with the note 976054, which is currently still being processed internally.
    Note 976054 contains a setup instruction for EWA for non-ABAP-components.
    Technically, for pure Java systems the "Central SDCCN" of the Solution Manager is used as indeed pure Java systems do not have a SDCCN.
    Double stack installations do not make use of the Central SDCCN, using their local SDCCN to obtain the non-ABAP data that is collected by the Diagnostics part of the Solution Manager.
    The note will be released in the very near future.
    Best regards,
    Walter Heibey

  • EWA for Java

    Hi
    I have setup the EWA for ABAP and now I want to setup for Java stack systems like portal and other NW systems. I have installed Wily Introscope 7.2 and now I am looking at the Root cause analysis setup guide where it says to "Activate the BI source system" - Could someone tells me why do I need to do this. Is it something to do with BI systems that we have in our landscape?
    Another question is - What is the difference between the SMD agents and Introscope agents and CCMS agents?
    Or could someone point me to a simple guide to setup the EWA for Java?
    Thanks

    where it says to "Activate the BI source system" - Could someone tells me why do I need to do this. Is it something to do with BI systems that we have in our landscape?
    No.
    The performance data collected through the introscope agent must be stored somewhere. SMD uses the introscope agent to collect the data. The data is not stored in flat tables but in BI cubes. This is why you need to install the BI content on the Solution Manager system. The SMD setup then activates the BI content in the SolMan. So basically BI technology is used to generate the EWAs for Java systems.
    You can, however, use an existing BI system instead to store the performance data, if you have the appropriate BI_CONT patchlevel installed. Actually there are some drawbacks, it´s not yet fully automated, manual tasks have to be done to make this work.
    Another question is - What is the difference between the SMD agents and Introscope agents and CCMS agents?
    The SMD agent provide a "basic connection" between the SolMan and the Java system, the Wily Introscope agents instrument the functions/methods/classes and collects performance data. The CCMS agents are on a "higher layer", they can check e. g. that a specific application (e. g. the portal) is running but they can´t find out, how long a specific java method takes to be executed.
    Or could someone point me to a simple guide to setup the EWA for Java?
    There is no "simpler guide" for that.
    Setting up EWA for Java a challenging and complex task. For us we decided that it´s not worth it because there are too many manual things to be done (profile changes which are overwritten each time you implement an SP (flightrecorder), incompatibilities of autoprobe connectors for Wily (on Linux), manual tasks need tobe done if you use an external BI system and others).
    Good luck!
    Markus

  • EWA for Java Version 7.0

    Hi,
    We are doing system monitoring for our ABAP & Java systems.
    As part of this, we were able to get EWA for all ABAP Systems, But the same is not working in JAVA.
    Is that possible to generate or configure EWA for Java Systems with version 7.0
    Please Advise. .
    Thanks
    Arun

    Hi Arun,
    Please note that the requirements for EWA for ABAP and JAVA systems are very different.
    To generate EWA reports for JAVA systems you have to install solution manager diagnostics.
    Please take a look at the notes below:
    976054   Availability of EWA for Non ABAP components
    1010428 End-to-End Diagnostics
    1274287 End-to-End Diagnostics SP18(EHP1)- SP19 - SP20 - SP21 - SP22
    If you have already done that, please check the troubleshootings guide attached to note 1332428 and the troubleshooting for workload analysis in service.sap.com/diagnostics -> Media Library.
    Hope this can help.

  • Config in Sol Mgr 4.0 for EWA reports for NW2004s Systems??????????

    Dear Experts,
    We have installed Solution Manager 4.0 with latest Patch Level.
    We also have  BI 7.0 and ECC 6.0 Systems in Landscape.
    Requirement :
    I have to generate <b>Early Watch Reports</b> for the both BI & ECC systems in our Solution Manager.
    Please Let me know the configuration & steps for integration and to generate EWA's for the systems on a weekly BASIS.
    Blogs / Links / Guides are highly appreciated.
    Thanks in Advance to all SOlution Manager Experts.
    Regards
    PR

    hi,
    Please check these. It will solve your problem.
    https://websmp206.sap-ag.de/~sapidb/011000358700006819072005E
    https://websmp206.sap-ag.de/~sapidb/011000358700006936042005E.sim
    https://websmp206.sap-ag.de/~sapidb/011000358700005011442004E
    https://websmp206.sap-ag.de/~sapidb/011000358700008968942004E.sim
    https://websmp206.sap-ag.de/~sapidb/011000358700001581372005E.sim
    /people/federico.babelis2/blog/2006/04/23/sdcc--service-data-control-center-configuration-guide-for-dummies
    Feel free to revert back.
    --Ragu

  • Grey (blank) EWA reports generated for Portal systems

    I am attempting to set up EWA reports for J2EE systems. At this stage despite all efforts I continue to get grey rated (blank) reports generated for our Portal systems.
    As far as I can tell all required components are installed correctly (Wily, SMD server, SMD agents etc).
    This problem seems to be restricted to our Portal systems as report data is being generated for our XI J2EE engines with the same SMD components installed.
    CGA collection jobs are running successfully against the managed Portal systems, and I have attempted to manually generate reports via transaction DSA in the Solution Manager system, using an uploaded service data xml file generated with the SMD/services utility. This also results in a blank report.
    Our systems comprise the following components:
    Wily v7.1
    SMD 13 on Solution Manager and managed systems
    Solution Manager 4.0 SP13: (ABAP):
    SAP_ABA     700     0013     SAPKA70013
    SAP_BASIS     700     0013     SAPKB70013
    ST-PI  2005_1_700     0006     SAPKITLQI6
    PI_BASIS 2005_1_700     0013     SAPKIPYJ7D
    SAP_BW     700     0015     SAPKW70015
    SAP_AP     700     0009     SAPKNA7009
    BBPCRM     500     0009     SAPKU50009
    CPRXRPM     400     0010     SAPK-40010INCPRXRPM
    ST     400     0013     SAPKITL423
    BI_CONT     703     0008     SAPKIBIIP8
    ST-A/PI     01K_CRM560     0000          -
    ST-ICO     150_700     0011     SAPK-1507BINSTPL
    ST-SER     700_2006_2     0004     SAPKITLOK4
    Solution Manager (J2EE):
    sap.com     SAP_JTECHF     7.00 SP13 (1000.7.00.13.0.20070812015644)
    sap.com     ISAGENT     7.00 SP13 (1000.7.00.14.0.20070927052333)
    sap.com     SAP-JEE     7.00 SP13 (1000.7.00.13.0.20070812015311)
    sap.com     SAP-JEECOR     7.00 SP13 (1000.7.00.13.0.20070907082334)
    sap.com     BASETABLES     7.00 SP13 (1000.7.00.13.0.20070812013638)
    sap.com     CORE-TOOLS     7.00 SP13 (1000.7.00.13.0.20070812014121)
    sap.com     JLOGVIEW     7.00 SP13 (1000.7.00.13.0.20070812001600)
    sap.com     JSPM     7.00 SP13 (1000.7.00.13.0.20070812001700)
    sap.com     CAF     7.00 SP13 (1000.7.00.13.0.20070809092315)
    sap.com     UMEADMIN     7.00 SP13 (1000.7.00.13.0.20070809093947)
    sap.com     ADSSAP     7.00 SP13 (1000.7.00.13.0.20070812011854)
    sap.com     BI_MMR     7.00 SP13 (1000.7.00.13.0.20070812013749)
    sap.com     CAF-UM     7.00 SP13 (1000.7.00.13.0.20070809092324)
    sap.com     KM-KW_JIKS     7.00 SP13 (1000.7.00.13.0.20070812014519)
    sap.com     SAP_JTECHS     7.00 SP13 (1000.7.00.13.0.20070812015951)
    sap.com     BI_UDI     7.00 SP13 (1000.7.00.13.0.20070811190400)
    sap.com     LM-SERVICE     7.00 SP13 (1000.7.00.13.0.20070812001200)
    sap.com     LM-TOOLS     7.00 SP13 (1000.7.00.13.0.20070906104634)
    Among many, many others, the following notes and documentation has been followed:
    976054 Availability of EWA for Non ABAP components
    1010428 End-to-End Diagnostics
    762969 - Grey rating for Earywatch Report
    EWA guide for NON-ABAB components
    SAP Solution Manager 4.0 End-to-End Root Cause Analysis Installation Guide
    762969 - Grey rating for Earywatch Report
    And of course all the Wily & SMD installation guides.
    Please let me know if there is any other information required. I'm posting this in the hopes that someone else has had this problem and has been able to resolve it. I have read though what seems like hundreds of threads on SMD setup problems, however not many that describe the problem I'm having exactly.
    Many thanks in advace.
    Tim

    Hi Stephan,
    You're on the right track! When I try manually generate reports for our XI systems via uploaded service data, I only get valid report data if I generate report with graphics - otherwise the report is blank.
    Alas with the Portal systems, I get no report data either way.
    The XML storage table does contain data (with XI & Portal systems) - so comms with the J2EE is working.
    Thanks for your help.
    Tim

  • How can generated EWA for SAP Portal system

    Hi Guru there,
    Usually generate EWA should maintenan RFC, We have SAP Portal systems ( prod PP1 and test PT1 and dev PD1), but they are not appeared at saplogon and no general SAP interface, only operationing system level we can start/stop SAP system and database and from the operating system browser can see the portal work normal ( 50000 port) or not.
    How can I generate EWA from solman?
    waiting for your kind reply!
    best regards,
    WEI

    Hi Wei,
    Do you already know SAP Note <a href="http://www.service.sap.com/sap/support/notes/976054">976054</a>?
    This SAP Note describes the setup of EWA for NON-ABAP Components.
    Please see the description and the attachments.
    Best regards,
    Ruediger

Maybe you are looking for