About the Microsoft BizTalk Adapter Pack

Software Prerequisites

Software Prerequisites When Using the Adapters Through a .NET Application

Software Prerequisites When Using the Adapters with BizTalk Server

Software Prerequisites When Using the Adapters with ADO

Software Prerequisites When Using the Adapters with Microsoft Office SharePoint Server

Supported Enterprise Application Versions

For the Oracle Database Adapter

For the SAP Adapter

For the Siebel Adapter

For the SQL Adapter

For the Oracle E-Business Adapter

Compatibility Matrix Between 32-bit and 64-bit Versions of the Adapter, BizTalk Server, and Operating System

Installing the BizTalk Adapter Pack

Types of Installation

Scenarios for Installing the BizTalk Adapter Pack on 32-bit and 64-bit Platforms

Installing the BizTalk Adapter Pack in Interactive Mode

Installing the BizTalk Adapter Pack in Silent Mode

After Installing the BizTalk Adapter Pack

Installing the Enterprise Applications

Installation and Post-Installation Checklist

Modifying the BizTalk Adapter Pack Installation

Removing the BizTalk Adapter Pack

After Removing the BizTalk Adapter Pack

Removing the Custom RFCs

Upgrading from Previous Releases of the BizTalk Adapter Pack

Accessing the Adapter Pack Forum

Welcome to the Microsoft BizTalk Adapter Pack 2010 Installation Guide. This document provides software requirements and detailed instructions for installing the Microsoft BizTalk Adapter Pack.

For the latest version of this installation guide, go to http://go.microsoft.com/fwlink/?LinkID=188849.

About the Microsoft BizTalk Adapter Pack

The Microsoft BizTalk Adapter Pack contains adapters that enable enterprise applications and databases to interface with each other by implementing a common adapter framework. Similar to programming to Web services, adapters enable clients to program to different enterprise applications. Technically, adapters are a binding to Windows Communication Framework (WCF). The BizTalk Adapter Pack consists of the following adapters:

  • Microsoft BizTalk Adapter for Oracle Database (Oracle Database adapter).

  • Microsoft BizTalk Adapter for Oracle E-Business Suite (Oracle E-Business adapter).

  • Microsoft BizTalk Adapter for mySAP Business Suite (SAP adapter). This also includes the .NET Framework Data Provider for mySAP Business Suite (Data Provider for SAP).

  • Microsoft BizTalk Adapter for Siebel eBusiness Applications (Siebel adapter). This also includes the .NET Framework Data Provider for Siebel eBusiness Applications (Data Provider for Siebel).

    Note

    The Siebel adapter is not available for 64-bit platforms.

  • Microsoft BizTalk Adapter for SQL Server (SQL adapter).

Top of page

Software Prerequisites

The BizTalk Adapter Pack can be consumed from:

  • A .NET application

  • Microsoft BizTalk Server

  • An ADO interface

  • A Microsoft SharePoint portal

Based on how you use the adapters, the required software will vary.

Software Prerequisites When Using the Adapters Through a .NET Application

You must ensure the following software is installed on the computer where you will be using the BizTalk Adapter Pack to write .NET applications on top of the adapter. We recommend installing the software in the same order as listed here.

  1. Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 4

    Important

    .NET Framework 4 is essential to use BizTalk Adapter Pack with BizTalk Server 2010. However, you can use .NET Framework 3.5 SP1 and .NET Framework 4 to write .NET applications (channel/proxy) for connecting using adapters.

  2. Microsoft Visual Studio 2010

  3. The Microsoft Windows Communication Foundation (WCF) Line of Business (LOB) Adapter SDK (WCF LOB Adapter SDK)2010. You can download WCF LOB Adapter SDK 2010 from http://go.microsoft.com/fwlink/?LinkID=189401.

  4. Respective enterprise application clients and associated software. For the enterprise application client versions and other supporting DLLs that you must install for each adapter, see Supported Enterprise Application Versions.

Software Prerequisites When Using the Adapters with BizTalk Server

You must ensure the following software is installed on the computer where you will be using the BizTalk Adapter Pack with BizTalk Server. We recommend installing the software in the same order as listed here.

  • Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 4

    Important

    .NET Framework 4 is essential to use BizTalk Adapter Pack with BizTalk Server 2010. However, you can use .NET Framework 3.5 SP1 and .NET Framework 4 to write .NET applications (channel/proxy) for connecting using adapters.

  • Microsoft Visual Studio 2010

  • The Microsoft Windows Communication Foundation (WCF) Line of Business (LOB) Adapter SDK (WCF LOB Adapter SDK) 2010. You can download WCF LOB Adapter SDK 2010 from http://go.microsoft.com/fwlink/?LinkID=147367.

    Important

    You must also install a BizTalk add-in (Consume Adapter Service BizTalk Project Add-in) for Visual Studio that is shipped with the WCF LOB Adapter SDK. To install this add-in, you must perform a Custom or Complete installation of the WCF LOB Adapter SDK. Under the Custom option, select BizTalk Server Addin. Also, to install the add-in you must have installed Visual Studio before installing the WCF LOB Adapter SDK.

  • Microsoft BizTalk Server 2010

  • Respective enterprise application clients and associated software. For the enterprise application client versions and other supporting DLLs that you must install for each adapter, see Supported Enterprise Application Versions.

Software Prerequisites When Using the Adapters with ADO

The Microsoft BizTalk Adapter for mySAP Business Suite and Microsoft BizTalk Adapter for Siebel eBusiness Applications also include an ADO layer (Data Provider for SAP and Data Provider for Siebel), which you can use to write an ADO.NET client to connect to an SAP system or Siebel system, respectively. You can also use the ADO layer with SQL Server Integration Services (SSIS) to import and export data from the LOB application, and SQL Server Reporting Services (SSRS) to generate reports to present data from the LOB systems.

Note

Using the ADO Provider with SSRS is supported only for the Data Provider for SAP.

Ensure that the following software is installed on the computer where you will be using the BizTalk Adapter Pack with an ADO interface. We recommend installing the software in the same order as listed here.

  • Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 4

    Important

    .NET Framework 4 is essential to use BizTalk Adapter Pack with BizTalk Server 2010. However, you can use .NET Framework 3.5 SP1 and .NET Framework 4 to write .NET applications (channel/proxy) for connecting using adapters.

  • Microsoft Visual Studio 2008

  • The Microsoft Windows Communication Foundation (WCF) Line of Business (LOB) Adapter SDK (WCF LOB Adapter SDK) 2010. You can download WCF LOB Adapter SDK 2010 from http://go.microsoft.com/fwlink/?LinkID=147367.

  • SQL Server 2008 SP1 or SQL Server 2008 R2

  • Respective enterprise application clients and associated software. For the enterprise application client versions and other supporting DLLs that you must install for each adapter, see Supported Enterprise Application Versions.

