FAQs for Library Upgrade of SAP Snap Pack

What is happening?

We have upgraded the following libraries for the SAP Snap Pack:

  • JCo from 3.1.4 to 3.1.10

  • IDoc from 3.1.1 to 3.1.3.

The SAP Snap Pack depends on a native library. The available versions of this library are:

  • Linux:  libsapjco3.so md5sum: 8c37756820516807e2edff3ff332fdc1).

  • Mac: libsapjco3.dylib md5sum: e3c360818d9f640d875d2f18725131fd)

  • Windows:  sapjco3.dll md5sum: 188977c0315ec2d76c0ed74159c81f35)

Optional. You can verify the integrity of the file using md5sum (Linux).

Where can I get the updated native library?

You can download the shared library (Windows -sapjco3.dll) (Linux -libsapjco3.so)from the SAP portal.

Why did we upgrade the library for the SAP Snap Pack?

To improve security, performance, stability, and reliability.

What is the timeline for this upgrade?

This library upgrade is part of the August GA release (Stable) 438main27765 Snap Pack version for SAP.

Will my Org be impacted?

Yes, your Org will be impacted if the SAP Snap Pack uses the old SAP native library. The impact might be minimal if you use v3.1.10 or a higher version.

Do I need to reconfigure my Account or Snap settings?

No, you do not have to reconfigure both your Account settings or Snap settings; the account can remain as-is to work with the latest native library.

Do I need to update for Cloudplex or Groundplex deployments or Docker deployments?

All Cloudplexes are Linux-based (.rpm). If a Cloudplex is IAC-enabled, the native library will be installed as part of the upgrade. Similarly, Snaplex docker images will also contain the updated SAP JCo native library. However, non-IAC Cloudplexes and Groundplexes must be updated manually, and only the JCC nodes that use the SAP Snap pack need to be upgraded.

The path delimiters are important. For Linux, it is the forward slash (/). For Windows, the path delimiter is the backslash (\).

For specific steps on implementing the library upgrade, refer to this article.

Â