Informatica PowerCenter Essentials

Power Center Server consists of the Repository Server and Repository Database. The Repository Server manages connections and metadata storage, while the Repository Database stores all metadata objects. Repository Manager is a client tool for accessing the repository, not a server component.

Repository Manager allows you to view mapping dependencies through the Repository Navigator. You can expand mappings and see their dependencies on sources, targets, transformations, and other objects. This is essential for impact analysis before making changes.

A Shortcut dynamically reflects changes made to the original object. If you modify the source definition or transformation that the shortcut references, those changes automatically appear in all mappings using the shortcut. A Copy creates an independent duplicate that doesn't reflect changes.

The correct design process order is: first create source and target definitions, then build the mapping that connects them. Next, create a session task to define runtime parameters for the mapping, then wrap it in a workflow. After running, monitor and verify results. Creating workflow before session is incorrect because sessions are task components within workflows.

The Joiner transformation joins heterogeneous sources from different databases or flat file systems. Unlike Source Qualifier which can only join data from the same source, Joiner can combine data from different source types. It performs joins after data has been extracted from sources.

Expression transformation performs row-level calculations, applying logic to each row of data passing through it. It can create new ports, modify existing values, and apply functions like concatenation or arithmetic operations. Field-level would mean per-column (which doesn't make sense as a concept), and batch-level implies aggregation which Aggregator does.

Router transformation conditionally splits rows into multiple groups based on different filter conditions. Unlike Filter which drops rows not matching a single condition, Router can route rows to different downstream groups based on multiple conditions, with all rows being processed (either routed or passed through default group).

Rank transformation limits records to top or bottom of a range based on a specified port and ranking criteria. You can configure it to pass only the top N or bottom N records per group. Aggregator summarizes data, Expression calculates values, and Lookup fetches related data; none perform ranking by range.

Workflow Monitor provides two main views: Gantt Chart view shows task execution timelines and dependencies visually, while Task view shows task status and details in a tabular format. Both views are essential for monitoring different aspects of workflow execution and troubleshooting performance issues.

In Workflow Monitor, you can Reset a failed workflow to rerun it from the beginning, and Stop a running workflow. Debug is done in the Workflow Designer, not Workflow Monitor. Reset is used after failures, Stop is for terminating currently running workflows.

MAX is a valid aggregate function that returns the maximum value in a group. Group By is not a function but a clause that defines how data is grouped. Is Null is a conditional function, not an aggregate function. Other aggregate functions include SUM, COUNT, AVG, MIN, etc.

Sorting input data according to Group By ports significantly improves Aggregator performance. When data is pre-sorted, the aggregator doesn't need to build and manage a large aggregate cache in memory; it can process groups sequentially. Passing unsorted data requires caching all rows until all groups are complete, increasing memory usage and processing time.

The Filter transformation in Informatica PowerCenter is classified as Active because it can change the number of rows passing through it by filtering out records based on a condition. It is Connected because it requires data flow through input and output ports and cannot operate standalone like unconnected transformations.

The Aggregate transformation in Informatica has three types of ports: Input ports receive incoming data, Output ports return aggregated results, and Variable ports store intermediate calculations during aggregation. These ports work together to perform group-by calculations like sums, averages, and counts.

This statement is false. Aggregator transformations can handle both sorted and unsorted data. When data is sorted, the aggregator can optimize performance by grouping sorted rows, but it can also handle unsorted data by sorting it internally or using cache for grouping operations.

The Joiner transformation in Informatica supports four types of joins: Normal join (inner join), Master Outer join (preserves all master rows), Detail Outer join (preserves all detail rows), and Full Outer join (preserves all rows from both sources). These options provide flexibility for different data integration scenarios.

The Joiner transformation specifically accepts input from heterogeneous (different) sources, which is its primary purpose - joining data from different source types or systems. Options A, C, and D describe homogeneous sources (same source type), which would typically use a different join strategy. Option E is incorrect because Update Strategy transformations don't prevent Joiner usage.

Target definition ports cannot be edited in the Mapping Designer - they must be edited in the Target Designer first. This is by design to maintain consistency between the actual target definition in the repository and its usage in mappings. You can only view and use target ports in mappings, not modify them.

In Informatica PowerCenter, data flows through transformations via ports - input ports receive data, output ports pass transformed data, and variable ports store intermediate values. Ports act as the interface points where data enters, exits, or is processed within a transformation.

The Repository Manager is used for creating and managing folders in the PowerCenter repository, while the Admin Console handles administrative tasks like user management and service configuration. Workflow Manager is for workflow design, not folder administration.