Software Prerequisites When Using the Adapters with Microsoft Office SharePoint Server

The goal of using the adapters with Microsoft Office SharePoint Server is to present data from an LOB application on a SharePoint portal. To achieve this, a typical setup with the BizTalk Adapter Pack and Microsoft Office SharePoint Server involves the following:

  • A computer where you run the WCF Adapter Service Development Wizard.

  • A computer where you host the WCF service.

  • A computer where you can use the SharePoint Designer to define your External Content Types.

  • A computer where you use Microsoft Office SharePoint Server to present the information from an LOB application.

You may choose to have a single computer that can be used to do all the preceding tasks. However, if you choose to use different computers for different tasks, the following table summarizes the software prerequisites for each computer. If you are using a single computer, all the software must be present on that computer. We recommend installing the software in the same order as listed here.

Where the WCF Adapter Service Development Wizard is used

Where the WCF service is hosted

Where the Business Data Catalog Definition Editor is used

Where Microsoft Office SharePoint Server is used

  • Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 4

  • Microsoft Visual Studio 2010

  • The Microsoft Windows Communication Foundation (WCF) Line of Business (LOB) Adapter SDK (WCF LOB Adapter SDK) 2010. You can download WCF LOB Adapter SDK 2010 from the Microsoft BizTalk Adapter Pack installation disk.

  • Microsoft BizTalk Adapter Pack 2010

  • Respective enterprise application clients and associated software. See for the enterprise application client versions and other supporting DLLs that you must install for each adapter.

  • Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 4

  • The Microsoft Windows Communication Foundation (WCF) Line of Business (LOB) Adapter SDK (WCF LOB Adapter SDK) 2010. You can download WCF LOB Adapter SDK 2010 from the Microsoft BizTalk Adapter Pack installation disk.

  • Microsoft BizTalk Adapter Pack 2010

  • Respective enterprise application clients and associated software. For the enterprise application client versions and other supporting DLLs that you must install for each adapter, see .

  • Internet Information Services (IIS) 7.0

Top of page

Supported Enterprise Application Versions

The following section presents the server and client versions for the enterprise applications with which BizTalk Adapter Pack can be used. This section also provides information about the other client DLLs required for the BizTalk Adapter Pack.

For the Oracle Database Adapter

  • Supported server versions: Oracle database version 11.1, Oracle database version 10.2, Oracle database version 10.1, Oracle database version 9.2

  • Supported client versions: Oracle Data Access Components for Oracle Client 11.1.0.6 with Patch Set 11.1.0.7, Oracle Data Access Components for Oracle Client 11.1.0.7

    Important

    If you want to use the adapter to perform transactions on the Oracle database, make sure you install the Oracle Services For Microsoft Transaction Server component on the computer running the adapter client. You must install this as part of the Oracle client installation.

    Note

    To make sure your application works with the most recent version of ODP.NET, you must have the "policy DLLs" installed on the computer and registered in the GAC. For more information, see "Oracle Data Provider for .NET FAQ" at http://go.microsoft.com/fwlink/?LinkID=92834.

  • Supported client operating systems: Windows Server 2008 SP2, Windows Server 2008 R2, Windows Vista SP2, Windows 7

