Post on 15-Apr-2016
description
Configuration of System Monitoring in SAP
Solution Manager 7.1
Active Global Support
2011
© 2011 SAP AG. All rights reserved. 2
SAP Solution Manager 7.1 – System MonitoringOverview
The System Monitoring setup
• Configures the Monitoring and Alerting Infrastructure
• Configures managed systems for use with System Monitoring
© 2011 SAP AG. All rights reserved. 3
Check PrerequisitesSystem Preparation
Prerequisite for the System Monitoring Setup is a successful execution of the
System Preparation which consists of the following steps:
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
© 2011 SAP AG. All rights reserved. 4
Check PrerequisitesBasic Configuration
Prerequisite for the System Monitoring Setup is a successful execution of the Basic
Configuration which consists of the following steps:
Specify Project
Specify User &
Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
© 2011 SAP AG. All rights reserved. 5
Check PrerequisitesManaged System Configuration for SAP Solution Manager
Prerequisite for the System Monitoring Setup is a successful execution of the
Managed System Configuration of the Solution Manager system itself.
In case the SAP Solution
Manager system is not set as
“Diagnostics Relevant” parts of the
Monitoring & Alerting Infrastructure
will not work.
© 2011 SAP AG. All rights reserved. 6
Check PrerequisitesManaged System Configuration of Managed System
Prerequisite for the System Monitoring Setup of a managed system is a successful
execution of its Managed System Configuration.
© 2011 SAP AG. All rights reserved. 7
The System Monitoring Setup is integrated in transaction SOLMAN_SETUP
• Choose the section
Technical Monitoring
• Choose the monitoring use case
System Monitoring
• Follow the guided procedure
System Monitoring Setup
© 2011 SAP AG. All rights reserved. 8
This step provides you with a rating if the monitoring & alerting infrastructure is
already setup, or if you yet need to perform the infrastructure configuration.
System MonitoringOverview
Check / perform step 2
Continue with step 3
© 2011 SAP AG. All rights reserved. 9
To setup the system monitoring for a managed system first the Monitoring
Infrastructure needs to be configured. Therefore all sub-steps have to be executed.
This needs to be done only once and not per managed system.
This step provides you an overview of the Configure Infrastructure sub-steps.
System MonitoringConfigure Infrastructure
Direct navigation to one of
the sub-steps by clicking
the description link
By selecting a sub-step
the log area shows only
the logs of the selected
sub-step
© 2011 SAP AG. All rights reserved. 10
The prerequisite check ensures that the parts of SAP Solution Manager which are
needed for monitoring are setup correctly.
System MonitoringCheck Prerequisites
Checks if the Basic
Configuration is done
successfully
Checks if the BI setup
requirements are
fulfilledIn case of errors or warnings check
the “Details” for further information
© 2011 SAP AG. All rights reserved. 11
In this step some manual activities are performed. The activities
•Agent Framework
•Extractor Framework
•Alerting Framework
are optional. By default they don’t need to be executed. For an advanced
configuration they guide you to the related administration UIs which can also be
found in the Solution Manager Administration workcenter.
System MonitoringConfigure Manually (1/2)
Optional Steps.
The navigation links
guide to the related
administration UI
The “Execution Status” needs to be set
manually to “Performed” to get a green
status for the activity.
© 2011 SAP AG. All rights reserved. 12
The Content Customization
activity allows you to change
the content send in the
different types of notifications.
System MonitoringConfigure Manually (2/2)
2. Select content to
be shown
1. Select the
notification type to
be changed
3. Press the “Save”
button to persist the
changes
© 2011 SAP AG. All rights reserved. 13
In this step some automatic activities are performed by SAP Solution Manager.
They need to be executed successfully. In case of errors or warnings check the log
details for further information.
System MonitoringConfigure Automatically
© 2011 SAP AG. All rights reserved. 14
Template Settings
• Configured on template level
in Template Maintenance
• Overwrites the Global Settings
The Monitoring and Alerting Infrastructure provides three configuration levels to
allow a fast straight forward configuration without loosing the flexibility to configure
special use cases. It is applicable for:
• Incidents
• Notifications
• Third-Party Components
• Workmodes
System MonitoringConfiguration Levels
Global Settings
• Configured in
Infrastructure Configuration
• Used as default if there are no
Template or Alert specific
settings
Alert Settings
• Configured on template level
in Template Maintenance
• Overwrites the Global Settings
and Template Settings
© 2011 SAP AG. All rights reserved. 15
In this step the global setting are done for:
• Incidents
• Notifications
• Third-Party Components
System MonitoringDefault Settings (1/4)
The summary tab provides an
overview which functionality is
enabled. The details for each
functionality are configured on
the related tabs.
© 2011 SAP AG. All rights reserved. 16
On the incident tab the incident specific global setting are done.
System MonitoringDefault Settings (2/4)
Switch
Auto-Incidents
on or off
Define the
default support
component
Define if the
confirmation of an
incident automatically
closes the related
alert in the alert inbox
Define the
default CRM
transaction type
© 2011 SAP AG. All rights reserved. 17
On the notification tab the notification specific global setting are done. You define if notification
are send automatically in case of an alert and define who should receive a notification. Further
notification setting (e.g. maintenance of SMS server) can be done in the Technical
Administration workcenter Notification Management
System MonitoringDefault Settings (3/4)
Switch
Auto-Notifications
on or off
Add / delete
entries from the
list of recipients.
An entry is either
a single recipient
or a recipient list.
Configure your
own settings
when you want to
be notified via
email or SMS
Maintenance of
Recipient Lists
Maintenance of
notification
settings for global
recipients
© 2011 SAP AG. All rights reserved. 18
On this tab you can configure the usage for third-party connectors (e.g. HP
OpenView). Before a third-party connector can consume events from the Monitoring
& Alerting Infrastructure a third-party specific BAdI implementation needs to be
done.
System MonitoringDefault Settings (4/4)
© 2011 SAP AG. All rights reserved. 19
In this step the Monitoring specific BI content gets activated. The BI based
Reporting Health Checks needs to have a green status before the BI Content
Activation can be started.
System MonitoringReporting Settings
The Start button
schedules the batch job
CCMS_BI_SETUP which
does the BI content
activation in background.
While the job is running
the status icon shows a
running icon.
© 2011 SAP AG. All rights reserved. 20
In case of an BI health check error the result tree is automatically opened and shows the
errors. The Long text info button opens a detailed error description and a procedure how to
solve the problem. Once the problem is solved the related check needs to be re-executed to
get a green health check status. Otherwise the BI Content activation cannot be started.
System MonitoringReporting Settings
Re-execute the check after
the problem is solved
© 2011 SAP AG. All rights reserved. 21
In this step you can configure the settings for the monitoring related BI housekeeping
and the Monitoring & Alerting Infrastructure housekeeping.
System MonitoringHousekeeping
Monitoring related
BI housekeeping
settings
Monitoring & Alerting
Infrastructure
housekeeping
settings
Configures when
alerts get
automatically
closed
© 2011 SAP AG. All rights reserved. 22
This step allows to configure the global setting for which workmode the monitoring
is enabled / disabled. Workmodes for systems can be scheduled in the Technical
Administration workcenter Work Mode Management
System MonitoringWorkmode Settings
© 2011 SAP AG. All rights reserved. 23
System MonitoringUpdate Content
This step download the latest content updates from the SAP Service
Marketplace (using the SAP-OSS connection). You can perform this either via
download from the SMP automatically
1. Choose Update Content
2. Check Log
Or in the expert mode
1. Upload File
2. Apply desired Version
Check the log
© 2011 SAP AG. All rights reserved. 24
In this step you see the monitoring content delivered by SAP in the SAP Templates.
SAP Templates cannot be modified but copied to Custom Templates. The Custom
Templates can be adapted to the customer needs.
System MonitoringTemplate Maintenance – Overview
Templates are grouped
by Managed Object
Type
SAP Template
Custom Template
Product group for
which the template is
applicable.
© 2011 SAP AG. All rights reserved. 25
To create a custom template you need to:
System MonitoringTemplate Maintenance – Create Custom Templates
1. Select a SAP Template
and press
Create Custom Template
2. Provide a name for
the custom template3. Press the
save button
4. Provide a package
name in case you want to
transport the custom
template. Otherwise set
the Local Object flag to
keep it as a local object.
© 2011 SAP AG. All rights reserved. 26
In step 6 Setup Monitoring default templates will be assigned to the managed
objects of the systems in scope to simplify the setup procedure.
Initially the SAP Template is the default template. To use a custom template as
default template you first need to define it as the default.
System MonitoringTemplate Maintenance – Define the Default Templates
1. Select a
managed
object type
2. For each product version
you can select a specific
default template
© 2011 SAP AG. All rights reserved. 27
In a custom template you can configure on template level settings for:
• Incidents
• Notifications
• Third-Party Components (in expert mode)
• Workmodes
which overwrite the Global Settings done in the Configure Infrastructure step.
System MonitoringTemplate Maintenance – Template Settings
© 2011 SAP AG. All rights reserved. 28
In a custom template you can also on alert level configure settings for:
• Incidents
• Notifications
• Third-Party Components (in expert mode)
• Workmodes
which overwrites the global and template level settings.
System MonitoringTemplate Maintenance – Alert Settings
1. Select an
alert on the
alert tab
2. Perform the
configuration
on the related
detail tab
© 2011 SAP AG. All rights reserved. 29
To change the threshold of a metric you need to have a custom template. Threshold
cannot be changed in the SAP Templates.
System MonitoringTemplate Maintenance – Change Thresholds
1. Select the metric you
want to change on the
metric tab and press the
Change Settings button
2. Now the threshold
values can be changed
The Modified flag
indicates that original
settings derived from the
SAP template have
changed
© 2011 SAP AG. All rights reserved. 30
In this step you have to select the technical system for which you want to setup the
system monitoring.
System MonitoringDefine Scope (1/2)
Line multi-selection is
possible via
Strg + left mouse click
Use filter functionality
to search for systems
Reflects the managed
system setup status.
A successful
execution is prerequisite
for the monitoring setup
Show details
provides more
information about e.g.
managed system
setup with direct
jump-in possibility
Status of previous
System Monitoring
setup
© 2011 SAP AG. All rights reserved. 31
On the Technical Systems tab you can select one or multiple technical systems for the system monitoring
setup.
On the Database tab you can select database to setup system monitoring for standalone databases.
On the Technical Scenarios tab you can create technical scenario of type System Monitoring to group
systems together. When selecting a technical scenario all technical systems of the scenario will be taken
into scope for the next steps.
System MonitoringDefine Scope (2/2)
© 2011 SAP AG. All rights reserved. 32
In this step the system monitoring setup is done for the system selected in step
5 Define Scope:
1. Default templates (see Template Maintenance step) get assigned to the managed
objects when entering the step and no template was assigned before.
2. Change the template assignment if required.
3. Press the Apply and Activate button to start the configuration.
4. When the configuration is finished check the logs for details.
System MonitoringSetup Monitoring – Process
© 2011 SAP AG. All rights reserved. 33
System MonitoringSetup Monitoring – Change Template Assignment
1. To change the template
assignment select a
managed object press the
Assign Template button
2. Per installed product
one template can be
selected via the drop-
down box.
© 2011 SAP AG. All rights reserved. 34
System MonitoringSetup Monitoring – Additional Functions
Sets the template assignment for
the selected Managed Object
back to the default as defined in
the Template Maintenance step
Refresh of the UI
Press after you
performed Managed
Object specific change
Opens new window to
perform managed object
specific configuration.
E.g. change threshold
only for the select
managed object
Opens new window with
the directory browser
where you can check the
currently active
configuration used for
system monitoring
Indicates if a managed
object specific
configuration was done
© 2011 SAP AG. All rights reserved. 35
To get data in BW for the Interactive Reporting the data collection needs to be
activated in this step. Procedure:
1. Select All
2. Press the Activate button
System MonitoringReporting
Systems of type
JAVA cannot be
selected as the data
collection is already
activated when the
managed system
setup is done
© 2011 SAP AG. All rights reserved. 36
In this step, the status of all steps of the System Monitoring setup.
Now you can start using the monitoring applications.
System MonitoringComplete
© 2011 SAP AG. All rights reserved. 37
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission 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 of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C 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 Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
© 2011 SAP AG. All rights reserved
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.