On this page
Supported source platforms
Choose among eight supported source platforms, grouped into data and application estates, and prepare the right source artifacts for each.
modernAIze supports SAS, Qlik, Informatica PowerCenter, SAP BW, Teradata, DataStage, COBOL, and webMethods. Choose the source platform when creating the project, then supply its scripts, exports, or definitions.
The two estate families describe how to investigate the material. Data estates center on data movement and transformation. Application estates center on program or service behavior. Read Data estates and application estates for the distinction and the questions each perspective answers.
Data estates
| Source platform | Main analysis inputs | Start here |
|---|---|---|
| SAS | SAS program source (.sas), including relevant macros and includes | SAS |
| Qlik | Load scripts (.qvs, .txt) and included script material | Qlik |
| Informatica PowerCenter | Repository XML exports and associated SQL, parameter, or definition files | Informatica PowerCenter |
| SAP BW | Extracted metadata and object definitions in JSON, packaged with their catalog | SAP BW |
| Teradata | BTEQ and SQL source (.bteq, .sql, .tsql, .td) | Teradata |
| DataStage | DSX exports (.dsx), directly or in a ZIP | DataStage |
These inputs describe how data is produced. Prepare the processing definitions and dependencies, rather than supplying only the business data produced by the source system.
Application estates
| Source platform | Main analysis inputs | Start here |
|---|---|---|
| COBOL | Program source and copybooks (.cob, .cbl, .pco, .cpy, or extensionless members) | COBOL |
| webMethods | Integration Server service and namespace definitions (flow.xml, node.ndf, node.idf, manifest.v3) | webMethods |
These inputs describe application behavior and its interfaces. Include called programs or services and shared definitions needed to understand the selected operation.
How the source artifacts are collected
| Platform | Collection route | Dedicated collection program |
|---|---|---|
| SAS | Collect program, macro, and include source files | Not required for this file-collection route |
| Qlik | Export/copy load-script text and collect included scripts | Not required for this script-export route |
| Informatica PowerCenter | Native repository XML export plus parameter and associated files | PowerCenter’s export tools |
| DataStage | Native DSX export of jobs and related definitions | DataStage’s export tools |
| Teradata | Collect SQL/BTEQ source and export database-object definitions | Native database tooling |
| COBOL | Collect/export source members, copybooks, and called programs | Source repository or mainframe export tooling |
| webMethods | Collect/export Integration Server package and namespace artifacts | Native package tooling |
| SAP BW | Extract catalog and object detail from SAP | SAP BW extraction agent, supplied for the engagement |
Each platform page distinguishes native assets (programs, jobs, services, structures, and configuration) from the files that carry them. A filename extension describes the container; it does not describe all the behavior inside.
Source files, supporting material, and packaging
Source artifacts carry the behavior to analyze. Supporting material adds context, such as parameter values, structure definitions, or a metadata workbook. Packaging groups the files for transfer. A ZIP does not make an otherwise unsupported document into a native source format.
SAS, Qlik, Informatica PowerCenter, and SAP BW also accept .xlsx workbooks as
supporting inputs. Keep the native scripts or exports as the basis of the
behavioral analysis; an Excel workbook is not a replacement for missing source.
Upload supporting workbooks separately from ZIP archives using Files or Folder;
see upload batches and limits.
The platform pages identify the main preparation requirements.
Check the result against the intended scope
After analysis, compare the expected programs, jobs, services, or objects with the represented inventory and relationships. File acceptance establishes that the material can enter the project; the available asset detail establishes how far you can investigate the selected behavior.
Use Prepare source inputs for the common handover and verification steps. A reference to an omitted routine or service remains a dependency to resolve with its owner.