Session Configuration Object

By Raju.Yanamamala

This chapter includes the following topics:

Session Configuration Object Overview

Advanced Settings
Log Options Settings
Error Handling Settings
Partitioning Options Settings
Session on Grid Settings
Working with a Session Configuration Object

Session Configuration Object Overview

Each folder in the repository has a default session configuration object that
contains session properties such as commit and load settings, log options, and
error handling settings. You can create multiple configuration objects if you want
to apply different configuration settings to multiple sessions.

When you create a session, the Workflow Manager applies the default
configuration object settings to the Config Object tab on the session. You can
also choose a configuration object to use for the session.

When you edit a session configuration object, each session that uses the session
configuration object inherits the changes. When you override the configuration
object settings in the Session task, the session configuration object does not
inherit changes.

Configuration Object and Config Object Tab Settings

You can configure the following settings in a session configuration object or on the
Config Object tab in session properties:

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.
Session on grid. When Session on Grid is enabled, the Integration Service
distributes session threads to the nodes in a grid to increase performance and
scalability.

Advanced Settings

Advanced settings allow you to configure constraint-based loading, lookup

caches, and buffer sizes.
Table 8-1 describes the Advanced settings of the Config Object tab:

Table 8-1. Config Object Tab - Advanced Settings

Advanced Settings Description
Constraint Based Integration Service loads targets based on primary key-
Load Ordering foreign key constraints where possible.
Cache Lookup() If selected, the Integration Service caches PowerMart 3.5
Function LOOKUP functions in the mapping, overriding mapping-
level LOOKUP configurations.
If not selected, the Integration Service performs lookups on
a row-by-row basis, unless otherwise specified in the
mapping.
Default Buffer Block Size of buffer blocks used to move data and index caches
Size from sources to targets. By default, the Integration Service
determines this value at run time.
You can specify auto or a numeric value. If you enter 2000,
the Integration Service interprets the number as 2000
bytes. Append KB, MB, or GB to the value to specify other
units. For example, you can specify 512MB.
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 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 Size or
decrease Default Buffer Block Size.
Line Sequential Buffer Affects the way the Integration Service reads flat files.
Length Increase this setting from the default of 1024 bytes per line
only if source flat file records are larger than 1024 bytes.
Maximum Memory Maximum memory allocated for automatic cache when you
Allowed for Auto configure the Integration Service to determine session
Memory Attributes cache size at run time.
You enable automatic memory settings by configuring a
value for this attribute. If you enter 2000, the Integration
Service interprets the number as 2000 bytes. Append KB,
MB, or GB to the value to specify other units. For example,
you can specify 512MB.
If the value is set to zero, the Integration Service uses
default values for memory attributes that you set to auto.
Maximum Percentage Maximum percentage of memory allocated for automatic
of Total Memory cache when you configure the Integration Service to
Allowed for Auto determine session cache size at run time. If the value is set
Memory Attributes to zero, the Integration Service uses default values for
memory attributes that you set to auto.
Additional Concurrent Enables the Integration Service to create lookup caches
Pipelines for Lookup concurrently by creating additional pipelines.
Cache Creation Specify a numeric value or select Auto to enable the
Integration Service to determine this value at run time.
By default, the Integration Service creates caches
concurrently and it determines the number of additional
 pipelines to create at run time. If you configure a numeric
value, you can configure an additional concurrent pipeline
for each Lookup transformation in the pipeline.
You can also configure the Integration Service to create
session caches sequentially. It builds a lookup cache in
memory when it processes the first row of data in a cached
Lookup transformation. Set the value to 0 to configure the
Integration Service to process sessions sequentially.
Custom Properties Configure custom properties of the Integration Service for
the session. You can override custom properties that the
Integration Service uses after the DTM process has started.
The Integration Service also writes the override value of the
property to the session log.
DateTime Format Date time format defined in the session configuration
String object. Default format specifies microseconds:
MM/DD/YYYY HH24:MI:SS.US.
You can specify seconds, milliseconds, or nanoseconds.
MM/DD/YYYY HH24:MI:SS, specifies seconds.
MM/DD/YYYY HH24:MI:SS.MS, specifies milliseconds.
MM/DD/YYYY HH24:MI:SS.US, specifies microseconds.
MM/DD/YYYY HH24:MI:SS.NS, specifies nanoseconds.
Pre 85 Timestamp Trims subseconds to maintain compatibility with versions
Compatibility prior to 8.5. The Integration Service converts the Oracle
Timestamp datatype to the Oracle Date datatype. The
Integration Service trims subsecond data for the following
sources, targets, and transformations:
-Relational sources and targets
-XML sources and targets
-SQL transformation
-XML Generator transformation
-XML Parser transformation
Default is disabled.