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
  • Common Content for Data Integration 10.5
  • 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

Application Object Dependencies

Application Object Dependencies

An application object that you select to include in an application patch might be related to other application objects based on the selected object's set of dependencies.
Objects within an application can contain the following dependencies:
Direct
A direct dependency is an application object that the selected object uses and any direct dependencies of the direct dependency.
The following table lists the direct dependencies for each object type:
Object
Possible Direct Dependencies
Workflow
  • Mapping
  • Mapplet
  • Reusable transformation
  • Logical data object
  • Physical data object
Mapping
  • Mapplet
  • Reusable transformation
  • Logical data object
  • Physical data object
Mapplet
  • Reusable transformation
  • Logical data object
  • Physical data object
Reusable Transformation
  • Logical data object
  • Physical data object
Logical Data Object
  • Physical data object
Physical Data Object
  • A physical data object cannot have a direct dependency.
Parameter Set
  • A parameter set cannot have a direct dependency or be a direct dependency.
Indirect
An indirect dependency is an application object that uses the selected object, or an application object that uses a direct dependency of the selected object. Indirect dependencies include any direct dependencies of the indirect dependency.
Remote
A remote dependency is an application object that is an indirect dependency of an indirect dependency for the selected object. Remote dependencies include any direct dependencies of the remote dependency.
An application patch inherits other application objects based on a selected object's dependencies. For example, you can create an application patch that inherits a selected object's direct and indirect dependencies.
You cannot select mapplets, reusable transformations, and logical data objects in an application patch, but the patch can inherit these objects.
For more information about identifying indirect and remote dependencies, see the following Informatica How-To Library article:

Example. Dependency Sets

The following image shows the set of dependencies for an application object
Mapping A
:
This image shows a dependency diagram for an application. In the application, a workflow Workflow A uses a mapping Mapping A. The mapping Mapping A uses the reusable transformation Reusable Transformation A which uses the data object Physical Data Object A. A different workflow Workflow B uses the mappings Mapping B and Mapping C. The mapping Mapping B uses the reusable transformation Reusable Transformation A and the data object Physical Data Object B. The objects Reusable Transformation A and Physical Data Object A have the label "direct." The objects Workflow A, Mapping B, and Physical Data Object B have the label "indirect." The objects Workflow B and Mapping C have the label "remote."
The following table describes the set of dependencies for the mapping
Mapping A
:
Dependency Type
Object
Description
Direct
Reusable Transformation A
The reusable transformation is a direct dependency because the mapping
Mapping A
 uses the reusable transformation.
Direct
Physical Data Object A
The physical data object is a direct dependency because the mapping
Mapping A
 ultimately uses the data object through the reusable transformation
Reusable Transformation A
.
Indirect
Workflow A
The workflow is an indirect dependency because the workflow uses the mapping
Mapping A
.
Indirect
Mapping B
The mapping
Mapping B
 is an indirect dependency because the mapping
Mapping B
 uses a direct dependency of the mapping
Mapping A
: the reusable transformation
Reusable Transformation A
.
Indirect
Physical Data Object B
The physical data object is an indirect dependency because it is a direct dependency for the mapping
Mapping B
 which is an indirect dependency for the mapping
Mapping A
.
Remote
Workflow B
The workflow is a remote dependency because it is an indirect dependency for the mapping
Mapping B
 which is an indirect dependency for the mapping
Mapping A
.
Remote
Mapping C
The mapping
Mapping C
 is a remote dependency because it is a direct dependency for the workflow
Workflow B
 which is a remote dependency for the mapping
Mapping A
.

Relationship Priority

Relationships between physical data objects, mappings, and workflows take priority over relationships between other types of objects.
For example, the following image shows a set of dependencies for a data object
Physical Data Object A
:
This image shows a dependency diagram for an application. In the application, a workflow Workflow A uses a mapping Mapping A. The mapping Mapping A uses a mapplet Mapplet A which uses a data object Physical Data Object A. The mapping Mapping A and the mapplet Mapplet A have the label “indirect.” The workflow Workflow A has the label “remote.”
The mapping
Mapping A
 is an indirect dependency because the relationship between the mapping
Mapping A
 and the data object
Physical Data Object A
 takes priority over the following relationships:
  • The relationship between the data object
    Physical Data Object A
     and the mapplet
    Mapplet A
    .
  • The relationship between the mapplet
    Mapplet A
     and the mapping
    Mapping A
    .
Since the mapping
Mapping A
 is an indirect dependency, its direct dependency
Mapplet A
 is an indirect dependency for the data object
Physical Data Object A
.
0 COMMENTS
We’d like to hear from you!