For the SAP Adapter

  • Supported server versions: SAP ECC 6.0 Unicode, SAP ECC 6.0 with EHP 4.0, SAP ECC 5.0 Non-Unicode, SAP ECC 5.0 Unicode, SAP R/3 4.7 Non-Unicode, SAP R/3 4.7 Unicode, SAP R/3 4.6c Non-Unicode

  • Supported client versions: SAP RFC SDK 7.11 UNICODE, SAP RFC SDK 7.1 UNICODE, SAP RFC SDK 7.0 UNICODE, SAP RFC SDK 6.4 UNICODE

    Note

    The SAP adapter requires Unicode version of the RFC SDK irrespective of whether the SAP system is Unicode or non-Unicode.

  • Supported client operating systems: Windows Server 2008 SP2, Windows Server 2008 R2, Windows Vista SP2, Windows 7

  • Required drivers: The following table lists the DLLs required by the BizTalk Adapter Pack to interface with the SAP system. Most of the packages that contain these DLLs must be downloaded from the SAP Service Marketplace.

    To obtain downloads from the SAP Service Marketplace, you must first:

    • Install the Download Manager available from the SAP Service Marketplace.

    • Configure the Download Manager by using your credentials for the SAP Service Marketplace.

    • Be authorized by the SAP administrator in your organization to download software from the SAP service Web site. This is required because access to the SAP Software Distribution Center is restricted by a 'Download Software' authorization object. This ensures that software is downloaded only by authorized users.

    • Install the program, SAPCAR, required to extract the files from the packages that you download from the SAP Service Marketplace. The SAPCAR is also available from the SAP Service Marketplace.

    For the 32-bit and 64-bit version of the BizTalk Adapter Pack, you must have the respective 32-bit and 64-bit versions of these DLLs.

    • On a 32-bit computer, the 32-bit version of the DLLs must be added to the C:\Windows\System32 folder.

    • On a 64-bit computer, the 32-bit version of the DLLs must be added to the C:\Windows\SysWow64 folder. The 64-bit version of the DLLs must be added to the C:\Windows\System32 folder.

    SAP client version

    Required drivers

    6.4

    • SAP RFC SDK 6.40 UNICODE. This is available as part of SNOTE* 27517. The instructions to download the SDK are available at http://go.microsoft.com/fwlink/?LinkID=94691. After you have downloaded and extracted the SDK, copy all the DLLs from the \rfcsdk\bin and \rfcsdk\lib folders to the relevant location mentioned preceding this table.

    • DLLs are available from SAP as part of R3DLLINST.zip. This contains Microsoft run-time DLLs and can be downloaded from the SAP site. See SNOTE* 684106 for more information. You can download the .zip file from http://go.microsoft.com/fwlink/?LinkID=94693. This link has an “Attachments” option from where you can download the package.

    • If you use SAP Secure Network Communications (SNC) to connect to an SAP system, you must also have the relevant DLLs from SAP. These DLLs are different for 32-bit and 64-bit platforms and are available with SNOTE* 352295. You can download the DLLs from http://go.microsoft.com/fwlink/?LinkID=104032. This link has an “Attachments” option from where you can download the package. The names of the DLLs are:

    • For 32-bit: gsskrb5.dll, gssntlm.dll

    • For 64-bit x86: gx64krb5.dll, gx64ntlm.dll

    7.0

    • SAP RFC SDK 7.00 UNICODE. This is available as part of SNOTE* 27517. The instructions to download the SDK are available at http://go.microsoft.com/fwlink/?LinkID=94691. After you have downloaded and extracted the SDK, copy all the DLLs from the \rfcsdk\bin and \rfcsdk\lib folders and to the relevant location mentioned preceding this table.

    • DLLs are available from SAP as part of R3DLLINST.zip. This contains Microsoft run-time DLLs and can be downloaded from the SAP site. See SNOTE* 684106 for more information. You can download the .zip file from http://go.microsoft.com/fwlink/?LinkID=94693. This link has an “Attachments” option from where you can download the package.

    • If you use SAP Secure Network Communications (SNC) to connect to an SAP system, you must also have the relevant DLLs from SAP. These DLLs are different for 32-bit and 64-bit platforms and are available with SNOTE* 352295. You can download the DLLs from http://go.microsoft.com/fwlink/?LinkID=104032. This link has an “Attachments” option from where you can download the package. The names of the DLLs are:

    • For 32-bit: gsskrb5.dll, gssntlm.dll

    • For 64-bit x86: gx64krb5.dll, gx64ntlm.dll

    7.1

    • SAP RFC SDK 7.10 UNICODE. This is available as part of SNOTE* 27517. The instructions to download the SDK are available at http://go.microsoft.com/fwlink/?LinkID=94691. After you have downloaded and extracted the SDK, copy all the DLLs from the \rfcsdk\bin and \rfcsdk\lib folders to the relevant location mentioned preceding this table.

    • DLLs are available from SAP as part of R3DLLINST.zip. This contains Microsoft run-time DLLs and can be downloaded from the SAP site. See SNOTE* 684106 for more information. You can download the .zip file from http://go.microsoft.com/fwlink/?LinkID=94693. This link has an “Attachments” option from where you can download the package.

    • Microsoft Visual C++ run-time DLLs required for SAP 7.1 client are available from the following links:

    • If you use SAP Secure Network Communications (SNC) to connect to an SAP system, you must also have the relevant DLLs from SAP. These DLLs are different for 32-bit and 64-bit platforms and are available with SNOTE* 352295. You can download the DLLs from http://go.microsoft.com/fwlink/?LinkID=104032. This link has an “Attachments” option from where you can download the package. The names of the DLLs are:

    • For 32-bit: gsskrb5.dll, gssntlm.dll

    • For 64-bit x86: gx64krb5.dll, gx64ntlm.dll

    7.11

    • SAP RFC SDK 7.11 UNICODE. This is available as part of SNOTE* 27517. The instructions to download the SDK are available at http://go.microsoft.com/fwlink/?LinkID=94691. After you have downloaded and extracted the SDK, copy all the DLLs from the \rfcsdk\bin and \rfcsdk\lib folders to the relevant location mentioned preceding this table.

    • DLLs are available from SAP as part of R3DLLINST.zip. This contains Microsoft run-time DLLs and can be downloaded from the SAP site. See SNOTE* 684106 for more information. You can download the .zip file from http://go.microsoft.com/fwlink/?LinkID=94693. This link has an “Attachments” option from where you can download the package.

    • Microsoft Visual C++ run-time DLLs required for SAP 7.11 client are available from the following links:

    • If you use SAP Secure Network Communications (SNC) to connect to an SAP system, you must also have the relevant DLLs from SAP. These DLLs are different for 32-bit and 64-bit platforms and are available with SNOTE* 352295. You can download the DLLs from http://go.microsoft.com/fwlink/?LinkID=104032. This link has an “Attachments” option from where you can download the package. The names of the DLLs are:

    • For 32-bit: gsskrb5.dll, gssntlm.dll

    • For 64-bit x86: gx64krb5.dll, gx64ntlm.dll

    * SNOTEs are release notes that accompany fixes released by SAP.

For the Siebel Adapter

  • Supported server versions:

    • Siebel 8.0: 8.0.0.2

    • Siebel 7.8: 7.8.2.8

    • Siebel 7.7: 7.7.2.10

    • Siebel 7.5: 7.5.3.17 + Quick Fix 7.5.3.17[16285]QF0H05

  • Supported client versions: Siebel Web Client 8.0, Siebel Web Client 7.8, Siebel Web Client 7.7, Siebel Web Client 7.5

  • Supported client operating systems: Windows Server 2008 SP2, Windows Vista SP2, Windows 7

    Note

    The Siebel adapter is not available for 64-bit platforms.

For the SQL Adapter

  • Supported server versions: SQL Server 2000, SQL Server 2005, SQL Server 2008 SP1, SQL Server 2008 R2

  • Supported client versions: Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 4 bundle the client DLLs required to connect to SQL Server. You do not need to explicitly install any client DLLs on your computer.

  • Supported client operating systems: Windows Server 2008 SP2, Windows Server 2008 R2, Windows Vista SP2, Windows 7

  • Required drivers:

    • For SQL Server 2005: If you create User Defined Types (UDTs) in SQL Server, make sure the respective assemblies for the UDTs are added to the GAC.

    • For SQL Server 2008 SP1 or SQL Server 2008 R2:

      • If you use the UDTs shipped with SQL Server 2008 SP1 or SQL Server 2008 R2, for example, Geography, make sure the following DLLs are present on the computer where you use the adapter to perform operations on SQL Server. For example, if you create BizTalk projects to perform operations on SQL Server, these DLLs must be present on the computer where BizTalk Server is running.

        • Make sure Microsoft.SqlServer.Types.dll is added to the GAC.

        • Make sure SqlServerSpatial.dll is available in the System32 folder.

        You can install these DLLs on the computer by running the SQL Server 2008 SP1 or SQL Server 2008 R2 setup and selecting Management Tools – Basic and Management Tools – Complete in the Feature Selection page of the wizard.

      • If you use the adapter to perform operations on columns of FILESTREAM data types, make sure you have SQL Client Connectivity SDK installed. You can install the SQL Client Connectivity SDK by running the SQL Server 2008 SP1 or SQL Server 2008 R2 setup and selecting SQL Client Connectivity SDK in the Feature Selection page of the wizard. The adapter uses the sqlncli10.dll, installed with the SQL Client Connectivity SDK, to perform FILESTREAM operations.

      • If you create your own UDTs in SQL Server, make sure the respective assemblies for the UDTs are added to the GAC.

