Forward Administrative Messages across Network Boundaries
Rendezvous distributed queue software depends on administrative announcements (as well as point-to-point messages) between distributed member transports.
These messages travel freely within a single network segment. However, if your network consists of several segments connected by Rendezvous routing daemons, then you must instruct the routing daemons to forward the subjects in Critical Subjects for Distributed Queues.
|
Warning |
We do not recommend sending messages across network boundaries to a distributed queue, nor distributing queue members across network boundaries. However, when crossing network boundaries in either of these ways, you must configure the Rendezvous routing daemons to exchange |
Routing daemons must forward the subjects in Critical Subjects for Distributed Queues in both directions—import and export.
Similarly, if clients in your network use TLS to connect to rvsd or rvsrd, you must configure the secure daemon to authorize the subjects in Critical Subjects for Distributed Queues.
|
Subject |
Description |
|
Rendezvous distributed queue software uses administrative messages with these subjects. Whenever potential scheduler members run in one network, and potential listener members of the same distributed queue run in a second network, then routing daemons must forward these subjects in both directions between the two networks. Similarly, whenever potential listener members of the same distributed queue run in two separate networks, then routing daemons must forward these subjects in both directions between the two networks. |
|
|
Rendezvous distributed queue software uses administrative messages with these subjects. Whenever a process in one network sends task messages to potential scheduler members in a second network, then routing daemons must forward these subjects in both directions between the two networks. |
|
|
Rendezvous distributed queue software uses administrative messages with these subjects. Whenever potential scheduler members of the same distributed queue run in two separate networks, then routing daemons must forward these subjects in both directions between the two networks. |