Adaptive Computing Technical Overview

Slides:



Advertisements
Similar presentations
Copyright 2009 SAP All rights reserved
Advertisements

Data Consistency in SAP BW Know How Network Conference Call May 29 th 2003 Mike Eacrett BW RIG, SAP Labs, LLC.
Rapid database migration to Sybase Adaptive Server Enterprise
SYSTEMATIC THOUGHT LEADERSHIP FOR INNOVATIVE BUSINESS SAP Research and FP7-SEC Skills and know-how Cedric Ulmer, Senior Researcher SAP Research.
Knowledge, Action, and Context Uwe Riss SAP Research, Karlsruhe.
Definition Usage Target Group Availability Benefits More info Cost
SAP Organization Change Management (OCM) Toolkit
Mutatis Mutandis Evaluating DBMS Test Adequacy with Mutation Testing Ivan T. Bowman, HANA Product Engineering June 24, 2013 Public.
Best Run Global Purchasing Training Documentation: Hubwoo (SRM) Merchandise Catalog Order Process GPO Commodity Marketing April, 2013.
Six Reasons Why Customers Chose BC Sets for Global Rollouts
Web SAP Peter McNulty, SAP Labs, LLC Sam Tingleff, SAP Labs, LLC Sinisa Zimek, SAP Labs, LLC.
Talent Management with SuccessFactors Erwin F. Schoellkopf / Regional Sales Manager June 11, 2013.
Jens Lemcke Research Associate, SAP AG Co-Authors: Michael Altenhofen, Egon Börger An Execution Semantics for Mediation Patterns.
Keith Harmon Solution Manager, SAP AG Transforming Information into Knowledge Bergen, Norway May 10-13, 2006.
Gunther Stuhec SAP AG Container Ship.  SAP AG 2003, Title of Presentation, Speaker Name / 2 What kind of containers exists in Modeling? 1/3 1. Generic.
CRM Analytics Architecture
University Logo Introduction to SAP and the UA Tom Wilder, Department of Accounting and MIS California State University, Chico October 14, 2009.
The Way to new ERP Horizons Matthias Kaiser, Ph.D. Sr. Research Scientist SAP Research From Monoliths to Molecules and how they all can make Humpty-Dumpty.
SAP Codepage Conversion Check Convert From an EBCDIC to an ASCII Codepage Successfully Service and Support Product Management SAP AG.
WS-I BP1.0 Recommendations On WSDL1.1 Kevin Liu October 2003.
Mail Interface with SMTP PlugIn in SAP WAS Based Components Parlin Sitanggang.
Baseline Package: Organizational Structure (J02) Overview SAP AG.
Multiple Components in One Database (MCOD) Dr. Georg Leffers SAP AG.
Multiple Components in One Database (MCOD)
Multiple Components in One Database (MCOD) Dr. Georg Leffers SAP AG.
SAP Exchange Infrastructure
Presentation transcript:

Adaptive Computing Technical Overview

Adaptive Computing Technical Overview General information Building blocks and characteristics The Adaptive Computing Controller Summary

From 3-tier Client/Server to Enterprise Services 3-tier Client/Server Architecture Enterprise Services Architecture Composite Applications UI UI UI Role-based UI built on Services Process Automation built on Services mySAP ERP Financials Human Resources Corporate Services Operations SAP NetWeaver Process Client-Server: Quit easy / One Component-one database – static ESA: around the integration platform SAP Netweaver More complex, several components working very closely together Several databases -> More and more adaptive business solution are required – so we need an Adaptive Computing Infrastructure Components Business Module CRM ERP ... Technology Basis Solution Components Database DB DB DB

Adaptive Computing Adaptive Computing is a new approach to design hardware, software and system services following the business-driven need to permanent change and adaptability It is about empowering the customer to be able to run any service any time on any server. In this context the word application service is used to describe any kind of scenario, solution or application component A computing infrastructure is called adaptive, if it allows the dynamic assignment of hardware resources to serve specific application services. In this way, SAP NetWeaver enables an 'Adaptive Computing Infrastructure' and thus ensures that business solutions based on SAP NetWeaver run at peak cost efficiency

