nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

sirishb

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

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

JFarmer

Hi @SirishByreddy

We are working on a solution for importing and exporting parts of a Workflow Manager deployment (diagrams, job templates, etc). This is on our near-term roadmap but I do not have a firm date on when this will be available.

However, this can be done now using our Python API. We're also working on a sample script that you can use to get started and should have that ready in the next week or two. I'll post back here once we have that ready to go.

Thanks,

Jonathan

sirishb

Hi @JFarmer ,

Thank you for the update and python api script will help us to proceed further. Thanks.

Regards,

sirish

bmcc

Hi @JFarmer,

Has there been any progress on this sample script?

I am in a similar situation to @sirishb, and will shortly be embarking on a project to automate the duplication of workflow manager assets between Portals with the Python API.

Any guidance would be much appreciated.

Thanks,

Blair

JFarmer

Hi Blair,

We're working on this, sorry for the delay. Hope to have something here for you both soon.

Jonathan

JFarmer

Hi @sirishb @bmcc @SirishByreddy

Thanks for your patience while we got this work done.

There is a public repository on GitHub for Workflow Manager samples. There is now a directory for service-based code that has been written such as the admin tools (import/export) and the reconcile/post tool that may be published as a GP service to automate this task in workflows. As new Python tools are written for repeatable tasks or updates are made for newer versions of the software, they will be uploaded here.

Workflow Manager Service-based Samples:

https://github.com/Esri/workflowmanager-samples/tree/master/ServiceBased

Let me know if you have any questions. We are working on 11.0 sample scripts as it's a little different there. Those should be up soon.

Jonathan

bmcc

Thanks a lot @JFarmer.

Is there a way to migrate multiple job templates which use the same extended properties table to the same workflow?

Multiple job templates can be created against the same table by using the duplicate job template button in the Workflow Manger web app. However, when attempting to migrate the second job template to a new workflow with the Python API it returns an error:

Duplicate extended property table name(s) found: test_table_01
(Error Code: 0)

This seems to be because the table gets created when the first job template is migrated, but when the same extended table properties are specified for the second job template the API attempts to create that same table again rather than assigning the existing table to the job template.

I have not been able to find a solution to this with the tool I have been working on. I have tested this sample code and found the same limitation, do you know of a solution for this?

Thanks,

Blair

sirishb

Thanks a lot @JFarmer.

We are also facing the similar problem for "import/export" as mentioned by 'Blair'.

We are facing an issue in 'reconcile/post tool', when we try to execute getting error "Version already in edit mode. Only one user can be editing a branch version". We have not been able to find a solution to this with the tool and we are working on this. Any suggestion/solution for this?.

Thanks.

Sirish

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

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:

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

conda install -c esri arcgis=2.0.0
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

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.

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.

Haley_Clowes

Hi @JFarmer ,

I have a similar use case in which I would like to duplicate a Workflow Manager Project within an Enterprise 11.0 environment. I don't suppose the 11.0 sample scripts are available yet please?

Many Thanks,

Haley

JFarmer

Hi @Haley_Clowes

You can use the existing 10.9.x scripts as-is for 11.0 with one caveat that you will need to tweak the code a bit if you have extended property tables shared with multiple job types.

On a related note, we've built import / export functionality into the Workflow Manager REST API for the 11.1 release which should help. We have it on the near-term roadmap to get it into the web app itself.

Jonathan

Haley_Clowes

Thank you, Jonathan!

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.