if the instances are going to run on seperate boxes, then you don't need to do anything else other then have the seperate database instances.
if you are going to run on the same box, that is not easily supported at the moment, but you do have 1 of 2 options. 1) you could setup multiple instances of jboss to run on one machine. this would require you to setup port bindings so you don't get conflicts when trying to start multliple instances 2) you could deploy nukes multiple times in the same instance, but that would require you to change the mbean names contained in the -service.xml files so they are unique (you'd also have to change the servlet root context in the application.xml file as well). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836964#3836964 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836964 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
