Integrate with SAP

This article contains a brief description of the changes in working with SAP libraries since v4.5.10

IDE

From the IDE perspective, everything remains almost the same.
If the user tries to create a new SDK project for the first time with SAP as backend, the IDE will ask the user to specify where we can find the *.jar and native library (*.dll, *.so, *.jnilib) to update *.ini file of IDE to update it’s classpath (to allow the Import BAPI functionality).

The difference is we no longer install the SAP libraries into the Maven local repository (~/.m2).
Instead, we copy the SAP libraries into the ~/.openlegacy/sap-libs directory, and each SDK project (SAP based) will refer to library in this directory.

Running as an Executable Jar

Users no longer need to copy any SAP-related files into the root of the API project. Everything will be picked up automatically from ~/.openlegacy/sap-libs.
All other steps remain the same.

Side Note

During any Maven command from command prompt, users can specify a custom directory, where we can find SAP libraries. To do that, users must use -Dsap.jco.dir option.
For example: