1.2.0 (January 14, 2019)
To see the full changelog please use the following link.
Communication with SAP ECC (R3) established using SAP Java Connector (SAP JCo).
SAP Java Connector 3.0.19 SDK is being used.
||false||Log Level. Default value (
||false||Recommended value of allocated memory, MB||
Connection Type - Mandatory. type of connection. Options:
Application Server and
Message Server. Application Server (AS) provides programming interfaces to handle data (get, create, update, delete). The application server exposes two interfaces: ABAP and Java.
The SAP Message Server manages communication between the application servers, passes requests from one application server to another within the system and contains information about application server groups and the current load balancing within them. It uses this information to choose an appropriate server when a user logs on to the system.
SAP Message Service - Mandatory for connection type:
SAP System Number - Mandatory. System Number of SAP ECC (R/3, ERP) DB.
SAP Client Number- Client Number of SAP ECC (R/3, ERP). Client number may be different for different installations. But here is an example of clients available in one of the standard installation types (an extraction from SAP’s official documentation):
000- serves as standard delivery client (as usual in on-premise deployments)
100- is the primary demo client that contains the pre-configured scenarios and sample data.
200- can be used to experience the activation of SAP Best Practices on your own (see the SAP Best Practices implementation guide for details)
300- contains the activated Best Practices based on the White-list approach
400- contains the activated Best Practices based on the merged-client-000 approach
SAP Hostname - Mandatory. Domain or IP of SAP ECC (R/3, ERP) System.
SAP User Name - Mandatory. Username that used for SAP ECC (R/3, ERP) connection.
SAP Password - Mandatory. Password that used for SAP ECC (R/3, ERP) connection.
SAP Language- Language to operate in SAP ECC (R/3, ERP).
SAP ECC (R/3, ERP) component includes the following triggers:
SAP ECC (R/3, ERP) component includes the following actions:
RFC Servertrigger currently supports callback requests only. RFC server can not define the RFC call response. After receiving the request the server responses with an input BAPI structure.
RFC Servertrigger works for realtime flows only.
A component can be deployed to the platform starting from the version
3.19.0-rc.1. Sap Jco client library is not supported in the default version of the task docker image.
Steps to deploy the component:
docker build . --no-cache -t 10.25.0.54:31001/docker_dir/5d5a7ffa8cd40800110e37e3:test19
10.25.0.54- IP address one of platform nodes
docker_dir- the name of the docker directory
31001- port of docker registry
test19- tag of the docker image which you will use for new component version
docker push 10.25.0.54:31001/docker_dir/5d5a7ffa8cd40800110e37e3:test19
repobuildswhich connected with your last
git pushand update version of docker image to
"dockerImage" : "docker_dir/5d5a7ffa8cd40800110e37e3:test20",