Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
gorbenkoteh
Active Participant

Quote.




"Everything you do as a system administrator should serve a single

purpose: to secure and protect system integrity..."

 - Sebastian Schreckenbach "SAP Administration - Practical Guide"




This quote about a series of blog-posts about business continuity and High Availability of SAP Systems. Monitoring is a very important part of this process.


Another post from this series (The list is being updated.):


 

Logical Prerequisites.



You are an SAP Basis Administrator and you want to monitor your SAP Landscape

and you want setup EWA (Early Watch Alert) for a managed system for this purpose.


Technical prerequisites.


Solution Manager 7.2

SAP HANA as Database

The managed system must be registered in the LMDB (Registration in LMDB - this is one of the steps during system installation via SWPM)


Resolution.



Step 0. Managed Systems Configuration in Solution Manager



Transaction - SOLMAN_WORKCENTER

Configuration - Managed Systems Configuration

Check system - Configure System - Full Configuration Incl. Service Delivery /EWA






Step 1. Assign Product



Choose Set Diagnostics-Relevance to calculate the product instances that are relevant for diagnostics. Following the link "Edit Assignment" (Link to LMDB)






Set Diagnostic-Relevance for product instances






Step 2. Check Prerequisites



Create SAP HANA Database User in Tenant database

e.g.SOLMAN_MONITORING

with rolesap.hana.admin.roles::Monitoring


More in Notes 1892593 and 1592925


Links/Notes:

1892593 - Preparing Support Services for SAP HANA Scenarios


1592925 - SAP HANA Studio service connection






Step 3. Maintain RFCs



Step 3.1. Superuser


Provide superuser for user creations/role update

superuser - existing user in a managed system






Step 3.2. Create Communication RFCs between Solution Manager and managed system.


Check create/update RFC-destinations for all offers from the list and Execute









Step 4. Assign Diagnostics Agent



More in my satellite blog-post


Step 5. Enter the System Parameter



Provide information for Introsctope/CTS+ (if exists, relevant for non-ABAP systems)






DB Parameters

Provide credentials to the user in the tenant database from Step 2.





Step 6. Maintain Users


Creating or Updating Users in managed system

SAPSUPPORT (Dialog)

SMDAGENT_<SID OF SOLMAN>(System)




Step 7. Finalize Configuration



Maintain Automatic and Manual Activities.


Automatic:






Manual:






Step 8. Check Configuration



Execute option "Check Configuration"


Step 9. Complete



All steps must be green/yellow and not red


Step 10.  EWA Managment



Transaction - SOLMAN_WORKCENTER

Configuration - Application Configuration - EarlyWatch Alert Managment


Step 11. Define scope



Define managed system


Step 12. Activate EWA


Typical configuration - EWA builds on Monday morning







Step 13. Check Software Component Level



The software components ST/PI, ST-A/PI must have the latest available patch level.

Typical errors:







Step 14. Display Diagnosis



SDCCN status of ABAP technical systems.

All messages must be in green status






Step 15. Maintain Recipients


Assign Recipients and define Report format (doc/pdf/html)

Friendly Advice - use Mailing Group instead of a specific e-mail address


Step 16. Configure EWA Content


For example, you can include analyzing data from Data Volume Management (DVM) to EWA


Links/Notes:

2035999 - FAQ: Automated DVM self-service documents / New DVM EWA chapter setup and creation


2036442 - EarlyWatch Alert (EWA) - Data Volume Management (DVM)


2582367 - DVM Chapter in EWA is Missing Data



Step 17. Preparation in managed ABAP-system



Transaction - STC01 - Task manager for technical configuration

Task List -> Early Watch Alert to SAP Configuration






Transaction - SDCCN - Service Data Control Center

Goto -> Settings ->Task Specific -> RFC Destination Settings


Add a new RFC destination







RFC Destination for SAP EWA Report must be set as Master/active









Step 18. Ad-hoc EWA



You can create an Ad-hoc EWA report for ABAP and non-ABAP system.

More in Note  #2357073









Links:

2357073 - How to Create an Ad Hoc EarlyWatch Alert SAP - Solution Manager 7.2







Step 19. SAP EarlyWatch Alert Workspace (Cloud EWA)





SAP EarlyWatch Alert Workspace is the central landing page that shows the most important results from the latest service reports across all systems.


Prerequisites for this step:




  1. The EWA service is activated in SAP Solution Manager on-premise and the Send to SAP flag is set in the app Configuration: Application Operations - EarlyWatch Alert Management



It's here:








N.B.

Only systems with IT Admin Role QAS and Production fit to Send to SAP role







You can set up the correct IT Admin Role in the LMDB

It's here:

Transaction - LMDB - Landscape Management and Logical Components





or the data is sent directly from the monitored system, as described in SAP Note 207223.





Links/Notes:

EarlyWatch Alert Workspace


2282944 - EarlyWatch Alert: Solution Manager 7.2 how to setup/configure EWA reports or add email recipients


1684537 - EarlyWatch Alert not sent to SAP: troubleshooting guide


207223 - SAP EarlyWatch Alert Processed at SAP


SAP EarlyWatch Alert Workspace – gain an overview on your system landscape health


Now available: SAP EarlyWatch Alert Workspace for all databases and Dashboard with BW KPIs


The New 2 Billion Record Limit in the SAP EarlyWatch Alert Workspace


1907891 - How to change the server name of Diagnostics Agent - Solution Manager






Troubleshooting


Problem:


SAP EarlyWatch Alert Sessions with error "Service data is overdue"






Resolution:


For ABAP systems:

1769513 - EWA not generated - session data is overdue (red flag status)


For JAVA systems:

2736980 - EarlyWatch Alert (EWA) is not getting generated for non-ABAP systems


Also

Check transaction SDCCN in Solution Manager






Check "Step 5. Enter the System Parameter" and fix the problem with credentials






Problem:

No status update; no managed system admin user for the system during EWA Setup







Resolution:

Implement Note 2682560 - "No status update; no managed system admin user for system, client" in Maintain Users





Problem:

SAP Service Delivery is active, a BACK RFC connection is needed





Resolution:

1763337 - Enabled for AGS Service Delivery in Managed System Config.



Problem:

Provide a superuser role upload with error

But user exists with correct roles in the correct client.

Resolution:

Clear browser cache.


Problem:

A diagnostic agent installed but nothing in "Find Agent" section





Resolution

Check the Server section and compare Server name with an output of command hostname on OS level

This names must be the same







Problem:

SAP CIM model (1.6.56) is outdated, update it (see SAP Note 669669)

Resolution:

669669 - Update of SAP System Component Repository






Conclusion.



SAP BASIS Routine task with examples from real life was provided.


4 Comments
Labels in this area