Replace Attunity Replicate with HPE Shadowbase Off and/or On-platform Data Integration

1. The remote query tool started to interfere with the NonStop processing and the tool was reaching its End-Of-Service-Life (EOSL).
2. The report processing needed to heavily transform the non-relational Enscribe database information into a usable format, and also required re-transmission of the data across the network for each report run. In other words, every time the report was requested, the same processing had to occur to the same data over and over and over.
3. This architecture is sensitive to network activity and load, and produces a lot of CPU overhead, in particular on the production environment.
4. In addition, the volume of reporting was growing quickly and the manufacturer’s operations relied on this querying and reporting process.
   • If you want to see volumes of reporting grow, show a manager a report that shows important information, and every manager in that department will also want to see the same thing – on demand.
5. The reporting application used a non-standard interface to the NonStop database. This created a barrier for the customer leveraging some of the more advanced applications for processing and analyzing data.
6. The application also needed to share the results of this additional processing, the Online Analytical Processing, back with the NonStop environment in order to optimize shop floor control.

Solution

• Use HPE Shadowbase Essentials, in particular, the SBDDLUTL Utility, to map the Enscribe DDL into equivalent target SQL (or HPE NonStop SQL/MP or SQL/MX) schema formats
  • This Utility extracts the DDL definitions from the Enscribe DDL catalog, and generates the SQL CREATE TABLE statements in the target SQL environment’s format.
  • Then, DBAs can simply run the SQL CREATE TABLE statement on the local HPE NonStop server (SQL/MP or SQL/MX), or to a remote “Other Server” (in any supported target SQL format).
• Use HPE Shadowbase Data Integration to perform an online load of the source data to initially populate the (off or on-platform) target database, without requiring an application outage.
• Then, use HPE Shadowbase Data Integration to keep the target database synchronized with additional changes from the source by reading the TMF audit trails, and transforming and replicating the changes down into the target SQL database.