topic Re: Newbie multitenancy questions in Alfresco Archive

Newbie multitenancy questions

lossril — Tue, 20 Oct 2015 13:11:56 GMT

Hello,I've read about multitenancy in Activiti and have some questions about it.Okay, for example we might have two Activiti REST webapps connected to the same database where processes with two different tenantIDs are deployed. 1. How does webapp identify itself with tenantID? I didn't find anything

Re: Newbie multitenancy questions

jbarrez — Tue, 20 Oct 2015 17:33:30 GMT

1. When you use multitenancy, you always need to pass the tenantId. How you get this tenantId from your current user, that is up to you.

2. Again, you will need to provide the tenantId. There is a non-MT method, and a MT-enabled methode, like void signalEventReceivedWithTenantId(String signalName, String tenantId);

3. Same. The timer is created in the context of a tenant, when you deployed the process definition.

Re: Newbie multitenancy questions

lossril — Wed, 21 Oct 2015 07:40:50 GMT

Well, I still don't get the idea how the Activiti ProcessEngine gets its own tenantID and starts only those processes which have the correct tenantID.

For example, I create the deployment with the process starting by timer, it would have some tenantID 'rest1'. We have two(or more) REST webapps or any other ProcessEngine instances poking the same database. So what happens when the time comes for process to start? Which ProcessEngine would create the process instance? Would they create several process instances?

I got the point about signals having their tenantIDs though, so when signal arrives(e.g. via REST), it triggers only for the process instances which have the tenantID.

Re: Newbie multitenancy questions

lossril — Mon, 26 Oct 2015 15:57:45 GMT

Well, can someone explain it to me?

Re: Newbie multitenancy questions

jbarrez — Wed, 28 Oct 2015 19:09:00 GMT

Relax, this is an open source forum, we try to answer in a best effort way, but many people are on holiday now.

> I still don't get the idea how the Activiti ProcessEngine gets its own tenantID and starts only those processes which have the correct tenantID.

You deploy a certain process definition and provide a tenant id. All process instances derived from this process definition inherit this tenant id. Note that you pass the tenantId when calling the runtimeService.startProcessInstanceByKey() for example.

For your example: the process definition was deployed with a certain tenantId. The timer inherited that tenantId. The process instance that is started will inherit the same tenantId.

Re: Newbie multitenancy questions

lossril — Mon, 02 Nov 2015 07:46:59 GMT

Yes, sure, sorry. I've just bumped the thread so it wouldn't be buried.

Okay, this makes a bit more sense now, thanks a lot!

Re: Newbie multitenancy questions

jwestra — Tue, 23 Feb 2016 23:19:20 GMT

Hi!

I'm not sure the OP's question #2 was ever answered regarding signals that are tenant-aware… I TOO have the same question

I am looking at the 5.19.0.2 API's :

RuntimeService.signal(String executionId)
RuntimeService.signal(String executionId, Map<String, Object> processVariables)

Neither of them pass the tenantId.

Is there a different way to pass a tenantId via a Signal that I am missing, perhaps as a special, reserved processVariable key?

Jason

Re: Newbie multitenancy questions

jbarrez — Wed, 24 Feb 2016 10:15:05 GMT

No, and neither should pass the tenant id. signal is executionId bound. execution ids are unique accross tenants.

You're confusing it with signalEventReceived (the BPMN signal), which does have it: signalEventReceivedWithTenantId().

Re: Newbie multitenancy questions

jwestra — Wed, 24 Feb 2016 20:28:19 GMT

Hah. So many ids and keys to keep track of in my head… That makes perfect sense. Thanks!