Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
SAP Solution Manager 7.2 SP5
Part 4 of 4
System Monitoring
By OZSoft Consulting for ITConductor.com
Solution Manager 7.2 SP 5: System Monitoring
• The Setup (Part 1), Preparation & Configuration (Part 2), and
Managed Syste...
Solution Manager 7.2 SP 5: System Monitoring
• Run transaction SOLMAN_SETUP: Application Operations -> System Monitoring
•...
System Monitoring: Configure Infrastructure
• In this step, you configure the monitoring infrastructure.
• In this step, y...
System Monitoring: Configure Infrastructure
• In this step, you perform manual activities to configure the System and Appl...
System Monitoring: Default Settings
• In this step you can enable or disable the following functions for the System & Appl...
System Monitoring: Reporting-Settings
• In this step, the health check results of the BI-based reporting are displayed, so...
System Monitoring: Housekeeping
• In the step "Housekeeping" you make settings for the BI and the Monitoring and Alerting ...
System Monitoring: Workmode Settings
• In the step "Workmode Settings" you can change the global settings for the handling...
System Monitoring: Update Content
• In the last step of the infrastructure configuration you update the monitoring content...
System Monitoring: Standard Users
• In the step "Standard Users" you can create users in SAP Solution Manager that have th...
System Monitoring: Template Maintenance
• The content of System Monitoring is delivered in SAP templates which contain met...
System Monitoring: Define Scope
• In this step you select the managed object you want to configure for system monitoring. ...
System Monitoring: Setup Monitoring
• In this step monitoring templates will be assigned to the managed systems in scope.
...
System Monitoring: Complete
• The system monitoring setup is completed for the managed systems in scope.
• In this step th...
System Monitoring: Demo
• Check System Monitoring in SOLMAN_WORKCENTER
• You can also access Solution Manager content from...
System Monitoring: Demo
• Click on a System’s:
• Click on a System’s Alert count:
ozsoft-consulting.com ITConductor.com 17
System Monitoring: Demo
• Click on a System’s Alert count:
• Alert Details: Shows Metric Rating
ozsoft-consulting.com ITCo...
System Monitoring: Demo
• Metric Monitoring:
ozsoft-consulting.com ITConductor.com 19
Solman 7.2 System Monitoring: Summary
• Solution Manager 7.2 System Monitoring is a project, not a simple
task, which invo...
Solman 7.2 System Monitoring: Comparison
• In this example we set up Solman to monitor an S/4HANA
environment, total effor...
SAP Monitoring as a Service
• Every customer’s Solution Manager should be monitored as a
business critical environment for...
• Any Questions?
• Contact Info: info@itconductor.com
• Follow us: https://www.linkedin.com/company/it-conductor
Let
itcon...
Upcoming SlideShare
Loading in …5
×

Solution Manager 7.2 SAP Monitoring - Part 4 - System Monitoring

SAP Solution Manager 7.2 SAP Monitoring
Part 4 of 4 (System Monitoring)
Visit https://www.itconductor.com/blog/solution-manager-7.2-sap-monitoring-part-4-system-monitoring the complete eBook download

  • Login to see the comments

