240 likes | 436 Views
A Global Leader in Data Migration, Replication, and Integration Solutions. Agenda. tcVISION Overview Architecture Metadata & Modeling Replication tcVISION Demo Q & A. Mainframe Data Replication and Integration without Compromise. Different data formats Different data models
E N D
A Global Leader in Data Migration, Replication, and Integration Solutions
Agenda • tcVISION • Overview • Architecture • Metadata & Modeling • Replication • tcVISION Demo • Q & A
Mainframe Data Replication and Integration without Compromise
Different data formats Different data models Large data volumes Limited batch window Requirement for up-to-date information Moving/replicating data... as much as needed as little... as transparent... as flexible... as secure... ...AS POSSIBLE Data Replication The Problem: TheSolution: ...with
tcVISION Overview • Innovative software solution to process changed data • Automatically identifies changes and files • Continuously propagates the changed data to target systems in real-time or time intervals • Offers a rich set of processing and control mechanisms • Contains powerful bulk processors for initial load of mass data or the cyclic exchange of larger data volumes • Efficient, fast and reliable • Supports multiple datasources – Oracle, SQL Server, DB/2, IMS/DB, VSAM, DL/I, ADABAS, IDMS, DATACOM, Flat File
Control Board • MS Windows GUI Interface • Single and central point of administration • View manager and transaction logs • Built-in Wizards for mapping and modeling metadata • Script Generation for bulk transfer and replication • Monitoring • Replication status • Script output • DBMS extensions
Wizard-Assisted Metadata Import • Copy Books • VSAM file layout • IMS/DLI Segment layout • PS/PDS/SAM file layout • IMS DBD, PSB • Segment hierarchy • Key information • Dictionaries • ADABAS PREDICT • CA-DATACOM • Schema definitions • CA-IDMS
Mapping & Modeling • Metadata import supported for ADABAS, DATACOM, DB2, Copybooks, IDMS, MySQL, ODBC data sources, Oracle, SQL Server, and tcACCESS data sources • Automated generation of normalized RDBMS schemata with explicit source column to target column mapping • Robust modeling and mapping via wizards – normalize, denormalize, substring, concatenate, filter, table lookup, user-exits, operators (+, -, *, /), date/time • All mapping information stored in a RDBMS-based metadata repository
Designed for Bi-Directional Replication • Replicate to non-RDBMS databases’ native schema, no schema changes required for target mainframe databases (ADABAS, DATACOM, DB/2, IDMS, IMS & VSAM) • Sample table replication scenarios: • 1:1 Replication • 1:n Replication with no dependencies • 1:n Replication with dependencies (OCCURS and MU/PE) • n:1 Replication with no dependencies • n:1 Adjunction replication (source Parent & Child table(s) • n:1 Combination replication • n:n Replications
Support for Complex Replication Scenarios n:1 1:1 1:n n:n • Also special cases: • Data Warehouse Replication • Journal Replication
Multiple CDC Methods Data Latency Data Transfer Volume
Multiple CDC Methods • Efficient transfer of entire databases • Analysis for data consistency (verification) • Initial load (ETL) and periodic mass data transfer • One-stepdata transfer • IMS/DB, DL/I, VSAM, DB2, Oracle, SQL Server, ADABAS, CA-IDMS, CA-DATACOM, sequential files, ODBC • Transfer of changed data in scheduled time frame • Generally batch-type process • Generally run immediately after archive log creation • IMS/DB, VSAM, DB2, DL/I, Oracle, SQL Server, ADABAS, IDMS, CA-DATACOM, CICS logs • Comparison of data snapshots using checksums • Efficient transfer of changed data since last processing • Flexible processing options (SORT etc.) • Automatic creation of deltas by tcVISION • IMS/DB, DL/I, VSAM, DB2, Oracle, SQL Server, ADABAS, CA-IDMS, CA-DATACOM, sequential files, ODBC • Real-time capture of changed data directly from the DBMS • Secure data storage even across DBMS restart • Flexible propagation methods • CA-IDMS, IMS/DB, VSAM, DB2, CA-DATACOM, ADABAS, Oracle, SQL Server
Staged Processing Stage 3: Data in DML or Loader format Exit pointsavailable at every stage Stage 2:Data normalized with structure definition Stage 1:Data in tcVISION format (before and after images) Stage 0:Data in internal raw format
tcVISION - Flexibility • User defines on WHICH platformstage processing should be done • Normal implementation: Do as little as possible on the mainframe • Mainframe: Capture data; Send data (internal format) to target (Stage 0) • Receiving machine: Process data up to Stage 3
Cost Savings • Use Staged Processing to reduce mainframe resource consumption • Minimum processing on the mainframe – only what is essential • Process all DBMS Journal and Log datasets on Open System • Data Transformation is carried out on target platform – Open System; e.g., • Data converted from mainframe data types to relational data types • Generation of SQL / SQL Loader files • Date-time formatting • EBCDIC-ASCII translation
tcVISION – ADABAS CDC • Real-time CDC – captures the Adabas CLOG using Adabas UEX4 & UEX8. tcVISION uses a Data Collector & Data Pool to collect & temporarily store the CLOG records until they are ready to be processed • Batch CDC – uses the Adabas PLOG • Efficient – tcVISION reads the CLOG & PLOG and only transfers transactions for Adabas files defined to tcVISION. All other transactions are ignored. • Using Staged Processing, transformation of CLOG & PLOG data is performed on open systems, which saves mainframe CPU & DASD
tcVISION – Oracle CDC • Uses ORACLE REDO Logs • 'Single Instance Mode' supported for 10.1, 10.2 and 11.1 • Log processing may not be on the same processor where the database is running • may not be on the same archticeture (Little/Big Endian machines) • may not be on the same operating system(Windows, UNIX, LINUX)
tcVISION – Oracle CDC • SCN– System Change Number • This is a sequential counter, identifying precisely a moment in the database. This is the most accurate way to identify a moment in time. • tcVISION Control Board can be used to display current SCN • PROLOG script can be used query current SCN from ORACLE and pass to tcSCRIPT • Using RESTART FILES a "running SCN" is automatically maintained