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

Q replication performance considerations


Now let's move on to look at some Q replication performance considerations. Our Q replication environment is made up of four components:

  • The DB2 database layer comprising the source and target databases

  • WebSphere MQ

  • Q Capture

  • Q Apply

Let's look at tuning each of these components.

The DB2 database layer

The DB2 source or target databases: The tuning that should be performed for the DB2 databases is normal tuning that we would do for any database. The only point to bear in mind is that the amount of DB2 log space required may increase due to DATA CAPTURE CHANGES being set. There are no other special considerations if the databases are involved in Q replication.

We may need to run RUNSTATS and REORGS on the replication control tables—these tables should be treated as any other application table.

The WebSphere MQ layer

We have mentioned the MAXDEPTH parameter for queues (Refer to the MQ Queue management—To define a Local Queue section of Chapter 4), and if we increase...