Language: Cantonese
Format: Technical sharing, TapData walkthrough, and Q&A
IBM i systems continue to support many business-critical operations, while analytics platforms, modern databases, APIs, and digital applications increasingly require access to the data held in these core systems.
Repeated batch exports, direct database queries, and custom point-to-point integrations may work for individual requirements, but they can become difficult to maintain as the number of downstream consumers grows.
In this practical technical session, we will introduce the concept of Db2 for i data offloading, discuss where a CDC-based approach can help, and walk through how TapData can deliver continuously changing core data to modern downstream systems.
What you’ll learn
Why organizations offload Db2 for i data, and where direct queries, batch exports, and custom integrations may become limiting.
A practical data-delivery pattern for making IBM i data available to modern databases, analytics platforms, APIs, and applications.
How a CDC-based offloading flow can continuously capture and deliver source changes without requiring downstream systems to repeatedly query the core.
How TapData can be used to configure, run, and monitor an IBM i data-offloading flow through a short practical walkthrough.
Session outline
- 1.Why offload data from IBM i? Common scenarios where IBM i data is needed by analytics, reporting, modern databases, APIs, and digital applications—and why repeated access to the core can become difficult to scale.
- 2.Common approaches to IBM i data delivery A brief comparison of direct database queries, scheduled batch exports, custom integrations, and CDC-based offloading.
- 3.A practical Db2 for i offloading pattern A reference data flow for continuously delivering IBM i data to modern downstream systems while reducing repeated access to the core.
- 4.TapData implementation walkthrough How an IBM i source, a modern target system, and a continuous data flow are co