This is the second blog in a series on how to install, check and troubleshoot your Duet Enterprise installation. This time we will focus on the SharePoint side of the installation.
As you know Duet Enterprise is now General Available (GA) and can be downloaded from the Service Marketplace. [DVD: http://www.service.sap.com/swdc -> Installations and Upgrades -> A – Z Index -> D -> DUET ENTERPRISE -> DUET ENTERPRISE 1.0 -> Installation; Latest Service Pack SP02: http://www.service.sap.com/patches -> A – Z Index -> D -> DUET ENTERPRISE -> DUET ENTERPRISE 1.0 -> Comprised Software Component Versions -> SAP IW FND 100 & SAP IW CNT 100 & SAP IW TNG 100 , …]
If you bought the required licenses from SAP you will also find the Microsoft bits that are required for the SharePoint 2010 add-on on the Service Marketplace. Unlike with the SAP installation you can jump right to SP02 and install these files. So there is no need to first download and install the DVD, but you can go to http://www.service.sap.com/patches -> A – Z Index -> D -> DUET ENTERPRISE -> DUET ENTERPRISE 1.0 -> Comprised Software Component Versions where you will find the SharePoint parts under DUET ENTERPRISE CONTENT 1.0. (if you are a Microsoft customer you can download this software from MSDN).
The most up-to-date documentation on what exactly has to be done on the SharePoint side can be found online on Microsoft TechNet. In this blog I will concentrate on the very basic steps to setup a Proof of Concept.
Prepare the SharePoint Server
The first step that you — as the SharePoint administrator — must do is collect and handover some information to the SAP admin. Like outlined in the first blog this is the HTTPS enabled URL to the SharePoint server, the SSL certificate and the STS certificate and — if required — connection details to the Active directory. You should also hand over the SAP Service Models.ZIP file that contains template BDC (Business Data Catalog) XML files that will be modified and retrurned to you by the SAP admin.
|HTTPS URL to the SharePoint Server||https://contoso.corp.com:443|
|SSL certificate of the SharePoint server||\\\\contoso\\UpdatedModels\\DuetSSLCert.cer|
|STS certificate of the SharePoint server||\\\\contoso\\UpdatedModels\\DuetSTSCert.cer|
|BDC Models for Duet Enterprise||SAP Service Models.zip|
|AD DS Server name||contosoDC|
|Port number of AD DS||389|
|AD DS account and password||Contoso\\ADUser|
|Attribute in AD DS where SAP user name is maintained||This name is an attribute in AD DS. For example, sAMAccountName.|
|User Base Domain Name||CN=Users,DC=dev24,DC=dev,DC=contoso,DC=com|
Since the goal of this blog is to setup a proof of concept environment (with the Start Service ready-to-use capabilities), I will explain how to create a new web application (so there is no intereference with your existing web applications that you might have running), extend it for secure access and also create a self signed certificate.
Install Duet Enterprise Add-on
Installing Duet Enterprise is as simple as installing any Microsoft product. Just run setup.exe from the SP02 installation files. By default it will create a folder on C:\\Program Files\\Duet Enterprise\\1.0 and copy all required files in there.
Then you have to install Duet Enterprise into SharePoint. For this open a command shell and run from the above folder DuetConfig.exe /Install
That was it. Now Duet Enterprise should be ready…
Again I will first concentrate on the ready to use capability Reporting, Starter Servivces and Workflow. The main goal really is to see “some” SAP data in SharePoint and then continue from there — after all Duet Enterprise is an integration platform. The next steps can only be performed once you get some information from the SAP admin.
User name for WSDL access
|Password for WSDL access||SomePassword|
|SSL certificate of SCL System||SSL_servername.cert|
|Updated BDC Model files||BDC.zip|
Since the communication from the SAP system (or better the Service Consumption Layer, SCL) to SharePoint is done via SSL we have to import the SSL certificate from the SAP system first. Then we also have to import Business Data Connetivity, BDC models. This can be done manual (but is a very painful process), or via the DuetConfig tool.
Before running this tool make sure that you have created / initialized the Secure Store in SharePoint Central Administration. After that run
DuetConfig /ImportBDC <path to the extracted BDC model files>\\models.xml /AddUsers “NT Authority\\Authenticated Users” /UserName SP_ACCESS /Password <Password> /Email <Email>
With this command all the models in the BDC.zip will be imported, all Authenticated users will get access to use these services (however, in the end site permissions and of course SAP permissions will kick in) and for retrieving the WSDLs from the SAP System that are mentioned in each model file, the service user SP_ACCESS will beused.
After that — even if you are not going to use Reporting or Workflow — deploy all scenarios to SharePoint. Like said we want to get the Start Services running and for that we need everything deployed. For Reporting and Workflow you first have to adjust the DuetConfig.exe.config files.
The important things here are the Reporting section where you have to specify the HTTPS enabled web application URL and a service user (which is used to send data from the SAP system to SharePoint).
Then in the workflow section you also have to specify a service user. They can be the same, but I would recommend to use two different ones to make troubleshooting simpler.
Once that is done, just run (where vmw3428 is my SharePoint server and 20000 is the port of my web application):
DuetConfig.exe /configuresolution “Reporting” /webappurl http://vmw3428:20000
This will deploy the required solutions on SharePoint. Then just continue with the other solution.
DuetConfig.exe /configuresolution “Workflow” /webappurl http://vmw3428:20000
DuetConfig.exe /configuresolution “ProductWorkspace” /webappurl http://vmw3428:20000
DuetConfig.exe /configuresolution “OrderToCash” /webappurl http://vmw3428:20000
DuetConfig.exe /configuresolution “CustomerWorkspace” /webappurl http://vmw3428:20000
DuetConfig.exe /configuresolution “Portal” /webappurl http://vmw3428:20000
That is it!
Create a new Site Collection
Now go to SharePoint Central Administration from which you can create a new Site Collection on the web application that you have specified above.
When the site collection is created — and the users are already mapped on the SAP side — you should already see data under the Customers, Products or Reporting tab.
However, before Reporting and Workflow can be used you have to hand over two additional URLs and access users to the SAP admin. This is the WSDLs for OBAFileReceiver (=Reporting) and OBAWorkflowService (=Workflow). Without this information no Reports or Workflow will ever reach SharePoint :-). The URL is always build up like this https://<server>:<port>/<yourSiteCollection>/_vti_bin/OBAFilesReceiver.asmx?wsdl or https://<server>:<port>/<yourSiteCollection>/Tasks/_vti_bin/OBAWorkflowService.asmx?wsdl
URL to OBAFileReciever for reporting
URL to OBAWorkflowService for Workflow
Report publisher account
SAP workflows service account
You can take a look at all these steps if you click on the image below.
It’s that simple!
Like I said the goal here was just to get you started. In the next Microsoft related blog I will talk about Workflow (which requires a little more configuration), the Role Sync (which also requires the configuration of the User Profile Store) and the My Site / My Profile integration.