Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Broker Servers | Running Multiple Broker Servers on the Same Host Machine | Running Multiple Broker Servers in a Single webMethods Broker Environment
Running Multiple Broker Servers in a Single webMethods Broker Environment
Running multiple instances of Broker Server can be more advantageous than running multiple Brokers on a single Broker Server. For example, instead of hosting two Brokers on a single server, you might create two Broker Servers that each have a single Broker. By hosting the Brokers on individual Broker Servers, each Broker has a dedicated queue storage system with its own log file.
When you create a new instance of Broker Server, the server_config utility creates the following items for the new server:
*A data directory
*A configuration file
*A set of queue storage files
Additionally, it registers the new Broker Server with the Broker Monitor. If you are running on a Windows platform, the server_config utility will also register the new Broker Server as a Windows service.
When creating a new Broker Server, keep the following points in mind:
*Make sure the Broker Server's block of three ports does not interfere with the Broker Monitor port (the default port is 6850) or with ports used by other Broker Servers (or other applications) running on the host machine. For more information about port assignments, see Broker Server Communication Ports.
*To prevent documents from paging to virtual storage, ensure that the host machine is equipped with sufficient physical memory to support the volume of documents received by all Broker Server instances that it hosts.
*Each Broker Server on the machine requires access its own set of queue storage files. To prevent disk contention among the Broker Servers, queue storage files may need to be divided across different devices.
The Broker Server will start automatically after you create it unless you include the -nostart option in the server_config command.