OIC - Fixing WSDL Import and Element Errors While Configuring External Partner Adapters in Oracle Integration (OIC)

Fixing WSDL Import and Element Errors While Configuring External Partner Adapters in Oracle Integration (OIC)

Use Case:

An external partner has provided a WSDL for integration. While trying to create a connection in Oracle Integration Cloud (OIC) using the SOAP adapter and uploading the provided WSDL, errors such as missing imports or undefined elements occur. These issues prevent successful adapter configuration and integration setup.

Problem Statement:

During SOAP adapter configuration in OIC, uploading the partner-provided WSDL throws errors like:

• "Failed to import WSDL: Could not resolve import..."
• "Element XYZ not defined in the schema..."

This is typically due to:

• Missing referenced XSD or WSDL files.
• Incorrect or inaccessible schema locations.
• Unresolvable namespace dependencies.

Solution Steps:

Step 1: Collect All WSDL and XSD Dependencies

• Request the external partner to share a complete WSDL bundle including all dependent XSD and WSDL files.
• Alternatively, download all externally referenced schema files from the URLs defined in the WSDL (if accessible).

Step 2: Update Import References (If Needed)

• Edit the main WSDL to correct any broken <xsd:import> or <wsdl:import> paths.
• Use Notepad++ or XML editors to verify and fix namespaces and schema locations.

Step 3: Validate WSDL Using a WSDL Parser or SoapUI

• Open the WSDL in tools like SoapUI or Altova XMLSpy to ensure it parses successfully before uploading to OIC.

Step 4: Create Connection in OIC

• Go to Connections > Create a new SOAP connection.
• Use the hosted WSDL URL (with all dependencies accessible).
• Test the connection to ensure it's configured without error.

Step 5: Build Integration

• Create a new integration and use the configured connection.
• Configure the SOAP adapter and validate that all operations and messages are correctly displayed.
• Proceed with integration mapping and testing.

Detailed screenshots:

Few of the error examples with solutions

Issue1: one message part was missing

Solution1: Added the missing message part.

Issue2: unused import element with no actual import elements.

Solution2: Removed the import element

Issue3: Restriction element was using same namespace what import element using

Solution 3: removed that restriction part.