how to migrate ArcGIS Workflow Manager (service-driven) from one environment to another environment

[SirishByreddy]

Hi All,

ArcGIS enterprise version: 10.9.1

We are using ArcGIS Workflow Manager Server (service-driven) and we have approximately 60+ different workflow diagrams, different job templates with extended properties, email templates and configurations etc..

Is there anyway or approach to migrate these workflow diagrams, job templates, email templates from environment to another environment (Ex: from UAT environment to PROD environment) instead of recreating all. Thanks.

Regards,
Sirish

[Haley_Clowes]

Thank you, Jonathan!

[JFarmer]

@bmcc @sirishb 

It looks like we'll need to update the script to account for shared extended properties tables. Apologies for that. I don't have a set timeline there but we are working on it now.

In the meantime, it looks like you can do the import twice as a workaround here. The second import attempt should work for that second job template. 

@sirishb 

On the rec and post tool issue, I'm afraid I don't have too much information beyond what the error message is saying. It sounds like there may be editing going on when the tool tries to run? Since we don't have a specific Reconcile and Post step in Workflow Manager though, this issue shouldn't be specific to us. You should be able to reproduce that outside of Workflow Manager, running the script manually. May be worth it to create a new question with some more details on the workflow or see if Tech Support can assist.

[bmcc]

Hello @JFarmer,

We have built and have been using a migration tool to successfully move workflows between a number of ArcGIS Enterprise environments. Thanks for your earlier support.

Error:

Now however we are encountering an issue attempting to run the tool against a new environment. The following error occurs when trying to create either of these objects:

• arcgis.gis.workflowmanager.WorkflowManager
• arcgis.gis.workflowmanager.WorkflowManagerAdmin

"RuntimeError: Unable to locate Workflow Manager Server. Please contact your ArcGIS Enterprise Administrator to ensure Workflow Manager Server is properly configured."

Investigation:

The Workflow Manager server is available from the same machine where the script is running, via both the browser and ArcGIS Pro. I am able to create workflows via the browser and run jobs as normal via Pro. The issue occurs only when trying to access the workflow manager via the Python API.

The only obvious difference with this environment is that the Workflow Manager server is on a separate federated ArcGIS Server. In all previous environments where this code has been run successfully, the Workflow Manger server was on the Hosting server making up part of a base deployment.

Are you able to provide any suggestions for further investigation?

In particular, do you think it may be relevant that the Workflow Manager server is on a separate machine?

Thanks,

Blair

[PaulDhandapani]

Waiting in the same queue for solution.  Receiving the exact same error message as like you...

@JFarmer - any break-through?

[JFarmer]

Hi @PaulDhandapani 

The only known issue we have is that Python API bug I mentioned with 1.9x. If you upgrade to 2.0.0 or higher, does that not solve the issue? If not, you may need to work with Tech Support to troubleshoot further as we aren't aware of any other issues in this area.

[JFarmer]

Hi @bmcc 

It's possible you are running into a bug with the Workflow Manager Python API bug (arcgis 1.9.x) where you have multiple federated servers and it cannot find the Workflow Server if it is not first in the list. You'll need to upgrade the Python library in Pro using the Conda command line.

Check Python API library:

1. In Pro, go to File -> Package Manager and look for the arcgis package to check the version. If it is at 1.9.x then it will need to be upgraded to 2.0.0 or higher.

Upgrade arcgis Library:

2. Ensure you have created a clone of the Python environment in Pro

3. Open the Python3 command prompt (you can type cmd into the search at the bottom of the screen)

4. Change the directory to the cloned environment if it is not already pointing there.

If the cmd prompt does not have the path to the cloned environment, type in:  cd pathToYourEnvironment

(ex. Cd C:\Users\<yourusername>\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone)

5. Type in the conda command line to update the arcgis package to 2.0.0

1. conda install -c esri arcgis=2.0.0
2. Hit enter and follow prompts. It will ask to continue about half way through the process and you will have to select Y/N.

6. When this completes, close and open Pro (if it was open during the update) and check the arcgis library in the Package Manager. It should be updated to 2.0.0.

If this isn't it, you may need to work with Tech Support to troubleshoot this one a bit more.

Jonathan 

[sirishb]

@JFarmer  We have followed the provided steps and now we are able to import workflow templates and diagrams using Python API.

Thank you very much.