Office Sap Implementation

8/8/2019 Office Sap Implementation

1/21

/

Duet Implementation Best PracticesWhitepaperPublished: July 2008For the latest information, see http://www.duet.com


2/21

Table of Contents

Executive Summary..............................................................................................3Introduction ...........................................................................................................4Planning the Architecture of a Duet Environment .................................................5

Duet Architecture and Landscape Overview .....................................................5Recommended Duet Landscapes .....................................................................6

Single Duet Host:...........................................................................................6Distributed Duet Host.....................................................................................7Scalability and High Availability Considerations.............................................8

Communication Flow Authentication ..............................................................9Where to find Duet Requirements and Documentation ...................................10

Hardware & Software Requirements ...........................................................10Sizing...........................................................................................................10Landscape Planning ....................................................................................10Installation and Configuration of Duet..........................................................10

Release Information.....................................................................................10Duet How to Guides and Blogs....................................................................10How to get started...............................................................................................11

Duet Project Team ..........................................................................................11Resource Requirements ..............................................................................11

Project Timelines.............................................................................................14Technical Training...........................................................................................15Duet Installation Flow ......................................................................................16

Duet Best Practices ............................................................................................17Project Planning ..............................................................................................17Installation .......................................................................................................18

Operations and Maintenance ..........................................................................20Conclusion ..........................................................................................................21


3/21

Executive Summary

By using Duet Software, companies can easily and quickly access SAP business processes anddata via their familiar Microsoft Office environment. Duet allows customers to leverage theirexisting Microsoft / SAP infrastructure, providing the Microsoft Office user with an intuitiveinterface to access and interact with business processes. These processes include: BudgetMonitoring, Leave Management, Time Management, Organization Management, TravelManagement, E-Recruitment Management, Reporting and Analytics, Sales Management,Demand Planning, Contract Life Cycle Management and Purchasing Management.

Duet is the result of a groundbreaking collaboration between SAP and Microsoft. It is designedto revolutionize how Information Workers interact with enterprise applications. Duet softwarebrings together the worlds of business productivity applications and enterprise applications. Itassists in not only improving the way the customer conducts business on a day-to-day basis, butallows customers to access disparate business processes exposed via SAPs Enterprise ServicesArchitecture.

In this whitepaper we will describe the various components that make up a Duet environment, a

proposed landscape, as well as scalability and high availability options surrounding Duet. In orderto assist customers in planning the deployment of Duet, a sample implementation timeline isprovided with discussions on resource requirements, available training and best practices takenfrom early Duet customer implementations.

For more details on the Duet Scenarios and their functionality, go to http://www.Duet.com.
http://www.duet.com/http://www.duet.com/


4/21

Introduction

Early Duet implementations have proven to be straightforward allowing customers to leverageexisting Microsoft and SAP investments already in place. The path to a successful Duetimplementation requires an understanding of :

The underlying Microsoft and SAP components involved A clear picture of who should be in the implementation team and what are their skills Things to consider in project timelines Implementation pre-requisites and installation Project best practices


5/21


6/21

Recommended Duet Landscapes

Single Duet Host:

The recommended landscape for a Duet deployment combines both Microsoft IIS (InternetInformation Server) services and SAP J2EE components onto a single standalone Duet Server.This single host will house the Duet Metadata Service, Request Service, SAP Duet Server andSAP Duet Add-On.


7/21

Distributed Duet Host

When implementing Duet, reliability and scalability are key concerns. The Duet architectureprovides the flexibility to also separate Microsoft and SAP components. This allows a customer toscale each independently based on required workload or firewall considerations.

As an example, the Duet Microsoft components can be deployed into a customers existing IISenvironment, using an existing SQL Server database to store the Duet Metadata. In addition,SAPs Duet J2EE components can be installed onto a NetWeaver Java Web Application Serverwithout affecting the backend ERP ABAP system.


8/21

Scalability and High Availability Considerations

The Duet Server can be broken out into multiple configurations for scalability and high availability.Because standard Microsoft and SAP technologies are used in a Duet environment, existingscalability methodologies can be implemented to improve performance.

For example, to scale the Microsoft IIS services on the Duet Server, an industry standard loadbalancer can be used. The SAP Java components can be scaled by following general SAPpractices used for a NetWeaver Java Web Application Server.

Similarly, standard high availability options can be used to provide increased reliability throughoutthe Duet landscape. For example, SAP Central Instance and database redundancy can beaccomplished using operating system cluster solutions.

Microsoft DuetComponents (IIS)

SAP DuetComponents

(NW Web AS Java)

SAP Backend(NW Web AS ABAP)

Scalability Windows LoadBalancing

F5 Networks

Add clusteredJ2EE nodes

