Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Upgrade to Duet Enterprise 2.0 on SharePoint Server 2013

Published: November 20, 2012

Summary: Learn how to upgrade from Duet Enterprise 1.0 on SharePoint Server 2013 to Duet Enterprise 2.0 on SharePoint Server 2013.

Applies to:  Duet Enterprise for Microsoft SharePoint and SAP Server 2.0 

This article guides you through the process of upgrading Duet Enterprise 1.0 running on a SharePoint Server 2013 farm to Duet Enterprise 2.0 running on SharePoint Server 2013.

In this article:

Before you begin

You must verify that the following prerequisites are in place before you do any of the procedures that are described in this article.

  • Duet Enterprise 1.0 is running on SharePoint Server 2013.

    Tip Tip:

    Upgrading directly from Duet Enterprise 1.0 on SharePoint Server 2010 to Duet Enterprise 2.0 on SharePoint Server 2013 is not supported. You must first upgrade to Duet Enterprise 1.0 running on SharePoint Server 2013. For more information, see Upgrade to Duet Enterprise 1.0 on SharePoint Server 2013.

  • Verify that the SAP administrator has upgraded the SAP system to Duet Enterprise 2.0. During this upgrade process, the SAP administrator creates OData endpoints for the Duet Enterprise 2.0 Workflow, Reporting, and RoleSync solutions.

    Tip Tip:

    Get the LsiUrls for the Reporting, Workflow, and RoleSync endpoints from the SAP administrator. You will need them later when you import BDC models.

Optional PowerShell scripts

A set of PowerShell Scripts are available for download that you can use to complete some of the procedures in this article. Although these scripts are not supported, they have been tested by the Duet Enterprise test team. Procedures in which scripts are available indicate that an optional script is available and also provide the manual steps for those who do not want to use scripts.

If you want to use the scripts, we recommend that you download them now from MSDN Code Gallery.

Block user access to SAP data

If users have access to SAP data on Duet Enterprise-enabled web sites on the SharePoint Server 2013 farm, we recommend that you block user access to this SAP data. Of course, you will want to warn users that they will not have access during the upgrade.

To block access to SAP data, ask the SAP administrator to remove the STS Certificate for Duet Enterprise from SAP NetWeaver. In a later procedure, you will provide the SAP administrator with a different certificate to trust. Do not continue with the upgrade until the SAP administrator has removed the certificate and you have verified that SAP data is no longer displayed in Duet Enterprise sites.

You can verify that the STS certificate was removed by going to a SharePoint site that displayed SAP data. You will see the following error message: "Message from External System: 'An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.'"

note Note:

You might need to refresh the browser to verify that SAP data is no longer displayed a particular site.

Prepare to install Duet Enterprise 2.0

Complete the procedures in this section before you install Duet Enterprise 2.0.

In this section:

Deactivate unsupported features

The features that are listed in the following table are provided with Duet Enterprise 1.0 to enable users to offline synchronization of data to Microsoft Outlook. These features are not supported in Duet Enterprise 2.0. If they are enabled on any of your sites, you must deactivate them before you install Duet Enterprise 2.0.

Features not supported in Duet Enterprise 2.0

Feature name (in user interface) Feature name (in PowerShell) Level

BCS Solution Galleries

OBABuildingBlocks

Site collection

BCS Solution Design Feature

OBADesign

Site

Complete these steps to deactivate these features on all sites and site collections before you install Duet Enterprise 2.0.

note Note:

You must be a site owner to deactivate features at the site-level and a site collection administrator to deactivate features at the site collection-level.

To deactivate the BCS Solution Design Feature

  1. In a browser, go to a site.

  2. Click Site Actions, and then click Site Settings.

  3. Under Site Actions, click Manage site features.

  4. In the BCS Solution Design Feature row, do the following:

    1. If the Status column displays Active, click Deactivate to deactivate the solution.

      Deactivate button screen shot
    2. If the Status column does not display Active, the feature is not active. No further action is needed.

      note Note:

      If the BCS Solution Design Feature row is not listed on the Features page, it means that this feature is not available on the site.

To deactivate the BCS Solution Galleries feature

  1. In a browser, go to a top-level site in a site collection.

  2. Click Site Actions, and then click Site Settings.

  3. Under Site Collection Administration, click Site collection features.

  4. In the BCS Solution Galleries row, do the following:

    1. If the Status column, displays Active, click Deactivate to deactivate the solution.

      Deactivate button screen shot
    2. If the Status column, does not display Active, the feature is not active. No further action is needed.

      note Note:

      If the BCS Solution Design Feature row is not listed on the Features page, it means that this feature is not available on the site-collection.

Uninstall Duet Enterprise Solutions and Duet Enterprise language packs

Complete the procedures in this section to uninstall all of the Duet Enterprise 1.0 solutions and language packs for Duet Enterprise 1.0. You can see the names of the solutions that you have installed on the Solution Management page in Central Administration. In Central Administration, in the Quick Launch, click System Settings. Under Farm Management, click Manage farm solutions.

The following solutions are provided with Duet Enterprise 1.0 and Feature Pack 1 for Duet Enterprise 1.0. You must uninstall each of the solutions that are installed on the SharePoint Server 2013 farm:

  • obacustomerworkspace.wsp

  • obaextensions.wsp

  • obaordertocash.wsp

  • obaportal.wsp

  • obaproductcenter.wsp

  • obareporting.wsp

  • obataskflow.wsp

  • sap.office.duetenterprise.reporting.wsp

  • sap.office.duetenterprise.workflow.wsp

Uninstalling solutions involves two phases. You must first retract the solutions and Duet Enterprise language packs that were deployed. Note that Central Administration refers to this action as retract and PowerShell refers to this action as uninstall. After the solutions are retracted (not deployed) you will then remove the solutions.

Retract solutions by using Central Administration

You must retract the Duet Enterprise language packs before retracting the solutions that they support. Duet Enterprise language packs are deployed as solutions. You can easily identify them on the Solution Management page in Central Administration because the names of the Duet Enterprise language packs have the same name as the solution that they support except that the names have a four digit number surrounded by round brackets appended to the solution name.

The following screen shot shows a solution with two Duet Enterprise language packs installed. One for the French language (Language ID 1036) and the other for the Japanese language (Language ID 1041). The solution without a language ID appended to the name is referred to as a core solution because it provides all the elements of the solution in the default language. For example, if you installed the English language version of Duet Enterprise 1.0 then the core solutions are English language only.

Solution Management screen shot

In this example, you must retract the obacustomerworkspace.wsp(1036) and obacustomerworkspace.wsp(1041) language packs before retracting the obacustomerworkspace.wsp core solution.

Tip Tip:

Ensure that the Status column of the language packs display Not Deployed before you attempt to retract the core solution.

Complete the following procedure to retract the language packs and solutions.

Tip Tip:

See the list earlier in this section for the list of solutions that are provided with Duet Enterprise 1.0.

