Interoperability Ms Sap Part Ii

Interoperability between SAP Portal and MicroSoft SharePoint Presented By Visit us at Richa Roy Booth #530 Name SAP NW Advisor & Client Partner Sapphire 2009 ProSoft CyberWorld Group 11th – 15th May , Orlando FL richa.roy@prosoftcyberworld.com

Agenda • Recap of first webinar • Why Interoperability between MicroSoft Portal and SAP? • MOSS Platform Features • Business Data Catalog • MicroSoft Centric View Of Interoperability • How to Set up SSO Between Two Portals • Roadmap For Interoperability Between SAP Portal and MOSS • Q&A

Agenda • Recap of first webinar • Why Interoperability between MicroSoft Portal and SAP? • MOSS Platform Features • Business Data Catalog • MicroSoft Centric View Of Interoperability • How to Set up SSO Between Two Portals • Roadmap For Interoperability – SAP & MicroSoft • Q&A

Recap of First Webinar • History of SharePoint Portal • History of SAP Portal • Why Interoperability between SAP Portal and MicroSoft Sharepoint Portal • Which Portal should take lead ? • SAP Centric View Of Interoperability • MicroSoft Centric View Of Interoperability

Why SAP NW interoperability with .NET?

Why Interoperability between SAP NW Portal and MOSS ? Both SAP NW Portal and MicroSoft Sharepoint portal are increasingly being deployed synchronously in the same companies and organizations. To complete the information flow within the organizations interoperability between these two portals is must.

Why Interoperability Between MicroSoft Portal and SAP ? • Because it’s needed – In a co-existent scenario • Customers rely on SAP for human resources, finance, sales and distribution, material management. • Customers also rely on MOSS for collaboration, document management – Issue • Transactional/ Structural information stored in SAP is not available for information workers in their day-to-day work environment for example – MOSS The process of “Creating Customer Order” involves SAP for only about 15% of the activity. Rest 85% activities like collaborating on documents, talking to subject matter experts and analyzing information occurs outside of SAP and in an disconnected environment.

Why Interoperability Between MicroSoft Portal and SAP ? • Because it’s possible • New innovation in MOSS 2007 enable customers to make MOSS 2007 a dynamic consumer of SAP services and processes • Achieved in a almost code – free environment • Because it’s advantageous • Integrate tool for ad hoc communication, collaboration and information management into SAP’s structured work environment • Empowering information workers to solve problems that fall outside the specifications of existing processes • Enabling employees to use electronic forms, automate data, providing real time information using their familiar environment

Agenda • Recap of first webinar • Why Interoperability between MicroSoft Portal and SAP? • MOSS Platform Features • Business Data Catalog • MicroSoft Centric View Of Interoperability • Gaps and Areas of Improvement • How to Set up SSO Between Two Portals • Roadmap For Interoperability – SAP & MicroSoft • Q&A

MOSS 2007 Platform – New Features Server Farm Web App Web App Web App Web Application Site Collection Site Collection Site Collection Site Collection Sites Lists Libraries Sites Lists Libraries Sites Lists and Libraries Documents Items Folders

MOSS 2007 Platform – New Features • MOSS 2007 provides better business capabilities by adding new features to it’s Portal platform – Business Intelligence – Unified Communication and Collaboration – Enterprise Search – Enterprise Content Management

MOSS 2007 Platform – New Features • MOSS moved the code required for following in the infrastructure as oppose to individual front-end application – Connection – Communication – Identity Management • Introduced “Business Data Catalog”

Agenda • Recap of first webinar • Why Interoperability between MicroSoft Portal and SAP? • MOSS Platform Features • Business Data Catalog • MicroSoft Centric View Of Interoperability • Gaps and Areas of Improvement • How to Set up SSO Between Two Portals • Roadmap For Interoperability – SAP & MicroSoft • Q&A

Business Data Catalog • New business data feature introduced in MOSS 2007 • Provides an easy, code-free (almost) way to integrate business data from back-end server applications – SAP, Siebel • Bridges the gap between Portal site and business applications • Enables you to bring key data from various business applications to MOSS 2007 – lists, web parts, search, user profile, and custom applications

Business Data Catalog - High Level Architecture

Business Data Catalog • BDC design is based on standardized metadata – Describes the location and format of back-end system and data entities defined in that system • Connectivity with traditional ERP systems – Web services • Connectivity with database systems – ADO.NET providers • Display BDC application data within portal site ( Out-Of-The-Box) – Business Data Web Parts – Lists – Search – Custom Solutions – User Profile Importer

Business Data Catalog Application Describe information that is supplied by back end system in terms of “entity”- Definition – things that business users would want to search for or on which they might XML file want to take an action. Eg- customer order, account Identifiers Properties Methods Name of web service operations and the parameters that are required to call them. For systems that are accessible via web services Names of stored procedures and SQL statements for systems that are databases BDC – Shared Services MOSS Portal BDC Application

