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

Copying (promoting) Q replication environments


What do we mean by copying (or promoting) environments? Well, suppose we have developed a replication solution on a test machine and now want to build a similar solution on a production machine—we have two choices: if we have built the test solution using ASNCLP scripts, then we can just move these scripts over to the production machine, edit them to reflect the new schema, database names, and so on and then run them there. The point to watch out for with this approach is that the scripts have to be complete—what happens if something has been changed, which has not been reflected in the ASNCLP scripts! The second option is to use the promote functionality of the ASNCLP commands, which we will discuss next.

The ASNCLP PROMOTE procedure

Let's look at promoting a unidirectional setup from a test environment to a production one. We have replication set up between DB2A and DB2B on test and want to move this to DB2C and DB2D on production.

We will issue...