Developing Applications with the SAP .Net PDK and .Net Connector

1. Developing Applications with the SAP .Net PDK and .Net Connector Matt Schababerle Lenny Terris Senior Architect Senior Consultant

2. Learning Points • Understand the capabilities of the .Net PDK and .Net Connector • Learn how to leverage SAP and Microsoft tools in an SOA architecture • Lessons learned using the .Net Connector and .Net PDK

3. Agenda • SAP – Microsoft Interoperability Overview • .Net PDK Architecture & Features • .Net Connector Architecture & Features • Demonstration Scenario • Demonstration • Lessons Learned

4. SAP – Microsoft Interoperability Overview

5. SAP / Microsoft Interoperability History • SAP and Microsoft have been integration partners for over 10 years, starting with the first release of R/3 on Windows NT in 1994. • The partnership has deepened over the years as Microsoft / SAP usage has increased. • Over half of all SAP installations, approximately 58,000 have occurred on the Windows platform • One quarter of all SAP installations occur on MS SQL Server • Microsoft has been running SAP R/3 as its ERP system since 1995 and has also implemented BW, APO, GTS, and SCEM • SAP Development staff is co-located with SQL development team in Redmond

6. SAP / Microsoft Interoperability Timeline • Over time, SAP has increasingly recognized the need for customers to integrate their Microsoft applications into their SAP environment. • April 1994 – First R/3 release for Windows NT • August 1995 – SQL Server Support. • January 1997 – Integration with MS Exchange • October 1997 – DCOM Support • Feb 2000 – mySAP.com / Windows 2000 Launch • April 2003 – SAP Support for Windows Server 2003 • May 2004 – SAP Netweaver / Microsoft .Net Interoperability announcement • April 2005 – SAP and Microsoft announce Mendocino Initiative

7. SAP NetWeaver™ PEOPLE INTEGRATION Multichannel access … Portal Collaboration INFORMATION INTEGRATION Bus. Intelligence Knowledge Mgmt Master Data Mgmt Composite Application Framework Lifecycle Management PROCESS INTEGRATION Integration Broker BusinessProcess Mgmt APPLICATION PLATFORM J2EE ABAP DB and OS Abstraction SAP Netweaver / Microsoft Interoperability Overview • Recognizing that it’s customers have made investments in other technology solutions, SAP has chosen to partner with IBM and Microsoft to develop interoperability solutions. • Microsoft and SAP have similar applications and interoperability options at every level of the Netweaver stack.

8. Why Use the .Net Toolkits ? • SAP Customers have heavily invested in Windows-based infrastructure and training for their personnel • Many customers have developed custom applications, sometimes mission critical, that can benefit from integration with SAP applications • These customers want to leverage their SAP and .Net Investments by integrating the two environments • Combining .Net and SAP application development allows customers to combine the best of both worlds

9. SAP Netweaver IT Practices & Scenarios .Net PDK & Connector

10. .Net PDK Architecture & Features

11. Runtime .Net PDK Architecture • .Net Components are developed in Visual Studio 2003 using the SAP .Net PDK Add-in and deployed to SAP Netweaver Portal • Portal Runtime for .Net enables .Net components to communicate with other Portal components and external systems

12. .Net PDK Features • Fully integrated with Visual Studio 2003 • Hot deploy & preview components directly in the portal from Visual Studio • Debug components on local machine • Supports Team development on single shared portal • Help Files integrated into Visual Studio Help • Project template for portal applications in Visual Studio • Portal Component and System Templates • SAP .Net UI controls inherit portal look & feel (Expanded in version 2.0) • Design portal pages directly in Visual Studio (New in Version 2.0) • Portal Style Designer extends portal styles to non-SAP UI components (New in Version 2.0) • Object Based Navigation features supported (New in Version 2.0) • Multiple options for deploying .Net Applications to the portal (Enhanced in Version 2.0)

