Camuna license key is not deployed in DB

Need help to automatically deploy camunda-license key.
I am using camunda spring boot starter.
I am not using @EnableProcessApplication in my spring boot application as @SpringBootApplication class is coming from a library jar adopted.
I have put license file:camunda-license.txt in src/main/resources still it is not deployed while process engine comes up. It was getting deployed if i use @EnableProcessApplication along with @SpringBootApplication

Any help will be appreciated.

Hi @Amit_keshri,

If you are an enterprise customer, you should open a support ticket in our issue tracker:
https://docs.camunda.org/enterprise/support/

Are you using the enterprise edition in your artifacts?
https://docs.camunda.org/manual/7.10/user-guide/spring-boot-integration/#using-enterprise-edition

Also, you need to use at least the @SpringBootApplication annotation in order for the Camunda configuration to be loaded.

Best,
Nikola

Thanks nikola for your reply.
I am using @SpringBootApplication annotation in a class which is coming from library so camunda default process engine is coming up fine with all the *.bpmn files in src/main/resources are getting deployed as part of SpringAutoDeployment as i am not using @EnableProcessApplication.
My only problem is that i do not observe the camunda license key is automatically deployed though i have put camunda-license.txt file in src/main/resources

Regards,
Amit

Hi Amit,

Thanks for the extra information. Are you by any chance extending or modifying the DefaultProcessEngineConfiguration class, or extending the AbstractCamundaConfiguration? I have seen some examples of users doing this improperly, which results in the license file not being read.

Best,
Nikola

Hi Nikola,

No I am not touching above mentioned classes.

@Amit_keshri did you ever solve this? I’m seeing the same behaviour; the key is simply never picked up, not even an exception if I refer to a non-existent one.

Hi @Amit_keshri , @tiesebarrell, I am also facing the same exact issue, did you got this resolved issue ? If Yes, can you let me know the steps taken to overcome this ?

thanks
Vasu

@vasu.patnaik unfortunately, no. I didn’t get it to work this way, so I resorted to writing a simple process engine plugin that does the same. I had used that approach before in non Spring Boot projects. I was mainly curious why it didn’t work the way I expected based on the documentation.

Hi @tiesebarrell, @vasu.patnaik,

Can you provide an example project that replicates the issue? Previously, I wasn’t able to reproduce it.

Best,
Nikola

Hi,
i’m facing similar issue, i have also reproduced it on sample project:

For obvious reasons i have removed content of camunda-license.txt, please have a look.

(this issue seems to be very random, in few other projects i did not face any issues with license file)

Hi @JohnArray,

In your example, you are not overriding the Camunda version to EE (7.12.0-ee), so that the enterprise artifacts can be used. This means that the validation code for the enterprise license detects a Community edition artifact and doesn’t even attempt to read the license. You can see the documentation here: https://docs.camunda.org/manual/latest/user-guide/spring-boot-integration/#using-enterprise-edition on how this can be achieved.

So, using your example project didn’t pick up the license. However, as I explained above, this was expected. By doing the modifications described in the link above the license key is picked up and works as expected for the EE version.

As a side-note, from Camunda 7.13.0, the Camunda Spring Boot Starter will be using the same version as the platform, so you will need to use the correct version from the start.

Best,
Nikola

PS
If you are an enterprise customer, please create a Support ticket in our issue tracker. You can find out how to do it here: https://docs.camunda.org/enterprise/support/.

1 Like