If you use a connection parameter in a mapping, you can override the connection defined in the
mapping
task at runtime with values specified in a parameter file.
When you define a connection value in a parameter file, the connection type must be the same as the default connection type in the mapping task. For example, you create a Flat File connection parameter and use it as the source connection in a mapping. In the
mapping
task, you provide a flat file default connection. In the parameter file, you can only override the connection with another flat file connection.
When you override an FTP connection using a parameter, the file local directory must the same.
You cannot use a parameter file to override a lookup with an FTP/SFTP connection.
Some connectors support only cached lookups. To see which type of lookup a connector supports, see the help for the appropriate connector.
In the mapping, create an input parameter:
Select
connection
for the parameter type .
Select
Allow parameter to be overridden at runtime
.
In the mapping, use the parameter as the connection that you want to override.
In the mapping task, define the parameter details:
Select a default connection.
On the
Schedule
tab, enter the parameter file directory and parameter file name.
In the parameter file, define the connection parameter with the value that you want to use at runtime.
Precede the parameter name with two dollar signs ($$). For example, you have a parameter with the name ConParam and you want to override it with the connection OracleCon1. You define the runtime value with the following format:
$$ConParam=OracleCon1
If you want to change the connection, update the parameter value in the parameter file.