Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Parameter Files Overview

Parameter Files Overview

Ratings: (0)|Views: 1,284|Likes:
Published by ypraju

More info:

Published by: ypraju on Dec 22, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Parameter Files
By Y P Raju
Parameter Files Overview
A parameter file is a list of parameters and variables and their associated values.These values define properties for a service, service process, workflw, worklet, or session. The Integration Service applies these values when yourun a workflow or session that uses the parameter file.Parameter files provide you with the flexibility to change parameter and variablevalues each time you run a session or workflow. You can include information for multiple services, service processes, workflows, worklets, and sessions in asingle parameter file. You can also create multiple parameter files and use adifferent file each time you run a session or workflow. The Integration Servicereads the parameter file at the start of the workflow or session to determine thestart values for the parameters and variables defined in the file. You can create aparameter file using a text editor such as WordPad or Notepad.Consider the following information when you use parameter files:
Types of parameters and variables.
You can define different types of parameters and variables in a parameter file. These include service variables,service process variables, workflow and worklet variables, session parameters,and mapping parameters and variables. For more information, seeParameter and Variable Types.
Properties you can set in parameter files.
Use parameters and variables todefine many properties in the Designer and Workflow Manager. For example,you can enter a session parameter as the update override for a relational targetinstance, and set this parameter to the UPDATE statement in the parameter file.The Integration Service expands the parameter when the session runs. For information about the properties you can set in a parameter file, seeWhere toUse Parameters and Variables.
Parameter file structure.
Assign a value for a parameter or variable in theparameter file by entering the parameter or variable name and value on a singleline in the form name=value. Groups of parameters and variables must bepreceded by a heading that identifies the service, service process, workflow,worklet, or session to which the parameters or variables apply. For moreinformation about the structure of a parameter file, seeParameter File Structure.
Parameter file location.
Specify the parameter file to use for a workflow or 
session. You can enter the parameter file name and directory in the workflow or session properties or in the pmcmd command line. For more information, seeConfiguring the Parameter File Name and Location.
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:
Service variables.
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.
Workflow 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.
Worklet variables
. 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.
Session parameters.
Define values that can change from session to session,such as database connections or file names. $PMSessionLogFile and$ParamName are user-defined session parameters.
Mapping 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.
Mapping variables.
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.
Email variables.
Define session information in an email message such as thenumber of rows loaded, the session completion time, and read and writestatistics.
Local variables.
Temporarily store data in variable ports in Aggregator,Expression, and Rank transformations.
Built-in variables.
Variables that return run-time or system information, such asIntegration Service name or system date.
Transaction control variables.
Define conditions to commit or rollbacktransactions during the processing of database rows.
ABAP program variables.
Represent SAP structures, fields in SAP structures,or values in the ABAP program.
Where to Use Parameters and Variables
You can use parameters and variables to assign values to properties in theDesigner and Workflow Manager and to override some service and serviceprocess properties. For example, you can use a parameter to specify the Lookupcache file name prefix or the default remote directory for an FTP connection.If the property is a SQL statement or command, you can either use parametersand variables within the statement or command, or you can enter a parameter or variable in the input field for the property, and set the parameter or variable to theentire statement or command in the parameter file.For example, you want to use a parameter or variable in a relational targetoverride. You can enter a parameter or variable within the UPDATE statement of a relational target override and define the parameter or variable below theappropriate heading in the parameter file. Or, to define the UPDATE statement ina parameter file, complete the following steps:1.In the Designer, edit the target instance, enter session parameter $ParamMyOverride in the Update Override field, and save the mapping.2. In the Workflow Manager, configure the workflow or session to use a parameter file. For more information, seeConfiguring the Parameter File Name andLocation.3.Set $ParamMyOverride to the SQL UPDATE statement below the appropriateheading in the parameter file. For more information about parameter fileheadings, seeParameter File Structure.You can also use a parameter file to override service and service processproperties defined in the Administration Console. For example, you can overridethe session log directory, $PMSessionLogDir. To do this, configure the workflowor session to use a parameter file and set $PMSessionLogDir to the new file pathin the parameter file.You can specify parameters and variables for the following PowerCenter objects:
You can use parameters and variables in input fields related tosources. For more information, seeTable 28-1.
You can use parameters and variables in input fields related to targets.For more information, seeTable 28-2.
You can use parameters and variables in input fields relatedto transformations. For more information, seeTable 28-3.
You can use parameters and variables in input fields related to tasks inthe Workflow Manager. For more information, seeTable 28-4.
You can use parameters and variables in input fields related toSession tasks. For more information, seeTable 28-5.

Activity (21)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Vikas Bhasin liked this
Suresh Kumar liked this
ajaygj liked this
vinay712 liked this
mvssatish liked this
outofmind liked this
natrajdreams liked this
nelrick1984 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->