Table of Contents

Search

  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. Datatype Reference
  17. Configure the Web Browser

Designer Guide

Designer Guide

Rules and Guidelines for Mapplets

Rules and Guidelines for Mapplets

The following list summarizes the rules and guidelines that appear throughout this chapter:
  • You can connect an Input transformation to multiple transformations in a mapplet. However, you cannot connect a single port in the Input transformation to multiple transformations in the mapplet.
  • An Input transformation must receive data from a single active source.
  • A mapplet must contain at least one Input transformation or source definition with at least one port connected to a transformation in the mapplet.
  • A mapplet must contain at least one Output transformation with at least one port connected to another transformation in the mapping.
  • When a mapplet contains a source qualifier that has an override for the default SQL query, you must connect all of the source qualifier output ports to the next transformation within the mapplet.
  • If the mapplet contains more than one source qualifier, use a Joiner transformation to join the output into one pipeline. If the mapplet contains only one source qualifier, you must connect the mapplet output ports to separate pipelines. You cannot use a Joiner transformation to join the output.
  • When you edit a mapplet, you might invalidate mappings if you change the mapplet type from passive to active.
  • If you delete ports in the mapplet when the mapplet is used in a mapping, you can invalidate the mapping.
  • Do not change the datatype, precision, or scale of a mapplet port when the mapplet is used by a mapping.
  • If you use a Sequence Generator transformation, you must use a reusable Sequence Generator transformation.
  • If you use a Stored Procedure transformation, you must configure the Stored Procedure Type to be
    Normal
    .
  • You cannot include PowerMart 3.5-style LOOKUP functions in a mapplet.
  • You cannot include the following objects in a mapplet:
    • Normalizer transformations
    • Cobol sources
    • XML Source Qualifier transformations
    • XML sources
    • Target definitions
    • Pre- and post- session stored procedures
    • Other mapplets

0 COMMENTS

We’d like to hear from you!