The Role of Industry Standards for the Administration of Global System Landscapes - PowerPoint PPT Presentation

Loading...

PPT – The Role of Industry Standards for the Administration of Global System Landscapes PowerPoint presentation | free to download - id: 1840d7-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

The Role of Industry Standards for the Administration of Global System Landscapes

Description:

The Role of Industry Standards for the Administration of ... Chipset. Appliance. Network Accelerator. SAP AG 2005, Title of Presentation / Speaker Name / 7 ... – PowerPoint PPT presentation

Number of Views:24
Avg rating:3.0/5.0
Slides: 48
Provided by: d357
Learn more at: http://www.minet.uni-jena.de
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: The Role of Industry Standards for the Administration of Global System Landscapes


1
The Role of Industry Standards for the
Administration of Global System Landscapes
  • Dr. Gregor Karl FreySAP, NW Operations
    Infrastructure

2
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
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 800
    AM to 500 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)

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

5
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
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

7
World Wide System Landscape
8
Distributed Business Processes
Order Process
  • Business Processes depend not only on internal
    but additionally on external services
  • The IT-service center is responsible for the
    whole process

9
Cascading of Help Desks
Partner
SAP
Customer
Incident
Incident
Incident
AnalysisfromCustomer
AnalysisfromCustomer SAP
10
Industry Standards
  • Metrical System
  • Paper Sizes
  • Character Encoding
  • C, C, C
  • HTML
  • XML
  • Web Service

Standards Boost the Economic Growth !
  • HTTP
  • TCP/IP
  • POP3
  • Ethernet
  • WiFi
  • Public Key Cryptography
  • GSM
  • UMTS

11
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
12
What is ITIL?
  • ITIL
  • is a reference model for all management
    processes of IT-services.
  • creates a common vocabulary for describing
    IT-services, consisting of its glossary of
    tightly defined terms
  • is a series of books published by the OGC
    (Office of Government Commerce), formerly CCTA
    (Central Computer and Telecommunications Agency)
  • is supported by the British Standards
    Institution for IT service Management (BS15000)

13
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.

14
ITIL Framework
Planning of the Implementation of Service
Management
ICT Infrastructure Management (ICTIM)
Business Perspective
Service Management
Service Support
Technology
Business
Service Delivery
Security
Application Management
15
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

16
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

17
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
18
What is CIM?
  • CIM is
  • an implementation neutral model for the
    description of management information
  • defines schemas of managed objects in the real
    world
  • facilitates the integration of management
    information from different sources
  • object-oriented model with relational aspects
    (keys)

19
CIM Schema Overview
Technology- and Vendor-specific extensions
Extension Models
Metrics
Networks
Physical
Policy
Support
System
User
Interoperability
Database
Application
Device
Events
Common Models
Core Model
CIM Schema
Syntax Rules
Meta-Schema
CIM Specification
20
CIM Meta-Model
  • CIM objects are instances of classes
  • CIM objects possess a key (single or multi-valued)

21
J2EE Application Server Model
J2EE_Servlet
Service
J2EE_EJB
System
J2EE_ResourcesOnServer

J2EE_Resource
J2EE_DeployedObject
1
(Abstract)

J2EE_Server
DeploymentDescriptor string
J2EE_DeployedObjectsOnServer
Vendor string
Version string
1

0..1
1
1
J2EE_ModulesOnServer
J2EE_Module

J2EE_ServerProcesses
J2EE_ServiceComponent
1..n
1
J2EE_Application
Process

J2EE_AppsOnServer
22
Database Model
  • Based on RFC 1697 (RDBMS MIB)

