Configuring JDBC support in Siren Federate
To ingest data from the Avatica server you will need to enable support for JDBC datasources in at least one of the Elasticsearch nodes of your cluster.
It is recommended that you use a coordinator node for this purpose, however, if you are just evaluating the platform, you can use any node.
To enable JDBC support, add the following setting to the
elasticsearch.yml file and restart the node:
If you have enabled TLS support in your Avatica server, you must copy a Java keystore file that contains the Avatica server certificate to the Elasticsearch configuration directory. This is to ensure that it can be read by the Siren Federate client, which will verify the server certificate.
You can generate a truststore from a P12 file by following these steps:
Export the server certificate without its key from the P12 file with
openssl, for example:
openssl pkcs12 -in avatica.p12 -clcerts -nokeys -out ca.pem
Create a Java keystore with
keytool, taking a note of the password you choose to encrypt the file, for example:
keytool -import -file ca.pem -alias ca -keystore truststore.jks
truststore.jks file can then be copied to the configuration directory of the Elasticsearch node that has JDBC support enabled; the password of this file will be specified in the datasource configuration in Siren Investigate.
You can find more details about the available JDBC configuration options and recommendations in the Siren Federate documentation.
With Avatica server running and JDBC support enabled in Siren Federate, you can create a JDBC datasource in Siren Investigate.