Connector issues when moving BPMN from SaaS to onprem env

Camunda 8 Topics Discussion & Questions
1

Hi … there are 2 issues when I moved the BPMN from SaaS to on-prem , actually my local environment. They are all related to the connector shape.

I have a rest connector shape in the BPMN diagram running fine in the Camunda SaaS. But when I download and try to deploy to my local environment ( docker compose setup) using desktop modeler (version 5.0.0), there are 2 issues.

Issue 1: connector attribute does not show in the desktop modeler. I believe this is due to the REST Connector (No Auth) template is not in place as I see the red error “not found” in template attribute. But not sure how to get it.

Issue 2: Anyway, I published to the local camunda environment ( the latest using docker compose). It stopped at the connector shape. It seems that the connector task is treated as a external task. But on SaaS, the engine makes the rest call and continued. Not sure if it is expected behavior?

Does it mean connector will NOT be supported on the on-prem install ? It is kind of time saver for the prototyping.

Thanks,

Walter

2

Hey @emailtowalter!
So far the connectors are not supported in the Camunda 8 SaaS version.
You would need to write your own REST service task to get this done right now.

Maybe our product management knows more about the path forward for this whole topic. :thinking:
Tagging @aleksander-dytko and @PreetiNirwal.

3

@Hafflgav I guess you meant to say that connector is not supported in on-prem version. That is my problem. I can see it may be a bigger challenge if it is not on the on-prem version. Most of systems are internal use. For external task pattern, it is easy. Our API can reach the internet. The reverse could be a problem for connector pattern — For SaaS to reach out our internal API, we will have to punch a hole for the network to make our API reachable to the Camunda SaaS. More security hurdle.

4

Hi @emailtowalter

In on-prem, at the moment you have to run a job worker to execute the rest call.

You can clone this repository and start the spring boot application or use the docker image as described in the README.md: GitHub - camunda-community-hub/zeebe-http-worker: Zeebe worker for HTTP calls.

This will be changing as more connector functionality comes to on-prem in the near-term future, but for now, this is the Way.

For SaaS, you will soon be able to write your own connector templates. The job workers for these connectors can run in your own network, so punching through the firewall will not be an issue.

Josh

2 Likes