How to deploy custom wmx steps to WMX Web Version?

2391
1
10-26-2015 10:54 AM
ChelseaDuncan1
New Contributor

I have successfully developed and implemented many custom wmx steps on desktop 10.3.1.

I have modified those for server, making sure that no desktop only WMX assemblies are being used.

I used C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe to register the .dll files on the server machine. I stored the .dll files (registered with RegAsm.exe [64]) C:\Program Files\ArcGIS\WMX\Server10.3\Bin for the WMX Web Version application to consume it.

When the .dll is successfully registered and stored in this location, the web version application of WMX still cannot find the step. The equivalent steps registered on desktop and stored in the desktop install bin folder are executing without issue on the same machine.

How should I be deploying these .dll files on the server machine such that the WMX web viewer application can access them?

What is the purpose of this exe: C:\Program Files\ArcGIS\WMX\Server10.3\Bin\UpdateWMServer.exe   ?

0 Kudos
1 Reply
by Anonymous User
Not applicable

Hi Chelsea,

Thanks for your question, for configuring Workflow Manager Server custom steps there are a few important things to keep in mind. The items below are on the assumption that you're developing this using .Net.

- When building the step ensure that you are not relying on Desktop only WMX assemblies like ESRI.ArcGIS.Utilities or ESRI.ArcGIS.JTXUI. For the first you would want to use Common Utilities. This is something to look out for in the samples, as they may use Utilities.

-  Make sure to target "Any CPU" (MSIL) in your code

- The DLL will need to be deployed to every machine that you intend on using it from Workflow Manager, both desktop and server machines.

- For desktop machines the step will need to be registered with the 32bit version of regasm and for server it will need to be registered using the 64-bit version. You can find it typically at c:\Windows\Microsoft.NET\Framework64\... If your machine is using both desktop and server you'll need to register it twice per above.

In general we recommend (whenever possible) to develop the step for desktop first, make sure it is working correctly in the desktop environment and then make the necessary changes for Server. It is much easier to debug any potential issues after confirming it's solid on Desktop.

Thanks, if you have any further questions feel free to let us know.

Cheers,

Michael

0 Kudos