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.
This book will accompany you throughout your Q replication journey. It 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.
In this book, 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 real-time Q replication scenarios with step-by-step instructions.
Chapter 1, Q Replication Overview, describes why we want to replicate data and what is available today in the IBM world of data replication. It introduces the architecture of Q replication and different types of Q replication available and discusses various DB2 replication sources including XML data and compressed data, and looks at filtering and transformations.
Chapter 2, Q Replication Components, discusses three layers—DB2 database layer, the WebSphere MQ layer, and the Q replication layer that make up a Q replication solution and also showed the relationship between Replication/Publication Queue Map, Q subscription, and subscription group.
Chapter 3, The DB2 Database Layer, looks at creating the databases used in Q replication, the Q replication control tables, and their structure.
Chapter 4, WebSphere MQ for the DBA, illustrates the working and setup of WebSphere MQ.
Chapter 5, The ASNCLP Command Interface, illustrates the working and setup of the ASNCLP Command Interface, guides you through some of the Q replication setup tasks, and shows you how to perform them using ASNCLP commands.
Chapter 6, Administration Tasks, focuses on the administrative tasks that we need to perform to set up and administer a Q replication environment.
Chapter 7, Monitoring and Reporting, looks at monitoring and reporting on the Q replication setup. It also describes the Replication Alert Monitor and how to use monitors.
Appendix A, Setup Procedures: Steps to Follow, describes the tools available to set up Q replication, goes through various scenarios, and gives step-by-step instructions. This can be downloaded from http://www.packtpub.com/sites/default/files/downloads/1544_Appendix.zip
In the course of this book, you will need the following software utilities to try out various code examples listed:
InfoSphere Replication Server 9.7.1
WebSphere MQ V6.0 or V7.0
If you are a professional who needs to set up and administer a Q replication or Event Publishing environment, then this is the book you need. The book will give you a clear understanding of how to implement Q replication. The examples are based on a Linux, UNIX, or Windows operating system, but the principles are equally applicable to Q replication on z/OS.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: "A target database is created using the DB2 script file as shown next."
A block of code is set as follows:
CONNECT RESET; DROP DB db2b; CREATE DB db2b; UPDATE DB CFG FOR db2b USING logarchmeth1 disk:c:\temp; BACKUP DATABASE db2b TO c:\temp;
When we wish to draw your attention to a particular part of a command-line block, the relevant lines or item(s) are set in bold:
SUBNAME S STATE_TIME
---------- - --------------------------
T10001 A 2006-02-22-18.32.22.112000
T10002 I 2006-02-22-18.22.14.468000
T10003 I 2006-02-22-18.22.14.478002Any command-line input or output is written as follows:
$ db2 "select substr(subname,1,10) as subname, state as S, state_time from asn.ibmqrep_subs"New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "There is also a Sample entries button, which will give us some default queue names.".
Note
Tips and tricks appear like this.
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or e-mail <[email protected]>.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Note
Downloading the example code for this book
You can download the example code files for all Packt books you have purchased from your account at http://www.PacktPub.com. If you purchased this book elsewhere, you can visit http://www.PacktPub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.