Professional Documents
Culture Documents
Early Watch
Early Watch
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 .......................................25 Further Information ........................................................................................................ 31
System Requirements
SAP Solution Manager 7.0 ST400 SP15 ST-SER 2008_1 SP3 Satellite system: This Best Practice is based on the use of SDCCN, and so the systems in your system landscape 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 in such systems, please see SAP Note 216952. Data sources for EarlyWatch Alert: Depending on the managed system, EarlyWatch Alert can use data which is collected via SDCCN or which is reported into the Solution Manager Diagnostics Tool. For example, the EarlyWatch Alert for a CRM system reads data stored in the Business Intelligence InfoCubes of 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 the satellite 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 SAP Note 976054.
Procedure
Activating the EarlyWatch Alert in SAP Solution Manager
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_N SDCCN can be initialized manually/locally, or centrally from the SAP Solution Manager system.
Figure 3
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 4
Figure 5
Figure 6
At the bottom of this screen you will also find this icon listed 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 service definitions from the master SAP Solution Manager. It also ensures that during the data collection important information about the satellite can be imported from the SAP Solution Manager system. If a satellite system is connected to several SAP Solution Manager Systems, choosing one of these as "master" will not prevent communication with the other SAP Solution Manager systems. SAP Note 1075827 (Master Flag in SDCCN) contains further details.
SAP recommends that the SAP Solution Manager system itself is also monitored via EarlyWatch Alert. The destinations SDCCN can use for this purpose are either called NONE or SM_<SID>CLNT<nr>_BACK. They must also be listed in the above screen, but must be added 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 the description below. If an SAP Solution Manager system has its own *BACK destination flagged as master, the service definitions will automatically be taken from SAP, via SDCC_OSS. However, the setting enables the collection of information about components and so on, as described in SAP Note 1075827, and therefore is still valid.
10
Set up RFC Destinations from SAP Solution Manager to the Satellite Systems
11
If the *BACK RFC connection is created with the RFC Generation function in the system landscape maintenance (SMSY), the system can be set to automatically create an authorized user: 1. Call transaction SMSY. Use icon other object to choose the system to which you want to generate the RFC connection.
Figure 7
2. Double-click the link for the ABAP-based main instance of the system for which you want to generate RFC connections
Figure 8
12
3. Go to change mode. 4. Choose a client in the Clients tab. 5. Choose Generate RFC Destinations
Figure 9
Figure 10
13
7. Choose the user options. In the above example, a new user and password will be generated. 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; this can be found at service.sap.com/instguides -> SAP Components -> SAP Solution Manager <current release>
14
Figure 11
This 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 are flagged 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 activate SDCCN must be displayed in this overview. In the example below, TT5 has just been added.
Figure 12
3. To activate the Service Data Control Center, click on the Activate symbol:
15
4. In the next screen, we recommend to click Yes, to connect this system to the SAP Support Portal. This will create destination SDCC_OSS
Figure 13
5. If SDCCN was successfully activated, you will get a green rating in column SDCCN Status
Figure 14
6. 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 service definitions from the master SAP Solution Manager. It also ensures that during the data collection, important information about the satellite can be imported from the SAP Solution Manager system. SAP Note 1075827 (Master Flag in SDCCN) contains further details.
16
17
Create a Solution
Access the Solution Overview in your SAP Solution Manager system (transaction solution_manager). Click . Enter the name and language of the new solution; then click Continue.
Figure 15
In the next screen, you will get confirmation that the new solution has been created and has been assigned an ID number.
Figure 16
18
Figure 17
Fill in the name of the new logical component, choosing a name in the customers name space. Select the correct product, and ensure fields Product Version and Main Instance are filled correctly; then confirm.
Figure 18
19
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 combination of system and client.
Figure 19
20
Select which combination of system and client should be monitored in this solution: right click on the relevant cell and choose Put in Solution.
21
In the Solution Directory, you can also check which systems are already included in an established solution.
Figure 20
22
The Maintenance Task in SDCCN in each satellite system executes a session refresh to all destinations in the list in SDCCN -> Goto -> Settings -> Task specific -> RFC destinations -> Settings -> RFC destinations.
Figure 21
If the connections work, the sessions are brought into SDCCN in the satellite systems, under the session numbers described above. The log of the Maintenance Task documents this activity as a task of the type Session refresh. 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 icon in the overview of EarlyWatch Alert sessions, which indicates that the session is ready for processing. The next background job SM:EXEC SERVICES will automatically process the data, 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 the settings in the SAP Solution Manager system. Via transaction solution_manager -> <Solution Name>-> Operations Setup -> Solution Monitoring -> EarlyWatch Alert -> Link Setup EarlyWatch Alert you can get to the EarlyWatch Alert Administration area (transaction SOLMAN_EWA_ADMIN). This is based on BSP (Business Server Page) technology from ST400 SP15.
23
Here, you can change the default settings for the session dates; the transfer to SAP and the archiving 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 for Solutions.
Figure 22
24
EarlyWatch Alert for Solutions also requires the following minimum prerequisites in the SAP Solution Manager: ST-SER 700_2008_1 ST Release 400, Support Package SP15 Further 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 -> Technology Consultant & System Administrator -> -> EarlyWatch Alert (EWA), Service Level (SL) and Solution Reporting -> SAP EarlyWatch Alert for Solutions Introduction.
Figure 23
All of the SAP EarlyWatch Alert sessions which were generated for all systems in this solution are displayed.
25
All the SAP EarlyWatch Alert sessions are assigned a rating. You can access a HTML version 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 permanent Word 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 will be assigned an overdue icon. . Clicking on the link for this session will bring you to a screen from which you can access SDCCN in the satellite system, to check if there are any problems with the settings there.
Figure 24
26
Figure 25
Individual 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
Additional sessions:
If you wish to check if any changes you made to a satellite have an effect on the EarlyWatch Alert report for that satellite system, you do not need to wait for next weeks regular EarlyWatch Alert session to be executed. Instead, you can create an additional session:
Figure 26In
the next screen, you can select for which satellite system in this solution you wish to create the session, and which type of session you wish to create.
Figure 27
After you have selected a date for your additional session, it will appear in the overview of sessions, together with the regular periodical sessions. At the bottom of the screen, you will see 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
Figure 28
This will create an individual task Session refresh which will be executed as soon as a background 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 the data collection and transfer.
Figure 29
You 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 Manager system to force an immediate processing of the data. Refresh the overview of EarlyWatch Alert sessions. The additional session should now show the icon indicating that data is available: Click on the link for this session to get to the next screen: .
29
Figure 30
If you select Start service processing all EarlyWatch Alert sessions in this solution which have data available will be processed. At the end of this job the additional session you created will also have a rating. You can then access the report as described above.
30
Further Information
Useful Notes
SAP Note 1257308 SAP Note 1170668 SAP Note 91488 SAP Note 1172939 SAP Note 976054 SAP Note 569116 SAP Note 930747 SAP Note 69455 SAP Note 539977 SAP Note 763561 SAP Note 1075827 SAP Note 216952 SAP Note 762696 SAP Note 33135 SAP Note 1040343 FAQ: Using EarlyWatch Alert The role of SAP Solution Manager in Remote Service Delivery SAP Support Services: Central preparation note Technical prerequisites for remote service delivery in SSM Availability of EWA for Non ABAP components Release strategy for Solution Manager Service Tools (ST-SER) Service Delivery on SAP Solution Manager (Recommended Notes) Service tools for Applications ST-A/PI (ST14 & RTCCTOOL) Release strategy for Add-On ST-PI Service Data Control Center (SDCCN) - FAQ Master flag in SDCCN Service Data Control Center (SDCC) - FAQ Grey rating for EarlyWatch Alert Guidelines for OSS1 EarlyWatch Alert (EWA) for Solutions
Useful components:
SV-SMG-SYS: SV-SMG-OP: Problems in defining a system in transaction SMSY Problems which may occur during the creation of the EarlyWatch Alerts in the SAP Solution Manager system Problems with SDCCN
SV-SMG-SDD:
SV-SMG-SER-EWA: Questions regarding the content of the EarlyWatch Alert reports BC-UPG-ADDON: XX-SER-NET: Questions which occur during the implementation of addons Questions regarding destination SAPOSS
Once the EarlyWatch Alert is set up and running there may be problems which may occur later on in the life cycle of a satellite system. The EarlyWatch Alert report section Service Preparation gives detailed information about which problem occurred, and which corrective steps can be taken.
31
32