Using Workflow and Session Parameter File Simultaneously
Author: Amit Singh Yadav Date written: 18/01/10 Declaration
I/We hereby declare that this document is based on my/our personal experiences and/or experiences of my/our project members. To the best of my/our knowledge, this document does not contain any material that infringes the copyrights of any other individual or organization . Amit Singh Yadav
Target readers: All
Keywords: Informatica Parameter File, $PMMergeSessParamFile, workflow, informatica, parameter file, session, merge files
Using Parameter file The challenge is to use session level parameter file and workflow level parameter file at the same time. The problem being that when you define a workflow parameter file and a session parameter file for a session within the workflow, the Integration Service uses the workflow parameter file, and ignores the session parameter file. Session Parameter File: It contains session parameters which contain values that can change from session to session, such as database connections or file names. $PMSessionLogFile and $ParamName are user-defined session parameters. Also variables that we use in source queries like date criterion e.g. $$Lastrun Workflow Parameter File It contains workflow level parameters. For example, you can use a workflow variable in a Decision task to determine whether the previous task ran properly. In a workflow, $TaskName.PrevTaskStatus is a predefined workflow variable and $ $SessionName is a user-defined workflow variable.
Using both session and workflow level parameter file. First let me tell you why we need both the parameter files in our workflow. Recently we decided to use third party scheduling tool, Workload Manager (WLM), scheduling product by CA Inc. WLM schedules jobs across platforms e.g. dependent jobs across Informatica, teradata, UNIX MF can be scheduled together. Now the requirement of this...