![]() ![]() If s_session_test1 is used in WKLT_workletA and WKLT_workletB with two different values, then we can define the parameter value as, This can be very well achieved by indicating the specific session name through its worklet as in the below example. There can be situations where a reusable session used in two different worklets can need two different param values at two instances. There can also be a separate parameter file that can be defined for a session, where the parameter value defined in this param file takes the higher precedence than the one defined in the workflow’s param file. So here in the session ‘s_sample_session_name’, the ‘’$$Param_test” holds the value 2012 and not the 2011 for the higher precedence by the session level parameter. The session level parameters are defined in the workflow’s parameter file with the session name, this has the precedence over the global parameters. These are the parameters defined in the whole workflow’s parameter files, directly as parameters. This is the least precedence level, defined as initial value in the mapping designer itself. There are different levels of precedence of the parameters, The parameter files are saved with an extension. Similarly any value from the ‘=’ till the end of the line shall be considered as the value to the respective parameter. The parameters are detected by the Informatica IS with a $$ and takes the parameter name from the $$ till the occurrence of the ‘=’ symbol, anything between $$ and = shall be considered as the parameter name. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |