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

Monitoring using the Replication Alert Monitor


We can use the Replication Alert Monitor (RAM) to monitor the state of our replication environment.

The Replication Alert Monitor is a program, which comes bundled with the replication code which checks the status of various replication objects and reports on these.

The Replication Alert Monitor control tables are described in the The control tables The Replication Alert Monitor control tables section of Chapter 3, but the question that we need to answer is, where do these control tables go. We can put them on the same server on which Q Capture is running, or the same server on which Q Apply is running, or they can be placed on a totally different server, as shown in the following diagram. Here we have a monitoring server called MONDB and two monitored servers called DB2A and DB2B.

Before we look at setting up the Replication Alert Monitor, let's first look at the Q Capture and Q Apply conditions that we can monitor.

Running Alert Monitoring is...