AnsweredAssumed Answered

Workflow Manager Configuration (JXL) Deployment

Question asked by apurvdanke on Sep 27, 2017
Latest reply on Nov 30, 2018 by MBroadbent-esristaff


The workflow manager configuration deployment is becoming a big challenge for us. We have many different custom job types, Maps(MXD's), Workflows, Notifications, Queries, step types, job filters which we're using in our Workflow Manager configuration. Initially we used to export the entire Workflow Manager configuration as a JXL file and then this file would get installed into target environments such as testing and production environments. After installing, we would need to import this JXL file into Workflow Manager Administrator, but we would need to do a lot of post installation activities, such as setting the target data workspace, adding/removing users according to target environments, setting the data workspaces for job types, subscribing users to notifications etc. These post installation steps would take a lot of time and there is always a chance that some mistakes would be committed during these steps.


However we found that we can also export individual entities like job types, workflows, notifications, queries etc. as JXL files and import these in target environment as part of deployment. This approach works fine for new additions in the WFM configuration such as new workflow, new job type, new step type etc. However if we need to make changes to existing entity such as a workflow, or a job type, then we cannot overwrite the existing entity in WFM administrator by choosing to import the JXL file. For example if we need to make changes to an existing job type, then in the target environment we first need to delete the existing job type and then import the JXL for the updated job type. However at the time of deleting the existing job type, we get an error message as given below.



Now it is understood that there are jobs which currently exist in WFM for this particular job type. However there are a huge number of jobs for this particular job type. As we're using OS Authentication for WFM, the jobs and their job versions need to be deleted by the respective users. Before deleting the jobs, they should reconcile and post their edits in their job versions to SDE.Default to ensure their edits are not lost. Once all the jobs and versions are deleted, then it would be possible to delete the job type in WFM and import the updated job type JXL. This is a huge time-consuming activity. It would be great if there was a way to get around this and be able to simply overwrite the changes for this job type in WFM Administrator, without needing to delete any jobs. I know that there is an option to import the entire WFM configuration JXL file, and while doing that we do get an option whether to clear the existing jobs or to retain them. But we do not want to import the entire WFM configuration, for updating just one job type. Any suggestions are greatly appreciated.


We are using ArcGIS Desktop 10.4.1 with Workflow Manager. Database used is Oracle 12G, and the users connect via OS authentication to WFM.