SOAP Adapter in OIC Explained

SOAP Adapter in Oracle Integration Cloud (OIC Gen 3)

In modern enterprise integrations, the SOAP Adapter in Oracle Integration Cloud continues to play a critical role, especially when dealing with legacy systems and enterprise-grade applications. Even in OIC Gen 3, SOAP-based integrations remain widely used in ERP, HCM, and third-party systems.

This guide explains the SOAP Adapter from a real implementation perspective, covering architecture, setup, testing, and common challenges—exactly how you would encounter it in a project.

What is SOAP Adapter in Oracle Integration Cloud?

The SOAP Adapter in OIC is used to connect to SOAP-based web services using WSDL definitions. It allows integrations to:

• Consume external SOAP services
• Expose integrations as SOAP services
• Handle structured XML payloads
• Support WS-Security standards

In practical terms, if you’re working with Oracle Fusion APIs (ERP/HCM/SCM), most of them are still exposed via SOAP—making this adapter extremely important.

Real-World Integration Use Cases

From actual project experience, SOAP Adapter is commonly used in the following scenarios:

1. Employee Data Integration (HCM)

• Fetch employee details from Oracle HCM using SOAP APIs
• Integrate with external payroll systems
• Use scheduled integrations with SOAP calls

2. Invoice Creation in ERP

• Send invoice data from third-party billing system to Oracle ERP
• Use SOAP-based createInvoice service
• Handle large XML payloads

3. Supplier Data Synchronization

• Fetch supplier data from ERP Cloud
• Push to procurement or legacy systems
• Use secure SOAP communication with certificates

Architecture / Technical Flow

In a real OIC Gen 3 implementation, the SOAP Adapter fits into the flow as follows:

1. Trigger or Schedule Integration
2. SOAP Adapter invokes external WSDL service OR exposes SOAP endpoint
3. XML payload transformation using Mapper
4. Response handling and fault processing

Typical Flow:

Key Components:

Prerequisites

Before configuring SOAP Adapter, ensure the following:

• Valid WSDL URL or file
• Access to SOAP endpoint
• Authentication details (Basic Auth / WS-Security)
• SSL certificates (if required)
• Proper network connectivity (OIC connectivity agent if on-prem)

Step-by-Step Build Process in OIC Gen 3

Let’s walk through a real example: Invoking a SOAP service from OIC

Step 1 – Create Integration

Navigate to:

Home → Integrations → Create → App Driven Orchestration

• Provide Name: Invoke_SOAP_Employee_Service
• Select Trigger (REST/Schedule)

Step 2 – Add SOAP Adapter as Invoke

Click + → Invoke → SOAP Adapter

• Enter Name: Invoke_Employee_Service

Step 3 – Configure SOAP Connection

Provide WSDL

• Option 1: Upload WSDL file
• Option 2: Enter WSDL URL

Example:

Step 4 – Select Service and Operation

• Choose Service from WSDL
• Select Operation (e.g., getEmployeeDetails)

Step 5 – Configure Request Parameters

• OIC auto-generates request schema
• Map input fields

Example:

Step 6 – Configure Security

Depending on service:

• Basic Authentication
• WS-Security (Username Token)
• Certificates (for secure communication)

Step 7 – Map Request Data

Use Mapper:

• Drag and drop fields
• Convert data formats if required

Step 8 – Handle Response

• Map SOAP response to target format
• Extract required fields

Example:

• Employee Name
• Department
• Salary

Step 9 – Activate Integration

• Click Activate
• Enable tracking

Testing the SOAP Adapter Integration

Test Scenario

Invoke employee service with:

Expected Response

Validation Checklist

• Correct SOAP endpoint invoked
• Proper request mapping
• Response received without faults
• Data transformation works correctly

Common Errors and Troubleshooting

From real project debugging, here are frequent issues:

1. Invalid WSDL

Error:

Solution:

• Validate WSDL using browser
• Check accessibility

2. Authentication Failure

Error:

Solution:

• Verify credentials
• Check WS-Security policy

3. SSL Certificate Issues

Error:

Solution:

• Upload certificates in OIC
• Configure trust store

4. Namespace Mismatch

Issue:

• Request fails due to incorrect XML namespace

Solution:

• Validate namespaces in SOAP envelope
• Match WSDL definition exactly

5. Large Payload Performance Issues

Solution:

• Use streaming if possible
• Optimize mapping logic

Best Practices from Real Implementations

1. Always Validate WSDL First

Before importing into OIC, test WSDL in tools like SOAP UI.

2. Use Reusable Connections

• Create one SOAP connection per service
• Reuse across integrations

3. Handle Faults Explicitly

• Use fault handlers
• Log error details

4. Secure Integrations Properly

• Use HTTPS endpoints
• Prefer certificate-based authentication

5. Optimize Mapping

• Avoid complex XSLT logic
• Keep transformations simple

6. Enable Tracking

• Track key fields (e.g., EmployeeId)
• Helps in debugging production issues

Advanced Concepts (Consultant-Level Insights)

1. SOAP Adapter as Trigger

You can expose OIC integration as a SOAP service:

• Generate WSDL automatically
• External systems can invoke OIC

2. Handling Attachments (MTOM)

Used in scenarios like:

• Invoice documents
• PDF attachments

3. Asynchronous SOAP

• Request sent without waiting for response
• Used in batch processing

4. WS-Policy Support

Supports advanced security:

• Encryption
• Digital signatures

Real Implementation Scenario (End-to-End)

Project: ERP Invoice Integration

• Source: Billing system
• Target: Oracle ERP Cloud
• Adapter Used: SOAP Adapter

Flow:

1. Billing system sends data to OIC
2. OIC transforms payload
3. SOAP Adapter calls ERP invoice API
4. Response stored in log table

Challenges Faced:

• Complex XML structure
• Authentication errors
• Large payload handling

Solution:

• Used staging tables
• Simplified mapping
• Implemented retry logic

Frequently Asked Questions (FAQ)

1. Is SOAP Adapter still relevant in OIC Gen 3?

Yes. Many Oracle Fusion APIs (especially ERP and HCM) still use SOAP, making it highly relevant.

2. Can SOAP Adapter handle large XML payloads?

Yes, but performance tuning is required. Use efficient mapping and avoid unnecessary transformations.

3. What is the difference between REST and SOAP Adapter in OIC?

Summary

The SOAP Adapter in Oracle Integration Cloud (OIC Gen 3) is a foundational component for enterprise integrations. Despite the rise of REST APIs, SOAP remains critical in Oracle ecosystems.

From real-world projects, the key to success lies in:

• Understanding WSDL structure
• Proper security configuration
• Efficient XML mapping
• Strong error handling

If you are working on Oracle Fusion integrations, mastering SOAP Adapter is not optional—it’s essential.

For deeper reference, always review Oracle’s official documentation:
https://docs.oracle.com/en/cloud/saas/index.html