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

Viewing messages using asnqmfmt


We can use the asnqmfmt command to format and view messages that are used in Q replication and Event Publishing.

Note that for Event Publishing, we must run the asnqmfmt command from the directory that contains the mqcap.xsd schema definition file (the default location is SQLLIB/samples/repl/q).

The asnqmfmt command has many parameters (shown next), but the two required as a minimum are the queue name we want to view messages for and the Queue Manager name to which the queue belongs:

  • queue_name: This parameter specifies the name of a WebSphere MQ queue whose messages we want to format, view, and optionally delete.

  • queuemanagername: This parameter specifies the name of the WebSphere MQ Queue Manager where the queue is defined.

  • ofilepath_name: This parameter specifies the name of the file that contains the formatted output. If the -o parameter is not specified, the formatted messages will be written to standard output (stdout). By default, the file is created...