<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic What is best way to share tools/scripts that are used by WMX steps? in ArcGIS Workflow Manager Questions</title>
    <link>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268929#M570</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have created many custom GPTools, scripts and models that I have incorporated into WMX workflows as steps. What is the best way to share these tools across my organization, so that the steps work for everyone?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For example, I have attempted to store a toolbox on our ArcSDE Geodatabase, but when I set a path to a tool script from WMX to the toolbox in SDE - the path calls on my user name and C drive:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;/toolboxpath:"C:\Documents and Settings\motta\APPLICATION DATA\ESRI\Desktop10.0\ArcCatalog\Connection to diaengsql01.sde\DEN.WMX.SharedWMXToolbox" /tool:BatchDescribeProjection64Bit&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Additionally, our organization is utilizing 32 bit and 64 bit operating systems. This is causing me frustration, because scripts are stored in different folders for 32 and 64 bit users. Should I store them on a network drive? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there anyway to store and call upon tools in SDE? Scripts? Should I be thinking about .dll's?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Mar 2011 20:00:08 GMT</pubDate>
    <dc:creator>AshleyMott</dc:creator>
    <dc:date>2011-03-17T20:00:08Z</dc:date>
    <item>
      <title>What is best way to share tools/scripts that are used by WMX steps?</title>
      <link>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268929#M570</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have created many custom GPTools, scripts and models that I have incorporated into WMX workflows as steps. What is the best way to share these tools across my organization, so that the steps work for everyone?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For example, I have attempted to store a toolbox on our ArcSDE Geodatabase, but when I set a path to a tool script from WMX to the toolbox in SDE - the path calls on my user name and C drive:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;/toolboxpath:"C:\Documents and Settings\motta\APPLICATION DATA\ESRI\Desktop10.0\ArcCatalog\Connection to diaengsql01.sde\DEN.WMX.SharedWMXToolbox" /tool:BatchDescribeProjection64Bit&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Additionally, our organization is utilizing 32 bit and 64 bit operating systems. This is causing me frustration, because scripts are stored in different folders for 32 and 64 bit users. Should I store them on a network drive? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there anyway to store and call upon tools in SDE? Scripts? Should I be thinking about .dll's?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2011 20:00:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268929#M570</guid>
      <dc:creator>AshleyMott</dc:creator>
      <dc:date>2011-03-17T20:00:08Z</dc:date>
    </item>
    <item>
      <title>Re: What is best way to share tools/scripts that are used by WMX steps?</title>
      <link>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268930#M571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Ashley,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The first thing I'd recommend is to ensure that any models/scripts in your toolbox are set to use relative paths, not absolute paths.&amp;nbsp; (There's a description of this option &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//005700000009000000.htm"&gt;here&lt;/A&gt;&lt;SPAN&gt;.)&amp;nbsp; You'll likely need to do this no matter what else you do.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Next, I can think of two ways to proceed, though I've only used the first one myself:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;1) Use the [ENV:...] token and an environment variable to point to your toolbox&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Our project had an installer that would copy the toolboxes &amp;amp; supporting files into a location under "C:\Program Files" or "C:\Program Files (x86)" depending on whether the host machine was running 32-bit or 64-bit windows.&amp;nbsp; Before it finished, the installer created a system environment variable (ex., "PROJ_INSTALL_DIR") that pointed to the install folder.&amp;nbsp; That let us use an &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Using_Tokens/00380000002m000000/"&gt;environment variable token&lt;/A&gt;&lt;SPAN&gt; in the step's arguments to refer to the toolbox location.&amp;nbsp; For example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[INDENT]/toolboxpath:"[ENV:PROJ_INSTALL_DIR]\Toolboxes\..."[/INDENT]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;...and that would expand out to "C:\Program Files\MyProject\Toolboxes\..." or "C:\Program Files (x86)\MyProject\Toolboxes...", depending on the individual machine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The downside is that without an installer, it's not easy to control the toolbox location or environment variable settings on each machine.&amp;nbsp; Also, changing the "/toolboxpath" step argument to include a token plays havoc with the parameter-editing GUI in the WMX Administrator; this is a little annoying if you need to make changes to the step parameters in the future.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;2) Install the tools in a shared location on your network&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;If your organization has a shared directory that's accessible by all of the users of this script -- for example, "S:\Shared" -- you could install the toolbox and its supporting files there.&amp;nbsp; (I &lt;/SPAN&gt;&lt;SPAN style="font-style:italic;"&gt;think&lt;/SPAN&gt;&lt;SPAN&gt; you could also use a UNC path -- ex. "\\servername\Shared".)&amp;nbsp; Either way, you'd just update your "/toolboxpath" step arguments appropriately, then you should be good to go.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I haven't tried this "shared area" approach myself, so I may be missing some pitfalls.&amp;nbsp; Certainly all of the machines will need to be on the (same) network.&amp;nbsp; Also, if your tools refer to any data that's packaged with the toolbox (say, FCs in a single file GDB), I suppose there could be resource contention issues.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I hope this helps.&amp;nbsp; I'm definitely curious to hear how you solve this; please post an update if/when you can!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Brian D.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Mar 2011 16:58:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268930#M571</guid>
      <dc:creator>BrianDemers</dc:creator>
      <dc:date>2011-03-18T16:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: What is best way to share tools/scripts that are used by WMX steps?</title>
      <link>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268931#M572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Brian,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for the awesome response. I have (at least, for now) set up my toolbox, scripts, etc. on a shared drive. I didn't want to get into the issues you cited with the environment token. I think I may go down the UNC path - path in the near future. I just need to study up on that, because that is new for me.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks again for all of the great advice!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Ashley&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Mar 2011 17:56:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workflow-manager-questions/what-is-best-way-to-share-tools-scripts-that-are/m-p/268931#M572</guid>
      <dc:creator>AshleyMott</dc:creator>
      <dc:date>2011-03-21T17:56:15Z</dc:date>
    </item>
  </channel>
</rss>

