Вы находитесь на странице: 1из 18

Informatica Session Properties

Session in Informatica has following tabs:


General Tab Properties Tab Configuration Tab Mapping Tab (Transformations View) Mapping Tab (Partitions View) Components Tab Metadata Extensions Tab

General Tab

Properties Tab

1) General Options :- General Options settings allow you to configure session log file name, session log file directory, parameter file name and other general session settings. 2) Performance :- The Performance settings allow you to increase memory size, collect performance details, and set configuration parameters.

Properties Tab - General Options Settings


Recovery Strategy 1) Resume from the last checkpoint. The Integration Service saves the session state of operation and maintains target recovery tables. 2) Restart. The Integration Service runs the session again when it recovers the workflow. 3) Fail session and continue the workflow. The Integration Service cannot recover the session, but it continues the workflow. This is the default session recovery strategy.

Properties Tab - Performance Options Settings


DTM process(Data Transformation Manager). Creates threads to initialize the session, read, write, and transform data, and handle pre- and postsession operations.

Collect Performance Data Collects performance details when the session runs.
Enable High Precision Processes the Decimal data-type to a precision of 28. Session Retry On Deadlock The Integration Service retries target writes on deadlock for normal load.

Properties Tab - Performance Options Settings


Pushdown Optimization 1) None. The Integration Service does not push any transformation logic to the database. 2) To Source. To the source database. 3) To Target. To the target database. 4) Full. To both the source database and target database. Session Sort Order Sort order for the session associated with the Integration Service code page. 0. BINARY,2. SPANISH,3. TRADITIONAL_SPANISH 4. DANISH,5. SWEDISH,6. FINNISH Informatica server runs in two modes i.e Unicode and ASCII mode. When we run the session in Unicode, session would run on selected sort order. If session run on ASCII mode ,session would run default on BINARY order.

Config Object Tab

Advanced. Advanced settings allow you to configure constraint-based loading, lookup caches, and buffer sizes. Log options. Log options allow you to configure how you want to save the session log. By default, the Log Manager saves only the current session log. Error handling. Error Handling settings allow you to determine if the session fails or continues when it encounters pre-session command errors, stored procedure errors, or a specified number of session errors. Partitioning options. Partitioning options allow the Integration Service to determine the number of partitions to create at run time.

Config Object Tab - Advanced Option


Default Buffer Block Size Size of buffer blocks used to move data and index caches from sources to targets.

Line Sequential Buffer Length Number of bytes that the Integration Service reads for each line.
Additional Concurrent Pipelines for Lookup Cache Creation Restricts the number of pipelines that the Integration Service can create concurrently to pre-build lookup caches. Pre-build Lookup Cache Allows the Integration Service to build the lookup cache before the Lookup transformation receives the data. Values are Auto,Always Allowed,Always Disallowed.

Config Object Tab Log Option


Save Session Log By If you select Save Session Log by Timestamp, the Log Manager saves all session logs, appending a time stamp to each log. If you select Save Session Log by Runs, the Log Manager saves a designated number of session logs.

Writer Commit Statistics Log Frequency Frequency that the Integration Service writes commit statistics in the session log.
Writer Commit Statistics Log Interval Time interval, in minutes, to write commit statistics to the session log.

Config Object Tab Error handling


Stop On Errors
Indicates how many non-fatal errors the Integration. 0 specifies non-fatal errors do not cause the session to stop. Overrides tracing: Selects tracing level as None, Terse, Normal, Verbose Initialization, or Verbose Data. Terse: Integration Service logs initialization information and error messages and notification of rejected data. Normal: Integration Service logs initialization and status information, errors encountered, and skipped rows due to transformation row errors. Summarizes session results, but not at the level of individual rows. Verbose Initialization: In addition to normal tracing, Integration Service logs additional initialization details, names of index and data files used, and detailed transformation statistics.

Verbose Data: In addition to verbose initialization tracing, Integration Service logs each row that passes into the mapping. Also notes where the Integration Service truncates string data to fit the precision of a column and provides detailed transformation statistics.
Log Row Data : Specifies whether or not to log transformation row data. When you enable error logging, the Integration Service logs

Config Object Tab Partitioning options


Dynamic partitioning
Disabled. Do not use dynamic partitioning. Based on number of partitions. Sets the partitions to a number that you define in the Number of Partitions attribute. Based on number of nodes in grid. Sets the partitions to the number of nodes in the grid running the session. Based on source partitioning. Determines the number of partitions using database partition information. The number of partitions is the maximum of the number of partitions at the source. Based on number of CPUs. Sets the number of partitions equal to the number of CPUs on the node that prepares the session. Default is disabled.

Mapping tab Transformation View

Source Options

Readers. Displays the reader that the Integration Service uses with each source instance. Connections. Displays the source connections. Properties. Displays source and source qualifier properties. For relational sources, you can override properties that you configured in the Mapping Designer.

Source Filetype : Indicates whether the source file contains the source data, or a list of files with the same file properties. Select Direct if the source file contains the source data. Select Indirect if the source file contains a list of files.

Target Options
Writers. Displays the writer that the Integration Service uses with each target instance. For relational targets, you can choose a relational writer or a file writer. Choose a file writer to use an external loader. Connections. Displays the target connections. Properties. Displays different properties for different target types. For relational targets, you can override properties that you configured in the Mapping Designer.

Target Load Type : Choose Bulk when you load to DB2, Sybase, Oracle, or Microsoft SQL Server. Bulk mode improves session performance, but limits the ability to recover because no database logging occurs.

Mapping tab Partition View

Components Tab

Metadata Extensions Tab


Extension Name : Name of the metadata extension. Metadata extension names must be unique in a domain. Datatype : Datatype: numeric (integer), string, boolean, or XML.

Value :

Value of the metadata extension. For a numeric metadata extension, the value must be an integer. For a boolean metadata extension, choose true or false. For a string or XML metadata extension, click the button in the Value field to enter a value of more than one line. The Workflow Manager does not validate XML syntax. Precision : Maximum length for string or XML metadata extensions. Reusable : Select to make the metadata extension apply to all objects of this type (reusable). Clear to make the metadata extension apply to this object only (non-reusable). Description : Description of the metadata extension.

Thank You!!

Вам также может понравиться