Transformation is a repository object that generates, modifies, or passes data.

Passive Transformations -----------------------Expression Lookup Input/Output SQL (Active also) HTTP Stored Procedure Seq Generator Source Qualifier ---------------SQL Query UserDefined Join Source Filter Select Distinct Number of Sorted Ports- adds an ORDER BY clause

Joiner Transformation ---------------------- two related heterogeneous sources - to join 3 sources we need 2 joiner t/fs. - join type> Normal, Master Outer, Detail Outer and Full Outer - Joiner Data Cache size > default 2,000,000 bytes - Joiner Index Cache Size > default 1,000,000 bytes - Sorted Input > Specifies that data is sorted - Transformation Scope> Specifies how the Integration Service applies the transf ormation logic to incoming data. You can choose Transaction, All Input, or Row. Union Transformation -------------------- multiple input group and one output group. - does not remove duplicate rows. - can connect heterogeneous sources Filter Transformation --------------------- Discarded rows do not appear in the session log or reject files. - You can specify multiple condition using AND and OR logical operator Aggregator ---------- Aggregator Data Cache - Aggregator index Cache - output last row of each group - Sorted input Sorter ------

- casesensitive - distinct Rank -----Rank -Rank -Rank -Rank Data Cache Index Cache Port> only 1 Index> to store ranking position for each row in a group

Lookup ------ Get a related value - Perform a calculation - Update slowly changing dimension tables - With a dynamic cache, the Integration Service inserts or updates rows in the c ache during the session. Stored Procedure ---------------- for populating and maintaining databases. DBA create stored procedures to auto mate tasks that are too complicated for standard SQL statements. - You can use stored procedure to complete following task: - Check the status of a target database before loading data into it. - Determine if enough space exists in a database. - Perform a specialized calculation. - Drop and recreate indexes. - There are three type of data that pass between Integration service and stored procedure transformation: - Input/output Parameters: In stored procedure transformation, you provide val ue through input parameter and receive value through output parameter - Return values: The value returned by the procedure - Status code: notifies whether or not the stored procedure completed successf ully. - Connected and Unconnected> It either runs before or after the session, or is c alled by :SP reference qualifier in an expression transformation in the mapping. - Running Options of Stored Procedure - Normal: runs where the transformation exists in the mapping on a rowbyrow basi s. Connected stored procedures run only in normal mode. - Preload of the Source: This is useful for verifying the existence of tables o r performing joins of data in a temporary table. - Postload of the Source: This is useful for removing temporary tables. - Preload of the Target: This is useful for verifying target tables or disk spa ce on the target system. - Postload of the Target: This is useful for recreating indexes on the database . Update Strategy --------------- In Power Center, you set the update strategy at two different levels: - Within a session: you can instruct the Integration Service to either treat a

ll rows in the same way (for example, treat all rows inserts), or use instructio ns coded into the mapping to flag rows for different database operations. - Within a mapping: Within a mapping, you use the Update Strategy transformati on to flag rows for insert, delete, update, or reject. - You can define how to flag rows for Update strategy when you configure a sessi on. You can flag all rows for insert, delete, or update, or you can select the data driven option, where the Integration Service follows instructions coded into Update Strategy transformations within the mapping. Insert Update Delete Reject DD_INSERT DD_UPDATE DD_DELETE DD_REJECT 0 1 2 3

