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

MQ Channel management


This section looks at how we define, stop, start, and display the status of WebSphere MQ Channels. For each local Queue Manager, we need a Sender Channel and a Receiver Channel, both of which need a matching pair on a remote Queue Manager.

To define a Channel

In the following figure, on the left-hand side, we are on QMA and define two Channels:

  • A Sender Channel called QMA.TO.QMB, which uses the Transmission Queue QMB.XMITQ and points to the remote WebSphere MQ system at IP address 127.0.0.1, which is listening on port number 1451 (which is QMB).

  • A Receiver Channel called QMB.TO.QMA, which is used to receive messages (from QMB in this case).

There are corresponding Sender and Receiver Channels defined on QMB. Note that the pair of Sender and Receiver Channel names on both QMA and QMB must be the same, so the Receiver Channel on QMB must have the same name as the Sender Channel on QMA.

To start a Channel

There are four ways of starting a Channel, the choice depending on your...