Parameter file is a text file that contains parameters and variables which can be referenced in Sessions and Workflows.   Multiple Session and Workflows can share the same parameter file by logically grouping the Parameter file as mentioned below.

Each section is preceded by a heading that identifies the Integration Service, Integration Service process, Workflow, Worklet or session to which the parameters or variables need to be defined. Parameters and variables need to be defined below the heading.

Characteristics:

  • The Integration Service interprets all characters between the beginning of the line and the first equals sign as the parameter name and all characters between the first equals sign and the end of the line as the parameter value.

Parameter File Sections:

The following table describes the parameter file headings that define each section in the parameter file and the scope of the parameters and variables that you define in each section. We can define the parameters in the file as shown below:

Heading Example Scope
[Global] $PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

All Integration Services, Integration Service processes, workflows, worklets, and sessions.
[Service:service name] [Service:ETLI]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

The named Integration Service and workflows, worklets, and sessions that this service runs.
[Service:service name.ND:node name] [Service:ETLI.ND:node1]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

The named Integration Service process and workflows, worklets, and sessions that this service process runs.
[folder name.WF:workflow name] [SCN_D.WF:w_test]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

The named workflow and all sessions within the workflow.
[folder name.WF:workflow name.WT:worklet name] [SCN_D.WF:w_test.WT:wrk_sub_test]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

The named worklet and all sessions within the worklet.
[folder name.WF:workflow name.WT:worklet name.WT:worklet name…] [SCN_D.WF:w_test.WT:wrk_sub_test. WT:wrk_sub_test1]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

The nested worklet and all sessions within the nested worklet.
[folder name.WF:workflow name.ST:session name]

-or-

[folder name.WF:workflow name.WT:worklet name.ST:session name]

-or-

[folder name.session name]

-or-

[session name]

[SCN_D.WF:w_test.ST:s_test]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

or

[SCN_D.WF:w_test.WT:wrk_sub_test. ST:s_test]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

Or

[SCN_D.ST:s_test]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

Or

[s_test]

$PMSuccessEmailUser=pcadmin@mail.com

$PMFailureEmailUser=pcadmin@mail.com

The named session.

Precedence:

Create each heading only once in the parameter file. If there are multiple headers with the same name, Integration service will always refer to the first one and ignore the rest.
For example, a parameter file contains the following identical headings:[HET_TGTS.WF:wf_TCOMMIT1]

$$platform=windows

[HET_TGTS.WF:wf_TCOMMIT1]

$$platform=unix

$DBConnection_ora=Ora2

In workflow wf_TCOMMIT1, the value for mapping parameter $$platform will be “windows” and not “unix”.  Also, session parameter $DBConnection_ora is not defined.

If we define the same parameter or variable in multiple sections in the parameter file, the parameter or variable with the smallest scope takes precedence over parameters or variables with larger scope. For example, a parameter file contains the following sections:[HET_TGTS.WF:wf_TGTS_ASC_ORDR]$DBConnection_ora=Ora2[HET_TGTS.WF:wf_TGTS_ASC_ORDR.ST:s_TGTS_ASC_ORDR]$DBConnection_ora=Ora3

In session s_TGTS_ASC_ORDR, the value for session parameter $DBConnection_ora is “Ora3.” In all other sessions in the workflow, it is “Ora2”.

Comments:

Comments can be defined on parameter files. The Integration Service ignores lines that are not valid headings and do not contain an equals sign character (=).  The following lines are examples of parameter file comments:

—————————————

Created 10/11/06 by Smith.

*** Update the parameters below this line when you run this workflow on Integration Service Int_01. ***

; This is a valid comment because this line contains no equals sign.

Tips And Tricks:

  • If  we  enter a space between the parameter name and the equals sign, the Integration Service interprets the space as part of the parameter name.
  • If a line contains multiple equals signs, the Integration Service interprets all equals signs after the first one as part of the parameter value.
  • Mapping parameter and variable names are not case sensitive.
  • Precede parameters and variables in mapplets with the mapplet name
  • When defining parameter values, do not use unnecessary line breaks or spaces
  • Do not enclose parameter or variable values in quotes.

Posted by Priya T
Comments (0)
August 23rd, 2011

Comments (0)