ADABAS SQL GW is
Non a Sacrificial Gateway to ADABAS!
Active Data Warehousing
With ADABAS SQL GATEWAY
Nikolai Chmatov
Manager, Tactical Solution, Market Product & Services October 16, 2012
Table of Contents
Slide 3
What was Before?
Slide 4
What was the Target?
Slide 5
Active Data Warehousing vs Traditional Data
Warehousing
Slide 6
Business Value of Data Freshness
Slides 7-8
WHY the ADABAS SQL GATEWAY?
Slides 9-17
HOW was it done?
Slides 18-19
What Else?
What was Before?
Traditional Data Warehousing (TDW)
Traditional Data Warehousing is –
an integrated & logically consistent store of detailed data used to aid the decision making process.
Little to no interaction with customer or supplier channels Primarily batch data feeds (one way data flow)
Variety of the “predefined” non customizable reports…
WHY
Active Data Warehousing?
WHY with
ADABAS SQL GATEWAY?
ADABAS
Operational and/or Transactional System (s)Traditional
Data
Warehouse
Batch
What was the Target?
Active Data Warehousing (ADW)
Active Data Warehousing is traditional DW plus very current
detailed data (combined with historical data) for strategic, tactical and event-driven business decision making.
Timely updated – (Real Time/Good Time)
Pre-designed triggers and queries to detect significant events Event-based Notification Service (ENS)
Ability to use bi-directional data flows
Decision Assistance (via analytic applications). Tracking of tactical decision and actual result.
ADABAS
Operational and/or Transactional System (s)Active
Data
Warehouse
Batch
ENS
Continuous- Initiate external Process - Update Database - Notify Ops. (e-mail)
@
WHY
Active Data Warehousing?
Active Data Warehousing vs Traditional Data Warehousing
•
Strategic Decision Making
Active data warehousing moves all analysis into the database to answer complex business questions quickly and with scalability...
Businesses need to perform analysis for planning, forecasting, profiling, fraud detection, trending, and pattern analysis to identify the proper action based on business drivers.
•
Tactical Decision Making
Active data warehousing is also about to supplying information to front-line decision makers...
Businesses need repeatable, consistent execution of data-driven decision by all constituencies,
Business Value of Data Freshness
What is the relationship of data freshness to business value?
Consider the following Value-Time Curve.
The real situation may be
more complex, as shown
in the following figure.
Value action taken business event Time Value Action Taken business event Time Information delivered data stored action distance
• Oracle CDC Adapters (Adabas & VSAM)
• Pros - Publish-and-Subscribe Model
• Cons - CDC adapters are integrated by the Oracle Application Server
- Too many components and platforms
• TIBCO Object Service Broker (Adapters for Adabas & VSAM)
• Pros – Good for stabile process (TDW but not ADW)
• Cons – TIBCO Object Service Broker’s rules engine is an external process written in assembler, COBOL, PL1/1, CICS,
C, etc
- SDKs are available for use with 3rd generation programming languages including Java, C, and C++. - These adapters provide performance by capturing changes directly from the database logs.
• iWay Software's Intelligent Adapter (Connectors for Adabas & VSAM)
• Pros – Third-party products can also access the adapter via iWay connectors, including ODBC, OLE DB, JDBC
• Cons – All dictionaries are on Mainframe side and any changes in data definition will required re-compiling entire
dictionary and re-link it with the Connector.
• SOFTWARE AG/CONNEX ADABAS SQL Gateway
• Pros – imports Predict data dictionaries or Natural DDMs or/and imports Adabas metadata directly from Dynamic DDL
and FDT into a CONNX Data Dictionary file (CDD). – creates virtual tables to represent MU and PEs
– single metadata model that efficiently spans all enterprise data sources – Third-party products can also access ADABAS data via ODBC, OLE DB, JDBC
• Cons – Poor user interface
•
“Regular” or Traditional Data Warehousing
Daily (overnight) data refreshing
Predefine queries & reports
Mainly distribution via e-mails or via DW Front-End
Very minimal ability of ad hoc queries & reporting
•
Business requirements
Operates with real data on a real-time or good time base with the
core business applications
Be able to create ad hoc queries & reports
Be able to monitor data or/and event changes
Be able to run all existing reports
Be able to capture some particular data events
Be able to update data on certain conditions
Without Action, there is no Benefit
Users need convert data into information (Grids, Pictures, Graphs, Trends…)
Get the Information to People Who Need It Aggregation, Reconciliation,
Calculation, Cases, Rules
Logical Views (Combining External & Internal data into one logical View) Data Collection from Inside and Outside of company
Classical Data/Knowledge Pyramid
Gather
Assign Context
Analyze
Distribute
Visualize
Act
ADABAS
Operational and/or Transactional System (s)Traditional
Data
Warehouse
Batch
Oracle & PowerBuilder
Views & Historical tables MS Windows Server 2003 ADABAS SQL GW MS SQL Server IBM iSeries Access Oracle Call Interface
ADABAS
Operational and/or Transactional System (s)Traditional
Data
Warehouse
Batch
Oracle & PowerBuilder
HOW was it done?
•
ADABAS Database defined at MS SQL Level
as a Linked Server
•
ADABAS Database defined at MS SQL Level
as a Linked Server
•
Starting from MS SQL Server 2005
we can use “CONNX OLE DB Provider”
driver directly when SQL 2000 can work
only with MS OLE DB provider for ODBC
•
ADABAS Database defined at MS SQL Level
as a Linked Server
•
Starting from MS SQL Server 2005
we can use “CONNX OLE DB Provider”
driver directly when SQL 2000 can work
only with MS OLE DB provider for ODBC
•
Make sure that you’ve got
a right “Server Options”
•
ADABAS Database defined at MS SQL Level
as a Linked Server
•
Starting from MS SQL Server 2005
we can use “CONNX OLE DB Provider”
driver directly when SQL 2000 can work
only with MS OLE DB provider for ODBC
•
Make sure that you’ve got
a right “Server Options”
•
Do not forget “Security”!
•
ADABAS Database defined at MS SQL Level
as a Linked Server
•
Starting from MS SQL Server 2005
we can use “CONNX OLE DB Provider”
driver directly when SQL 2000 can work
only with MS OLE DB provider for ODBC
•
Make sure that you’ve got
a right “Server Options”
•
Do not forget “Security”!
•
And at the end, after all of the above –
ADABAS Database can be accessed
as a regular SQL View or Table
from any SQL-based tool.
But in fact - the right way is the way which is working!
There are so many ways of doing it…
There are so many stories telling how…
Nikolai Chmatov
Manager, Tactical Solution, Market Product & Services October 15, 2012
+1 416-918-3466
Adabas and Natural Sessions for Process World 2012
Time Slot
Adabas and Natural Track Presentations
Tuesday, 10/16 11:15 – 12:00
Managing DMV Pictures & Signatures with Adabas Large Object (LOB) Fields – State of South Dakota
Tuesday, 10/16 1:30 – 2:15
Active Data Warehousing Made Easy with Adabas SQL Gateway – Royal Bank of Canada
Tuesday, 10/16 2:30 – 3:15
Achieve Significant Quality Improvements by using Better Test Data with Data Masking for Adabas – Pennsylvania State University
Tuesday, 10/16 3:30 – 4:15
What’s next for Adabas and Natural? The Strategic Direction – Software AG
Tuesday, 10/16 4:30 – 5:15
Case Study – FSCJ: College Inventory Management using a Mobile Application
Wednesday, 10/17 11:15 – 12:00
Adabas Replication: How we do it at NYC DoITT – New York City Department of Information Technology
Wednesday, 10/17 1:30 - 2:15
EntireX Broker Centralizes Drivers License Management State-Wide – State of Virginia
Wednesday, 10/17 2:30 - 3:15
Natural Remote Data Collector (RDC); Monitoring and much more – State of Washington Retirement System