Business Data Catalog • Creating “entity” in SAP system for consumption in BDC – Custom BAPI Objects • Combine discrete BAPI’s into consumable business entities – SAP Enterprise Services • SAP delivered enterprise services – Custom Web Services • Develop new web services – Custom MicroSoft BizTalk Server Orchestration • Creating discrete orchestration that manage the necessary RFC and BAPI calls

Business Data Catalog • MOSS 2007 ships out with four out-of-the-box business data web parts • Purpose is to display business data in a portal application without need of any programming • These web parts are generic and can show any type of data “entity” registered in Business Data Catalog

Integration using PDK for .NET • Portal Development Kit for MicroSoft .NET ( PDK for .NET) can be used to create iViews for SAP NW Portal. • Three components of PDK for .NET are – Portal Add- In for Visual Studio • An extension to Visual Studio 2005 • Used to build, deploy and debug portal components in .NET – Portal Runtime for MicroSoft .NET • Processes .NET components at runtime – Java -.NET Interoperability framework Portlets created using PDK for .NET can be used both in • A mechanism that enables API calls between Java Stack SAP Portal and MOSS Portal and .NET stack. Allows to access java based portal services from .NET code

Integration using MOSS iView Web Part • Steps for creating MOSS iView Web Part – Managing the list of trusted SAP hosts • TrustedSAPHostsConfig.xml – Configure SSO between MOSS and SAP Portal – Creating iView Web Parts in MOSS 2007 • Edit the page and add the iView Web Part to the page • Then you can configure iView by pasting the relative URL of the iView to the Web Part tool pane. – Creating an iView Web Part catalog • Central repository of pre-defined iView Web Parts • Export iView definition to a file on the file system and then import the iView definition to the Web Part gallery.

Integration using WSRP consumer Web Part • Manage the list of trusted WSRP Producers – TrustedWSRPProducers.config – Add SAP Portal as WSRP producer to this list • Configure SSO between MOSS and SAP Portal • Create WSRP web part in MOSS portal – Edit the page and add WSRP web part to the page • Add your WSRP compliant content to your web part

Integration using BSP Pages • Business Server Pages – SAP’s page development environment – BSP applications are rendered through web browser – BSP can be wrapped using ASP’s and rendered into MOSS 2007

Integration Using MicroSoft .NET Data Provider • The .NET Data Provider for SAP NetWeaver BI is officially certified to report on SAP NetWeaver Business Intelligence • Included in the SQL Server 2005 Reporting Service SP1 • BW acts as a data source for SQL Server Reporting Services (SSRS) using .NET Data Provider for SAP NW BI • The .NET Data Provider for SAP NetWeaver BI uses the SAP BW XMLA interface • SSRS reports can be based on any query created by the SAP BW query designer

Scenario – Workflow Integration • Define organizational-level workflow using SAP data • Windows Workflow Foundation – Integrated with MOSS 2007 – Create Workflow • Out-Of-The-Box workflow • Custom code-free workflow using MicroSoft Office SharePoint Designer • Bring in SAP data using BDC and display in Business Data Web Part

Scenario – Analyze SAP Data in Excel 2007*** • Consume, analyze and model SAP information in Office Excel 2007 with no code • Office Excel 2007 – Render model and presentation items from spreadsheet • Display SAP information in Office Excel 2007 – Charts, PivotTables • Publish the workbook to Office SharePoint server 2007 site • Information Worker can see this information in relation to other relevant information – For example customer sales chart shown next to key customer contact information in a web part in MOSS 2007

Scenario – Forms Driven Business Processes • Create forms driven business process in MOSS with SAP data – InfoPath Forms Services • A new feature of MOSS 2007 • Scalable, security-enhanced, standard-based form solution • Create forms using – Traditional Office InfoPath rich client – New MicroSoft Visual Studio Editor – Build InfoPath forms that consume and present web services – Use 100% browser-based front-end to work with SAP information

How to Set Up SSO Between Two Portals • SSO is required for all SSO scenarios • Steps for SSO configuration – Configure and start MOSS 2007 SSO service – Configure MOSS 2007 SSO settings – Set encryption key – Manage SAP Enterprise Application Definition – Specify SAP Application User Account Mapping

Configure and Start MOSS 2007 SSO Service • A service account is used to activate SSO service • SSO service account must meet following criteria – A domain user account, not a group account. – An Office MOSS 2007 farm administrator account. – A member of the local Administrators group on the encryption-key server, the first server that the Single Sign On is enabled. – Be either the same as the MOSS 2007 Single Sign-on administrator account or a member of the same administration group that the SSO administrator belongs to. – Have “Log on As a Service” user rights assignment in local security policy settings • Use Windows Server Management Console to activate SSO service – SSOSRV

