Kbase 19975: SonicMQ: How to Set Protocol for Interbroker Communication
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/08/2001 |
|
SUMMARY:
This solution applies to Progress SonicMQ Versions 2000.x and 3.x.
It explains how to specify the protocol to be used for interbroker
communication (communication between brokers in a cluster), if you
wish to use a protocol other than the default protocol.
SOLUTION:
By default, the protocol and port specified by the broker.ini
parameters DEFAULT_SOCKET_TYPE and PORT, respectively, are used for
interbroker communication. To use a different protocol, set the
broker.ini parameter NUM_ACCEPTORS to equal the total number of
acceptors (protocol/port pairs) to be used for client and interbroker
communication, and add the following to broker.ini, where n designates
the acceptor number to be used for interbroker communication:
INTERBROKER_ACCEPTOR=n
SOCKET_TYPE_n=<protocol for interbroker communication>
PORT_NUMBER_n=<port for interbroker communication>
NOTE: The broker.ini parameter IB_CONFIG_SERVER is the connection string used by a broker to connect to its configuration server, and has the format: <protocol>://<hostname>:<port number>
When changing a configuration server's INTERBROKER_ACCEPTOR,
and/or the SOCKET_TYPE_n or PORT_NUMBER_n used by its
INTERBROKER_ACCEPTOR, be sure to check IB_CONFIG_SERVER in broker.ini
for each broker in the cluster administered by that configuration
server, and to make any necessary changes to its value so that it
still corresponds to the acceptor used by the configuration server for
interbroker communication.
References To Written Documentation:
Sonic Knowledge Base Solution 19870:
SonicMQ: Connecting Remote Clients Using Multiple Protocols.
Sonic Knowledge Base Solution 19697:
SonicMQ: How To Set Up a Security-Enabled Cluster.