Confluent Platform
Synopsis
This section shows how to launch the ODP Source Connector on a Confluent Platform running locally within a docker environment.
Preliminary Setup
- Install Docker Engine and Docker Compose on the machine where you plan to run the Confluent Platform.
- If you’re using a Mac or Windows, Docker Desktop includes both.
- Download and launch a ready-to-go Confluent Platform Docker image as described in Confluent Platform Quickstart Guide.
- Make sure that the machine running the Confluent Platform is connected to the SAP® source.
- Make sure you have a licensed version of the SAP® Java Connector 3.1 SDK before proceeding.
Connector Installation
The connector can be installed either manually or through the Confluent Hub Client.
In both scenarios, it is beneficial to use a volume to easily transfer the connector file into the Kafka Connect service container. If running Docker on a Windows machine, make sure to add a new system variable COMPOSE_CONVERT_WINDOWS_PATHS
and set it to 1
.
Manual Installation
To install the ODP Source Connector, follow these steps:
- Unzip the downloaded file,
init-kafka-connect-odp-x.x.x.zip
. - Get a copy of SAP® Java Connector v3.1.11 SDK and move it to the
lib/
folder inside the unzipped connector folder. SAP® JCo consists ofsapjco3.jar
, and the native libraries likesapjco3.dll
for Windows OS orsapjco3.so
for Unix. For instance include the native libsapjco3.so
next to thesapjco3.jar
. - Move the unzipped connector folder into the configured
CONNECT_PLUGIN_PATH
of the Kafka Connect service. -
Within the directory where the
docker-compose.yml
of the Confluent Platform is located you can start the Confluent Platform using Docker Compose.docker-compose up -d
Confluent CLI
Install the zipped connector init-kafka-connect-odp-x.x.x.zip
using the Confluent Hub Client from outside the Kafka Connect docker container:
confluent connect plugin install {PATH_TO_ZIPPED_CONNECTOR}/init-kafka-connect-odp-x.x.x.zip
Further information on the Confluent CLI can be found in the Confluent CLI Command Reference.
Connector Configuration
The connector can be configured and launched using the control-center service of the Confluent Platform.
- In the control-center (default: localhost:9091) select a Connect Cluster in the Connect tab.
Choose a Connect Cluster. - Click the “Add connector” button and select the ODPSourceConnector.
Add a connector. - Enter a unique name for the connector instance and provide any other required configuration.
For the ODP Source Connector to extract data from a SAP® source, you need to follow these steps:
-
Transfer the properties including a minimal configuration to the Confluent Control Center user interface. Remember to add in your license key.
name = odp-source-connector connector.class = org.init.ohja.kafka.connect.odp.source.ODPSourceConnector tasks.max = 1 sap.odp.license.key = "Your license key here" sap.odp.subscriber-name = OhJaODPKafkaConnector sap.odp#00.name = Test sap.odp#00.context = SAPI sap.odp#00.topic = ODPSAPITEST jco.client.ashost = 127.0.0.1 jco.client.sysnr = 20 jco.client.client = 100 jco.client.user = user jco.client.passwd = password
- Launch the source connector.
Starting a Connector via REST Call
-
Save the example configuration JSON file into a local directory, e.g. named as
source.odp.json
. Remember to add in your license key.{ "name": "odp-source-connector", "config": { "connector.class": "org.init.ohja.kafka.connect.odp.source.ODPSourceConnector", "tasks.max": "1", "sap.odp.license.key": "Your license key here", "sap.odp.subscriber-name": "OhJaODPKafkaConnector", "sap.odp#00.name": "Test", "sap.odp#00.context": "SAPI", "sap.odp#00.topic": "ODPSAPITEST", "jco.client.ashost": "127.0.0.1", "jco.client.sysnr": "20", "jco.client.client": "100", "jco.client.user": "user", "jco.client.passwd": "password" } }
-
Once the configuration JSON is prepared, you can start the connector by sending it via a REST call to the Kafka Connect REST API. Use the following command to send a POST request:
curl -X POST http://localhost:8083/connectors \ -H "Content-Type:application/json" \ -H "Accept:application/json" \ -d @source.odp.json
-
Once the connector is started successfully, the Kafka Connect REST API will return a response in JSON format with details about the connector, including its status and any potential errors. You can verify that the connector is running by checking its status:
curl -X GET http://localhost:8083/connectors/odp-source-connector/status
This will return a JSON object indicating whether the connector is running, its tasks, and any associated errors.
- Entering user credentials: To prevent from SAP® user lockout during the connector configuration process, it is recommended to enter the
jco.client.user
andjco.client.passwd
properties in theJCo Destination
configuration block with caution since the control-center validates the configuration with every user input which includes trying to establish a connection to the SAP® system. - Get recommended values automatically: If you enter the properties in the
JCo Destination
configuration block first, value recommendations for some other properties will be loaded directly from the SAP® source system. - Display advanced JCo configuration properties: You can display the advanced JCo configuration properties in the Confluent Control Center UI by setting the configuration property
Display advanced properties
to1
. - Configure multiple
ODP Sources
: Since you can push data to multipleODP Sources
in one connector instance, an additionalODP Source
configuration block will appear once you provided the required information for the firstODP Source
configuration block. - Selection limits in Confluent Control Center UI: There’s a limit to the number of
ODP Sources
that can be configured in the Confluent Control Center UI for one connector instance. If you need to configure additional sources beyond this limit, you can do so in the UI without any recommendations by using the Additional Properties section. The same applies to the number of selection conditions in full initialization mode.