When you define the parameter file as a resource for a node, verify the Integration Service runs the session on a node that can access the parameter file. Define the resource for the node, configure the Integration Service to check resources, and edit the session to require the resource.

When you create a file parameter, use alphanumeric and underscore characters. For example, to name a source file parameter, use $InputFile

Name

, such as $InputFile_Data.

All session file parameters of a particular type must have distinct names. For example, if you create two source file parameters, you might name them $SourceFileAccts and $SourceFilePrices.

When you define the parameter in the file, you can reference any directory local to the Integration Service.

Use a parameter to define the location of a file. Clear the entry in the session properties that define the file location. Enter the full path of the file in the parameter file.

You can change the parameter value in the parameter file between session runs, or you can create multiple parameter files. If you use multiple parameter files, use the

pmcmd

Startworkflow command with the -paramfile or -localparamfile options to specify which parameter file to use.

You can change connections for relational sources, targets, lookups, and stored procedures.

When you define the parameter, you can reference any database connection in the repository.

Use the same $DBConnection parameter for more than one connection in a session.