13. .Net PDK Installation & Configuration Installation • Use Setup Wizard to install portal add-in for Visual Studio • Install Portal runtime for .Net • Install Java - .Net interoperability components using SDM Configuration • Assign Logon Account to Portal Runtime for .Net Service • Define Server in Microsoft Management Console (MMC) • Configure .Net Portal Services in Enterprise Portal • See OSS Central Installation Note 800842 for installation details • OSS Notes 846408 (v1.0 Patch 3) and 898153 (v2.0) have installation validation tools attached to the notes as zip files

14. .Net PDK Visual Studio Interface

15. .Net Connector Architecture & Features

16. .Net Connector High Level Architecture

17. .Net Connector Features • The .Net Connector and Proxy Wizard allow you to: • Write .NET Windows and Web form applications that access SAP remote enabled functions (RFC) • • Create client applications for the SAP server using either RFCs or HTTP/SOAP/XML (outside-in) • • Develop RFC server applications that run in a .NET environment and can be implemented from within the SAP System (inside-out) • Development Can take place entirely within Visual Studio • • Use the Proxy Wizard integrated in Microsoft Visual Studio .NET to generate proxy objects that are easy to use • • Use any common programming language that has full access to the Microsoft .NET Framework • • Use IntelliSense help in Microsoft Visual Studio .NET through strongly typed data models and method signatures • • Bind SAP tables and structures to Windows and Web form controls (DataBinding) • • Use security authentication methods such as Single Sign-on, Kerberos, and Microsoft Passport • The .Net Connector is also packages as the Microsoft Biztalk SAP Adapter. This provides a smooth development path for customers implementing Biztalk with previous .Net Connector experience

18. Installation & Configuration – SAP Connector • Prerequisites: • Microsoft Visual Studio .NET 2003 • Java Runtime Environment (JRE) 1.3 or later • Required for proxy generation • Not needed once proxies have been generated • If you are using a Java VM other than the Sun Java VM version 1.3 (including newer Sun Java VM versions) you must have a registry entry pointing to your Java VM like the following: • [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft] • [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment] • “CurrentVersion”=“1.3” • [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.3] • “JavaHome”=“C:\\Program Files\\IBM\\Java13\\jre” • Installation Packages: • • SAP Connector for Microsoft .NET 1.03 Installation for Visual Studio 2003 • Full version installation for development computers with Visual Studio .Net 2003 • SAP Connector for Microsoft .NET 1.03 Runtime Installation • Runtime installation for deployment computers

19. Installation & Configuration – BizTalk Adapter for mySAP v2.0 • Prerequisites: • Microsoft Visual Studio .NET 2005 • Microsoft BizTalk Server 2006 • Including all BTS 2006 prerequisites • SAP .NET Connector version 1.0.3 • Newer versions of the SAP .NET Connector have been released but at the time of this presentation, the Adapter is dependent on this specific version of the SAP .NET Connector • Installation Packages: • Microsoft BizTalk Adapter v2.0 for mySAP Business Suite • Microsoft BizTalk Adapter v2.0 for mySAP Business Suite Service Pack CTP • Configuration • Create a Send Port in BizTalk that uses the SAP Adapter • Provide SAP Connection information: such as Client, System ID, etc. • Use XMLTransmit and XMLReceive Pipelines

20. Demonstration Scenario

21. Scenario Background: • A Hitachi Consulting customer was interested in developing a proof of concept to demonstrate the benefits of a custom user interface for casual SAP users. The scope of the project included: • Developing a user interface for purchase requisition approval and goods receipts • Deploying the solution to the customer’s SharePoint portal environment • Developing an alerting mechanism to notify users of purchase requisitions awaiting their approval • The solution was developed using Visual Studio 2003, SharePoint Portal Server, Biztalk Server 2006 with the SAP .Net Connector, and SAP R/3 Enterprise 4.7 • User Interface developed in Visual Studio and deployed to SharePoint environment • SAP Integration developed using Biztalk Orchestrations and SAP .Net connector to communicate with SAP BAPI’s • Alerting mechanism developed using Windows Workflow Foundation

