1z0-1042-24 Oracle Cloud Infrastructure 2024 Application Integration Professional Questions and Answers

Create a custom batch call function, register the function as a Library in your OIC environment, then use the JavaScript call action to invoke the application.

Reactivate the integration and use the disable tracing and message tracking option, which will optimize performance for each invocation to the application.

Use the Append option in the Write File operation of the Stage File action within a loop to create a single batch file to be sent to the application.

Throttle the individual synchronous calls by adding a wait activity prior to each invocation to the application within the loop, then fetch a batch response after the loop.

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.

File adapter is not supported in high availability environments. When using file adapter and if some groups have multiple instances, use a dedicated agent group (with one agent only).

You need to have the OIC ServiceDeployer role permissions to download and install the OIC on-premises connectivity agent.

Increase the number of instances to handle the error.

Contact Oracle Support.

Immediately restart the integration instance.

Check the instance activity stream for specific error messages and details.

You can create the new integration as a different major version of the existing one.

You can create the new integration from scratch by using the same display name and specifying a different identifier.

You can clone the existing integration and specify it to use the schedule pattern instead of the application pattern.

You can use the convert tool to change from the application pattern to the schedule pattern.

Use the REST adapter configuration wizard to define the structure of the CSV when configuring the invoke connection, then map the MTOM attachment directly.

Map the received MTOM attachment directly to the REST adapter invoke map action using the encodeReferenceToBase64 function.

Create and register a JavaScript function to convert the contents, invoke it using the JavaScript call action, then map the result to the REST adapter invoke map action.

Create an NXSD in Oracle JDeveloper to define the schema of the CSV and use it to map the transformed data to the REST adapter invoke map action.

Import the JavaScript library file into your OIC instance’s database schema, then use a Local Invoke action to call the function.

Import the JavaScript library file to the project, then use the JavaScript action within the integration flow to reference the library function.

Copy and paste the JavaScript function code into a new JavaScript stage within the integration flow, then map the inbound and outbound data elements in the corresponding Map action.

Use the Function Call action within the integration flow to reference the external URL that is hosting the JavaScript library function.

OIC lookups are based on a static definition, meaning you create and populate them during design time, and cannot be changed by runtime activities.

Using the connectivity agent, you can create hybrid integrations and exchange messages between applications in private or on-premises networks and OIC.

An application-driven integration can contain one or more trigger (source) connections for requests sent to OIC and one or more invoke (target) connections for requests sent from OIC.

When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.

"FREQ=DAILY;BYDAY!=SA,SU;BYHOUR=15"

"FREQ=WEEKLY;BYDAY=MO-FR;BYHOUR=15"

"FREQ=DAILY;BYDAY=MO-FR;BYHOUR=15"

"FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=15"

You cannot drag and drop an XSLT flow control statement directly to a target node element.

You can drag and drop a source data element to multiple target node elements.

You cannot drag and drop a source data element to a target node element that is already mapped.

You cannot drag and drop an XPath function activity directly to a target node element.

"FREQ=DAILY;BYDAY!=SA,SU;BYHOUR=15"

"FREQ=WEEKLY;BYDAY=MO-FR;BYHOUR=15"

"FREQ=DAILY;BYDAY=MO-FR;BYHOUR=15"

"FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=15"

Read File

List Files

Write File

Delete File

Read File in Segments

Write File

Read File

Read File in Segments

Delete File

Download File

Identity certificates

Message protection certificates

Multi Domain SSL Certificate

Unified Communications Certificate

Trust Certificate

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.

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

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.

Nested Switch actions are not supported and, therefore, you may need to create more complex conditional expressions, if necessary.

Data objects returned from actions within a branch of a switch action are not visible in the mainflow of the integration after the switch action.

The switch action must include an otherwise branch.

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.

When you open the Map Editor for a request or response message in an integration, the data structures are automatically populated with the information pulled from the trigger and invoke connections.

An application pattern integration can contain one or more trigger (source) connections for requests sent to OIC and one or more invoke (target) connections for requests sent from OIC.

Using the connectivity agent, you can create hybrid integrations and exchange messages between applications in private or on-premises networks and OIC.

OIC Lookups are based on a static definition, meaning you create and populate them during design time.

Event pattern integrations

Schedule pattern integrations

SOAP trigger connection-based integrations

File trigger connection-based integrations

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.

Any external SFTP client can access File Server if an OIC administrator has configured specific folder access permissions for that client.

To write files to the OIC File Server from an internal OIC integration flow, a File Server action must be used.

Access to the OIC File Server Management REST APIs is limited to users that have been granted the ServiceAdministrator role.

The OIC File Server is disabled by default in a newly provisioned OIC instance.

Failed instances exceeding a specified percentage.

One or more connectivity agents are unavailable.

The email quota has exceeded the threshold.

Certificates that are set to expire within seven days.

You can choose to retain the event subscription, where events are resent if the integration is reactivated again within six hours.

Processing of any new messages will be immediately stopped.

You will not be able to observe any failed instances occurring after the deactivation request.

All existing history, monitoring, and runtime data will be lost.

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.

Performing inbound polling for records to process in an Oracle Autonomous Data Warehouse database

Transferring files to an FTP server installed on-premises or behind a firewall

Creating orders in Oracle E-Business Suite

Publishing messages to Azure Service Bus

You can create the new integration as a different major version of the existing one.

You can clone the existing integration and specify it to use the scheduled orchestration pattern.

You cannot create another integration that uses the same name.

You can create the new integration by using the same display name but with a different identifier.

iCal

cron

YAML

Groovy

get-value-from-lookup

getLookup

get-content-as-string

lookupValue

You must choose an existing REST adapter trigger connection resource.

You cannot convert a scheduled integration to a REST adapter-triggered integration with multiple verbs.

Any existing scheduled parameters will be automatically converted to integration properties.

You cannot convert a scheduled integration with assignments that have the fault data type.