Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica Data Quality 10.4.0
  • All Products

Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Application Patch Deployment
  12. Application Patch Deployment Example
  13. Continuous Integration and Continuous Delivery (CI/CD)
  14. Object Import and Export
  15. Appendix A: Data Type Reference
  16. Appendix B: Keyboard Shortcuts
  17. Appendix C: Connection Properties

Developer Tool Guide

Developer Tool Guide

Back Next

Patch Type: Direct, Indirect, and Remote

Patch Type: Direct, Indirect, and Remote

This section describes an application patch that inherits direct, indirect, and remote dependencies.

Identify the Inherited Objects

The following image shows the objects that the patch includes when you inherit direct, indirect, and remote dependencies:
This image shows a deployed run-time application and an updated design-time application. The deployed run-time application has the following objects: Workflow B, Mapping A, Mapping B, Mapping C, Lookup B, Data Object A, and Data Object D. Mapping A uses Data Object A. Mapping B uses Lookup B which uses Data Object A. Mapping C uses Data Object D. Workflow B uses Mapping B and Mapping C. The updated design-time application has the following objects: Workflow B, Mapping A, Mapping B, Mapping C, Data Object A, Data Object B, and Data Object C. Mapping A uses Data Object A. Mapping B uses Data Object A and Data Object B. Mapping C uses Data Object C. Workflow B uses Mapping B and Mapping C. In the updated design-time application, Mapping A is labeled as the selected object and Data Object A is labeled as a direct dependency. Mapping B and Data Object B are labeled as indirect dependencies. Workflow B, Mapping C, and Data Object C are labeled as remote dependencies.
The following table lists the dependencies that the patch inherits when the mapping
Mapping A
 is the selected object:
Type of Dependency
Dependencies
Direct
  • Data Object A
Indirect
  • Mapping B
  • Data Object B
Remote
  • Workflow B
  • Mapping C
  • Data Object C

Assess the Object Impact

The following image shows the impact to the run-time objects after the patch is deployed:
This image shows a deployed run-time application and an updated design-time application. The deployed run-time application has the following objects: Workflow B, Mapping A, Mapping B, Mapping C, Lookup B, Data Object A, and Data Object D. Mapping A uses Data Object A. Mapping B uses Lookup B which uses Data Object A. Mapping C uses Data Object D. Workflow B uses Mapping B and Mapping C. In the deployed run-time application, Workflow B, Mapping A, Mapping B, Mapping C, and Data Object A are labeled as modified objects. Data Object B and Data Object C are labeled as added objects. Lookup B and Data Object D are labeled as orphaned objects. The updated design-time application has the following objects: Workflow B, Mapping A, Mapping B, Mapping C, Data Object A, Data Object B, and Data Object C. Mapping A uses Data Object A. Mapping B uses Data Object A and Data Object B. Mapping C uses Data Object C. Workflow B uses Mapping B and Mapping C. In the updated design-time application, Mapping A is labeled as the selected object and Data Object A is labeled as a direct dependency. Mapping B and Data Object B are labeled as indirect dependencies. Workflow B, Mapping C, and Data Object C are labeled as remote dependencies.
Because the patch inherits mappings
Mapping B
 and
Mapping C
, the mappings use their design-time dependencies in the run-time application. The reusable transformation
Lookup B
 and the data object
Data Object B
 become orphans in the run-time application.

Evaluate the Scope of the Changes

The following table shows the number of objects that are impacted during patch deployment:
Scope Item
Number of Objects
Selected
7
Updated
Modified: 5
Affected: 0
Total: 5
Added
2

Findings

If you create a patch that inherits direct, indirect, and remote dependencies, the changes to the run-time application are transparent. The updated and added objects in the run-time application match the selected objects in the design-time application and you can expect the run-time application to transform data in the same way as the objects in the design-time application.
The trade-off is that all objects experience down-time, and you might be better off by redeploying the application. When you redeploy the application, you update the same objects with the benefit of removing the orphaned objects from the run-time application: the reusable transformation
Lookup B
 and the data object
Data Object D
.
0 COMMENTS
We’d like to hear from you!