For the Oracle E-Business Adapter

  • Supported server versions: Oracle E-Business Suite 12 (with Oracle database version 10.2), Oracle E-Business Suite 11.5.10.2 (with Oracle database version 10.2), Oracle E-Business Suite 11.5.10.2 (with Oracle database version 9.2), Oracle E-Business Suite 12.1 (with Oracle Database 11.1)

  • Supported client versions: Oracle Data Access Components for Oracle Client 11.1.0.6 with Patch Set 11.1.0.7, Oracle Data Access Components for Oracle Client 11.1.0.7

    Important

    If you want to use the adapter to perform transactions on the Oracle E-Business Suite, make sure you install the Oracle Services For Microsoft Transaction Server component on the computer running the adapter client. You must install this as part of the Oracle client installation.

    Note

    To make sure your application works with the most recent version of ODP.NET, you must have the "policy DLLs" installed on the computer and registered in the GAC. For more information, see http://go.microsoft.com/fwlink/?LinkID=92834.

  • Supported client operating systems: Windows Server 2008 SP2, Windows Server 2008 R2, Windows Vista SP2, Windows 7

Top of page

Compatibility Matrix Between 32-bit and 64-bit Versions of the Adapter, BizTalk Server, and Operating System

The following table presents a compatibility matrix between the 32-bit and 64-bit versions of the operating system, adapter, and BizTalk Server.

Oracle Database Adapter + BizTalk Server

SAP Adapter + BizTalk Server

Siebel Adapter + BizTalk Server

Oracle E-Business Adapter + BizTalk Server

SQL Adapter + BizTalk Server

Operating System

32-bit

64-bit

32-bit

64-bit

Yes

N/A

Yes

Yes

32-bit

64-bit

Yes

N/A

Yes

Yes

32-bit

64-bit

Yes

N/A

No

No

32-bit

64-bit

Yes

N/A

Yes

Yes

32-bit

64-bit

Yes

N/A

Yes

Yes

Legend

  • Yes = Supported.

  • No = Not supported.

  • N/A = Not Applicable.

For more information about the supported installation scenarios for installing the 32-bit and 64-bit BizTalk Adapter Pack, see Scenarios for Installing the BizTalk Adapter Pack on 32-bit and 64-bit Platforms.

Top of page

Installing the BizTalk Adapter Pack

Make sure you have the prerequisites installed before installing the BizTalk Adapter Pack. For more information, see Software Prerequisites. You can install the BizTalk Adapter Pack in the following two ways:

  • In interactive mode: By running the setup wizard

  • In silent mode: By using the command line

    Important

    You must have administrative privileges on the computer where you install the BizTalk Adapter Pack, irrespective of whether you are installing by using the wizard or the command line.

Types of Installation

This section lists the types of BizTalk Adapter Pack installations and the features that install according to the particular type of installation you choose when running the setup wizard.

You can choose from the following types of installation:

  • The Typical and Complete options install all the adapters, with the associated data providers. You do not have the option of choosing a particular adapter to install.

  • The Custom option installs one or more adapters, with the associated data providers. You can choose the adapters that you want to install. If you choose to install a data provider, you must install the corresponding adapter also. However, you can install an adapter without installing the corresponding data provider. You do this by expanding the ADO Providers node, and then selecting the providers that you do not want to install. See Installing the BizTalk Adapter Pack in Interactive Mode.

    For example, if you choose to install the Data Provider for SAP, you must also install the SAP adapter. However, you can install the SAP adapter without installing the Data Provider for SAP.

Scenarios for Installing the BizTalk Adapter Pack on 32-bit and 64-bit Platforms

With BizTalk Server, the BizTalk Adapter Pack can be used for:

  • Visual Studio design time (when generating metadata for operations on LOB applications).

  • BizTalk Server Administration console design time (for creating physical ports).

    Note

    BizTalk Server Administration console runs as a 32-bit Microsoft Management Console (MMC) application.

  • BizTalk run time (when sending and receiving messages from LOB applications).

You can have an installation setup where you perform all these tasks on the same computer or different computers. Because both Visual Studio and BizTalk MMC are 32-bit processes, you must install the 32-bit BizTalk Adapter Pack on the computer where you want to perform the design-time tasks. Here are the supported scenarios for installing the BizTalk Adapter Pack on 32-bit and 64-bit platforms.

Scenarios for Installing the BizTalk Adapter Pack on a 32-bit Platform

The following are the supported scenarios for installing the BizTalk Adapter Pack on a 32-bit platform.

For Visual Studio design time

For BizTalk MMC design time

For BizTalk run time

For Visual Studio design time and/or BizTalk MMC design time + BizTalk run time

  • Install 32-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

  • Install 32-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

  • Install 32-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

  • Install 32-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

Scenarios for Installing the BizTalk Adapter Pack on a 64-bit Platform

The following are the supported scenarios for installing the BizTalk Adapter Pack on a 64-bit platform.

For Visual Studio design time

For BizTalk MMC design time

For BizTalk run time

For Visual Studio design time and/or BizTalk MMC design time + BizTalk run time

  • Install 64-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

  • Install 64-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

For a 32-bit BizTalk process:

  • Install 64-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

For a 64-bit BizTalk process:

  • Install 64-bit WCF LOB Adapter SDK.

  • Install 64-bit BizTalk Adapter Pack.

  • Install 64-bit LOB client and other required DLLs.

For a 32-bit BizTalk process:

  • Install 64-bit WCF LOB Adapter SDK.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

For a 64-bit BizTalk process:

  • Install 64-bit WCF LOB Adapter SDK.

  • Install 64-bit BizTalk Adapter Pack.

  • Install 64-bit LOB client and other required DLLs.

  • Install 32-bit BizTalk Adapter Pack.

  • Install 32-bit LOB client and other required DLLs.

Note

On any computer where you want to perform design-time tasks, using either Visual Studio or BizTalk MMC, you must install the 32-bit BizTalk Adapter Pack.

Installing the BizTalk Adapter Pack in Interactive Mode