To retract the installed solutions and language packs

  1. In Central Administration, on the Quick Launch, click System Settings.

  2. In the Farm Management section, click Manage Farm Solutions.

    The core solutions and associated language packs that are installed on the SharePoint farm appear on the Solution Management page.

  3. In the Name column, find the name of the solution that you want to retract. If a language pack is deployed for the solution, go to step 4. Otherwise, go to step 9.

    Tip Tip:

    Duet EnterpriseDuet Enterprise language packs have a four-digit number surrounded by round brackets appended to the name. For example, obaportal.wsp(1036). If the language pack is deployed, the Status column for the language pack will display Deployed.

  4. In the Name column, click the link of the language pack.

  5. On the Solution Properties page, click Retract Solution.

  6. On the Retract Solution page, click OK.

    note Note:

    You are returned to the Solution Management page and the Status column for the Duet Enterprise language pack you are retracting changes to Retracting.

  7. If additional language packs are installed for this solution, go to step 4. Otherwise, continue to step 8.

  8. After several moments, refresh the browser. When the Status column for the language packs that you retracted displays the status Not Deployed, continue to step 9. Otherwise, repeat step 8.

  9. In the Name column, click the link of the solution that you want to retract.

  10. On the Solution Properties page, click Retract Solution.

  11. On the Retract Solution page, click OK.

    note Note:

    You are returned to the Solution Management page and the Status column for the solution you are retracting changes to Retracting.

  12. After the solution is retracted, the status column displays Not Deployed. This typically requires you to refresh the browser.

  13. If you have other solutions and Duet Enterprise language packs to retract, go to step 3. Otherwise, proceed to Remove solutions by using Central Administration.

Remove solutions by using Central Administration

After all solutions and Duet Enterprise language packs are retracted, the next step is to remove them from the farm. This removes all traces of the solutions including the files in the file system.

Tip Tip:

You must remove the associated language packs before you can remove a core solution.

To remove solutions and Duet Enterprise language packs

  1. In Central Administration, on the Quick Launch, click System Settings.

  2. In the Farm Management section, click Manage Farm Solutions.

    The solutions and language packs that are installed on the SharePoint farm appear on the Solution Management page. Ensure that all Duet Enterprise 1.0 solutions and language packs were retracted before you continue. Retracted solutions and language packs have the status of Not Deployed.

  3. In the Name column, find the name of the solution that you want to remove. If a language pack is displayed in the Name column for the solution, go to step 4. Otherwise, go to step 8.

    Tip Tip:

    Duet Enterprise language packs have a four-digit number surrounded by round brackets appended to the name. For example, obaportal.wsp(1036). If the language pack is deployed, the Status column for the language pack will display Deployed.

  4. In the Name column, click the link of the Duet Enterprise language pack.

  5. On the Solution Properties page, click Remove Solution.

  6. A dialog box is displayed that asks if you are sure that you want to remove the solution. Click OK to continue.

    note Note:

    You are returned to the Solution Management page and the solution that you removed is no longer listed on the page.

  7. If additional language packs are installed for this solution, go to step 4. Otherwise, continue to step 8.

  8. In the Name column, click the link of the solution that you want to remove.

  9. On the Solution Properties page, click Remove Solution.

  10. A dialog box is displayed that asks if you are sure that you want to remove the solution. Click OK to continue.

    note Note:

    You are returned to the Solution Management page and the solution that you removed is no longer listed on the page.

  11. If you have other solutions and Duet Enterprise language packs to remove, go to step 3. Otherwise, proceed to Uninstall BDC Models (Optional).

Complete uninstallation of Duet Enterprise language packs

If you installed any Duet Enterprise 1.0 language packs, you must complete this procedure before you install Duet Enterprise 2.0. Otherwise, setup will fail. If Duet Enterprise language packs were not deployed, skip to Uninstall BDC Models (Optional).

Tip Tip:

To complete this procedure, you must know the four-digit language code for each language pack that is installed. Duet Enterprise 1.0 language packs will be listed on the Uninstall or change a program page in Control Panel. To view this page, from Control Panel, under Programs, click Uninstall a program.

The following illustration shows Duet Enterprise 1.0 language packs that are installed for Language IDs 1036 and 1041.

Uninstall or change a program screen shot

To complete the following procedure, you must know the Language Identifier in both Hex and decimal, as shown in the following table.

Table: Language codes and Language IDs

Language Language code Language ID (LCID Decimal) Language ID (LCID Hex)

Arabic (Saudi Arabia)

ar-sa

1025

0401

German

de-de

1031

0407

English (United States)

en-us

1033

0409

Spanish

es-es

3082

0c0a

French

fr-fr

1036

040c

Hebrew (Israel)

he-il

1037

040d

Italian

it-it

1040

0410

Japanese

ja-jp

1041

0411

Portuguese (Brazil)

pt-br

1046

0416

Russian

ru-ru

1049

0419

Turkish

tr-tr

1055

041f

Chinese (China)

zh-cn

2052

0804

Chinese (Taiwan)

zh-tw

1028

0404

You can remove the Duet Enterprise 1.0 language packs manually or using the uninstalllangpacks.ps1 PowerShell script. If you have not already done so, you can download the script from MSDN Code Gallery.

Do one of the following:

To complete uninstallation of Duet Enterprise language packs manually

  1. Open a command prompt as an administrator.

  2. Type the following command, and then press ENTER:

    msiexec.exe /x {90140000-00BF-{<LanguageID>}-1000-0000000FF1CE} RUNNINGFROMSETUP=TRUE

    Where <LanguageID> is the four-digit hexadecimal-equivalent LCID of the language pack that is installed. Refer to the Language ID (LCID Hex) column of the previous table for a list of Language IDs supported by Duet Enterprise 1.0.

    For example, to uninstall a language pack with the language ID of 1036 you would enter the following:

    msiexec.exe /x {90140000-00BF-{040c}-1000-0000000FF1CE} RUNNINGFROMSETUP=TRUE

  3. Repeat step 2 to remove any additional language packs that you have installed.

  4. Proceed to Disable health analyzer rule definition.

To complete uninstallation of Duet Enterprise language packs using the script

  1. Log on to a web server in the SharePoint Server farm.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2013 Products.

  4. Click SharePoint 2013 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    <path>\uninstalllangpacks.ps1

    Where <path> is the location where you downloaded the scripts. For example, if you downloaded the scripts to c:\scripts, then you would enter c:\scripts\uninstalllangpacks.ps1.

  6. After you press Enter, the following actions occur:

    • The command prompt displays the decimal value of the culture code, also known as the Locale Identifier (LCID), for each Duet Enterprise 1.0 language pack that is installed.

    • The "Successfully uninstalled culture: <cultureCode> for each language pack that was uninstalled is also displayed.

      Where, <cultureCode> is the decimal value of the culture code, also known as Locale Identifier (LCID) for the language pack that was uninstalled.

    • After all Duet Enterprise language packs are removed, Internet Information Services is stopped and restarted.

      The following illustration shows the output of the script that was used to uninstall the Duet Enterprise 1.0 Language pack for the Japanese language. If more than one language pack is installed, the first three lines of the script's output is repeated for each language.

      This screenshot shows the output of the uninstalllangpacks.ps1 PowerShell script. In this example, the script uninstalled the Duet Enterprise 1.0 Language pack for the Japanese language.

Disable health analyzer rule definition

After upgrading to Duet Enterprise 2.0, the health rule named "Duet Enterprise Solutions Health" must be deleted. You can do this manually or using the healthrule.ps1 PowerShell script. If you have not already done so, you can download the script from MSDN Code Gallery.

Do one of the following:

To delete the health analyzer rule definition manually

  1. In Central Administration, in the Quick Launch, click Monitoring.

  2. In the Health Analyzer section, click Review rule definitions.

  3. In the Category : Configuration section, click the Duet Enterprise Solutions Health link. If this link does not exist, it means that this health rule has already been deleted.

  4. On the ribbon, click Edit Item.

  5. On the ribbon, click Delete Item.

  6. Click OK in the dialog box that is displayed to confirm that you want to delete the rule definition.

  7. Proceed to Install Duet Enterprise 2.0.