Solution Manager 7.2 SAP Monitoring - Part 4 - System Monitoring

  1. 1. SAP Solution Manager 7.2 SP5 Part 4 of 4 System Monitoring By OZSoft Consulting for ITConductor.com
  2. 2. Solution Manager 7.2 SP 5: System Monitoring • The Setup (Part 1), Preparation & Configuration (Part 2), and Managed Systems Configuration (Part 3) must have been completed successfully. If not, visit these other sections: • Solution Manager 7.2 SAP Monitoring - Part 1 (Setup) • Solution Manager 7.2 SAP Monitoring - Part 2 (Configuration) • Solution Manager 7.2 SAP Monitoring - Part 3 (Managed System Config) • In this Part 4: We will assign the application scenario and final steps for System Monitoring ozsoft-consulting.com ITConductor.com 2
  3. 3. Solution Manager 7.2 SP 5: System Monitoring • Run transaction SOLMAN_SETUP: Application Operations -> System Monitoring • This step is the entry point and overview page of the system monitoring configuration. System Monitoring includes technical systems, DBMS and hosts. ozsoft-consulting.com ITConductor.com 3
  4. 4. System Monitoring: Configure Infrastructure • In this step, you configure the monitoring infrastructure. • In this step, you use the automatic activities to check the prerequisites for the configuration of the System & Application Monitoring infrastructure. ozsoft-consulting.com ITConductor.com 4
  5. 5. System Monitoring: Configure Infrastructure • In this step, you perform manual activities to configure the System and Application Monitoring infrastructure: 1. The activities are displayed in the Manual Activities table. To display the Documentation of the activities, choose Display in the relevant row. 2. To perform the activity, choose the link in the column Navigation. 3. When you have performed the activity, change the Execution Status to Performed and choose Save. ozsoft-consulting.com ITConductor.com 5
  6. 6. System Monitoring: Default Settings • In this step you can enable or disable the following functions for the System & Application Monitoring: • Automatic Incident Creation - Choose Active for this dropdown list box on the Summary tab page, if you want incidents (support messages) to be automatically created (in Solution Manager Support Desk) from Alerts. If you choose Inactive, you can still create incidents manually from the alert inbox. • Automatic Notification - Choose Active for this dropdown list box on the Summary tab page, if you want alerts to automatically send notifications as e-mails or SMS. If you choose Inactive, you can still create notifications from the alert inbox. • Third-Party Components - Choose Active for this dropdown list box on the Summary tab page, if you have integrated one or more 3rd party tools to work with System & Application Monitoring. ozsoft-consulting.com ITConductor.com 6
  7. 7. System Monitoring: Reporting-Settings • In this step, the health check results of the BI-based reporting are displayed, so you can see whether the preconditions for successfully activating the BI-based reporting are met. If no health check is finished with an error, activate the BI content if you want to use BI-based reporting. • If health check is finished with an error, see the SAP note 2483407 - "Cannot read the RFC destination from the BW to the Solution Manager", error in Solution Manager 7.2 ozsoft-consulting.com ITConductor.com 7
  8. 8. System Monitoring: Housekeeping • In the step "Housekeeping" you make settings for the BI and the Monitoring and Alerting Infrastructure related housekeeping. It is recommended to leave the default settings und just save in this step. Please be sure you really know what you are doing when you change settings here, as these settings have an influence on the data growth in Solution Manager and hence changes here can lead to huge data growth if not considered carefully. • The upper tray contains the settings for the BW housekeeping. Per default minute interval data are kept for 19 days and then aggregated to hourly data which are then kept for 31 days and so on. The lower tray contains the housekeeping settings for the monitoring and alerting infrastructure. The alert store housekeeping settings determine when an open alert is confirmed automatically and when a confirmed alert is deleted. ozsoft-consulting.com ITConductor.com 8
  9. 9. System Monitoring: Workmode Settings • In the step "Workmode Settings" you can change the global settings for the handling of the alerting if work modes are configured for a system. The monitoring can be paused depending on the work mode a system is in and you can even have different thresholds depending on the work mode. This way you avoid getting alerts if you system is in a planned downtime. Work modes can be scheduled in the Technical Administration Workcenter under Work Mode Management. • As the alert consumer settings for notifications and incidents etc. also the work mode settings have the three hierarchy levels "Global", "Template" and "Metric/Alert". Global settings are overwritten by template settings and template settings are overwritten by metric/alert specific settings. ozsoft-consulting.com ITConductor.com 9
  10. 10. System Monitoring: Update Content • In the last step of the infrastructure configuration you update the monitoring content. The monitoring content contains all templates that are delivered by SAP for System Monitoring and all other scenarios like PI Monitoring, as well as data collector templates. • The content needs to be updated after every support package implementation. It is recommended to implement the latest version. If your monitoring is running fine, there is no need to update the content independent of the support package implementation. If you have problems with a metric and the troubleshooting reveals that it has an error in the definition of the content, a content update might help. • If new content is found then you will see it in this step indicated by a "Yes" for New Content Available and also the "Update" button will be activated. ozsoft-consulting.com ITConductor.com 10
  11. 11. System Monitoring: Standard Users • In the step "Standard Users" you can create users in SAP Solution Manager that have the exact right amount of authorizations to perform System Monitoring. The step is optional, you don't need to create the users to run System Monitoring. However it might be useful to take the information provided here as template to build an authorization concept for your Solution Manager. • You can create two different levels of users. The L2 (Level 2) user is the more powerful user. Please check the documentation in the column "Documentation" for the users for more information. To create all users with the default names select the "Create all Users" button. Or create the users one by one. ozsoft-consulting.com ITConductor.com 11
  12. 12. System Monitoring: Template Maintenance • The content of System Monitoring is delivered in SAP templates which contain metrics, alerts and events used to monitor managed objects. SAP delivers templates for a various kind of managed objects. The templates are groups by managed object type, which can be a host, a database, a technical system or a technical instance. • Templates are dependent on the product version of the managed object. • A template can only be assigned if the correct product version is selected during the managed system setup of the managed system. • The delivered SAP templates already have meaningful settings; if you do not want to change these, you can skip this step. If you want to make changes, we recommend that you make these changes in your own template. You can create a template of this type by selecting the template on which you want to base your template, and choosing the Create Custom Template button. ozsoft-consulting.com ITConductor.com 12
  13. 13. System Monitoring: Define Scope • In this step you select the managed object you want to configure for system monitoring. Without selecting a managed object you cannot proceed to the next setup steps. You can either select technical systems, technical scenarios, hosts, or databases. • Before you can configure system monitoring for a managed object you have to finish the Managed System Configuration for the object. • Once you have selected all systems you want to set up, click the "Next" button. Make sure you are in Edit mode when you click Next, otherwise no default templates will be assigned to the selected systems. • In this step you can also remove monitoring from a managed object if necessary using the "Remove Monitoring" button. ozsoft-consulting.com ITConductor.com 13
  14. 14. System Monitoring: Setup Monitoring • In this step monitoring templates will be assigned to the managed systems in scope. • Each managed technical system consists of several managed objects of type technical instance, database and host. • Managed objects can have one template per installed product. • Choose the Apply and Activate button to apply and activate the assigned templates (you can display or change the default templates in step Template Maintenance). For all managed objects in scope the assigned templates are applied and activated. This is done in the background, so you can continue the configuration right away. ozsoft-consulting.com ITConductor.com 14
  15. 15. System Monitoring: Complete • The system monitoring setup is completed for the managed systems in scope. • In this step the status of all previous system monitoring steps are displayed. ozsoft-consulting.com ITConductor.com 15
  16. 16. System Monitoring: Demo • Check System Monitoring in SOLMAN_WORKCENTER • You can also access Solution Manager content from the Fiori Launchpad ozsoft-consulting.com ITConductor.com 16
  17. 17. System Monitoring: Demo • Click on a System’s: • Click on a System’s Alert count: ozsoft-consulting.com ITConductor.com 17
  18. 18. System Monitoring: Demo • Click on a System’s Alert count: • Alert Details: Shows Metric Rating ozsoft-consulting.com ITConductor.com 18
  19. 19. System Monitoring: Demo • Metric Monitoring: ozsoft-consulting.com ITConductor.com 19
  20. 20. Solman 7.2 System Monitoring: Summary • Solution Manager 7.2 System Monitoring is a project, not a simple task, which involves: • Planning, budget, time, resources (Solman as well as the managed infrastructure) • Installation of Solution Manager, upgrade, patches • System Preparation including BW store, SLD, LMDB, Introscope, Life Cycle Managers • Basic Configuration: Solution Manager Diagnostics Agents, Host agents and connectivity • Managed Systems Configuration: discover agents, assign products • System Monitoring: scope of systems and report • Search Engine: TREX installation is needed for non-HANA databases • Solman is a mission-critical enterprise application with full IT landscape which requires dedicated management of: systems, software, components, connectivity, knowledge, and team. In return, you get automated aggregation of alerts, metrics and chart. For historical metrics, you need to configure BI ozsoft-consulting.com ITConductor.com 20
  21. 21. Solman 7.2 System Monitoring: Comparison • In this example we set up Solman to monitor an S/4HANA environment, total effort (60 hours – Solman Installation & Setup, 20 hours Managed System Configuration). The effort excluded infrastructure cost and setup, and without TREX search engine • In comparison, IT-Conductor took less than 1 hour to configure and monitor S/4HANA using cloud-based SaaS platform, no infrastructure required: https://www.itconductor.com/blog/cloud- based-sap-monitoring-of-s4hana-on-azure ozsoft-consulting.com ITConductor.com 21
  22. 22. SAP Monitoring as a Service • Every customer’s Solution Manager should be monitored as a business critical environment for optimal availability and performance. IT-Conductor can be used in this scenario ‘How to Monitor SAP Solution Manager’: https://www.itconductor.com/blog/how-to-monitor-sap-solution- manager • Get the latest SAP Monitoring Comparison v2.0 https://www.itconductor.com/blog/sap-monitoring-tools-video- overview • What if you just need help with SAP Basis and/or Solution Manager? Engage OZSOFT’s 20+ years experienced global SAP Basis services ozsoft-consulting.com ITConductor.com 22
  23. 23. • Any Questions? • Contact Info: info@itconductor.com • Follow us: https://www.linkedin.com/company/it-conductor Let itconductor.com @itconductor ozsoft-consulting.com ITConductor.com 23

×