Informatica Parameter Files

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

$PMSuccessEmailUser=pcadmin@m
ail.com
[Global]

[Service:service
name]

$PMFailureEmailUser=pcadmin@ma
il.com

[Service:ETLI]
$PMSuccessEmailUser=pcadmin@m
ail.com

Steria

Scope
All
Integrati
on
Services,
Integrati
on
Service
processe
s,
workflo
ws,
worklets,
and
sessions.
The
named
Integrati
on
Service

Page 1 of 6

$PMFailureEmailUser=pcadmin@ma
il.com

[Service:ETLI.ND:node1]
[Service:service
name.ND:node
name]

$PMSuccessEmailUser=pcadmin@m
ail.com
$PMFailureEmailUser=pcadmin@ma
il.com

[SCN_D.WF:w_test]
[folder
name.WF:workf
low name]

$PMSuccessEmailUser=pcadmin@m
ail.com
$PMFailureEmailUser=pcadmin@ma
il.com

[SCN_D.WF:w_test.WT:wrk_sub_tes
t]
[folder
name.WF:workf
low
name.WT:workl
et name]

Steria

$PMSuccessEmailUser=pcadmin@m
ail.com
$PMFailureEmailUser=pcadmin@ma
il.com

and
workflo
ws,
worklets,
and
sessions
that this
service
runs.
The
named
Integrati
on
Service
process
and
workflo
ws,
worklets,
and
sessions
that this
service
process
runs.
The
named
workflo
w and all
sessions
within
the
workflo
w.
The
named
worklet
and all
sessions
within
the
worklet.

Page 2 of 6

[folder
name.WF:workf
low
name.WT:workl
et
name.WT:workl
et name...]

[folder
name.WF:workf
low
name.ST:session
name]
-or-

[SCN_D.WF:w_test.WT:wrk_sub_tes
t. WT:wrk_sub_test1]
$PMSuccessEmailUser=pcadmin@m
ail.com
$PMFailureEmailUser=pcadmin@ma
il.com

[SCN_D.WF:w_test.ST:s_test]
$PMSuccessEmailUser=pcadmin@m
ail.com

or

-or-

$PMFailureEmailUser=pcadmin@ma
il.com

-or[session name]

The
named
session.

$PMFailureEmailUser=pcadmin@ma
il.com

[folder
name.WF:workf
low
name.WT:workl
et
name.ST:session
name]

[folder
name.session
name]

The
nested
worklet
and all
sessions
within
the
nested
worklet.

[SCN_D.WF:w_test.WT:wrk_sub_tes
t. ST:s_test]
$PMSuccessEmailUser=pcadmin@m
ail.com

Or
[SCN_D.ST:s_test]
$PMSuccessEmailUser=pcadmin@m
ail.com
$PMFailureEmailUser=pcadmin@ma
il.com
Or
[s_test]
$PMSuccessEmailUser=pcadmin@m
ail.com

Steria

Page 3 of 6

$PMFailureEmailUser=pcadmin@ma
il.com

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_OR
DR]$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. ***

Steria

Page 4 of 6

; 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.

Sample Param file

Other vital points:

Steria

Page 5 of 6

Comments: Something very important and different from other languages and tools, Any
line written apart from valid headings or do not contains character (=) are comments.
Null Values: Here is the deal Parameter can be assigned by NULL values.
Spaces: Something very important, **Remember** Integration service will consider space as
part of value assigned to it, if there is a space between parameter name and equal sign.

Steria

Page 6 of 6