Configuring Basic Information Properties

You can enter a name and description on the Basic Info page of each adapter in your integration.

What You Can Do from the Basic Info Page

You can specify the following values on the Basic Info page. The Basic Info page is the initial wizard page that is displayed whenever you drag an adapter to the section of the integration canvas supported by your adapter.

  • Specify a meaningful name.
  • Specify a description of the responsibilities.

What You See on the Basic Info Page

The following table describes the key information on the Basic Info page.

Element Description

What do you want to call your endpoint?

Provide a meaningful name so that others can understand the responsibilities of this connection. You can include English alphabetic characters, numbers, underscores, and dashes in the name. You cannot include the following:
  • Blank spaces (for example, My Inbound Connection)

  • Special characters (for example,  #;83& or righ(t)now4)

  • Multibyte characters

What does this endpoint do?

Enter an optional description of the connection’s responsibilities. For example: This connection receives an inbound request to synchronize account information with the cloud application.

Do you want to configure this as a callback invoke?

Select Yes to configure the SOAP Adapter as a callback invoke. This option is only available when configuring the SOAP Adapter as an invoke in an orchestrated integration. See Asynchronous Trigger Support in Orchestrated Integrations.

Additional Field is Displayed if Importing a Prerelease 16.3.3 Integration

If you are configuring the SOAP Adapter, there is an additional property if you imported a prerelease-16.3.3 integration. This property enables you to modify the transport mechanism, if needed. Starting with release 16.3.3, the underlying infrastructure for the SOAP Adapter runtime facilitates the delivery of new features in 16.3.3 and releases going forward. This change in infrastructure can cause backwards incompatibility under very exceptional situations for existing integrations using the SOAP Adapter. To preserve the backward compatibility of existing integrations, the newer runtime must be selected. Existing integrations using the SOAP adapter continue to use the 16.2.5 SOAP Adapter runtime and there are no differences in behavior.

Users modifying existing integrations to uptake the new runtime must take extra measures to check whether the integrations work the same as they were prior to uptaking the new runtime. In case of differences in behavior, you can select either not to uptake the new runtime for the existing flows or make necessary adjustments to the client application calling integrations or the SOAP API that is called by the ICS flow (depending upon how the SOAP adapter is used in the ICS flow)

New integrations built using 16.3.3 or above use the updated SOAP Adapter runtime by default.

Element Description

Preview updated SOAP adapter runtime

You can uptake the new 16.3.3 or later functionality exposed by the SOAP Adapter.

  • Yes: Provides the following functionality. The underlying transport mechanism used is the cloud SDK-based JCA transport.

    • Support for specifying the TLS version for a specific external SOAP API. The pre–16.3.3 SOAP Adapter runtime assumes all external SOAP APIs are protected using TLS version 1. The new capability allows support for invocation of SOAP APIs hosted on different versions: TLS version 1, TLS version 1.1, and TLS version 1.2.

    • Support for suppressing timestamps in SOAP documents sent to external SOAP APIs protected using username password token security policy. Some external SOAP services secured using the username password token security policy cannot handle the timestamps included in the SOAP/HTTP header. In that scenario, you can use this feature to enable the suppression of the timestamp in the outgoing SOAP documents.

    • Support for ignoring the absence of timestamps in the response SOAP document sent by the external SOAP APIs. Some external SOAP services secured using the username password token security policy do not have the ability to include timestamps in the SOAP HTTP header of the response SOAP messages to be sent back to the calling applications. In that scenario, you can use this feature to enable Oracle Integration Cloud Service to ignore the absence of the timestamp in the outgoing SOAP documents.

    • Support for disabling the validation of the SOAP action.

    • Support for adding SOAP and HTTP headers to outbound and inbound requests and handling the responses with headers to propagate back to the user.

    • Support for multiple part messages in document-style WSDLs.

    • Support for two-way SSL outbound communication.

  • No: Uses 16.2.5 functionality. The underlying transport mechanism used is the Oracle Service Bus-based HTTP transport.


If you import a pre-16.3.3 integration into Oracle Integration Cloud Service 16.3.3 or later that includes the SOAP Adapter, you must open the adapter in edit mode and explicitly select Yes to uptake the new 16.3.3 functionality.