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

Choose the Application Patch Type

Choose the Application Patch Type

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:
This image shows the Source Object Selection page in the Incremental Deployment wizard. Next to Include, the page lists the following options: Selected objects, Selected objects and first-degree related objects, and Selected objects and all related objects.
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
:
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 inheritance." The objects Workflow A, Mapping B, and Physical Data Object B have the label "indirect inheritance."
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
Mapping A
.

0 COMMENTS

We’d like to hear from you!