Step 4. Match the Dependencies to Design-time Objects
Step 4. Match the Dependencies to Design-time Objects
After you identify dependencies in the run-time application, match the run-time objects to their corresponding design-time instances. The design-time objects assume the same type of dependency as their run-time instances.
The following image shows how the run-time objects are matched to corresponding design-time objects:
Based on the above image, the mapping
Mapping B
has the following dependencies:
Type of Dependency
Dependencies
Direct
Mapplet A
Physical Data Object B
Indirect
Mapping A
Mapping C
Workflow B
Reusable Transformation C
Remote
Workflow A
The reusable transformation
Reusable Transformation C
becomes an indirect dependency for the mapping
Mapping B
, because it is a direct dependency for the mapping
Mapping C
which is an indirect dependency for the mapping
Mapping B
.
Notice how the indirect and remote dependencies reflect the set of dependencies in the run-time application. For example, the design-time application suggests that the workflow
Workflow A
is an indirect dependency for the mapping
Mapping B
because the workflow uses the mapping in the design-time application. When you examine the run-time application, you can see that the workflow
Workflow A
is actually a remote dependency.
After you have identified the indirect and remote dependencies, you can choose to include the dependencies in the application patch by creating a patch that inherits indirect dependencies or indirect and remote dependencies.