General Page
Moving Db2 changed data to Netezza
The Event Publishing Format
EP captures data from the DB2 transaction log and writes it to a Websphere MQ queue. It supports 2 formats:
- A delimited format where transaction information - table row, column values, etc. - is separated by delimiters, most often commas.
- An XML format where transaction information is enclosed in self-described tags in an XML document.
Sample Event Consumer to Update Netezza
- Overview - Updating Netezza with DB2 Changed Data Using Event Publishing
- Sample code - asnconsumer.zip
Final Note on Event Consumers
Queues are not the only way of publishing data. It can also be published to tables.
For example, CCD, or Consistent Change Data, tables hold changed data in a format easily consumed by applications through SQL. A popular use-case is the multi-tier distribution scenario where tier-1 is the production system, tier-2 is a mid-tier consolidation server with CCD tables populated with tier-1 changed data (no Capture process is running on tier-2) and tier-3 servers are regional servers where Apply processes pull the appropriate changed data from tier-2 CCD tables.
Event publishing combined with specialized event consumers delivers simple solutions for integration scenarios.
Related Information
Was this topic helpful?
Document Information
Modified date:
07 April 2020
UID
ibm11105185