Routing in Unconnected Message Broker Clouds

In a properly configured Message Broker cloud, messages from all server configurations to which the subscriber is connected are routed to the appropriate Message Broker for that subscriber. However, in unconnected clouds, not all Message Brokers are aware of other Message Brokers and cannot forward messages appropriately.

You might have unconnected clouds because:

• The clouds are not properly configured.
• The clouds are intentionally configured this way, perhaps for increased security.

Suppose a client accesses two StarTeam Server configurations. Suppose that each server configuration uses a different Message Broker, and that these two Message Brokers are in unconnected clouds (see figure below). In this case, if the client chooses an MPX profile that specifies Message Broker 1 when it opens Project 1, the client receives messages for only the StarTeam Server configuration in the first cloud. The client treats the StarTeam Server configuration in the second cloud as if it did not support ActiveMQ MPX. The client performs all functions properly for such “disjoint” StarTeam Server configurations, but it does not receive the performance and instant notification benefits provided by ActiveMQ MPX.