Deploy "Custom" Custom Steps WMX Server

3060
2
Jump to solution
07-21-2015 05:45 AM
Mary_EllenPerko__not_ncid_
Occasional Contributor

Hi.  We're implementing WMX for Desktop for some users and WMX for Server and web app for other users.  And we need to develop several "custom" custom steps (e.g. the WMX developer kit samples). So, we need to be able to deploy the same "custom" custom steps in both environments.  Can anyone point me to information that could help us answer the following types of questions?

~ How do we deploy a "custom" custom step tool (e.g. something from the WMX developer kit samples) so it is available to users using the web app version of WMX.

~ What is the best practice for creating "custom" custom step tools that need to work in both environments.  What is the best approach?  What do we need to watch out for?  What can we do in one environment, but not the other.

~ In the past, we've created a .dll and installed it on each desktop WMX user's computers - is that the correct way to deploy custom steps for desktop users?

Thanks,

Mary Ellen

0 Kudos
1 Solution

Accepted Solutions
MichaelBroadbent
Esri Contributor

Hi Mary Ellen,

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

View solution in original post

0 Kudos
2 Replies
MichaelBroadbent
Esri Contributor

Hi Mary Ellen,

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

View solution in original post

0 Kudos
Mary_EllenPerko__not_ncid_
Occasional Contributor

Thank you!  This exactly what we needed to get started.  Very much appreciated!

0 Kudos