You can have multiple brokers in your record and replay topology. If you use different brokers for deploying your message flows and for recording data captured from those message flows to a database, then you must configure a publish/subscribe relationship between the brokers.
Read the concept topic Record and replay.
Data capture is based on a publish/subscribe model. You configure monitoring on message flows that you have deployed to a broker, for example, to broker MONBKR. MONBKR publishes to the topic that you specify when you configure your monitoring events. The topic identifies the source of the data that you want to capture. You specify this topic in your DataCaptureSource configurable service.
You define a DataCaptureStore configurable service where you specify the integration server to use for processing the captured data, egForRecord. The broker that you use to create the DataCaptureStore configurable service, RECBKR, subscribes to the monitoring topic. The subscription messages that this broker receives are processed by egForRecord and recorded to the data source specified in the DataCaptureStore configurable service.
You must use the same broker to create the DataCaptureStore and the DataCaptureSource configurable services.
In this scenario, MONBKR publishes on the monitoring topic and RECBKR subscribes to the topic. If MONBKR runs on queue manager MONQM and RECBKR runs on queue manager RECQM, then you need to configure a publish/subscribe relationship between MONQM and RECQM.
You can choose to create either a cluster or a hierarchical publish/subscribe relationship between the two queue managers. If you plan to add queue managers to your topology frequently, then a cluster relationship is more appropriate. See the topics on "Publish/subscribe topologies" in the WebSphere® MQ Version 7 Information Center online. This example uses a hierarchical relationship. In the example, values enclosed in single quotation marks can be replaced with your preferred values, but keep the quotation marks if you use lowercase characters. Complete the following steps:
Next:
Consider the performance implications of your record and replay topology; see Tuning data capture.
Complete the steps for recording data; see Recording data.