Creating and operating a heterogeneous network

You can integrate your existing MQSeries Publish/Subscribe broker network with a WebSphere Business Integration Event Broker broker network to create a mixed, heterogeneous network. This enables publications and subscriptions to be propagated through one logical network, made up of two or more physical networks. As a result, subscribers to the MQSeries Publish/Subscribe brokers can target information being published to the WebSphere Business Integration Event Broker broker network, and subscribers to the WebSphere Business Integration Event Broker brokers can target information being published to the MQSeries Publish/Subscribe broker network.

MQSeries Publish/Subscribe brokers and WebSphere Business Integration Event Broker brokers can be running on Windows or other platforms.

There are two ways in which a WebSphere Business Integration Event Broker broker can be joined to the MQSeries Publish/Subscribe network; it can be joined either as a leaf node (that is, as a child of an existing MQSeries Publish/Subscribe broker) or as a parent node (that is, as the parent of an existing MQSeries Publish/Subscribe broker).

Every WebSphere Business Integration Event Broker broker that you integrate into an MQSeries Publish/Subscribe network must have a minimum of two queues available:
  • SYSTEM.BROKER.DEFAULT.STREAM

    This queue supports the default publication stream. You must create this queue on every broker. You must also create and deploy a message flow that services this stream queue.

  • SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS

    This queue is used by the broker to communicate with neighboring MQSeries Publish/Subscribe brokers. You must create this queue on every broker, however the message flow for this queue is created internally by the broker.