Transaction Control ------------------>> A transaction is the set of rows bound by commit or rollback rows. In Power Center, you define transaction control at two levels: - Within a mapping: You define transactions using an expression in a Transaction Control transformation. Based on the return value of the expression, you can ch oose to commit, roll back, or continue without any transaction changes. - Within a session: When you configure a session, you configure it for userdefin ed commit. You can choose to commit or roll back a transaction if the Integratio n Service fails to transform or write any row to the target. When you run the session, the Integration Service evaluates the expression for e ach row that enters the transformation. When it evaluates a commit row, it commi ts all rows in the transaction to the target or targets. TC_CONTINUE_TRANSACTION >default value of the expression TC_COMMIT_BEFORE> commits the transaction, begins a new transaction, and writes the current row to the target. The current row is in the new transaction. TC_COMMIT_AFTER> writes the current row to the target, commits the transaction, and begins a new transaction. The current row is in the committed transaction. TC_ROLLBACK_BEFORE> rolls back the current transaction, begins a new transaction , and writes the current row to the target. The current row is in the new transa ction. TC_ROLLBACK_AFTER> writes the current row to the target, rolls back the transact ion, and begins a new transaction. The current row is in the rolled back transac tion. Normalizer ---------For a cobol source 2 columns are created- Generated Key: a port generated for each REDEFINES clause to specify the gener ated key. - Use the generated key as a primary key column in the target table and to cre ate a primaryforeign key relationship. - GK_<redefined_field_name> - Generated Column ID: a port generated for each OCCURS clause to specify the po sitional index within an OCCURS clause. - Use the generated column ID to create a primaryforeign key relationship.

- GCID_<occuring_field_name> Sequence Generator ------------------ to create unique primary key values - replace missing primary keys - cycle through a sequential range of numbers. NEXTVAL: Connect NEXTVAL to multiple transformations to generate unique values f or each row in each transformation. ------CURRVAL: CURRVAL is NEXTVAL plus the Increment By value. You typically only conn ect the CURRVAL port when the NEXTVAL port is already connected to a downstream transformation. >> You might reuse a Sequence Generator when you perform multiple loads to a sin gle target. SQL Transformation ------------------> it processes SQL queries midstream in a pipeline. You can insert, delete, upda te, and retrieve rows from a database > processes the query and returns rows and database errors. >> Script mode : runs SQL scripts that are externally located. You pass a script name to the transformation with each input row. The SQL transformation outputs one row for each input row. - An SQL transformation running in script mode runs SQL scripts from text file s. You pass each script file name from the source to the SQL transformation Scri pt Name port. The script file name contains the complete path to the script file. - When you configure the transformation to run in script mode, you create a pa ssive transformation. The transformation returns one row for each input row. The output row contains results of the query and any database error. - When the SQL transformation runs in script mode, the query statement and que ry data do not change. When you need to run different queries in script mode, yo u pass the scripts in the source data. Use script mode to run data definiti on queries such as creating or dropping tables. >> Query mode : The SQL transformation executes a query that you define in a que ry editor. You can pass strings or parameters to the query to define dynamic que ries or change the selection parameters. You can output multiple rows when the query has a SELECT statement. - When an SQL transformation runs in query mode, it executes an SQL query that you define in the transformation. You pass strings or parameters to the query f rom the transformation input ports to change the query statement or the quer y data. - When you configure the SQL transformation to run in query mode, you create a n active transformation. The transformation can return multiple rows for each in put row. HTTP Transformation ------------------- enables you to connect to an HTTP server to use its services and applications.

> Read data from an HTTP server : passes the data to the target or > Update data on the HTTP server: TP server responses to the target

it retrieves the data from the HTTP server and a downstream transformation in the mapping. it posts data to the HTTP server and passes HT or a downstream transformation in the mapping.

GET - Reads data from an HTTP server POST - Writes data from multiple input port to the HTTP server SIMPLE POST - Simplified version of POST method. Writes data from one input por t as a single block of data to the HTTP server - Configure groups and ports: - Manage HTTP request/response body and header details by configuring input an d output ports. - You can also configure port names with special characters. - Configure a base URL: - Configure the base URL for the HTTP server you want to connect to. Java Transformation ------------------- You can use Java transformation API methods and standard Java language constru cts. - As I to - As fter an active transformation : You must use Java transformation generate Row AP generate an output row. a passive transformation : Passive transformations generate an output row a processing each input row.

- Use the Java Code tab to define, compile, and fix compilation errors in Java c ode. - A Java transformation can have input ports, output ports, and input/output por ts. You create and edit groups and ports on the Ports tab. - You can specify default values for ports. - When you create a Java transformation, it includes one input group and one out put group. Transformations that are not supported in mapplet are: 1. Normalizer 2. Cobol sources 3. xml sources 4. xml SQ 5. Target definition 6. Pre and post session stored procedures 7. other mapplets