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

The control tables


For Q replication to function, it needs to store information about its Replication Queue Maps and Q subscriptions in control tables, located on the source and target servers.

The control tables are called <schema>.<table-name>, where <schema> defaults to ASN. Some of the control tables are user updateable, and others are internal tables that should only be updated by Q Capture and Q Apply.

In the following table descriptions:

Column descriptions marked with (97) at the end are columns new in DB2 9.7 compared with previous releases of DB2.

We use the following nomenclature:

CHAR means CHARACTER, NNWD means NOT NULL WITH DEFAULT, VCHAR means VARCHAR, INT means INTEGER, NN means NOT NULL, and FBD means FOR BIT DATA.

Note

Not all the control tables are initially created for each scenario, for example, the IBMQREP_EOLFLUSH control table is only created for replication from an Oracle source (new in DB2 9.7.1).

The Q Capture control tables

In this section, we look at...