HPE Shadowbase solutions offer sophisticated data replication, data integration, and application integration functionality for heterogeneous platforms and databases (known as “Other Servers”). The HPE Shadowbase product suite for Other Servers also meets HPE customers’ needs for continuous business operations, which require minimizing planned and unplanned downtime. HPE Shadowbase software extends its suite of replication products by supporting replication to and from a variety of platforms and databases, including Oracle, Microsoft SQL Server, and IBM Db2® source databases on most UNIX, Linux, and Microsoft Windows platforms, as well as IBM mainframe support (z/OS) for Db2 as a source.
HPE Shadowbase software is the preferred product for customers who need these advanced capabilities:
As shown in Figure 1, the HPE Shadowbase for Other Server replication products perform real-time change data capture (CDC) from Oracle, SQL Server, and Db2 source databases using either a log file extract approach or highly efficient C external routines in the Shadowbase Collector process. These changes are generated to a Shadowbase Database of Change (DOC) that serves as a stable queue for storing the transactional data to be replicated. This capability is helpful in the event the network or target environment is unavailable. Data from the DOC can be replicated to another system using a Transaction Forwarding Server (TFS) or directly into a target database on the same or other system using a Transaction Replay Server (TRS). Additionally, the TFS or TRS can also forward the DOC data into another environment (such as a real-time business intelligence system) using Shadowbase application integration solutions.
Case Study: Two Merged Retailers Integrate HPE NonStop SQL and Oracle RAC
Case Study: Winning the Battle Against Internet Banking Fraud by Leveraging Real-Time Data and Application Integration
Use Case: Prevent Fraudulent Activity for Online Banking
Use Case: Replicate and Transform Insurance Claims Data
White Paper: The Benefits of Switching from Scale-up to Scale-out Architectures