Integration
Informatica & Talend
Export governed mappings as Informatica PowerCenter XML or Talend .item definitions. Each export filename and embedded comment carries the source ULID and ApproverReleaseSigned entry hash, so an auditor can prove the transformation running in production matches the version a Magellan Approver actually signed.
Division of labor
Who actually does the work — SME vs. Developer
Informatica Mapping Designer is a developer surface. The semantic work — does this column mean the same thing, is the code system right, does this transformation match policy — is the work an SME is qualified to do, but cannot do there. Magellan moves that work to the SME and emits the Informatica artifact from the approved decision.
| Task | Informatica | Magellan |
|---|---|---|
| Propose source → target match | Developer in Mapping Designer | SME in Magellan UI, ranked candidates from the Semantic Match Engine |
| Justify the match | Developer comment or Confluence page | SME selects the algorithm class and rationale, captured in the audit ledger |
| Review & approve | Developer peer review | SME reviewer + SME approver, signed into the hash-chained ledger |
| Generate runtime artifact | Developer hand-builds in PowerCenter / IICS | Emitted automatically at the approved SemVer (PowerCenter XML, IICS task) |
| Run the load | Developer / ops | Same developer / ops — unchanged |
Propose source → target match
Informatica
Developer in Mapping Designer
Magellan
SME in Magellan UI, ranked candidates from the Semantic Match Engine
Justify the match
Informatica
Developer comment or Confluence page
Magellan
SME selects the algorithm class and rationale, captured in the audit ledger
Review & approve
Informatica
Developer peer review
Magellan
SME reviewer + SME approver, signed into the hash-chained ledger
Generate runtime artifact
Informatica
Developer hand-builds in PowerCenter / IICS
Magellan
Emitted automatically at the approved SemVer (PowerCenter XML, IICS task)
Run the load
Informatica
Developer / ops
Magellan
Same developer / ops — unchanged
The Informatica adapter emits PowerCenter XML for sessions, mappings, transformations, source/target definitions, and reusable transformations. The output validates against the PowerCenter XML schema for the target version (9.x and 10.x supported); the Talend adapter emits `.item` and `.properties` pairs that import cleanly into Talend Studio without re-modeling.
Every emitted artifact embeds the source mapping ULID and the ULID of the `ApproverReleaseSigned` entry that authorized the export. In Informatica XML the stamp lives in the `<DESCRIPTION>` of the top-level `MAPPING` element and in a `MAGELLAN_PROVENANCE` metadata extension; in Talend `.item` files it lives in the `<elementParameter name="DOCUMENTATION">`. A diff between the production artifact and a fresh Magellan export should be exactly zero — and if it is not, an auditor can name what changed.
The export is byte-deterministic. Re-running the export against the same mapping ULID produces a byte-identical artifact. This is what allows a CI step to assert 'the artifact in the repo matches the signed mapping' as a hash equality check, not a structural diff that has to be tolerant of whitespace.
Each export writes an `ArtifactExported` entry to the ledger carrying the mapping ULID, the target tool identifier (`Informatica/PowerCenter@10.5` or `Talend/Studio@8.0`), the artifact format, and the SHA-256 of the emitted bytes. A reviewer can replay the chain to prove which Magellan version generated which file in which Informatica or Talend project repository.
Bidirectional ingest is supported through Custom Import. An Informatica XML or Talend `.item` produced outside Magellan can be ingested back through an `ImportAdapter`, producing `MappingImported` entries with the same provenance discipline as a spreadsheet ingest. The round-trip — Magellan → Informatica → Magellan — is hash-checkable, which is the strongest property an external ETL platform can offer in a regulated environment.
When the Approver promotes a new mapping version, the export pipeline regenerates the artifact and the CI/CD step (see CI/CD Pipelines) refuses to deploy any Informatica or Talend project whose committed artifact does not hash-match the latest signed export. This closes the gap between a signed Magellan decision and the transformation that actually runs in production.
Audit ledger entries written by this capability
Each action in this capability appends one of the following entry types to the ULID‑keyed, SHA‑256 hash‑chained audit ledger. A reviewer can replay the chain to reconstruct exactly what happened, when, and under which role.
ArtifactExportedArtifactImportedApproverReleaseSignedReleasePromotedSee informatica & talend demonstrated against your data
Pick a sample dataset or bring your own. We will walk the ledger from ingest through Approver release in a single working session.
Request a demoRelated across the platform
Where this capability hands off — upstream adapters, downstream governance, and the underlying audit primitives.