Composite Application Framework The NetWeaver Capability Adaptive Computing SAP NetWeaver™ PEOPLE INTEGRATION SAP NetWeaver provides a way to virtualize application services, and provides a single central point of control for flexible compute resource assignment for existing and new code to run on dedicated/changing hardware. Multi channel access … Portal Collaboration INFORMATION INTEGRATION Bus. Intelligence Knowledge Mgmt Master Data Mgmt Composite Application Framework Life Cycle Mgmt PROCESS INTEGRATION Integration Broker Business Process Mgmt APPLICATION PLATFORM J2EE ABAP DB and OS Abstraction Adaptive Computing IT INFRASTRUCTURE Adaptive computing is not just the under laying infrastructure for the Integration platform SAP Netweaver that allows us to use resources very flexible and efficient. AC also supports the “Lifecycle Management” : Implementation of new solutions: start on small servers, grow with your needs Upgrade: Take a snapshot, upgrade your snapshot system…(In combination with advanced storage functionality) OS upgrades, Tests Server exchange… / lease period ends Operating Systems Hardware Storage Application Services

Adaptive Computing Technical Overview General information Building blocks and characteristics The Adaptive Computing Controller Summary

Adaptive Computing - The four building blocks Network Control Storage Have dedicated resources for computing, storage, network and control Pool them and share them – if appropriate Define application services and virtualize them Key of the concept is the separation of the infrastructure into building blocks

Adaptive Computing Virtualization Layer The Adaptive Computing Building Elements Solution Stack Automated Execution Adaptive Computing Controller Adaptive Computing Virtualization Layer Computing Infrastructure Adaptive Computing Virtualization Layer Enables a virtualization layer to start any service any time on any server Automated Execution Application Services Management, Auto Inventory, Netboot@SAP Adaptive Computing Controller Provides a single point of control to operate, observe and manage an adaptive business solution

Adaptive Computing Virtualization Layer Adaptive Computing – SAP/Application View Deliverables How to enable Solutions (Services, components ) to become adaptive Virtualization Requirements for application White papers Requirement list Logical Landscape based on SAP NetWeaver™ Solution Management SAP/Application View Solution Stack Automated Execution Adaptive Computing Controller Adaptive Computing Virtualization Layer Computing Infrastructure

Partner View (Products/Solutions) Adaptive Computing – Technology Partner View Solution Stack Automated Execution Adaptive Computing Controller Adaptive Computing Virtualization Layer Computing Infrastructure Partner View (Products/Solutions) Deliverables How to enable partners to certify their products Certification process Requirement list Certification tools Porting guide Physical landscape Plattform/technology requirements System management Platform ( OS, DB, netboot, virtualization layer, ... ) Storage ( NFS, SAN, NAS, ... ) 3rd party management software

Characteristics of the building blocks HW+OS provisioning Easy add and remove computing resources with low admin efforts Single point of OS maintenance: netboot (shared or multiple OS), OS deployment, or equivalent technology Network Connects computing nodes to each other Builds up connection between building blocks ‘Computing’ and ‘Storage’ Transport layer for virtualization Computing Network Adaptive Computing Controller Provides a single point of control to operate, observe and manage an adaptive business solution Capability of SAP NetWeaver™ (based on Standards: SAP J2EE engine, XML, CIM…) Interfaces with SAP Solution Manager Controller Command Interface for communication with third party software Storage Data Application Services: SAP instances managed and assigned to a dedicated computing resource Installation-free provisioning for Application services No local disk space required to run SAP applications; application data stored on storage system within a network Control Storage

Adaptive Computing Technical Overview General information Building blocks and characteristics The Adaptive Computing Controller Summary

High level architecture Browser Browser/ SAPGUI Web Application Server Web Application Server Adaptive Computing Controller Solution Manager System Landscape Directory

ACC Controller Command Interface SAP Standalone Gateway Communication and Function Overview HTTP SolMan R/3 ABAP system Web AS Application Service RFC (RZ70) OS Shared memory RFC SolMan Station saposcol HTTP (saposcol –b | sldreg ..) sapacoscol HTTP ACC SLD sapgwXX sapacosprep ssh WBEM (XML) RFC ACC Controller Command Interface OS SAP Standalone Gateway WebAS 6.40 J2EE Engine Computing Nodes HTTPS Chapter 3.11 Computing nodes sapacosprep: must be available on each computing node and will be called from the ACC via ssh to prepare the OS (NW interface, mount, …). After sapacosprep has finished, the application service is able to start. saposcol: is a general available agent from SAP for collecting OS information per host, which writes it’s data to the local shared memory. This agent is started each time after the boot of the server. sapacoscol: reads data (hostnames, OS version, CPU utilization, …) out of the shared memory and transfers it to the ACC. This agent is started each time after the boot of the server. During each start of the computing node the xml output of this agent (saposcol –b) is used to register this host with sldreg at the central SLD (a single registration process would be enough). Application Service: registers once via the transaction RZ70 in the central SLD. • ACC Station SLD: is the “data store” for the landscape and configuration data of the adaptive services and the adaptive hosts. The ACC connects to the SLD via WBEM. The Solution Manager acts as the design engine for the adaptive environment and gets the basic data from the SLD and writes the “adaptive data” after the modeling process back to the SLD. The communication with the Solution Manager is done via RFC calls. ACC: The Adaptive Computing Controller as the center of infrastructure management solution, communicates with different components of the infrastructure: sapacoscol: as long as this agent reports any application specific virtual interface to the ACC, the controller shows the physical host, where the interface is up, as used for this service. sapacosprep: is the program, which initiates the OS specific preparations like configuring the NW interfaces, managing the mounts, …. This program is directly called by the ACC via SSH and reports back to the ACC the return codes and the output of the OS commands. The only direct communication between the SolMan and the ACC is the notification functionality, that in the SolMan some data was changed. The protocol is HTTP. Controller Command Interface: The ACC communicates with external programs via the Controller Command Interface (CCI). This interface provides basic functionality of the ACC to external programs the. The communication protocol is HTTPS. SAP Standalone Gateway: is the communication platform for all RFC based communication between SLD, SolMan and the “to managed” systems. SolMan Station Solution Manager: acts as design engine for the configuration data of the adaptive computing environment and gets the basic data from the SLD and after the modeling process writes the “adaptive data” back to the SLD. The communication with the Solution Manager is done via RFC calls. The only direct communication between the SolMan and the ACC is the notification functionality, that in the SolMan some data was changed. The protocol is HTTP. OS external program connect to the ACC CCI ACC Station Legend: single registration ongoing data transfer

Logon screen On the following slides two demo scenarios are presented start of an application service relocation of an application service visualizes specific information leads to the next controller view  click

View after logon

Physical landscape view

Controller log

Logical landscape (collapsed view)  click

Logical landscape (expanded view)  click

Logical landscape (expanded view)  click

Logical landscape  click

Logical landscape (expanded view)  click

Select an application service  click

Select a server  click

Auto select  click

Start application service  click

Confirmation  click

Dependency needs to be confirmed  click

Application service about to start  click

Switch to physical landscape  click

Application services starts on server  click

Entries in controller log  click

Switch back to physical landscape  click

Relocation of an application server  click

Select a specific server  click

Start relocation  click

Check dependencies  click

service relocates  click

logical landscape

logical landscape

logical landscape

Switch to controller log  click

relocation took less than 5 minutes  click

detailed log information  click

observation window  click

CPU/memory load of servers in the AC landscape

Adaptive Computing Technical Overview General information Building blocks and characteristics The Adaptive Computing Controller Summary

Comparing the Adaptive Computing characteristics Current Infrastructure Adaptive Computing Box centric (Server, DB) Installation per server Individually Infrastructure & operation Backup / Recovery per server Sizing per component/peak High availability requires additional (expensive) hardware and increases complexity Service oriented, abstracting the hardware Service available in the network Standardized Building blocks Backup per logical landscape Shared resource model possible High availability fundamentally included

Benefits for our customers Customers Statements By increasing flexibility and decreasing TCO, ROI is much more visible High flexibility to run new projects High flexibility to assign and utilize hardware resources Easy setup and integration of new components into common infrastructure Customer Experiences First customers like Hella and T-Systems report TCO savings of around 25%

Current Status of Adaptive Computing SAPPHIRE ´03, Orlando (June 2003) Successful demonstration of proof-of-concept SAPPHIRE ´04, New Orleans (May 2004) SAP AG announces Adaptive Computing as a capability of NetWeaver Adaptive Computing Controller 1.0 ACC 1.0 Ramp-Up, June 2004 Customer and Partner Participation First customer success stories HELLA T-Systems

Newest information can be found on http://service.sap.com/adaptive

Copyright 2004 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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Copyright 2004 SAP AG. Alle Rechte vorbehalten Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der 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, und Informix sind Marken oder eingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern. Oracle ist eine eingetragene Marke der Oracle Corporation. UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc. HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java ist eine eingetragene Marke von Sun Microsystems, Inc. JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die vorliegenden Angaben werden von SAP AG und ihren Konzernunternehmen („SAP-Konzern“) bereitgestellt und dienen ausschließlich Informationszwecken. Der SAP-Konzern übernimmt keinerlei Haftung oder Garantie für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Aus den in dieser Publikation enthaltenen Informationen ergibt sich keine weiterführende Haftung.