Skip to content

Latest commit

 

History

History
51 lines (28 loc) · 2.78 KB

sap-java-connector-3cee866.md

File metadata and controls

51 lines (28 loc) · 2.78 KB

SAP Java Connector

The SAP Java buildpack provides an option to use the SAP Java Connector.

The SAP Java buildpack provides an option to use the SAP Java Connector (SAP JCo).

To activate SAP JCo in the SAP Java buildpack, set the environment variable USE_JCO to true.

Sample Code:

manifest.yml

---
applications:
- name: <app_name>
  ...
  env:
    USE_JCO: true

The previous method of activating the SAP JCo feature, by defining a service instance for both the connectivity and destination services in the manifest.yml file, has been deprecated and stops working at the end of a transition phase.

The activation of SAP JCo will provide all relevant libraries in the application container, so the Java Connector API ↗️ can be used. To use SAP JCo during runtime, a destination and an XSUAA service instance are mandatory. Additionally, if you want to set up on-premise connectivity, a connectivity service instance is required.

SAP JCo is only available for the Tomcat-based application containers that are included in the SAP Java Buildpack. Spring Boot applications only work with SAP JCo if you're using WAR deployment.

Related Information

Invoking ABAP Function Modules via RFC (Neo) ↗️

Invoking ABAP Function Modules via RFC ↗️

Invoke ABAP Function Modules in On-Premise ABAP Systems ↗️

About JCo ↗️