Perform the following steps to install the BizTalk Adapter Pack using the setup wizard.

To install the BizTalk Adapter Pack in interactive mode

  1. Insert the Microsoft BizTalk Adapter Pack installation disk into the CD-ROM drive.

  2. From the root location of the installation CD, double-click AdaptersSetup.msi (for an x86-based platform) or AdaptersSetup64.msi (for an x64-based platform).

    Note

    If you are installing the BizTalk Adapter Pack on a virtual machine, the setup wizard might not proceed beyond a dialog box informing that the setup is checking for available disk space. In such cases, we recommend that you use the silent installation option. For more information, see Installing the BizTalk Adapter Pack in Silent Mode.

  3. Read the information on the Welcome screen, and then click Next.

  4. Read and accept the end-user license agreement (EULA), and then click Next.

  5. In the Choose Setup Type dialog box:

    • To install the most common features, click Typical.

    • To select the adapters you want to install, click Custom, and then proceed to the next step.

    • To install all the features, click Complete.

      Important

      To install only the adapter that you use to interface with your enterprise application, you should perform a Custom installation.

  6. Perform this step if you chose to do a Custom installation in the previous step. If you chose to perform a Typical or Complete installation, proceed to step 7.

    1. In the Custom Setup dialog box, expand the Base Adapters node to see the list adapters available with the BizTalk Adapter Pack.

    2. For the adapters that you do not want to install, click the icon next to the adapter name, and then select Entire feature will be unavailable.

    3. Similarly, expand the ADO Providers node, and then select the providers that you do not want to install.

    4. Click Next.

  7. Click Install.

  8. In the Customer Experience Improvement Program dialog box, specify whether you would like to enroll for the Customer Experience Improvement Program (CEIP). As part of CEIP for BizTalk Adapter Pack, you can share the following data with Microsoft:

    • Data related to the computer hardware on which you are installing the BizTalk Adapter Pack.

    • Data related to the enterprise application versions you will be using with the BizTalk Adapter Pack.

    Specify your choice and click OK. For more information about CEIP, see http://go.microsoft.com/fwlink/?LinkID=144699.

    Note

    You can always change your preference regarding enrolling for CEIP by running the Setup in Repair mode from the Control Panel.

  9. Click Finish.

Installing the BizTalk Adapter Pack in Silent Mode

Use the msiexec command to perform a silent installation of the BizTalk Adapter Pack. As part of the msiexec command, you must specify the individual components that you want to install. The following table lists the values for each component in the BizTalk Adapter Pack. Provide these values to install (or remove) specific components. To install (or remove) more than one component, you can provide a combination of these values separated by a comma.

Component name

Corresponding value for command-line properties

Oracle Database adapter

DbFeature

Oracle E-Business adapter

OracleEBSFeature

SAP adapter

SapBaseAdapterFeature

Siebel adapter

SiebelBaseAdapterFeature

SQL adapter

SqlFeature

Data Provider for SAP

SapAdoFeature

Note

You must provide this value only if you are installing the SAP adapter also.

Data Provider for Siebel

SiebelAdoFeature

Note

You must provide this value only if you are installing the Siebel adapter also.

All components

ALL

Important

The feature names are case-sensitive.

The following procedure demonstrates how to perform a silent installation of BizTalk Adapter Pack for different components.

To install the BizTalk Adapter Pack in silent mode

  1. Insert the Microsoft BizTalk Adapter Pack installation disk into the CD-ROM drive.

  2. Open a command prompt, and navigate to the root of the installation CD.

  3. Run the following commands based on what you want to install:

    Note

    To perform silent installation on an x64-based platform, in the following commands, replace AdaptersSetup.msi with AdaptersSetup64.msi.

    • To perform a complete installation, which installs all the adapters including the .NET Framework Data Providers, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=ALL
    • To install only the Oracle Database adapter, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=DbFeature
    • To install only the Oracle E-Business adapter, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=OracleEBSFeature
    • To install only the SAP adapter, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SapBaseAdapterFeature
    • To install the SAP adapter along with Data Provider for SAP, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SapBaseAdapterFeature,SapAdoFeature
    • To install only the Siebel adapter, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SiebelBaseAdapterFeature
    • To install the Siebel adapter along with Data Provider for Siebel, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SiebelBaseAdapterFeature,SiebelAdoFeature
    • To install only the SQL adapter, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SqlFeature
    • To install all the base adapters, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SapBaseAdapterFeature,SiebelBaseAdapterFeature,DbFeature,OracleEBSFeature,SqlFeature
    • To install the two .NET Framework Data Providers, type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SapAdoFeature,SiebelAdoFeature
    • Any type of custom installation by separating the components by a comma. For example, to install the SAP adapter with the Data Provider for SAP, and the Siebel adapter type:

      msiexec /i AdaptersSetup.msi /qn ADDLOCAL=SapBaseAdapterFeature,SapAdoFeature,SiebelBaseAdapterFeature
    • You can also opt to enroll for CEIP as part of the silent installation. As part of CEIP for BizTalk Adapter Pack, you can share the following data with Microsoft:

      • The computer hardware on which you are installing the BizTalk Adapter Pack.

      • The enterprise application versions you are using to connect using the BizTalk Adapter Pack.

      To do so, type:

      msiexec /i AdaptersSetup.msi /qn CEIP_OPTIN=true
      By default the option is false. For more information about CEIP, see http://go.microsoft.com/fwlink/?LinkID=144699.

      Important

      While installing the BizTalk Adapter Pack Evaluation version in silent mode, the default option for CEIP is true.

    For more information about the msiexec command type msiexec on the command line and press ENTER or see http://go.microsoft.com/fwlink/?LinkID=103199.

After Installing the BizTalk Adapter Pack

You might need to perform the following tasks after installing the BizTalk Adapter Pack, based on what operations you want to perform using the adapter:

  • Invoking transactional RFCs (tRFCs) in an SAP system. If you want to invoke tRFCs in an SAP system, you must run the SQL script, SapAdapter-DbScript-Install.sql. This script is installed as part of the BizTalk Adapter Pack installation.

  • Manually registering the bindings. Register the adapter bindings and the .NET Framework Data Providers if the setup wizard failed to do so.

  • Using the Data Provider for SAP. You must install the custom RFCs if you chose to install the Data Provider for SAP.

Creating SQL Server Database Objects (Only for the SAP Adapter)

