Professional Documents
Culture Documents
Net Connector
Matt Schababerle Senior Architect Lenny Terris Senior Consultant
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
Agenda
SAP Microsoft Interoperability Overview .Net PDK Architecture & Features .Net Connector Architecture & Features Demonstration Scenario Demonstration Lessons Learned
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
INFORMATION INTEGRATION Bus. Intelligence Knowledge Mgmt Master Data Mgmt PROCESS INTEGRATION Integration Business Broker Process Mgmt APPLICATION PLATFORM J2EE ABAP DB and OS Abstraction
Combining .Net and SAP application development allows customers to combine the best of both worlds
Runtime
Portal Runtime for .Net enables .Net components to communicate with other Portal components and external systems
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
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
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
Demonstration Scenario
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 customers 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 BAPIs Alerting mechanism developed using Windows Workflow Foundation
Solution Architecture 1
Users Purchase Requisition Approver Purchase Delivery Receiver
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 RFCs or Web Services facilitated by SAP .Net Connector
Operational Mgmt
Security
Exception Management
Authentication
Configuration
Authorization
Service Layer
Notification
GetPurchReqs
ApprovePurchReq
GetPODetail
GetPurchReqDet
GetPOs Orchestration
POGoodsReceipt
Solution Architecture 2
Users Purchase Requisition Approver Purchase Delivery Receiver
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.
Operational Mgmt
List .
Security
Exception Management
Authentication
Configuration
Authorization
Service Layer
Notification
GetPurchReqs
ApprovePurchReq
GetPODetail
GetPurchReqDet
GetPOs Orchestration
POGoodsReceipt
Demonstration
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 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
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!
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