It's been a while since we last spoke about this, but I believe I have found an
interesting solution that does not require the creation of a separate partition.
Basically, I modified the farm-service.xml file on the Windows node to include an
additional deployment URL:
<attribute name="URLs">
| farm/,farm_windows/
| </attribute>
This additional URL is only specified in the farm-service.xml on the Windows node, so
the Unix nodes have no idea that this URL even exists. I partially tested this by
creating the farm_windows directory on my Windows node and placing one of my
Windows-specific deployment files there. I started the Windows node and verified that
it deployed everything, including the item in the farm_windows directory. I then
started the Unix node and watched to see what was farmed and deployed. Lo and behold,
only those items in the farm directory on the Windows node were farmed and deployed to
the Unix node. I have not yet tested this with a second Windows node, as my server
cluster does not currently have another Windows machine, but I suspect that it will
work as expected and farm all of the deployments, including those in the farm_windows
directory, so long as the farm-service.xml on the Windows node specifies farm_windows
in the URL list.
<a
href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826012#3826012";>View
the original post</a>
<a
href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826012>Reply
to the post</a>
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
