SPC 386

SAP
Agility Reach Adoption

Client InteroperInteroperability

SAPGUI on Windows

mySAP CRM Mobile Client on Tablet PC Project Mendocino Ships as Duet TM mySAP.com Solutions on Pocket PC Office announced as a native SAP UI (along with Web, SAP Desktop Office Interop SmartClient, SmartClient, and Mobile) Duet V3 will be built on the next version of the Office Platform including SharePoint Integration with Exchange Server DCOM Connector Joint Commitment to Advanced Web Services Portal Development Kit .NET SAP .NET Connector

Applications & Services

RFC SDK

SAP Enterprise Services Explorer for Microsoft .NET

Application Infrastructure

SAP R/3 on SQL Server SAP R/3 on Windows NT Microsoft Becomes SAP Customer

SAP 64-Bit Windows (for Itanium) 64 SAP is Windows 2000 Launch Partner mySAP SCM for Xbox Manurfacturing SAP Is SQL Server 2005 Launch Partner Mendocino Business Alliance

Business Alliance

Agreement Between Bill Gates and Hasso Plattner

SAP and Microsoft sign new agreement covering and communicate plans for next three versions of Duet

SAP NetWeaver and Microsoft .NET Announcement

1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008

Web 2.0 Portal

Provision New Hire

Reach

Create Work Order Create Opportunity

Devices & People Legacy Custom Apps

CRM

Delete P.O.

Order to Cash

ERP Data Trading Partners

Ship Product Engineering Change Request

Agility

1 MOSS = 7 SAP Screens

Procurement Cockpit

20+ SAP screens to perform desired action OffOff-line approval workflow Data dumps into Excel for analysis E-mail collaboration with partners

Role-based Cockpit combines SAP analytical and transaction workflows and data in a collaborative, exception-based workbench

Improve usability and access to backbackend business processes for suppliers Improve supply chain processes that are unstructured, lacked consistency, and required heavy amounts of verbal and written communications, all of which resulted in repetitive and lost communications as well as delays in order processing.

Guided, complete information relevant to the business process provides holistic context to carry out the suppliers job function.

C o n s u m e

Sharepoint Server: BDC, Forms, ExcelServices, Web DynPro, iViews, BSP

Windows Presentation Foundation, Silverlight

Microsoft Mobile Platform

Office Client: Outlook, Word, Excel, Silverlight, WPF, InfoPath

C o m p o s e

Optional Human/Human Workflow: K2, AgilePoint, Nintex, SharePoint WF BizTalk Sap XI/PI WCF RFC/BAPi Web Service SAP ERP SAP SRM SAP CRM Other SAP Modules Ent Service API/WS
Planning, Production & Maintenance Systems

3rd Party

WCF Adapter

E x p o s e

Other Legacy Systems

 Grab the UI iViews WSRP BSPs, Web Dynpro Grab the data BI-only scenario; do not attempt otherwise OpenHub .NET data provider for SAP Business Warehouse Grab the API BAPIs, RFCs, etc. Other Integration Scenarios Search, Document Management,

 NetWeaver Portal offers a WSRP Producer SharePoint Server 2007 can consume WSRP compliant Portlets WSRP (still 1.0) has lots of limitations WSRP implementations vary from vendor to vendor

 iViews are SAP Enterprise Portals equivalent of Web Parts Lightweight integration of portlets MOSS SSO is a prerequisite to iView Web Parts No Drag & Relate or other inter-portlet communication available Users must be mapped UI/stylesheets apply partly only (hard to apply themes)

 Re-use of existing Business Packages from SAP Web Dynpro Applications run on top of the ABAP stack or the JAVA stack No NetWeaver Portal required if Web Dynpro for ABAP is used Single Sign-On requires SAP NetWeaver JAVA stack Desired look and feel by CSS

 For SAP we choose Web Services connectivity  BDC Definition Editor (part of MOSS SDK download) creates service description  Import XML description file to BDC as Shared Application  Create Actions if needed

 BDC limitations Only SOAP or ADO.NET Must have Web Service layer between BDC and BAPIs/RFCs Can call only one SOAP method at a time Aggregating output from a set of method calls is NOT possible in this release As SAP BAPIs/RFCs are extremely granular, this presents a problem Youll need a Web Service layer Youll need a composition technique

