Select to view content in your preferred language

Coverting Back to ArcGIS Workflow Manager Server (Classic)

454
1
Jump to solution
02-09-2021 08:58 PM
AlvinKhaw
Esri Contributor

Q1. Just would like to understand whether is it possible for the customer to convert back to ArcGIS Workflow Manager Server (Classic) from the new Service-Based ArcGIS Workflow Manager?

For Example,

Customer has been a user of the ArcGIS Workflow Manager Server (Classic) and decided to convert it to the new Service-Based ArcGIS Workflow Manager. 2 months later, customer feel the new Service-Based ArcGIS Workflow Manager does not meet their requirement and would prefer the Classic version. Under this kind of scenario can the customer convert it back to the Classic version.

 

Q2. Can the customer still used the ArcGIS Worflow Manager Server (Classic) after they convert it to the new version?

I have read through the Q & A post but can't seems to find the answer. Hope someone can help me on this.

 

0 Kudos
1 Solution

Accepted Solutions
JFarmer
Esri Contributor

Hi Alvin,

Thanks for posting your questions! Please see some answers below and let me know if you have any questions.

  • Q1: Workflow Manager Classic and the new service driven architecture are based on two different technologies, each with different underlying architecture. Because of this, developing tools to fully migrate from one product to the other is a challenge. We have discussed developing limited conversion tools to move parts of a Workflow Manager Classic deployment into the new service driven architecture but those tools are not available now. In general, we’d recommend users try not to transition back to Workflow Manager Classic as that product is planned to be depreciated over time.
  • Q2: Whether a user can use Workflow Manager Classic or the new services driven architecture is dependent on whether they are licensed for those products. Users can certainly purchase licenses for both products, however, it is more common that organizations are converting their Workflow Manager Classic licenses into User Type Extensions for the new service driven architecture. In those cases, once the license conversion is complete, they are no longer licensed for nor able to use Workflow Manager Classic.

Thanks!

Jonathan

View solution in original post

0 Kudos
1 Reply
JFarmer
Esri Contributor

Hi Alvin,

Thanks for posting your questions! Please see some answers below and let me know if you have any questions.

  • Q1: Workflow Manager Classic and the new service driven architecture are based on two different technologies, each with different underlying architecture. Because of this, developing tools to fully migrate from one product to the other is a challenge. We have discussed developing limited conversion tools to move parts of a Workflow Manager Classic deployment into the new service driven architecture but those tools are not available now. In general, we’d recommend users try not to transition back to Workflow Manager Classic as that product is planned to be depreciated over time.
  • Q2: Whether a user can use Workflow Manager Classic or the new services driven architecture is dependent on whether they are licensed for those products. Users can certainly purchase licenses for both products, however, it is more common that organizations are converting their Workflow Manager Classic licenses into User Type Extensions for the new service driven architecture. In those cases, once the license conversion is complete, they are no longer licensed for nor able to use Workflow Manager Classic.

Thanks!

Jonathan

0 Kudos