When you use the Incremental Deployment Wizard, you can choose the type of application patch that you want to create. The application patch type determines the level of dependencies that the patch inherits.
A patch can inherit direct, indirect, and remote dependencies. With each level of dependencies, the patch inherits more objects. The inherited objects are included in the patch, and the overall impact that the patch has on the run-time application increases. You can choose the dependencies to inherit depending on the application design and the application objects that you want to update.
The following image shows the list of patch types in the wizard:
When you deploy the patch, the Data Integration Service replaces the run-time instances of the selected objects and the inherited dependencies in the run-time application, and it might affect other run-time objects. The Data Integration Service updates the affected objects to use the replaced run-time objects, but the affected objects are not replaced with their design-time instances.
If the application contains highly-dependent objects, the dependencies that an application patch inherits can be inversely related to the number of affected objects in the run-time application. As an application patch inherits fewer dependencies, the run-time application might contain more affected objects.
Example. Dependency Inheritance
The following image shows the direct and indirect dependencies that a patch inherits where the selected object is a mapping
Mapping A
:
The patch inherits the following direct and indirect dependencies:
Direct dependencies. The patch inherits the reusable transformation
Reusable Transformation A
and the data object
Physical Data Object A
because the objects are direct dependencies for the selected mapping
Mapping A
.
Indirect dependencies. The patch inherits the mapping
Mapping B
and the data object
Physical Data Object B
because the objects are indirect dependencies for the selected mapping
Mapping A.
Note that the patch does not inherit the workflow
Workflow B
and the mapping
Mapping C
because the objects are remote dependencies for the selected mapping