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 Listener management


Before a local Queue Manager can send messages to a remote Queue Manager, we need to start a Listener for the remote Queue Manager. The default MQ Listener port number is 1414, and if we use this port, then we do not have to specify a port number when we issue the start listener command, but in our examples, we use port numbers other than the default. This section looks at how we manage the MQ Listeners. We will look at the different ways of defining, starting, and stopping a Listener.

Defining/Starting an MQ Listener

There are two ways of defining and starting an MQ Listener:

The first method uses the run Listener RUNMQLSR command. The parameters for the command are the type of connectivity (-t), the Queue Manager name (-m), and the port number to be started (-p). So if we want to start a TCP listener on port 1450 for Queue Manager QMA, we would issue:

$ runmqlsr -t tcp -m QMA -p 1450

This command can be put into a batch file (SYSA_QMA_START_RUNMQLSR.BAT) and in UNIX...