Activating the SAP EarlyWatch Alert on                  Solution Manager 7.0                 Best Practice for Solution Ma...
Applicability, Goals and RequirementsTo ensure that this Best Practice is the one you need, consider the following goals a...
System RequirementsSAP Solution Manager 7.0ST400 SP15ST-SER 2008_1 SP3Satellite system:This Best Practice is based on the ...
Best Practice ProcedurePreliminary TasksBefore executing this Best Practice, install the SAP Solution Manager and define t...
ProcedureActivating the EarlyWatch Alert in SAP Solution ManagerStep 1: RTCCTOOL – Service Preparation CheckProgram RTCCTO...
Figure 2: Report RTCCTOOL6
Step 2: Set up of the Service Data Control CenterThe Service Data Control Center (transaction SDCCN) is a service tool tha...
This action will trigger several individual processes:           Destination SDCC_OSS will be created, as a copy of SAPOSS...
Defining RFC Destinations for SAP Solution Manager SystemsThe SAP Solution Manager system must have RFC destinations that ...
SAP recommends that the SAP Solution Manager system itself is also monitored viaEarlyWatch Alert. The destinations SDCCN c...
Defining RFC Destinations for the Satellite SystemsEach satellite system must have an RFC destination that points to the S...
If the *BACK RFC connection is created with the ‘RFC Generation function’ in the systemlandscape maintenance (SMSY), the s...
3. Go to ‘change mode’.4. Choose a client in the Clients tab.5. Choose Generate RFC DestinationsFigure 96. Choose the type...
7. Choose the “user options”. In the above example, a new user and password will begenerated.8. You can enter the RFC dest...
Central activation of SDCCN via Transaction SMSYIt is possible to activate the SDCCN in the various satellite systems from...
4. In the next screen, we recommend to click ‘Yes’, to connect this system to the SAPSupport Portal. This will create dest...
Step 3: Define your Solution Landscape and allocate the SystemsTo be able to monitor a satellite system via SAP EarlyWatch...
Create a SolutionAccess the ‘Solution Overview’ in your SAP Solution Manager system (transactionsolution_manager).Click   ...
Creating a Logical Component:SMSY or ‘System landscape maintenance’, select ‘Logical Components’ -> Right click ->‘Create ...
The next screen shows the newly created logical component, ready to be filled with systems.Click in the cell with the rele...
Assign Logical Components to a SolutionAccess the Solution Directory to assign the new logical component to a solution:/ns...
In the Solution Directory, you can also check which systems are already included in anestablished solution.Figure 20The sy...
Continuous Automatic Monitoring:After the logical component has been added to a solution, the first SAP EarlyWatch Alertse...
Here, you can change the default settings for the session dates; the transfer to SAP and thearchiving of the EarlyWatch Al...
EarlyWatch Alert for Solutions also requires the following minimum prerequisites in the SAPSolution Manager:        ST-SER...
All the SAP EarlyWatch Alert sessions are assigned a rating. You can access a HTMLversion of the report for any session wi...
Automatic Emailing of ReportsIt is also possible to have the reports emailed automatically to nominated email addresses.Th...
Additional sessions:If you wish to check if any changes you made to a satellite have an effect on the EarlyWatchAlert repo...
Figure 28This will create an individual task ‘Session refresh’ which will be executed as soon as abackground process becom...
Figure 30If you select ‘Start service processing’ all EarlyWatch Alert sessions in this solution whichhave data available ...
Further InformationUseful NotesSAP Note 1257308      FAQ: Using EarlyWatch AlertSAP Note 1170668      The role of SAP Solu...
© Copyright 2008 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or f...
Upcoming SlideShare
Loading in...5
×

Activating the sap early watch alert on solution manager 7.0

11,461