To invoke tRFCs in an SAP system you must run the SQL script, SapAdapter-DbScript-Install.sql. This script is installed as part of the BizTalk Adapter Pack installation and creates database objects in SQL Server. The script is typically installed at <installation drive>:\Program Files\Microsoft BizTalk Adapter Pack. You can run this script against any SQL Server database, as long as you specify that database name while using the adapter to invoke tRFCs.

Registering the Bindings

During the BizTalk Adapter Pack installation, the setup wizard may fail to register the adapter bindings or the .NET Framework Data Provider for mySAP Business Suite, but proceeds with the adapter installation. This might result due to problems with Windows Communication Foundation (WCF) installation, Microsoft Windows Communication Foundation (WCF) Line of Business (LOB) Adapter SDK installation, or the machine.config file being corrupt.

Perform these steps only if the setup wizard fails to register the adapter bindings or .NET Framework Data Providers in the machine.config file.

To register the adapter bindings or the .NET Framework Data Providers

  • Navigate to the machine.config file on the computer. For example, on a 32-bit platform, the machine.config is available under <system drive>:\WINDOWS\Microsoft.NET\Framework\<version>\CONFIG.

    • For Microsoft .NET Framework 3.5 SP1, <version> is the version v2.0.50727 of the .NET Framework.

    • For Microsoft .NET Framework 4, <version> is the version v4.0.30319 of the .NET Framework.

  • Open the file using a text editor.

  • To register the adapter bindings:

    1. Search for the element "system.serviceModel" and add the following under it:

      <client>
        <endpoint binding="sapBinding" contract="IMetadataExchange" name="sap" />
        <endpoint binding="siebelBinding" contract="IMetadataExchange" name="siebel" />
        <endpoint binding="oracleDBBinding" contract="IMetadataExchange" name="oracleDb" />
        <endpoint binding="oracleEBSBinding" contract="IMetadataExchange" name="oracleEBS" />
        <endpoint binding="sqlBinding" contract="IMetadataExchange" name="mssql" />
      </client>
    2. Search for the element "bindingElementExtensions" under system.serviceModel\extensions.

    3. Look for the missing adapter binding. Add the following sections under the "bindingElementExtensions" node, depending on the missing adapter binding. You must register all the bindings if the setup wizard fails to register any.

      For the SAP adapter, add:

      <add name="sapAdapter" type="Microsoft.Adapters.SAP.SAPAdapterExtensionElement,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For the Siebel adapter, add:

      <add name="siebelAdapter" type="Microsoft.Adapters.Siebel.SiebelAdapterExtensionElement,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For the Oracle Database adapter, add:

      <add name="oracleDBAdapter" type="Microsoft.Adapters.OracleDB.OracleDBAdapterExtensionElement,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For the Oracle E-Business adapter, add:

      <add name="OracleEBSAdapter" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingElementExtensionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For the SQL adapter, add:

      <add name="sqlAdapter" type="Microsoft.Adapters.Sql.SqlAdapterBindingElementExtensionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    4. Search for the element "bindingExtensions" under system.serviceModel\extensions.

    5. Look for the missing adapter binding. Add the following sections under the "bindingExtensions" node, depending on the missing adapter binding. You must register all the bindings if the setup wizard fails to register any.

      For SAP adapter, add:

      <add name="sapBinding" type="Microsoft.Adapters.SAP.SAPAdapterBindingSection,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Siebel adapter, add:

      <add name="siebelBinding" type="Microsoft.Adapters.Siebel.SiebelAdapterBindingSection,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Oracle Database adapter, add:

      <add name="oracleDBBinding" type="Microsoft.Adapters.OracleDB.OracleDBAdapterBindingSection,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Oracle E-Business adapter, add:

      <add name="OracleEBSBinding" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingCollectionElement, Microsoft.Adapters.OracleEBS,Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For SQL adapter, add:

      <add name="sqlBinding" type="Microsoft.Adapters.Sql.SqlAdapterBindingCollectionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      Note

      For information about how to determine the public key, see Determining the Public Key and Version.

    6. To register the .NET Framework Data Providers:

      1. Search for the element DbProviderFactories under the system.data node.

      2. Look for the missing .NET Framework Data Providers. Add the following sections under the DbProviderFactories node, depending on the missing provider. You must register all the providers if the setup wizard fails to register any.

        For the Data Provider for SAP, add:

        <add name="SAPClient Data Provider" invariant="Microsoft.Data.SAPClient" 
            description=".NET Framework Data Provider for mySAP Business Suite"    type="Microsoft.Data.SAPClient.SAPClientFactory,Microsoft.Data.SAPClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        
        For the Data Provider for Siebel, add:

        <add name="SiebelClient Data Provider" invariant="Microsoft.Data.SiebelClient"
            description=".NET Framework Data Provider for Siebel eBusiness Applications"
            type="Microsoft.Data.SiebelClient.SiebelProviderFactory,Microsoft.Data.SiebelClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        
      3. Save and close the machine.config file.

Determining the Public Key and Version

Perform the following steps to determine the public key and version for an adapter or .NET Framework Data Provider.

To determine the public key

  1. Navigate to the Windows directory, typically C:\WINDOWS\assembly.

  2. Right-click the DLL for which you want the public key, and then select Properties. The following table lists the name of the DLLs for each adapter and provider.

    Adapter/.NET Framework Data Provider

    Name of the DLL

    SAP adapter

    Microsoft.Adapters.SAP

    Siebel adapter

    Microsoft.Adapters.Siebel

    Oracle Database adapter

    Microsoft.Adapters.OracleDB

    Oracle E-Business adapter

    Microsoft.Adapters.OracleEBS

    SQL adapter

    Microsoft.Adapters.Sql.dll

    Data Provider for SAP

    Microsoft.Data.SAPClient

    Data Provider for Siebel

    Microsoft.Data.SiebelClient

  3. On the General tab, the value against the Public Key Token label specifies the public key for the DLL. Similarly, the value against the Version label specifies the version number for the DLL.

  4. Copy the public key, and then click Cancel.

Installing the Custom RFCs

You only need to perform this task if you want to use the Data Provider for SAP. For instructions on installing custom RFCs, see the "Installing Custom RFCs for the Data Provider for SAP" topic in the SAP adapter documentation. The document is typically installed at <installation drive>:\Program Files\Microsoft BizTalk Adapter Pack\Documents.

Important

If you are using an earlier version of the custom RFCs provided with the BizTalk Adapter Pack, you must upgrade them to the RFCs provided with this release. You must do so by removing the earlier RFCs and instead installing the RFCs shipped with this release.

