5 Implement Common Patterns Using the REST Adapter
You can use the REST Adapter to implement the following common patterns.
Differences Between Implementation Patterns and Recipes
Unclear about the difference between implementation patterns and recipes? Both assets provide different solutions.
-
Implementation patterns describe a common use for this adapter. The pattern can range from a simple configuration task (such as how to configure a specific security policy for this adapter) to a high level overview of how to use this adapter in an integration.
-
Recipes, known as prebuilt integrations, are preassembled, easily installable, integration solutions. A recipe contains all the resources required for a specific integration scenario. The resources include integration flows, adapter connections, lookups, and certificates. Use a recipe to quickly get started building an integration. See the Recipes and Accelerators page on the Oracle Help Center.
Topics:
- Connect to an Endpoint that Requires a Content-Length Header to Be Sent
- OAuth-Protected Patterns
- Propagate OAuth User Identity Between Services
- REST API Consumption Patterns
- 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
- Pass the Payload as URL-Encoded Form Data
-
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