share point 2010 and sap integration
TRANSCRIPT
Revolutionizing the SAP user experience… with SharePoint Matthew OrdishSAP Solutions Director. SCDMicrosoft [email protected]
SPC 386
WHY?
SAP AgilityReach
Adoption
HOW
The next 70min!!
Relationship
Architecture and Design Principles
Today
Tomorrow
Microsoft and SAP – A Strong Partnership
ClientInteroper-ability
Applications& Services
ApplicationInfrastructure
Business Alliance
1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008
• SAPGUI on Windows®
• SAP Desktop Office Interop
• mySAP.com Solutions on Pocket PC
• Project Mendocino Ships as Duet TM
• mySAP CRM Mobile Client on Tablet PC
• Integration with Exchange Server
• DCOM Connector
• RFC SDK
• SAP R/3 on SQL Server™
• SAP R/3 on Windows NT
• Microsoft Becomes SAP Customer
• SAP is Windows® 2000 Launch Partner
• mySAP SCM for Xbox Manurfacturing
• SAP Is SQL Server 2005 Launch Partner
• SAP 64-Bit Windows (for Itanium)
• SAP .NET Connector
• Portal Development Kit .NET
• Joint Commitment to Advanced Web Services
• Mendocino Business
Alliance
• Agreement Between Bill Gates and Hasso Plattner
• SAP NetWeaver and Microsoft .NET Announcement
Full Interoperability
• SAP and Microsoft sign new agreement covering and communicate plans for next three versions of Duet
• Office announced as a native SAP UI (along with Web, SmartClient, and Mobile)
•Duet V3 will be built on the next version of the Office Platform including SharePoint
• SAP Enterprise Services Explorer for Microsoft .NET
SOA and OBA strategy
Reach
Agility
Expose
Compose
Consume
Devices& People
Web 2.0
TradingPartners
Data
CRM
CustomApps
Legacy
Provision New Hire
Order to Cash
EngineeringChange Request
Portal
ERP
Create Work Order
Ship Product
Create Opportunity
Delete P.O.
Single Sign On DashboardECC, SRM, BW, Maximo – Application Data
8
Approvals Dashboard to approve any item in processQuick Links for easy access into core Backbone functionsTop Reports list the top 5 reports from each sectionSearch Center to search across Backbone on any item you have access toReal Time Information about projects displays simple report data
SAP Goods Movement Consolidation of 7 SAP Screens
9
=
1 MOSS = 7 SAP Screens
Role-Based Supply Chain WorkbenchesProcurement Cockpit
20+ SAP screens to perform desired actionOff-line approval workflowData dumps into Excel for analysisE-mail collaboration with partners
Role-based “Cockpit” combines SAP analytical and transaction workflows and data in a collaborative, exception-based workbench
Supplier Collaboration
Improve usability and access to back-end business processes for suppliersImprove 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.
The ECC (Expose,Compose,Consume) approach to SOA & OBA
WCF Adapte
r
Compose
BizTalkSap XI/PI
3rd Party
Optional Human/Human Workflow: K2, AgilePoint, Nintex, SharePoint WF
WCF
Consume
Sharepoint Server:BDC, Forms,
ExcelServices, Web DynPro, iViews, BSP
Office Client:Outlook, Word, Excel,
Silverlight, WPF, InfoPath
Microsoft Mobile
Platform
Windows Presentation Foundation, Silverlight
SAP ERPPlanning,
Production &Maintenance
Systems
Expose SAP CRM
API/WSEnt
ServiceRFC/BAPi
Web Service
Other SAP Modules
SAP SRM Other Legacy
Systems
SharePoint Server Integration
Overview SAP Integration with MOSS• 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,
WSRP Web Part
• 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
iView Web Part• iViews are SAP
Enterprise Portal’s 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)
Web Dynpro and BSP in MOSS• 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
BDC connecting to SAP WebServices 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
Issues with Consuming SAP APIs
• 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
• You’ll need a Web Service layer
• You’ll need a composition technique
Silverlight & SharePoint
Convergence of Silverlight and SharePoint will growSilverlight within SharePoint offers RIA capabilities for SAP integrations:
Enhanced Office Business Applications
SharePoint
Web Part
Silverlight App.
The SAP Enterprise Services Explorer for .NET
• 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 Server‘s 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
Searching SAP Content
SAP NetWeaver™SAP NetWeaver Portal
mySAP Business Suiteand SAP R/3
HR
SAP Net Weaver Identity Management
CRM
ERP
…
R/3
Virtual Directory Server
Microsoft Windows Server
Exchange Server
Sharepoint Portal
Active Directory
Single Sign-On
SPNego
User Management
Identity Center MIIS
Microsoft .NET
Applis
truct
ure
Fronte
nd, A
pplic
ati
on &
Serv
ices
End-to-end Identity Management and Single Sign-On
Based on AD, Kerberos and SAP Logon Tickets. SAML tokens are not interoperable today
Possible Architecture (MOSS Focus)
24
Microsoft / SAP Technology Center
Demo
Tommorrow• BCS• iFrames• CMIS• SAML• Silverlight
Business Connectivity ServicesEnhance SharePoint platform capabilities with out-of-box features, services and tools that streamline development of solutions with deep integration of External Data and Services.
Office Apps
BDC Client Runtime
Offline Operation
sCache
DevPlatfor
m
Business Intelligenc
e
Enterprise content mgmt
Collaboration social
EnterpriseSearch
ECT Store
BDC Runtim
e
Security
Solution packagin
g
Out of boxUI
Web 2.0LOBSiebelSAPDynamics
SharePointDesign Tools
Visual Studio
SharePoint
Designer
External Data is Surfaced In…Server
External listsInfoPath
Web partsBusiness DataXSLTListView, XSLTListForm, Chart Web Part, InfoPath
External Data ColumnWorkflow Search External Content Type (ECT) PickerECT Instance Picker
ClientSharePoint WorkspaceOutlook
Can be extended to include Taskpane
External Data PartsList of itemsSingle item
Word AccessExternal Data Picker
iFrame
iView Web Part no longer available in SharePoint 2010iFrame Integration of iViews, BSPs, and Web Dynpro ApplicationsBenefits
Out-of-box usage of Business Packages from SAPSecurityLeft-hand Navigation
CMIS Goals
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 systemso Expose standard set of APIs for existing capabilities of CM repositorieso 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 technologieso Web 2.0o Internet Scaleo Service-orientationo Resource-orientation
Enterprise Content Management : SAP Strategy and Relation to KM
Composite Apps with SAP core and extended ECM services
Out-of-the-Box Business apps with embedded SAP core and extended ECM services
SAP ECM Core Services Extended ECM Services (by Partners)
SAP ECM Service Layer
DocumentMgt. (DMS)(ABAP)
RecordsMgt.(RM) (ABAP)
Document Management
Digital AssetManagement
…
In/OutputManagement
Further Apps (e.g. Portal)
Forms Management
Records Management
Basic Content Services(KM)(JAVA)
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 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
Security and Identity
1. Request Security Token2. Request Security Token Response3. Request from Web Service Client using WSS 1.04. Response from Web Service Provider using WSS 1.0
SAML-based SSO for Web Services in SAP NetWeaver 7.01/7.11 SR 1*
Authentication of incoming Web Service Requests based on the WS Security SAML Token Profile 1.0
Supported Confirmation Methods: “Holder-of-Key (HoK)” and “Sender-Vouches (SV)”
Holder-of-Key: Symmetric Keys only
Sender-Vouches: Token must be signed using STR-Transform**
* 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
WS ConsumerWS
Provider
SAML Token (HoK)
SAML-based SSO for Web Services in SAP NetWeaver 7.02/7.12* Acquisition of issued SAML Tokens from an external Security
Token Service (STS)
Improved support and interoperability for security metadata
* Enhancement Package 2 for SAP NetWeaver Application Server 7.0/7.1
WSConsumer
SAML Token (HoK)
WSProvider
SecurityToken
ServiceSAML Token (HoK)
Conclusion
SAP Agility Reach Adoption
Achieved today and tomorrow though
Microsoft Sharepoint & OfficeSOA
and the Expose, Compose and Consume design
pattern
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after
the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.