New ManagementService.setLicenseKey option preferred?

Camunda 7 Topics Discussion & Questions
1

I noticed a new method was introduced with 7.12 to insert the enterprise license key into the database, with ManagementService.setLicenseKey. Good to see there’s now a standard way to do this in the API, besides putting it into the properties table yourself. I also see that the way it’s stored by the API is different from what would previously have been the effect of putting it into the field in Admin.

The current implementation of GetLicenseKeyCmd looks for the key in two ways: first the new way, then in the older properties table as a fallback.

Does this mean that the new way is preferable to the properties table and the latter might be deprecated at some point? We use a process engine plugin that applies the key to any created engine, but currently still uses the old way, so I’m wondering if we need to switch for future stability.

2

Can someone from the Camunda team make a statement on the preferred approach?

3

Hi Tiese,

We are currently changing the format of licenses so that a license file will be a bit larger. Unfortunately that means it won’t necessarily fit into the property table anymore, so that’s why the 7.12 license key API stores it by default in the byte array table (and the property just contains a reference to the byte array).

Nevertheless, the API remains backwards compatibility, i.e. it can still ready licenses stored in the property table. So as long as you are on an “old” license, it is fine to stick with the property. I recommend to eventually switch to the new API for storing the license. For any more detailed questions, I suggest contacting customer support, as we can provide more details about how the licenses work in a confidential setting.

Cheers,
Thorben

4

Hey Thorben,

thanks for making that clear. I think we will migrate to the new way for future proofness but it’s good to know that nothing will change any time soon and that if the license fits in the property table now and is valid, it will remain that way until renewed.

Best,
Tiese

5

Hi Thorben,

I have set the Camunda License Key using the ManagementService.setLicenseKey(camundaLincenseKey). Ex: processEngine.getManagementService().setLicenseKey(camundaLicenseKey);

This method inserted records in the following tables.

ACT_GE_BYTEARRAY
ACT_GE_PROPERTY

First it insert into the BYTEARRAY and it’s ID has been referenced in PROPERTY table. After this, accessing the Camunda Cockpit, it is still asking for the licensekey.

image
image1296×667 43.8 KB

6

Hey @prabhakergoli,

Please contact Camunda support to resolve this efficiently.

Cheers,
Thorben

7

Hi Thorben,

Thanks for your quick reply. It is because of the format of the License Key.

Thanks
Prabhaker Goli