To delete the health analyzer rule definition using the script

  1. Log on to a web server in the SharePoint Server farm.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2013 Products.

  4. Click SharePoint 2013 Management Shell.

  5. At the Windows PowerShell command prompt, type the following command:

    <path>\healthrule.ps1

  6. Where <path> is the location where you downloaded the scripts. For example, if you downloaded the scripts to c:\scripts, then you would enter c:\scripts\healthrule.ps1.

  7. After you press Enter, the command prompt displays the decimal value of the culture code, also known as Locale Identifier (LCID), for each language that is installed and displays the "Successfully unregistered health rules" message for the health analyzer rules for each language.

Install Duet Enterprise 2.0

In this section:

Install Duet Enterprise 2.0 binary files

Use this procedure to uninstall Duet Enterprise 1.0 components that might still be installed on the SharePoint Server 2013 farm and copy the Duet Enterprise 2.0 files to the file system.

To install Duet Enterprise 2.0 binary files

  1. Log on to a front-end web server in the SharePoint Server 2013 farm as a member of the Windows Administrators group.

  2. As administrator, open a Windows Command Prompt window.

  3. At the command prompt, type cd:\directory\, where directory is the local or network location of the Duet Enterprise setup files.

  4. From the installation location of the Duet Enterprise 2.0 files, type the following command, and then press ENTER:

    setup.exe /install

    The Duet Enterprise 2.0 for Microsoft SharePoint and SAP license agreement is displayed.

  5. On the Duet Enterprise 2.0 for Microsoft SharePoint and SAP license agreement page, select the I accept the terms in the license agreement check box, and then click Install.

  6. When complete, you receive the following message: "Duet Enterprise setup completed successfully."

    The Duet Enterprise 2.0 binary files are now copied to the host computer.

  7. Verify that the following files and folders are created in the default directory path <systemDrive>:\Program Files\Duet Enterprise\2.0:

    • BDC Models (Folder)

    • Solutions (Folder)

    • DuetConfig.exe

    • DuetConfig.Intl.dll

    • OBA.Server.Logging.Resources.dll

Verify Full Control access to the User Profile Service application

Before you perform the following procedure, verify that the account that you will use to run DuetConfig.exe is both a member of the Farm Administrators SharePoint group and has been granted Full Control permissions on the User Profile Service Application.

note Note:

You must be a member of the Farm Administrators SharePoint group to complete this procedure.

To verify access to the User Profile Service Application

  1. In Central Administration, in the Application Management section, click Manage service applications.

  2. On the Manage Service Applications page, click the row that contains the User Profile Service Application that you upgraded earlier.

  3. On the ribbon, in the Sharing group, click Permissions.

  4. In the Connection Permissions dialog box, do one of the following:

    1. If the user account that you will use to run DuetConfig.exe appears in the middle pane, click the user account.

    2. If the user account that you will use to run DuetConfig.exe does not appear in the middle pane, type the user account in the top pane and then click Add.

  5. In the bottom pane, verify that the Full Control check box is selected.

  6. Click OK.

Manage DuetRoot certificate

This section describes the procedure to manage the DuetRoot.pfx and DuetRoot.cer certificates when you upgrade to Duet Enterprise for Microsoft SharePoint and SAP Server 2.0.

In this section:

Create the .pfx self-signed certificate and target application in the Secure Store service application

Complete this procedure to create a self-signed root certificate by using the DuetConfig.exe -CreateSelfSignedCertificate command. Use this procedure if you want to create a self-signed certificate. This procedure creates a self-signed certificate that is issued by the Duet Root Certificate Authority.

To create the .pfx self-signed certificate

  1. As administrator, open a Windows Command Prompt window on the computer from which you ran setup /install earlier.

  2. At the command prompt, navigate to the folder that contains the DuetConfig.exe file. By default, this is the C:\Program files\Duet Enterprise\2.0\ folder.

  3. At the command prompt, type the following command, and then press ENTER:

    DuetConfig - CreateSelfSignedCertificate -Path <Root Certificate file path\filename>.pfx -Password <password>

    Where:

    • <Root Certificate file path\filename> is the path where you want to save the certificate and the name of the certificate.

    • <password> is the password that you want to assign to the certificate.

    For example, if you want to create a certificate named DuetRoot to the C:\ drive and assign the password DuetPassword, then you would enter the following:

    DuetConfig - CreateSelfSignedCertificate -Path c:\DuetRoot.pfx -Password DuetPassword

    note Note:

    If no password is given here, you are prompted to enter one after you press ENTER. If that occurs, enter a password and press ENTER again.

  4. Record this password. You will need it later to configure this certificate.

  5. At the command prompt, you receive the following message: "Certificate " <Root Certificate file path\filename>" has been generated successfully."

    Where <Root Certificate file path\filename> is the path to which you saved the certificate and the name of the certificate.

The Duet Enterprise Root certificate is now created and is ready to be configured for use with the Secure Store Service service application.

Configure the .pfx certificate

Use this procedure to configure the .pfx certificate that you created in the previous procedure and create a target application in the Secure Store Service service application named DuetApp. This procedure also stores the certificate in a target application named "DuetApp" in the Secure Store Service service application that you specify.

To configure the .pfx certificate and target application in the Secure Store service application

  1. As administrator, open a Windows Command Prompt window.

  2. At the command prompt, navigate to the folder that contains the DuetConfig.exe file. By default, this is the C:\Program files\Duet Enterprise\2.0\ folder.

  3. At the command prompt, type the following command, and then press ENTER:

    DuetConfig.exe -ConfigureRootCertificate -SecureStoreServiceApplicationName "<Name of Secure Store Service Application>" -Path "<Root Certificate file path\filename>.pfx" -Password <password>

    Where:

    • <Name of Secure Store Service Application> is the name of the Secure Store Service applications that you are using for Duet Enterprise.

    • <Root Certificate file path\filename> is the path to and file name of the certificate that you created in the previous procedure. Note that this must be saved as a .pfx file.

    • <password> is the password that you assigned to the certificate in the previous procedure.

    For example, if the name of your Secure Store Service application that you are using for Duet Enterprise is DuetSecureStore and the path to and name of the certificate that you created in the previous procedure is C:\DuetRoot.pfx, and you assigned the password DuetPassword, you would enter the following at the command prompt:

    DuetConfig.exe -ConfigureRootCertificate -SecureStoreServiceApplicationName "DuetSecureStore" -Path "c:\DuetRoot.pfx" -Password DuetPassword

  4. At the command prompt, you receive the following message: "Duet Root certificate has been configured in Secure Store with target application name DuetApp."

  5. For verification, navigate to the Secure Store Service service application page and confirm that the target application DuetApp is shown.

Export the .pfx certificate as a .cer certificate

Use this procedure to export the client certificate that you created and configured. After exporting the .pfx certificate as a.cer certificate, you will give it to the SAP administrator. The SAP administrator will use it to create a trust relationship on the SAP system.

