Modify an Integration

You can modify an existing integration, including changing a source or target connection, reconfiguring the connection, and updating the data mapping. Changes to the source or target can cause changes to the existing mappings.

If the integration you want to modify is active, deactivate it first. The integration must not be active. See Deactivate an Integration for instructions.

1. In the navigation pane, click Design, then Integrations.
2. Hover over the integration to change, then click Edit .
3. To modify the trigger or invoke adapter connection, select the connection and click Actions , then click Edit.
4. Modify any necessary fields in the pages of the Adapter Endpoint Configuration Wizard.
5. To assign a new invoke connection, select the connection, and click Actions , then click Delete . You cannot delete a trigger connection in an integration.
6. Add the new adapter to the canvas.
7. Configure the new connection.
8. To modify a data mapping, click the appropriate map icon and update the mappings. See Mapping Data of Using the Oracle Mapper with Oracle Integration 3.
9. When you are done making changes, click Save.

Note:

If your integration is locked and stuck in Draft mode, see Recover Unsaved Integration Changes.

Impact on the Mapper of Editing the Endpoint Information in an Integration

You can edit the endpoint information in an integration that is not active. The changes that you make can impact your mappings. For example, minor edits such as changing the endpoint description do not delete the existing mappings. Major edits such as changing the selected business objects or operations delete the mappings. In these cases, you must recreate your mappings. Before you save your updates, you are prompted to confirm your changes.

The impact of major and minor endpoint changes on an integration are as follows:

• If a minor change is detected, for example:

  • If a map is using either the request or response of the application as a primary input, output, or secondary input, the map is validated.

  • If a map is using a fault of the application as a primary input or output, the map is deleted.

  • If a map is only using a fault of the application as a secondary input, the secondary input is removed.

• If a major change is detected, for example:

  • If a map is using a request, response, or fault of the application as a primary input or output, the map is deleted.

  • If a map is only using a request, response, or fault of the application as a secondary input, the secondary input is removed.

The following are examples of major endpoint changes:

• If the application message exchange pattern changes (for example, from synchronous to asynchronous).

• If a root element name or root element namespace of the input request changes.

• If a root element name or root element namespace of the output response changes.

If none of the above changes occur, then the change is considered minor.

1. In the navigation pane, click Design, then Integrations.
2. Hover your cursor over the integration to edit, then click Edit .
   The integration must not be active.
3. In the integration canvas, select the trigger or invoke endpoint to edit, then click Edit .
4. Make appropriate changes in the Adapter Endpoint Configuration Wizard, then click Done.
5. Select to confirm your changes when prompted. Minor edits do not delete your mappings. Major edits delete your mappings.