23
MOF Example
Qualifiers
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.JCPJSR77.3.1.1.1 objectNameV1.0"
string Name Description (
"Contains the original XML deployment descriptor
that was " "created for this
application during the deployment process."),
MappingStrings "JSR77.JCPJSR77.3.5.0.1 "
"deploymentDescriptorV1.0" string
DeploymentDescriptor
Class Name
Properties
24
Visio
  • Demo

25
WMI CIM Studio
Demo
26
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
27
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

28
JMX Architecture
Proprietary Management Application
Proprietary Management Application
Web Browser
Distributed Services Level
JMX Manager
Agent Level
Mbean Server
Agent Services
Resource 1 (MBean)
Instrumentation Level
Resource 2 (MBean)
Host 1
Host 2
29
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

30
Example for a MBean
  • public interface LoadStatisticsMBean
  • public int getNumberOfUsers()
  • public int getNumberOfRequests()
  • public double getAverageRequestTime()
  • public long getAverageSessionSize()
  • public class LoadStatistics implements
    LoadStatisticsMBean
  • public int getNumberOfUsers()
  • return numberOfUsers
  • public int getNumberOfRequests()
  • return numberOfRequests
  • public double getAverageRequestTime()
  • return averageRequestTime
  • public long getAverageSessionSize()
  • return averageSessionSize

31
The MBean Server
  • MBeans are registered under an object name
  • An object name has the formltdomain
    namegtltpropertygtltvaluegt (,ltpropertygtltvaluegt)
  • Object names can contain wildcards , ?.Example
    descriptionprinter, typelaser,
  • 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

32
Example Registration with MBeanServer
  • MBeanServer mbs ManagementFactory.getPlatformMBe
    anServer()
  • ObjectName name1 new ObjectName("example1typeL
    oadStatistics")
  • LoadStatistics load new LoadStatistics()
  • mbs.registerMBean(load, name1)

Demo Start Eclipse Start JConsole
33
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
34
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

35
WS-Management Architecture (2)
MTOM SOAP Message Transmission Optimization
Mechanism
36
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

37
WS-Transfer Get
Get
Get Response
  1. ltCIM_Processorgt
  2. ltFamilygt165lt/Familygt
  3. ltDeviceIDgtCPU0lt/DeviceIDgt
  4. ltOtherFamilyDescriptorgtIntel Xeon
    (TR)lt/OtherFamilyDescriptorgt
  5. ltMaxClockSpeedgt3000lt/MaxClockSpeedgt
  6. ltCurrentClockSpeedgt3000lt/CurrentClockSpeedgt
  7. ltDataWithgt32lt/DataWithgt
  8. ltAddressWithgt32lt/AddressWithgt
  9. ltLoadPercentagegt2lt/LoadPercentagegt
  10. ltSteppinggt5lt/Steppinggt
  11. lt/CIM_Processorgt
  1. ltEnvelopegt
  2. ltHeadergt
  3. ltTogthttp//sap_server/wsmanlt/Togt
  4. ltResourceURIgtwsman//../Processorlt/Resourc
    eURIgt
  5. ltActiongthttp//schemas.xmlsoap.org/ws/2004/0
    9/transfer/Getlt/Actiongt
  6. ltSelectorSetgt
  7. ltSelector NameDeviceIDgtCPU0lt/Selectorgt
  8. lt/SelectorSetgt
  9. ltReplyTogthttp//schemas.xmlsoap.org//addres
    sing/role/anonymouslt/ReplyTogt
  10. ltMessageIDgtuuid91c167fb-2c3a-4F1A-8d59-01b0
    c18a0723lt/MessageIDgt
  11. lt/Headergt
  12. ltBodygt lt/Bodygt
  13. lt/Envelopegt
  1. ltEnvelopegt
  2. ltHeadergt
  3. ltTogthttp//schemas.xmlsoap.org/ws/2004/08/ad
    dressing/role/anonimouslt/Togt
  4. ltActiongthttp//schemas.xmlsoap.org/ws/2004/0
    9/transfer/GetResponselt/Actiongt
  5. ltRelatesTogtuuid91c167fb-2c3a-4F1A-8d59-01b0
    c18a0723lt/RelatesTogt
  6. lt/Headergt
  7. ltBodygt DATAlt/Bodygt
  8. lt/Envelopegt

38
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
39
Standards
Topic Standard(adopted by SAP) StandardBody
Information Model Common Information Model (CIM) DMTF
Protocol WS-Management (WS-Man) DMTF
Instrumentation Java Management Extensions (JMX) JCP
  • CIM, WS-Man, and JMX are orthogonal standards
  • Together they ensure full interoperability
    Plug-and-Manage

CIM
WS-Man
Information Model
Protocol
JMX
Instrumentation
40
Interconnection of JMX, CIM WS-M
  • For a Management Applicationa MBeanServer
    looks likea lightweight CIM-OM

Management Application
WS-Man
WS-Man
41
EndpointReferences, ObjectNames, CIM-Classes
WS-ManEndpointReference
ltwsatogthttp//myMbeanServerlt/wsatogt ltwsmResourc
eURIgt http//schemas.dmtf.org/wsman/2005/06/ci
mv2.9/CIM_J2EEApplication lt/ wsmResourceURIgt ltwsm
SelectorSetgt ltwsmSelector
NameNamegtPetstorelt/wsmSelectorgt
ltwsmSelector NameCreationClassNamegt
CIM_J2eeApplication lt/wsmSelectorgt lt/wsmSele
ctorSetgt
refers to
addresses
JMX ObjectName
CIM Class
class CIM_J2eeApplication CIM_ApplicationSystem
string Name string DeploymentDescriptor
CIMClass CIM_J2eeApplication, NamePetstore, Cre
ationClassNameCIM_J2eeApplication
is Instance of
42
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.JCPJSR77.3.1.1.1
    objectNameV1.0"
  • string Name
  • Description (
  • "Contains the original XML deployment
    descriptor that was "
  • "created for this application during
    the deployment process."),
  • MappingStrings "JSR77.JCPJSR77.3.5.0.1
    "
  • "deploymentDescriptorV1.0"
  • string DeploymentDescriptor

ltxscomplexType name" CIM_J2eeApplication_Type"gt
ltxsannotationgt ltxsappinfogt
ltcimClassgtCIM_J2eeApplicationlt/cimClassgt
ltcimSuperclassgt CIM_ApplicationSystemlt/cimSuperc
lassgt lt/xsappinfogt lt/xsannotationgt
ltxssequencegt ltxselement name"Name"
type"xsstring"/gt ltxselement
nameDeploymentDescriptor" type"xsstring"/gt
lt/xssequencegt lt/xscomplexTypegt
XSD-Type
public class CIM_J2eeApplicationMBean extends
CIM_ApplicationSystemMBean public String
Name public String DeploymentDescriptor
CIM-Class
MBean
43
Introduction
The Need for Standards
Process ITIL
Model CIM
API JMX
Protocol WS-Management
Why Standards are not Enough
The NetWeaver Administrator and its Partner
Strategy
44
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.

45
Plug-And-Manage Data bus
Discovery
Incidents
Monitors
Landscape
Reports
Configuration
SUNStorages
MS OM
Amberpoint
HP OV
  • Give and take of management data
  • Chain of services provided on top of this data

46
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

47
NW-Integration Points for SOA-Management Partners
NetWeaver
NWAdmin UI
central
ISVTool
WS-Man
NWAdmin Data Provisioning
Outbound
central
ISVResource
WS-Man
NWAdmin Local Agent
Inbound
local
NW Managed Resource
local
About PowerShow.com