Add Dialoginstances (AppServers)

High Availability MSCS Clustering Clustering

For more information on scalability and high availability solutions for a Duet environment,please refer to the Duet for Microsoft Office and SAP: SAP Operations Guide, found onthe SAP Service Marketplace at http://service.sap.com/instguides.
http://service.sap.com/instguideshttp://service.sap.com/instguides


9/21

Communication Flow Authentication

Providing a Single Sign-on experience for access to the backend SAP business processes, theDuet client is authenticated by the Duet Server using Windows authentication mechanisms (e.g.Active Directory, Kerberos etc.) Once authenticated, the Duet Server uses the SAP NetWeaverinfrastructure to provide the Duet client with a logon ticket. The Duet Client can thencommunicate directly with the backend SAP system, using a web service call to the ServiceBundle, fulfilling the client request (e.g. submit a leave request). When data needs to betransferred to the client, the backend SAP system communicates with the Exchange Server usingthe Request Handler on the Duet Server (e.g. manager receives an approve / reject email foremployees leave request).


10/21

Where to find Duet Requirements and Documentation

Hardware & Software RequirementsFor information about hardware and software requirements of the Duet components, refer to: Duet for Microsoft and SAP: Installation Guide in SAP Service Marketplace at:

http://service.sap.com/instguidesSAP xAppsDuetDuet 1.5 Duet Product Availability Matrix:http://service.sap.com/pam

Sizing Duet Sizing Guide:http://service.sap.com/sizing

Landscape Planning Duet for Microsoft Office and SAP: SAP Operations Guide in SAP Service Marketplace at:

http://service.sap.com/instguidesSAP xAppsDuetDuet 1.5

Installation and Configuration of Duet Duet for Microsoft and SAP: Installation Guide in SAP Service Marketplace at:

http://service.sap.com/instguidesSAP xAppsDuetDuet 1.5 Duet for Microsoft and SAP: SAP ERP Configuration Guide in SAP Service Marketplace at:

http://service.sap.com/instguidesSAP xAppsDuetDuet 1.5

Release Information Duet for Microsoft and SAP: Master Guide in SAP Service Marketplace at:

http://service.sap.com/instguidesSAP xAppsDuetDuet 1.5. Look in the sectionreferring to important notes.

Duet How to Guides and BlogsHow to Guides and Blogs for Duet can be found on the Service Marketplace:

Duet How To Guideshttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+how+to&cat=sdn_all

Duet Blogshttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+blog&cat=sdn_all

* Note: As of July 30, 2008, the SAP Service Marketplace only has documents related to Duet1.5 SP0 and not Duet 1.5 SP1. The documents for Duet 1.5 SP1 will get published in the near

future as we get closer to the new release availability.
http://service.sap.com/instguideshttp://service.sap.com/pamhttp://service.sap.com/sizinghttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+how+to&cat=sdn_allhttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+how+to&cat=sdn_allhttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+blog&cat=sdn_allhttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+blog&cat=sdn_allhttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+blog&cat=sdn_allhttps://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+how+to&cat=sdn_allhttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/sizinghttp://service.sap.com/pamhttp://service.sap.com/instguides


11/21


12/21

Business Expert(s)

Having someone on the project who can provide the functional (business configuration) expertiseis important. The business expert(s) must ensure that the application associated to the Duetscenario being installed is fully functional and configured in the backend SAP system(s) so thatthey can be executed independently of Duet. For example, for the Time Management scenario, a

business expert will ensure that time entries can be submitted correctly via the CATS applicationin the SAP Backend system.

Duration: Part time during Planning, Preparation and Testing phases. They should be availablefor the Installation phase just in case there are issues in the backend functionality.

Skill Set: This depends on the scenario that is implemented. For example, if the Duet HRscenarios are being implements ( Time and Leave Management etc), then the business expertmust have expertise in SAP HCM, ESS/MSS and CATS applications.

NetWeaver Expert(s) -Web AS JAVA and ABAP

Resources with expertise with the SAP Web AS ABAP and Java are required.

Duration: Full time throughout Planning, Installation, Testing and go-live phases

Skill Set:ABAP: SAP Backend System Patching / Transports/Communication configuration, SAPAuthorization (User Setup)Web AS Java: J2EE installation, security configuration based on the NetWeaver Java WebApplication Server with configuration of trust systems, connecting Active Directory to UserManagement Engine (UME), Kerberos for encrypted authentication etc.

Technical Expert(s)

Resources with expertise with various Microsoft components are required.

Duration:Not required full time for the entire project but must be available for any specific taskas required.