Published on

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
11,461
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
369
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Activating the sap early watch alert on solution manager 7.0

  1. 1. Activating the SAP EarlyWatch Alert on Solution Manager 7.0 Best Practice for Solution Management Version Date: November 2008ContentsApplicability, Goals and Requirements........................................................................... 2Best Practice Procedure .................................................................................................... 4 Preliminary Tasks .........................................................................................................4 Procedure..........................................................................................................................5 Activating the EarlyWatch Alert in SAP Solution Manager........................................5 Step 1: RTCCTOOL – Service Preparation Check .....................................................5 Step 2: Set up of the Service Data Control Center ...................................................7 Step 3: Define your Solution Landscape and allocate the Systems.......................17 Step 4: Access the Results in the SAP Solution Manager .......................................25Further Information ........................................................................................................ 311
  2. 2. Applicability, Goals and RequirementsTo ensure that this Best Practice is the one you need, consider the following goals andrequirements.Goal of Using this Best PracticeSAP EarlyWatch Alert is a tool that regularly provides customers with information about theperformance of their SAP systems. It is fully integrated into the SAP Solution Manager, andis included in the maintenance agreement with SAP, at no extra cost. By running andmonitoring SAP EarlyWatch Alert you can increase system stability and performance for yourentire solution landscape. For this reason, SAP strongly recommends activating SAPEarlyWatch Alert for all productive systems.SAP EarlyWatch Alert gathers performance data using a data collecting mechanism that runsas a background job.This data is sent from the satellite systems to your central SAP Solution Manager system forprocessing and evaluation. The EarlyWatch Alerts for your satellite systems are also thebasis for further analysis, via EarlyWatch Alert for Solutions or via Service Level Reporting.If the overall rating of the SAP EarlyWatch Alert is red, the service results will automaticallybe sent to SAP Support. If all sessions are rated yellow or green, results will be sent to SAPSupport once every four weeks.Since the reports provide a history of a system’s performance, EarlyWatch Alert aids theanalysis of performance related problems which may occur.Staff and Skills RequirementsThis Best Practice can be applied by any experienced SAP system administrator.2
  3. 3. System RequirementsSAP Solution Manager 7.0ST400 SP15ST-SER 2008_1 SP3Satellite system:This Best Practice is based on the use of SDCCN, and so the systems in your systemlandscape need an SAP R/3 version of 4.0B or higher.Satellites on basis releases below 4.0B can only use SDCC. Regarding data collections insuch systems, please see SAP Note 216952.Data sources for EarlyWatch Alert:Depending on the managed system, EarlyWatch Alert can use data which is collected viaSDCCN or which is reported into the Solution Manager Diagnostics Tool. For example, theEarlyWatch Alert for a CRM system reads data stored in the Business Intelligence InfoCubesof the Solution Manager Diagnostics.This Best Practice describes the basic steps for systems containing an ABAP stack only,where the administration of the EarlyWatch Alert session data is executed by SDCCN in thesatellite system itself.EarlyWatch Alert can also be set up for Java components, such as Enterprise Portals.Prerequisites and setup for this are described separately in a user guide attached to SAPNote 976054.Duration and TimingDuration: Assuming you have successfully installed the SAP Solution Manager, and definedthe satellite systems, you need approximately half a day per satellite system for the initialimplementation of the steps recommended in the central service preparation in SAP Note91488. In addition, you require around 15 minutes per connected SAP system to set uptransaction SDCCN (Service Data Control Center).Timing: Implement the steps from this best practice document prior to the Going Live periodof the relevant satellite systems.3
  4. 4. Best Practice ProcedurePreliminary TasksBefore executing this Best Practice, install the SAP Solution Manager and define the satellitesystems. To do so, you can use the ‘Set-Up System Landscape’ wizard in the SAP SolutionManager Implementation Guide (IMG). You can find this under ‘Configuration’ – ‘BasicSettings’.It is crucial that the correct component is chosen for each maintained system, as this willdetermine which checks are executed in the EarlyWatch Alerts and other sessions. For moreinformation, refer to the SAP Service Marketplace at www.service.sap.com/solutionmanager.In each system, apply the steps from SAP Note 91488 (Central Note for Service Preparation).This will ensure that the connections to access the systems directly are set up, that theservice tools are up to date, and that the performance collectors and OS collectors run.The SAP Note also points to further notes with specific recommendations for certain SAPcomponents, database platforms and basis releases.SAP Note 1257308 “FAQ: Using EarlyWatch Alert” is the central note for additional stepsspecific for certain ST-SER releases and general procedures when using the EarlyWatchAlert.4
  5. 5. ProcedureActivating the EarlyWatch Alert in SAP Solution ManagerStep 1: RTCCTOOL – Service Preparation CheckProgram RTCCTOOL is delivered via addon ST-A/PI (see SAP Note 69455). It is a servicetool that establishes a connection to SAP and accesses an up to date list of required actionsand SAP Notes which are necessary to prepare your system and to successfully perform aservice session.Execute program RTCCTOOL in transaction SE38 to verify that relevant required actionsand SAP notes have been successfully implemented. If necessary, import any requiredupdates. All SAP notes displayed with yellow and red traffic lights must be reviewed andimplemented. Those displayed with green traffic lights are up-to-date and successfullyimplemented. (Figure 2.)Addon ST-A/PI also contains data collectors, as well as other tools which are needed toexecute service sessions. To enable smooth processing of session data it should be kept upto date in both SAP Solution Manager as well as all satellite systems.For more detailed Information, refer to SAP Note 69455.5
  6. 6. Figure 2: Report RTCCTOOL6
  7. 7. Step 2: Set up of the Service Data Control CenterThe Service Data Control Center (transaction SDCCN) is a service tool that provides youwith an overview of your SAP EarlyWatch Alert sessions and controls the data transferbetween your satellite SAP systems and the central SAP Solution Manager system. It alsocontrols the data transfer to SAP where applicable. SDCCN also controls the update of theservice definitions both on your SAP Solution Manager system and the satellite systems.The basic set up of SDCCN is described below, for further details on set up and use ofSDCCN, refer to SAP Note 763561.SDCCN must be set up on the central SAP Solution Manager system as well as all relevantsatellite systems.SDCCN is available with addon ST-PI 2005_1. For details see SAP Note 539977.Prerequisites: ST-PI 2005_1 must be installed. The newest available support packages for this addon should also be installed. This can be verified using RTCCTOOL, as described above. Destination SAPOSS to SAP must be functional. For more information see SAP Note 33135. The user executing the activation must have the necessary authorizations, that is, role SAP_SDCCN_ALL, containing profile S_SDCC_ADM_NSDCCN can be initialized manually/locally, or centrally from the SAP Solution Managersystem.Manual Initialization of SDCCNCall SDCCN. When you call SDCCN for the first time, all tabs will be empty.Initialize SDCCN locally via Utilities ->Activate:Figure 37
  8. 8. This action will trigger several individual processes: Destination SDCC_OSS will be created, as a copy of SAPOSS. AUTO_SESSION_MANAGER (the controlling job for the older tool SDCC) is descheduled where necessary. The customizing settings for the various task types are filled with the default values. A task of the type ‘Maintenance Task ‘ and one of the type ‘Service Preparation Check’ are created. The Task Processor (Job Name /BDL/TASK_PROCESSOR) is created. This is the controlling background job for SDCCN.You will see a log which documents if these steps were executed successfully:Figure 4SDCCN now contains 2 tasks:Figure 58
  9. 9. Defining RFC Destinations for SAP Solution Manager SystemsThe SAP Solution Manager system must have RFC destinations that point to SAP. TheseRFC destinations are used to connect to SAP for various reasons: Forwarding SAP EarlyWatch Alerts with RED ratings to SAP Updating Service Definitions from SAP Checking for “data model updates”, which include data used during EarlyWatch Alert processing, for example new HotnewsThe original RFC Destination is called SAPOSS and should normally already be configuredin your system. Otherwise, you can create it using transaction OSS1. If you have problemswith RFC destination SAPOSS, see SAP Note 33135.As mentioned above, during initialization, SDCCN creates its own copy of SAPOSS. Thiscopy is called SDCC_OSS.In SDCCN -> Goto -> Settings -> Task specific -> RFC destinations -> Settings -> RFCdestinations you can check which destinations SDCCN knows.Figure 6At the bottom of this screen you will also find this icon which can be used to test thelisted destinations.In this list, you can also see which SAP Solution Manager system is flagged as ‘master’system. Setting a ‘master’ system ensures that the satellite system takes the ‘servicedefinitions’ from the master SAP Solution Manager. It also ensures that during the datacollection important information about the satellite can be imported from the SAP SolutionManager system. If a satellite system is connected to several SAP Solution ManagerSystems, choosing one of these as "master" will not prevent communication with the otherSAP Solution Manager systems. SAP Note 1075827 (Master Flag in SDCCN) containsfurther details.9
  10. 10. SAP recommends that the SAP Solution Manager system itself is also monitored viaEarlyWatch Alert. The destinations SDCCN can use for this purpose are either called NONEor SM_<SID>CLNT<nr>_BACK. They must also be listed in the above screen, but must beadded after initialization. Destination NONE should already exist in SM59.SM_<SID>CLNT<nr>_BACK can be created as for any other satellite system, as per thedescription below.If an SAP Solution Manager system has its own *BACK destination flagged as ‘master’, theservice definitions will automatically be taken from SAP, via SDCC_OSS. However, thesetting enables the collection of information about components and so on, as described inSAP Note 1075827, and therefore is still valid.10
  11. 11. Defining RFC Destinations for the Satellite SystemsEach satellite system must have an RFC destination that points to the SAP Solution Managersystem. The RFC connection is used to transfer data collections to the SAP SolutionManager system, for any service session scheduled for delivery in that SAP SolutionManager system. This includes SAP EarlyWatch Alert sessions.The connection to the SAP Solution Manager system must be listed inSDCCN -> Goto -> Settings -> Task specific -> RFC destinations -> Settings ->RFC destinations. The relevant destination is called SM_<SID of SAP SolutionManager>CLNT<nr>_BACKIt is generated in the SAP Solution Manager system and, after generation, is automaticallyentered in SDCCN in the satellite system.Set up RFC Destinations from SAP Solution Manager to the Satellite SystemsManual generation of the *BACK destinationThe*BACK destination is needed in the SDCCN of the satellite system, to be able toexchange session data with the SAP Solution Manager system.It is created from within transaction SMSY in the SAP Solution Manager system.The following prerequisites are needed: A working dialog connection such as *TRUSTED or LOGIN. Once the *BACK destination is created, these can be deleted again. A communication user for the BACK RFC connection in the SAP Solution Manager system with the following authorization profiles and roles: S_CUS_CMP (SAP_S_CUS_CMP) Read data S_CMSREG (SAP_S_CSMREG) -> Central system repository data S_BDLSM_READ (SAP_S_BDLSM_READ) -> SDCCN data SAP_SV_FDB_NOTIF_BC_ADMIN -> Service Desk messages SAP_SUPPDESK_CREATE -> Service Desk messages11
  12. 12. If the *BACK RFC connection is created with the ‘RFC Generation function’ in the systemlandscape maintenance (SMSY), the system can be set to automatically create anauthorized user:1. Call transaction SMSY. Use icon ‘other object’ to choose the system to which you want togenerate the RFC connection.Figure 72. Double-click the link for the ABAP-based main instance of the system for which you wantto generate RFC connectionsFigure 812
  13. 13. 3. Go to ‘change mode’.4. Choose a client in the Clients tab.5. Choose Generate RFC DestinationsFigure 96. Choose the type of RFC connection you wish to generateFigure 1013
  14. 14. 7. Choose the “user options”. In the above example, a new user and password will begenerated.8. You can enter the RFC destination of a server group for load distribution in the ‘Attributes’group box.You can find more information in the section ‘RFC destinations’ of the ‘Security Guide’; thiscan be found at service.sap.com/instguides -> SAP Components -> SAP Solution Manager<current release>14
  15. 15. Central activation of SDCCN via Transaction SMSYIt is possible to activate the SDCCN in the various satellite systems from within your SAPSolution Manager system. Prerequisites: The user executing the activation has the necessary authorizations in the satellite system, that is, role SAP_SDCCN_ALL, containing profile S_SDCC_ADM_N The license key must be installed in the satellite system The current version of the ST-PI Add-on (ST-PI 2005_1_<Release> or higher) is installed in the satellite system The satellite systems are defined in ‚System landscape maintenance’ ( SMSY) The prerequisite READ_RFC connection has been generated RFC destination NONE for the SAP Solution Manager system itself is available1. Choose Environment -> Solution Manager Operations -> Administration SDCCN.Figure 11This brings you to a dialog box in which the connected systems and their status are shown.Systems which can be activated are flagged with the symbol Activate. Active systems areflagged with the symbol Execute in the Call SDCCN column.2. To add a system in the overview, choose Insert. All systems for which you wish to activateSDCCN must be displayed in this overview. In the example below, TT5 has just been added.Figure 123. To activate the Service Data Control Center, click on the Activate symbol:15
  16. 16. 4. In the next screen, we recommend to click ‘Yes’, to connect this system to the SAPSupport Portal. This will create destination SDCC_OSSFigure 135. If SDCCN was successfully activated, you will get a green rating in column ‘SDCCNStatus’Figure 146. To call the Service Data Control Center, click Execute.For further information, choose the Information symbol. The dialog box Help is displayed.7. At this point, you can also decide to make the SAP Solution Manager system the ‘master’system for the satellite system. This ensures that the satellite system takes the ‘servicedefinitions from the master SAP Solution Manager. It also ensures that during the datacollection, important information about the satellite can be imported from the SAP SolutionManager system. SAP Note 1075827 (Master Flag in SDCCN) contains further details.16
  17. 17. Step 3: Define your Solution Landscape and allocate the SystemsTo be able to monitor a satellite system via SAP EarlyWatch Alert, the system must beintegrated into a logical component, which in turn must be integrated into a solution.The following steps must be executed: Create a new solution Create a logical component Add the logical component to the solution Mark systems in logical component which are to be monitored in this solutionTo assign a system to a logical component and to create a new one, you can also use thewizard ‘Assignment to a logical component’ which can be started from displaying the systemin SMSY. Also, the previously mentioned ‘Set-Up System Landscape’ wizard will allow youto start it.For a detailed description on how to set up your solution landscape, you can refer to severalsources:1. SAP Solution Manager documentation at service.sap.com/solutionmanager -> MediaLibrary.2. I Tutor simulation at service.sap.com/rkt-solman -> SAP Solution Manager 7.0 ->Technical roles -> Technology Consultant & System Administrator -> System and SolutionMaintenance (SMSY) -> System Landscape (SMSY) - Creating Systems3. Online documentation of your SAP Solution Manager.A brief overview is given below.17
  18. 18. Create a SolutionAccess the ‘Solution Overview’ in your SAP Solution Manager system (transactionsolution_manager).Click . Enter the name and language of the new solution; then click ‘Continue’.Figure 15In the next screen, you will get confirmation that the new solution has been created and hasbeen assigned an ID number.Figure 1618
  19. 19. Creating a Logical Component:SMSY or ‘System landscape maintenance’, select ‘Logical Components’ -> Right click ->‘Create New Logical Components’Figure 17Fill in the name of the new logical component, choosing a name in the customers’ namespace.Select the correct product, and ensure fields Product Version and Main Instance are filledcorrectly; then confirm.Figure 1819
  20. 20. The next screen shows the newly created logical component, ready to be filled with systems.Click in the cell with the relevant role, and from the F4 help, choose the relevant combinationof system and client.Figure 19Save your selections once all relevant cells are filled.20
  21. 21. Assign Logical Components to a SolutionAccess the Solution Directory to assign the new logical component to a solution:/nsolution_manager -> Access solution -> Solution Landscape -> Solution LandscapeMaintenanceSelect which combination of system and client should be monitored in this solution: right clickon the relevant cell and choose ‘Put in Solution’.21
  22. 22. In the Solution Directory, you can also check which systems are already included in anestablished solution.Figure 20The systems in the green cells are included in the solution.22
  23. 23. Continuous Automatic Monitoring:After the logical component has been added to a solution, the first SAP EarlyWatch Alertsession is automatically created for each system marked for monitoring, with the current dateas session date. All subsequent SAP EarlyWatch Alert sessions will, by default, bescheduled once a week, on Monday. The sessions each have their own unique sessionnumber, which you can see when you hover the mouse over a session in the list ofEarlyWatch Alerts for the solution. For monitoring to work, this session number must beshown in the SDCCN of the corresponding satellite system.The ‘Maintenance Task’ in SDCCN in each satellite system executes a ‘session refresh’ to alldestinations in the list in SDCCN -> Goto -> Settings -> Task specific -> RFC destinations ->Settings -> RFC destinations.Figure 21If the connections work, the sessions are brought into SDCCN in the satellite systems, underthe session numbers described above.The log of the ‘Maintenance Task’ documents this activity as a task of the type ‘Sessionrefresh’.Each session in SDCCN for which data is collected and transferred produces a log also.When data has arrived in a session in SAP Solution Manager, you will see this iconin the overview of EarlyWatch Alert sessions, which indicates that the session is ready forprocessing. The next background job SM:EXEC SERVICES will automatically process thedata, that is, execute and rate the EarlyWatch Alert session.If you wish to change the default scheduling of the EarlyWatch Alerts you have to change thesettings in the SAP Solution Manager system.Via transaction solution_manager -> <Solution Name>-> Operations Setup -> SolutionMonitoring -> EarlyWatch Alert -> Link ‘Setup EarlyWatch Alert’ you can get to theEarlyWatch Alert Administration area (transaction SOLMAN_EWA_ADMIN). This is based onBSP (Business Server Page) technology from ST400 SP15.23
  24. 24. Here, you can change the default settings for the session dates; the transfer to SAP and thearchiving of the EarlyWatch Alerts (see the Online Help for more information).Here, you can also decide if a system should be included in the EarlyWatch Alert forSolutions.Figure 22EarlyWatch Alert for SolutionsThe EarlyWatch Alert for Solutions (EWAfS) enables its users to gain an overview of thecurrent status of entire solution landscapes within one consolidated report. This overviewincludes historical developments, aggregated solution KPIs and detailed statistics aboutdedicated systems of the solution. The solution-based report consolidates alerts generatedby the regular EarlyWatch Alert monitoring services and classifies them, to identify potentialareas for improvement, such as performance or stability.EarlyWatch Alert for Solutions is particularly useful for the monitoring of systems whichparticipate in the monitoring of your documented Business Processes. The report toolaccesses the Solution Manager Solution Repository where the Business Processes aredocumented, and so provides a link between standard EWAs and individual core businessprocesses with regard to performance evaluations.As EarlyWatch Alert for Solutions is composed from information contained in the datacollections of the individual EarlyWatch Alerts, it must be scheduled after the last individualEarlyWatch Alert for the contributing systems has been processed.If the selection of systems differs from the proposed default selection, you should ensure thatall systems relevant for the business process are taken into account in the report.This is based on the assumption that the solution landscape was previously created to reflectthe systems participating in the core business processes, and that these core businessprocesses were maintained in the Solution Manager Solution Repository.EarlyWatch Alert for Solutions can then provide a specific evaluation of the performance ofthese core processes. Otherwise, only the most frequently used transactions are evaluated.The monitoring service EarlyWatch Alert for Solutions depends in some parts on the SolutionManager Diagnostics (SMD) in conjunction with the Solution Manager BI. The reportingcapabilities of the EarlyWatch Alert for Solutions are restricted to the products available inthe SMD. For details on supported products see SAP Note 1040343. All other products andproduct releases will not have report output.24
  25. 25. EarlyWatch Alert for Solutions also requires the following minimum prerequisites in the SAPSolution Manager: ST-SER 700_2008_1 ST Release 400, Support Package SP15Further information about EarlyWatch Alert for Solutions can be found in SAP Note 1040343.More information is also in the RKT Learning Maps for SAP Solution Manager:Service.sap.com/rkt-solman -> SAP Solution Manager 7.0 -> Technical roles -> TechnologyConsultant & System Administrator -> -> EarlyWatch Alert (EWA), Service Level (SL) andSolution Reporting -> SAP EarlyWatch Alert for Solutions – Introduction.Step 4: Access the Results in the SAP Solution ManagerTo view the reports for both SAP EarlyWatch Alert and EarlyWatch Alert for Solutions in yourSAP Solution Manager system, access the relevant solution, then choose ‘Operations ->Solution Monitoring -> EarlyWatch AlertFigure 23All of the SAP EarlyWatch Alert sessions which were generated for all systems in thissolution are displayed.25
  26. 26. All the SAP EarlyWatch Alert sessions are assigned a rating. You can access a HTMLversion of the report for any session with a rating by clicking on the link next to the rating icon.The HTML reports are not stored. You also have the possibility of generating a permanentWord report, by clicking on the ‘Word’ icon.To access the actual checks of an individual EWA session, click on this icon .If a session with a scheduled date of more than one day in the past has not been rated, it willbe assigned an ‘overdue’ icon. . Clicking on the link for this session will bring you to ascreen from which you can access SDCCN in the satellite system, to check if there are anyproblems with the settings there.Figure 2426
  27. 27. Automatic Emailing of ReportsIt is also possible to have the reports emailed automatically to nominated email addresses.This can be set up either for the entire solution or for individual systems.Entire Solution 1. Call the SAP Solution Manager (transaction SOLUTION_MANAGER). 2. Open the solution. 3. Choose Edit - Automatic E-mail transmission. A dialog box is displayed. 4. Choose Create E-mail. A second dialog box is displayed. 5. Select a ‘session name’ and ‘report type’ from the Input Help, and specify an e-mail address. 6. Confirm. 7. The session type and the e-mail address are displayed in the first dialog box. Click on to leave.Figure 25Individual systems 1. Access the maintenance view of table DSWP_SYS_EMAIL 2. Choose New Entries 3. Enter the following values: Object ID (use F4 help to select solution) SAP system ID (use F4 help) E-Mail address 4. Save your entries.As soon as the next session is rated, a report will be sent to the specified e-mail address.27
  28. 28. Additional sessions:If you wish to check if any changes you made to a satellite have an effect on the EarlyWatchAlert report for that satellite system, you do not need to wait for next week’s regularEarlyWatch Alert session to be executed. Instead, you can create an additional session:Figure 26Inthe next screen, you can select for which satellite system in this solution you wishto create the session, and which type of session you wish to create.Figure 27After you have selected a date for your additional session, it will appear in the overview ofsessions, together with the regular periodical sessions. At the bottom of the screen, you willsee a message stating the session number of the additional session:If you wish to execute this session immediately, access SDCCN in the satellite system.From the ‘To do’ tab choose Task -> Create -> Refresh sessions. Choose the relevant*BACK destination, and choose to execute this task ‘Now’.28
  29. 29. Figure 28This will create an individual task ‘Session refresh’ which will be executed as soon as abackground process becomes available.The session refresh will bring the new additional session into the SDCCN overview of tasks‘To do’.You can then mark this session, and via ‘Edit – Start now’ force an immediate start of thedata collection and transfer.Figure 29You can check the session log for the progress of the task. Once the data transfer to the*BACK destination has been completed, you can go back to the SAP Solution Managersystem to force an immediate processing of the data.Refresh the overview of EarlyWatch Alert sessions. The additional session should now showthe icon indicating that data is available: .Click on the link for this session to get to the next screen:29
  30. 30. Figure 30If you select ‘Start service processing’ all EarlyWatch Alert sessions in this solution whichhave data available will be processed. At the end of this job the additional session youcreated will also have a rating. You can then access the report as described above.30
  31. 31. Further InformationUseful NotesSAP Note 1257308 FAQ: Using EarlyWatch AlertSAP Note 1170668 The role of SAP Solution Manager in Remote Service DeliverySAP Note 91488 SAP Support Services: Central preparation noteSAP Note 1172939 Technical prerequisites for remote service delivery in SSMSAP Note 976054 Availability of EWA for Non ABAP componentsSAP Note 569116 Release strategy for Solution Manager Service Tools (ST-SER)SAP Note 930747 Service Delivery on SAP Solution Manager (Recommended Notes)SAP Note 69455 Service tools for Applications ST-A/PI (ST14 & RTCCTOOL)SAP Note 539977 Release strategy for Add-On ST-PISAP Note 763561 Service Data Control Center (SDCCN) - FAQSAP Note 1075827 Master flag in SDCCNSAP Note 216952 Service Data Control Center (SDCC) - FAQSAP Note 762696 Grey rating for EarlyWatch AlertSAP Note 33135 Guidelines for OSS1SAP Note 1040343 EarlyWatch Alert (EWA) for SolutionsUseful components:SV-SMG-SYS: Problems in defining a system in transaction SMSYSV-SMG-OP: Problems which may occur during the creation of the EarlyWatch Alerts in the SAP Solution Manager systemSV-SMG-SDD: Problems with SDCCNSV-SMG-SER-EWA: Questions regarding the content of the EarlyWatch Alert reportsBC-UPG-ADDON: Questions which occur during the implementation of addonsXX-SER-NET: Questions regarding destination SAPOSSOnce the EarlyWatch Alert is set up and running there may be problems which may occurlater on in the life cycle of a satellite system. The EarlyWatch Alert report section ‘ServicePreparation’ gives detailed information about which problem occurred, and which correctivesteps can be taken.Background Information and ReferencesYou can find more information about the SAP EarlyWatch Alert Service in the SAP ServiceMarketplace under the quick link EWA (http://www.service.sap.com/ewa).More information about the SAP Solution Manager in the SAP Service Marketplace under thequick link solutionmanager (http://www.service.sap.com/solutionmanager).31
  32. 32. © Copyright 2008 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components ofother software vendors.Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, andOS/400® are registered trademarks of IBM Corporation.ORACLE® is a registered trademark of ORACLE Corporation. TMINFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of Informix SoftwareIncorporated.UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of SunMicrosystems, Inc., used under license for technology invented and implemented by Netscape.SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch,BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other products mentionedare trademarks or registered trademarks of their respective companies.Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials areprovided “as is” without a warranty of any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, orconsequential damages that may result from the use of these materials. SAP does not warrant the accuracy orcompleteness of the information, text, graphics, links or other items contained within these materials. SAP has nocontrol over the information that you may access through the use of hot links contained in these materials anddoes not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third partyWeb pages.32

×