Catalog Administrator Guide > Registering Unknown Data Types for Profile Run > Registering an Unknown Data Type as a Supported Data Type
  

Registering an Unknown Data Type as a Supported Data Type

In Enterprise Data Catalog, you can register unknown data types as varchar data type. The profiling scanner uses the registered data types for columns that have unknown data types.
    1. Unzip the catalogMapping.zip file located in the <Enterprise_Data_Catalog Installation Directory>/services/CatalogService/ScannerBinaries path in the Enterprise Data Catalog installation directory.
    The ZIP file contains a sample catalog-mapping.xml file.
    2. Open the catalog-mapping.xml file.
    The XML file contains the following XML elements:
    XML Element
    Description
    <CatalogMapping>
    </CatalogMapping>
    Root XML element.
    <Connection>
    <Name>
    </Name>
    </Connection>
    Enter the data type mapping information for a relational source. You can enter a generic connection type, such as ODBC or relational database-specific connection type, such as Oracle.
    <source>
    <Name>
    </Name>
    </source>
    If you enter the generic connection type, you must enter global for all the relational databases that you can use for mapping. For database-specific connection type, enter the name of the relational database. For example, for Oracle connection type, enter Oracle as the source database value.
    <ExcludeDataTypes>
    </ExcludeDataTypes>
    Enter the data type that you want to exclude from mapping.
    <ColumnDataTypes>
    </ColumnDataTypes>
    Enter the data type mapping.
    <item source=" " target=" " />
    Enter the source data type attribute and target data type attribute within quotes. You can enter one or more item elements.
    3. Enter the source data type attribute, and enter the target data type attribute as varchar. You can enter multiple source and target attributes.
    4. Save the XML file, and zip the file as catalogMapping.zip.
    5. Upload the ZIP file to the <Enterprise_Data_Catalog Installation Directory>/services/CatalogService/ScannerBinaries location in the Enterprise Data Catalog installation directory.
    6. Navigate to the <Enterprise_Data_Catalog Installation Directory>/.../CatalogService/ScannerBinaries/CustomDeployer/ location.
    7. Open the scannerDeployer.xml file.
    8. Enter the following content in the file:
    <ExecutionContextProperty isLocationProperty="true" dependencyToUnpack="catalogMapping.zip">
    <PropertyName>CATALOG_MAPPING_LOC</PropertyName>
    <PropertyValue>scanner_agents/profileMapping</PropertyValue>
    </ExecutionContextProperty>
    If the content already exists in a comment element, remove the comment element for the
    <ExecutionContextProperty isLocationProperty="true" dependencyToUnpack="catalogMapping.zip"> ... </ExecutionContextProperty>
    element.
    The
    <ExecutionContextProperty isLocationProperty="true" dependencyToUnpack="catalogMapping.zip"> ... </ExecutionContextProperty>
    element enables the profiling scanner to read the ZIP file.
    9. Save and close the file.
    10. In Informatica Administrator, recycle the Catalog Service.
    Note: After you change or update the XML file, recycle the Catalog Service and run the resource in Catalog Administrator.