Send the file as a multipart attachment to an OIC integration using a REST trigger, and make it available for processing using a Stage File action.

Retrieve the file by invoking a SOAP API, which sends Base64 encoded data within the SOAP body, and then decode the data and make it available for processing using a Stage File action.

Retrieve the file by invoking a SOAP API, which sends the document as an MTOM attachment, and make it available for processing using a Stage File action.

Retrieve the file from an external endpoint using APIs that support application/blob as content type, and make it available for processing using a Stage File action.

Upload the file to the OIC file server, and then use an FTP adapter Download File operation, which makes it available for processing using a Stage File action.

A user with the ServiceAdministrator role can recover the unsaved changes.

A user with the ServiceAdministrator role can unlock an integration that has unsaved changes.

Changes made while editing a Connections page cannot be recovered.

Changes made while working inside a data mapper cannot be recovered.

A backup copy is created after each complete task, therefore there is no time limit to logging back in and recovering the changes.

It is used to suspend processing within the integration flow.

It can be configured to loop through elements until a condition is met.

It is used to trigger an error after a specified duration.

It is used to schedule integration runs at specific times.

It is used to configure a global variable for delay settings.

Imported integrations cannot be immediately activated if their dependent connection resources are not already present in the target OIC environment.

Exported integrations include all their dependent connection resource information except URLsand credentials.

Integrations must be exported as a package if you want to import them into another OIC environment.

Imported integrations can be reconfigured to use different connection resources by using the OIC REST API.

Implement a scope fault handler to catch the runtime fault, and then use the Fault Return action providing mapped data for the custom fault.

Implement a scope fault handler to catch the runtime fault, then allow the global fault handler to automatically send the runtime fault to the error hospital.

Create a custom scope fault handler to catch the runtime fault, and then use the ReThrow Fault action to send the fault to the Error Hospital.

Implement the Global Fault handler to catch the runtime fault, and then use the Rethrow Fault action to send the custom fault to the client.

Both the Apache Kafka and OCI Streaming adapters support XML, JSON, and Avro message formats.

It is not mandatory to install a Connectivity agent to use the OCI Streaming Adapter for Inbound polling.

The Apache Kafka Adapter can be configured to support Transactions in case of Producer.

The OCI Streaming Adapter does not support consuming messages from a specified consumer group.

Since the File Adapter is not supported in high-availability environments, you must use an Agent Group that uses only one installed active Agent.

You must have the OIC ServiceDeployer role or higher permissions to download and install the OIC Connectivity Agent.

Each host on which the agent is installed must be configured on separate subnets and assigned to the same OIC Agent group.

You should install the connectivity agents on the same host as the target application, and then specify different Agent group identifiers for each Agent during its installation.

You cannot have more than two Agent instances per Agent group. Attempting to include a third Agent instance in the same group during installation results in an error.

It uses XML to define the service layer document which consists of origin of the web service, headers, port types, request, and response data.

It stands for "Web Service Description Language" and is a document written in XML.

It stands for "Web Service Description Language" and is a document written in Object Notation.

It is a wrapper for a SOAP message.

It uses XML or JSON to define the service layer document which consists of origin of the web service, headers, port types, request, and response data.

Event pattern integrations

Schedule pattern integrations

SOAP trigger connection-based integrations

File trigger connection-based integrations

Specify an adapter type.

Specify the connection role.

Configure the security properties.

Specify the corresponding lookup.

Configure the connection properties.

Execute a successful test of the connection.

The Read File in Segments operation allows you to process the segments sequentially or in parallel.

Segment sizes default to 50 records but can be configured to any other segment size.

You need to explicitly configure a Scope action for this operation if you want to add additional actions during the processing of each segment.

You must provide the actual filename because file references cannot be processed by the Read File in Segments operation.

iCal

cron

YAML

Groovy

The exported archive file can include a map file that is largely complete in content or a map file that is empty of content.

The exported archive must be imported into an Oracle Service Bus project in JDeveloper.

Once the advanced mapping is complete, you must import the entire integration that contains the updated .xsl files.

You must export the entire integration that contains one or more .xsl files.

