Duet 1.5 technical implementation overview

I will try not to enter into every detailed aspect of a Duet 1.5 technical implementation. However, if you are new to a Duet 1.5 landscape, you must always prepare very carefully all the pre-requisites outlined in the SAP Duet Guides (Admin and Master). The following components enter in action on a Duet 1.5 system:

• SAP Duet 1.5 Server (based on Netweaver 7.0 Java - SP18 or higher).
• SAP Duet 1.5 Business Applications (on top of Duet 1.5 Server).
• SAP ECC 6.0, Portal 7.0, CRM 2007... on your SAP landscape depending of the Business Application you are going to deploy.
• Microsoft Duet 1.5 Metadata Service - on Win2003 SP2.
  
• Microsoft Duet 1.5 Request Handler Service - on Win2003 SP2.
• Microsoft SQL Server 2005 SP3.
  
• Microsoft Exchange 2003 or higher.
• Microsoft Active Directory Service (ADS).
• Microsoft Internet Information Services.
  
• Client computers running on WinXP SP3 or higher, with Office 2003 Professional or higher.
• Microsoft Duet 1.5 client running on top of client computers.

You can run the Microsoft Duet 1.5 Metadata Service and Request Handler on the same host. -- You can also run on this host the SAP Duet 1.5 services, however this can be isolated if your platform of choice for SAP is not Microsoft. For example: * SAP Duet 1.5 BA (based on Netweaver 7.0), runs on Solaris_SPARC / Oracle. * Microsoft Duet 1.5 MDS and RHS, runs on Windows 2003 / MSSQL. Roadmap for a successfull implementation:

1. Read very carefully the SAP Duet 1.5 Master Guide, and Installation Guides.
2. Decide if you are going to run SAP Duet and Microsoft Duet on differents hosts.
3. Prepare the pre-requisites regarding the set-up of Exchange Server for Duet 1.5.
4. Create an ADS user for Duet Request Handler communication, and follow up the activities outlined in the guide to configure the correct properties of this user.
5. Create another ADS user for SAP Netweaver, (ex. j2ee-SID), and follow up the activities outlines in the guide to configure the correct properties of this user.
   
6. Install the Microsoft Duet 1.5 Metadata Service and the Request Handler service. You will be asked to enter a MSSQL Server instance for the Metadata Service DB. This SQL Server instance can be remote or local. Also, you will be asked for the credentials of user created in step 4, during the Request Handler installation.
7. Configure IIS websites accordingly as described on the installation guide.
   
8. Install SAP Netweaver 7.0 SP18 (or higher).
9. Install Duet 1.5 Core Server, Core Apps, Common, etc.. on top of Netweaver installation, using JSPM.
10. Follow the configuration steps through your URL http://sapduethost:5nn00/duet/config. Here you indicate where is the location of your Metadata Service and Request Handler Service. You are also being asked here again for the credentials of the RH Service.
11. Install Duet 1.5 Business Aplicattions through JSPM.
12. Configure UME LDAP connection through the offline configtool, providing user/pass created in step 5. Before entering any data, you must upload a Kerberos 5 ADS readonly template compatible with your OS. This template can be downloaded from OSS note 994791.
    
13. Check on Netweaver useradmin that you are able to search both UME database objects and LDAP users and groups.
14. Run SPNego as described on the installation guide to enable SSO between the client user and SAP. http://sapduethost:5nn00/spnego. Check that you are able to resolve all SAMACCOUNTNAMES.
15. Go to Visual Administrator and assign the spnego template created on previous step, to the OSP*TicketIssuer application.
16. Logon on a client computer using an LDAP user/pass and enter the following URL: http://sapduethost:5nn00/osp/TicketIssuer. If you get in response a XML file, the SSO mechanism has been activated succesfully. However, you are prompted for user/pass when entering the URL, it might be due to diverse problems (communication with SAP <-> ADS, wrong configuration of SPNego...etc.). When you have no clue of what is causing the problem, you can use the DIAGTOOL to trace network and kerberos issues.
17. Logon on the duet administration panel http://sapduethost:5nn00/duet, and set-up the systems connection related to the installed BAs. Test the connections and assign them your BAs.
18. Go to your backend systems (ERP, CRM, etc..), and create the ABAP Duet technical roles through PFCG as described on the install guide.
19. Go back to duet admin panel and follow up the activities outlined on the install guide to syncronize the ABAP Roles, with the Duet Java Roles.
20. Prepare the technical pre-requisites of the backend systems (requiered SP level, RFCs, SSO2, certificates on both ABAP and Java systems, etc..).
    
21. Once all the configuration is done on the SAP side we must now replicate all this information to the Metadata Service, Request Handler Service, and AzMan. Go to duet admin panel, and click on "Publish application metadata". It will take a while. Go to scheduled tasks tab, and check that all jobs are running correctly without warnings. Correct the errors if necessesary.
22. Please note that the LDAP user ID must be the same as the SAP ABAP Backend user ID. If this is not the case, replication of roles to AzMan will not work correctly.
23. Kindly ask your functional team to perform the Duet customizing on the backend systems, and on the duet applications. Once finished...
24. Implement the Duet 1.5 client on the client computers. During installation you will be asked for the Microsoft Request Handler Server. Enter the information as the input from step 6.
25. Set-up client Diagnostics on the SAP Duet 1.5 system.
26. Open Outlook and check that the Duet 1.5 pane is showing correctly and the results are what expected from the functional side.
    
27. ... and finally: Install Duet 1.5 client support tools on the client computers to troubleshoot any additional technical issue.

Please let me know if you encounter additional problems during this complex implementation process. I will be more that glad in assist you!