The binding service brings all of the port definitions into a single file (without it,
they ports are scattered all over the place). This makes it easier to define multiple sets
of port configurations if you plan on running multiple instances of the app server on the
same host - two instances cannot use the same ports because you get port conflicts.
Alternately, if you have multiple IP addresses defined on you host (either with multiple
network cards or youi have set up virtual IP addresses on a single card), you can run
multiple app server instance by binding each ot its own IP address. Example:
run -c config1 -b 192.168.0.100
run -c config2 -b 192.168.0.101
Thus, either option (binding to separate IP addresses, or using the binding service) can
be used to run multiple instances.
The -b 0.0.0.0 option binds the ports to all IP addresses defined on the host. Thus is you
have multiple IP addresses, port 8080, for example, is bound to every address. This means
that a browser can access web apps via any of those IP addresses (example, via both
and via http://192.168.0.100:8080
, and it will be the exact same
Of course, you can combine the two mechanism. Thus you could use the binding service to
define the ports and still use the -b option to bind to one or all IP addresses.
View the original post :
Reply to the post :