Download OIC Lookup

Download Design-time Audit Records

View Design-time Metrics

View Current Email Count

View Connectivity Agent Group Status

Both standard and custom HTTP headers can be defined for both the request and the response.

File attachments can be accepted as a request option for the Trigger interface, but you cannot include attachments as a response to the client.

Although you can define both query and template parameters, only template parameters are available for mapping in the mapper because query parameters are considered optional.

If you select a PUT or POST action (HTTP method), you must define a JSON response payload format.

Unified Communications Certificate

Multi Domain Certificate

Identity Certificate

Message Protection Certificate

Exported integrations include all their dependent connection resource information except URLs and credentials.

Integration must be exported as a project deployment if you want to import them into another OIC environment.

Imported integrations cannot be immediately activated if their dependent connection resources are not already present in the target OIC environment.

Imported integrations can be reconfigured to use different connection resources by using the OIC REST API.

Unlimited

10

5

7

Files uploaded through the Connectivity Agent can only be read with a file reference, with regard to both the Read Entire File and Read File in Segments operations.

Files uploaded through connectivity agent cannot be unzipped using a file reference.

Files uploaded through connectivity agent are not available with the zip file operation.

Files uploaded through connectivity agent are not available with the list file operation.

Use the Raise Fault action within your integration flow to generate custom faults and handle them accordingly.

Create a separate integration solely for the purpose of handling faults and configure your main integration to call it when necessary.

Open the Global Fault handler page on the integration canvas and add actions as needed to handle unexpected faults.

Add a Try-Catch action to your integration flow and configure it to catch and handle any faults.

SAML

PGP

X.509

Signing key

A client application hardcodes all URIs for resource endpoints, allowing it to navigate the API without relying on server responses.

A client application receives resource representations that include hyperlinks to related resources, enabling dynamic navigation based on the server’s responses.

A client application receives a base URI from the server and constructs all subsequent resource URIs by concatenating strings.

A client application pre-fetches all possible resource states and transitions to minimize server interactions.

The data structure for the target service is always displayed on the right side in the Designer view.

In the Designer view, the Sources section contains data structures of all available data objects, which includes integration metadata, tracking variables, global variables, and integration property values.

All transformation mappings use extensible Stylesheet Language (XSL).

All Source and Target data objects are represented internally as JSON structures.

All transformation mappings use eXtensible Stylesheet Language (XSL).

In the designer view, the Sources section contains data structure of all available data objects, which includes integration metadata, tracking variables, global variables, and integration property values.

The data structure for the target service is always displayed on the right side in the designer view.

All source and target data objects are represented internally as JSON structures.

When you navigate to the mapper and select a target element, Expression Builder launches in auser-friendly mode by default.

SOAP clients can easily hold stateful references to remote server-side SOAP objects.

SOAP is platform independent and programming language independent.

SOAP typically leverages XML-based payloads to communicate between two client machines across any modern network.

SOAP commonly serves as a cleaning agent that removes excess data from the transmission protocol.

SOAP provides flexibility for message formatting allowing for loose coupling between a client and a server.

SOAP over HTTP is typically not blocked by firewalls and proxy servers.

SOAP clients can easily hold stateful references to remote server-side SOAP objects.

SOAP is platform independent and programming language independent.

SOAP typically leverages XML-based payloads to communicate between two client machines across any modern network.

SOAP commonly serves as a cleaning agent that removes excess data from the transmissionprotocol.

SOAP provides flexibility for message formatting allowing for loose coupling between a client and a server.

SOAP over HTTP is typically not blocked by firewalls and proxy servers.

Check the instance logs for specific error messages and details.

Increase the number of instances to handle the error.

Immediately restart the integration instance.

Contact Oracle Support and wait for a response.

Add a Try-Catch action to your integration flow and configure it to catch and handle faults.

Create a separate fault handling integration and configure your integration to invoke it when necessary using the Rethrow Fault action.

Open the Global Fault Handler page on the integration canvas and add actions to handle faults.

Use the Throw New Fault action within your integration flow to send caught faults to the OIC Error Hospital.