Scribd
Upload
46 views

Creating Configuration Object and Its Use

Creating Configuration Object and its use: 1. In the Workflow Manager: Special Objects -> Special Configuration, add a new Configuration Object and provide a name and description. 2. The Configuration Object tab includes settings for commit and load options, logging, and error handling that can be customized from defaults. 3. Configuration Objects allow customizing settings that apply to sessions run with that Configuration Object, rather than using the global default settings.

Uploaded by

nandy39
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
46 views

Creating Configuration Object and Its Use

Creating Configuration Object and its use: 1. In the Workflow Manager: Special Objects -> Special Configuration, add a new Configuration Object and provide a name and description. 2. The Configuration Object tab includes settings for commit and load options, logging, and error handling that can be customized from defaults. 3. Configuration Objects allow customizing settings that apply to sessions run with that Configuration Object, rather than using the global default settings.

Uploaded by

nandy39
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Creating Configuration Object and its use:

The Configuration Object tab in the session property includes commit and load settings, log
options, and error handling settings. The default Configuration tab is 'default_session_config'. In
the session property, we can set the configuration object as default or the object we created.
Creating a Configuration Object:
1. In the Workflow Manager: Special Objects -> Special Configuration

2. Add new Configuration Object.

3. Enter the name for new configuration Object and Description required.
4. In the Properties wizard, we have three tab pages (Advanced, Log Options, Error Handling)

Configuration Object Tab - Advanced Settings

Advanced
Settings
Constraint
Based Load
Ordering

Required/Optional

Description

Optional

The Informatica Server loads targets based on primaryforeign key constraints where possible.

Optional

If selected, the Informatica Server caches PowerMart 3.5


LOOKUP functions in the mapping, overriding mapping-level
LOOKUP configurations.
If not selected, the Informatica Server performs lookups on
a row-by-row basis, unless otherwise specified in the
mapping.

Default Buffer
Optional
Block Size

This setting is performance related.


Note: The session must have enough buffer blocks to
initialize. The minimum number of buffer blocks must be
greater than the total number of sources (Source Qualifiers,
Normalizers for COBOL sources), and targets. The number
of buffer blocks in a session = DTM Buffer Pool Size / Buffer
Block Size. Default settings create enough buffer blocks for
83 sources and targets. If the session contains more than
83, you might need to increase DTM Buffer Pool Size or
decrease Default Buffer Block Size.

Line
Sequential
Optional
Buffer Length

Affects the way the Informatica Server reads flat files.


Increase this setting from the default of 1024 bytes per line
only if source flat file records are larger than 1024 bytes.

Cache
Lookup()
Function

Configuration Object Tab - Log Options Settings

Log Options Required/Optional

Save
Session Log
By

Save
Session Log
for These
Runs

Description

Required

If you select Save Session Log by Timestamp, the


Informatica Server saves all session logs, appending a
timestamp to each log.
If you select Save Session Log by Runs, the Informatica
Server saves a designated number of session logs.
Configure the number of sessions in the Save Session Log
for These Runs option.
You can also use the $PMSessionLogCount server variable
to save the configured number of session logs for the
Informatica Server.

Required

The number of historical session logs you want the


Informatica Server to save.
The Informatica saves the number of historical logs you
specify, plus the most recent session log. Therefore, if you
specify 5 runs, the Informatica Server saves the most recent
session log, plus historical logs 0-4, for a total of 6 logs.
You can specify up to 2,147,483,647 historical logs. If you
specify 0 logs, the Informatica Server saves only the most
recent session log.

Configuration Object Tab - Error Handling Settings

Error
Handling
Settings

Stop On
Errors

Override
Tracing

On Stored
Procedure
Error

Required/Optional

Description

Optional

Indicates how many non-fatal errors the Informatica Server


can encounter before it stops the session. Non-fatal errors
include reader, writer, and DTM errors. Enter the number of
non-fatal errors you want to allow before stopping the
session. The Informatica Server maintains an independent
error count for each source, target, and transformation. If
you specify 0, non-fatal errors do not cause the session to
stop.
Optionally use the $PMSessionErrorThreshold server
variable to stop on the configured number of errors for the
Informatica Server.

Optional

Overrides tracing levels set on a transformation level.


Selecting this option enables a menu from which you choose
a tracing level: None, Terse, Normal, Verbose Initialization,
or Verbose Data.

Optional

Required if the session uses pre- or post-session stored


procedures.
If you select Stop Session, the Informatica Server stops the
session on errors executing a pre-session or post-session
stored procedure.
If you select Continue Session, the Informatica Server
continues the session regardless of errors executing presession or post-session stored procedures.
By default, the Informatica Server stops the session on
Stored Procedure error and marks the session failed.

On PreSession
Command
Task Error

On Pre-Post
SQL Error

Optional

Required if the session has pre-session shell commands.


If you select Stop Session, the Informatica Server stops the
session on errors executing pre-session shell commands.
If you select Continue Session, the Informatica Server
continues the session regardless of errors executing presession shell commands.
By default, the Informatica Server stops the session upon
error.

Optional

Required if the session uses pre- or post-session SQL.


If you select Stop Session, the Informatica Server stops the
session errors executing pre-session or post-session SQL.
If you select Continue, the Informatica Server continues the
session regardless of errors executing pre-session or postsession SQL.
By default, the Informatica Server stops the session upon
pre- or post-session SQL error and marks the session failed.

You might also like