Informatica Paramter File

development contention single single wedge Using Workflow and school term line of reasoning File Simultaneously condition Amit Singh Yadav Date written 18/01/10 Declaration I/We hereby halt that this catalogue is found on my/our in the flesh(predicate) experiences and/or experiences of my/our project members. To the best of my/our knowledge, this document does not contain any actual that infringes the copyrights of any other individual or organization . Amit Singh Yadav Target subscribe toers All Keywords Informatica line File, $PMMergeSessParamFile, work flow, informatica, argument bear down, school term, merge commovesThe Challenge Using contestation show The challenge is to exercise posing aim disceptation register and work flow level argument file at the same sequence. The problem be that when you define a workflow parametric quantity file and a seance contestation file for a session at heart the workflow, the Integration Service lend oneselfs the workflow disceptation file, and ignores the session tilt file. school term Parameter File It contains session logical arguments which contain value that washbowl qualifying from session to session, much(prenominal) as database connectors or file name. PMSessionLogFile and $Param call off are exerciser-defined session lines. Also variables that we intake in source queries like date banner e. g. $$Lastrun Workflow Parameter File It contains workflow level disceptations. For example, you can use a workflow variable in a Decision task to determine whether the old task ran properly. In a workflow, $TaskName. PrevTaskStatus is a predefined workflow variable and $ $SessionName is a user-defined workflow variable. Problem Statement Using two session and workflow level argumentation file.First let me tell you why we necessity both the controversy files in our workflow. deep we decided to use third party programming tool, Workload Manager (WLM), scheduling produc t by CA Inc. WLM schedules jobs crossways platforms e. g. dependent jobs across Informatica, teradata, UNIX MF can be scheduled together. Now the indispensability of this scheduler is that 1. You need to have a scheduler level contestation file with all the sessions names used in the workflow. 2. You need to use this same argument file as workflow level argument file in your workflow.The problem we faced was that our sure situation is The sql query in our sessions is charter * from where date $ $lastrun. We have a session level line of reasoning file and all time the session runs it fillings $$lastrun from the session parameter file. At the end of the session a script is run which updates the $$lastrun with todays date so that next time when the session is run it picks up data for dates $$lastrun. This is how our session level parameter files looks $ much mStaging_PCare. parm Using Parameter file s_mStaging_PCare $$lastrun=2009-12-20 ? session_name - ? Lastrun dateNow if a workflow level parameter file is used, the variable $$lastrun willing have to be deferred paymented in the workflow parameter file. And If we will mention $$lastrun there, then Informatica will pick up the date from the workflow parameter file, while the session level parameter file variable, $$lastrun, will be updated by a script in the session so, we need something through which we can use both workflow and session parameter file. Solution There is a precise useful property in Informatica called $PMMergeSessParamFile which when traffic circle to TRUE will force Informatica to read both session and workflow parameter file.What we did was we created a new workflow parameter file with the all the sessions name in it and for every session we have raiment $PMMergeSessParamFile=TRUE. Now when workflow runs it looks for $$lastrun in workflow parameter file and when it does not harness the value there, it looks for $ $lastrun in session parameter file. It gets the value there and session succeeds. In the end the script updates the session level parameter file with todays date. In this way we were able to use both 1. Workflow level parameter file which was the requirement of WLM. 2.Session Level parameter file which was required by our session since the script updates session level parameter file and we did not wanted to dislodge the script. This is how our new workflow level parameter files looks $ much PCare_Staging_WLM. par s_mStaging_PCare ? Session Name -? parameterized connection $DBConnectionSource=Tera_ETL_VIEWS_NE $PMMergeSessParamFile=TRUE ? Property lap(p) to true Using Parameter file After using this parameter file Informatica will pick up connection name from the above parameter file and $$lastrun from session parameter file since $PMMergeSessParamFile is commemorate to TRUE.This is what was required. Usage 1. 2. This property will lease users to use both session and workflow level parameter file at same time. Like in the scenario above. state there are sessions which are based on Incremental logic i. e. Session level parameter file is automatically created by UNIX script. Now if users wants to have parameterized connections for such sessions then either they need to change their script which generates parameter file or they can simple use $PMMergeSessParamFile and mention parameterized connection names at workflow level parameter file. . If users want a workflow to run two synchronal instances. If two workflows use same set of re-usable sessions then it overhauls in making parameter file names parameterized. It removes hard code of parameter file name from sessions. For more details please refer Informatica help section. Path given below. Parameter Files Configuring the Parameter File Name and Location References Informatica swear out Guide