Use the following rules and guidelines when you create parameter files:
List all session parameters. Session parameters do not have default values. If the Integration Service cannot find a value for a session parameter, it may fail the session, take an empty string as the default value, or fail to expand the parameter at run time. Session parameter names are not case sensitive.
List all necessary mapping parameters and variables. Mapping parameter and variable values become start values for parameters and variables in a mapping. Mapping parameter and variable names are not case sensitive.
Enter folder names for non-unique session names. When a session name exists more than once in a repository, enter the folder name to indicate the location of the session.
Precede parameters and variables in mapplets with the mapplet name. Use the following format:
mapplet_name.parameter_name=value mapplet2_name.variable_name=value
Use multiple parameter files. You assign parameter files to workflows, worklets, and sessions individually. You can specify the same parameter file for all of these tasks or create multiple parameter files.
When defining parameter values, do not use unnecessary line breaks or spaces. The Integration Service interprets additional spaces as part of a parameter name or value.
Use correct date formats for datetime values. Use the following date formats for datetime values:
MM/DD/RR
MM/DD/YYYY
MM/DD/RR HH24:MI
MM/DD/YYYY HH24:MI
MM/DD/RR HH24:MI:SS
MM/DD/YYYY HH24:MI:SS
MM/DD/RR HH24:MI:SS.MS
MM/DD/YYYY HH24:MI:SS.MS
MM/DD/RR HH24:MI:SS.US
MM/DD/YYYY HH24:MI:SS.US
MM/DD/RR HH24:MI:SS.NS
MM/DD/YYYY HH24:MI:SS.NS
You can use the following separators: dash (-), slash (/), backslash (\), colon (:), period (.), and space. The Integration Service ignores extra spaces. You cannot use one- or three-digit values for year or the “HH12” format for hour.
Do not enclose parameter or variable values in quotes. The Integration Service interprets everything after the first equals sign as part of the value.
Use a parameter or variable value of the proper length for the error log table name prefix. If you use a parameter or variable for the error log table name prefix, do not specify a prefix that exceeds 19 characters when naming Oracle, Sybase, or Teradata error log tables. The error table names can have up to 11 characters, and Oracle, Sybase, and Teradata databases have a maximum length of 30 characters for table names. The parameter or variable name can exceed 19 characters.
List all session parameters. Session parameters do not have default values. If the Integration Service cannot find a value for a session parameter, it may fail the session, take an empty string as the default value, or fail to expand the parameter at run time. Session parameter names are not case sensitive.
List all necessary mapping parameters and variables. Mapping parameter and variable values become start values for parameters and variables in a mapping. Mapping parameter and variable names are not case sensitive.
Enter folder names for non-unique session names. When a session name exists more than once in a repository, enter the folder name to indicate the location of the session.
Precede parameters and variables in mapplets with the mapplet name. Use the following format:
mapplet_name.parameter_name=value mapplet2_name.variable_name=value
Use multiple parameter files. You assign parameter files to workflows, worklets, and sessions individually. You can specify the same parameter file for all of these tasks or create multiple parameter files.
When defining parameter values, do not use unnecessary line breaks or spaces. The Integration Service interprets additional spaces as part of a parameter name or value.
Use correct date formats for datetime values. Use the following date formats for datetime values:
MM/DD/RR
MM/DD/YYYY
MM/DD/RR HH24:MI
MM/DD/YYYY HH24:MI
MM/DD/RR HH24:MI:SS
MM/DD/YYYY HH24:MI:SS
MM/DD/RR HH24:MI:SS.MS
MM/DD/YYYY HH24:MI:SS.MS
MM/DD/RR HH24:MI:SS.US
MM/DD/YYYY HH24:MI:SS.US
MM/DD/RR HH24:MI:SS.NS
MM/DD/YYYY HH24:MI:SS.NS
You can use the following separators: dash (-), slash (/), backslash (\), colon (:), period (.), and space. The Integration Service ignores extra spaces. You cannot use one- or three-digit values for year or the “HH12” format for hour.
Do not enclose parameter or variable values in quotes. The Integration Service interprets everything after the first equals sign as part of the value.
Use a parameter or variable value of the proper length for the error log table name prefix. If you use a parameter or variable for the error log table name prefix, do not specify a prefix that exceeds 19 characters when naming Oracle, Sybase, or Teradata error log tables. The error table names can have up to 11 characters, and Oracle, Sybase, and Teradata databases have a maximum length of 30 characters for table names. The parameter or variable name can exceed 19 characters.
guideness for creating parameters..
ReplyDeleteinformatica training
guidliness for creating parametes nic eposts..
ReplyDeleteinformatica online training
Thank you for providing useful contentInformatica Online Training
ReplyDeleteHyderabad
Thank you so much for throwing light on such an important topic, not sure if you are interested in 3rd party product but ZappySys has very easy solution.
ReplyDeleteLink here"
Informatica Read Rest Api