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. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Parameters in Mapplets Example

Parameters in Mapplets Example

You can define mapplet parameters and override them with mapping parameters.
You might define an SQL transformation that returns customer data from a Customer table. You add the SQL transformation to a mapplet and parameterize the run-time connection.
You then add the mapplet to mappings that retrieve customer data from different databases. You define a mapping parameter in each mapping to override the default connection from the mapplet parameter.
The following table lists the connection parameters that you might create for the mapplet and for the mappings:
Object Name
Object Type
Parameter Name
Parameter Default Value
mp_Get_Customer
Mapplet
mp_cust_connection
Oracle_Default
m_billing_mapping
Mapping
m_acctg_connection
Oracle_AcctDB
m_order_fill_mapping
Mapping
m_shipping_connection
Oracle_Warehouse
m_cust_main_mapping
Mapping
m_master_connection
Oracle_Cust_Mast
The mapplet, mp_Get_Customer, has a connection parameter called mp_cust_connection. The parameter has Oracle_Default as the default connection name. This connection might reference a test database, for example.
Each mapping has a connection parameter that overrides the mp_cust_connection parameter. Each mapping connects to the accounting, the warehouse, or the customer master database.
You must bind each mapping parameter to the mapplet parameter to override the default value. To change the value of the mapping parameters at runtime, you can configure a parameter set or a parameter file.

0 COMMENTS

We’d like to hear from you!