Multi Tenancy: Schema usage in Camunda BPM Run

Hi Team,

I am trying to implement multi-tenancy by following the link “https://github.com/camunda/camunda-bpm-examples/tree/master/multi-tenancy/schema-isolation”. This link deals with using WildFly Distro. I am slightly confused at the section " Configuring Process Engines"
I am using a Standalone Camunda BPM Run, where I only update the bpmns and application.yml (default.yml) files for deployment.

How can I map the schema here? How can I implement (Configuring of Process Engines) in default.yml file ?
Could you share some pointers on this.

Team,
Appreciate if you could share some insights on this issue.

Thanks…

Hi @Saju_John_Sebastian1,

Camunda Spring Boot and Camunda Run are build to run only a single process engine, configured with the spring boot mechanisms.

If you want to set up multi tenancy with multiple databases, you have to start several Camunda Run installations, one for each database schema.

Hope this helps, Ingo

Thanks for the input @Ingo_Richtsmeier .
Regarding “you have to start several Camunda Run installations, one for each database schema.”
Could you share an example on usage of DB schema where we can configure the DB schema using default.yml file (for Camunda Run)

Hi @Saju_John_Sebastian1,

I don’t have an example by hand, but from my little DB2 experience it ended up in a jdbc URL containing the schema name.

This jdbc URL has to be used in the default.yml.

Hope this helps, Ingo