Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Where to Assign Parameters
  6. Mapping Outputs
  7. Generate a Mapping from an SQL Query
  8. Dynamic Mappings
  9. How to Develop and Run a Dynamic Mapping
  10. Dynamic Mapping Use Cases
  11. Mapping Administration
  12. Export to PowerCenter
  13. Import From PowerCenter
  14. Performance Tuning
  15. Pushdown Optimization
  16. Partitioned Mappings
  17. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Rule Specifications and Mapplets

Rule Specifications and Mapplets

A rule specification is a Model repository object that uses business logic to describe transformation operations. Users create rule specifications in Informatica Analyst. You can add a rule specification to a mapping in the same way that you add a mapplet to a mapping.
You can also add a rule specification to a mapplet and deploy a rule specification from the Developer tool as a web service.
An Analyst tool user can generate one or more mapplets from a rule specification. Each mapplet contains transformations that represent the rule specification logic. When you run a mapping that contains either the rule specification or the corresponding mapplet, you get the same results.
You can edit a mapplet that a user generates from a rule specification in the same way as any mapplet that you create in the Developer tool. You cannot edit a rule specification in the Developer tool. Add a rule specification to a mapping when you want the mapping to apply the logic that the rule specification represents. Add the corresponding mapplet to a mapping when you want to use or update the mapplet logic independently of the rule specification.

Rules and Guidelines for Rule Specifications

  • A rule specification contains a primary rule set and optionally contains additional rule sets. The primary rule set represents the complete logic of the rule specification. Additional rule sets define discrete data analysis operations and provide outputs that other rule sets can read.
    The mapplet that represents the primary rule set has the same name as the rule specification.
  • If you rename a rule specification in the Developer tool, the Analyst tool displays the name when the user opens the rule specification. If you rename the mapplet for the primary rule set, you do not change the rule specification name.
  • If an Analyst tool user adds, deletes, or edits an input in a rule specification, the user breaks all input links to other objects in a mapping. If an Analyst tool user adds, deletes, or edits an output in a rule specification, the user breaks all input links to other objects in a mapping. The edits that break the links include changes to the name, precision, or data type of an input or output. Update the links in any mapping that uses the rule specification.
    If an Analyst tool user updates the business logic in a rule specification but does not alter the inputs or outputs, the input and output links do not break. The changes that the user makes are available to the mapping when the user saves the rule specification.

0 COMMENTS

We’d like to hear from you!