To export the client certificate

  1. As administrator, open a Windows Command Prompt window.

  2. At the command prompt, navigate to the folder that contains the DuetConfig.exe file. By default, this is the C:\Program files\Duet Enterprise\2.0\ folder.

  3. At the command prompt, type the following command, and then press ENTER:

    DuetConfig -ExportRootCertificate -Path <Root Certificate file path\filename>.cer

    Where <Root Certificate file path\filename> is the path to and file name that you want to use for this. Note that this must be exported as a .cer file.

    For example, if you want to export the file that has the name DuetRoot to the C:\ folder, you would enter the following at the command prompt:

    DuetConfig -ExportRootCertificate -Path c:\DuetRoot.cer

  4. At the command prompt, assuming you named the certificate DuetRoot, you receive the following message: "Root certificate for Duet is exported successfully to file c:\DuetRoot.cer."

Share the.cer certificate with the SAP administrator

When the.cer certificate is successfully exported, you must share it with the SAP administrator.

note Note:

In the path where you created and exported the certificates there are two certificates. One is listed as type: Security Certificate and one is listed as type: Personal Information. The .pfx certificate is listed as type: Personal Information and the.cer certificate is listed as type: Security Certificate. You will give the.cer certificate that is listed as type: Security Certificate to the SAP administrator.

Give the.cer certificate (type: Security Certificate) file to the SAP administrator.

Install and deploy Duet Enterprise language packs

If Duet Enterprise language packs were installed before the upgrade, you must reinstall and deploy them now.

In this section:

Verify SharePoint 2013 language packs are installed

You must make sure that the SharePoint 2013 language pack is installed for each language that you will use on your sites before you install the Duet Enterprise language packs.

The SharePoint 2013 language packs that you want to use must be installed on each web server in the SharePoint Server 2013 farm. For information about installing SharePoint 2013 language packs, see Install or uninstall language packs for SharePoint 2013.

Tip Tip:

You can view the "Uninstall a program" page in Windows Control Panel to verify that SharePoint 2013 language packs are installed on a particular web server.

Install Duet Enterprise language packs

Duet Enterprise language packs are provided as separate ISO images, one for each supported language. Download the Duet Enterprise language packs that you want to install from the same web page that you downloaded the Duet Enterprise 2.0 ISO file. You must install them on each web server in the SharePoint Server 2013 farm.

Verify Duet Enterprise language pack installation

You can verify successful installation of a Duet Enterprise language pack by viewing the "Uninstall a program" page in Windows Control Panel.

To view language packs on the Uninstall a program page

  1. Log on to a web server in the SharePoint Server 2013 farm as administrator.

  2. Click Start, and then click Control Panel.

  3. Under Programs, click Uninstall a program.

  4. In the Name column, look for a language pack. For example, the name of the Duet Enterprise language pack for the French language is listed as "Duet Enterprise for Microsoft SharePoint and SAP Server 2.0 Language Pack – French."

Additionally, the .WSP files that support the language of each of the starter services solutions are copied to the subfolders within C:\Program Files\Duet Enterprise\2.0\Solutions\Starter Services\ folder. For example, if you installed the Duet Enterprise language pack for the French language, you would find the OBACustomerWorkspace.fr-FR.wsp file inside the C:\Program Files\Duet Enterprise\2.0\Solutions\Starter Services\Account\ folder.

You will use these WSP files to deploy the language packs that you installed. For more information, see Add and deploy Duet Enterprise language packs for starter services later in this article.

Import BDC models and set Metadata Store permissions

Before importing any Business Data Connectivity (BDC) models, you will need the LsiUrl from the SAP administrator for each of the following BDC models to use when DuetConfig.exe is run and the models are imported. You must configure a Duet publishing URL and account. You must grant users permissions on the BDC models that you import before they can access the SAP data that those models represent.

The following models are provided with Duet Enterprise 2.0 and are installed in this default directory path: <systemDrive>:\Program Files\Duet Enterprise\2.0\BDC Models. This directory contains other models that are installed by default and are not used as part of this deployment.

  • Workflow

  • UserSubscription

  • Reporting

  • RoleSync

Each of these models must be imported individually because the procedures to import them are not the same. Use the following procedures to import the BDC Models for the Reporting, Workflow, and RoleSync solutions.

In this section:

Import the Reporting model

The Reporting BDC model is imported into Duet Enterprise 2.0 by using the DuetConfig.exe -importbdc command. It requires an LsiUrl to import successfully, which you must get from the SAP administrator before importing the model. Use the following procedure to import the Reporting BDC model.

To import the Reporting model

  1. Verify that you have the following administrative credentials: Windows Administrators group on the front-end web server that is running SharePoint Server 2013 to complete this procedure. You must also be a member of the Farm Administrators group on the SharePoint Server farm on which you are installing Duet Enterprise 2.0.

  2. As administrator, open the Windows command prompt.

  3. At the command prompt, type the default path of the DuetConfig.exe file:

    cd /d C:\Program Files\Duet Enterprise\2.0

  4. At the command prompt, type the following command, and then press ENTER:

    Duetconfig.exe -importbdc -featurename Reporting -BdcServiceApplication "<BDC Service Application>" -lsiurl <LsiUrl>

    Where:

    • <BDC Service Application> equals the BDC Service application name.

    • <LsiUrl> is the LsiUrl URL that is provided to you by the SAP administrator for the Reporting solution.

  5. When complete, at the command prompt, you receive the following message: "The specified BDC model was successfully imported."

Import the Workflow model's core and user subscription

The Workflow BDC model is imported into Duet Enterprise 2.0 by using the DuetConfig.exe -importbdc command. It requires an LsiUrl to import successfully. It also requires an additional parameter named UserSubLsiUrl. This UserSubLsiUrl is used for the UserSubscription model, an additional model only imported together with the workflow model. The UserSubscription model allows users to subscribe to workflow tasks on individual Duet Enterprise 2.0 workflow sites. Use the following procedure to import the Workflow and UserSubscription BDC models.

To import the Workflow model's core and user subscription

  1. Verify that you have the following administrative credentials: Windows Administrators group on the front-end web server that is running SharePoint Server 2013 to complete this procedure. You must also be a member of the Farm Administrators group on the SharePoint Server farm on which you are installing Duet Enterprise 2.0.

  2. As administrator, open the Windows command prompt.

  3. At the command prompt, type the default path of the DuetConfig.exe file:

    cd /d C:\Program Files\Duet Enterprise\2.0

  4. At the command prompt, type the following command, and then press ENTER:

    Duetconfig.exe -importbdc -featurename Workflow -BdcServiceApplication <BDC Service Application> -lsiurl <LsiUrl> -usersubLisurl <UserSubLsiUrl>

    Where:

    • <BDC Service Application> equals the BDC Service application name.

    • <LsiUrl> is the LsiUrl URL that is provided to you by the SAP administrator that matches the BDC model for the Workflow solution.

    • <UserSubLsiUrl> is the UserSubLsiUrl URL that is provided to you by the SAP administrator.

  5. When complete, at the command prompt, you receive the following message: "The specified BDC model was successfully imported."

Import and configure the RoleSync model

The RoleSync BDC model is imported into Duet Enterprise 2.0 by using the DuetConfig.exe -importbdc command. It requires both an LsiUrl to import successfully. Use the following procedure to import the RoleSync BDC model. After the model is imported, it must be configured to start the required timer jobs.

