Book Image

IBM InfoSphere Replication Server and Data Event Publisher

By : Pav Kumar-Chatterjee, Pav Kumar Chatterjee
Book Image

IBM InfoSphere Replication Server and Data Event Publisher

By: Pav Kumar-Chatterjee, Pav Kumar Chatterjee

Overview of this book

Business planning is no longer just about defining goals, analyzing critical issues, and then creating strategies. You must aid business integration by linking changed-data events in DB2 databases on Linux, UNIX, and Windows with EAI solutions , message brokers, data transformation tools, and more. Investing in this book will save you many hours of work (and heartache) as it guides you around the many potential pitfalls to a successful conclusion. This book will accompany you throughout your Q replication journey. Compiled from many of author's successful projects, the book will bring you some of the best practices to implement your project smoothly and within time scales. The book has in-depth coverage of Event Publisher, which publishes changed-data events that can run updated data into crucial applications, assisting your business integration processes. Event Publisher also eliminates the hand coding typically required to detect DB2 data changes that are made by operational applications. We start with a brief discussion on what replication is and the Q replication release currently available in the market. We then go on to explore the world of Q replication in more depth. The latter chapters cover all the Q replication components and then talk about the different layers that need to be implemented—the DB2 database layer, the WebSphere MQ layer, and the Q replication layer. We conclude with a chapter on how to troubleshoot a problem. The Appendix (available online) demonstrates the implementation of 13 Q replication scenarios with step-by-step instructions.
Table of Contents (12 chapters)
IBM InfoSphere Replication Server and Data Event Publisher
Credits
About the Author
About the Reviewer
Preface

Summary


In this chapter, we looked at how to monitor and report on the Q replication setup. We showed how to monitor that Q Capture and Q Apply were running, how far Q Capture is behind the DB2 log, and how far Q Apply is behind Q Capture. We then went on to describe the Replication Alert Monitor and how to use monitors. We also looked at other available tools to monitor the Q replication setup, and covered the asnqanalyze command to report on the system. We then covered seven what if scenarios, and drew all of these into a summary diagram. We finally covered some performance considerations and some common Q replication error messages.

This brings us to the end of our Q replication journey. We have shown you how to plan and set up a Q replication scenario and how to monitor it. We hope that you have found the book useful and wish you every success on your Q replication journey.

The Appendix (available online) will take you through numerous examples of setting up Q replication and Event Publishing...