Joe, welcome to the JBoss forums!
It is usually preferred to edit the service.bat file to make it start up alternate configurations - just edit the line that starts the server.
As to stopping the server, that relies only on the hostname and the JNDI port for the the app server (it is completely independent of which configuration was started). As long as those are the defaults (localhost:1099) then no change is required. If you do change the defaults, then edit service.bat to pass the proper value to shutdown (using the -s parameter).
Hey! Thanks ^_^
I guess I'm still missing something. I didn't explain it exactly right the first time, sorry.
I can change the 'service start' configuration in service.bat to start alternate configurations, that works fine, but that just runs the server as a service and doesn't install it.
If I run 'service install', it doesn't actually start the server, so I can't add the '-c <configuration>' to it. 'net start <svcname>' starts the service once it's installed, but I can't give it an alternate configuration option, so I resorted to editting the run.bat file.
I've seen other posts about using the Java Service Wrapper, so maybe I should be using that to install alternate server configurations? It just seems weird that, since 'service.bat install' will install the default configuration, it wouldn't have a method for installing alternate configurations.
You need to make a copy of service.bat specific for your service and place the "-c xxx" into the copy. Then run the copy to install the service. If you want to run multiple services, there are also a number of other changes you will need to make in service.bat. I have already done that with my service.bat; to see the changes download the source code for JBoss in Action (http://www.manning.com/jamae) and look at jbia-src/ch15/src/service/windows/service.bat.
The thing is that when you start the JBoss server, that fires up jbosssvc.exe and all it does is run service.bat (check out what 'install' does in service.bat). The biggest issue is that whoever wrote the service.bat file never gave a thought as to how it was to be used in a real environment; they just wrote enough to get it to work with minimal functionality.
Ok, somehow I missed that the service start command 'net start <svcname>' called called 'service.bat start', so adding the '-c xxx' there would do what I wanted. I knew it was something stupid I didn't understand.
Thanks for being patient with a newbie.