Table of Contents

Search

  1. Preface
  2. Components
  3. Business services
  4. File listeners
  5. Fixed-width file formats
  6. Hierarchical schemas
  7. Intelligent structure models
  8. Mapplets
  9. Saved queries
  10. Shared sequences
  11. User-defined functions

Components

Components

PowerCenter XML files for mapplets

PowerCenter XML files for mapplets

To use a mapplet in
Data Integration
, you upload a PowerCenter XML file that defines a PowerCenter mapplet.
Consider the following rules when you use a PowerCenter XML file to create a
Data Integration
mapplet:
  • If the mapplet includes a transformation that uses a connection, then the PowerCenter XML file must contain only one workflow, one Session task, one mapping, and one mapplet.
    If the mapplet doesn't include a transformation that uses a connection, then the PowerCenter XML file must include one mapplet. The workflow, Session task, and mapping are optional.
  • The session can use any type of connection.
  • You do not have to map all source and target fields in the PowerCenter mapping.
  • The PowerCenter mapplet 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 you use a mapplet in a
    synchronization
    task, the PowerCenter mapplet cannot contain multiple Input transformations.
  • If you use a mapplet in a
    mapping
    task, the PowerCenter mapplet can contain multiple Input transformations.
  • Data Integration
    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 PowerCenter XML file that contains the mapplet.
  • The PowerCenter mapplet cannot contain reusable objects such as shortcuts because
    Data Integration
    does not use a repository to store reusable objects. Export the mapplet without reusable objects.


Updated August 03, 2020