SAP note 0000684106

wM 10.7
SAP Adapter

image

Does anyone has the actual note?

image

Why does SAG includes a link to another company in it’s own documentation?

Hi Luis,

when placed at the right locations there should be no need to register any Microsoft libs.
I prefer running IS an Application using manual start from Windows StartMenu to save performance when the instances are not needed.

The SAP Shared libs (either DLL for Windows or SL/SO for Unix/Linux) from JCo 3.1 should be placed under IntegrationServer/instances/default/lib, the jars (sapjco3.jar and sapidoc3.jar; they are the same for Windows and Unix/Linux) go to IntegrationServer/instances/default/packages/WmSAP/code/jars/static.
Remember to shutdown and restart the IS afterwards.
A simple restart of IS would not load the native lib parts.
These will only load when IS started from scratch.

SAG adds the link to the SAP notes to point the customers to the latest version of these SAP notes instead of having to update their own documentation every time the SAP notes will change.

Regards,
Holger

Addendum:
Remember to apply latest fixes for wM SAP Adapter 10.1 to avoid issues with incompatibilities between SAG SAP Adapter Fixes and the different JCo 3.1.x builds.

Regards,
Holger

Thanks Holger.

Actually I have those files in the correct locations. I followed the installation guide until I reach this part of the SAP note which is nowhere to find in the internet! I think this note is a static content, so it would make sense to include it in the documentation it self rathen than mention a number. Not a good policy in my view…and believe me I used to praise to the skies SAG documentation.

image

The only thing I am missing are the fixes and this dll registry.

Regarding run as service, it needs to be this way so it can start with machine restarts and as there are user restrictions.

Hi Luis,

I have just checked the SAP Support Portal and it looks like the SAP note 0000684106 does no longer exist in their database due to outdated content.

Please check the following SAP-Note instead (you require a login to SAP Marketplace and/or Support Portal):
2786882

In this case SAG should update the documentation for the SAP Adapter to point to the current version of the proper SAP notes.

Remember that these SAP specific documents are only available to registered SAP customers with valid login.

As we are not running our systems on Windows in production we never used Windows services here.
We have only Designer running locally on Windows for development purposes, everything else is running on Unix.
And for local development it is sufficient to start the instances manually when you need them.

Regards,
Holger

Yeah, I don’t have it (the account)… Will need to open a ticket with SAG, I’ll try to remember update thread once sorted.

Thanks!

Hi Luis,

how did you receive the JCo files then without having an account with SAP?
If you received them from your SAP Environment, get in contact with this team and ask them to retrieve the SAP note for you.

Regards,
Holger

If you are running Integration Server as a service, run register dll command to start Adapter
for SAP. For information on installing Microsoft DLLs, see SAP note 0000684106.

From SAP Note 2786882 it says:

On Windows platforms, JCo 3.1 requires the Visual Studio 2013 C/C++ runtime libraries to be installed on the system. If not present, download and install the “Visual C++ 2013 Redistributable Package” from the Microsoft knowledge base article Update for Visual C++ 2013 Redistributable Package - Microsoft Support and choose the package, which corresponds to the used Locale and JVM bit-width (x64 for 64-bit or x86 for 32-bit).

After this we need to copy the files bellow to %WinDir%
System32

msvcr120.dll

949 KB

12.0.40664.0

msvcp120.dll

445 KB

12.0.40664.0

vcamp120.dll

332 KB

12.0.40664.0

vcomp120.dll

118 KB

12.0.40664.0

vccorlib120.dll

243 KB

12.0.40664.0

mfc120.dll

4,322 KB

12.0.40664.0

mfc120u.dll

4,347 KB

12.0.40664.0

mfc120chs.dll

46 KB

12.0.40664.0

mfc120cht.dll

46 KB

12.0.40664.0

mfc120deu.dll

74 KB

12.0.40664.0

mfc120enu.dll

64 KB

12.0.40664.0

mfc120esn.dll

73 KB

12.0.40664.0

mfc120fra.dll

74 KB

12.0.40664.0

mfc120ita.dll

72 KB

12.0.40664.0

mfc120jpn.dll

53 KB

12.0.40664.0

mfc120kor.dll

53 KB

12.0.40664.0

mfc120rus.dll

70 KB

12.0.40664.0

Important in the machine I was working the vcredist_x64.exe was not working, as it has an invalid certificate. Hence the procedure on previous step.

  • Finally restart the full server machine.

Had JCos from other installation.