Table of Contents
- Title and Copyright Information
- Preface
- 1 Understand the SOAP Adapter
- 2 SOAP Adapter Concepts
- 3 Create a SOAP Adapter Connection
- 4 Add the SOAP Adapter Connection to an Integration
-
5
Implement Common Patterns Using the SOAP Adapter
- Best Practices for Invoking SOAP Endpoints
- Configure MTOM Support in the SOAP Adapter
- Consume Taleo SOAP APIs
- Invoke a SOAP-Based Integration with a Timestamp
- Configure Custom SOAP Headers for the SOAP Adapter
- Call Oracle Fusion Applications Business Intelligence Publisher Report Services
- Integrate PeopleSoft with Oracle Integration
- Create a Keystore File for a Two-Way, SSL-Based Integration
- Invoke a SOAP Endpoint with an Explicit Authorization Header
- Implement Oracle Enterprise Scheduler Web Service Calls
-
6
Troubleshoot the SOAP Adapter
- Regenerate the SOAP Adapter Connection After WSDL Definition Updates
- Use the Correct SoapUI Version to Load and Test SOAP Endpoints
- Edit Adapter Connections in Active Integrations
- Multiple SOAP Adapter Invokes with Custom Headers Created Prior to 17.4.3
- SOAP Endpoint Invocation Fails with OSB-380001: mustUnderstand Error
- Specify Connection Property Values with the REST API
- Callback Integrations Fail with a Configured SOAP Action Mismatch Error
- Integrations Fail with SAML Security Policy Selected in Inbound Direction
- Schemas Not Successfully Loaded in Mapper When Using Headers Configured with WSDLs Ending in asmx
- Resolve SOAP Action Mismatch Errors in the SoapUI
- Resolve Exceptions While Invoking Oracle Integration From External Clients
- Connection Error When Using the Incorrect TLS Version
- Extra Information is Included in the Response Headers Returned as Part of the Response Message
- Basic Authentication Fields are Unavailable when Updating a SOAP Adapter Connection after Importing a 16.2.5 Integration
- Unexpected Use of the Suppression Insertion of Timestamp into WS-Security Header Feature in the SOAP Adapter Causes an Unrelated Error Response
- Pre-17.2.5 Integration Failures with an Invoke SOAP Adapter Configured with the Basic Authentication Security Policy and Suppress Timestamp Set to No