On this page
Informatica PowerCenter
Prepare Informatica PowerCenter inputs for a data estate, collect the relevant dependencies, and verify the scope represented in Understand.
modernAIze supports Informatica PowerCenter as a data estate source platform. Prepare exports that cover the selected mappings and their execution context. A mapping’s transformations describe the processing, while reusable objects, parameters, and workflow context help explain how that processing is used. This guide concerns Informatica PowerCenter.
Inputs to prepare
PowerCenter repository XML exports. Parameter files (.par) and delimited sample data (.csv, .dat, .txt)
can accompany them; .xlsx is available for supporting dictionary material.
The uploader also admits .sql, .dtd, and .ctrfl, but this does not
establish standalone analysis of those formats. Retain such files for manual
source review and ensure the repository XML includes the relevant definitions.
Upload supporting .xlsx workbooks through Files or Folder, separately
from ZIP archives. Keep native source alongside the workbook; see
upload batches.
Native assets and what to collect
| Asset | Material to supply | What it contributes |
|---|---|---|
| Mapping | PowerCenter XML export | Sources, targets, transformations, ports, and connections |
| Mapplet or reusable transformation | Its definition in the repository export | Reused logic referenced by mappings |
| Source and target definition | Exported repository definitions | Field structure and source/target identity |
| Workflow and session | Their exported definitions | Execution relationships and session context |
| Parameter file | .par file | Values used to interpret parameterized processing |
| Associated SQL and definitions | Retain relevant .sql, .dtd, or .ctrfl files with the handover | Manual context; upload acceptance does not guarantee interpretation as standalone source |
| Sample data | Approved delimited .csv, .dat, or .txt files | Sample columns associated with the export, not arbitrary text notes |
| Dictionary | Supporting .xlsx workbook, uploaded separately | Dictionary context |
Use a PowerCenter repository export, not an arbitrary XML document. Selecting a mapping without its reusable objects can leave references whose implementation is not present in the package.
How to collect the inputs
Export the selected objects through PowerCenter’s native repository tooling. Include the dependent objects needed for the assessment, then collect parameter files and associated SQL from their controlled locations. A native export is the collection route; this preparation does not require a separate modernAIze extractor.
Preserve repository and folder context where names repeat. Review parameter files for connection secrets before transfer, and record the execution values that change behavior. Support for PowerCenter exports does not imply that another Informatica product’s package has the same structure.
Prepare the source
- Identify the mappings and outputs to assess in the selected repository revision.
- Collect the XML export and the relevant source, target, and reusable object definitions.
- Include parameter files and associated SQL needed to interpret the mapping and session behavior.
- List referenced objects or external processes that remain outside the export.
Investigate the analysis
Follow sources through mapping transformations to targets. Inspect expressions, lookups, joins, filters, and reusable mapping logic where they affect the chosen output. Use workflow and parameter context to establish which variant of that processing the assessment describes.
Start with Briefing for the system-level explanation, then use the appropriate Landscape view and available Detail links to investigate the relevant processing. Keep the question tied to the supplied source revision.
Example review question
The following example is synthetic.
For monthly revenue, identify the mapping that produces the monthly target and the lookup or expression used for currency conversion. Check whether parameter values select a different source or rate set in the intended execution.
Verify the scope
Confirm that expected mappings and source-to-target relationships are represented. If a reusable object is referenced but its definition is absent, return to the export scope. If a parameter determines behavior, retain the approved value or interpretation with the assessment.