During a recent project I was using the BizTalk SAP Adapter to interact with a custom BAPI that was exposed as an RFC. In order to get the Add Adapter Service Wizard in BizTalk to work properly, I had to install all of the SAP dependency libraries on the BizTalk server. I was amazed at how complicated this whole process was. There are a couple things I would like to do in this blog post:
- Give the names of all of the files that must be used for 32-bit and 64-bit installs of the SAP dependencies for the 6.4 version of the SAP RFC SDK.
- Provide a shell script for copying all of the SAP dependencies for 32-bit and 64-bit installs of the SAP dependencies
- Provide some additional details on the SAP Adapter installation.
The reasons I am posting on this is because I think the InstallGuide.htm which is included with the BizTalk Adapter Pack is a little vague. The file is already very long and inclusive but some important details like the names of many of the SAP client files is not included. Below is an expanded list of directions for the 6.4 version of the SAP client dependency installation:
| SAP client version
| Required drivers
|
|
6.4 32-bit
|
- librfc32u.dll (SAP RFC SDK 6.40 UNICODE). This is available as part of SNOTE* 413708. The instructions to download this are available at http://go.microsoft.com/fwlink/?LinkID=94691.
[BC Comment] Copy to C:WindowsSystem32
- DLLs available from SAP as part of the package, UCLIB.SAR. See SNOTE* 785368 (http://go.microsoft.com/fwlink/?LinkID=94692) for more information. This package is available as part of SAP KERNEL 6.40, which is available from the SAP Service Marketplace. While downloading the SAP Kernel, make sure you download the “database independent” version.
[BC comment] So the following DLLs will need to be copied to c:WindowsSystem32:
- icudt26l.dll
- icudt30l.dll
- icuin26.dll
- icuin30.dll
- icuuc26.dll
- icuuc30.dll
- 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.
[BC comment] So the following DLLs will need to be copied to c:WindowsSystem32:
- mfc71.dll
- mfc71u.dll
- msvcp71.dll
- msvcr71.dll
- 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:
- Copy to C:WindowsSystem32: gsskrb5.dll, gssntlm.dll
- [BC Comment] To create a simple deployment package for all of the DLLs, copy all of the DLLs from the above steps to a separate folder. Then use the following script to install all of these into the correct place. I found using a script was a lot easier for administrators and vastly simplified the overall process. Here is the script (rename to .bat after downloading): InstallSAPDLLs32-bit.txt
|
| ———-
| ————————————————————————————-
|
|
6.4 64-bit
|
- librfc32u.dll 64-bit (SAP RFC SDK 6.40 UNICODE). This is available as part of SNOTE* 413708. The instructions to download this are available at http://go.microsoft.com/fwlink/?LinkID=94691.
[BC Comment] Copy to C:WindowsSystem32
- librfc32u.dll 32-bit (SAP RFC SDK 6.40 UNICODE). This is available as part of SNOTE* 413708. The instructions to download this are available at http://go.microsoft.com/fwlink/?LinkID=94691.
[BC Comment] Copy to C:WindowsSysWow64
- DLLs available from SAP as part of the package, UCLIB.SAR. See SNOTE* 785368 (http://go.microsoft.com/fwlink/?LinkID=94692) for more information. This package is available as part of SAP KERNEL 6.40, which is available from the SAP Service Marketplace. While downloading the SAP Kernel, make sure you download the “database independent” version.
[BC comment] So the following 32-bit DLLs will need to be copied to c:WindowsSysWow64:
- icudt26l.dll
- icudt30l.dll
- icuin26.dll
- icuin30.dll
- icuuc26.dll
- icuuc30.dll
Very similar 64-bit DLLs will need to be copied to C:WindowsSystem32:
- icudt26l.dll
- icudt30l.dll
- icuin26.dll
- icuin30.dll
- icuuc26.dll
- icuuc30.dll
- 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.
[BC comment] So the following DLLs will need to be copied to c:WindowsSystem32:
- mfc71.dll
- mfc71u.dll
- msvcp71.dll
- msvcr71.dll
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 copy to C:WindowsSysWow64: gsskrb5.dll, gssntlm.dll
- For 64-bit copy to c:WindowsSystem32: gx64krb5.dll, gx64ntlm.dll
[BC Comment] To create a simple to use install script for 64-bit it is a little more complicated because the names are the same for many of the DLLs for 32-bit and 64-bit versions. Make a folder to hold the files and then make sub folders for UCLIB-32, UCLIB-64, RFC-32, and RFC-64. Copy all of the 32-bit UCLib files to UCLib-32 and similarly for UCLIB-64, RFC-32, and RFC-64.
Then use the following script in the root folder of the install files to install all of these into the correct place. I found using a script was a lot easier for administrators and vastly simplified the overall process. Here is the script (rename to .bat after downloading): InstallSAPDLLs64-bit.txt
|
I wonder if the reason Microsoft is not able to provide a redistributable of these SAP components is due to SAP licensing restrictions. In any case, these directions will help you simplify the complexity of the SAP adapter dependencies’ install and dramatically improve the install experience after you get all of the files downloaded.
Thanks,
Like this:
Like Loading...
Related
MS Innovations Blog 
BTW, this is the install of the WCF-SAP adapter, part of the BizTalk adapter pack v2
Hi Ben,
Do you know if these DLLs will work for BizTalk Adapter pack 2010 too?
We have a 64bit server running IIS7.
Thanks,
Robert
Robert,
With BizTalk 2010, there is an updated BizTalk adapter Pack. The adapter pack is now distributed on the same install media as BizTalk server.
I am not sure how much has changed for the SAP install
Thanks,