/

Duet Implementation Best Practices

Whitepaper
Published: July 2008
For the latest information, see http://www.duet.com
Table of Contents
Executive Summary ..............................................................................................3
Introduction ...........................................................................................................4
Planning the Architecture of a Duet Environment .................................................5
Duet Architecture and Landscape Overview .....................................................5
Recommended Duet Landscapes .....................................................................6
Single Duet Host:...........................................................................................6
Distributed Duet Host.....................................................................................7
Scalability and High Availability Considerations.............................................8
Communication Flow – Authentication ..............................................................9
Where to find Duet Requirements and Documentation ...................................10
Hardware & Software Requirements ...........................................................10
Sizing...........................................................................................................10
Landscape Planning ....................................................................................10
Installation and Configuration of Duet..........................................................10
Release Information.....................................................................................10
Duet How to Guides and Blogs....................................................................10
How to get started...............................................................................................11
Duet Project Team ..........................................................................................11
Resource Requirements ..............................................................................11
Project Timelines.............................................................................................14
Technical Training ...........................................................................................15
Duet Installation Flow ......................................................................................16
Duet Best Practices ............................................................................................17
Project Planning ..............................................................................................17
Installation .......................................................................................................18
Operations and Maintenance ..........................................................................20
Conclusion ..........................................................................................................21
Executive Summary

By using Duet Software, companies can easily and quickly access SAP business processes and
data via their familiar Microsoft Office environment. Duet allows customers to leverage their
existing Microsoft / SAP infrastructure, providing the Microsoft Office user with an intuitive
interface to access and interact with business processes. These processes include: Budget
Monitoring, Leave Management, Time Management, Organization Management, Travel
Management, 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 designed
to revolutionize how Information Workers interact with enterprise applications. Duet software
brings together the worlds of business productivity applications and enterprise applications. It
assists in not only improving the way the customer conducts business on a day-to-day basis, but
allows customers to access disparate business processes exposed via SAP’s Enterprise Services
Architecture.

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 order
to assist customers in planning the deployment of Duet, a sample implementation timeline is
provided with discussions on resource requirements, available training and best practices taken
from early Duet customer implementations.

For more details on the Duet Scenarios and their functionality, go to http://www.Duet.com.
Introduction
Early Duet implementations have proven to be straightforward allowing customers to leverage
existing Microsoft and SAP investments already in place. The path to a successful Duet
implementation 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
Planning the Architecture of a Duet Environment
Providing a highly available and scalable solution is required for Duet’s business critical
processes. This is accomplished by understanding the components that make up the Duet
architecture and how data is exchanged between Microsoft and SAP technologies.

Duet Architecture and Landscape Overview

The basic Duet architecture consists of three core components that a customer should deploy for
a basic implementation.

These are:
ƒ The Duet Client
This is the presentation layer of the architecture.

ƒ The Duet Server consisting of Microsoft and SAP Components

The Duet Server provides the necessary authentication mechanism, the metadata
defining available ESA web services for each scenario, the Exchange Server Interface
and the Active Directory-to-SAP user mapping.

ƒ SAP ERP / CRM / SRM / SCM / BI backend(s) (Can be multiple backend systems).
SAP is the line of business system from which the customer retrieves their business
critical data. Additional functionality can be introduced using optional pluggable services
such as customizable links to a corporate portal (SAP Enterprise Portal or Microsoft
Office SharePoint).
Recommended Duet Landscapes
Single Duet Host:

