Table of Contents

Search

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

Developer Mapping Guide

Developer Mapping Guide

Persisted Mapping Outputs and Deployment

Persisted Mapping Outputs and Deployment

When you redeploy a workflow 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:
  • When you deploy a workflow as an application for the first time, you do not have to perform any additional tasks if a Mapping task has persisted mapping outputs.
  • When you redeploy an application, you can choose whether to retain the state information or to discard it. If you choose to retain the state information, the mapping output values do not change in the repository when you redeploy the application. Otherwise the mapping outputs state is removed from persistence.
  • The mapping outputs state is not backed up when you back up and restore a mapping or workflow.
  • If you rename or recreate a mapping output, you cannot use the persisted mapping output value from a previous workflow run.

0 COMMENTS

We’d like to hear from you!