topic Urgent - production deployment option? in Alfresco Archive

Urgent - production deployment option?

kethur — Mon, 17 Dec 2012 09:51:06 GMT

Hi Team,We have a workflow that needs to be deployed everytime there is a change to the workflow. Usually, if we have activiti explorer we can deploy the bar file as needed. But, we are not using the explorer in our project. Option 1). specify the location of the bar file in activiti-context.fil

Re: Urgent - production deployment option?

kethur — Tue, 18 Dec 2012 10:45:24 GMT

Hi,

Could you please reply to this one?

Thanks,
Raj

Re: Urgent - production deployment option?

mmaker1234 — Tue, 18 Dec 2012 12:18:52 GMT

Hello Raj,

Your requirements are somewhat contradictory:

We have a workflow that needs to be deployed everytime there is a change to the workflow.
…
Option 1). … Problem with this is, everytime we restart the server, it deploys the bar file. Which we dont want.

Please clarify your requirements first.

I would suggest to use Option 1) and to modify current Activity deployer to best fit your needs - you should best know how to distinguish if there are changes in the deployment package.

Best Regards,
Monique

Re: Urgent - production deployment option?

kethur — Tue, 18 Dec 2012 18:00:51 GMT

Thanks for the response.

So, the below means, we want to deploy the workflow "Only if there is a change to the workflow and not when we restart our jboss server".

For example, if i configure a directory where the activity looks for deployment .bar files. For the first time, its okay because, Activiti finds the bar file and deploys. But, next time when i restart the server, the bar file is still in that directory location so, it redeploys the same bar file with a different version. I want to avoid this situation.

Option 1). specify the location of the bar file in activiti-context.file. Problem with this is, everytime we restart the server, it deploys the bar file. Which we dont want.

Option 2). Write a shell script to call a java class that deploys the bar file into process engine. Problem - We prefer not to write an external propgram to deploy.

I am looking for an option something like: When i start my app server, it should look into a directory for a bar file and if the bar file is already deployed, do not deploy it again.

Re: Urgent - production deployment option?

jbarrez — Wed, 19 Dec 2012 08:14:57 GMT

For JBoss we do not have anything specific. However, with Spring we have a 'duplicate filter', check the org.activiti.spring.SpringProcessEngineConfiguration class on how thats done. You could apply something similar yourself.