Configure MOSS SSO Settings • Enter SSO Administrator Account Information in central administrator • SSO Administrator Account specifies the set of people who can – Create, delete or modify application definitions – Back up encryption key • If a group is specified here all the members of this group must be member of local administrator group on encryption key server

Set Encryption Key • First server in the server farm that has SSO enabled becomes the encryption key server • Encryption key server generates and stores the encryption key • Encryption key is used to encrypt/decrypt the credentials that are stored in the SSO database • Encryption key is generated using Central Administration • Note – Do not forget to check the check box “Re-encrypt all credentials using the new encryption key” • You can also select media to back up encryption key in section “Encryption Key Backup In Drive”

Manage SAP Enterprise Application Definition • Enter following information for creating new SSO definition for SAP application – Display Name • Enter name that users will see when prompted for credentials – Application Name • Name of SSO application – Contact • Email address of the person responsible for SSO definition – Account Type • Choose “Individual” if every MOSS user will be mapped to a single unique SAP account • Choose “Group” if a group of MOSS users will be mapped to a single SAP account – Windows Authentication • Check this checkbox if SAP Portal uses windows authentication

Specify SAP Application User Account Mapping • Enter following information – Enterprise Application Definition • Same as Display Name from previous setting – User Account Name • Provide MOSS user account in domainuser logon format – Provide SAP Account Information • User Name/ Password for SAP application

History of MicroSoft and SAP Relationship

Collaboration Technology Support Center (CTSC) • Joint team of experts from SAP and MicroSoft • Provide guidance and help for better integration between SAP and MicroSoft products • CTSC maintains neutral position between SAP and MicroSoft towards customers and partners

Roadmap for Interoperability – Front End Interoperability Support users in their daily business MicroSoft NetWeaver Mobile Smart Rich Web Apps Office Portal Devices Client Client Channels .NET Web Visual Web Java Framework Dynpro Composer Services Technologies Benefits and Values Reuse of existing software and component Flexibility of choice Familiarity with existing user interfaces

Roadmap for Interoperability – Front End Interoperability • Office – Project Duet ( Formerly known as Mendocino) – Pre-packaged scenarios • Time Management • Budget Monitoring • Leave Management • Organization Management – Open for development of custom scenarios – Supports pluggable services • Portal Interoperability • SAP Mobile App

Roadmap for Interoperability – Service Oriented Architecture • Permits composition of business processes by connecting applications and components through web services • Supported by both MicroSoft and SAP

Roadmap for Interoperability – Development Paths SAP NetWeaver™ Microsoft .NET PORTAL FRAMEWORK Mobile Enterprise Portal Duet APPLICATION DEVELOPMENT Enterprise Service Architecture NetWeaver Developer Studio SAP Portal Microsoft .NET Framework IBF / Web Visual Development Duet Dynpro Composer Kit for Infrastructure Visual Studio Microsoft .NET Service Oriented Architecture (ESA, SOA) APPLICATION PLATFORM mySAP Solutions .NET Applications SAP NetWeaver Microsoft .NET Based on Web Services and open standards protocols Based on other protocols SAP Centric Applications

Roadmap for Interoperability – Development Paths SAP NetWeaver™ Microsoft .NET FRONTEND Custom Duet Office Mobile Application Sharepoint APPLICATION DEVELOPMENT Enterprise Service Architecture NetWeaver Developer Studio Microsoft .NET Framework IBF / Smart Client ASP .NET Duet WinForms WebForms Infrastructure Visual Studio Service Oriented Architecture (ESA, SOA) APPLICATION PLATFORM mySAP Solutions .NET Applications .NET Connector SAP NetWeaver Microsoft .NET Based on Web Services and open standards protocols Based on other protocols MicroSoft Centric Applications

Roadmap for Interoperability- End To End Identity Management SAP NetWeaver™ SAP NetWeaver Portal Sharepoint Portal Single Sign-On SPNego mySAP Business Suite Exchange and SAP R/3 CRM ERP R/3 HR … User Management Active UME CUA Directory MIIS SAP Net Weaver Application Server Microsoft Windows Server

Richa Roy SAP NW Advisor richa.roy@prosoftcyberworld.com (732)579-7406 Visit us at Booth #530 Sapphire 2009 11th – 15th May , Orlando FL

References • Whitepaper “Integrating MicroSoft SharePoint Server 2007 and SAP” at http://msdn.microsoft.com • http://msdn.microsoft.com/en-us/library/ms546541.aspx • http://download.microsoft.com/download/9/c/1/9c1d7e04- ce95-4bb4-809d- 3bfdf6739769/OV_CTSC_SAP_MS_Partnership.ppt • https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/libr ary/uuid/d5f7d1b2-0701-0010-eb9c-cc9579b797f5

Interoperability Ms Sap Part Ii

0 comments

Notes on slide 1

Favorites, Groups & Events