Test REST Adapter Trigger Connection-Based Integrations
You can test app driven orchestration integrations designed with a REST Adapter trigger connection from the Test page in Oracle Integration. This eliminates the need to use third-party software to run this type of integration.
Operation Section
If the REST Adapter trigger connection-based integration is configured with multiple operations, the Operation section is displayed. This section contains the Operation list for selecting the appropriate operation, along with the HTTP method and relative URI (for the selected operation in case of multiple operations). If your integration contains only a single operation, this list is not displayed.
Request and Response Sections
The Request and Response sections enable you to trigger and view response output for your REST Adapter trigger connection-based integrations. Links are provided at the top to access the Track Instances page and the endpoint metadata.
The Request section consists of the following fields:
- URI Parameters: Shows the list of expected path (or template) and query parameters. You can enter data in this field.
- Headers: Shows the custom headers, including Accept and Content-Type based on the integration configuration.
- Body: Enables you to view the
message body contents or upload a file. Support is provided
for uploading payloads with multipart payloads or for
uploading nontextual payloads such as PDF or image files.
- If the request operation does not
have a body, the following message is
displayed.
This request does not have a body
- If the request operation includes a
body, its contents are automatically displayed.
For example:
- If you want to browse for and
upload a binary or nontextual payload (such as a
PDF or image file), click
File. For this example, an
image file is uploaded.
- For endpoints with
multipart payloads, a form is displayed under the
Body field that can be used
to provide a value for each part in the multipart
body. Two multipart attachments types are
supported in the request payload:
- multipart/form-data
- multipart/payload with structured
data such as JSON and XML:
- multipart/form-data
- multipart/mixed
For the following example, two headers for multipart/form-data are visible under the Headers tab.
Use cases for both multipart attachment types are provided. See Test REST Adapter Trigger-Based Integrations with Multipart Attachments on the Test Page.
- If the request operation does not
have a body, the following message is
displayed.
- cURL: Enables you to copy the
equivalent
curl
command. Thecurl
command is generated based on the endpoint's metadata and your provided input.
- Click Test to invoke the
integration.
The activity stream for this instance is displayed on the right side of the page. You can also access the instance in the Track Instances page by clicking Track Instances above the operation.
- Check the Response section
for response details.
The Response section consists of the response body (if any), headers included in the body, HTTP status of the headers (
200 OK
for this example), and instance ID of the triggered integration (if any). - Scroll to the right of Status and note the instance ID link. This link takes you to the details page for the instance under the Track Instances page.
- Click the Body tab in the Response section and place your cursor in the response message.
- From the
menu, click either Download to download the response payload in a file or Copy to Clipboard to copy the response payload to your clipboard.