Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM Upgrade - Moving Workflow instances

Avatar

Level 2

We are doing an AEM upgrade from 6.4 to 6.5.

So the plan is to clone the existing and do an in-place upgrade, while this being done, there are chances of updates happening on the existing system with uploading assets and workflow updates. We want to make sure all the active workflows in the existing system is coped to the new instance.

 

What would be the best way to move all the delta workflow instances from one instance to other? Would packaging the entire /var/workflow/instances cause any issue? 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 10

I would recommend you to do a content freeze while you are doing an upgrade in production. When you move content or workflows from 6.4 to upgraded instance then you basically bring in data which has not been in place upgraded. The in place upgrade utility will make sure to update any properties on the nodes which have changed in 6.5 version. So it will not be a good practice to bring content from 6.4 instance after you have done in place upgrade. 

View solution in original post

3 Replies

Avatar

Community Advisor

Hi,
I am not sure if packaging will work, because instance contains workflow id(should be change to etc to var) and other meta info which will be used by workflow instance.

I would suggest to get all the incomplete workflow instance payload path and re run workflow again using bulk workflow manager or via script against those payloads.

 

Avatar

Level 2

Thanks Arun, utility for running workflows would work. But in cases for example, when the clone is created "WF Instance A" is running in both old and new instances. Assume, post cloning "WF Instance A" in existing instance is made "COMPLETE", but in the new 6.5 instance the would be still in RUNNING state right? And also there are chances of WF history getting missed.

Avatar

Correct answer by
Level 10

I would recommend you to do a content freeze while you are doing an upgrade in production. When you move content or workflows from 6.4 to upgraded instance then you basically bring in data which has not been in place upgraded. The in place upgrade utility will make sure to update any properties on the nodes which have changed in 6.5 version. So it will not be a good practice to bring content from 6.4 instance after you have done in place upgrade.