To import the RoleSync model

  1. Verify that you have the following administrative credentials: Windows Administrators group on the front-end web server that is running SharePoint Server 2013 to complete this procedure. You must also be a member of the Farm Administrators group on the SharePoint Server farm on which you are installing Duet Enterprise 2.0.

  2. As administrator, open the Windows command prompt.

  3. At the command prompt, type the default path of the DuetConfig.exe file:

    cd /d C:\Program Files\Duet Enterprise\2.0

  4. At the command prompt, type the following command, and then press ENTER:

    Duetconfig.exe -importbdc -featurename RoleSync -BdcServiceApplication <BDC Service Application> -lsiurl <LsiUrl>

    Where:

    • <BDC Service Application> equals the BDC Service application name.

    • <LsiUrl> is the LsiUrl URL that is provided to you by the SAP administrator that matches the BDC model that you want to import.

  5. When complete, at the command prompt, you receive the following message: "The specified BDC model was successfully imported."

To configure RoleSync

  1. Verify that you have the following administrative credentials: Windows Administrators group on the front-end web server that is running SharePoint Server 2013 to complete this procedure. You must also be a member of the Farm Administrators group on the SharePoint Server farm on which you are installing Duet Enterprise 2.0.

  2. As administrator, open the Windows command prompt.

  3. At the command prompt, type the default path of the DuetConfig.exe file:

    cd /d C:\Program Files\Duet Enterprise\2.0

  4. At the command prompt, type the following command, and then press ENTER:

    DuetConfig.exe -ConfigureRoleSync -UserProfileServiceApplicationName "<User Profile Service Application Name>"

    Where "<User Profile Service Application Name>" equals the name of the User Profile service application.

  5. At the command prompt, you receive the following message: "The specified Profile Synchronization Job was successfully configured."

    The timer job for RoleSync is now created.

Set Metadata Store permissions

Before you can verify the successful configuration and connection between the SharePoint and SAP systems, you must configure Metadata Store permissions.

To set Metadata Store permissions

  1. Verify that you have the following administrative credentials: Windows Administrators group on the front-end web server that is running SharePoint Server 2013 to complete this procedure. You must also be a member of the Farm Administrators group on the SharePoint Server farm on which you are installing Duet Enterprise 2.0.

  2. In Central Administration, in the Quick Launch, click Application Management.

  3. In the Service Applications section, click Manage service applications.

  4. On the Service applications page, click the link for the Business Data Connectivity service Application that you are using for Duet Enterprise 2.0. By default, the name of the link is BDC Service but this name can be changed by an administrator.

  5. In the View section, select BDC Models from the drop-down list. The following four imported models are displayed:

    • OBA.Server.Reporting

    • OBA.Server.RoleSync

    • OBA.Server.UserSubscription

    • OBA.Server.Workflow

  6. On the BDC Models page, use Set Object Permissions and Set Metadata Store Permissions to set both object and Metadata Store permissions for all four of these BDC models. All users who access these models will need individual permissions to access content from these BDC models.

    • Set Object Permissions: Execute, Selectable in Client, Edit, and Set Permissions. (For the publisher account only all permissions are required. For all other accounts, you can choose one or more permissions.)

    • Set Metadata Store Permissions: Execute, Selectable in Client, Edit, and Set Permissions. Make sure to select the Propagate permissions to all BDC models, External Systems and External Content Types in the BDC Metadata Store. Doing so will overwrite existing permissions. (For the publisher account, only all permissions are required. For all other user accounts, only the Execute and Selectable in Client permissions and necessary).

  7. You might have to run IIS reset to allow these permissions to take effect immediately.

Install, configure, and register Duet Enterprise 2.0

Use this procedure to perform a basic deployment configuration of Duet Enterprise 2.0. This procedure also installs the Aggregated Business Calendar solution that was originally provided with Feature Pack 1 for Duet Enterprise 1.0.

This procedure assumes that you are still logged on to the same host computer with the same administrative account that you chose to use for all processes and services. Before you perform the following procedure, verify that the account that you will use to run DuetConfig.exe is both a member of the Farm Administrators SharePoint group and is granted Full Control permissions on the User Profile service application that you are using for Duet Enterprise 2.0.

To install, configure, and register Duet Enterprise 2.0

  1. Log on to the host server as a member of the Farm Administrators group.

  2. Click Start, click All Programs, and then click Accessories.

  3. Right-click the command prompt, and then click Run as administrator.

  4. At the command prompt, navigate to the folder that contains the DuetConfig.exe file. By default, this is the C:\Program files\Duet Enterprise\2.0\ folder.

  5. At the command prompt, type the following command, and then press ENTER:

    DuetConfig -install

  6. When DuetConfig.exe is complete, at the command prompt, you receive the following messages:

    • "Successfully registered the diagnostic service."

    • "Successfully installed all features."

    • "Successfully registered health rules."

    • "Successfully installed help files."

    • "Successfully upgraded Duet Enterprise."

    • "Successfully configured Duet Enterprise."

  7. If the DuetConfig.exe.config file, that you configured when you installed Duet Enterprise 1.0 on the SharePoint Server 2013 farm had separate accounts configured for the ReportPublisherAccount value and the ServiceAccount value, you will see the following message in the command prompt:

    "Reporting and Workflow have been configured with different publisher accounts in the WebApplication <URL of your web application>

    Workflow publisher account : <Account you had configured for the ServiceAccount value> Reporting publisher account : <Account you had configured for the ReportPublisherAccount value>

    Please specify a publisher account from one of the above or a new one:"

    If this occurs, enter the publisher account that you want to use as the publisher account, and then press ENTER. Otherwise go to step 9.

    Tip Tip:

    The account that you choose must be configured in the SAP system as the publisher account for Duet Enterprise 2.0.

  8. (Optional) To verify that the publishing URL was migrated, enter the following at the command prompt, and then press ENTER:

    DuetConfig.exe -getsettings

    This command writes the publishing account settings to a file that is named Settings.xml in the same folder from which you entered the command. You can then use Notepad to view the file.

  9. The Duet Enterprise 2.0 files are now installed, configured, and registered. Leave the command prompt open. You will need it for the next procedure.

Synchronize SAP roles with the SharePoint user profile store

Duet Enterprise 2.0 uses a timer job to bring the user role assignments from the SAP system into the SharePoint user profile store. You must run the "Duet Enterprise Profile Synchronization" timer job at least one time.

note Note:

You must be a member of the Farm Administrators group to complete this procedure.

Before you start this procedure, ask the SAP administrator to to make sure that that the "Synchronize roles to consumers" job has finished running on the SAP system.

The SAP administrator must run the "Synchronize roles to consumers" job periodically to synchronize the user roles on the SAP system with the SAP profile store on the server that is running SAP NetWeaver. We recommend that you do not synchronize the SAP user profile store with the SharePoint user profile store until the SAP administrator has completed the synchronization job. Otherwise, the synchronization job between the SAP profile store and the SharePoint user profile store can take much longer to complete. Note that the "Synchronize roles to consumers" job takes approximately 80 minutes to synchronize 100,000 users, while synchronizing the profile store in SAP NetWeaver to the SharePoint user profile store takes approximately 100 minutes to synchronize 100,000 users. If you plan to schedule these synchronization jobs, we recommend that you run them manually first to determine how much time each takes, on average, to run on your systems.

To synchronize profiles

  1. In Central Administration, on the Quick Launch, click Monitoring.

  2. On the Monitoring page, in the Timer Jobs section, click Review job definitions.

  3. On the Job Definitions page, in the Title column, click the Duet Enterprise Profile Synchronization for <User Profile service application name> link.

    Where <User Profile service application name> is the name of the User Profile service application that you are using for role synchronization.

    Tip Tip:

    If you have only one User Profile service application, by default this name is Duet Enterprise Profile Synchronization for User Profile Service Application.

  4. On the Edit Timer Job page, click Run Now.

    note Note:

    This timer job is scheduled to run one time per day but you can configure it to run less often if it causes a performance problem.

