Summary

This chapter focused on the administrative tasks that we need to perform to set up and administer a Q replication environment. We started by looking at how we define the WebSphere MQ queues and the Q replication control tables. We moved on to look at Q subscription maintenance tasks, such as creating, altering and dropping a Q subscription. We then looked at how we should handle source table maintenance, where we covered adding and removing columns from a Q subscription. Next, we looked at administering the Q Capture and Q Apply programs, and when we need a password file. Finally, we looked at how to promote a Q replication environment from a test system to a production system.

In these six chapters, we have covered the building blocks that are needed for Q replication. We bring this all together in Appendix A, which covers setting up different scenarios from the simplest unidirectional scenario to a scenario involving peer-to-peer four-way replication.

Before we look at the examples...