37ESS - Setting Enterprise Integration Manager Options

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 15

Essentials (Siebel 7.

7)

Module 37: Setting Enterprise


Integration Manager Options
Module Objectives

After completing this module you will be able to:


 Use configuration file parameters to enhance performance
 Set troubleshooting flags
 Run deletes
 Extend interface (EIM) tables to support base table
column extensions

 Why you need to know:


 To reduce time spent importing data
 To troubleshoot import problems successfully
 To leverage the full capabilities of EIM

Module 37: Setting Enterprise Integration Manager Options 2 of 15


0/3

Configuration (.ifb) Parameters


 Use enhanced configuration parameters to speed EIM
processing and reduce elapsed time
 Process options
 Import options
 Explicit and implicit primaries

Module 37: Setting Enterprise Integration Manager Options 3 of 15


1/3

Process Options
 Explicitly include or exclude tables and columns to avoid
unnecessary processing
 Use ONLY BASE TABLES, ONLY BASE COLUMNS
or
 Use IGNORE BASE TABLES, IGNORE BASE COLUMNS
 Example:
Directs task to process only
these target tables

Module 37: Setting Enterprise Integration Manager Options 4 of 15


1/3

Process Options Continued


 Set options to control processing and enhance performance
 Set USING SYNONYMS to FALSE to avoid unnecessary
processing
 USING SYNONYMS applies to accounts only
 Use SHELL to process multiple EIM tables/sections in a single
run
 Example:

Directs task to
ignore account
synonyms

Module 37: Setting Enterprise Integration Manager Options 5 of 15


2/3

Import Options
 Set options to preprocess EIM rows and columns
 Use FILTER QUERY to select a subset of EIM rows for
processing
 Use DEFAULT COLUMN or FIXED COLUMN to set values for
EIM columns
 Example:

EIM column,
operator, and value

Module 37: Setting Enterprise Integration Manager Options 6 of 15


3/3

Setting Primaries
 Improves performance by eliminating sub-queries when
displaying data from Parent and Child tables
 If primaries are not used, a new query needs to be executed to
identify any Child records each time a Parent record is displayed
 Two types of Primary settings:
 Explicit Primary
 Implicit Primary

Module 37: Setting Enterprise Integration Manager Options 7 of 15


3/3

Explicit Primaries
 Use the Primary flag to set explicit primaries through EIM
 Use when the external system knows which child should be
primary

EIM_ACCOUNT
EIM table
NAME ADDR_ADDR ADDR_CITY ACC_PR_ADDR
Acme Elm Street Boston Set the PFK to point
Acme Main Street San Mateo Y to this child data

S_ORG_EXT S_ADDR_ORG
ROW_ID NAME PR_ADDR_ID OU_ID ROW_ID ADDR CITY
A Acme 3333 A 1111 Elm Street Boston
A 3333 Main Street San Mateo
Base tables

Module 37: Setting Enterprise Integration Manager Options 8 of 15


3/3

Implicit Primaries
 Allow EIM to implicitly set primaries
 Use when the external system does not know the primary
 Sets the primary to be the child with the lowest ROW_ID
 Mimics auto primary in the application

EIM EIM_ACCOUNT
table
NAME ADDR_ADDR ADDR_CITY
Acme Elm Street Boston
Acme Main Street San Mateo

S_ORG_EXT S_ADDR_ORG
ROW_ID NAME PR_ADDR_ID OU_ID ROW_ID ADDR CITY
A Acme 1111 A 1111 Elm Street Boston
A 3333 Main Street San Mateo
Base tables
Module 37: Setting Enterprise Integration Manager Options 9 of 15
Set Troubleshooting Flags
 Job parameters can override component-level event logging to
create additional information in the log
 Trace Flags = 1
 Records processing steps
 SQL Trace Flags = 8
 Records summary SQL
 Should only be done in test
environment
 Dramatically impedes EIM
performance and generates
large log file
 Error Flags = 1
 Records details regarding
failed rows

Module 37: Setting Enterprise Integration Manager Options 10 of 15


Run Deletes
 To eliminate records produced by incorrect runs or to delete
unneeded data
 Example:

Deletes rows from


S_PROD_INT that match
rows on EIM_PROD_INT that
match the criteria

Module 37: Setting Enterprise Integration Manager Options 11 of 15


Populate Extension Columns
 To populate base table extension columns through EIM:
 Add an extension column to the EIM table
 Map the EIM column to the base column
 Test the mapping by running EIM on the server
 Use the Interface Table Mapping wizard

EIM Base
table table

EIM Base
Extension Extension
Column Column

Module 37: Setting Enterprise Integration Manager Options 12 of 15


Create Mappings for Extension Columns and Tables
 Update EIM table mappings to include columns or tables you
have added using the Interface Table Mapping wizard
 Select the table in Tools, right-click, select EIM Table
Mapping… and complete the wizard

Specify base table Specify a unique prefix for interface table


columns created for mapping extension columns

Select the interface table you want


to map to the extension table or column

Module 37: Setting Enterprise Integration Manager Options 13 of 15


Summary

This module showed you how to:


 Use configuration file parameters to enhance performance
 Set troubleshooting flags
 Run deletes
 Extend interface (EIM) tables to support base table
column extensions

Module 37: Setting Enterprise Integration Manager Options 14 of 15


Lab
 In the lab you will:
 Load product data into the interface table
 Import product data from the interface table to base tables using
enhanced configuration parameters and troubleshooting flags
 Delete product data from the interface table

Module 37: Setting Enterprise Integration Manager Options 15 of 15

You might also like