Use connector for multiple processes

[dmitryi.vasiliev20]

I have the following problem:
A connector for Camunda has been written, and it is used in two different processes. These processes are served by two different services(spring boot). When the process served by the first service reaches the connector, it can be handled by the second service, which is responsible for the other process.

I want to write a outbound connector and use it in multiple processes by connecting a dependency to a project.

Example:

@Component
@OutboundConnector(
    name = "KAFKA_OUTBOUND_CONNECTOR",
    inputVariables = {"status", "stage"},
    type = "status-camunda-connector:1"
)
public class KafkaOutboundConnector implements OutboundConnectorFunction {}

[ev.bilske]

Hi @dmitryi.vasiliev20 , thanks for your question. I’m happy to help!

I don’t quite understand your question. May you please rephrase or provide more context?

Thanks

[dmitryi.vasiliev20]

@ev.bilske

I don’t quite understand your question. May you please rephrase or provide more context?

Yeah, I’ll try.

I have two Spring Boot applications (processes) and a Camunda connector.
App1 → process1 (deployed)
App2 → process2 (deployed)

The connector is used in both applications with the same type. When process1 starts and reaches the connector step, app2 processes this request instead of app1.

How can I correctly build this link? Do I need a separate application for processing connectors, or not?
Example of setting up a connector:
<zeebe:taskDefinition type="status-camunda-connector:1" />

[ev.bilske]

Thanks for rephrasing!

It sounds like you need to use two different Connector types - a different type for each process.

You can see this doc for how you can override the type in one of the applications.

I hope that helps!

[dmitryi.vasiliev20]

I want to use custom connectors for my processes. Do I need to deploy the connector as a standalone service? Is this the right decision?

[chillleader]

That’s correct: to execute custom connectors, you need to host the connector runtime bundled with your custom connectors. We recommend running it as a standalone application.

You can either use our supported Docker images and simply add your connectors to the classpath (doc), or build it with Maven similarly to how it’s done in the connectors repository (example).

Feel free to reach out if you encounter any issues!