The recommended landscape for a Duet deployment combines both Microsoft IIS (Internet
Information 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 and
SAP Duet Add-On.
Distributed Duet Host

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

As an example, the Duet Microsoft components can be deployed into a customer’s existing IIS
environment, using an existing SQL Server database to store the Duet Metadata. In addition,
SAP’s Duet J2EE components can be installed onto a NetWeaver Java Web Application Server
without affecting the backend ERP ABAP system.
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, existing
scalability methodologies can be implemented to improve performance.

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

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

Microsoft Duet SAP Duet SAP Backend

Components (IIS) Components (NW Web AS ABAP)
(NW Web AS Java)
Scalability • Windows Load • Add clustered • Add Dialog
Balancing J2EE nodes instances (App
• F5 Networks Servers)
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 on
the SAP Service Marketplace at http://service.sap.com/instguides .
Communication Flow – Authentication

Providing a Single Sign-on experience for access to the backend SAP business processes, the
Duet 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 NetWeaver
infrastructure to provide the Duet client with a logon ticket. The Duet Client can then
communicate directly with the backend SAP system, using a web service call to the Service
Bundle, fulfilling the client request (e.g. submit a leave request). When data needs to be
transferred to the client, the backend SAP system communicates with the Exchange Server using
the Request Handler on the Duet Server (e.g. manager receives an approve / reject email for
employee’s leave request).
Where to find Duet Requirements and Documentation
Hardware & Software Requirements
For 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/instguides → SAP xApps → Duet → Duet 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/instguides → SAP xApps → Duet → Duet 1.5

Installation and Configuration of Duet

ƒ Duet for Microsoft and SAP: Installation Guide in SAP Service Marketplace at:
http://service.sap.com/instguides → SAP xApps → Duet → Duet 1.5
ƒ Duet for Microsoft and SAP: SAP ERP Configuration Guide in SAP Service Marketplace at:
http://service.sap.com/instguides → SAP xApps → Duet → Duet 1.5

Release Information
ƒ Duet for Microsoft and SAP: Master Guide in SAP Service Marketplace at:
http://service.sap.com/instguides → SAP xApps → Duet → Duet 1.5. Look in the section
referring to important notes.

Duet How to Guides and Blogs

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

ƒ Duet How To Guides

https://www.sdn.sap.com/irj/sdn/advancedsearch?query=Duet+how+to&cat=sdn_all
ƒ Duet Blogs
https://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 Duet
1.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.
How to get started
Information surrounding the preparation for Duet projects has been gathered from Microsoft, SAP
and implementation partners around the world. This information is provided to further simplify the
deployment of Duet into current Microsoft / SAP environments. Customers can increase the ease
of implementation by first determining what areas will be impacted by the project, what resources
are needed and how long an implementation will take.

Duet Project Team

Resource Requirements

Based on best practices, customers who are in the project preparation phase should begin their
Duet project by gathering the necessary resources. This will help manage their expectations and
help them understand how they will contribute to the implementation.

Customer Commitment SAP / Microsoft / Implementation

Partner
Executive Sponsor
Project Manager Project Manager
Project Team Members
ƒ Business Experts – SAP ERP ESS/MSS, SAP CRM, SAP SRM, SAP BI etc.
(depending on Duet scenarios being implemented )
ƒ Netweaver Expert – Web AS JAVA
ƒ Technical Expert (eg. Microsoft ADS, Microsoft Office, Microsoft Exchange, Software
Deployment, Domain Administration, IIS, SQL Server)
Project Team Members
ƒ Duet Expert

Executive Sponsor

As with most projects, an Executive Sponsor to champion the project is recommended. This can
help secure funding, as well as provide an assurance that issues are escalated during the project.

Project Manager(s)
Assigning a Project Manager will also help keep the project on track. Ideally, there should be a
Project Manager from both the SAP side and the customer side and the Customer Project
Manager would be the main driver.

Duration: Full time during Planning phase, part time during Installation and Testing phases to
monitor progress and facilitate issue resolution
Skill Set: Project Management Experience
Business Expert(s)

Having someone on the project who can provide the functional (business configuration) expertise
is important. The business expert(s) must ensure that the application associated to the Duet
scenario being installed is fully functional and configured in the backend SAP system(s) so that
they 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 application
in the SAP Backend system.

Duration: Part time during Planning, Preparation and Testing phases. They should be available
for 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 HR
scenarios are being implements ( Time and Leave Management etc), then the business expert
must 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, SAP
Authorization (User Setup)
Web AS Java: J2EE installation, security configuration based on the NetWeaver Java Web
Application Server with configuration of trust systems, connecting Active Directory to User
Management 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 task
as required.

Skill Set:
ƒ Microsoft ADS ( User setup / Troubleshooting )
ƒ Microsoft Exchange Server ( Troubleshooting )
ƒ Software Deployment ( Client Roll out, System Management Server (SMS) )
ƒ Domain Administration ( Preparation )
Duet Expert
A resource on the project with experience implementing Duet will make the implementation
efficient and effective. Microsoft and SAP Professional Services organizations as well as
Partners have Duet implementation experience from the early stages of the product. If a Duet
resource is not internally available, a Microsoft or SAP Duet Expert or an experienced partner
should be considered.

Duration:
Full time throughout Planning, Installation and Testing phases

Skill Set: Expert with Duet implementations and scenarios

Project Timelines
The following project plan is an estimate based on early Duet implementations performed by
Microsoft 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 sufficient
because Duet uses current business processes. A 2 tier landscape will keep costs of
implementing low. A 3 tier landscape can also be used if desired.
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 Duet
configuration itself. Online learning maps are available on the SAP Service Marketplace with Duet
training classes being delivered by both Microsoft and SAP. Additional information and education
material is located at http://service.sap.com/education.

An alternative method of training can include implementing a small test environment which can
help with hands-on education. Duet installation and configuration guides are available on the SAP
Service Marketplace: http://service.sap.com/instguides -> xApps -> Duet.
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.
Duet Best Practices
Project Planning
The 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 a

company 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 arise
specific to your environment. With Duet, there are interdependencies between the
various systems (ABAP, J2EE, Internet Information Server, SQL Server, Exchange
Server, 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 User’s Client machines

ƒ Carefully plan how Duet will be deployed on user machines for production with minimal
effort / 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 from
Desktop to Duet Server to Exchange to SAP Backend systems.
Document your System Landscape

ƒ Because of the various servers, services and tools used during a Duet implementation, it
is important to document system hostnames, locations, IP addresses, operating system
accounts, J2EE passwords, Visual Administrator accounts, SDM (Software Deployment
Manager) 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 the Duet for Microsoft and SAP: Installation
Guide in SAP Service Marketplace

SAP Backend Systems must be patched to the pre-requisite level and any extra notes
have been applied – see Duet 1.5 Release Information Note
SAP Backend Applications associated to Duet Scenarios must already be configured so
that they can be used independent of Duet
Use the Duet Check Tool delivered in the SAP Backend to check for some of the
backend pre-requisites – this tool can be found in the Duet IMG, transaction SIMGH in
the master SAP system backend.
Duet Landscape must be built (hardware and software pre-requisites in place) on the
Duet server(s) and the Duet clients
Users 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 patches
can be moved to production.

Installation
Gather all required documentation and follow the guides during installation
ƒ Start with the Duet for Microsoft and SAP: Master Guide in the Service Marketplace
ƒ Have your landscape documentation on hand for quick access during the installation
ƒ View Duet how to guides and blogs for tips on configuration and troubleshooting

Increase Duet Logging when troubleshooting

During the installation of the Duet Server, Duet Add-On, Duet Client and Business Applications,
customers should regularly review the J2EE Log Viewer provided with the SAP Web Application
Server Java installation. The standard log configuration does not provide information regarding all
errors. However, the J2EE event log can be configured to view all errors by making modifications
to specific settings in the Log Configurator found in the J2EE Visual Administration tool.

Utilize Duet test and support tools for monitoring and testing throughout installation and
go-live
ƒ Duet Backend Check Tool
ƒ Duet Client Support Tool
ƒ Duet Administration UI
ƒ Duet Sync Monitor tool also known as the Client Monitor Tool

For the Report and Analytics Scenario, implement controls to minimize overhead on
backend system due to Report scheduling

Because the reporting scenario, allows for real-time and scheduled reporting from a backend
SAP ERP or SAP Business Intelligence system, some administrative considerations should be
incorporated in implementation
ƒ Larger Exchange mailboxes for Report Management users should be considered. Report
templates can be configured with default criteria by the Duet administrator to minimize
the possibility of large reports.
ƒ Limit Duet reports to 4 MB and utilize the Duet option .ZIP to reduce the size of reports
being delivered to Duet
ƒ Only allow critical reports to be able to run ad-hoc
Operations and Maintenance
Support and Escalation

ƒ Document Support and escalation procedures for Duet which includes who should be
responsible for support and timelines that issues must get resolved before escalating.
ƒ Have backup and recovery plans clearly documented and clearly define responsibility
ƒ Incorporate Duet support and escalation into existing company procedures to ensure
consistency and reduce learning curve.
Conclusion
Implementing Duet takes an understanding of the various components involved and advance
project preparation. Knowing what to avoid is sometimes as important as knowing what to do!
From the experiences of early Duet implementations, best practices have been developed and
delivered to customers to ensure ease of deployment. These best practices assist customers in
moving from the implementation phase to quickly enjoying the Duet experience. Microsoft and
SAP continue to jointly develop, deliver and support best-practices for global deployments of
Duet.