Ah, I should have added that this is for a strictly in-house Galaxy implementation with absolutely no intention of publishing these specific tools (just these ones!  I promise I&#39;ll publish other tools in the future :) <div>
<br><br><div class="gmail_quote">On Tue, Apr 5, 2011 at 12:38 PM, Peter Cock <span dir="ltr">&lt;<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Apr 5, 2011 at 5:27 PM, andrew stewart<br>
&lt;<a href="mailto:andrew.c.stewart@gmail.com">andrew.c.stewart@gmail.com</a>&gt; wrote:<br>
&gt; I&#39;m aware of how to configure Galaxy to use SGE in universe_wsgi.ini,<br>
&gt; however what I want to do is a little different.  Because I only want<br>
&gt; certain processes to be submitted to the queue, I&#39;d rather control this at<br>
&gt; the tool configuration level (the xml wrapper).<br>
<br>
</div>Hi Andrew,<br>
<br>
That seems like a bad idea for portable XML wrappers - having local<br>
configuration information hard coded within a tool wrapper would<br>
prevent the tool (and any workflow using it) from being shared with<br>
another Galaxy server.<br>
<font color="#888888"><br>
Peter<br>
</font></blockquote></div><br></div>