Keep production seperate from unrelated installations. Dont' want to bring down prod by others.
Maybe you can combine the test and demo instances into one.
Yes, I agree - separate prod from the others. Probably will be done, lets say they have 2 boxes for 3 systems (test, demo and prod). OK, like you say, combine test and demo. Same question applies - what's the method or approach people have made to solve this? Instances of JBOSS or code for it?
I've tried to code, but it means changing package names in the .java classes (to ensure separate class file identifications referred to in the ejb-jar.xml) otherwise you get the same class even if different jndi names specified in the ejb-jar.xml. Rather not change the source.
More input gladly accepted folks!
Don't code for it. It will be a nightmare maintaining separate names in JNDI for everything. Run multiple JBoss instances on a box. The config is very easy, using the binding service to manage listen ports. If you haven't yet, buy the admin/config guide. I think there is also a downloadable doc chapter on the binding service in the SF download area.
another option you have is to multihome the box
then start multiple jboss instances like so:
1) jboss/bin/run.bat -b 192.168.1.101
2) jboss/bin/run.bat -b 192.168.1.102
now you have multiple jboss instances running on the same box
but all using the same ports for their services (ie. the NamingService
is always running on 1099).
On my windows 2000 box it is fairly easy to define more
than one IP adr for my one network card (network --> properties for you network card --> TCP/IP properties --> advanced )