Rules and Guidelines for the PowerCenter XML File
Use the following rules and guidelines for the PowerCenter XML file used for a mapplet:
- •The XML file must contain exactly one workflow, session, mapping, and mapplet.
- •The PowerCenter workflow must contain a valid session and mapping.
- •The PowerCenter session can use any type of connection. However, it is easier if the session uses flat file connections for the source and target.
- •You do not have to map all source and target fields in the PowerCenter mapping.
- •The PowerCenter mapping can contain the following supported transformations:
- - Aggregator transformation
- - Expression transformation
- - Filter transformation
- - HTTP transformation
- - Lookup transformation
- - Salesforce Lookup transformation (multiple matches returns a single match)
- - Salesforce Picklist transformation
- - Salesforce Merge transformation
- - Sorter transformation
- - Stored procedure transformation with exception handling
- - Transaction Control transformation
- - Web Services consumer transformation
- - XML Generator transformation with flat file or database sources
- - XML Parser transformation with flat file or database sources
- •If the PowerCenter mapping or mapplet contains a Stored Procedure transformation, the stored procedure must include exception handling.
- •If you use the mapplet in a Data Synchronization task, the underlying PowerCenter mapplet cannot contain multiple Input transformations.
- •If you use the mapplet in a Mapping Configuration task, the PowerCenter mapplet can contain multiple Input transformations.
Note: Informatica Cloud flattens PowerCenter mapplets with multiple input groups into mapplets with one input group. Therefore, the ports in each input group in the PowerCenter mapplet must have unique names. If the names are not unique, rename the input ports in PowerCenter before you export the workflow XML file that contains the mapplet.