This topic was last updated on: June 05, 2009
The following are some frequently asked questions (FAQs) related to Microsoft BizTalk Adapter for mySAP Business Suite.
What are the supported SAP server versions?
The SAP adapter can be used to connect to the following versions of the SAP servers:
- SAP R/3 4.6c Non-Unicode
- SAP R/3 4.7 Non-Unicode
- SAP R/3 4.7 Unicode
- SAP ECC 5.0 Non-Unicode
- SAP ECC 5.0 Unicode
- SAP ECC 6.0 Non-Unicode
- SAP ECC 6.0 Unicode
What are the supported SAP client versions?
The SAP adapter supports the following SAP client versions:
- SAP RFC SDK 6.4 UNICODE
- SAP RFC SDK 7.0 UNICODE
- SAP RFC SDK 7.1 UNICODE
.gif) Note |
|---|
| The SAP adapter requires Unicode version of the RFC SDK irrespective of whether the SAP Server is Unicode or non-Unicode. |
What client libraries must be present on the system where the SAP adapter is installed?
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 and copy them to the relevant location mentioned just preceding this table.
- DLLs 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 will be using 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 copy them to the relevant location mentioned just preceding this table.
- DLLs 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 will be using 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 and copy them to the relevant location mentioned just preceding this table.
- DLLs 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. These are available from the following links:
- If you will be using 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.
What are the supported BizTalk versions for the BizTalk Adapter Pack?
The BizTalk Adapter Pack is supported with Microsoft BizTalk Server 2006 R2 and BizTalk Server 2009.
In which user context should the setup be run?
You must always run the BizTalk Adapter Pack setup wizard under a user context with administrative privileges on the computer.
Does the Microsoft BizTalk Adapter Pack support tracing?
Microsoft BizTalk Adapter Pack enables adapter clients to activate Windows Communication Foundation (WCF) tracing and adapter-specific tracing. For more information about tracing, see Diagnostic Tracing and Message Logging.
Where are the trace files stored?
The trace files are stored at a location that the adapter clients specify. The adapter clients can specify this location while enabling tracing. For more information about tracing, see Diagnostic Tracing and Message Logging.
How do I view the traces?
You can use the WCF Service Trace Viewer tool to view the traces. For more information about the tool, see http://go.microsoft.com/fwlink/?LinkId=91243.
Are performance counters available for the adapters?
The BizTalk Adapter Pack provides a "LOB Time (Cumulative)" performance counter to measure the time, in milliseconds, that the LOB client library takes to complete an action initiated by the adapter. For more information about performance counters see Using Performance Counters.
How do I enable performance counters for adapters?
You can enable or disable the performance counters by setting the binding property EnablePerformanceCounters. Set EnablePerformanceCounters binding property to True to enable performance counters. To disable performance counters, set EnablePerformanceCounters to False. By default, EnablePerformanceCounters is set to False.
Other Resources
Getting Started