For more information about SharePoint timer jobs, see View timer job status in SharePoint 2013.

Verification step

After role synchronization is complete, the SAP Roles field at the bottom of each SharePoint user profile page displays the SAP roles that the user is assigned to.

To view the SAP Roles property for a particular user profile

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group or is a Service Application Administrator for the User Profile service application.

  2. In Central Administration, in the Application Management section, click Manage service applications.

  3. On the Manage Service Applications page, in the Type column, click the User Profile service application to select the row.

  4. On the ribbon, in the Operations group, click Manage.

  5. On the Manage Profile Service page, in the People section, click Manage User Properties.

  6. On the Manage User Profile Properties page, in the Property Name column, select the user profile property that you want to view, and then click Edit.

  7. On the Edit User Profile Property page, locate SAP Roles field (typically at the bottom of the page), and verify that SAP roles are displayed.

  8. When you are finished, click Cancel and Go Back.

    note Note:

    These SAP roles will also be available in People Picker when granting permissions to securable objects, such as sites, list, and files. SAP roles will also be available when you run shared reports if you have configured the Reporting solution.

Run the Duet Enterprise Configuration Check

Use this procedure to verify the configuration of Duet Enterprise 2.0 and to show the status of all imported models and features and verifies that the security configuration is working.

To run the Duet Enterprise Configuration Check

  1. Verify that you have the following administrative credentials: Windows Administrators group on the front-end web server that is running SharePoint Server 2013 to complete this procedure. You must also be a member of the Farm Administrators group on the SharePoint Server farm on which you are installing Duet Enterprise 2.0.

  2. As administrator, open a Windows Command Prompt window.

  3. At the command prompt, go to the directory to which you installed the Duet Enterprise 2.0 files. By default, this is the C:\Program Files\Duet Enterprise\2.0 folder.

  4. At the command prompt, type the following command, and then press ENTER:

    duetconfig.exe -CheckConfiguration

  5. At the command prompt, you receive the following message: "Please wait while the check configuration result is retrieved and written to the output file. This operation can take several minutes to complete…".

    The CheckConfiguration result is written to <systemDrive>:\Users\<useraccount>\AppData\Local\Temp\1\CheckConfigurationResult.xml, where <useraccount> equals the name of the publisher account specified when you configured the publishing URL and account.

  6. To view this file, browse to the location shown at the command prompt, and then open the CheckConfigurationResult.xml file in your XML-compatible web browser. You will have to allow all scripts to run.

  7. On the Duet Enterprise Configuration Check page, the following information is displayed:

    • Overall Status   This displays the overall status of all security connections, models, and features. If all these are working correctly, the status column will display Success.

    • Farm-Scoped Features   This displays the status of RoleSync, Validate Root Authority Certificate, and Security. If all these are working correctly, the status column will show Success for each. Note that RoleSync will show as failed until it is run for the first time. This is expected and does not indicate a problem. Running RoleSync one time will change this fail to success.

    • Web Application-Scoped Features   This displays the status of Publishing Settings, Reporting, and Workflow. If all these are working correctly, the status column will show Success for each.

  8. If any of these features, models, or items show as Failed in the status column, you can get more information about the failure by clicking Diagnostic Checks in the failed component section.

Related reports workaround

Use this procedure to update the external content types that support related reports for Duet Enterprise 1.0.

To configure related reports

  1. In Central Administration, in the Quick Launch, click Application Management.

  2. In the Service Applications section, click Manage service applications.

  3. In the Name column, click the link for the Business Data Connectivity service Application that you are using for Duet Enterprise 1.0.

  4. In the View section, select External Content Types.

  5. In the Name column, click an external content type that supports a related report. For example, the Account or Product external content type.

  6. On the View External Content Type page, scroll down the page, and then select the check box next to the form that you want to edit.

  7. On the ribbon, in the Actions group, click Edit.

    note Note:

    If the form that you selected does not contain a related report, the Edit option will be unavailable.

  8. On the Edit Action page, in the Navigate To This URL box, replace the text Scheme_Id=REPORT to Scheme_Id=IWSES~DE_REPORT, and then click OK.

    Navigate To This URL screen shot
  9. Repeat steps 6 through 8 to edit additional forms within the selected content type. When all forms for the selected external content type are configured, continue to step 10.

  10. Repeat steps 1 through 9 to edit additional external content types.

Replace the Workflow Tasks Aggregation Web Part

You must remove the Workflow Tasks Aggregation Web Part on all pages in each site that contains this Web Part. You will then insert the Duet Enterprise 2.0 version of the Web Part. Until you do this, users will see the following Web Part error on those affected sites.

"Web Part Error: A Web Part or Web Form Control on this page cannot be displayed or imported. The type SAP.Office.DuetEnterprise.Workflow.TasksAggregationWP, SAP.Office.DuetEnterprise.Workflow, Version=1.0.1.0, Culture=neutral, PublicKeyToken=8ede04ace7fbcb32 could not be found or it is not registered as safe."

You can replace this web part manually or you can use the WFAggregatorWP.ps1 PowerShell script. If you have not already done so, you can download the script from MSDN Code Gallery.

Do one of the following:

To replace the Workflow Tasks Aggregation Web Part manually

  1. Browse to a site on that uses the Workflow Web Part. For example, this Web Part would have been used on every Workflow Tasks site, by default. For example, go to a Workflow Tasks site in a Duet Enterprise Sites site collection; click the Tasks Center tab; in the Quick Launch, click All Site Content; and in the Sites and Workspaces section, click the link to the workflow tasks site that you want to configure.

  2. On the site page that contains the Workflow Web Part, click the Page tab.

  3. On the ribbon, click Edit Page.

  4. Click the down-arrow for the old Web Part, and then click Delete.

    Workflow Web Part screen shot
  5. In the pane where you want to add the Workflow Web Part, click Add a Web Part.

  6. Under Categories, click Duet Enterprise.

  7. Under Web Parts, click My SAP Workflow Tasks, and then click Add.

  8. On the ribbon, click Stop Editing.

    The Workflow Tasks Web Part appears on the page.

  9. Proceed to Install and deploy Starter Services solutions.

To replace the Workflow Tasks Aggregation Web Part using the script

  1. Log on to a web server in the SharePoint Server farm. Ensure that you have the following permissions:

    • Member of the Windows Administrators group

    • Site collection administrator.

  2. On the Start menu, click All Programs.

  3. Click Microsoft SharePoint 2013 Products.

  4. Click SharePoint 2013 Management Shell.

  5. At the Windows PowerShell command prompt, enter the following command:

    <path>\WFAggregatorWP.ps1 <Workflow site URL>

    Where <path> is the location where you downloaded the scripts and <Workflow site URL> is the URL of the top-level site in a site collection that contains one or more Workflow Tasks sites. For example, if you downloaded the scripts to c:\scripts, and you are replacing web parts on the http://contoso/sites/Duet site collection, then you would enter c:\scripts\WFAggregatorWP.ps1 http://contoso/sites/Duet/.

  6. After you press Enter, the command prompt displays the URL of the sites being processed and the sites on which the web part was found. After at least one web part is found and replaced and the script is finished processing a particular site, the command prompt displays "Done". Otherwise the script processes the next site until all sites within the site collection are processed.

    The following screenshot is an example of the script's output. In this example, you can see that web parts were replaced on the TestTask and TestTask3 sites but a web part was not replaced on the TestTask2 site.

    Example output
  7. When the script completes for the specified site collection, repeat steps 5 through 6 for each remaining site collection that contains a Workflow Tasks Aggregation Web Part.