Skill Set: Microsoft ADS ( User setup / Troubleshooting ) Microsoft Exchange Server ( Troubleshooting ) Software Deployment ( Client Roll out, System Management Server (SMS) ) Domain Administration ( Preparation )


13/21


14/21

Project Timelines

The following project plan is an estimate based on early Duet implementations performed byMicrosoft and SAP. The proposed timeline is based on the following assumptions:

Prerequisites mentioned in previous section are already in place 1 Duet scenario 10 production users *2 Tier landscape One Dev/QA Landscape and One Production Landscape

*Note: Based on past Duet production installations, a 2 tier landscape has been sufficientbecause Duet uses current business processes. A 2 tier landscape will keep costs ofimplementing low. A 3 tier landscape can also be used if desired.


15/21

Technical Training

Since Duet reuses existing investments taken from your current Microsoft and SAP environment,technical training of the resources involved while implementing Duet should focus on the Duetconfiguration itself. Online learning maps are available on the SAP Service Marketplace with Duettraining classes being delivered by both Microsoft and SAP. Additional information and educationmaterial is located at http://service.sap.com/education.

An alternative method of training can include implementing a small test environment which canhelp with hands-on education. Duet installation and configuration guides are available on the SAPService Marketplace: http://service.sap.com/instguides-> xApps -> Duet.
http://service.sap.com/educationhttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/education


16/21

Duet Installation Flow

To complete setup and deployment of Duet, install Duet components in the following order:

1. Install Duet Server components from Microsoft.The Duet Server components from Microsoft are provided as two installers:

Microsoft.OBA.MetadataService.msi

Microsoft.OBA.RequestHandler.msi

2. Install and configure the Duet Server/Add-On from SAP.

3. Install and configure the Duet business applications on the SAP Duet Add-On host.

4. Install and configure the Duet client components from Microsoft on client computers.


17/21

Duet Best Practices

Project PlanningThe project planning phase for deploying Duet will vary from customer to customer. When

planning for a Duet implementation, the following best practices are recommended:

Complete horizontal coordination and communication between various groups within acompany is mandatory

Duet requires a horizontal as well as vertical collaboration within a company. This product touches various departments such as SAP systems, Exchange Systems,

Security, J2ee, business groups, desktops etc. Availability and the communication within these groups will strongly influence the success,

acceptance and timelines of the installation. Ensure the business community driving the Duet implementation are included in the planning

Phase

Start with a Phased versus a Big Bang Approach

Starting with a phased approach will help to quickly isolate any issues that may arisespecific to your environment. With Duet, there are interdependencies between thevarious systems (ABAP, J2EE, Internet Information Server, SQL Server, ExchangeServer, Active Directory and the Microsoft Office client).

A phased approach can be grouped by users, backend systems, scenarios etc.

Ensure Resource Availability

Customer Internal Dedicated Resource Experienced Duet Resources SAP Business Expert who knows internal business processes Engage the Exchange / ADS group and the Security group as early as possible as users

need to be created and security needs to be considered

Determine Strategy for Duet installation on Users Client machines

Carefully plan how Duet will be deployed on user machines for production with minimaleffort / time by the user

Test installation method on test machines or selected users before doing a mass roll out

Group(s) within a company must own Duet once it is live

Assignment of who is responsible for monitoring and making future decisions about

upgrades, new scenarios etc. is required Clear plan and team assignment for Operations / Administration / Support after the Go-

live is critical at the beginning of the project and must encompass data flow systems fromDesktop to Duet Server to Exchange to SAP Backend systems.


18/21

Document your System Landscape

Because of the various servers, services and tools used during a Duet implementation, itis important to document system hostnames, locations, IP addresses, operating systemaccounts, J2EE passwords, Visual Administrator accounts, SDM (Software DeploymentManager) passwords, SAP Agent accounts, SAP backend ABAP accounts, etc.

Ensure all pre-requisites are in place before starting the Duet Installation

For details on the Duet pre-requisites, refer to theDuet for Microsoft and SAP: Installation

Guide in SAP Service Marketplace

SAP Backend Systems must be patched to the pre-requisite level and any extra noteshave been applied see Duet 1.5 Release Information NoteSAP Backend Applications associated to Duet Scenarios must already be configured sothat they can be used independent of DuetUse the Duet Check Tool delivered in the SAP Backend to check for some of thebackend pre-requisites this tool can be found in the Duet IMG, transaction SIMGH inthe master SAP system backend.

Duet Landscape must be built (hardware and software pre-requisites in place) on theDuet server(s) and the Duet clientsUsers must be given the correct SAP authorizations in the SAP Backend System

Consider System Patching requirements when creating timelines

Patching systems may require additional time for QA application testing before patchescan be moved to production.

Installation


19/21


20/21


21/21

Documents

Office Sap Implementation