![AGENDA ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (19)
Similar to Informatica Power Center 7.1
Similar to Informatica Power Center 7.1 (20)
More from ganblues
Recently uploaded
Recently uploaded (20)
Informatica Power Center 7.1
- 1. INFORMATICA POWER CENTER 7.1
- 10. Questions???
- 11. INFORMATICA SERVER & DATA MOVEMENT
- 18. DTM THREADS
- 21. Questions???
- 27. Questions???
- 50. Questions???
- 51. DESIGNER
- 52. SCREEN SHOT OF DESIGNER
- 69. Questions???
- 70. TRANSFORMATIONS USED IN INFORMATICA
- 99. COMPARING ROUTER & FILTER TRANSFORMATIONS
- 127. Questions???
- 128. RE – USABLE TRANSFORMATIONS AND MAPPLETS
- 131. SAMPLE MAPPLET IN A MAPPING
- 132. EXPANDED MAPPLET
- 134. Questions???
- 135. WORKFLOW MANAGER & WORKFLOW MONITOR
- 138. WORKFLOW MANAGER – SCREEN SHOT
- 141. CREATE TASK
- 143. WORKFLOW MONITOR – GANTT CHART
- 144. WORKFLOW MONITOR – TASK VIEW
- 146. Questions???
- 147. PERFORMANCE TUNING
- 163. COMMIT POINTS
- 166. Questions???
- 167. DEBUGGER
- 169. DEBUGGER
- 172. Questions???
- 173. INFORMATICA POWERCENTER 7.1 ENHANCEMENTS This Presentation part describes new features and enhancements to Informatica PowerCenter version 7.0. forming Informatica PowerCenter version 7.1
- 186. Applications / Database / DataMarts / Legacy Systems / Real Time Profiling Access Via Designer / Wizard Profile Rules Mapping INFORMATICA POWERCENTER Profiling Warehouse In PowerCenter In PowerAnalyser In 3 rd Party reporting tool Reports Data Profiling Built into PowerCenter
Editor's Notes
- Global repository. The global repository is the hub of the domain. Use the global repository to store common objects that multiple developers can use through shortcuts. These objects may include operational or application source definitions, reusable transformations, mapplets, and mappings. Local repositories. A local repository is within a domain that is not the global repository. Use local repositories for development. From a local repository, you can create shortcuts to objects in shared folders in the global repository. These objects typically include source definitions, common dimensions and lookups, and enterprise standard transformations. You can also create copies of objects in non-shared folders.
- Global repository. The global repository is the hub of the domain. Use the global repository to store common objects that multiple developers can use through shortcuts. These objects may include operational or application source definitions, reusable transformations, mapplets, and mappings. Local repositories. A local repository is within a domain that is not the global repository. Use local repositories for development. From a local repository, you can create shortcuts to objects in shared folders in the global repository. These objects typically include source definitions, common dimensions and lookups, and enterprise standard transformations. You can also create copies of objects in non-shared folders.
- The Figure shows the processing path between the Informatica Server, repository, source, and target
- The Informatica Server can combine data from different platforms and source types. For example, you can join data from a flat file and an Oracle source, and write the transformed data to a Microsoft SQL Server database. When a session starts, the Informatica Server retrieves mapping and session metadata from the repository to extract data from the source, transform it, and load it into the target. The Informatica Server can combine data from different platforms and source types
- The Informatica Server can combine data from different platforms and source types. For example, you can join data from a flat file and an Oracle source, and write the transformed data to a Microsoft SQL Server database. When a session starts, the Informatica Server retrieves mapping and session metadata from the repository to extract data from the source, transform it, and load it into the target. The Informatica Server can combine data from different platforms and source types
- The Load Manager is the primary Informatica Server process
- The Load Manager holds the connection to the repository for the value set in the Informatica Server configuration, LMStayConnectToRepositDuration When you start the Informatica Server. When you start the Informatica Server, the Load Manager launches and queries the repository for a list of sessions configured to run on the Informatica Server. When you configure a session. When you add, update, or schedule a session in the Server Manager, the repository stores all the session metadata. The Load Manager maintains a list of sessions and session start times. When a session starts. When a session starts, the Load Manager fetches the session information from the repository to perform the validations and verifications prior to starting the DTM process. The execute lock allows the Informatica Server to run the session and prevents you from starting the session again until it completes. If the session is already locked, the Informatica Server cannot start the session. A session may be locked if it is already running, or if an error occurred during the previous run that prevented the repository from releasing the execute lock.
- Four transformation threads. The DTM creates one transformation thread for each partition. The DTM creates an additional transformation thread for partition for each Aggregator or Rank transformation. So, the DTM creates four transformation threads to process the mapping in Figure above.
- Standalone repository. A repository that functions individually, unrelated and unconnected to other repositories. Global repository. (PowerCenter only.) The centralized repository in a domain, a group of connected repositories. Each domain can contain one global repository. The global repository can contain common objects to be shared throughout the domain through global shortcuts. Once created, you cannot change a global repository to a local repository. You can promote an existing local repository to a global repository. Local repository. (PowerCenter only.) A repository within a domain that is not the global repository. Each local repository in the domain can connect to the global repository and use objects in its shared folders. A folder in a local repository can be copied to other local repositories while keeping all local and global shortcuts intact.
- When restoring a repository, you must have a database available for the repository. You can restore the repository in a database that has a different code page from the original database, if the code pages are compatible. If a repository already exists at the location, the Repository Manager asks you to delete the repository before restoring a backup repository. If no repository exists, the Repository Manager creates a repository before restoring the backup repository.
- Source and target dependencies report (S2t_dep.rpt) - Shows the source and target dependencies as well as the transformations performed in each mapping
- Write lock - Created when you create or edit a repository object in a folder for which you have write permission Execute lock - Created when you start a session or batch, or when the Informatica Server starts a scheduled session or batch Save lock - Created when you save information to the repository The repository permits multiple read locks, one write lock, and one execute lock simultaneously on each repository object. This means that one user can edit a session while the Informatica Server runs the session, and another user can view the session properties at the same time. You can view existing locks in the repository in the Repository Manager. The Repository Manager provides two ways to view locks: Browse the repository. Use the Navigator and main windows to display the folders, versions, and objects in use. Show locks. Use a menu command to view all locks in the repository. This method provides more detailed information and allows you to sort your view of the locks.
- You must create a folder in a new repository before you can connect to the repository using the Designer or Workflow Manager. You can copy objects from one folder to another, so if you want to use an object in a non-shared folder, you can copy it into your working folder. If you work with multiple repositories, you can also copy objects across repositories. You can continue working in the new version, while preserving the older version. You might use versions to archive work while continuing with development.
- In your repository, you might create folders for each data warehouse development project, subject area, user, or type of metadata. If you can divide the data warehouse into different types of information, you might create a single folder for each type of data. For instance, when you set up the accounting data warehouse, you might create one folder for accounts payable and another for accounts receivable. You can create a folder for each repository user, designed to store work for that user only. If users work on separate projects, this technique avoids any problems that might occur if two people attempt to edit the same piece of metadata at the same time. You might create a different folder for each type of metadata (source definitions, target definitions, mappings, schemas, and reusable transformations) that you create through the Designer.
- When you copy a folder from a global repository to a local repository in the same domain, the Repository Manager verifies whether a folder of the same name exists in the global repository. If it does not, the Repository Manager uses the folder name for the copied folder. If it does, the Repository Manager asks you to rename the folder. The Repository Manager preserves shortcuts to shared folders in the global repository, changing the local shortcuts to global shortcuts. When you copy both a shared folder and a non-shared folder with dependent shortcuts across repositories and then recopy the shared folder from the source repository, the shortcuts in the non-shared folder in the target repository point to the folder in the source repository. The shortcuts in the non-shared folder always point to the folder you select when you copy/replace a shared folder.
- Re-establish shortcuts. Maintain shortcuts to objects in shared folders. If the Repository Manager cannot re-establish shortcuts, it marks the affected mappings, mapplets, and sessions invalid in the repository and lists them in the Output window. Choose an Informatica Server. Use the Informatica Server to run all sessions and batches in the folder if a matching Server does not exist in the target repository. Copy connections. Copy database, FTP, and external loader connection information if matching connection names do not exist in the target repository. Copy persisted values. Copy the saved persisted values for mapping variables used in a session. Compare folders. Compare folders to determine how they are related with the compare folders functionality. Replace folders. Replace an existing folder, including all objects associated with the folder. The Repository Manager copies and replaces folders as a single transaction. If you cancel the copy before it completes, the Repository Manager rolls back all changes.
- Versions to compare. The wizard automatically selects pairs of versions with the same version number in each folder for comparison. You can also specify the versions to compare in each folder. Object types to compare. You can specify the object types to compare and display between folders. The Repository Manager compares objects based upon specific object attributes. See Table 6-3 for a list of compared attributes for object types. Direction of comparison. The Repository Manager performs directional comparisons. A directional comparison checks the contents of one folder against the contents of the other. You can specify either one-way or two-way comparisons.
- Figure shows two folders in the same repository, Orders1 and Orders2. If you compare the folders using a one-way comparison, the source definition ORDER_ITEMS, present in Orders2 but not in Orders1, is not noted as a comparison. If you compare the folders using a two-way comparison, the absence of ORDER_ITEMS in Orders1 is noted as a difference.
- Because sessions and batches are not associated with version numbers, the version pairs specified in the Versions to compare list do not impact a comparison of sessions or batches. If you want to compare only sessions and batches, you can accept the default version pairs without affecting the outcome of the comparison. The Repository Manager does not compare the field attributes of the objects in the folders when performing the comparison. For example, if two folders that have matching source names and column or port names but differing port or column attributes, such as precision or datatype, the Repository Manager does not note these as different.
- Can delete a folder version to remove unnecessary versions from the repository By archiving the contents of a folder into a version each time you reach a development landmark, you can access those versions if later edits prove unsuccessful. For example, you can create a folder version after completing a version of a difficult mapping, then continue working on the mapping. If you are unhappy with the results of subsequent work, you can revert to the previous version, then create a new version to continue development. Thus you keep the landmark version intact, but available for regression. When working with multiple versions, make sure you have the appropriate version active. The repository saves version information by workspace, so if someone else uses your machine and changes the active version, that version remains active on your machine until changed
- Exporting and importing an object is similar to copying an object from one folder or repository to another folder or repository. When you copy objects between folders or repositories, you must be connected to both repositories simultaneously. However, when you export an object from one repository and import the object into another repository, you do not need to connect to both repositories simultaneously. You might want to export an object in any of the following circumstances: You want to copy an object between two repositories, but you cannot connect to both repositories from the same client. Export the object and electronically transfer the XML file to the target machine. Then import the object from the XML file into the target repository. You previously copied a mapping or mapplet that uses a reusable transformation to another repository. Then later you changed the reusable transformation. Instead of copying the entire mapping or mapplet again, you can export and import the reusable transformation. You want to export an object from your development repository and deploy it in the production repository. You have an invalid session that you need to troubleshoot. Export the invalid session and its associated mapping, electronically transfer the XML file to someone else for troubleshooting.
- To import a source definition: In the Source Analyzer, choose Sources-Import from Database. Select the ODBC data source used to connect to the source database. If you need to create or modify an ODBC data source, click the Browse button to open the ODBC Administrator. Create the appropriate data source and click OK. Select the new ODBC data source. Enter a database username and password to connect to the database. Note: The username must have the appropriate database permissions to view the object. You may need to specify the owner name for database objects you want to use as sources. Click Connect. If no table names appear or if the table you want to import does not appear, click All. Drill down through the list of sources to find the source you want to import. Select the relational object or objects you want to import. You can hold down the Shift key to select blocks of record sources within one folder, or hold down the Ctrl key to make non-consecutive selections within a folder. You can also select all tables within a folder by selecting the folder and clicking the Select All button. Use the Select None button to clear all highlighted selections.
- When you create a flat file source definition, you must define the properties of the file. The Source Analyzer provides a Flat File Wizard to prompt you for the above mentioned file properties. You can import fixed-width and delimited flat file source definitions that do not contain binary data. When importing the definition, the source file must be in a directory local to the client machine. In addition, the Informatica Server must be able to access all source files during the session.
- You can create the overall relationship, called a schema , as well as the target definitions, through wizards in the Designer. The Cubes and Dimensions Wizards follow common principles of data warehouse design to simplify the process of designing related targets.
- Connectors - Connect sources, targets, and transformations so the Informatica Server can move the data as it transforms it A mapplet is a set of transformations that you build in the Mapplet Designer and can use in multiple mappings
- When you edit and save a mapping, some changes cause the session to be invalid even though the mapping remains valid. The Informatica Server does not run invalid sessions
- The Designer marks a mapping invalid when it detects errors that will prevent the Informatica Server from executing the mapping The Designer performs connection validation each time you connect ports in a mapping and each time you validate or save a mapping. At least one mapplet input port and output port is connected to the mapping. If the mapplet includes a Source Qualifier that uses a SQL override, the Designer prompts you to connect all mapplet output ports to the mapping. You can validate an expression in a transformation while you are developing a mapping. If you did not correct the errors, the Designer writes the error messages in the Output window when you save or validate the mapping. When you validate or save a mapping, the Designer verifies that the definitions of the independent objects, such as sources or mapplets, match the instance in the mapping. If any of the objects change while you configure the mapping, the mapping might contain errors.
- Example of an active transformation is a Filter transformation that removes rows that do not meet the configured filter condition. Example of a passive transformation is an an Expression transformation that performs a calculation on data and passes all rows through the transformation An unconnected transformation is not connected to other transformations in the mapping. It is called within another transformation, and returns a value to that transformation.
- The Informatica Server performs aggregate calculations as it reads, and stores necessary data group and row data in an aggregate cache Aggregate expression - Entered in an output port, can include non-aggregate expressions and conditional clauses Group by port - Indicates how to create groups. can be any input, input/output, output, or variable port Sorted Input option - Use to improve session performance. To use Sorted Input, you must pass data to the Aggregator transformation sorted by group by port, in ascending or descending order Aggregate cache - Aggregator stores data in the aggregate cache until it completes aggregate calculations. It stores group values in an index cache and row data in data cache
- You can enter multiple expressions in a single Expression transformation. As long as you enter only one expression for each output port, you can create any number of output ports in the transformation. In this way, you can use one Expression transformation rather than creating separate transformations for each calculation that requires the same set of data.
- As an active transformation, the Filter transformation may change the number of rows passed through it. A filter condition returns TRUE or FALSE for each row that passes through the transformation, depending on whether a row meets the specified condition. Only rows that return TRUE pass through this transformation. Discarded rows do not appear in the session log or reject files. To maximize session performance, include the Filter transformation as close to the sources in the mapping as possible. Rather than passing rows you plan to discard through the mapping, you then filter out unwanted data early in the flow of data from sources to targets. You cannot concatenate ports from more than one transformation into the Filter transformation. The input ports for the filter must come from a single transformation. The Filter transformation does not allow setting output default values.
- Allows to join sources that contain binary data To join more than two sources in a mapping, add additional Joiner transformations An input transformation is any transformation connected to the input ports of the current transformation. Specify one of the sources as the master source, and the other as the detail source. This is specified on the Properties tab in the transformation by clicking the M column. When you add the ports of a transformation to a Joiner transformation, the ports from the first source are automatically set as detail sources. Adding the ports from the second transformation automatically sets them as master sources. The master/detail relation determines how the join treats data from those sources based on the type of join. For example, you might want to join a flat file with in-house customer IDs and a relational database table that contains user-defined customer IDs. You could import the flat file into a temporary database table, then perform the join in the database. However, if you use the Joiner transformation, there is no need to import or create temporary tables.
- Can configure the lookup transformation to be connected or unconnected, cached or uncached
- Connected and unconnected transformations receive input and send output in different ways. Sometimes you can improve session performance by caching the lookup table. If you cache the lookup table, you can choose to use a dynamic or static cache. By default, the lookup cache remains static and does not change during the session. With a dynamic cache, the Informatica Server inserts rows into the cache during the session. Informatica recommends that you cache the target table as the lookup. This enables you to look up values in the target and insert them if they do not exist.
- NewLookupRow. The Designer automatically adds this port to a Lookup transformation configured to use a dynamic cache. Indicates whether or not the row is in lookup cache. To keep the lookup cache and the target table synchronized, you want to pass rows to the target when the NewLookupRow value is equal to 1. Associated Port. Associate lookup ports with either an input/output port or a sequence ID. The Informatica Server uses the data specified in the associated ports to insert into the lookup cache when it does not find a row in the lookup cache. If you associate a sequence ID, the Informatica Server generates a primary key for the inserted row in the lookup cache.
- The Informatica Server builds the cache when it processes the first request lookup request. It queries the cache based on the lookup condition for each row that passes into the transformation. When the Informatica Server receives a new row (a row that is not in the cache), it inserts the row into the cache. You can configure the transformation to insert rows into the cache based on input ports or generated sequence IDs. The Informatica Server flags the row as new. When the Informatica Server receives an existing row (a row that is in the cache), it flags the row as existing. The Informatica Server does not insert the row into the cache. Use a Router or Filter transformation with the dynamic Lookup transformation to route new rows to the cached target table. You can route existing rows to another target table, or you can drop them. When you partition a source that uses a dynamic lookup cache, the Informatica Server creates one memory cache and one disk cache for each transformation.
- The Router transformation is more efficient when you design a mapping and when you run a session For example, to test data based on three conditions, you only need one Router transformation instead of three filter transformations to perform this task. Likewise, when you use a Router transformation in a mapping, the Informatica Server processes the incoming data only once. When you use multiple Filter transformations in a mapping, the Informatica Server processes the incoming data for each transformation
- The Informatica Server generates a value each time a row enters a connected transformation, even if that value is not used. When NEXTVAL is connected to the input port of another transformation, the Informatica Server generates a sequence of numbers. When CURRVAL is connected to the input port of another transformation, the Informatica Server generates the NEXTVAL value plus one.
- Connect NEXTVAL to multiple transformations to generate unique values for each row in each transformation. For example, you might connect NEXTVAL to two target tables in a mapping to generate unique primary key values. The Informatica Server creates a column of unique primary key values for each target table. If you want the same generated value to go to more than one target that receives data from a single preceding transformation, you can connect a Sequence Generator to that preceding transformation. This allows the Informatica Server to pass unique values to the transformation, then route rows from the transformation to targets.
- The Source Qualifier displays the transformation datatypes. The transformation datatypes in the Source Qualifier determine how the source database binds data when you import it. Do not alter the datatypes in the Source Qualifier. If the datatypes in the source definition and Source Qualifier do not match, the Designer marks the mapping invalid when you save it.
- In the mapping shown above, although there are many columns in the source definition, only three columns are connected to another transformation. In this case, the Informatica Server generates a default query that selects only those three columns: SELECT CUSTOMERS.CUSTOMER_ID, CUSTOMERS.COMPANY, CUSTOMERS.FIRST_NAME FROM CUSTOMERS When generating the default query, the Designer delimits table and field names containing the slash character (/) with double quotes.
- In the mapping shown above, although there are many columns in the source definition, only three columns are connected to another transformation. In this case, the Informatica Server generates a default query that selects only those three columns: SELECT CUSTOMERS.CUSTOMER_ID, CUSTOMERS.COMPANY, CUSTOMERS.FIRST_NAME FROM CUSTOMERS When generating the default query, the Designer delimits table and field names containing the slash character (/) with double quotes.
- In the mapping shown above, although there are many columns in the source definition, only three columns are connected to another transformation. In this case, the Informatica Server generates a default query that selects only those three columns: SELECT CUSTOMERS.CUSTOMER_ID, CUSTOMERS.COMPANY, CUSTOMERS.FIRST_NAME FROM CUSTOMERS When generating the default query, the Designer delimits table and field names containing the slash character (/) with double quotes.
- In the mapping shown above, although there are many columns in the source definition, only three columns are connected to another transformation. In this case, the Informatica Server generates a default query that selects only those three columns: SELECT CUSTOMERS.CUSTOMER_ID, CUSTOMERS.COMPANY, CUSTOMERS.FIRST_NAME FROM CUSTOMERS When generating the default query, the Designer delimits table and field names containing the slash character (/) with double quotes.
- It determines how to handle changes to existing records When you design your data warehouse, you need to decide what type of information to store in targets. As part of your target table design, you need to determine whether to maintain all the historic data or just the most recent changes. For example, you might have a target table, T_CUSTOMERS, that contains customer data. When a customer address changes, you may want to save the original address in the table, instead of updating that portion of the customer record. In this case, you would create a new record containing the updated address, and preserve the original record with the old customer address. This illustrates how you might store historical information in a target table. However, if you want the T_CUSTOMERS table to be a snapshot of current customer data, you would update the existing customer record and lose the original address.
- It determines how to handle changes to existing records When you design your data warehouse, you need to decide what type of information to store in targets. As part of your target table design, you need to determine whether to maintain all the historic data or just the most recent changes. For example, you might have a target table, T_CUSTOMERS, that contains customer data. When a customer address changes, you may want to save the original address in the table, instead of updating that portion of the customer record. In this case, you would create a new record containing the updated address, and preserve the original record with the old customer address. This illustrates how you might store historical information in a target table. However, if you want the T_CUSTOMERS table to be a snapshot of current customer data, you would update the existing customer record and lose the original address.
- The Rank transformation differs from the transformation functions MAX and MIN, in that it allows you to select a group of top or bottom values, not just one value. For example, you can use Rank to select the top 10 salespersons in a given territory. Or, to generate a financial report, you might also use a Rank transformation to identify the three departments with the lowest expenses in salaries and overhead. While the SQL language provides many functions designed to handle groups of data, identifying top or bottom strata within a set of rows is not possible using standard SQL functions. Allows to create local variables and write non-aggregate expressions
- During a session, the Informatica Server compares an input row with rows in the data cache. If the input row out-ranks a stored row, the Informatica Server replaces the stored row with the input row. If the Rank transformation is configured to rank across multiple groups, the Informatica Server ranks incrementally for each group it finds.
- During a session, the Informatica Server compares an input row with rows in the data cache. If the input row out-ranks a stored row, the Informatica Server replaces the stored row with the input row. If the Rank transformation is configured to rank across multiple groups, the Informatica Server ranks incrementally for each group it finds.
- Limitations exist on passing data, depending on the database implementation Stored procedures are stored and run within the database. Not all databases support stored procedures, and database implementations vary widely on their syntax. You might use stored procedures to: Drop and recreate indexes. Check the status of a target database before moving records into it. Determine if enough space exists in a database. Perform a specialized calculation. Database developers and programmers use stored procedures for various tasks within databases, since stored procedures allow greater flexibility than SQL statements. Stored procedures also provide error handling and logging necessary for mission critical tasks. Developers create stored procedures in the database using the client tools provided with the database.
- You can run several Stored Procedure transformations in different modes in the same mapping. For example, a pre-load source stored procedure can check table integrity, a normal stored procedure can populate the table, and a post-load stored procedure can rebuild indexes in the database. However, you cannot run the same instance of a Stored Procedure transformation in both connected and unconnected mode in a mapping. You must create different instances of the transformation. If the mapping calls more than one source or target pre- or post-load stored procedure in a mapping, the Informatica Server executes the stored procedures in the execution order that you specify in the mapping.
- The stored procedure issues a status code that notifies whether or not the stored procedure completed successfully
- You can pass a value from a port, literal string or number, variable, Lookup transformation, Stored Procedure transformation, External Procedure transformation, or the results of another expression. Separate each argument in a function with a comma. Except for literals, the transformation language is not case-sensitive. Except for literals, the Designer and Informatica Server ignore spaces. The colon (:), comma (,), and period (.) have special meaning and should be used only to specify syntax. The Informatica Server treats a dash (-) as a minus operator. If you pass a literal value to a function, enclose literal strings within single quotation marks. Do not use quotation marks for literal numbers. The Informatica Server treats any string value enclosed in single quotation marks as a character string. When you pass a mapping parameter or variable to a function within an expression, do not use quotation marks to designate mapping parameters or variables. Do not use quotation marks to designate ports. You can nest multiple functions within an expression (except aggregate functions, which allow only one nested aggregate function). The Informatica Server evaluates the expression starting with the innermost function.
- After you save a mapplet, you can use it in a mapping to represent the transformations within the mapplet. When you use a mapplet in a mapping, you use an instance of the mapplet. Like a reusable transformation, any changes made to the mapplet are automatically inherited by all instances of the mapplet. Can use it in a mapping to represent the transformations within the mapplet
- After you save a mapplet, you can use it in a mapping to represent the transformations within the mapplet. When you use a mapplet in a mapping, you use an instance of the mapplet. Like a reusable transformation, any changes made to the mapplet are automatically inherited by all instances of the mapplet. Can use it in a mapping to represent the transformations within the mapplet
- Apply the following rules while designing mapplets: Use only reusable Sequence Generators Do not use pre- or post-session stored procedures in a mapplet Use exactly one of the following in a mapplet: Source Qualifier transformation ERP Source Qualifier transformation Input transformation Use at least one Output transformation in a mapplet
- This does not replace the Server Manager, since there are many tasks that you can perform only with the Server Manager
- Repository username. This can be configured optionally as an environment variable. Repository password. This can be configured optionally as an environment variable. Connection type. The type of connection from the client machine to the Informatica Server (TCP/IP or IPX/SPX). Port or connection. The TCP/IP port number or IPX/SPX connection (Windows NT/2000 only) to the Informatica Server. Host name. The machine hosting the Informatica Server (if running pmcmd from a remote machine through a TCP/IP connection). Session or batch name. The names of any sessions or batches you want to start or stop. Folder name. The folder names for those sessions or batches (if their names are not unique in the repository). Parameter file . The directory and name of the parameter file you want the Informatica Server to use with the session or batch.
- Target-based commit. The Informatica Server commits data based on the number of target rows and the key constraints on the target table. The commit point also depends on the buffer block size and the commit interval. Source-based commit. The Informatica Server commits data based on the number of source rows. The commit point is the commit interval you configure in the session properties.
- For example, a session is configured with target-based commit interval of 10,000. The writer buffers fill every 7,500 rows. When the Informatica Server reaches the commit interval of 10,000, it continues processing data until the writer buffer is filled. The second buffer fills at 15,000 rows, and the Informatica Server issues a commit to the target. If the session completes successfully, the Informatica Server issues commits after 15,000, 22,500, 30,000, and 40,000 rows.
- Although the Filter, Router, and Update Strategy transformations are active transformations, the Informatica Server does not use them as active sources in a source-based commit session.
- The Informatica Server might commit less rows to the target than the number of rows produced by the active source. For example, you have a source-based commit session that passes 10,000 rows through an active source, and 3,000 rows are dropped due to transformation logic. The Informatica Server issues a commit to the target when the 7,000 remaining rows reach the target. The number of rows held in the writer buffers does not affect the commit point for a source-based commit session. For example, you have a source-based commit session that passes 10,000 rows through an active source. When those 10,000 rows reach the targets, the Informatica Server issues a commit. If the session completes successfully, the Informatica Server issues commits after 10,000, 20,000, 30,000, and 40,000 source rows.
- If a session fails or if you receive unexpected results in your target, you can run the Debugger against the session You might also want to run the Debugger against a session if you want the Informatica Server to process the configured session properties
- Can create data or error breakpoints for transformations or for global conditions Cannot create breakpoints for mapplet Input and Output transformations Create breakpoints. You create breakpoints in a mapping where you want the Informatica Server to evaluate data and error conditions. Configure the Debugger. Use the Debugger Wizard to configure the Debugger for the mapping. You can choose to run the Debugger against an existing session or you can create a debug session. When you run the Debugger against an existing session, the Informatica Server runs the session in debug mode. When you create a debug session, you configure a subset of session properties within the Debugger Wizard, such as source and target location. You can also choose to load or discard target data. Run the Debugger. Run the Debugger from within the Mapping Designer. When you run the Debugger the Designer connects to the Informatica Server. The Informatica Server initializes the Debugger and runs session. The Informatica Server reads the breakpoints and pauses the Debugger when the breakpoints evaluate to true. Monitor the Debugger. While you run the Debugger, you can monitor the target data, transformation and mapplet output data, the debug log, and the session log. When you run the Debugger, the Designer displays the following windows: Debug log. View messages from the Debugger. Session log. View session log. Target window. View target data. Instance window. View transformation data. Modify data and breakpoints. When the Debugger pauses, you can modify data and see the effect on transformations, mapplets, and targets as the data moves through the pipeline. You can also modify breakpoint information.