Parameter and Variable Types
A parameter file can contain different types of parameters and variables. Whenyou run a session or workflow that uses a parameter file, the Integration Servicereads the parameter file and expands the parameters and variables defined inthe file.You can define the following types of parameter and variable in a parameter file:
Define general properties for the Integration Service such asemail addresses, log file counts, and error thresholds. $PMSuccessEmailUser,$PMSessionLogCount, and $PMSessionErrorThreshold are examples of service variables. The service variable values you define in the parameter fileoverride the values that are set in the Administration Console.
Service process variables.
Define the directories for Integration Service filesfor each Integration Service process. $PMRootDir, $PMSessionLogDir, and$PMBadFileDir are examples of service process variables. The service processvariable values you define in the parameter file override the values that are setin the Administration Console. If the Integration Service uses operating systemprofiles, the operating system user specified in the operating system profilemust have access to the directories you define for the service process variables.
Evaluate task conditions and record information in aworkflow. For example, you can use a workflow variable in a Decision task todetermine whether the previous task ran properly. In a workflow,$TaskName.PrevTaskStatus is a predefined workflow variable and $$VariableName is a user-defined workflow variable.
. Evaluate task conditions and record information in a worklet.You can use predefined worklet variables in a parent workflow, but you cannotuse workflow variables from the parent workflow in a worklet. In a worklet,$TaskName.PrevTaskStatus is a predefined worklet variable and $$VariableName is a user-defined worklet variable.
Define values that can change from session to session,such as database connections or file names. $PMSessionLogFile and$ParamName are user-defined session parameters.
Define values that remain constant throughout asession, such as state sales tax rates. When declared in a mapping or mapplet,$$ParameterName is a user-defined mapping parameter.
Define values that can change during a session. TheIntegration Service saves the value of a mapping variable to the repository atthe end of each successful session run and uses that value the next time yourun the session. When declared in a mapping or mapplet, $$VariableName is amapping variable.You cannot define the following types of variables in a parameter file:
$Source and $Target connection variables.
Define the database location for a relational source, relational target, lookup table, or stored procedure.
Define session information in an email message such as thenumber of rows loaded, the session completion time, and read and writestatistics.