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
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.