Mapping data connection objects to a database

You can map data connection objects to an imported database. As a result, lineage reports display the actual database name rather than the data connection object wherever the database asset occurs.

Before you begin

You must have the Information Governance Catalog Information Asset Administrator role.

About this task

Jobs from IBM® InfoSphere® DataStage® read from or write to data sources by using stages. The stage defines data connections such as the URL, server name, database name, user credentials, and SQL statements that are needed to access the database. Different stages might use different data source names to refer to the same database. During lineage analysis of job designs and job runs, the names of the host and data sources that are found in the job's stages are added to the list of data connection objects.

For lineage to continue the flow through databases that are referred to by different data source names, you must map the data connection object to the imported database. Lineage uses this information to create relationships between stages and imported database tables. If this mapping is not done, the lineage for that job displays the database tables as virtual assets that might not link correctly to the rest of the lineage flow.

At times, you might need to map the data connection objects to a database that cannot be imported because of your internal security policies. In this case, you can identify those data connection objects as being the same, and select one of them as the preferred name for when you display lineage reports.

Procedure

  1. Click Administration.
  2. Expand Lineage Management.
  3. Click Lineage Administration.
  4. Click Data Connection Mappings in the left pane.
  5. If the database that you want to map to was imported, do these steps:
    1. In the Data Connections Mappings pane, select the data connection that you want to map to the database, and then click Edit.
    2. In the Bound to Database list, select the database to map a data connection to.

      Do this step for each data connection that you need to map to the database. If you have many mappings, it might be more convenient to edit the first data connection that was bound to a database. Then, in the Same as Data Connections field, add all other data connections that map to the same database.

  6. If the database that you want to map to cannot be imported due to your security policies, do these steps:
    1. Edit the first data connection. In the Same as Data Connections field, add all other data connections that would map to the same database that is not imported.

      The database assets are displayed as virtual assets because the database was not imported.

    2. Select one of the identical data connections to be the preferred data connection.
      In lineage reports, this preferred data connection is displayed wherever any of these data connection objects participate in the data flow.
  7. Click Save.