Bridge Specifications
| Vendor | IRI, Inc. (CoSort) |
| Tool Name | CoSORT RowGen |
| Tool Version | 8.2 to 9.x |
| Tool Web Site | http://www.cosort.com/products/rowgen |
| Supported Methodology | [Data Integration] ETL (Source and Target Data Stores) via DDF Text File |
SPECIFICATIONS
Tool: IRI, Inc. (CoSort) / CoSORT RowGen version 8.2 to 9.x via DDF Text File
See http://www.cosort.com/products/rowgen
Metadata: [Data Integration] ETL (Source and Target Data Stores)
Component: IriCoSortRowGen version 11.2.0
OVERVIEW
This bridge generates a text file in SortCL DDF format for immediate or centralized use in RowGen data generation and custom file synthesis operations. Test files produced in RowGen can be used to populate ETL and DB tools in the same form and format as real files, without compromising the security of real data.
REQUIREMENTS
The current bridge only supports flat flat file layouts for RowGen output files, but does not produce the metadata for detailed manipulations on synthesized data which RowGen supports.
RowGen runs on all UNIX, Linux and Windows platforms with the command:
rowgen /SPECIFICATION=jobname.rcl
Where jobname.rcl is a cross-platform-compatible text file defining the creation of one or more formatted files containing randomly-generated or randomly-selected (from set file) field elements.
You can paste .DDF descriptions of input and output files directly under the /INFILE and/or /OUTFILE sections of a RowGen job script, or incorporate them by reference in any RowGen (or CoSORT SortCL ) application with the /SPECIFICATION=metadatafile.ddf. For details on RowGen, see: http://www.cosort.com/public/solutions/rowgen/rowgen.htm.
See also: CoSORT (SortCL) Data Definition File (DDF) Export Bridge.
FREQUENTLY ASKED QUESTIONS
n/a
LIMITATIONS
Refer to the current general known limitations at https://www.metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||
| Directory | Defines folder where to write resulting output files (one per table). | DIRECTORY | Mandatory | |||||
| File prefix | Outputs one file per Class in the source model. Each file name is matching the original Class name. You can define a common file name prefix for all files by this option. | STRING | ||||||
| Export non-file classes as | Defines a rule on how to export classes that were created from other than flat files sources. You can choose not to export them at all or you can pick a format from the list. If you choose to use 'Delimited files', make sure you specify appropriate delimiter by 'Delimiter text' option. |
ENUMERATED |
|
Do not export | ||||
| Delimiter text | Defines a delimiter text for a delimited file export. This option is used only if 'Delimited files' value is set for the 'Export non-file classes as' option. |
STRING | , |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) |
"IRI CoSORT RowGen Data Definition File" Metamodel IriCoSort |
Mapping Comments |
| Attribute | /FIELD | |
| Comment | # Comments in the DDF file | |
| Description | # Comments in the DDF file | |
| Name | field name (if physical name is not specified) | |
| PhysicalName | field name | |
| Position | Ouput is sorted by position | |
| DataType | Data Type name | |
| Length | Field length | |
| Scale | Field scale | |
| Class | /FILE | Only FlatFiles classes are exported. |
| Comment | # Comments in the DDF file | |
| Description | # Comments in the DDF file | |
| Name | File name (if physical name is not specified) | |
| PhysicalName | File name | |
| PropertyType | Used to extractorigin specific flat file metadada | |
| PropertyValue | Used to extractorigin specific flat file metadada |