You can use parameters to represent additional properties such as connections, SQL statements, sort and group-by port lists, expression variables, and run time environment.

You can use the following parameter types for dynamic mappings: expression, input link set, port, port list, resource, and sort list.

You can bind mapping parameters to mapplet parameters or to transformation parameters in the

Instance Value

column of a

Parameters

tab. You can also bind mapplet parameters to transformation parameters.

When you bind a parameter to another parameter, the parameter overrides the other parameter at run time. You can create a mapping or a mapplet parameter from an existing parameter and bind the parameters in one step. Click the

Expose as Mapping Parameter

option or the

Expose as Mapplet Parameter

option for the parameter you want to override.

You can bind parameters from a mapping to parameters in a Read or Write logical data object mapping.

You can define a parameter set for a workflow or mapping. A parameter set is an object in the Model repository that contains a set of parameters and parameter values to use at run time. You use a parameter set with a mapping, Mapping task, or workflow. You can add one or more parameter sets to an application when you deploy the application. You can add a parameter set to multiple applications and deploy them.

You can set the run-time environment with a parameter. Configure a string parameter at the mapping level. Set the default value to Native or Hadoop. When you select the run-time environment for the mapping, click

Assign Parameter

and select the parameter that you configured.