Top of page

Installing the Enterprise Applications

For instructions on installing the enterprise applications, see the respective installation guides for enterprise applications. See the user documentation for each adapter for information about specific configuration changes, if any, required to be performed for each enterprise applications. The user documents for the adapters are installed along with the adapters, typically at <installation drive>:\Program Files\Microsoft BizTalk Adapter Pack\Documents.

Top of page

Installation and Post-Installation Checklist

Perform the following tasks related to installation and post-installation of the BizTalk Adapter Pack:

  • Make sure you installed all the software prerequisites with the right installation option. For more information, see Software Prerequisites.

  • Make sure you have the right version of the enterprise applications installed on your computer where you installed the BizTalk Adapter Pack. See Supported Enterprise Application Versions.

  • enterprise application you want to connect to, make sure you installed the BizTalk Adapter Pack with the Custom installation option. Make sure you have not installed the BizTalk Adapter Pack with the Complete installation option. See Installing the BizTalk Adapter Pack.

  • If you want to make tRFC calls to the SAP system using the SAP adapter, make sure you create the required tables in a SQL Server database. See After Installing the BizTalk Adapter Pack.

  • While running the setup wizard for the BizTalk Adapter Pack, if you get an error message informing that the setup failed to register the bindings, make sure you register them manually. See After Installing the BizTalk Adapter Pack.

  • If you chose to install the Data Provider for SAP as part of the BizTalk Adapter Pack installation, make sure you install the custom RFCs on the SAP system. See After Installing the BizTalk Adapter Pack.

Top of page

Modifying the BizTalk Adapter Pack Installation

Perform the following steps to modify the BizTalk Adapter Pack installation. Make sure you have the WCF LOB Adapter SDK installed before you run the setup wizard to modify the BizTalk Adapter Pack installation.

You can modify the BizTalk Adapter Pack installation in the following two ways:

  • In interactive mode: By running the setup wizard

  • In silent mode: By using the command line

To modify the BizTalk Adapter Pack installation in interactive mode

  1. Log on using an account that is a member of the BizTalk Server Administrators group.

  2. Click Start, and then click Control Panel.

  3. In Control Panel, double-click Programs and Features.

  4. In the Programs and Features dialog box, select Microsoft BizTalk Adapter Pack 2010, and then click Change/Remove.

  5. Read the information on the Welcome screen, and then click Next.

  6. In the Change, repair, or remove installation dialog box:

    • To select the components you want to install, click Change and proceed to Step 6.

    • To repair errors in the most recent installation, click Repair and proceed to Step 7.

    • To remove Microsoft BizTalk Adapter Pack from the computer, click Remove and then proceed to Step 10.

  7. If you chose to modify the installation:

    • Expand the Microsoft BizTalk Adapter Pack node to specify whether you want to install the base adapters or the .NET Framework Data Providers, or both.

    • Expand the Base Adapters node to specify whether you want to install all the adapters or specific adapters.

    • Expand the ADO Providers node to specify whether you want to install all the providers or specific providers.

    • Click Next.

    • Click Change, and then click Finish.

  8. If you chose to repair the installation, in the Ready to repair Microsoft BizTalk Adapter Pack dialog box, click Repair. The wizard starts repairing the installation.

  9. If required, change your preferences regarding opting for CEIP, and then click OK. For more information about CEIP, see http://go.microsoft.com/fwlink/?LinkID=144699.

  10. Click Finish.

  11. If you chose to remove the adapters, in the Ready to remove Microsoft BizTalk Adapter Pack dialog box, click Remove, and then click Finish.

To modify the BizTalk Adapter Pack installation in silent mode

  1. Open a command prompt, and navigate to the root directory of the BizTalk Adapter Pack installer.

  2. Run a command similar to the following:

    Note

    To modify the BizTalk Adapter Pack installation in a silent mode on an x64-based platform, in the following commands, replace AdaptersSetup.msi with AdaptersSetup64.msi.

    msiexec /i AdaptersSetup.msi /qn REMOVE=DbFeature ADDLOCAL=SapBaseAdapterFeature
    This command removes the Oracle Database adapter and installs the SAP adapter.

    By using different values for the REMOVE and ADDLOCAL properties, you can add or remove specific components. Refer to the table under the Installing the BizTalk Adapter Pack in Silent Mode section for information about the values that you can specify for the ADDLOCAL and REMOVE properties.

    You can also perform a silent repair by using the /f option as part of the msiexec command. For example:

    msiexec /i AdaptersSetup.msi /qn /f
    You can use various different combinations with the /f option. For more information about the msiexec command type msiexec on the command line and press ENTER or see http://go.microsoft.com/fwlink/?LinkID=103199.

    Important

    While modifying the BizTalk Adapter Pack installation in the silent mode, you cannot change your preferences for opting in or out of CEIP. The preferences will remain the same as you specified during the installation, even if you explicitly set the CEIP_OPTIN to true or false.

Top of page

Removing the BizTalk Adapter Pack

Important

If you created tables in the SQL Server database to work with the tRFC feature of the SAP adapter, you must manually remove them before removing the BizTalk Adapter Pack. The BizTalk Adapter Pack installation copies a SapAdapter-DbScript-Uninstall.sql file typically at <installation drive>:\Program Files\Microsoft BizTalk Adapter Pack. You must run this file to remove the tables you created.

Perform the following steps to remove the BizTalk Adapter Pack from your computer. Make sure you have the WCF LOB Adapter SDK installed before you run the setup wizard to remove the adapters.

You can remove the BizTalk Adapter Pack in the following two ways:

  • In interactive mode: By running the setup wizard

  • In silent mode: By using the command line

To remove the BizTalk Adapter Pack in interactive mode

  1. Click Start, and then click Control Panel.

  2. In Control Panel, double-click Programs and Features.

  3. In the Programs and Features dialog box, select Microsoft BizTalk Adapter Pack 2010, and then click Remove.

  4. In the Installer dialog box, click Yes.