22. Scenario Background Continued: • After delivering the proof of concept to the customer, Hitachi Consulting redeployed the user interface from SharePoint to Enterprise Portal for demonstration purposes using the SAP .Net PDK. This allows a side by side comparison of the two user interfaces supporting the same process. It also demonstrates the flexibility and reusability of components developed in a Services Oriented Architecture framework. • Today’s demonstration will have 3 parts: • Demonstrate SharePoint Portal Interface • Demonstrate Enterprise Portal Interface • Demonstrate process for developing and deploying components to the Enterprise Portal environment.

23. Users Purchase Purchase Requisition Delivery Approver Receiver Presentation Layer Operational Mgmt Security Windows SharePoint Portal Server Purch . Req . List Purch . Req . Purch . Order List Purch . Order Webpart Detail Webpart Webpart Detail Webpart Exception Authentication Management Configuration Authorization Service Layer ASP . NET Application BizTalk ( Web Services ) Notification Enterprise SSO BizTalk Server 2006 BizTalk Adapter for SOAP GetPurchReqs ApprovePurchReq GetPODetail GetPurchReqDet GetPOs POGoodsReceipt Orchestration BizTalk Adapter for mySAP SAP Interface ( SAP . NET Connector , SAP Application Server ) Data Layer Common Data Model SAP R / 3 ( Oracle or SQL ) Solution Architecture 1 • Presentation layer, business logic, and data persistence are separated. • Process integration is accomplished using MS Biztalk Orchestrations and Windows Workflow foundation. • Communication with SAP via RFC’s or Web Services facilitated by SAP .Net Connector • Services Oriented Architecture Solution

24. Users Purchase Purchase Requisition Delivery Approver Receiver Presentation Layer Operational Mgmt Security SAP Enterprise Portal Server Purch Req List Purch Req Purch Order List Purch Order iView Detail iView iView Detail iView . . . . . . Portal Runtime for Microsoft .Net Exception Authentication Management Configuration Authorization Service Layer ASP . NET Application BizTalk ( Web Services ) Notification Enterprise SSO BizTalk Server 2006 BizTalk Adapter for SOAP GetPurchReqs ApprovePurchReq GetPODetail GetPurchReqDet GetPOs POGoodsReceipt Orchestration BizTalk Adapter for mySAP SAP Interface ( SAP . NET Connector , ) SAP Application Server Data Layer Common Data Model SAP R / 3 ( Oracle or SQL ) Solution Architecture 2 • SAP Enterprise Portal is substituted for SharePoint • Portal executes .net applications via Portal Runtime for .Net • Separation of presentation layer from business logic, combined with .Net interoperability tools, allows substitution of components without major redevelopment effort. • Services Oriented Architecture Solution

25. Demonstration

26. Key Learnings • The .Net PDK is very simple to install and well integrated with Visual Studio. Very small learning curve for experienced .Net Developers • Deployment of .net components to the portal is smooth and reliable • .Net developers using the PDK will benefit from training on the Enterprise Portal PCD and content administration. • Installation is the trickiest part of using the SAP Adapter, once configured using the SAP Adapter is relatively easy • The SAP Adapter enables the generation of schemas based on RFCs • These schemas can then be used by BizTalk to generate messages to be sent to and received from SAP • By default, each call to SAP is contained within its own transaction • This is not conducive to calls that require a commit work to be submitted after successful submission – such as BAPI_GOODSMVT_CREATE • It is possible to manipulate the transaction through message headers within a BizTalk Orchestration • The SAP Adapter is a little finicky and can sometimes produce errors that are not very helpful

27. Q & A Matt Schababerle Senior Architect Hitachi Consulting www.hitachiconsulting.com Direct: 713.458.5029 Mobile: 281.772.3604 mschababerle@hitachiconsulting.com Inspiring your next success! ®

28. Additional Resources • SAP Developer Network https://www.sdn.sap.com/irj/sdn/developerareas/dotnet • SAP Marketplace https://service.sap.com/netweaver (requires login) PDK Menu Path: SAP Netweaver ->Netweaver in detail -> People Integration -> Portal -> Portal In Detail .Net Connector menu Path: SAP Netweaver ->Netweaver in detail -> Application Platform -> Connectivity -> Connectors • Microsoft-SAP http://www.microsoft-sap.com/technology.aspx

29. 1608 Session Code: