Developer Tool Guide

10.5.3
- 10.5.6
- 10.5.2
- 10.5.1
- 10.5

Back Next

Inheriting Direct, Indirect, and Remote Dependencies

Inherit direct, indirect, and remote dependencies when you have complete information about the design-time and run-time applications.

You might have complete information about an application when you are the sole developer or the functional administrator for an application. When you make changes to the design-time application, you might expect all of the changes to be propagated to the run-time application to ensure that the run-time application mirrors the design-time application.

Example

You manage an application that contains workflows that run mappings which share different data objects. After you deploy the application and test the outputs, you edit one of the data objects.

To propagate the changes in the data object to every other application object that uses the data object, you create a patch that inherits direct, indirect, and remote dependencies. When you select the data object, the patch inherits any workflows and mappings that use the data object.

The following image shows how the inheritance appears in the Incremental Deployment wizard:

This image shows the Source Object Selection page in the Incremental Deployment wizard. Next to Include, the option "Selected objects and all related objects" is selected. The table lists the following objects: the data objects Data Object A and Data Object B, the mappings Mapping A and Mapping B, and the workflows Workflow A and Workflow B. The data object Data Object A is selected. The data object Data Object B, the mappings Mapping A and Mapping B, and the workflows Workflow A and Workflow B are inherited, and their rows are greyed out. The bottom of the page states that 6 out of 6 objects are selected, 6 out of 6 objects will be updated, and 0 objects will be added.

The following image indicates the selected object and the inherited direct, indirect, and remote dependencies:

This image shows a dependency diagram for an application. In the application, the workflow Workflow A uses a mapping Mapping A, and the workflow Workflow B uses the mapping Mapping B. The mappings Mapping A and Mapping B share the data objects Physical Data Object A and Physical Data Object B. The data object Physical Data Object A has the label "selected." The objects Mapping A, Mapping B, and Physical Data Object B have the label “indirect.” The workflows Workflow A and Workflow B have the label “remote.”

To propagate the changes in the data object

Physical Data Object A

to the mappings and workflows that use the data object in the run-time application, you can also use a patch that inherits only direct dependencies. If you select the data object, the wizard identifies the mappings and workflows to be affected objects and the Data Integration Service updates the mappings and workflows during patch deployment.

A patch that inherits direct, indirect, and remote dependencies, however, provides more transparency about how the objects will be updated. It provides a higher guarantee that updated objects in the run-time application will transform data in the same way as the objects in the design-time application.

Rename Saved Search

Table of Contents

Developer Tool Guide

Developer Tool Guide

Inheriting Direct, Indirect, and Remote Dependencies

Inheriting Direct, Indirect, and Remote Dependencies

Example