1. Using the SOAP Adapter with Oracle Integration Generation 2
  2. Troubleshoot the SOAP Adapter
  3. Multiple SOAP Adapter Invokes with Custom Headers Created Prior to 17.4.3

Multiple SOAP Adapter Invokes with Custom Headers Created Prior to 17.4.3

If you have integrations with multiple SOAP Adapter invokes that have custom headers created prior to 17.4.3, note the following details.

Assume you have the following use case:

  • Three different integrations (Flow1, Flow2, and Flow3) use the SOAP Adapter as a trigger connection with custom HTTP headers configured (created before 17.4.3). A static namespace is used for the inbound wrapper.

  • Flow4 is a delegating pattern integration with multiple invoke connections using the endpoints of Flow1, Flow2 and Flow3 (created in 18.3.3) This flow uses dynamic namespaces for all outbound wrappers.

Activating Flow4 causes a failure because there is a conflict with the wrapper schema between Flow1 and Flow2 when used as an invoke.

Note the following workaround and solutions:

  • Workaround:

    Ensure that the schema is the same between integrations (for example, Flow1 and Flow2). If the custom HTTP headers used have a different description, this can cause a schema conflict. Keep the same description in all integrations for the schema to be synchronized. If you edit the Flow 2 trigger description to match Flow1 and re-activate the integration, then recreate the Flow2 invoke in Flow4, the issue is resolved.

  • Actual solution:

    Recreate the Flow1, Flow2, and Flow3 integrations to use the dynamic wrapper namespaces that are available after 17.4.3. If the flows are recreated in the latest Oracle Integration version, dynamic namespaces are available and there is no activation issue for Flow4. Note that there is significant rework required to recreate the integrations because it involves some complex logic and the change is in the trigger.

  • Alternative solution to avoid rework:

    Manually update the namespaces in the Flow1, Flow2, and Flow3 triggers to include dynamic namespaces and reactivate the integrations, then use them in Flow4.

    Note:

    Manual updating is not recommended because the change can impact downstream mappings and assignments based on the integration design.