Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Broker Servers | Configuring Broker Server for high throughput in high-latency and high-bandwidth networks | Configuring Parallel Channels in Broker Servers
Configuring Parallel Channels in Broker Servers
The parallel channel messaging feature enables Broker Servers to use more than one TCP/IP socket for Broker to Broker communication.
Broker Server uses the baseport -3 and baseport -4 ports. These ports must be available for parallel channel messaging.
In the communicating Broker Servers, you need to enable parallel channel messaging, and specify the number of sockets required for Broker to Broker communication.
The parallel channel messaging feature supports basic authentication in both UNIX and Windows systems. Supports SSL only on a UNIX system.
When you configure parallel channels in a Broker Server, streaming is enabled, if you have not explicitly disabled streaming by specifying rbroker-streaming-enabled=0 in the awbroker.cfg file. On a high-bandwidth network, you can achieve high speed message transfer when you configure parallel channels with streaming.
If streaming is enabled when you enable parallel channel messaging, set the rbroker-streaming-window-size, connection-sndbuf-size, and connection-rcvbuf-size configuration parameters as required. For information about configuring streaming, see Configuring Streaming in Broker Servers.
*To configure parallel channels for communication between Broker Servers
1. Stop the Broker Server.
2. On the machine where Broker Server is installed, locate the Broker Server's configuration file (awbroker.cfg).
3. Open the configuration file with a text editor.
4. To enable parallel channels, specify:
5. To specify the message size or the batch size limit that the remote Broker must use while sending messages to other Brokers, set the value in the rbroker-max-send-events-size parameter. Setting this parameter according to your network bandwidth avoids message delivery delays. Adjust the message size or the batch size limit according to the receive Broker log file size. The default value is 16MB. Maximum value recommended is 64MB. Adjust the receiving Broker Server's run-time log file size as required.
6. To define the number of sockets the remote Broker can request for communicating with another Broker, assign the value to the rbroker-parallelchannel-count parameter.
Make sure that the number of parallel channels requested by both the communicating Brokers is the same. If the number of parallel channels requested by the two communicating Brokers is not the same, then the default value of 5 parallel channels are used for message communication.
7. Save the configuration file.
8. Restart the Broker Server.