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

Similar Messages

MAI for managed systems residing in separate network

Hello!
We are considering to implement the new Monitoring and Alerting Infrastructure (MAI) with Diagnostics Agents for our SAP systems.
The most of our SAP managed systems reside in separate network (differ from SOLMAN network).
In order to retrieve CCMS-data from these systems we must use RFC connections within SAP router string.
Has someone already successfully set up MAI for managed systems that reside in separate network?
Of great interest are the information about
1) Integration of these systems into DBACOCKPIT of SOLMAN
2) Installation of Diagnostic Agent on remote host
Many thanks for your information.

Hello SAP-SDN,
as for your initial question:
Has someone already successfully set up MAI for managed systems that reside in separate network?
Of great interest are the information about
1) Integration of these systems into DBACOCKPIT of SOLMAN
2) Installation of Diagnostic Agent on remote host
1.- actually on process, but still don0t found any problem to do on remote network trought sapruter.
2.- actually working and running, the unique limitation is the connection between willy hostagent and wily EM.
as for your next question:
1a) database related data in your Alerting (e.g. tablespaces)
1b) database related data in your IT Performance Reporting/Interactive Reporting (e.g. growth of database)
1c) DBACOCKPIT connection for the remote SAP system
1a) for ewa ABAP you can get that information from a remote netwaork managed system without any problem
1b) for ewa ABAP you can get that information from a remote netwaork managed system without any problem
1c) still on process, but i think that can be possible as well is possible to connect the remote SMD diagnostic agent trought one or more saprouters.

Quick help - Is SAPHOSTAGENT Mandatory for managing system (solman) ?

Hi All,
Quick question, Is SAPHOSTAGENT Mandatory for managing system (solman) ?
No data in infocube OSMD_PE2D (JAVA MEMORY USAGE) and i'm trying to narrow down the problem. Therefore, i want to know is SAPHOSTAGENT Mandatory for managing system (solman) ?
Thanks,
Nicholas Chang

Hi All,
I've figured out that DAA and SAPHOSTAGNET is needed for SOLMAN EHP1 SPS > 20 as the diagram depicted in AgentInstallation.pdf, from Note 1365123 - Installation of Diagnostics Agents.
and i've resolved the problem where data is populated in OSMD_PE2D and JAVA MEMORY USAGE data and etc is appearing in WA and EWA.
Step performed:
1) before rerun diagnostic system setup, ensure RFC for SELF_DEST for BW source system is working fine and importantly, all field should be empty in technical settings, logon & security and etc. Perform RFC and authorization check.
2) rerun diagnostic system setup and ensure all result returned green, and check CCMSBI_SETUP_E2E log. Ensure it completed successfully. ( you need to adjust WEBADMIN & SOLMANDIAG RFC by putting in the gateway host and port to avoid intermittent RFC error, also enlarge RFC resource in table E2E resources)
3) go to TX rstco_admin and ensure status is activation successful.
4) follow sapnote 1259109 and upload the latest xml according to your solman version.
5) Install object accordingly by following note 1342231 & 1110013 (the note specify the bugs happen in SPs18, whilst my solman version is EHP1 SPs27 and i was reluctant to apply at the first place. But upon checking, most of the objects mentioning in the note that required installed are not installed!)
6) Rerun managed system setup
7) Check infocube OSMD_PE2D after 1 hour or 1 day?? unsure as i checked after one day.
Cheers,
Thanks,
Nicholas Chang.

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

Solution Manager - EarlyWatch Alert shows red flag for managed system.

Hi Guys,
I tried to fix EarlyWatch alert report for Managed systems of QA and Dev which showed red flag on SolMan in DSWP. While trying to generate BACK RFC Destination to SolMan for QA and Dev, it messed up the EarlyWatch alert reports of Prod which was successfully working upto this point. And now the red flag appears for Prod system on SolMan in DSWP instead of two bottle sign.
As for why Dev and QA did not work, I found out it was NONE internal RFC popped whenever I tried to choose the RFC to connect to SolMan while Prod which was working fine before always showed BACK rfc. That's why I tried to fix BACK rfc for Dev and QA.
Please help me to fix these EWA problems.
Thanks,
Modena

Hi Modena,
Please see the link below for this specific issue:
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728

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

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

Understanding and using Logical Components for Managed System configuration

Experts.....
I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System. Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.
General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!
- Our SAP landscape is not very complex
1. only ERP and EP (Dev/Test/Prod).
2. We are utilizing HR Self Service (XSS).
3. The ERP ABAP systems are on Netweaver 7.01.
4. EhP4 has been installed, however we only activated the HCM business functions. Therefore SAP_HR is on 604 whereas SAP_APPL is on 600. I think this might be driving some of the confusion in SMSY
For the DEV ABAP system I am trying to configure:
1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"
2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant
3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default. I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"
4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"
5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections
From what I can tell, I think this is correct:
1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them
2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???
3. For the Solutions, my plan is to create
a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system
b. Production ERP with the prod erp/ep systems only
Thanks for any advice/guidance to help me avoid future problems!!
Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.
For example with ChaRM you could have 2 logical components.
ZCHARM_DEV development (100) -> QA (200) -> prod (300)
ZCHARM_SEC security (900) -> QA (200) -> prod(300)
One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.
Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

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

Early Morning Page (daily) for managed systems

Hello!
We are using the newest SAP Solution Manager 7.1 and would like to automatically generate
a Early Morning Page (daily report) for all the managed systems.
Of great interest is the following content in this Early Morning page:
- introduction/comment/own text
- growth of database/file systems and history of previous week
- Dialog response time and history of previous week
- amount of short dumps
Does SAP Solution Manager7.1 provide this service or there are some other tools that can fulfill our requirements?

Tailored SLR. This sounds good.
To my knowledge you can generate SLR monthly or weekly.
What I need:
an automatic short daily report with the status symbol and all the important KPI values like DB growth, response time, etc.
Thank you!

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

Not find EWA Session in the managed system

Hi all,
I am configuring SOL 7.1 for EWA.
I have configured SDCCN both on Solution manager 7.1 and Managed System.
In the solution manager, i can find EWA session for managed system.
The question is : When i run "Refresh sessions" on the T-code: SDCCN of Managed system, it can not retrive EWA session where exist on the Solution manager.
How do i do? Can someone help, please.
BR
Wu

after reconfiguration in new client,
Follow Note 727998 - Complete Replacement of Service Definitions for SDCC/SDCCN
step 1 :
in the solution manager:
1.1 run report BDL_DELETE_ALL_TABLES in SE38
1.2 SDCCN-> Goto -> Settings -> Task specific -> RFC destinations.
       Ensure that connection 'NONE' and SDCC_OSS is maintained, and that the 'master'
1.3 Execute a "service definition refresh" in SDCCN
1.4 Delete any task 'Maintenance Package' in the 'To do' tab in SDCCN.
1.5 Create a new periodic task 'Maintenance Package' in SDCCN
1.6 Call function module /BDL/_GENERATE_LOGFUNCINCLUDES in SE37
        Assign the value 'ALL' to the import parameter 'OPTION' (keep the default values for all other parameters) and execute the module.
1.7 Execute "refresh session" in SDCCN
step 2:
in the managed system:
1.1 run report BDL_DELETE_ALL_TABLES in SE38
1.2 SDCCN-> Goto -> Settings -> Task specific -> RFC destinations.
       Ensure that only connection SM_<SOL>_BACK' (delete SDCC_OSS )is maintained, and that the 'master'
1.3 Execute a "service definition refresh" in SDCCN
1.4 Delete any task 'Maintenance Package' in the 'To do' tab in SDCCN.
1.5 Create a new periodic task 'Maintenance Package' in SDCCN
1.6 Call function module /BDL/_GENERATE_LOGFUNCINCLUDES in SE37
        Assign the value 'ALL' to the import parameter 'OPTION' (keep the default values for all other parameters) and execute the module.
1.7 Execute "refresh session" in SDCCN
Best Regards,
Wu

Metrics of EWA for managed system are in gray

Similar Messages

Maybe you are looking for