I'm very new to JBOSS, having a really hard time trying to figure out how to bind different .ear deployments to specific ports. I'm migrating an app server from WebLogic to JBOSS. In WebLogic, this was quite a simple thing using the web console. Looks like in JBOSS, I'll have to tweak some config files, that's fine, but I can't make it work.
My use-case is that I have two separate ear files that I want to deploy on different ports from a single server bound to a single IP address:
myApp1.ear: port 7001
myApp2.ear: port 7201
I dug through all kinds of docs and googled and searched these forums and found various things, but nothing specific to this scenario.
I started messing with bindingservice.beans/META-INF/bindings-jboss-beans.xml. Looks like this is where it would be configured, I tried a few settings to no avail though. I see where I can change the default port number, that would account for one of the ports, but what about the other?
I also dug through conf/jboss-service.xml file but couldn't really find anything in there, though I do see some things relating to ports.
Why do I need this port configuration you might ask? I really don't, except there's a large install base of client applications that are already configured to point to these ports since it's how it was in WebLogic when those clients were deployed. So to prevent having to update all the clients, it seems like it should be an easy matter to just bring up all these services on the ports as they are today.
From what I'm finding, it seems the only option is to bring up two separate servers bound to the same IP but changing the default port on each server, and applying port offsets to prevent port collisions. This seems pretty messy though, compared to WL.
Any guidance would be greatly appreciated.