Add the Oracle Utilities Adapter as a Trigger Connection

When you drag the Oracle Utilities Adapter into the integration canvas as a trigger connection, the Adapter Endpoint Configuration Wizard is invoked. Based on your selections in the wizard, the following pages can be displayed.

Trigger Basic Info Page

Field Description

Field	Description
What do you want to call your endpoint?	Provide a meaningful name so that others can understand the purpose of the connection. For example, `LinkedInTarget_update_status`. You can use English alphabetic characters, numbers, underscores, and dashes in the name. You cannot use: Blank spaces (for example, `My FTP Connection`) Special characters (for example, `#;83&` or `righ(t)now4`) Multibyte characters
What does this endpoint do?	Enter an optional description of connection functionality.
What is the endpoint's relative resource URI? (Available only in the REST-based trigger (inbound) direction.)	Enter the endpoint's relative resource URI. The endpoint must begin with a `/`, followed by letters.

What do you want to call your endpoint?

Provide a meaningful name so that others can understand the purpose of the connection. For example, LinkedInTarget_update_status. You can use English alphabetic characters, numbers, underscores, and dashes in the name. You cannot use:

Blank spaces (for example, My FTP Connection)
Special characters (for example, #;83& or righ(t)now4)
Multibyte characters

What does this endpoint do?

Enter an optional description of connection functionality.

What is the endpoint's relative resource URI?

(Available only in the REST-based trigger (inbound) direction.)

Enter the endpoint's relative resource URI. The endpoint must begin with a /, followed by letters.

Note:

Starting with Release 23.08, the Upload WSDL option for trigger connections is no longer supported.

Trigger Request Page

This page enables you to select the external system to treat as the request object for this integration for OUAF applications.

Field	Description
Select a Business Object	Select the business object from the Oracle Utilities application to receive as a request that starts the integration.
Filter by object name	Enter the initial letters to filter the display of business objects.
Select Media Type (Available only for REST endpoints.)	JSON is displayed for selection.

Field

Description

Select a Business Object

Select the business object from the Oracle Utilities application to receive as a request that starts the integration.

Filter by object name

Enter the initial letters to filter the display of business objects.

Select Media Type

(Available only for REST endpoints.)

JSON is displayed for selection.

For non-OUAF applications that are a REST-based endpoint, the trigger Request page is as follows:

Field	Description
Select a Request Object	Select a service request object to invoke.
Filter by object name	Enter the initial letters to filter the display of business services.
Request Media Type	Upon selecting the Operation, the supported media type will be displayed automatically. This can include the following values: JSON: Denoting that the payload received is in JSON format. Multipart Mixed: Indicates that an attachment is received with a JSON payload. For example, a CSV file accompanied by a JSON file that contains metadata information about the attachment.
Select the Operation	Select an operation from the published web service to perform on the service request object.

Trigger Response Page

This page enables you to select the external system to treat as the response object for this integration for OUAF applications.

Field	Description
Select a Business Object	Select the business object from the Oracle Utilities application to receive as a response from the integration.
Filter by object name	Enter the initial letters to filter the display of business objects.
Select Media Type (Available only for REST endpoints.)	JSON is displayed for selection.
Response Type	Select one of these options: Request-Response: The default. The Oracle Utilities application waits until a response is received from the integration. This is also known as the request and response message exchange pattern. Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern). Send Faults

For non-OUAF applications that are a REST-based endpoint, the trigger Response page is as follows:

Field	Description
Select a Response Object	Select the service response object from the Oracle Utilities application to receive as a response from the integration.
Filter by object name	Enter the initial letters to filter the display of business objects.
Response Media Type	Upon selecting the operation, the supported media type is displayed automatically. This can include the following values: JSON: Indicates that the payload received is in JSON format. Multipart Mixed: Indicates that an attachment is received, along with a JSON payload. For example, a CSV file accompanied by a JSON file that contains metadata information about the attachment.
Select the Operation	Select an operation from the published web service to perform on the service response object.
Response Type	Select one of these options: Request-Response: The default. The Oracle Utilities application waits until a response is received from the integration. This is also known as the request and response message exchange pattern. Disable the checkbox for asynchronous calls (also known as the one-way message exchange pattern). Send Faults

Summary Page

Field	Description
Summary	Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard. The information that’s displayed can vary by adapter. For some adapters, the selected business objects and operation name are displayed. For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.

Field

Description

Summary

Displays a summary of the trigger (source) or invoke (target) configuration values that you defined on previous pages of the wizard. The information that’s displayed can vary by adapter. For some adapters, the selected business objects and operation name are displayed. For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file. To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.