Resolve workflow template referencing old DLL

In Duet Enterprise 1.0, the workflow web parts existed in a dynamic link library (DLL) file that does not exist in Duet Enterprise 2.0. These web parts have been moved to a different DLL file. After installed Duet Enterprise 2.0, you must remove the references to the old web parts and replace them with the Duet Enterprise 2.0 web parts.

Workflow Tasks sites that are affected by this issue will display the following error message on the site:

Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type SAP.Office.DuetEnterprise.Workflow.TasksAggregationWP, SAP.Office.DuetEnterprise.Workflow, Version=1/0.1.0, Culture=neutral, PublicKeyToken=8ede04ace7fbcb32 could not be found or it is not registered as safe.

On the Workflow Tasks site, if you click Edit Page on the PAGE tab, and then click Add a Web Part, you will see the resource names from the old DLL file instead of the actual web part group and web part names for the affected web parts.

To delete the old Duet Enterprise Workflow Web Parts

  1. On the Workflow Tasks site, click the gear icon and then click Site settings.

  2. Under Site Collection Administration, click Go to top level site settings.

  3. Under Web Designer Galleries, click Web parts.

  4. Select the check-box next to the following web parts:

    • LinksViewerWebPart.webpart

    • TaskAttachmentsWP.webpart

    • TaskDetailsWP.webpart

    • TaskParticipantsWP.webpart

    • TasksAggregationWP.webpart

  5. In the Files tab of the Ribbon, click Delete Document.

To Deactivate and reactivate the Workflow feature

  1. On the Workflow Tasks site, click the gear icon and then click Site settings.

  2. Under Site Actions, click Manage site features.

  3. In the Duet Enterprise - SAP Workflow row, click Deactivate and then click Deactivate this feature. This removes the old web part from the Designer Gallery.

  4. After the feature is deactivated, click Activate to activate the Duet Enterprise - SAP Workflow feature. This puts the Duet Enterprise 2.0 version of the web part into the Web Designer Gallery.

To replace the old web part on the Workflow Tasks sites

  1. On the Workflow Tasks site, in the Ribbon, click the PAGE tab.

  2. In the Edit section, click Edit Page.

  3. Click the arrow in the old web part and then click Delete.

  4. Click Add a Web Part.

  5. Under Categories, click Duet Enterprise and then under Parts click My SAP Workflow Tasks and then click Add.

Install and deploy Starter Services solutions

Use the procedures in this section to install the Starter Services solutions to the SharePoint solution store and then deploy them to both the 14 and 15 hives. Deploying the solutions to both hives ensures that the solutions work on sites that use either the SharePoint 2010 or the SharePoint 2013 experience.

To install Starter Services solutions

  1. Log on to a front-end web server in the SharePoint Server 2013 farm as a member of the Windows Administrators group.

  2. As administrator, open a SharePoint 2013 Management Shell.

    Click Start, click All Programs, click Microsoft SharePoint 2013 Products, right-click SharePoint 2013 Management Shell, and then click Run as administrator.

  3. At the command prompt, type the following command, and then press ENTER:

    $solutionFolderPath = $env:PROGRAMFILES + 'duet enterprise\2.0\solutions\starter services'

  4. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\Account\OBACustomerWorkspace.wsp

  5. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\OrderToCash\OBAOrderToCash.wsp

  6. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\Portal\OBAPortal.wsp

  7. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\Product\OBAProductCenter.wsp

  8. Leave the SharePoint 2013 Management Shell open. You will use it in the next procedure.

    note Note:

    After each solution is installed, the name and SolutionID of the solution are displayed in the command prompt with the Status "Not Deployed."

Use the following procedure to deploy these solutions to both hives.

To deploy the Starter Services solutions

  1. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obacustomerWorkspace.wsp -gacdeployment -local -CompatibilityLevel all

  2. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obaproductcenter.wsp -gacdeployment -local -CompatibilityLevel all

  3. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obaordertocash.wsp -gacdeployment -local -CompatibilityLevel all

  4. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obaportal.wsp -gacdeployment -local -AllWebApplication -CompatibilityLevel all

Verify that the starter solutions are deployed

Use this procedure to verify that the starter services that you deployed in the previous procedure are deployed.

To verify starter services solutions are deployed

  1. In Central Administration, on the Quick Launch, click System Settings.

  2. In the Farm Management section, click Manage farm solutions.

  3. Verify that the following solutions have the Status "Deployed."

    • Obacustomerworkspace.wsp

    • Obaordertocash.wsp

    • Obaportal.wsp

    • Obaproductcenter.wsp

    note Note:

    You will not see solutions for Workflow, Reporting, or RoleSync on the Solution Management page in Central Administration because they are not deployed as .wsp packages in Duet Enterprise 2.0. Instead, they were installed and deployed earlier when you ran Setup.exe.

Add and deploy Duet Enterprise language packs for starter services

Use the procedures in this section to add the Duet Enterprise language packs to the SharePoint solution store and then deploy them to all web applications in your SharePoint farm.

You must know the language codes and language IDs for the languages that you are adding and deploying in the following procedures.

Table: Language codes and Language IDs

Language Language code Language ID

Arabic (Saudi Arabia)

ar-sa

1025

German

de-de

1031

English (United States)

en-us

1033

Spanish

es-es

3082

French

fr-fr

1036

Hebrew (Israel)

he-il

1037

Italian

it-it

1040

Japanese

ja-jp

1041

Portuguese (Brazil)

pt-br

1046

Russian

ru-ru

1049

Turkish

tr-tr

1055

Chinese (China)

zh-cn

2052

Chinese (Taiwan)

zh-tw

1028

To add Duet Enterprise language packs for Starter Services Solutions

  1. Log on to a front-end web server in the SharePoint Server 2013 farm as a member of the Windows Administrators group.

  2. As administrator, open a SharePoint 2013 Management Shell.

    Click Start, click All Programs, click Microsoft SharePoint 2013 Products, right-click SharePoint 2013 Management Shell, and then click Run as administrator.

  3. At the command prompt, type the following command, and then press ENTER:

    $solutionFolderPath = $env:PROGRAMFILES + 'duet enterprise\2.0\solutions\starter services'

  4. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\Account\OBACustomerWorkspace.<LanguageCode>.wsp

    Where <LanguageCode> is the language code for the language that you are adding.

  5. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\OrderToCash\OBAOrderToCash.<LanguageCode>.wsp

    Where <LanguageCode> is the language code for the language that you are adding.

  6. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\Portal\OBAPortal.<LanguageCode>.wsp

    Where <LanguageCode> is the language code for the language that you are adding.

  7. At the command prompt, type the following command, and then press ENTER:

    Add-SPSolution $solutionFolderPath\Product\OBAProductCenter.<LanguageCode>.wsp

    Where <LanguageCode> is the language code for the language that you are adding.

  8. Repeat steps 4 through 7 for any additional languages that you want to add.

  9. Leave the SharePoint 2013 Management Shell open. You will use it in the next procedure.

