Customers expect responsive real-time solutions when it comes to event streaming across multiple channels. InfoCDC is a lightweight, easy-to-use, and affordable Change Data Capture solution for IBM i (AS/400) data.
Zero Code Solution
CDC solutions currently available on IBM i platform require extensive planning and implementation, specialized skills, and are rather heavy and expensive to operate.
InfoCDC is designed to be an intuitive, lightweight solution that provides core data integration capabilities at a fraction of the cost of competing products.
Supports major integration platforms
Data changes are streamed via Data Queues using native and fast IBM i objects for inter-process communications. Any middleware or target system that is capable of listening for Data Queue messages can receive CDC changes and apply them to the target systems.
Infoview connectors for MuleSoft, Kafka and other major integration platforms further simplify delivery of real-time integration and data replication solutions
Ability to configure tables and columns to replicate
Easy setup and configuration, auto-creation of all required components such as data queues, format tables, and flow definitions
Non-intrusive low system impact change detection leveraging IBM i journals
Auto-detect primary keys and unique keys and let users define custom keys for legacy files
Support is provided by our product engineering team who develop and maintain the product, ensuring fast response and resolution.
Listen for changes in specific columns and ignore irrelevant changes
Support for both commitment control (commits / rollbacks) and auto commit changes
Data Queue messages align with the IBM i Format Table data structure, passing the data in a compact, easy to deserialize, binary format
Flexible Proof of Concept Models
Letting companies evaluate on their own terms
- Upon receiving the serial numbers of the IBM i servers planned to be leveraged for the POC, a 30-day trial license will be provided along with installation documentation
- In house teams will design and implement the Kafka and MuleSoft components and IBM i configuration to their desired use case
- As always, the Infoview team will be available to answer any questions and assist with configuration or troubleshooting upon request
- For a short period of time (40 hours) a consultant will be allocated to review the POC scope and assist the involved teams.
- The scope would be small and include 1-2 simplified scenarios working end to end in a non-production environment
- Entails the creation of the desired use case in our own sandbox environment
- Once configured, results will be demoed to applicable teams with knowledge transfer sessions
Our team will
- Take complete ownership of the implementation of the involved components and corresponding architecture
- Configure DQ listeners, and target DB sync connector for a major standard DB
- Create an initial snapshot of the source IBM i tables and import them into the target database manually then turn on the replication
- Load test and transition to customer IT team for operations and expansion
- Configure DQ listeners, and target DB sync connector for a major standard DB
Configure connector with the IBM i and create flows within MuleSoft studio
- Initiate integration for a select amount of product uses cases
- Align integrations with organizational standards
- Host knowledge transfer sessions with team members taking ownership of the implemented components and integrations
Our team will
Typically, it last 2-3 months and requires a formal SOW
Frequently asked questions
Looking to increase communication from us to you
Is InfoCDC installed and run on the IBM i?Yes, the InfoCDC is installed and run on the IBM i, this is because it is journal based
Once the product is configured, is there any manual coding required to leverage the product?The only manual process involved with the InfoCDC pertains to the configuration of the product itself. Once configured, the product monitors for DB2 changes automatically and then streams to target API’s as defined by the user.
How does the product capture the change on the selected table on DB2?Via journal files on the IBM i
Once InfoCDC is installed on an IBM i server, is auto-discovery enabled on the server?At this point, manual process – focus is not so much replicating database or entire server, but to replicate a subset of tables and maybe tables a subset of data that would make more sense from an application perspective
Does the Infoview team offer POC’s to customers?Absolutely! Our service team is here to assist with product configuration, first use case implementation, and can also assist with defining tables, full installation of prod in sandbox/non-prod, and as well as corresponding connector configurations to ensure everything works from the IBM i perspective.
Does InfoCDC require timestamps on the table?Time stamps are not required, as the product is not polling periodically based on time stamps. InfoCDC connects directly into DB2 journals, almost like Kafka persistently logs data and events, whenever a change happens, one or more entries are pushed into a journal that immediately is made available for a process on our end
How Much CPU or memory is needed for the InfoCDC to run on the IBM i?Overall, implementation will be relatively easy touch on IBM i system performance. Listening happens with a specific job, per journal, on IBM i compared to trigger solution. Very lightweight compares to filtering criteria and then sends to a data queue to external systems. In summary, largely depends on all components of systems, jobs, and processes (in the system).
Why did Infoview choose to invest in a CDC-based product?There are several products on the market focused on mass-scale replication, but are often heavy, expensive, and not easy to implement. We envisioned this product as a lightweight, easy-to-use alternative, that’s more accessible and requires less time to implement .
Must the InfoCDC be leveraged with an existing Infoview connector?The way the InfoCDC was developed, it expects a consumer to be listening to its outbound interface (currently, it’s a data queue with an associated format table). When bundled together, Infoview’s products are highly complementary and supported by our in-house team members.
Subscription Models, Delivery, and Support
Based on the number of physical IBM i servers and is linked to server serial number(s). A single server license applies to all LPARs (logical partitions) defined on that server at no additional cost.
Available in annual, three-year, and enterprise5 subscriptions. In addition, we also offer a cost-free evaluation license. Please reach out to the Infoview team for additional information.
Product licensing is available directly through Infoview Systems
Available during the regular business day, between 8:00 a.m. and 5:00 p.m. Eastern Time Zone or India Time Zone, Monday through Friday, excluding United States public holidays.
Available for product implementation, configuration, POC guidance, and system integration.
Ease of Use
Eliminate the need to capture and replicate database updates manually, while leveraging a user-friendly interface that does not require extensive training.
Data monitoring and copying rules
Adding a new data monitor can be done by simply stating a new control consisting of table level, row-level, and column level metadata. Furthermore, when a custom rule is created on the IBM i server, the InfoCDC maintains the rule when replicating data to another application.
Transferring Data from tables
Hassle free replication/ preventing inconvenient replication/ no more troublesome post-replication/ deliver only the desired replication / delivering only desired information
To increase efficiency, you can pick the desired column on a table to transfer data from, preventing the need to transfer a whole table for only a select amount of data.
InfoCDC was designed to work alongside a listener. Paired with our suite of AS400Gateway connector products including the MuleSoft or Kafka Connector, the product listens for database changes and streams them to their final distention in near real-time, enabling complete integration solutions with zero coding required.
An agile application
InfoCDC was designed as a lean system aiming to cause only a light usage of system resources when deployed on an IBM i server.
Integral part of a package
The InfoCDC was designed to work alongside a listener, such as MuleSoft/Kafka, a stand CDC component could be developed but would still require an external listener to make a complete product. This could be a data queue reader residing on an external IBM i system either homegrown by the client or developed by a third party.
New Data Monitoring
Adding a new data monitor can be done by simply starting a new control consisting of the table level, row level, and column level metadata, allowing users to monitor exactly what they want to monitor.
Formatting data copying rules
When a custom rule is created on the IBM i server, InfoCDC maintains this rule when replicating data to another application.
Helpful documentation and demonstration examples
Copyrights © 2022 by Infoview Systems Inc.