cancel
Showing results for 
Search instead for 
Did you mean: 

Error installing Sap Could Connector on MAC M1

Domingos81
Explorer
1,125

Hi Experts,

I downloaded the sapcc-2.15.0-macosx-x64.tar.gz file from the site, unzipped it using the -xzof sapcc-2.15.0-macosx-x64.tar.gz command and when running the script I had the following error:

Generating initial key store for Administration UI

Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /Users/domingosfernandes/Projects/Connector/./lib/native/libsapscc20jni.dylib

at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2393)

at java.base/java.lang.Runtime.load0(Runtime.java:755)

at java.base/java.lang.System.load(System.java:1953)

at com.sap.scc.jni.NativeLibrariesInitializer.initialize(NativeLibrariesInitializer.java:36)

at com.sap.scc.jni.SecStoreAccess.main(SecStoreAccess.java:222)

erro de keytool: java.lang.Exception: A senha da área de armazenamento de chaves deve ter, no mínimo, 6 caracteres

java.lang.Exception: A senha da área de armazenamento de chaves deve ter, no mínimo, 6 caracteres

at java.base/sun.security.tools.keytool.Main.doCommands(Main.java:1020)

at java.base/sun.security.tools.keytool.Main.run(Main.java:415)

at java.base/sun.security.tools.keytool.Main.main(Main.java:408)

Was not able to create the keystore properly

If anyone has had this problem and can share the solution I would appreciate it.

Tks,

Domingos Fernandes

View Entire Topic
ingo_neumann2
Employee
Employee

Hi Domingos,

the problem you are facing is caused by the fact that the SCC has bundled native OS libraries, that are not compatible with aarch64 (M1 architecture). Even if you try to run the SCC from a terminal in Rosetta, you are facing the issue. This is because you are most likely using a Java JDK that is compiled for aarch64 and not x64.

The overcome the issue, please download the Sapmachine JDK 17 for macOS (x64 architecture) - NOT the Installer - from https://sap.github.io/SapMachine/

Extract the .tar.gz file at a place of your choice.

In the location of your extracted SCC, insert the two following lines after the CATALINA_HOME=`pwd` line in the go.sh file to use the x64 Java version (there are other ways how to set the Java version, but this one is less destructive to your system).

#!/bin/bash

CATALINA_HOME=`pwd`
JAVA_HOME="<path to your x64 Sapmachine>/sapmachine-jdk-17.0.5.jdk/Contents/Home"
export PATH="$JAVA_HOME/bin:"$PATH

Now, execute go.sh from a Terminal that is running in Rosetta.

Upon first execution, you will receive some popups saying that the developer of "libsapscc20jni.dylib" cannot be verified. Allow the execution of the library in the macOS Privacy & Security settings. Run the go.sh file again afterwards.

You might have already a corrupt Java Keystore from your first attempts. In case it is not working after you have performed the above steps and you are seeing indications in the SCC logs that are related to a problem with the Java Keystore, try again with a freshly extracted version of the SCC.

Hope this helps!
- Ingo

declanmoore
Advisor
Advisor
0 Kudos

Just chiming in to add that I was running into the same issues on my M1 macbook with SCC installation and I followed your instructions and they have worked.

Thank you!