From Microsoft Office to Visual Studio A Comprehensive Guide to Integration Options Between SAP NetWeaver and Microsoft Products,

, Development Tools, and .NET Applications Franklin Herbas SAP

SAP NetWeaver and Microsoft .NET SAP NetWeaver and Microsoft .NET interoperability roadmap The Collaboration Technology Support Center Wrap-up

SAP NetWeaver and Microsoft .NET SAP NetWeaver and Microsoft .NET interoperability roadmap The Collaboration Technology Support Center Wrap-up

The SAP NetWeaver Announcement 2003

SAP NetWeaver
People Integration
Multi-Channel Access Composite Application Framework Portal Collaboration Life Cycle Management

Evolution of mySAP Technology Unifies and aligns people, information, and business processes
Integrates across technologies and organizational boundaries A safe choice with full .NET and J2EE interoperability

Information Integration
Business Intelligence Knowledge Management

Master Data Management

Process Integration
Integration Broker Business Process Management

The business foundation for SAP and partners

Powers business-ready solutions that reduce custom integration

Application Platform
J2EE ABAP

.NET

DB and OS Abstraction DB and OS Abstraction

Its Enterprise Services Architecture increases business WebSphere process flexibility

SAP AG 2005, 4

The SAPPHIRE 2004 Press Release

Microsoft and SAP Raise the Stakes for Web Services for the Enterprise
Companies Deepen Relationship through Broad Integration of SAP NetWeaver with Microsoft .NET NEW ORLEANS, La. and REDMOND, Wash. - May 12, 2004 - Microsoft Corp. and SAP AG (NYSE: SAP) today announced a significant expansion of their long-standing relationship based on a shared commitment to Web services...

Full press release on: http://www.sap.com/company/press/press.asp?pressID=2799

SAP AG 2005, 5

The SAPPHIRE 2004 Press Release: Key Topics

Technology deliverables:
SAP Enterprise Portal Development Kit for Microsoft .NET SAP .NET Connector Version 2.0 SAP Support for Visual Studio .NET SAP NetWeaver Support for Advanced Web Services Protocols SAP NetWeaver Support for Microsoft Smart Client Technology Integration between SAP NetWeaver, Microsoft Exchange, and Microsoft Windows SharePoint Services

Business engagement:
Joint staffing of Collaboration Technology Support Center Joint sales and marketing

SAP AG 2005, 6

Why SAP NetWeaver Interoperability with Microsoft .NET?

60% of SAP solutions run on Microsoft servers More than 90% of desktops use Windows and Office Microsoft Windows is the only platform that supports all SAP products Microsoft is one of our biggest partners: Microsoft is 95% partner and 5% competitor. (H. Kagermann) Therefore: SAP customers demand to understand interoperability between SAP NetWeaver with Microsoft .NET

We at Akzo Nobel Chemicals have chosen SAP and Microsoft as our key software vendors. For us it is extremely important to understand how both companies work together to give us the full technical interoperability between SAP NetWeaver and Microsoft .NET not only today, but also in the future
Gerard Helmink Group Information Officer, Chemical Division Akzo Nobel

SAP AG 2005, 7

SAP NetWeaver and Microsoft .NET SAP NetWeaver and Microsoft .NET interoperability roadmap The Collaboration Technology Support Center Wrap-up

Roadmap: SAP NetWeaver and Microsoft .NET Interoperability

People Integration
g g y g g

SAP Enterprise Portal Development Kit for .NET (PDK .NET) SAP .NET Connector 2.0 Smart Client Sample Applications Active Directory and Single Sign-On Outlook Web Access in EP (VS .NET 2005)

This roadmap contains the current status for existing or announced interoperability scenarios between SAP NetWeaver and Microsoft .NET
g

Information Integration
y y

= Solution ready = Solution announced = Collaboration Brief on SAP Developer Network (SDN)

Repository Mgr. for Sharepoint/Exchange Microsoft Content Management Server

(Early 2005) (Early 2005)

Process Integration
g g

Web Services Collaboration BizTalk Server and SAP XI Interoperability

(Ongoing)
(Status: October 2004; list is incomplete: This presentation reflects current planning. Contents may be changed without prior notice, and are in no way binding upon SAP)

Application Platform
g

Windows and SQL Server

(Ongoing)

Click on item for details. Click

to return to this slide. Click

for next agenda item

SAP AG 2005, 9

PDK .NET: Overview

Interoperability
Develop iViews using Microsoft Visual Studio .NET Integrate Microsoft-based applications into SAP Enterprise Portal (EP) Seamless integration with SAP Enterprise Portal 6.0 Leverage resources around Microsoft .NET framework and ASP.NET

Product roadmap
First prototype shown at SAPPHIRE 2003 by Shai Agassi (SAP) and Eric Rudder (Microsoft) Early adopter program since June 2004 Shipping now on SAP Developer Network (http://www.sdn.sap.com/sdn/developerareas/dotnet.sdn)

Available now on Available now on SAP Developer Network SAP Developer Network

SAP AG 2005, 10

PDK .NET: Architecture

Browser

.NET Server
Visual Studio .NET
.NET iView .NET Portal Services SAP .NET Controls SAP .NET Connector

Interoperability Interoperability Framework Framework Ja.NET Ja.NET

SAP J2EE EP 6
.NET Proxies & Managers (iViews & Services)

Portal Services

Deployment

SAP AG 2005, 11

PDK .NET: Architecture in Detail

The .NET Server
ASP.NET Networking process is used to run the .NET iViews. IIS is not being used All ASP.NET objects (request, response, session, application) should be available to the iView developers The server could run as NT service

Interoperability Framework
A framework that allows API calls from the Java stack to the .NET stack and vice versa For each .NET object that can be called from Java a Java proxy object is created and vice versa On the the .NET side, .NET Remoting technology is being used

SAP AG 2005, 12

PDK .NET: Building Blocks for .NET iViews

What is a .NET iView?
.NET iView can be written in a similar way of developing ASP.NET page A new class is introduced SAP.Portal.Web.UI.iView
Derives from System.Web.UI.Page means it is similar to ASP.NET page iViews inherit from it

Context objects are available through properties of the iView (Profile, Logger, User Information, )

SAP .NET controls

Provide a set of .NET controls that will be used to create .NET iViews in an easy way Support SAP unified rendering Easy connectivity to connectors responsible for retrieving data Use Portal User information Culture, Theme Will be available through the VS.NET Toolbox

SAP AG 2005, 13

PDK .NET: Deployment Modes

Offline Deployment
.NET iViews are packed in a PAR file (same as in Java) PRT deployment mechanism is being used
Deployment is done through the PRT HTTP API The assemblies and the files are being kept in the Portal Content Directory

Deployment to a remote server is supported

Hot Deployment is supported

When the developer deploys an iView that is already loaded, the server reloads the application domain All the existing requests are completed New requests run using the new iView version Session and cache objects are deleted

SAP AG 2005, 14

PDK .NET: Windows Runtime Environment J2EE & .NET servers reside on the same physical machine Windows machine

J2EE .NET J2EE .NET

J2EE .NET

SAP AG 2005, 15

PDK .NET: Hybrid Runtime Environment Separate machines for the J2EE servers and for the .NET servers. The J2EE server can be a Unix Machine

J2EE Cluster
SAP AG 2005, 16

.NET Cluster

PDK .NET: Visual Studio .NET Integration

Fully integrate solution into VS.NET, including:
Creation of SAP Portal Project Adding of SAP .NET iView Toolbars actions deploy, create Toolboxes .NET controls Menus

Use standard development behaviors

Debugging* Preview* Intellisense
*Only if connected to a Portal server

Developer can develop iViews when no Portal is running The development can be done working with remote Portal server (not installed on the same machine as VS.NET)
SAP AG 2005, 17

PDK .NET: Visual Studio .NET Integration (cont.)

SAP Menu

Solution Explorer SAP Server Explorer

SAP UI Controls

ContextSensitive Help

SAP AG 2005, 18

SAP .NET Connector

Interoperability
Design-time and runtime environment Visual Studio for PDK and SAP .NET Connector Use .NET Connector for fast and scalable access to 1000s of BAPIs and RFCs Leverage existing skills in Visual Studio, ASP, Visual Basic and C#

Product Roadmap
SAP .NET Connector 2.0 is available at the SAP Service Marketplace SAP .NET Connector 2.0 also ships as part of the PDK .NET on SAP Developer Network

SAP AG 2005, 19

SAP .NET Connector (cont.)

Highlights
SAP .NET Connector was the first dedicated SAP product offering SAP NetWeaver-.NET interoperability Extend mySAP applications with .NET components

Available today
Version 1.0 ships since 11/2002 More than 5,000 registered downloads so far Very positive feedback from customers and partners

SAP AG 2005, 20

SAP .NET Connector V2

Equal support for Visual Basic and C#
Beginning with Version 2.0, Visual Basic.NET is a first class language for the .NET Connector, with equal feature support as Visual C#

Integration with the Visual Studio Server Explorer

View SAP systems in the Visual Studio.NET Server Explorer Drag and drop function modules and BAPIs into your project Drag and drop an SAP system from the Visual Studio Server Explorer to create a Login component

Support for the BAPI object model

In version 2.0 the full BAPI object model is implemented by use of Proxy fields and improved databinding tools support

Additional tools support

Available now on Available now on SAP Developer Network SAP Developer Network

SAP AG 2005, 21

Office Integration and Smart Client Technologies

Product overview
Web Services-based solutions involving Office System and future smart client technologies

Interoperability
Now: Microsoft .NET Framework 1.1 and Microsoft Office 2003 2005: Visual Studio 2005 (Whidbey) Longhorn

Product roadmap
Word, Excel, and InfoPath demos SAP will deliver Office and smart client samples SAP will deliver Longhorn smart client and SDK

SAP AG 2005, 22

SAP Single Sign-On (SSO)

SAP EP provides SSO to back-end systems using:
SAP Logon Tickets Account Aggregation
SAP ISAPI FIlter DLL

Third-party Applications

SAP Logon Tickets can be used for SSO to:

SAP Applications Microsoft Web Applications such as Outlook Web Access Other applications with appropriate Web Server filter

New SAP Logon Ticket

e.g., Account aggregation

SAP Enterprise Portal

Initial Logon

SAP AG 2005, 23

The Ticket Bridge to Microsoft Web Applications

Microsoft Internet Information Server
3

SAP Filter

Impersonation Kerberos ticket

Kerberos Constrained Delegation

Check SAP Logon Ticket

Exchange 2003

Check if server is trusted for delegation

Active Directory 2003

Example: Outlook Web Access

SAP AG 2005, 24

Available now on Available now on SAP Developer Network SAP Developer Network

Outlook Web Access in Enterprise Portal

Interoperability
Access Outlook Inbox, Calendar, Tasks, Contacts from within SAP Enterprise Portal Authentication (SSO) issue solved: New Ticket Bridge
Windows Integrated Authentication (intranet) Kerberos Constrained Delegation (Windows 2003 and Exchange Server 2003)

Product roadmap
Exchange 2003 offers great Web user interface with Outlook Web Access (OWA) Use standard SAP EP iViews to visualize OWA in EP SAP Whitepaper explains OWA integration into EP Navigate from there into Outlook Windows client

SAP AG 2005, 25

Outlook Web Access in SAP Enterprise Portal: Sample

SAP AG 2005, 26

Repository Managers for SharePoint and Exchange

Product overview
Windows SharePoint Services ships with Windows Server 2003 SharePoint Portal Server integrates corporate WSS sites and adds services (search, navigation) Exchange Server offers Public Folders of interest

Interoperability
Unified view from SAP Knowledge Management to locally stored documents and outside repositories Leverage the investment in Microsoft document repositories Portlet (iView, Web Part) Syndication has clear limitations

Product roadmap
Microsoft will provide SharePoint- and Exchange-specific Repository Managers in early 2005

SAP AG 2005, 27

Microsoft Content Management Server

Interoperability
Content Management Server (CMS) is a comprehensive solution for content creation, publishing, and storage Microsoft Word, FrontPage as Simple Content Editing Tools CMS iViews to publish content and to support Business Managers and Business Users inside SAP Enterprise Portal

Product roadmap
Microsoft will offer CMS iViews for SAP Enterprise Portal 6.x in early 2005

SAP AG 2005, 28

BizTalk and SAP XI

Using Web services to connect the critical business information and processes in SAP NetWeaver with the power and productivity of Microsoft .NET will give our mutual customers a key competitive edge, said Bill Gates.
Interoperability
Message-based interoperability between XI and BizTalk Goal is to deliver integration solely via Web Services Both companies will drive advanced Web service protocols standards enabling reliable and transacted interoperability. Examples:
Including BPEL4WS WS-I Basic Profile WS-RM (Reliable Messaging)

SAP AG 2005, 29

Microsoft Platforms
Windows Server
Microsoft Windows is the most widely used OS, and the only one with end-to-end support for all SAP components Current servers impose no more limitations to scalability After three years of successful development cooperation with Microsoft, SAP was launch partner for Windows Server 2003 and its 64-bit version

SQL Server
Scalable and reliable state-of-the-art database Support for Yukon beta/Microsoft already live

Microsoft Certification
SAP R/3 Enterprise 4.7 is certified for Windows Server 2003 Datacenter Edition

SAP AG 2005, 30

SAP NetWeaver and Microsoft .NET SAP NetWeaver and Microsoft .NET interoperability roadmap The Collaboration Technology Support Center Wrap-up

The CTSC-MS Mission Statement

The Collaboration Technology Support Center is a joint team of experts from SAP and Microsoft that provides guidance and help for better integration between SAP and Microsoft products.

SAP AG 2005, 32

Relationship Triangle: Customer, SAP, Microsoft

Customer
Sa les les Sa
Co ns ult ing ing ult ns Co

SAP Microsoft Competence Center Collaboration Technology Support Center (CTSC-MS)

Development

Development

SAP AG 2005, 33

.NET Interoperability in SAP Developer Network

SAP AG 2005, 34

SAP Internal Information Portal About Microsoft

SAP AG 2005, 35

SAP NetWeaver and Microsoft .NET SAP NetWeaver and Microsoft .NET interoperability roadmap The Collaboration Technology Support Center Wrap-up

Further Information
Public Web:
http://www.sdn.sap.com SAP NetWeaver http://service.sap.com microsoft http://www.microsoft-sap.com .NET Interoperability

Contact the CTSC-MS

ctsc@sap.com thomas.meigen@sap.com andre.fischer@sap.com

SAP AG 2005, 37

For More Information: Access the SAP Developer Network www.sdn.sap.com

The central hub for the SAP technology community
Everyone can connect, contribute, and collaborate consultants, administrators and developers Focus around SAP NetWeaver and SAP xApps

High quality of technical resources

Articles, how-to guides, weblogs, collaborative areas, discussion forums, downloads, toolkits, and code-samples

A collaboration platform, not a one-way street

SAP experts from customers, partners and SAP

SDN is powered by SAP NetWeaver

Built on the SAP Enterprise Portal Featuring collaboration capabilities of SAP Knowledge Management
SAP AG 2005, 38

7 Key Points to Take Home

Interoperability with non-SAP technology plays an important role in SAP NetWeaver SAP NetWeaver is the business foundation for SAP and Partners Microsoft is 95% Partner and 5% Competitor SAP PDK .NET is fully integrated with Visual Studio .NET SAP provides Single Sign-On (SSO) functionality to back-end systems Microsoft Windows supports all SAP components The Collaboration Technology Support Center (CTSC) is a joint team of experts from both Microsoft and SAP

SAP AG 2005, 39

Questions?

Franklin.herbas@sap.com
Franklin Herbas
franklin.herbas@sap.com
Product Manager SAP NetWeaver Web AS, SAP Labs

Q&A

SAP AG 2005, 40

Copyright 2005 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. SAP AG 2005, 41