I am currently using Self-Managed Camunda on Docker on my laptop and I have a MS SQL database and a PostgreSQL database in a separated VM.
To access the both databases I am using the self-managed connectors like with this configuration:
Hi @kamilleB - the Postgres and MSSQL Connectors are contributed to the community by Infosys. From the Operate logs, it looks like the Connector is being invoked, which means the issue is likely with the Connectors themselves. Unfortunately, a quick look at the GitHub repository for those Connectors seems to confirm this:
So, what can you do, since itâs an issue with a third-party package rather than Camunda itself?
You can open another issue in the GitHub repository and/or comment on the issue linked above and wait for the maintainer to fix the issue.
Well thatâs unfortunate⌠I just wanted to create a quick demo of self-managed version of Camunda with a simple database and I finally may have to fix a connector provided by a partner in Camunda marketplaceâŚ
Is Camunda can check whatâs inside marketplace and can remove connectors if they are not working? It would help others to not get struggled like me.
Hi @kamilleB - Iâm sorry to hear you had issues, that sounds frustrating. Thank you for posting about it here.
For your initial issue: you could try the new Camunda-supported JDBC Connector as an alternative. We plan to formally release it as part of the 8.6.0-alpha2 release next month.
Thanks for your Marketplace feedback. Iâll bring it to the Connectors team to discuss further.
@kamilleB - we do have a certification program for Connectors in the Marketplace! Itâs intended to help avoid this exact kind of confusion. It is very new (as is the Marketplace), so developers/partners are still working on their certifications.
@kamilleB indeed, the documentation has not been published yet. That will happen closer to the formal release next month.
In the âdataâ variable (that contains the SQL query), try using this syntax: INSERT INTO dbo.Customers (id, name) VALUES (1, 'value-1'),(2,'value-2')
@kamilleB (and others who stumble on this thread) - Just to add a bit more context to understand whatâs happening, the Connectors require two pieces to work: the element template, and the Connector itself running with the Connector Runtime. If you are using the 8.5 Docker images, the Connectors Runtime image does not contain the JDBC Connector; you would either need to add it manually (by including the JAR in the classpath in the container, or by manually adding and configuring it within the container), or use the 8.6.0-alpha2 images. Hope that helps the situation make a little more sense!
Hey, @kamilleB, Did you run the connector yet? Example on Linux run the connector with this command. java -cp 'spring-zeebe-connector-runtime-8.1.17-with-dependencies.jar:connector-mysql-0.1.0-SNAPSHOT-with-dependencies.jar' io.camunda.connector.runtime.ConnectorRuntimeApplication
I tried with dbo, without dbo in the SQL query, I tried multiple ports, I changed the SQL queries, the process doesnât care and wait for long time. I donât understand why the task doesnât raise at least one error message to help debugâŚ
@kamilleB it looks like a connection issue to me, you should have a timeout at some point though.
But I think the host is incorrect, youâre running the Connectors runtime inside a Container so if your docker compose file looks like this (or similar):