Upload
duongcong
View
261
Download
6
Embed Size (px)
Citation preview
Monitoring Detailed Overview
UpdatedSeptember 28, 2005
Product ManagementSAP NetWeaver Infrastructure Management SAP AG
SAP AG 2005, Monitoring Detailed Overview / 2
Agenda
The Challenge of Monitoring a Landscape
Overview of CCMS Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 3
Agenda
The Challenge of Monitoring a Landscape
Overview of CCMS Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 4
The Challenge of Monitoring Landscapes
A typical solution landscape such as mySAP CRM at a customer site:Many hardware and software componentsMany interfacesBusiness processes that span multiple componentsIs Complex.
What does an administrator have to check?Are all components available? Are transactions performed with sufficient performance?Are all interfaces working properly?If a problem occurs: What is the cause of it? How can it be resolved?Are yesterday’s backups complete and usable?…
SAP AG 2005, Monitoring Detailed Overview / 5
Example: CRM / EBP Landscape
Middleware
Middleware
Advanced Planner and
Organizer
Business Intelligence
SAP BackendSystem
Employee
Vendor'sWeb Server
Vendor
Customer
EmployeeIntranet
Internet
Internet
Internet
Supplier Self-Services
XIITS
Enterprise Buyer
CRM Internet Sales
TREX
IMSSAP J2EE Engine
Catalog Server IPC
SAP J2EE Engine
IPC
SAP AG 2005, Monitoring Detailed Overview / 6
The Challenge
An administrator’s nightmare:Performance of crucial transactions is very low.Main components become unavailable.Business processes are delayed.
Action required:Locate the problem.
Find out its cause.
Tackle the problem.
Prevent this from happening again.
SAP AG 2005, Monitoring Detailed Overview / 7
The Solution: SAP’s Monitoring Infrastructure
SAP’s Monitoring Infrastructure has the following benefits:
Central monitoring in one single screenLarge landscapes can be centrally monitored at a low total cost of operation.
Full scalabilityLandscapes with only a few components or a large number of components can be efficiently monitored.
Preventive monitoring with alertsNo admin activity is required except in case of alerts. Alert notifications (e-mail, SMS …) can be triggered automatically.Assisted problem detection and resolutionFrom the central system, administrators can drill down to a monitored component to remove the cause of an alert using predefined analysis functions.
SAP AG 2005, Monitoring Detailed Overview / 8
Agenda
The Challenge of Monitoring a Landscape
Overview of SAP Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 9
Monitoring Infrastructure and Workload Statistics
Workload StatisticsAggregated data:
• in each component
• landscape-wide (in ABAP stack)
Detailed data:• in each component
• landscape-wide (in ABAP stack)
CCMS Monitoring InfrastructureOverview data:
• in each component
• landscape-wide (in ABAP stack)
JAVA
Engine
ABAP
Kernel
DSRSTAT
Two Different Aspects
SAP AG 2005, Monitoring Detailed Overview / 10
Monitoring Overview
SAP Web AS JavaSAP Web AS Java
Shared MemorySegment
AgentShared Memory
Segment
Non-SAP componentAgent
Push
SAP Basis ≥ 3.0SAP instance
Shared MemorySegment
Agent
SAP Web AS ABAP
Shared MemorySegment
SAP instance
Push
Agent
Solution Manager
3rd PartyTools
Central Monitoring Infrastructure
SAP NetWeaverAdministrator
ABAP Stack
Java Stack
BusinessIntelligence
SAP AG 2005, Monitoring Detailed Overview / 11
Central Views of Local Monitoring Data
SAP Web AS ABAP
RFC
RFC
RZ20
Shared Memory
RZ20
Local MonitoringCentral
MonitoringCentral
Monitoring
RZ20
CCMS Monitoring Infrastructure CCMS Monitoring Infrastructure
SAP Web AS ABAP
CENC11
SAP AG 2005, Monitoring Detailed Overview / 12
Monitoring Infrastructure
What is CCMS ?
The Computing Center Management System
is
SAP’s open, integrated infrastructurefor centrally monitoring SAP landscapesProvides alert monitor templatesPart of any SAP Web AS ABAP and SAP Basis componentFree of charge
SAP AG 2005, Monitoring Detailed Overview / 13
What can be monitored?
Predefined templates provide different monitoring views of SAP solutions and components:
Based on SAP Web Application Server (ABAP and Java, also Basis Releases as of 3.0)Enterprise Buyer Professional / Customer Relationship Mgmt.Supply Chain Management (APO / LiveCache)Supplier Relationship Management (SCM)Business Intelligence (BI)Exchange InfrastructureMobile InfrastructureEnterprise PortalInterfaces: tRFC / qRFC / ALE
Other SAP componentsInternet Transaction ServerIndex Management ServerBusiness Connector SAProuter…
Non-SAP componentsEMC2 Symmetrix…
SAP AG 2005, Monitoring Detailed Overview / 14
Agenda
The Challenge: Monitoring a Landscape
Overview of CCMS Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 15
SAP NetWeaver Monitoring
ABAP J2EE
ABAP Java
Central Monitoring Infrastructure Global Workload Statistics
NetWeaver Administrator on the Java Stack
SAP AG 2005, Monitoring Detailed Overview / 16
Architektur der CCMS-Monitoring-Infrastuktur
3rd Party Products
3rd Party Products
A P IA P I
Local Analysis
Central Auto
Reaction
Admini-stration
CCMS Alert Monitors
Solution Manager
NetWeaverAdministrator
Central Data Display
Local Shared Memory SegmentsLocal Shared Memory SegmentsMonitoring
ObjectMonitoring
Object
Data SupplierData
SupplierData
SupplierData
Supplier
Monitoring Object
Monitoring Object
Data SupplierData
SupplierData
SupplierData
SupplierData
SupplierData
Supplier
Monitoring Object
DataCollection
DataStorage
DB OS ABAP Java Non-SAP
DB
SAP AG 2005, Monitoring Detailed Overview / 17
Agenda
The Challenge: Monitoring Large Landscapes
Overview of CCMS
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 18
Alert Handling Overview
SAP Basis ≥ 3.0 SAP Web AS ABAP
Shared MemorySegment
Non-SAP component
SAP instanceSAP instanceSAPCCM4X
SAPCCMSR
Alerts displayed
SAP Web AS JavaSAP Web AS Java
Shared MemorySegment
Shared MemorySegment
Shared MemorySegment
SAPCCMSR
SAPCCM4X
Push
Push
SAPCM3X
SAPCCMSR
Central Monitoring Infrastructure
SAP NetWeaverAdministrator
ABAP Stack
Java Stack
Central Alert Notification
SAP AG 2005, Monitoring Detailed Overview / 19
Monitor Sets and Monitors
All tree nodes
Represents one physical or logical objectSummarizes alerts andpropagates them to higher nodes
Receive data and may create alertsUse data for analysisalerts
Monitoring TreeElements
Monitoring Attributes
Monitoring Object
View
SAP AG 2005, Monitoring Detailed Overview / 20
History and Current View
Current
Switch between views
History
SAP AG 2005, Monitoring Detailed Overview / 21
Displaying Alerts
Doubleclicking a node showsall corresponding alerts
SAP AG 2005, Monitoring Detailed Overview / 22
Removing the Cause of an Alert
2) Start the analysis method in the monitored system1) Mark the alert
CEN
SAP AG 2005, Monitoring Detailed Overview / 23
Analysis Method in Monitored System
Example
Monitored system
SAP AG 2005, Monitoring Detailed Overview / 24
Completing Alerts
CEN
3) Alert cause resolved in monitored component:Complete the alert in CEN
SAP AG 2005, Monitoring Detailed Overview / 25
Agenda
The Challenge: Monitoring Large Landscapes
Overview of CCMS Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 26
Monitoring Components
Monitoring Special Components
SLA Reporting
Availability Monitoring
SAP AG 2005, Monitoring Detailed Overview / 27
Monitoring Components
Monitoring Special Components
Central Monitoring
Central Monitoring
RZ20
CEN
Internet Pricing and Configurator
Host
IPC
SAPCCMSRRFC
SAP AG 2005, Monitoring Detailed Overview / 28
Monitoring Components
Monitoring Special Components
Central Monitoring
Central Monitoring
RZ20
CEN
Business ConnectorHost
BCBC
Jmon-APIJmon-API
SAPCCMSRRFC
SAP AG 2005, Monitoring Detailed Overview / 29
Monitoring Components
Central Monitoring
Central Monitoring
ITS
DLLDLL
AGate
RFC ITS
DLLDLL
AGate
RZ20
SAPCCMSR
SAPCCMSR
CEN
Monitoring Special Components
RFC
SAP AG 2005, Monitoring Detailed Overview / 30
Monitoring Components
SLA Reporting
Important for Reporting on Service Level Agreements (SLA):
Component availability
Front-end response times (SAPGUI)
Transaction-specific responsetimes
Standard response time
...
SAP AG 2005, Monitoring Detailed Overview / 31
Monitoring Components
New Components and Applications, and Solutions
Exchange Infrastructure 3.0
Mobile Infrastructure as of 2.5
Enterprise Portal 6/SP1; EP 5/SP6
SAP Business Intelligence (BI)as of 3.1
SAP Customer RelationshipManagement (CRM) as of 4.0
AP Supply Chain Management (SCM) as of 4.1
SAP Supplier RelationshipManagement (SRM) as of 2.0
SAP AG 2005, Monitoring Detailed Overview / 32
Monitoring Components
Availability Monitoring
HeartbeatStatus of last availability check
AvailabilityPercentage of sucessful heartbeat checksover a given period of time
SAP AG 2005, Monitoring Detailed Overview / 33
Availability: Different Levels – Different Mechanisms
Are all components up and running?
Any SAP Web AS Application (Java or ABAP)
Central Monitoring
Central Monitoring
Web AS ≥ 6.20
CEN
XML Message Request(GRMG)
MessageServer
CCMSPING Agent
ApplicationServer
SAP J2EEEngine
SAP Web AS
Other SAP Components(SAProuter, ITS)
RFC DestinationAny RFC-enabled
ComponentCheck
Process Monitoring
SAP AG 2005, Monitoring Detailed Overview / 34
Application Availability: GRMG and GRMG Lite
Infrastructure
GRMGInfrastructure
ABAP Application
GRMGApplication
SAP Web AS
AnyWeb Page
SAP Web AS ABAP≥ 6.20
GRMGApplication
Availability in %,Heartbeat
<?xml version="1.0" …<!DOCTYPE Customizing<!ELEMENT customizing …<!ELEMENT control(grmg…<!ELEMENT …
Configuration File
JavaApplication
Central Monitoring
Central Monitoring
XML Response
http status code / http status code and html output
XML Request
http head / http get
GRMG Liteas of 6.40 SP11
GRMG = Generic Request and Message Generator
SAP AG 2005, Monitoring Detailed Overview / 35
Newest Features of GRMG
GRMG „classic“ for SAP applications; GRMG „Lite“ HTTP PING / HTML scan for any web pagePassword encryption and improved logon capabilitiesEasy-to-use scenario editorAnalysis utilitiesStart/stop scenario executionScenario monitoring pausesScenario runtime measurement
SAP AG 2005, Monitoring Detailed Overview / 36
Application Availability
Example from SAP CRM Interaction CenterChecking the Broadcast Messaging Server with GRMG
Componentavailability
Scenarioavailability
SAP AG 2005, Monitoring Detailed Overview / 37
Availability Checks With CCMSPING
Are all components up and running?
Other SAP Components(SAProuter, ITS)
MessageServer Application
Server
SAP J2EEEngine
SAP Web AS
Central Monitoring
Central Monitoring
Web AS ≥ 6.40
CEN
CCMSPINGAgentpush
SAP AG 2005, Monitoring Detailed Overview / 38
Availability Checks With CCMSPING
Newest Features
Multiple CCMSPING agents in one landscape, for example, one per system groupCCMSPING pushes data to CEN in one-minute intervalsDynamic management of monitoring by way of referencesystem groups
SAP AG 2005, Monitoring Detailed Overview / 39
SAP System Landscape Availability
Availability Monitor for SAP System Landscapesusing the CCMSPINGagent
One availability node per monitored system
System availability
ABAP Instance
Java Instance
SAP AG 2005, Monitoring Detailed Overview / 40
RFC Destination Check
Central Monitoring
Central Monitoring
CEN
RFC DestinationRFCLIB
CheckAny RFC-enabled
Component
SAP AG 2005, Monitoring Detailed Overview / 41
RFC Destination Check
Example from SAP CRM Internet Sales Checking Availability of the Product Catalog Server‘sRFC Destination
RFC destinationavailability
SAP AG 2005, Monitoring Detailed Overview / 42
Process Monitoring
SAP or Non-SAP Component
processXSAPOsCol
processX
processY
SAPCCMSR
*procmon.ini
Central Monitoring
Central Monitoring
CEN
SAP AG 2005, Monitoring Detailed Overview / 43
Process Monitoring
...\prfclog\procmon\<xyz>procmon.ini
MaxDB isalive
SAP AG 2005, Monitoring Detailed Overview / 44
Windows Event Log Monitoring
The Windows Event Log
in the Alert Monitor
(triggered by switch in SAPCCMSR.INI)
SAP AG 2005, Monitoring Detailed Overview / 45
Agenda
The Challenge: Monitoring a Landscape
Overview of CCMS Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 46
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
Statistical Records Correlation (enhanced as of 6.20)
Enhanced CCMS Agents
Open Integration
SNMP Data Exchange With Third-Party Tools
SAP AG 2005, Monitoring Detailed Overview / 47
Enhanced Availability Checks
Availability of SAP SystemLandscapes(using the CCMSPING Agent)
RFC Destination Check
Application Availability(GRMG)
SAP AG 2005, Monitoring Detailed Overview / 48
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
Statistical Records Correlation
Enhanced CCMS Agents
Open Integration
SNMP Data Exchange With Third-Party Tools
SAP AG 2005, Monitoring Detailed Overview / 49
Performance Data Persistence — Why?
Monitoring data is displayed as views on shared main memory.
The performance data displayed in a CCMS Performance Monitor isvolatile:
The size of the shared memory monitoring segments is limited.
Monitoring data slots are continously overwritten.
Is there a need for persistent performance data?
Yes!
Long-term performance history reporting is needed, particularly for reporting purposes in the context of Service Level Agreements (SLA).
SAP AG 2005, Monitoring Detailed Overview / 50
Performance Data Persistence
SAP Web AS JavaSAP Web AS Java
Shared Memory
Non-SAP component
Shared Memory
SAP System forCentral Monitoring
SAP System forCentral Monitoring
SAP Web AS ≥ 6.20
Central Performance History
SAP Web Application Server
Shared Memory
SAP Basis ≥ 3.0
Shared Memory
SAP AG 2005, Monitoring Detailed Overview / 51
Performance Data Persistence
Features of the Central Performance History (CPH):Central collection of monitoring data of the complete systemlandscape in a performant way.
Handles minute, quarter-hourly and hourly monitoring data.
Aggregations from minute values to hourly, monthly and yearlyaverages
Reorganization provided
Accessible from the Alert Monitor
Configurable, scheduled reporting
Export of reported data to operating system level supported
SAP AG 2005, Monitoring Detailed Overview / 52
Analyzing Monitoring Data in BI — Why?
The CPH provides limited reporting on CCMS data stored in the central monitoring system.
Highly sophisticated reporting on such data can be achieved using SAP Business Intelligence (BI).
BI has the following benefits: Central part of SAP NetWeaver
Optimized for saving and analyzing huge amounts of data
Flexible and personalizable reports
Linking of reports (drill-down analysis)
Correlation of independent data sources (CCMS, CRM, FI)
Powerful SAP BI analysis tools (correlations, trends, ….)
Low-cost Service Level Management
SAP AG 2005, Monitoring Detailed Overview / 53
Data Flow Overview
Central Monitoring
DEF
Monitoring Infrastructure
Monitored
Systems
ABC
XYZSAP Web AS SAP Web AS ≥≥ 6.406.40
Info Cube
BusinessIntelligence
Info Cube
Report
As of 2006
WorkloadStatistics
ExtractorsSTAT
PerformanceData
Extractors
BI Content3.52
CPH
Alert Monitordisplays
data of thelast 24 hours
CPH stores data
older than 24hours
SAP AG 2005, Monitoring Detailed Overview / 54
Analyzing Monitoring Data in BI
Facts and Benefits :All performance data (from ABAP and Java stack) is collected in CPH:
Central data collection, aggregation, and reorganization
Delivered for CEN releases as of SAP Web AS ABAP 6.20 SP17
All data collected in CPH is transferred into BICCMS data is stored in several BI data containers (info cubes).
Demo reports are available.
Powerful reporting design using BI reporting tools.
Available as of SAP Web AS ABAP 6.20, Basis Plug-In 2004, and BI Contentrelease 3.52.
Statistical data from (from ABAP and Java stack) is transferred to BIBI as a central data platform for powerful root cause and performance analysisand SLA reporting.
To be delivered in 2006.
SAP AG 2005, Monitoring Detailed Overview / 55
Analyzing Monitoring Data in BI
SAP Business Intelligence can link any data from variouscontainers to create a new, virtual container.
Report
SAPPerformance
Data
Non-SAPCustomer
Data
VirtualData
Container
BI Standard
Technology
SAPApplication
Data
Advantage: Innovative and highly flexible analysis options
SAP AG 2005, Monitoring Detailed Overview / 56
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
SNMP Data Exchange With Third-Party Tools
Statistical Records Correlation
Enhanced CCMS Agents
Bi-directional Open Integration
SAP AG 2005, Monitoring Detailed Overview / 57
CCMS and Alert Management
What is Alert Management?An SAP standard framework for activereal-time delivery of mission critical information:
Support for e-mail, SMS/Pager, Fax, WAP, Web Interface ...
Personalized alert content and deliveryEasy-to-use definition environmentPreferred channels for messagesPublish and subscribe mechanism for alert topicsDisplayed in EP universal worklist
Escalation of alert notifications in case of inactivity
Supported by CCMS as of SAP Web AS 6.20
SAP AG 2005, Monitoring Detailed Overview / 58
Central Alert Management — Overview
Push
RFC
Alert
Alert Inbox WAP
Central MonitoringCentral Monitoring
SAP Web AS JavaSAP Web AS Java
Central Alert Management
Central Alert Management
SAP Web AS 6.20
SAPCCMSR
CEN ALM
SAPconnect:E-Mail, Fax, SMS, Pager, ...
SAP Web AS ABAPSAP Web AS ABAP SAPCCM4X
Alert
SAP AG 2005, Monitoring Detailed Overview / 59
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
Statistical Records Correlation
Enhanced CCMS Agents
Open Integration
SNMP Data Exchange With Third-Party Tools
SAP AG 2005, Monitoring Detailed Overview / 60
Workload Statistical Records
What are workload statistics used for?
To trace a business process running across multiple components
To find out how often a component has been calledBy whom?For what reason?From where?
To discover all parts and response times of a process
To analyze problems in CCMS monitoring using theappropriate analysis function
SAP AG 2005, Monitoring Detailed Overview / 61
Statistical Records Correlation
Cross-Component CorrelationJava writes distributed statistical records (DSRs)
JAVA
Engine
ABAP
Kernel
ERP
ABAP
Kernel
APO
DSR STAT STATWeb AS Java
≥ 6.20
Data is correlated across components using the
GUID contained in the passport
Central display• aggregated• detailed
SAP AG 2005, Monitoring Detailed Overview / 62
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
Statistical Records Correlation
Enhanced CCMS Agents
Open Integration
SNMP Data Exchange With Third-Party Tools
SAP AG 2005, Monitoring Detailed Overview / 63
Enhanced CCMS Agents
SAP Basis ≥ 3.0 SAP Web AS ABAP
Shared MemorySegment
Shared MemorySegment
Non-SAP component
Central MonitoringCentral Monitoring
SAP Web AS JavaSAP Web AS Java
Shared Memory
Segment
Shared MemorySegment
SAP Web AS ABAP≥ 6.20
SAPCCMSR SAPCCMSR
SAPCM3X SAPCCM4X
Push
Push
All monitoring datais pushed to CEN as of 6.20
CEN
SAP AG 2005, Monitoring Detailed Overview / 64
Enhanced CCMS Agents — Details
External Software
Log File
ExternalComponents
SAPOsCol
Alert File
DataSupplier
DataSupplier
RFC JAVA
JAVA Interface
SAP InstanceSAP Instance
Monitoring Segment
ProcessProcess Agent
Central MonitoringCentral Monitoring
CEN
SAP AG 2005, Monitoring Detailed Overview / 65
Enhanced CCMS Agents — Types
Different Types of Agents for Different ComponentsSAPCCMSR
Monitors the SAP J2EE Engine and components without any active SAP instance. Transfers detailed OS data to CEN by help of SAPOsCol.
SAPCCM4XTransfers CCMS alert monitoring data from any SAP System as of Release 4.0 to CENRequires no dialog work process on central systemCan be registered at several central systems to ensure high availability.
SAPCM3XConnects SAP Systems 3.X to a central monitoring systemdelivering the dispatcher‘s performance data.
CCMSPINGNew: Now an active data supplier for SAP system landscapemonitoring (pushes availability data to CEN)No longer requires a dialog work process on central system
SAP AG 2005, Monitoring Detailed Overview / 66
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
Statistical Records Correlation
Enhanced CCMS Agents
Open Integration
SNMP Data Exchange With Third-Party Tools
NetWeaver Administrator (as of SAP NetWeaver 04, SP 12)
SAP AG 2005, Monitoring Detailed Overview / 67
Open Integration
Open Integration with Third-Party Tools
Outbound Interface (XAL)Tight integration with third-party monitoring solutions. Provides access to a central SAP monitoring system with SAP landscape monitoring data, including data from Java components.
New: Inbound Interface (XMW)With XMW, third-party monitoring data can be reported into CCMS.Administrators can drill down into and trigger the third-party monitoring tool as an analysis method for further analysis.
Both interfaces are available for certification.
SAP AG 2005, Monitoring Detailed Overview / 68
Open Integration
New Inbound XML Interface
SAP Web AS ≥ 6.10
BAPICall
HTTP
Post
XML data is converted in a CCMS monitoring tree.XML interface is deliveredwith SAP Web AS 6.20 and patched down to 6.10.
Central MonitoringCentral Monitoring
CENCEN
CCMS Monitoring Infrastructure
SAPCCM4XAgent XML
SAP AG 2005, Monitoring Detailed Overview / 69
New Features at a Glance: ABAP Stack
Enhanced Availability Checks
Performance Data Persistence and BI Reporting
CCMS and Alert Management
Statistical Records Correlation
Enhanced CCMS Agents
Open Integration
SNMP Data Exchange With Third-Party Tools
SAP AG 2005, Monitoring Detailed Overview / 70
SNMP Data Exchange With Third-Party Tools
Exchange of Monitoring Data with Third-Party ToolsUsing The SNMP Protocol
SNMP is a de-facto standard for system management and monitoring
No additional interfaces required on the part of third-party tools
Low-cost solution implies reduced TCO
Central monitoring of components that support SNMP
Supports status reporting of devices and components(such as: SAP components or instances, network routers, switches, and printers)Various SNMP versions supported
SAP AG 2005, Monitoring Detailed Overview / 71
SNMP Data Exchange With Third-Party Tools
Central Monitoring
Central Monitoring
CEN
Alerts exchanged as SNMP traps
No additional interfaces
Monitored Components
Third-PartyMonitoring
Console
Monitored Components
SAP AG 2005, Monitoring Detailed Overview / 72
New Features at a Glance: Java Stack
J2EE Integration into CCMS Monitoring Infrastructure
Log Viewer Types
Distributed Statistics Records
One Agent Per J2EE Instance (as of 6.40)
SAP NetWeaver Administrator
The following slides provide a quick overview of these new features.
For more details, use quick link JAVAMONITORING in theSAP Service Marketplace
SAP AG 2005, Monitoring Detailed Overview / 73
J2EE Integration into CCMS Monitoring Infrastructure
J2EE EngineVisual Administrator
Logging
SAP Web AS Java
PerformanceData
Monitoring
Central MonitoringInfrastructure
Central MonitoringInfrastructure
SAP Web AS ABAP
CEN
CCMS Alert Monitors also display the data collected by the J2EE Engine.Availability checks of monitored J2EE componentsCentral data push to CEN by CCMSR agentNetWeaver Administrator will replace CCMS Alert Monitors and Visual Administrator.
SAP AG 2005, Monitoring Detailed Overview / 74
Monitoring Tree in Visual Administrator
SAP AG 2005, Monitoring Detailed Overview / 75
Log Viewer Types
Log Viewer Types
Central Log Viewer (NetWeaver Admin)Web-based
Integrated Log Viewer (Visual Administrator)All the logs written from the Engine and the running applications areautomatically registeredCustomizing the properties, switching on Log Monitoring ...
Standalone Log Viewer for Central Log ViewingConsists of Log Viewer Server and Log Viewer Client. Logs from a System Landscape can be viewed centrally in one Standalone Log Viewer Client, if oneLog Viewer Server runs on every host.
Command Line Log ViewerUsage: lv.bat, delivered with Standalone Log Viewer
Only for viewing local logs on consoleCan be switched on during deploymentConverts binary data into human readable data
SAP AG 2005, Monitoring Detailed Overview / 76
Distributed Statistics Records
Distributed Statistics Records (DSRs)statistical data written by the J2EE Engine
administered in the DSR Service of the Visual Administrator
DB
SAP System forCentral Monitoring
SAP System forCentral Monitoring
Hourly data pullfor statisticsaggregation
Aggreg.statistics
Single Record
Direct call forlast minutes‘ load
SAP Web AS JavaSAP Web AS Java
DSR Service
CollectorDatabase
SAP Web AS ABAP ≥ 6.20
SAP Web AS Java≥ 6.20
DSRCollector
File SystemSAPCCMSR
Agent
Non-aggregatedsingle records
SAP AG 2005, Monitoring Detailed Overview / 77
One Agent Per J2EE Instance
Monitoring Segment XXSAPCCMSR
Java 6.40Instance XXJava 6.40
Instance XX
Monitoring Segment YYSAPCCMSR
Java 6.40Instance YYJava 6.40
Instance YY
EJB / JMX
EJB / JMX
Central MonitoringCentral Monitoring
SAP Web AS ABAP ≥ 6.40
CEN
Performance increaseEasy-to-read monitorsThresholds of J2EE counters are maintained from CEN orVisual Administrator and stored in the J2EE database.SAPCCMSR with its monitoring data is treated like an SAP system.
SAP AG 2005, Monitoring Detailed Overview / 78
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the new browser-basedcentral administration and monitoring solutionfor your SAP NetWeaver system landscape.
It will replace both CCMS Alerts Monitors and Visual Administrator.
ABAP
SAP NetWeaver Administrator is a Java application that is part of the shipment of SAP NetWeaver ’04 from 6.40 SP 12 on and NW2004S.
Central Monitoring Infrastructure
SAP NetWeaverAdministrator
Central Administration and Monitoring
ABAP Stack
Java Stack
SAP AG 2005, Monitoring Detailed Overview / 79
SAP Netweaver Administrator
Key Capabilities
NetWeaver Administrator will replace CCMS Alert Monitors and Visual Administrator.Monitors ABAP and Java components together in a new Web applicationClear and structured data presentationState-of-the-art application based on WebDynpro, which meets latest SAP UI standardsDeals with current / historical data and alerts Central Web-based log viewer
SAP AG 2005, Monitoring Detailed Overview / 80
SAP NetWeaver Administrator
Java
ABAPMonitoring
Infrastructure
NetWeaverAdministrator
J2EEEngine
SAPCCM4X
SAPCCMSR-j2ee
SLDJ2EE
Engine
Central Monitoring and Administration System ABAP
MonitoredComponents
SLD SystemJava
SAP AG 2005, Monitoring Detailed Overview / 81
Agenda
The Challenge: Monitoring a Landscape
Overview of CCMS Monitoring
Architecture
Alert Handling
Monitoring Components
New Features at a Glance
Summary
SAP AG 2005, Monitoring Detailed Overview / 82
Summary
Central Monitoring of SAP LandscapesNetWeaver Administrator will replace CCMS Alert Monitors and Visual Administrator.
SAP’s central monitoring infrastructure is flexible and fully scalable.
Monitoring data is displayed centrally byCCMS Alert Monitors Solution ManagerSAP NetWeaver AdministratorThird-party monitoring tools
Workload StatisticsCorrelated across components (including Java)Displayed centrally in the Global Workload Monitor
Open integration with third-party products
CCMS is an integral part of SAP technology
Free of charge
SAP AG 2005, Monitoring Detailed Overview / 83
Certification for Third-Party Software Vendors
When third-party software is successfully certified, a company:
Receives the right to use the SAP tagline
Receives an SAP Interface Certificate
Acquires a listing in the SAP online partner and product directory-- a valuable resource for customers and consequently an opportunity for vendors to market their softwarewww.sap.com/icc
Satisfies one of the criteria for becoming an SAP partner www.sap.com/partner
SAP AG 2005, Monitoring Detailed Overview / 84
Further Information
SAP Service MarketplaceFor more information, use the quicklinks /monitoring and /javamonitoring.
Related SAP Traininghttp://www.sap.com/ → EducationADM106, Advanced System MonitoringADM100, SAP Technology AdministrationADM200, SAP Web AS Java Administration
ContactMail to Product Management: [email protected]
Consulting contact: Stephan Schmid([email protected])
SAP AG 2005, Monitoring Detailed Overview / 85
Copyright 2005 SAP AG. All Rights Reserved
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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
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 Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.