Explain about Informatica session properties

Session property is a series of instructions on how and when to transfer data from source to target.Just like other tasks you create in workflow manager, a session property is a job. Any session you create must have a corresponding mapping. A session may have one mapping at a time, and can not be changed once assigned. This must be added to a workflow to perform a session mission.

To get in-Depth knowledge on Informatica you can enroll for a live demo on Informatica online training

parameter	in document
lsi	present
focus	Informatica
kw density	1k-100k
fkw density	1
flesch	60
plagiarism	unique

 A session may be an object which can be reused or not reused. If you create a task creator session, it can be reused, but if you create a workflow designer session, it is non-reusable.

The multiple workflows can be added to a shared session.

Session Properties in Informatica

Using the session property you can configure various session features such as pre- and post SQL scripts, log file name and route, memory property, etc.

The session properties can also be overridden by mapping properties. Let us address the following important features of the session in this segment.

• Treat rows of sources 
• Interval of commitments
• Property of log file of a session
• Property Load Test
• Logging Choices
• Error Detection
• Source or Goal Properties
• Contacts

Step 1 

In task developer, open the session "s m emp emp target," which you create.Learn more from informatica course

 

Step 2

 

 To open the task edit window, double-click on the session icon within Task Creator.

Step 3

 Clicks on the Properties tab inside the "Edit Task" window.

Step 4

It will display the properties of the session in the Property tab.

Treat Source Rows as data driven in Informatica

This property helps you to determine how the destination table affects the source data. For instance, you can define that you should insert or delete the source record from the goal.

There are four options for this property-

• Insert 
• Upgrade
• Stretch
• Data-fueled

When this property is set for insertion, the source data to be inserted will be marked. It means just inserting the data.

The destination data will be updated by the source data when the property is set to update. The primary data key needs to be defined in the target table for updating.

When property is set to remove from the target table the source data that is already present in the list will be removed. To execute and apply the modifications to this property, the primary key should be specified in the target table.

The Informatica checks the source records are labelled, with the property set to data driven. If the source records are marked as insert in a mapping then records are inserted inside the goal. If records are marked in the mapping as an update, then the records are updated to the target. So what activity at the target will be conducted depends on how records are treated within the mapping.

 Handle Root Rows-Eliminate

Step 1

• Select "Delete" option in the session task 's property tab in "Treat Source Rows as"
• Select OK button

Step 2

• Open Informatica designer to define the primary key in the target table
• Open aim designer
• Double-clicking on the table "emp target"    
• This will open our target table with a "Edit Table."

Step 3

• In the target table edit window
• For the column EmpNo, from the scroll down menu , select key sort as "primary key" and
• Click OK link.

Step 4

• Save Informatica changes and implement this mapping workflow.
• When you execute this mapping you must delete the source records that are already present in the target.

Interval of Commitments-Property

This property defines the interval after which commit operation to the target table is rendered by the Informatica.

For instance, if you insert 20,000 records into a target table, and you define commit interval as 5,000, then a commit operation will be performed after every 5,000 record insertions in the target. Get more skills from informatica training

• Name of log file of session log file of session
• Setup to change this property
• Trace file name of the session by default and
• The log-file route

The $PMSessionLogDir is an Informatica variable, pointing to the default location "C:Informatica9.6.1serverinfa sharedSessLogs" in windows.

Activate Test Load

You can check your session and the mappings using this property. When using this function and running the sessions, records will be retrieved from the sources but not loaded into the target. This feature thus helps inside the mapping to test the correctness of mappings, parameter files, to function different transformations.

If this feature is enabled, then there is another property – No of Rows to Check, this property should be configured for the number of records you want to get from the source for the test load

Memory property

Memory properties give us the flexibility to fine-tune the performance optimisation memory allocated to the Informatica. When there is high bottleneck and poor performance then using the memory properties you can try to improve the performance.

Click on the "Config file" tab in the edit task window to customize memory resources. It will open another window, where the changes can be configured.

You may configure the memory properties within this section. For example, block size of the default buffer, the sequential buffer length, etc. Changes to those properties will determine how much memory should be allocated for their operation to Informatica services.

Logging Choices

You may configure the log properties of the session in this Property section. You can set the no to how many logs for a session you want to save, session log file max size.

Error Detection in Informatica

The error properties for the session can be configured in this section.

You can configure how many errors the session has to be stopped using Stop on Errors.

You can override the mapping tracking levels using override tracing.

You may also customize the session actions for various errors, such as stored procedure error, SQL error pre-post, etc.

Mapping Properties and Source or Target

You can customize the properties relating to the mapping and its sources / targets and transformations in the mapping tab of the session's edit task window. For this Properties portion, you can override the source and target property. you may add table name prefixes for the sources and targets that override the table names. Inside the mappings you can configure the properties of different transformations, sources and targets, besides that you can also review and override those properties in this section. Reviewing all of those assets is like a single spot.

Link Properties in Mapping Informatica

Using this property, you can identify source and destination database connections.

Source 

You may configure the properties relating to the mapping source in this section. For source, you can configure pre- and post SQL files.

You can override the SQL for source using the SQL query property. This segment also helps you to override the name of the source table.

Goal Equipment

You can configure destination details in this section. You can determine if the target load must be a bulk load or a normal mode. The performance gain in bulk load is achieved, as there are no redo log buffers handled by the database during loading. On the other hand, regular load is sloyour than bulk load, but recovery of the database is possible in case of failure.

You can also describe the property before filling in the target table to truncate it. This means the target table will be truncated before loading any records into the target, and then the load will be executed. This property is useful when you construct stage load mappings.You can also describe target pre-SQL table and post-SQL table. Pre SQL is the piece of SQL code that will be executed before inserting into the target table, and after loading the target table, post SQL code will be executed.

Progress or Lack of Session Assignment

If inside a workflow you have multiple sessions, then there may be a scenario where one or more sessions fail. In such a condition, a question arises as to what the workflow status would be because you have a workflow in which few tasks have failed, and few tasks have been successful. Informatica offers the option of setting this fault-specific property inside the workflow to handle such conditions. Configuring such behaviour

Step 1

Open the "wkf run command" workflow that you generated earlier

Step 2

Double click the task of the command, this will open the task edit window

• Select the category General
• Select the check box  against property.
• Choose The Ok Click.

Step 3 

Use Ctrl +s shortcut to save the changes.

After making the above changes, when you execute this workflow, if any of the tasks fail, the workflow status will be done as fail. So, you can identify that some of its tasks failed during the execution of your workflow.

I hope you reach a conclusion about Data Warehousing in Informatica. You can learn more about Informatica from online Informatica training

Conclusion:

I hope you to reach a conclusion about session properties of informatica. You can learn more from Informatica online training.