SharePoint

 eSOA design time support for Microsoft developers Succeeds the SAP connector for Microsoft .NET Add-in for Visual Studio 2005 Enables discovery of SAP enterprise services in .NET applications

 Option 1: have MOSS index SAP content BDC HTTP (for unstructured data) Option 2: federate SAP NetWeaver TREX Use Search Servers new federation feature (Available in Microsoft Search Server) TREX has Web service API (Must be adapted to present OpenSearch interface) Option 3: surface TREX in MOSS UI Add TREX-specific Web Parts to MOSS pages

Frontend, Application & Services

SAP NetWeaver
SAP NetWeaver Portal

Microsoft .NET

Single Sign-On

Sharepoint Portal

SPNego mySAP Business Suite and SAP R/3 CRM ERP HR R/3 Exchange Server

 Based on AD, Kerberos

and SAP Logon Tickets.  SAML tokens are not interoperable today

Applistructure

Identity Center

Virtual Directory Server

Active Directory

MIIS

SAP Net Weaver Identity Management

User Management

Microsoft Windows Server

24

Office Apps

Cache

Design Tools

SharePoint
Dev Platform Business Intelligence Enterprise content mgmt Collaboration social Enterprise Search

Dynamics

SAP

Siebel

LOB

Web 2.0

A standard for sharing information stored in disparate repositories that is designed to:
Ensure interoperability for people and for applications among multiple content repositories across all platforms
o Enable applications to target one or more ECM repositories uniformly for core content services

Easy mapping to existing ECM systems

o Expose standard set of APIs for existing capabilities of CM repositories o Leverage existing content

Provide several protocol bindings using the common domain model:

o Simple Object Access Protocol (SOAP) o Representational State Transfer (REST) / ATOM

Exploit web technologies

o o o o Web 2.0 Internet Scale Service-orientation Resource-orientation

Out-of-the-Box Business apps with embedded SAP core and extended ECM services

Composite Apps with SAP core and extended ECM services

Further Apps (e.g. Portal)

 SAP is decoupling the ECM infrastructure layer from the application / consumption layer  SAP will provide and maintain core / basic services, in ABAP and Java.  SAP will closely work with partners to provision extended ECM services.

SAP ECM Service Layer SAP ECM Core Services Extended ECM Services (by Partners)

Document Mgt. (DMS) (ABAP)

Records Mgt. (RM) (ABAP)

Basic Content Services (KM) (JAVA)

Document Management

Digital Asset Management

In/Output Management

Records Management

Forms Management

 SAP will keep the current scope of KM as a basic content service, in addition SAP will provide core missing features (e.g. archiving) and fix gaps. The KM architecture will remain unchanged and there will be no significant re-design  SAP will introduce an open ECM interface layer and partner for full-fledged ECM scenarios. SAP will focus on integrating and enriching SAP applications with ECM capabilities

1. 2. 3. 4.

SAML Token (HoK) WS Consumer WS Provider

* Enhancement Package 1 / Support Release 1 for SAP NetWeaver 7.0/7.1 AS ABAP and 7.1 AS JAVA ** already supported in SAP NetWeaver AS ABAP 7.0 > SP14, not supported out of the box in .NET 3.0/3.5

 
Security Token Service

SAML Token (HoK)

SAML Token (HoK) WS Consumer WS Provider

* Enhancement Package 2 for SAP NetWeaver Application Server 7.0/7.1

SAP

Agility Reach Adoption

Achieved today and tomorrow though

Sharepoint & Office SOA and the Expose, Compose and Consume design pattern

Microsoft