To deploy the Duet Enterprise 2.0 language packs

  1. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obacustomerWorkspace.wsp -gacdeployment -local -CompatibilityLevel all -language <languageID>

    Where <languageID> is the language identifier for the language that you are deploying.

  2. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obaproductcenter.wsp -gacdeployment -local -CompatibilityLevel all -language <languageID>

    Where <languageID> is the language identifier for the language that you are deploying.

  3. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obaordertocash.wsp -gacdeployment -local -CompatibilityLevel all -language <languageID>

    Where <languageID> is the language identifier for the language that you are deploying.

  4. In the SharePoint 2013 Management Shell, type the following command, and then press ENTER:

    Install-SPSolution obaportal.wsp -gacdeployment -local CompatibilityLevel all -language <languageID>

    Where <languageID> is the language identifier for the language that you are deploying.

  5. Repeat steps 1 through 4 for each language that you are deploying.

Post-upgrade cleanup

Use the procedures in this section to clean up traces of the Duet Enterprise 1.0 installation.

In this section:

Delete the User Access List

Use this procedure to remove the User Access List for each Workflow Tasks site. For example, a Tasks Center site.

note Note:

You must be a site owner to complete this procedure.

To delete the User Access List

  1. In a browser, go to a Workflow Tasks site.

  2. Click Site Actions, and then click Site Settings.

  3. In the Site Administration section, click Site libraries and lists.

  4. On the Site Libraries and Lists page, click the Customize "User Access List" link.

    note Note:

    If this link does not exist on the page, it means that this list does not exist and no further action is necessary.

  5. On the List Settings page, in the Permissions and Management section, click Delete this list.

  6. Click OK in the dialog box that is displayed to confirm that you want to delete this list.

  7. Repeat steps 1 through 7 on any additional Workflow Tasks sites.

Uninstall BDC Models (Optional)

We recommend that you uninstall the BDC models for the Workflow, Reporting, and RoleSync solutions that were provided by Duet Enterprise 1.0. You have replaced them with BDC models that use OData endpoints and use a different namespace than the BDC models provided with Duet Enterprise 1.0.

Complete this procedure to remove the BDC models listed in the following table. You do not have to remove any of the other BDC models that were provided with Duet Enterprise 1.0.

Model name Solution

ReportTemplate

Reporting

Role

RoleSync

SAP.Office.DuetEnterprise.Workflow

Workflow

SAP.Office.DuetEnterprise.Workflow.UserSubscription

Workflow

UserRoles

RoleSync

note Note:

You must be a farm administrator to complete this procedure.

To uninstall BDC models

  1. In Central Administration, on the Application Management page, in the Service Applications section, click Manage service applications.

  2. In the Business Data Connectivity Service Application Proxy row, click the link in the Name column.

  3. On the ribbon, in the View section, select BDC Models.

  4. In the BDC Model Name column, select the check box next to ReportTemplate.

  5. On the ribbon, click Delete, and then in the dialog box that appears, click OK to confirm that you want to delete this BDC model.

  6. In the BDC Model Name column, select the check box next to Role.

  7. On the ribbon, click Delete, and then in the dialog box that appears, click OK to confirm that you want to delete this BDC model.

  8. In the BDC Model Name column, select the check box next to SAP.Office.DuetEnterprise.Workflow.

  9. On the ribbon, click Delete, and then in the dialog box that appears, click OK to confirm that you want to delete this BDC model.

  10. In the BDC Model Name column, select the check box next to SAP.Office.DuetEnterprise.Workflow.UserSubscription.

  11. On the ribbon, click Delete, and then in the dialog box that appears, click OK to confirm that you want to delete this BDC model.

  12. In the BDC Model Name column, select the check box next to UserRoles.

  13. On the ribbon, click Delete and then in the dialog box that appears, click OK to confirm that you want to delete this BDC model.

    Important Important:

    Do not uninstall any of the other Duet Enterprise 1.0 BDC models that are not named in this procedure. The remaining Duet Enterprise 1.0 BDC models will be reused for Duet Enterprise 2.0.

Install Report feature

We recommend that you complete this procedure to avoid receiving the "Provisioning did not succeed. Details: Failed to completely create the top-level Web site. OriginalException: Object reference not set to an instance of an object" error when you create a new Reporting workspace. Note that this procedure installs the feature to both the 14 and 15 hives.

To install the Report feature

  1. Log on to a front-end web server in the SharePoint Server 2013 farm as a member of the Windows Administrators group.

  2. As administrator, open a SharePoint 2013 Management Shell.

    Click Start, click All Programs, click Microsoft SharePoint 2013 Products, right-click SharePoint 2013 Management Shell, and then click Run as administrator.

  3. At the command prompt, type the following command, and then press ENTER:

    Install-SPFeature OBAReportDataTypes –force –CompatibilityLevel 14

  4. At the command prompt, type the following command, and then press ENTER:

    Install-SPFeature OBAReportDataTypes –force –CompatibilityLevel 15

Enable the 2013 experience

When a site collection is available to upgrade, site collection administrators see a status bar on their sites indicating that they can upgrade them. They can choose to upgrade the site collection then or be reminded later. If the 2013 experience was disabled on site collections when upgrading to Duet Enterprise 1.0 on the SharePoint 2013 farm, you can re-enable the 2013 experience now.

For information about enabling the ability to upgrade a site collection to the 15 experience, see Manage site collection upgrades to SharePoint 2013.

Verify upgrade

We recommend that you verify that SharePoint is able to communicate with the SAP system and that solutions are healthy by running a configuration health check. For more information, see Configuration check for Duet Enterprise for SharePoint and SAP Server 2.0.

We also recommend that you verify any customizations that you might have made to the Duet Enterprise sites on the SharePoint Server 2010 farm work as expected on the SharePoint Server 2013 farm. Also verify that the Duet Enterprise solutions are working as expected at the site-level.

Verify enlisted tasks

Verify that all enlisted tasks that were created in Duet Enterprise 1.0 are working correctly. Site pages in an enlisted task site, that were created using the Duet Enterprise Workflow import feature, will be un-ghosted. On such sites, after upgrading to Duet Enterprise 2.0, the pages will continue to point to the old Duet Enterprise 1.0 dynamic link libraries (DLLs). In such cases, Duet Enterprise 2.0 can fail to load the Task details page. Complete this procedure to resolve this issue.

note Note:

You must be a site owner to complete the following procedures.

To verify and fix enlisted Task Details page issue

  1. In a browser, go to a Task Site.

  2. Open a task in an enlisted (imported) task site.

  3. If the task does not open, continue to step 4. Otherwise if you have additional Task Sites to verify, go to step 1. If you have no more Task Sites to verify, no additional action is necessary.

  4. In a browser, go to the Site pages library of the affected Task Site.

  5. Delete the wrktaskip.aspx page.

  6. As administrator, open a SharePoint 2013 Management Shell.

    Click Start, click All Programs, click Microsoft SharePoint 2013 Products, right-click SharePoint 2013 Management Shell, and then click Run as administrator.

  7. Deactivate the SAPWorkflowSite feature.

  8. Activate the SAPWorkflowSite feature.

  9. In a browser, go to the Task Site and verify that the Task Details page opens.

Enable user access to SAP data

You are now ready to enable users to access SAP data on the SharePoint Server 2013 farm. If you are using host names, this might be done by updating the IP address in DNS for each web application.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.