The Role of Industry Standards for the Administration of Global
System Landscapes Dr. Gregor Karl Frey SAP, NW Operations
Infrastructure
Slide 2
Model: CIM The Need for Standards Why Standards are not Enough
Protocol: WS-Management The NetWeaver Administrator and its Partner
Strategy Process: ITIL API: JMX Introduction
Slide 3
SAP AG 2005, Title of Presentation / Speaker Name / 3 Typical
IT-Scenario: Service Level Management An IT-Service Center, which
runs a portal for Employee Self Services, has contractually agreed
with its customer, that The portal is available every weekday, from
8:00 AM to 5:00 PM For at least 90% of the time With a maximal
login time of 5 sec For 2000 concurrent users. To fulfill such an
Service Level Objective (SLO) The required hardware and software
capacity must be determined (Capacity Management) The metrics
related to the SLO must be monitored and recorded (Availability
Management) The configuration of the software must be changed
according to needs (Configuration Management) The downtime for the
application of patches and upgrades must be planed (Release
Management)
Slide 4
SAP AG 2005, Title of Presentation / Speaker Name / 4 Typical
IT-Scenario: Root Cause Analysis An IT-User reports that the
Employee Self Service System Responds not fast enough Shows an
error, when a certain transaction is executed Does not log her in
As a consequence the IT-Service Center Verifies the availability of
the required resources Controls and compares configuration data
Checks all response-time related monitoring records Searches for
critical errors in log-files Sets up a test system with a higher
trace level to replay the scenario
Slide 5
Model: CIM The Need for Standards Why Standards are not Enough
Protocol: WS-Management The NetWeaver Administrator and its Partner
Strategy Process: ITIL API: JMX Introduction
Slide 6
SAP AG 2005, Title of Presentation / Speaker Name / 6 Managed
Objects Storage Firewall Load Balancer Network File system Database
Application Server Business Application Web Service Operating
System User Access Control List Certificates Telecom Devices
Printer Desktop Software Licenses Middleware Chipset Appliance
Network Accelerator
Slide 7
SAP AG 2005, Title of Presentation / Speaker Name / 7 World
Wide System Landscape
Slide 8
SAP AG 2005, Title of Presentation / Speaker Name / 8
Distributed Business Processes Business Processes depend not only
on internal but additionally on external services The IT-service
center is responsible for the whole process Order Process
Slide 9
SAP AG 2005, Title of Presentation / Speaker Name / 9
PartnerSAPCustomer Cascading of Help Desks Incident Analysis from
Customer Incident Analysis from Customer & SAP
Slide 10
SAP AG 2005, Title of Presentation / Speaker Name / 10 Industry
Standards Paper Sizes Character Encoding C, C++, C# Metrical System
HTML XML Web Service HTTP TCP/IP POP3 GSM UMTS Ethernet WiFi Public
Key Cryptography Standards Boost the Economic Growth !
Slide 11
Model: CIM The Need for Standards Why Standards are not Enough
Protocol: WS-Management The NetWeaver Administrator and its Partner
Strategy Process: ITIL API: JMX Introduction
Slide 12
SAP AG 2005, Title of Presentation / Speaker Name / 12 What is
ITIL? ITIL is a reference model for all processes of the management
of IT- services. The Information Technology Infrastructure Library
(ITIL) is a customizable framework of best practices for the IT
sector a comprehensive set of management procedures with which an
organization can manage its IT operations creates a common
vocabulary, consisting of its glossary of tightly defined terms
ITIL links the technical implementation and operations guidelines
and the strategic management, operational management and financial
management of a modern business
Slide 13
SAP AG 2005, Title of Presentation / Speaker Name / 13 ITIL as
a Standard ITIL is a De-Facto Standard ITIL is a series of books
published by the OGC (Office of Government Commerce), formerly CCTA
(Central Computer and Telecommunications Agency) ITIL is supported
by the British Standards Institution's standard for IT service
Management (BS15000).
Slide 14
SAP AG 2005, Title of Presentation / Speaker Name / 14
Advantages of ITIL 1.Make quality improvements measurable. ITIL
defines Key Performance Indicators (KPIs) 2.IT-Processes are
intentionally designed. They become flexible and transparent. 3.All
IT-Processes are aligned and consistent. 4.ITIL provides a
terminological standard. 5.Internal communication as well as the
communication to and from end-users and customers is integral part
of the it- processes. Increased customer satisfaction.
Slide 15
SAP AG 2005, Title of Presentation / Speaker Name / 15 Caveat!
Take Care: Bureaucracy and lack of individuality are general
disadvantages of ITIL principles. Therefore ITIL principles should
be adapted to fit within the organization with its specific
requirements and the application of ITIL principles should be
selective. No big bang introduction!
Slide 16
SAP AG 2005, Title of Presentation / Speaker Name / 16 ITIL
Sets 1.Service Delivery 2.Service Support 3.Planning to Implement
Service Management 4.Security Management 5.ICT Infrastructure
Management 6.The Business Perspective 7.Application Management
8.Software Asset Management ICT = Information & Communication
Technology
Slide 17
SAP AG 2005, Title of Presentation / Speaker Name / 17
Technology Business Planning of the Implementation of Service
Management ITIL Framework ICT Infrastructure Management (ICTIM)
Business Perspective Service Management Service Delivery Service
Support Application Management Security
Slide 18
SAP AG 2005, Title of Presentation / Speaker Name / 18
Management Problem Space Network OS/System Runtime Environment
Application Middleware Application ICT Infrastructure Management
(ITIL) DB, Web- server, etc Technical Process Business Process
Batch Job Print Job User Application Management (ITIL) Optimize
Service Support (ITIL) (Operational) (Problem/Change Mgmt) SAP
SupportCustomer DeployOperate Managed Elements Role Managed Element
Tasks Service Delivery (ITIL) (Tactical) (Service Level/
Availability Mgmt) IT Service Processes Misc Executes Supported by
Affect Implemented by Mgmt Support Tools Content Services
Monitoring Administration SW Lifecycle Mgmt influence Implemented
by
Slide 19
SAP AG 2005, Title of Presentation / Speaker Name / 19 Service
Delivery The Service Delivery is concerned with the pro-active
services that the business requires of its ICT provider in order to
provide adequate support to the business users. The discipline
consists of the following processes: Service Level Management
Capacity Management IT Service Continuity Management Availability
Management Financial Management
Slide 20
SAP AG 2005, Title of Presentation / Speaker Name / 20 Service
Delivery Service Level Management Availability Management Capacity
Management Finance Management Service Continuity Management CDB
(Capacity Data Base) Security Customer Requirements Goals Current
Status Alerts Exceptions Changes Management Tools & IT
Infrastructure
Slide 21
SAP AG 2005, Title of Presentation / Speaker Name / 21 Service
Level Management provides for continual identification, monitoring
and review of the levels of IT services specified in the Service
Level Agreements (SLAs). relies upon all the other areas of the
Service Delivery process to provide the necessary support which
ensures the agreed services are provided in a cost effective,
secure and efficient manner. Service Level Agreement (SLA) is a
formal written agreement made between two parties: the service
provider and the service recipient. contains clauses that define a
specified level of service, support options, incentive awards for
service levels exceeded and/or penalty provisions for services not
provided.
Slide 22
SAP AG 2005, Title of Presentation / Speaker Name / 22 Capacity
Management supports the optimal and cost effective provision of IT
services by helping organizations match their IT resources to the
business demands. The high level activities are: Application Sizing
Workload Management Demand Management Modeling Capacity Planning
Resource Management Performance Management.
Slide 23
SAP AG 2005, Title of Presentation / Speaker Name / 23 IT
Service Continuity Management IT Service Continuity Management
helps to ensure the availability and rapid restoration of IT
services in the event of a disaster. The high level activities are:
Risk Analysis Manage Contingency Plan Management Contingency Plan
Testing Risk Management.
Slide 24
SAP AG 2005, Title of Presentation / Speaker Name / 24
Availability Management Availability Management allows
organizations to sustain the IT service availability in order to
support the business at a justifiable cost. The high level
activities are: Realize Availability Requirements Compile
Availability Plan Monitor Availability Monitor Maintenance
Obligations.
Slide 25
SAP AG 2005, Title of Presentation / Speaker Name / 25
Financial Management for IT Financial Management for IT services
assesses the Total Cost Of Ownership. Costs are divided into
costing units: Equipment Software Organisation
Slide 26
SAP AG 2005, Title of Presentation / Speaker Name / 26 Service
Support The service support ensures that the customer has access to
the appropriate services to support the business functions. The
discipline consists of the following processes: Service Desk
Incident Management Problem Management Change Management Release
Management Configuration Management
Slide 27
SAP AG 2005, Title of Presentation / Speaker Name / 27 Service
Support Incident Management Problem Management Change Management
Configuration Management Service Desk (Function, no process)
Release Management CMDB (Configuration Management Data Base) User
Incidents Management Tools Updates, Workarounds Communication
Incidents Problems Known Errors RFCs Change Records ReleasesConfig
Items (CI) Relationships
Slide 28
SAP AG 2005, Title of Presentation / Speaker Name / 28 Service
Desk The Service Desk acts as the central point of contact between
service providers and users/customers. It is a central point for
reporting incidents and for users making service requests. The
Service Desk functions include: Receiving calls, first-line
customer support Recording and tracking incidents and complaints
Keeping customers informed on request status and progress Making an
initial assessment of requests, attempting to resolve them or refer
them to someone who can Monitoring and escalation procedures
relative to the appropriate SLAs Identifying problems Closing
incidents and confirmation with the customers Coordinating
second-line and third line support
Slide 29
SAP AG 2005, Title of Presentation / Speaker Name / 29 Incident
Management ITIL terminology defines an incident as: Any event which
is not part of the standard operation of a service and which
causes, or may cause, an interruption to, or a reduction in, the
quality of that service The first goal of the incident management
process is to restore a normal service operation as quickly as
possible and to minimize the impact on business operations. The
main incident management processes are the following: Incident
detection and recording Classification and initial support
Investigation and diagnosis Resolution and recovery Incident
closure Incident ownership, monitoring, tracking and
communication
Slide 30
SAP AG 2005, Title of Presentation / Speaker Name / 30 Problem
Management A `problem' is an unknown underlying cause of one or
more incidents. A `known error' is a problem that is successfully
diagnosed and for which a work-around has been identified. The goal
of Problem Management is to minimize the adverse impact of
incidents and problems on business that are caused by errors within
the IT infrastructure, and to prevent recurrence of incidents
related to these errors. Problem Management deals with resolving
the underlying cause of one or more Incidents. Activities are:
Problem identification and recording; Problem classification;
Problem investigation and diagnosis.
Slide 31
SAP AG 2005, Title of Presentation / Speaker Name / 31 Change
Management The goal of the Change Management process is to ensure
that standardized methods and procedures are used for efficient and
prompt handling of all changes, in order to minimize the impact of
change-related incidents upon service quality, and consequently
improve the day-to-day operations of the organization. The Change
Management process rules changes in. Hardware Software
Documentation The decision authority for all changes is the Change
Advisory Board (CAB).
Slide 32
SAP AG 2005, Title of Presentation / Speaker Name / 32 Release
Management Release Management is the process of distribution of
software and hardware. It ensures the availability of licensed,
tested, and version certified software and hardware, which will
function correctly. Activities: Design and implement procedures for
the distribution, installation and rollout of releases Coordinate
release communications, preparations and training activities
Provide management information about Release Management quality and
operations
Slide 33
SAP AG 2005, Title of Presentation / Speaker Name / 33
Configuration Management Configuration Management is a set of
processes that track all of the individual Configuration Items (CI)
in an IT infrastructure. Activities: Planning Identification
Control Status Accounting Verification and Audit Most organizations
use a Configuration Management Database (CMDB) to support the
Configuration Management. A CMDB is a unified or federated
repository of information related to all the CIs of the information
system.
Slide 34
SAP AG 2005, Title of Presentation / Speaker Name / 34 Planning
To Implement Service Management The ITIL discipline Planning To
Implement Service Management attempts to provide practitioners with
a framework for the alignment of business needs and IT provision
requirements. The guidelines suggest the development of a
Continuous Service Improvement Program (CSIP). It consists of the
following five steps: create vision analyze organization set goals
implement IT service management measure progress towards goals
using Key Performance Indicators (KPI)
Slide 35
SAP AG 2005, Title of Presentation / Speaker Name / 35 ICT
Infrastructure Management The Information and Communication
Technology (ICT) Infrastructure Management processes recommend best
practice for requirements analysis Planning Design Deployment
ongoing operations management technical support of an ICT
Infrastructure. The Infrastructure Management processes describe
those processes within ITIL that directly relate to the ICT
equipment and software that is involved in providing ICT services
to customers.
Slide 36
SAP AG 2005, Title of Presentation / Speaker Name / 36 (ICTIM
Process) Administration ICT Infrastructure Management (I) Design
and PlanningDeploymentOperations Obsolete Technical Support
Application Management Service Delivery Business CustomersUsers
Policy StrategyPlanProveDeployOperate Strategies, Plans and
Requirements Service Support Business Solution
Slide 37
SAP AG 2005, Title of Presentation / Speaker Name / 37 (ICTIM
Process) Administration ICT Infrastructure Management (II) Design
and PlanningDeploymentOperations Technical Support Business
CustomersUsers ObsoleteProve Policy StrategyPlanDeployOperate
RequirementsSolutions
Slide 38
SAP AG 2005, Title of Presentation / Speaker Name / 38
Application Management Application Management encompasses a set of
best practices proposed to improve the overall quality of IT
software development and support through the life-cycle of software
development projects. Application Management consists of the
following processes: Application Development Requirements Design
Implementation Service Management Deploy Operate Optimize
Slide 39
SAP AG 2005, Title of Presentation / Speaker Name / 39
Application Development PhasesService Management Phases Application
Management Deploy Requiremtents DesignBuildOperateOptimize Service
DeliveryService Support Assists and enablesManageability
Requirements
Slide 40
The Common Information Model (CIM) Authors: Gregor Frey,
Andreas Kppel
Slide 41
SAP AG 2005, Title of Presentation / Speaker Name / 41 Overview
Introduction Overview CIM/WBEM Basics Tools CIM Schema Core Model
Common Models
Slide 42
SAP AG 2005, Title of Presentation / Speaker Name / 42
Distributed Management Task Force Who is the DMTF ? founded in 1992
industry organization leading the development, adoption &
unification of management standards Their aim: reduce the expense
for the administration of IT systems Member companies 13 Board
Members 3Com, BMC, Cisco, (Compaq), Dell, HP, Tivoli (IBM), Intel,
Microsoft, NEC, Novell, Sun, Symantec voting members (all work
groups), asscociate members (one work group), academic members
(free membership) alliance members (The OpenGroup, ItSMF,...)
Organized in working groups
Slide 43
SAP AG 2005, Title of Presentation / Speaker Name / 43 WBEM
Goals Establish management infrastructure Provide a way to combine
information from different hard- & software management systems
Standardize information: how data is presented Process standard:
how components interact Solve problems of collecting end-to-end
management & diagnostic data in enterprise networks
Slide 44
SAP AG 2005, Title of Presentation / Speaker Name / 44 What is
Web Based Management? 1: using a Web Browser to look at management
data in management server 2: using a Web Browser to look at
management data directly 3: using Internet Technologies for
management Managed System Management Server Management Station
Managed System
Slide 45
SAP AG 2005, Title of Presentation / Speaker Name / 45 The WBEM
Standards (WBEM Triangle) Transport Encoding Transport Encoding
HTTP Access,Presentation CIM Data Description
Slide 46
SAP AG 2005, Title of Presentation / Speaker Name / 46 What is
CIM? Implementation neutral schema for the description of
management information Schemas that represent the real-world
objects being managed Facilitates the integration of management
information from different sources Data model not an implementation
Object-oriented model with relational aspects (keys)
Slide 47
SAP AG 2005, Title of Presentation / Speaker Name / 47 CIM
Schema Overview Core Model CIM Specification Meta-Schema CIM Schema
Syntax Rules Application Device Events Metrics Networks Physical
Policy Support System User Interoperability Common Models Database
Technology- and Vendor-specific extensions Extension Models
Slide 48
SAP AG 2005, Title of Presentation / Speaker Name / 48 Overview
Introduction Overview CIM/WBEM Basics Tools CIM Schema Core Model
Common Model
Slide 49
SAP AG 2005, Title of Presentation / Speaker Name / 49 WBEM
Implementation - General Architecture CIM Object Manager (CIMOM)
Method Other CIMOM ClassEvent Management Application Association
Managed Objects Instance CIM Repository Namespace static class
definitions (model) static instances WBEM Standard: CIMXML/CIM Ops
over HTTP Java: API/RMI MS: API/(D)COM MOF File via MOF compiler
Provider Client
Slide 50
SAP AG 2005, Title of Presentation / Speaker Name / 50 Managed
Objects WBEM Operation CIM Object Manager CIM Repository Event
Provider Management Application Other Providers Indications
(Events) Requests
Slide 51
SAP AG 2005, Title of Presentation / Speaker Name / 51 WBEM
Query Language (WQL) SQL dialect SELECT * FROM MyClass WHERE...
but: ASSOCIATORS OF {sourceobject} but: REFERENCES OF
{sourceobject} but:... where ISA baseclass 3 types of queries Data
query: retrieve instances Event query: event provider and consumer
registration Schema query: retrieve class definitions Executed by
CIMOM (providers may implement queries, too) Not yet standardized
but implemented New query language (CQL) is under way
SAP AG 2005, Title of Presentation / Speaker Name / 99
Application Architecture: Views and Elements System Processing
Elements Code Component Resource ActionData External System OS/
Host Logical Structure OS Data Flow Scenario Lifecycle Time:
shipping -> running Software Service Application View
Application Element
Slide 100
SAP AG 2005, Title of Presentation / Speaker Name / 100
Requirements for a Runtime Model Application Management
Requirements Manageability Requirements Meta Requirements
Architectural Requirements + Views & Elements Management
Abstraction Managed Objects Model Management Objects Managed Object
& Support Classes Granularity, Time-Relationship,...
Application Views/ Elements, Diversity, Complexity,...
Application-, Service Level-, Business Process Management,...
Managed Object & Support Classes Sub-Model & Managed Object
Class System Resource Usage, Dataflow, Report & Control State,
Exhibit Faults,
Slide 101
SAP AG 2005, Title of Presentation / Speaker Name / 101
Breaking Down the Model: Runtime Sub-Models
Slide 102
SAP AG 2005, Title of Presentation / Speaker Name / 102 Runtime
Overview SWF/ SWE Structure Application System Sub-Model Principal
Management Object Class Configuration Setting External System
System, Service, Resource, SWF/SWE Function Application Service
Resource UoW (Action) Data Event Indication inter- acts with
consists ofprovides performsdetermines dataflow emits applies
imple- ments Perfor- mance metrics Status Errors Metrics per
individual action Analysis Overview, Monitoring Statistics,
Summary, Aggre gations Runtime Model History Metrics, Statistics
stores behavior of the past Support Object Class CIM Class
Representing a Managed Object
Slide 103
SAP AG 2005, Title of Presentation / Speaker Name / 103 Schema
Resources www.dmtf.org/standards CIM @ DMTF: Schema Visios, MOFs
and whitepapers www.dmtf.org/education Tutorials and general
CIM-related documents http://ency.wdf.sap.corp:1080/CIM CIM @ SAP
\\dwdf050\ccms\Distributed_Management_Task_Force CIM @ CCMS
Slide 104
Java Management Extensions (JMX) Authors: Gregor Frey, Heiko
Kiessling
Slide 105
SAP AG 2005, Title of Presentation / Speaker Name / 105 What is
JMX? JMX is an infrastructure specification for managing business
applications, services and devices written in Java, and is divided
into Instrumentation level Agent level Distributed services level
JMX does not specify an object model, such as CIM JMX does not
include tool specifications JMX allows remote access through
separately defined management protocols
Slide 106
SAP AG 2005, Title of Presentation / Speaker Name / 106 JMX
Architecture Proprietary Management Application Proprietary
Management Application Web Browser Agent Level Distributed Services
Level Instrumentation Level JMX Manager Agent Services Mbean Server
PACC C Host 1Host 2 C Resource 1 (MBean) Resource 2 (MBean)
Slide 107
SAP AG 2005, Title of Presentation / Speaker Name / 107 MBeans
Managed Beans (MBeans) are proxies for managed objects such as
business applications, services and devices MBeans define At least
one constructor Getter and Setter methods Operations Notifications
MBeans are accessible through MBean Servers in a uniform fashion
but can be implemented in four different ways: Standard MBeans
Dynamic MBeans Open MBeans Model MBeans
Slide 108
SAP AG 2005, Title of Presentation / Speaker Name / 108
Standard MBeans Standard Mbeans have static interfaces named MBean
Getter methods are called get or is Setter methods are called set
Inheritance is taken into account MBean servers discover interfaces
through introspection AMBean AB implements extends
Slide 109
SAP AG 2005, Title of Presentation / Speaker Name / 109 Dynamic
MBeans Dynamic Mbeans have a specific interface DynamicMBean Info
method getMBeanInfo (no introspection possible) Getter method
getAttribute Setter method setAttribute Operation call method
invoke Applications: Wrappers Open MBeans Model MBeans Issues:
Coherence Dynamics
Slide 110
SAP AG 2005, Title of Presentation / Speaker Name / 110 Open
MBeans Open MBeans are Dynamic MBeans, and specified to be
discovered and used without prior knowledge of types Open MBeans
use predetermined types: Standard Types, such as Boolean, String
ObjectName CompositeData, equivalent to records TabularData, rows
of CompositeData queried by key Derivatives of the above Types are
revealed through Type info classes
Slide 111
SAP AG 2005, Title of Presentation / Speaker Name / 111 Model
MBeans Model MBeans are Dynamic MBeans which are configurable at
runtime through descriptors using field-value pairs There is a
reference implementation for Model MBeans
javax.management.modelmbean.RequiredModelMBean Model MBeans do
automatic attribute caching in attribute descriptors: Current
attribute values are taken from cache Attribute values are stale if
current time is past lastUpdateTimeStamp + currencyTimeLimit Model
MBeans do automatically send attribute change notifications: The
interface ModelMBeanNotificationBroadcaster supports listeners
interested in single attributes
Slide 112
SAP AG 2005, Title of Presentation / Speaker Name / 112
Notification Model Generic event class Notification open for
inheritance with Notification type as dynamic notification
namespace, similar to package namespace. Example:
jmx.mbean.registered Time stamp, sequence number, human-readable
message Interfaces: NotificationBroadcaster for notification
creators NotificationListener for objects interested in
notifications NotificationFilter for preselecting notifications on
behalf of listeners Special attribute change notification class:
AttributeChangeNotification with name, old and new values Special
AttributeChangeNotificationFilter with dynamically customizable
attribute preselection
Slide 113
SAP AG 2005, Title of Presentation / Speaker Name / 113 Agents
and the MBean Server In each Java VM with managed resources there
is at least one agent An agent consists of: An MBean Server Agent
services, e. g. dynamic loading A set of MBeans At least either one
connector or one protocol adaptor An MBean Server is An environment
for implementing monitoring policies A registry for Mbeans A single
entry point for calling MBeans in a uniform fashion from management
applications in other Java VMs
Slide 114
SAP AG 2005, Title of Presentation / Speaker Name / 114 The
MBean Server as registry MBeans are registered under an object name
An object name has the form: [ ] : = (, = )* Object names can
contain wildcards *, ?. Example: *:description=printer, type=laser,
* MBeans are (instantiated and) registered with object names which
have to be unique within one MBean Server MBeans can be queried
using An object name with wildcards, called the scope Additional
criteria referring to MBean attributes
Slide 115
SAP AG 2005, Title of Presentation / Speaker Name / 115
Monitoring Services A monitor observes an attribute of an Mbean,
the observed attribute, at intervals given as the granularity
period From this observation, a value is derived, the derived gauge
When the derived gauge satifies one of a set of conditions a
notification of the class MonitorNotification is issued When a
problem occurs, a notification is issued, e. g. of type
jmx.monitor.error.runtime There are three kinds of monitors:
CounterMonitor GaugeMonitor StringMonitor
Slide 116
SAP AG 2005, Title of Presentation / Speaker Name / 116 Counter
Monitor Observes integer attributes, which are equal to or larger
than zero and increasing A notification is issued whenever the
counter reaches or exceeds a threshold value An offset can be
specified, an appropriate multiple of which is added to the
threshold after issueing the notification Roll over is taken into
account using a modulus value Offset = 2 3 5 7 Event
Slide 117
SAP AG 2005, Title of Presentation / Speaker Name / 117 Gauge
Monitor Observes integer or float attributes, which are arbitrarily
increasing and decreasing A notification can be issued when the
gauge reaches or exceeds a high threshold value after having
reached or exceeded a low threshold value, and vice versa
(hysteresis) High Low Event
Slide 118
SAP AG 2005, Title of Presentation / Speaker Name / 118 String
Monitor Observes string attributes with respect to a reference
string, the string-to-compare If NotifyMatch is true then a
notification is sent when the string matches the string-to-compare
again for the first time If NotifyDiffer is true then a
notification is sent when the string differs from the
string-to-compare again for the first time XYZ ABC GHI DEF XYZ
Event String-to-compare = XYZ NotifyMatch = true NotifyDiffer =
false
Slide 119
SAP AG 2005, Title of Presentation / Speaker Name / 119 Timer
Service A timer is an instance of the class Timer A timer triggers
notifications of the special class TimerNotification at specific
dates and times, with the type given when calling the method
addNotification Notifications can be periodic with an optional
number of occurences All listeners to a timer receive all
notifications A timer can be started and stopped, and accumulated
notifications discarded or sent
Slide 120
SAP AG 2005, Title of Presentation / Speaker Name / 120
Relation Service The relation service supports associations among
MBeans with named roles and cardinality Consistent cardinality is
monitored when un-registrating MBeans, and inconsistent relations
are discarded Relations can be queried: Retrieval of relations
where a given MBean takes a specific role with the method
findReferencingRelations Retrieval of MBeans associated with a
given MBean with the method findAssociatedMBeans Library OwnerBook
PersonBook JMX Model UML Model Library 1..10..n 1..10..n Relation
Person Book OwnerBook
Slide 121
J2EE Management Authors: Gregor Frey
Slide 122
SAP AG 2005, Title of Presentation / Speaker Name / 122
Overview of relevant JSRs JSR 3: Java TM Management Extensions (JMX
TM ) SpecificationJava TM Management Extensions (JMX TM )
Specification provides a management architecture, APIs and services
for building Web-based, distributed, dynamic and modular solutions
to manage Java enabled resources. JSR 77: J2EE TM ManagementJ2EE TM
Management provides server vendors and tool vendors with a standard
model for managing the J2EE Platform. JSR 151: Java TM 2 Platform,
Enterprise Edition 1.4 (J2EE 1.4) SpecificationJava TM 2 Platform,
Enterprise Edition 1.4 (J2EE 1.4) Specification the current release
of the Java 2 Platform, Enterprise Edition. JSR 160: Java TM
Management Extensions (JMX) 1.5 SpecificationJava TM Management
Extensions (JMX) 1.5 Specification provides a standardized API for
remote connection
Slide 123
SAP AG 2005, Title of Presentation / Speaker Name / 123
J2EE-Management Support for J2EE-Management as defined by the JSR
77 is required by J2EE 1.4. The idea of the J2EE management
specification is to define an abstract management model, which can
be easily adapted to any management protocol. With JSR 77 the
following management topics are covered: discovery and navigation
between managed objects, notification of events on managed objects,
management of the running state monitoring of performance data For
the access of this information model an API is specified. This is
the so-called J2EE Management EJB Component, or MEJB for
short.
Slide 124
SAP AG 2005, Title of Presentation / Speaker Name / 124 JMX and
J2EE Management JMX and J2EE Management can be seen as
complementary specifications: JSR 77 defines a semantical model JSR
3 defines an implemtation technology and API There is an overlap
between JSR 77 and JSR 160: both define a similar API for accessing
a MBeanServer remotely: the MEJB and the MBeanServerConnection.
With J2SE 1.5 JMX and the remote infrastructure defined by JSR 160
are available in every compliant JVM.
Slide 125
SAP AG 2005, Title of Presentation / Speaker Name / 125
Hierarchy of Managed Objects
Slide 126
SAP AG 2005, Title of Presentation / Speaker Name / 126 Object
Names Structure of JMX Object Names: An JMX Object Name consists of
two parts: A domain name An unordered set of one or more key
properties [domainName]:property=value[,property=value]* The
ObjectName of a J2EEManagedObject contains predefined, required
properties to identify uniquely each managed object Place it within
the hierarchy of the J2EE management domain j2eeType: specifies the
subclass of of J2EEManagedObject name: identifies the instance of
the managed object parent properties: have the form type=name where
type is the j2eeType and name the name of the parent object
Slide 127
SAP AG 2005, Title of Presentation / Speaker Name / 127
Examples of ObjectNames in JSR77 Domains are J2EEManagedObjects
FirstEverBank: j2eeType=J2EEDomain, name=FirstEverBank
J2EEApplication FirstEverBank: j2eeType=J2EEApplication,
name=AccountsController, J2EEServer=BankServer1 J2EEModule
FirstEverBank: j2eeType=EJBModule, name=BankAccount,
J2EEApplication=AccountsController, J2EEServer=BankServer1
Slide 128
SAP AG 2005, Title of Presentation / Speaker Name / 128 JSR 77
Statistics JSR 77 Statistics provide performance data for Managed
Objects. A Managed Object may provide a list of performance
attributes, according to a corresponding Stats interface. The data
types for the performance attributes have to implement one of the
Statistic interfaces.
Slide 129
SAP AG 2005, Title of Presentation / Speaker Name / 129 Example
from the Statistic Model EJB is a ManagedObject, which is a
StatisticProvider. It returns true on calls to isStateManageable().
The call to getStats() returns an EJBStats object. This Stats
objects lists the performance attributes. These are: createCount,
and removeCount. Both of the listed performance attributes are of
type CountStatistic.
Slide 130
WS-Management (WS-Man) Authors: Gregor Frey, Fabrizio
Muscarella
SAP AG 2005, Title of Presentation / Speaker Name / 132
Introduction: What is WS-Management? WS-Management defines a
SOAP-based protocol for Systems Management Is a profile a
collection of references to other composable specs: WS-Addressing,
WS-Eventing, WS-Transfer and WS- Enumeration Specifies extensions
to and restricts how these protocols can be used Designed to scale
down to small-devices Defined over existing standards HTTP/S,
TCP/IP, TLS, XML, URI, SOAP Designed to be Information
Model-agnostic - compatible with the CIM Object Model
Slide 133
SAP AG 2005, Title of Presentation / Speaker Name / 133
WS-Management Requirements Constrain Web services protocols and
formats to allow small-footprint implementations in both hardware
and software Define minimum requirements for compliance without
constraining richer implementations Ensure composability with other
Web services specifications Minimize additional mechanism beyond
the current Web services architecture
SAP AG 2005, Title of Presentation / Speaker Name / 135
WS-Management: Architecture SOAP, HTTP, UDP, etc. WS-Transfer, WS-
Enumeration, WS-Eventing WS-Management WS-Addressing Systems
Management Expose a common set of operations, central to all
systems management (DISCOVER,GET,PUT,CREATE,RENA
ME,DELETE,ENUMERATE,SUBSCRI BE,EXECUTE). Contrain WS protocols,to
be implemented with a small footprint. Define minimum requirement.
Ensure composability. Minimize additional mechanism beyound the WS
architecture.
Slide 136
SAP AG 2005, Title of Presentation / Speaker Name / 136
WS-Management: Architecture (2) * MTOM: SOAP Message Transmission
Optimization Mechanism
Slide 137
SAP AG 2005, Title of Presentation / Speaker Name / 137
WS-Management Operations Typical systems management operations
Discover the presence of manageable resources Get, Update and
Delete properties of managed resources Create references to
manageable resources Enumerate the contents of containers and
collections such as large tables and logs Subscribe to events
emitted by managed resources Execute specific management
methods
SAP AG 2005, Title of Presentation / Speaker Name / 139
WS-Transfer Methods defined by WS-Transfer Get Put Create Delete
ClientAgent 1 2
Slide 140
SAP AG 2005, Title of Presentation / Speaker Name / 140
WS-Transfer (2) Provides a SOAP-based protocol for managing
resources and their representations Resource Operations Get fetch a
one-time snapshot of resource representation Put update a resource
by providing a replacement representation Delete Resource Factory
Operations Create returns Endpoint Reference of created
resource
SAP AG 2005, Title of Presentation / Speaker Name / 142
WS-Enumeration Supports enumeration of data sources that cannot
practically fit into a single SOAP message State can be maintained
by source or consumer No commitment on order or completeness
Operation to get an enumeration context Enumerate initiate
enumeration, return context Operation to fetch items from the
enumeration Pull gets one or more items contains context, may
contain MaxElements, MaxCharacters Operation to abandon an
enumeration Release Operation to manage enumeration lifetimes
Renew, GetStatus, EnumerationEnd
Slide 143
SAP AG 2005, Title of Presentation / Speaker Name / 143
WS-Enumeration (2) : Enumerating Data Same as base specification
WS-man allows using partial results Enumerate EnumerateResponse
(Context) Pull(3) PullResponse Pull(4) PullResponse Release
ReleaseResponse Client Agent Item Collection
SAP AG 2005, Title of Presentation / Speaker Name / 145
WS-Eventing Create, delete and renew event subscriptions Features
extensible event filtering Event delivery mode is extensible Event
source operations Subscribe creates a subscription and returns an
EPR for a service that manages the new subscription Subscription
manager operations Renew to extend a subscription Unsubscribe to
cancel a subscription GetStatus to check whether subscription is
still valid SubscriptionEnd notifies subscriber of unexpected
cancellation Push Event Delivery included
Slide 146
SAP AG 2005, Title of Presentation / Speaker Name / 146
WS-Eventing (2) Bookmarks Optional capability for Log-backed
subscriptions Bookmark is included with each event delivery
Service-defined cursor in the event stream Opaque to the client
Allows a later restart where the subscription left off
Slide 147
SAP AG 2005, Title of Presentation / Speaker Name / 147
WS-Eventing (3): Extension Event delivery mode Batched Grouped
event delivery Pull Event polling based on WS-Enumeration Trap
(Multicast) Asynchronous delivery using UDP multicast for small
messages Expiration expressed in duration (no requirement for
absolute time) Resume-able subscriptions Pick up where I left
off
Slide 148
SAP AG 2005, Title of Presentation / Speaker Name / 148
WS-Eventing (4) Defined by WS-Eventing Subscribe Push Defined by
WS-Management Extension PushWithAck (Ext) Batched (Ext) Pull (Ext)
Subscribe Group Policy Deliver Management Console Server Get
SAP AG 2005, Title of Presentation / Speaker Name / 150
Catalog: Features Lists the available ResourceURIs Provides
searchable metadata (Keywords) Provides relationships to external
and internal resources (eg Web URLs) Describes supported actions
for each resource Can provide the complete WSDL for a resource
using WS- Transfer:Get Can provide the XML Schema for a resource
using WS-Transfer:Get
Slide 151
SAP AG 2005, Title of Presentation / Speaker Name / 151
Catalog: Resource Discovery
SAP AG 2005, Title of Presentation / Speaker Name / 153
Security WS-Management supports multiple security models
Transport-level small footprint well established available
off-the-shelf components examples: HTTPS, SSL/TLS, SSH
Message-based flexible supports complex security models and
technologies composed using WS-Security Implementations can choose
even mix
Slide 154
SAP AG 2005, Title of Presentation / Speaker Name / 154
Supporting technologies CIM Schema Mapping Mechanical transform
from MOF to XSD Conversion of CIM types to XSD types Can be
performed at design time for embedded hardware Can be generated at
runtime on large systems Discovery Catalog A Catalog of references
to manageable resources References can be Local or Distributed
Resources can be instances or class types Supports Enumeration and
Transfer for simple and filtered enumeration of resources Provides
WBEM CIMOM functionality
Slide 155
SAP AG 2005, Title of Presentation / Speaker Name / 155 Some
benefits of using WS-Management Based on the Web Service
infrastructure Platform independence Same toolset for software
development and management Common management protocol for the
entire stack Hardware OS Applications Services
SAP AG 2005, Title of Presentation / Speaker Name / 157 1. 2.
3. http://sap_server/wsman 4. wsman://../Processor 5.
http://schemas.xmlsoap.org/ws/2004/09/transfer/Get 6. 7. CPU0 8. 9.
http://schemas.xmlsoap.org//addressing/role/anonymous 10.
uuid:91c167fb-2c3a-4F1A-8d59-01b0c18a0723 11. 12. 13. WS-Transfer
Get Manager Get GetResponse 1. 2. 3.
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonimous 4.
http://schemas.xmlsoap.org/ws/2004/09/transfer/GetResponse 5.
uuid:91c167fb-2c3a-4F1A-8d59-01b0c18a0723 6. 7. DATA 8. 1. 2. 165
3. CPU0 4. Intel Xeon (TR) 5. 3000 6. 3000 7. 32 8. 32 9. 2 10. 5
11.
Slide 158
SAP AG 2005, Title of Presentation / Speaker Name / 158
Example: Enumeration Manager Enumerate
http://134.134.201.169/agent?ResourceURI=(wsman:./PhysicalElements)
http://schemas.xmlsoap.org/ws/2004/09/enumeration/Enumerate
uuid:1778973d-10e9-477D-ae07-34e424e6577a
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
expiry time
Slide 159
SAP AG 2005, Title of Presentation / Speaker Name / 159
Example: Enumeration response
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
http://schemas.xmlsoap.org/ws/2004/09/enumeration/EnumerateResponse
uuid:1778973d-10e9-477D-ae07-34e424e6577a
uuid:dc0eeb8f-d025-4A45-a859-2b4ca640a1ff abcd123f
Slide 160
SAP AG 2005, Title of Presentation / Speaker Name / 160
Example: Enumeration (Pull) Manager Pull
http://134.134.201.169/agent?ResourceURI=(wsman:./PhysicalElements)
http://schemas.xmlsoap.org/ws/2004/09/enumeration/Pull
uuid:9180bb55-9f9d-4808-93ca-72a6e922105a
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
abcd123f 5
Slide 161
SAP AG 2005, Title of Presentation / Speaker Name / 161
Example: Enumeration (Pull Response) Manager New Server (no OS
present) 134.134.201.169 EnumerateResponse
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
http://schemas.xmlsoap.org/ws/2004/09/enumeration/PullResponse
uuid:9180bb55-9f9d-4808-93ca-72a6e922105a
uuid:6500bf62-72e6-4468-8c2d-cd969ed0bd56 1122eeff Data
Slide 162
SAP AG 2005, Title of Presentation / Speaker Name / 162
Example: XML-Schema [CIM Mapping] 406BigBlobMem-08K8198 Physical
Memory (DDR memory) DDR memory BigBlobMem Inc. DDR memory, The Big
Blob 99000ababab 756568432 1.0 True Jan 30, 2005 DDR, Blob
True
Slide 163
SAP AG 2005, Title of Presentation / Speaker Name / 163
WS-Eventing 1. 2. 3. http://sap_server/wsman 4.
wsman-sap://../AlarmEvents 5.
http://schemas.xmlsoap.org/../Subscribe 6.
http://schemas.xmlsoap.org//addressing/role/anonymous 7.
uuid:91c167fb-2c3a-4F1A-8d59-01b0c18a0723 8. 9. 10. 11. 12.
http://management_console/AlarmAssignedHandler 13. 14. 15. 16. http
://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
http://schemas.xmlsoap.org//SubscribeResponse
uuid:91c167fb-2c3a-4F1A-8d59-01b0c18a0723
uuid:bb254be0-a26e-4FC7-8ef1-9a99ef26eaa7 3456 P0Y0M0DT30H0M0S
http://management_console/AlarmAssignedHandler
http://www.sap.com/ws/2004/01/eventing/Alarm
uuid:b9b52b85-fc14-413C-a9b8-d729ee9e99aa P0Y0M0DT24H0M0S Crash
Subscribe Response Event
Slide 164
SAP AG 2005, Title of Presentation / Speaker Name / 164 Open
Source Implementations OpenWSMan: C/C++ implementation sponsored by
Intel(http://openwsman.org/)http://openwsman.org/ Wiseman : Java
implementation sponsored by Sun
(https://wiseman.dev.java.net/)
Slide 165
SAPs Integration Strategy for Operations Partners Strategy
Paper Gregor Frey, Director Operations Infrastructure
Slide 166
SAP AG 2005, Title of Presentation / Speaker Name / 166 Message
SAP welcomes the emerging interest in industry standards in the
field of IT-management. The new technology-wave of service oriented
architecture (SOA) reinforces the need of a unifying platform for
system and service management. Together with its partners SAP wants
to drive the development, alignment and adoption of the relevant
industry standards, to allow for a plug-and-manage of
IT-components.
Slide 167
SAP AG 2005, Title of Presentation / Speaker Name / 167
Standards CIM, WS-Man, and JMX are orthogonal standards Together
they ensure full interoperability: Plug-and-Manage Information
Model Protocol Instrumentation CIM WS-Man JMX TopicStandard
(adopted by SAP) Standard Body Information ModelCommon Information
Model (CIM) DMTF ProtocolWS-Management (WS-Man)DMTF
InstrumentationJava Management Extensions (JMX) JCP
Slide 168
SAP AG 2005, Title of Presentation / Speaker Name / 168
Interconnection of JMX, CIM & WS-M For a Management Application
a MBeanServer looks like a lightweight CIM-OM Management
Application WS-Man JMX-WSM Adapter MBeanServer CIM-WSM Adapter
CIM-OM
Slide 169
SAP AG 2005, Title of Presentation / Speaker Name / 169
EndpointReferences, ObjectNames, CIM-Classes JMX ObjectNameCIM
Class is Instance of WS-Man EndpointReference refers toaddresses
class CIM_J2eeApplication : CIM_ApplicationSystem { string Name;
string DeploymentDescriptor; } :CIMClass= CIM_J2eeApplication,
Name=Petstore, CreationClassName=CIM_J2eeApplication
http://myMbeanServer
http://schemas.dmtf.org/wsman/2005/06/cimv2.9/CIM_J2EEApplication
Petstore CIM_J2eeApplication
Slide 170
SAP AG 2005, Title of Presentation / Speaker Name / 170 Mapping
of DataTypes: CIM-Class, XSD-Type, MBean [Version ( "2.8.0" ),
Description ( "CIM_J2eeApplication identifies a J2EE application
that resides " "on a J2ee Server.")] class CIM_J2eeApplication :
CIM_ApplicationSystem { [Override ( "Name" ), Description ( "The
name of a J2EE Application. The name MUST be " "constructed using
the form specified in JSR77.3.1.1.1 in " "order to avoid the need
for manual key propagation."), MaxLen ( 256 ), MappingStrings {
"JSR77.JCP|JSR77.3.1.1.1 objectName|V1.0" }] string Name;
[Description ( "Contains the original XML deployment descriptor
that was " "created for this application during the deployment
process."), MappingStrings { "JSR77.JCP|JSR77.3.5.0.1 "
"deploymentDescriptor|V1.0" }] string DeploymentDescriptor; };
public class CIM_J2eeApplicationMBean extends
CIM_ApplicationSystemMBean { public String Name; public String
DeploymentDescriptor; } CIM_J2eeApplication CIM_ApplicationSystem
CIM-Class XSD-Type MBean
Slide 171
SAP AG 2005, Title of Presentation / Speaker Name / 171 SAPs
Partner Philosophy Unobtrusiveness Whatever tools and processes a
customer prefers to administrate his IT-landscape, the management
and monitoring of SAP-software must be possible from within this
environment. Completeness To operate his SAP-software a customer is
not required to buy and run any other management application then
the operation tools provided by SAP.
Slide 172
SAP AG 2005, Title of Presentation / Speaker Name / 172
Plug-And-Manage Data bus Give and take of management data Chain of
services provided on top of this data Incidents Monitors Landscape
Reports Configuration SUN Storages MS OMAmberpoint HP OV
Discovery
Slide 173
SAP AG 2005, Title of Presentation / Speaker Name / 173 Use
Cases Outbound: Providing NW data into 3rd party management
applications A partner wants to see the SAP monitoring data in his
management application (MS MOM, HP OpenView, IBM Tivoli, CA
Unicenter) and wants to manage SAP systems from within this
applications. Depending on the setup of the management solution at
the customer side, the partner application is used additionally to
the NWAdmin or it aims to substitute the NWAdmin completely.
Inbound: Integration of 3rd party resources into NWA A partner
wants his own resources to be managed and monitored by the SAP
NWAdmin. Examples: Http-Load-Balancer (Cisco), Storage Devices
(SUN), Chipset (Intel), OS (MS). A user might want to see the
status of the device, to start or stop it, analyze the logs, get
info about the load The data should be includable in overall
reports and guided operations should be definable for it
Slide 174
SAP AG 2005, Title of Presentation / Speaker Name / 174
NetWeaver NW-Integration Points for SOA-Management Partners NWAdmin
UI NWAdmin Data Provisioning NWAdmin Local Agent NW Managed
Resource ISV Tool ISV Resource WS-Man central local Outbound
Inbound