Carsten Erker

Salut Christophe, all JCo-Properties starting with jco.* are simply passed on to JCo, so you should be able to configure it as if you were using plain JCo. If you try this, it would be helpful if you could give a feedback here, since I am currently not able to test with a message server.

Salut Christophe, all JCo-Properties starting with jco.* are simply passed on to JCo, so should be able to configure it as if you were using plain JCo. If you try this, it would be helpful if you could give a feedback here, since I am currently not able to test with a message server.

Hello Christophe, Hibersap only implements the other way, calling SAP from Java applications. I think you have to use plain JCo for your use case.

Are you building with Maven/Gradle or are you managing your dependencies manually in Eclipse? In the first case Maven/Gradle should add the dependencies needed by Hibersap automatically to your build. In the latter case I would recommend switching to a real build system to avoid having to manage things manually. Which means you would have to look into the Hibersap poms and add dependencies (like apache-commons logging) to Eclipse and make Eclipse package them into the war you are deploying on Tomcat....

Home

Hi Chris, you can install the SAP-JCo library like described in the Hibersap documentation: http://hibersap.org/documentation/reference/#the-sap-java-connector-jco Alternatively, you can deploy it with the mentioned groupId/artifactId/version to an enterprise Maven repo like Nexus or Artifactory. And then declare the Gradle dependency with the coordinates org.hibersap:com.sap.conn.jco.sapjco3:3.0.15 in compile scope. Of course you can use a different version and also a different groupId if you l...

Showing "waiting to connect" indefinitely

The above outlined solution with a system dependency is far from being ideal and...