Configure Early Watch on 4.6C

Hi Expert,
We need to configure Early watch on 4.6C, please let us know the steps?
Thanks,
Frank.

Hi Frank,
If you have solution manager you can configure this. If you have Solution Manager 3.2 or 4.0 you need to set up RFC connections between these two. Once its done if its 3.2 use transaction code DSA and provide information which are needed. Then execute that you will be able to see the early watch report. In case of 4.0 you need to use transaction code SOLUTION_MANAGER / DSWP. There we can generate the Early watch report. To configure the solution monitoring
http://help.sap.com/saphelp_sm40/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
follow this link.
Regards
Vivek

Similar Messages

  • Document for configuring Early watch alerts And issue tracking system

    Hello Experts,
    Iam on SAP Solution Manager 4.0 and need step wise step procedure document for configuring Early watch alerts and Issue tracking system in solman 4.0 . I hv checked Help site and other standard config docs by SAP but getting confused and things are not working ,so help shall be appreciated.
    My Email id is [email protected] .
    Requested to revert at earliest as iam in urgent need of it .Points guaranteed.
    Thanks and Regards,
    Somya

    Hi Somya,
    setting up EWA is explained in Application help of SAP Solution Manager.
    It would be helpful to know, what you have already done and what is causing problems for you.
    Prerequisite to process EWA is to configure all steps described in the Basic Settings of SAP Solution Manager Configuration guide (tx SPRO).
    The configuration of Issue Tracking is also described in the IMG (Basically, it's required to activate a BC Set).
    Path in IMG: Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> Basic BC-Sets for Configuration -> Activate Issue Tracking BC Set
    Access the configuration guide:
    - run transaction SPRO
    - choose SAP Reference IMG
    - expand tree SAP Solution Manager -> Configuration -> Basic Settings
    - follow the steps under
    "Wizard-based Initial Configuration of Basic Settings", if your SolMan system has not been yet configured or
    "Standard Configuration of Basic Settings", if you have done already some configuration.
    Best regards,
    Ruediger Stoecker

  • How to configure Early watch report in SOLMAN

    I recently got chance to work on SOLMAN. Anyone could just point me in a right direction from where I can start to configure systems for early watch alert in SOLMAN.
    Thanks

    Hi Bill,
       Check the below link
    http://help.sap.com/saphelp_sm40/helpdata/EN/a4/a0cd16e4bcb3418efdaf4a07f4cdf8/frameset.htm
    do check the below use ful URL:
    http://help.sap.com/saphelp_sm40/helpdata/EN/b7/07e4cf1a364a0482e29122c329b7d3/frameset.htm
    For more information, see the SAP Service Marketplace at the following Internet address:
    service.sap.com/earlywatch
    Regards,
    S.Manu.

  • Configure Early Watch Reports in SolMan

    Hi Gurus,
        Can you please help me out in the steps of configuring SolMan for Early Watch Reports.
    Thanks in Advance,
    Sachin Kumar.

    Hello Sachin,
    Please implement/apply latest ST-PI and ST-API patches in your Dev system.
    after applying the patches please execute RTCCTOOL program in Se38 t code.
    This program helps in service preperation so that data from your satellite system(Dev) can be sent to
    solution manager system.
    once you are done with that we can configure Dev system in solution manager system and activate SDCCN.
    SDCCN will help in collecting data from dev to Solman.
    Please apply ST-PI and ST-API from SAINT transaction if it has never applied into your system.
    You can add dev qa and prd system in Solution manager system
    Use SMSY t code and add the systems(use add system with assistant option).
    this will help you to create the RFC's also which are responsible for cummunicating from Solution manager to Satellite and vice versa.
    after that make sure you execute the abap program RTCCTOOL and implement the missing notes thru that only which the report suggests.
    let me know if you face any issues for the above steps ...
    Cheers,Amber S

  • Early Watch Alert Configuration

    Hi,
    Can anyone tell me how to configure Early Watch Alert in Solution Manager 4.0.
    When i try to create a periodic request session data, It is created for early watch alert and not for EarlyWatch Alert for Solution Manager.
    And when i try to call from solution manager4 solution_manager->solution->Early Watch Alert then i get the following error.
    The data for this session is overdue. Data has not yet been transferred from the associated satellite system.
    Go to the Service Data Control Center (transaction SDCCN) in the satellite system and check why the data has not been sent.
    Typical sources of errors are:
    The RFC connection for the SAP Solution Manager system is not working.
    The 'Task Processor' background job, which collects the session data, has been changed.
    Problems arose while data was being collected (see the detail log for the task that collects the session data).
    A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data.
    Please help me.

    First of all, i'm no expert on this, but...
    1] Go to tcode: SDCCN
    2] You see 2 tasks to do. Maintenance Package and Service preparation check.
    3] Select Maintenance Package, in the menu Edit -> start now
    4] A new task is created with a session number
    5] Select the new task, in the menu Edit -> start now (this will take a few minutes).
    6] Now go to dswp, select your solution and see EarlyWatch Alert reports.
    7] You probably have to click on create report or something like that.
    I think this problem will solve itself, because it's a job which hasn't been started yet.
    Because the job hasn't started, the session does not yet exist, which will result in an error overdue.
    Some more information: http://help.sap.com//saphelp_sm40/helpdata/EN/6e/6135418ac8d92be10000000a1550b0/content.htm

  • Early Watch Report - Archive EWA

    Hello,
      I have configured Early Watch Report in my Solution Manager 4.0 on Windows Server 2003 4 weeks back.
    EWA report is comng perfectly  but in my Solution for each server I am able to see only 2 (Latest one and  Next Schedued) EWA report at a time.Not able to see previous week report.
    How can I see my older EWA reports ??
    Thanks,
    Chandresh Pranami

    hi.
    maybe you have configured that older reports are deleted after two weeks...
    there is a possibility to customize - i think its under transaction solution_manager.
    normally, they never go away.
    regards,
    martin

  • Query Regarding Early Watch Report

    Hi All,
    I have certain queries regarding the Early Watch Report.
    Our platform in Oracle 10g and OS is HP-UX.Please sombody help me with the following.
    1.What is Early Watch report and why we use it?
    2.How to configure Early watch report from Solution Manager for DEV and QUA and PRO server?
    3.If we dont configure will SAP take it from the system by logging in to client 066(correct me if I am wrong).
    I have read SAP notes 20722,917558,12103,371023 but cant really make out how to configure it for our servers via Solution Manager.
    PS:Helpful suggestions will be obliged and rewarded.
    Regards,
    Ashutosh

    Hi Ashutosh,
    Please check below answers for your queries:
    1.What is Early Watch report and why we use it?
    The SAP EarlyWatch Alert is a diagnosis service, for the solution monitoring of SAP and non-SAP systems in the SAP Solution ManagerThis process identifies potential problems early, avoids bottlenecks and monitors the performance of your systems. SAP EarlyWatch Alert monitors your most important business processes and systems.
    2.How to configure Early watch report from Solution Manager for DEV and QUA and PRO server?
    Prerequisites to configure the Early Watch Report:
    You have:
    ·        set up RFC connections between your satellite systems and the SAP Solution Manager system, and an RFC connection between the SAP Solution Manager and the SAP Service Marketplace.
    ·        checked the availability of the required tools for the SAP service session (ST-A, ST-PI add-on), with the report RTCCTOOL.
    ·        assigned the Solution Monitoring roles to the users.
    ·        set up the Automatic Session Manager (ASM) in the Service Data Control Center (transaction: SDCCN) for all SAP satellite systems and the central SAP Solution Manager of your solution (SAP note 91488).
    ·        set up your systems in a solution landscape in the SAP Solution Manager.
    Configuration steps:
    1.      You configure the SAP EarlyWatch Alert scheduling in the SAP Solution Manager.
    You have:
    ¡        scheduled the service sessions for your solution, in the SAP Solution Manager Solution Directory
    Procedure:
           1.      Choose the transaction SOLUTION_MANAGER.
           2.      Choose the Solution Landscape tab in the Operations Setup area.
           3.      Choose the Solution Settings link.
    You go to the Solution Directory.
    Alternatively, you can also select a solution from the Overview of active solutions and go to the Solution Directory.
           4.      Select your solution.
           5.      You can also enter contact person data in the Contact Person tab.
          Proceed as follows:
                                                      i.       Choose Add Contact Person.
                                                    ii.       Enter the required data.
                                                   iii.       Save your entries.
    §         The contact data appears in the Solution Monitoring sessions, e.g. in Set-Up Business Process Monitoringsapurl_link_0001_0004_0005.
           6.      Specify the settings for your solution, in the Solution Settings tab:
            Ex:  Day of SAP EarlyWatch Alert data download
    At the end save your entries.
    3.If we dont configure will SAP take it from the system by logging in to client 066?
    Yes, SAP uses this client when running the Early Watch Check.
    Hope it clears your doubt.
    Thanks
    Kishore

  • Early watch Alert in Solution Manager 7.1

    Hi All
    Are there any sap reference guides on configuring Early watch on Solution Manager 7.1?
    I tried looking this up in help.sap with little luck.
    We have installed Early watch 7.1 and have run solman_setup till the Basic Configuration phase (with some errors though)
    Is the managed system configuration a must for Early watch? Any guides or runbooks / notes from sap would be of great help.
    regards
    Ravi

    Dear Ravi Ponnuswami,
    There are so many documents available in SAP Market Place. and also available SAP Notes regarding this EWA installation.
    Try the below links
    http://help.sap.com/saphelp_sm32/helpdata/en/5a/b27f17edb04a6882c59f6619a267b9/content.htm
    http://help.sap.com/saphelp_smehp1/helpdata/en/2f/de3316e1fc425080f83c718bec41de/frameset.htm
    http://www.sap.com/korea/services/pdf/2_EWA_Overview_Info%20Day.pdf
    http://www.service.sap.com/~sapidb/011000358700001873212008E
    Regards
    Vasanth S

  • Early watch report - Status as it is in Solution manager

    Dear All,
    I have configure early watch report in solution manager.
    1. I have created new service for our production server.
    2. click on newly created service
    3. Press button "call Service Data Control Center"
    4  System ask for prodction password.
    5  now SDCCN's screen of production server open.
    6. Create a new task "Refresh sessions" with selecting "Now" option.
    7. Start a New task is created.
    8. Task is complited successfuly but sessio data not transmited to solution manager.
    I have also tried with "Start service processing. But still service is in "wait for session data". This status remains same as newly created service.
    Request you to please suggest solution
    Thanks in advance,
    Nirav

    Hello,
    When you press call Service Data Control Center, is it that there is a red flag for the EWA and when you click it you get that button? This means the EWA is scheduled in Solman, but on the managed system there is an issue with the SDCCN EWA task or the *_BACK RFC.
    First, the Maintenance Package task is what should be schedyuled daily. It will 1 Refresh the service defintions regularly and aslo perform a refresh sessions task. You should not be scheduling the refresh session task ( unless you want to send to SAP or a second Solution Manager sytem).
    The refresh session task will create an EWA task, and you did not mention this task was created from the refresh session task.
    If the EWA task is not created on the satellite once the refresh session is run, then there was no session. This would indicate an error in SMSY defintions, such as the  installation number there does not maych the actual installation number, as a for instance.
    SDCCN task logs have to be looked at as they may have errors inside, but the task has a green check.
    Also visit http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728
    Regards,
    Paul

  • How to Set Up Early Watch Alert

    Hi,
      Could anyone tell me how to configure Early watch alrery along with procedure.
    Regards,
    Saravanan

    Hi saravanan,
    In Solution_manager tcode, first select the solution for which to set the EWA (if you have multiple solutions).
    On the left side pane, you will find OPERATION SETUP to set EWA, Service level reporting,  BPM, System Monitoring. Select Setup Early Watch Alert.
    Furnish the details and Save.
    your EWA is configured now.

  • RFC configuration for system monitoring / Early Watch reports

    Hello Basis Gurus:
    Please help me out.....
    The early watch reports in the solution manager of my system are failing consistently to execute.This is happening for all the 3 systems DEV,QAS,PRD.when i click on individual earlywatch reports it takes me to a screen which says  "data for this report is overdue.....go to your satellite system SDCCN to see why the data was not sent...."
    It says ...check the following things.....
    "The RFC connection for the SAP Solution Manager system is not working.
    The 'Task Processor' background job, which collects the session data, has been changed.
    Problems arose while data was being collected (see the detail log for the task that collects the session data).
    A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data."
    I can see the task processor job , and the periodic Maintenance package scheduled everyday and completed sucessfully.So is it the RFC which is causing the problem.
    Im SM59 of the solman, i can see system generated RFCs for the PRD,DEV,QAS and SND  (...3 for each of these systems...).
    say for PRD, these are the 3 RFCs.
    1.)SM_PRDCLNT<client#>_READ.
    2.)SM_PRDCLNT<client#>_TMW.
    3.)SM_PRDCLNT<client#>_TRUSTED.
    I am not sure which RFCs among the 3 for any given system does the solman use to communicate to the satellite systems.
    *The user id section in the Logon Data of any of these RFCs is blank.and the password says "is initial"...*is this correct.Does the user id have to be a communication type of user...
    PLeaase advise as to what could be going wrong..
    Regards.

    Hi,
    The system uses ABAP Connection (Connection Type 3) to connect to different Systems to execute Functional Calls.
    Now in your case, there are 3 different connections meaning your Basis Team has used 3 connections for different connection activities. This is totally a business dependent scenario.
    Now each time you create a RFC Connection, the system will need the following information to remotely call another system, they are:
    Host Details of Target System
    Logon Details to remotely login
    For RFC Connections the User Type has to be Communications User. But there are companies which use Dialog User Types as well to remotely login for some cases. When the User ID is created for an RFC User and a Password is assigned to it, this Password is considered as the Initial Password by the system. This Password is taken as the Initial Password in the RFC Connection as well.
    There can be cases where the system is Trusted and there is no need of a password, but an Username is mandatory in all cases. Remember if you set the system as Trusted, the password option gets deactivated and the connection wont work, if the system does not have the Trusted status.
    But in any case you must assign the Username alongwith the Client and Language Details in the RFC Connection for it to work.
    Hope this helps.
    /Manoj

  • Early watch alert Dump:UNCAUGHT_EXCEPTION+ CX_DSVAS_API_CONTEXT_INSTANCE

    Hello All,
    I am facing issue while generating the early watch alert :
    In DSWP its showing ,DATA is available ;SAP earlywatch alert Session number :<>
    After processing button :  Start service processing
    Job schduling and getting failed Job Log:
    Job log overview for job:    SM:EXEC SERVICES 000000106120000 / 10520300
    Date       Time     Message text                                                                                Message class Message no. Message type
    02-06-2012 10:52:03 Job started                                                                                00           516          S
    02-06-2012 10:52:03 Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant &0000000000558, user ID BASISUSER)           00           550          S
    02-06-2012 10:52:03 MemSize Begin = 1368192   Bytes                                                                         DMD          000          I
    02-06-2012 10:52:05 Solution <000000106120000> "SID..." is being edited (Operations)                                       DSWP          438          S
    02-06-2012 10:52:05 <000000106120000> "SID..."(Operations)                                                                  DMD          000          I
    02-06-2012 10:52:05  ( EW_ALERT ) Session 2000000001331 for 02-13-2012 created (QDV)                                       DSWP          506          S
    02-06-2012 10:52:05 Difference "Create_Periodic_Services" = 278528                                                          DMD          000          I
    02-06-2012 10:52:05 Trying to perform session EC2000000001313                                                              DSWP          492          S
    02-06-2012 10:52:08 MODEL_KEY: SID <Installation Number> HANDLE: 6  MODEL_MODE: E  MODEL_VERSNR 00001 MODEL_CLASS: EWA Data Model      DMD          000          I
    02-06-2012 10:52:43 Internal session terminated with a runtime error (see ST22)                                             00           671          A
    02-06-2012 10:52:43 Job cancelled                                                                                00           518          A
    St22: Dump Log:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_DSVAS_API_CONTEXT_INSTANCE
    Date and Time          02-06-2012 10:52:43
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_DSVAS_API_CONTEXT_INSTANCE' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program 'SAPLDSVAS_PROC' has to be
         terminated.
    Please post your valubale suuggestions and how to proceed further.
    Thanks
    Nekkalapu

    HI Arjun,
    Earlier (upto jan15th ) its working fine no issues generating earlywatch alerts .
    After 15th onwards i am facing this issue i have not done any chnages in configuration part.
    As per your suggestion I have checked the below points:
    1)transaction AGS_UPDATE is up to date ?
    Answer:AGS_UPDATE is updated (ALL availeble updates are downloaded) and its showing green color 3 options .
    2)able to connect to your satellite system via Trusted RFC or able to create sessions?
    Answer: Yes its generating sessions probelm while running dswp t code genarating sessions only.
    3)RTCCTOOL showing all green ?
    Answer:
    Five are showing in red and two are showing green
    Red:
    Addon upgrade ST-A/PI 01N_700SOL
    ST-A/PI Addon Supportpackage SP01
    Proc. after addon impl.
    Switch on digital content verification
    ST-PI Support Packages
    Green:
    Addon ST-PI 2008_1_700
    Collectors and TCOLL
    Kindly please suggest how to proceed further.
    Thanks
    Nekkalapu

  • Same system being shown multiple time in Solution for Early Watch Report

    Hi Gurus ,
    I have some satellite system configured to Solution Manager . Today I can see the same system entry multiple time in the
    Operations: Solution Monitoring -> Early Watch Alert.
    eg .,
    I have a system whose SID is ABC , i can see the ABC entry for todays date (i.e., 4 FEB 08) nearly 4 time .And this systems are not rescheduled for the next EWR (i.e scheduled for 11 FEB 08- since we have kept a period of 7 days )
    Please suggest
    Anthony

    Hi Anthony,
    There was an error, that EWA sessions for one systems were scheduled multiple times per week.
    Please check [SAP Note 1083108 - Duplicate EarlyWatch Alerts|http://service.sap.com/sap/support/notes/1083108]
    Search for SAP Notes with key words: EWA, multiple, duplicate.
    Application area: SV-SMG-OP
    What's the software configuration of your SolMan?
    Best regards,
    Ruediger

  • Early watch alert task not created in SDCCN in satellite system

    Hello Everyone,
    I am trying to configure EWA in solution manger 7.0 ehp1. I have added the system in SMSY, created RFC SM_SIDCLNTXXX_READ and SM_SIDCLNTXXX_TRUSTED in solution manger and also created RFC SM_SIDCLNTXXX_TRUSTED and SM_SIDCLNTXXX_BACK in satellite system sucessfully.
    The Early watch Alert in TA DSWP is showing me a red flag. The job  /BDL/TASK_PROCESSOR in satellite system is being sucessfully finished.
    The problem I am facing is I cannot find task Early watch Alert in SDCCN in my satellite system and can not create other RFC such as SAPOSS and SDCC_OSS
    Could anyone please suggest how should i go about it?
    Component version of my satellite system is
    ST-A/PI - 01M_SCM570
    ST-PI - 2005_1_700  00003

    Hello Sohrab
    1) The SDCCN task logs will be on the Done tab - You can also check the logs in SLG1 at the time, there could be more information there.
    Typically the refresh definitions will have nothing, except when there are updates, so it is not unusual to see no updates here each time the task runs. If there are service sessions the maintains package should pick them up with refresh service task.
    Is the SM_<SID>CLNT<nnn>_BACK RFC set as the master in SDCCN?
    One test you can make is create a Refresh session task on the satellite. This is the task that the Maint. Package should run.
    It will just be easier for testing. If the refresh session task does not create any EWA tasks for the service sessions outstanding, then there is a configuration issue.
    If it works, then the Maintenance task is failing before it can shcedule the  refresh session task.
    I realize I haven't offered a solution, but a way of finding out where it is failing. Once we isolate where it is failing, we reduce the possibilities of what it could be, and we should be left with the solution.
    So forget the Maintenace Package for Now. Lets see if you can pull the service sessions with a Refresh Session Task.
    You know in the SDCCN task logs errors in the logs are prefaced by what looks like a yellow lightening bolt.
    So if you see these in any of the logs, you are encountering an error, and you should copy it here.
    Hope this helps to move you forward.
    Regards,
    Paul

  • Early Watch Session overdue - Error in Data Transfer

    Hi folks,
    in my solution, the Early Watch Reports from the productive system are labeled overdue (with a red flag). It says that there is no data transmitted from SDCC.
    When calling SDCC manually, it says that I don't have the necessary authorisation (one of the three S_SDCC_* profiles) to call it in the satellite system. I, though, HAVE all of the profiles.
    RFC also works fine.
    When calling SDCC in the productive system itself, it says: "EWA_SAPOSCOL_B : no matching interface found" " > function module not found" "EWA_SAPOSCOL_B : funcname /SDF/EWA_SAPOSCOL_B , module 001203", which seems to be the real problem. I don't have a clue what that means respective where to look to get rid of it.
    Can anybody solve this? Points will be rewarded as a matter of course. Thanx in advance!
    Dirk

    The red flag means the session is overdue.
    Could be for a number of reason - firstly are the trusts correct set? As it appears (from the text you've posted) you cant call SDCCN on the remote system from SOLMAN.
    The other reasons could be you dont have the correct configuration setup on the monitored node.
    SDCCN Check the RFC settings for Setting-Task specific.
    You should have a link pointing back to SOLMAN and this should have the tick for Master set.
    Check you have the correct sessions scheduled and they are set against the RFC for solman, not OSS and they are a periodic job.
    Sessions needed are
    Refresh Sessions
    Request session data.
    You can manually run the session by right clicking and say run now.
    If you are still struggling post additional details.
    RTCCTOOL is used to check patch levels are upto date, not the configuration or links. You can still run EWA without being on the latest patch.

Maybe you are looking for