To remove the BizTalk Adapter Pack in silent mode

  1. Open a command prompt, and navigate to the root directory of the BizTalk Adapter Pack installer.

  2. Run the following command:

    Note

    To remove the BizTalk Adapter Pack in silent mode on an x64-based platform, in the following commands, replace AdaptersSetup.msi with AdaptersSetup64.msi.

    msiexec /i AdaptersSetup.msi /qn REMOVE=DbFeature
    This command removes the Oracle Database adapter from the BizTalk Adapter Pack installation.

    By providing different values for the REMOVE property, you can remove specific components from the BizTalk Adapter Pack installation. Refer to the table in the Installing the BizTalk Adapter Pack in Silent Mode section for information about the values that you can specify for the REMOVE property.

    To completely remove the BizTalk Adapter Pack, execute the following command:

    msiexec /x AdaptersSetup.msi /qn
    For more information about the msiexec command type msiexec on the command line and press ENTER or see http://go.microsoft.com/fwlink/?LinkID=103199.

After Removing the BizTalk Adapter Pack

You might need to perform the following steps after removing the BizTalk Adapter Pack:

  • Remove the adapter bindings or the .NET Framework Data Provider registration, if the setup wizard failed to do so.

  • Remove the custom RFCs, if you chose to install the Data Provider for SAP.

Removing the Bindings or the .NET Framework Data Provider registration

Perform these steps only if the setup wizard fails to remove the adapter bindings or .NET Framework Data Provider registration from the machine.config file.

To remove the adapter bindings or .NET Framework Data Provider registration

  1. Navigate to the machine.config file on the computer. For example, on a 32-bit platform, the machine.config is available under <system drive>:\WINDOWS\Microsoft.NET\Framework\<version>\CONFIG.

    • For Microsoft .NET Framework 3.5 SP1, <version> is the version v2.0.50727 of the .NET Framework.

    • For Microsoft .NET Framework 4, <version> is the version v4.0.30319 of the .NET Framework.

  2. Open the file using a text editor.

  3. To remove the adapter binding registration:

    1. Search for the element "system.serviceModel" and remove the following from under the element:

      <client>
        <endpoint binding="sapBinding" contract="IMetadataExchange" name="sap" />
        <endpoint binding="siebelBinding" contract="IMetadataExchange" name="siebel" />
        <endpoint binding="oracleDBBinding" contract="IMetadataExchange" name="oracleDb" />
        <endpoint binding="OracleEBSBinding" contract="IMetadataExchange" name="oracleEBS" />
        <endpoint binding="sqlBinding" contract="IMetadataExchange" name="mssql" />
      </client>
      
    2. Search for the element "bindingElementExtensions" under system.serviceModel\extensions.

    3. Remove the following sections under the "bindingElementExtensions" node, depending on the available adapter binding. You must remove all the bindings if the setup wizard fails to remove any.

      For SAP adapter, remove:

      <add name="sapAdapter" type="Microsoft.Adapters.SAP.SAPAdapterExtensionElement,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Siebel adapter, remove:

      <add name="siebelAdapter" type="Microsoft.Adapters.Siebel.SiebelAdapterExtensionElement,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Oracle Database adapter, remove:

      <add name="oracleDBAdapter" type="Microsoft.Adapters.OracleDB.OracleDBAdapterExtensionElement,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Oracle E-Business adapter, remove:

      <add name="OracleEBSAdapter" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingElementExtensionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For SQL adapter, remove:

      <add name="sqlAdapter" type="Microsoft.Adapters.Sql.SqlAdapterBindingElementExtensionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    4. Search for the element "bindingExtensions" under system.serviceModel\extensions.

    5. Remove the following sections under the "bindingExtensions" node, depending on the available adapter binding. You must remove all the bindings if the setup wizard fails to remove any.

      For SAP adapter, remove:

      <add name="sapBinding" type="Microsoft.Adapters.SAP.SAPAdapterBindingSection,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Siebel adapter, remove:

      <add name="siebelBinding" type="Microsoft.Adapters.Siebel.SiebelAdapterBindingSection,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Oracle Database adapter, remove:

      <add name="oracleDBBinding" type="Microsoft.Adapters.OracleDB.OracleDBAdapterBindingSection,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For Oracle E-Business adapter, remove:

      <add name="OracleEBSBinding" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingCollectionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      For SQL adapter, remove:

      <add name="sqlBinding" type="Microsoft.Adapters.Sql.SqlAdapterBindingCollectionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    6. To remove the .NET Framework Data Provider registration:

      • Search for the element "DbProviderFactories" under the system.data node.

      • Look for the .NET Framework Data Providers that are still registered. Remove the following sections under the DbProviderFactories node, depending on the existing .NET Framework Data Providers. You must remove all the providers if they exist.

        For Data Provider for SAP, remove:

        <add name="SAPClient Data Provider" invariant="Microsoft.Data.SAPClient" 
            description=".NET Framework Data Provider for mySAP Business Suite"    type="Microsoft.Data.SAPClient.SAPClientFactory,Microsoft.Data.SAPClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Data Provider for Siebel, remove:

        <add name="SiebelClient Data Provider" invariant="Microsoft.Data.SiebelClient"
            description=".NET Framework Data Provider for Siebel eBusiness Applications"
            type="Microsoft.Data.SiebelClient.SiebelProviderFactory,Microsoft.Data.SiebelClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      • Save and close the machine.config file.

Removing the Custom RFCs

You must perform this step to remove the custom RFCs that you installed in the SAP system. For instructions on removing the custom RFC, see the "Installing Custom RFCs for the Data Provider for SAP" topic in the SAP adapter documentation. The document is installed along with the adapters, typically at <installation drive>: \Program Files\Microsoft BizTalk Adapter Pack\Documents.

Top of page

Upgrading from Previous Releases of the BizTalk Adapter Pack

Before upgrading the BizTalk Adapter Pack ensure:

  • You upgrade the WCF LOB Adapter SDK also. BizTalk Adapter Pack 2010 requires WCF LOB Adapter SDK 2010.

  • No applications that reference the adapter DLLs are running.

To upgrade BizTalk Adapter Pack

  1. Stop all applications that reference the adapter DLLs.

  2. Uninstall the older release of BizTalk Adapter Pack by clicking Start, and then clicking Control Panel > Programs and Features > Uninstall/Change.

  3. Install BizTalk Adapter Pack 2010.

    Important

    After you have upgraded the BizTalk Adapter Pack, the applications you created with the older version of the BizTalk Adapter Pack can be used with the upgraded version.

Top of page

Accessing the Adapter Pack Forum

You can use the Adapter Pack forum to discuss any issues you encounter with BizTalk Adapter Pack. The BizTalk Adapter Pack forum is available at http://go.microsoft.com/fwlink/?LinkId=87695.

Top of page