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

Rules and Guidelines for Persisted Mapping Outputs and Deployment

Rules and Guidelines for Persisted Mapping Outputs and Deployment

When you redeploy a mapping or you change a mapping output, you can affect the state of persisted mapping outputs.
Consider the following rules and guidelines for persisted mapping outputs:
  • The first time you deploy a mapping, you do not have to perform any additional tasks if a mapping has persisted mapping outputs.
  • When you redeploy a mapping, the persisted mapping outputs are retained in the repository. You can run the infacmd ms deleteMappingPersistedOutputs to delete persisted outputs from the repository.
  • The mapping outputs state is not backed up when you back up a mapping.
  • If you rename a mapping output, you cannot use the persisted mapping output value from a previous deployed mapping run. If you recreate a mapping output with the same name, you can use the persisted output value.

0 COMMENTS

We’d like to hear from you!