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 WebSphere MQ layer


The first thing we need to check is that the Queue Managers are running. We then need to check the Listeners and Channels. Let's look at a unidirectional setup as an example. There are a number of WebSphere MQ, operating system, and DB2 commands that can be issued on each system to check the status of the various components, as shown in the following diagram:

Note that points (d) and (e) are really in the Q replication layer, but are shown here for completeness.

Checking that the Queue Managers are running

Use the following DSPMQ MQ command to display the status of a Queue Manager:

$ dspmq

We will see the following message:

QMNAME(QMA) STATUS(Running)

If we see the following message:

QMNAME(QMA) STATUS(Ended unexpectedly)

Then the Queue Manager is not active and we need to start it using the STRMQM command, as described in the Create/start/stop a Queue Manager—Starting a Queue Manager section of Chapter 4, WebSphere MQ for the DBA.

Checking the state of the Listeners

Use the...