Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Broker Servers | Running Multiple Broker Servers on the Same Host Machine | Running Multiple Instances of webMethods Broker on the Same Host
 
Running Multiple Instances of webMethods Broker on the Same Host
You can run multiple instances of webMethods Broker on a single host machine. A webMethods Broker environment can run on each available IP address or port on the host.
One advantage to running multiple instances of webMethods Broker on a single host is for ease of management. For example, if the webMethods Broker environments share the same Broker Monitor port, you can discover and manage all of the Broker Servers running on that port in one Broker Server list through My webMethods.
There are several other reasons why you may want to run multiple instances of webMethods Broker on the same host machine. When you upgrade or change a Broker Server configuration on a production system, all Broker Servers in the same webMethods Broker environment must be stopped and restarted, disrupting the production system. However, when running multiple instances of webMethods Broker, each installation of webMethods Broker is a stand-alone application with its own set of unique configuration files and its own Broker Monitor so maintenance on one Broker Server does not affect the availability of another. Running multiple instances of webMethods Broker gives you the ability to upgrade or uninstall one instance of a Broker Server independently of the others.
When running multiple instances of webMethods Broker on the same host machine, keep the following points in mind:
*During installation, Broker Monitor binds to a port and IP address on the host machine. If multiple webMethods Broker environments exist on the same host machine using the same IP address, make sure each instance of Broker Monitor is assigned a unique port number. For more information about port assignments, see Ports and Running Multiple Instances of Broker Monitor .
*On UNIX platforms, each Broker Monitor instance requires its own start up script. Ensure that each start up script file is unique between each Broker Monitor instance. For more information about the start up script, see Starting Broker Monitor .