HPE Shadowbase Queue Manager (QMGR)

long queue of impatient people waitingWhat Is It?

How is it Configured?

Why Use It?

Figure 1 shows the process and data flows in a Shadowbase replication system that has a Queue Manager (QMGR). An application posts its changes to a source database, the data changes are read by the Shadowbase Collector(s), which then prepares the data for transport. The Collector(s) forward the changes to the QMGR.  The QMGR stores the data in the in-memory cache, and buffers and writes the data to disk-based queue files in large blocks, which makes the entire system more efficient by reducing the number of write operations to disk. The QMGR’s in-memory cache passes the data to the Shadowbase Consumer(s), and the Shadowbase Consumer(s) then applies the changes to the target database. Once this process is complete, the QMGR’s disk file information, previously written in large blocks, is marked as delivered.  During this process, if the Consumer(s) is not running or unable to take the data from the in-memory cache, the QMGR will later read the data back from the disk queue file and send it to the Consumer(s) when it is ready to apply the changes into the target database.

QMGR Flow Chart - from application to target database, the QMGR sits between the collector and consumer

Figure 1 — HPE Shadowbase Queue Manager (QMGR) Flow Chart

Key HPE Shadowbase QMGR Features Include: