Table of Contents
- Title and Copyright Information
- Preface
- 1 Understand the REST Adapter
-
2
REST Adapter Concepts
- Authentication Support
- REST API Support
- OpenAPI Support
- Attachment Support
- Header, Token, Query Parameter, and Array Support
- Swagger Support
- Mapper Connectivity Properties Support
- REST Endpoint Support
- Cross-Origin Resource Sharing (CORS) Support
- Complex Schema Support
- Resource Principal Session Token Support
- JWT Assertion Support for Outbound Invocations
- 3 Create a REST Adapter Connection
-
4
Add the REST Adapter Connection to an Integration
-
Add the REST Adapter as a Trigger Connection
- REST Adapter Trigger Basic Information Page
- REST Adapter Trigger Resource Configuration Page
- REST Adapter Trigger Request Parameters Page
- REST Adapter Trigger Request Page
- REST Adapter Trigger Request Header Page
- REST Adapter Trigger CORS Configuration Page
- REST Adapter Trigger Response Page
- REST Adapter Trigger Response Header Page
- REST Adapter Trigger Operations Page
- REST Adapter Trigger Operation Selection Page
- Summary Page
- Add the REST Adapter as an Invoke Connection
-
Add the REST Adapter as a Trigger Connection
-
5
Implement Common Patterns Using the REST Adapter
- Connect to an Endpoint that Requires a Content-Length Header to Be Sent
-
OAuth-Protected Patterns
- Configure the REST Adapter to Consume a REST API Protected with OAuth Custom Two Legged Token-Based Authentication
- Configure the REST Adapter to Consume a REST API Protected with OAuth Custom Three Legged Flow Token-Based Authentication
- Configure the REST Adapter to Consume a REST API Protected with OAuth 1.0 One-Legged Authentication
- Allow Client Applications to Consume an Integration Exposed as an OAuth-Protected REST API
-
REST API Consumption
Patterns
- Configure the REST Adapter to Consume a REST API Protected with the API Key
- Configure the REST Adapter to Consume an External REST API with No Metadata Described in a Document
- Configure a REST Adapter to Consume a REST API that Expects Custom HTTP Header Properties
- Configure the REST Adapter to Consume an Amazon Web Services (AWS) REST API
- JSON Content Patterns
- OpenAPI Document Patterns
- Best Practices for Invoking REST Endpoints
- Override the Endpoint URI/Host Name for an External REST API at Runtime
- Map to Construct the Payload for an External REST API that Accepts multipart/form-data as the Content Type
- Implement an Integration in which to Send an Incoming Message with a Base64-Encoded String to an External REST API that Accepts a Multipart Attachment
- Pass the Payload as URL-Encoded Form Data
- Implement an Integration to Send a PDF/CSV Document Downloaded from an SFTP Server to an External REST API that Accepts Only application/octet-stream as the Content Type
- Configure the REST Adapter to Expose an Integration as a REST API
- Enter q as a Standard HTTP Query Parameter with the Query as a Value
- Configure Oracle Integration to Call Oracle Cloud Infrastructure Functions with the REST Adapter
- Configure a REST Adapter Trigger Connection to Work Asynchronously
- Create a Keystore File for a Two-Way, SSL-Based Integration
- Access Oracle Cloud Infrastructure Service Resources Using RPST
- Invoke a Service Provider API with a JWT Assertion
-
6
Troubleshoot the REST Adapter
- ORABPEL-15235 Translation Failure Error Occurrence
- Failed REST Adapter Invoke Connection Retries Three Times Every 30 Seconds with a 504 Timeout Error
- Troubleshoot RPST and OCI Service Invocation Security Policy Issues
- Multipart Form-Data Endpoint Invocation Fails When Media Type is null
- Convert a Private Key from PKCS8 to RSA (PKCS1) Format for the OCI Signature Version 1 Security Policy
- HTTP Error Response for Pre-20.4.2 Connections is Not Compliant with the OpenAPI Specification
- REST Services that Return Multiple Successful Responses
- Error Handling with the REST Adapter
- REST Service Invoked by the REST Adapter Returns a 401 Unauthorized Status Response
- Configuration Limitation of Ten Pages in the Adapter Endpoint Configuration Wizard
- Keys with Null Values During JSON Transformation are Removed
- Large Sample JSON File Processing with Special Characters
- SSL Certification Troubleshooting Issues
- Fault and Response Pipeline Definitions in Basic Routing Integrations
- Empty Arrays Are Not Supported in Sample JSON Files
- Invoke Endpoint URI Must Match the Base URI + Resource URI in REST Adapter
- JD Edwards Form Service Invocation with the REST Adapter Causes APIInvocation Error
- REST Adapter Data is Only Saved When You Click Next
- Convert XML to a JSON Document
- Supported Special Characters in JSON Samples
- content-type is Missing for an Asynchronous Flow
- REST URLs Exceeding 8251 Characters Fail
- Send a "null" Value Instead of "" for Any Specific Key in JSON Through the REST Adapter
- 7 REST Adapter Samples