OCI App Integration Pro (1Z0-1042-25) flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

What is an OIC instance?

A region-scoped, identity-domain-scoped runtime of Oracle Cloud Application Integration that executes integrations, stores artifacts in its metadata repository, and hosts connections, lookups, and monitoring data.

Integration instance states

An instance moves through ACTIVATED, RUNNING, WAITING, COMPLETED, FAILED, or ABORTED. WAITING indicates an asynchronous callback or human task is pending; FAILED indicates an unhandled fault.

Project (package) purpose

A project groups related integrations, connections, and lookups for role-based access and for export/import as a single archive between environments.

Local lookup vs REST lookup

A local lookup stores static reference data inside the integration and is versioned with it; a REST lookup fetches values at runtime from an external service, so changes apply without redeployment.

Connectivity agent role

An agent runs inside a private network, opens an outbound HTTPS tunnel to the OIC instance, and proxies adapter calls to on-premises endpoints such as databases and file servers.

Agent group

A logical name configured on a connection that one or more agents join. Multiple agents in a group provide high availability and distribute adapter traffic.

REST adapter trigger vs invoke

As a trigger, the REST adapter exposes an endpoint that external callers invoke to start an integration. As an invoke, it calls an external REST service.

Database adapter polling strategies

Polling can use a timestamp column, a numeric sequence, or a logical-delete flag to detect new or changed rows. Each strategy requires a suitable column and a polling schedule.

Connection test failure causes

Common causes are wrong credentials, an unreachable endpoint URL, a missing or offline agent in the configured agent group, or a TLS certificate not trusted by the runtime.

App-driven trigger

A trigger that fires when a source application publishes a business event, such as an ERP or HCM event. The integration runs asynchronously with the event payload.

Scheduled trigger recurrence

A trigger configured with an iCal recurrence expression and timezone, such as FREQ=DAILY;INTERVAL=1, which creates one instance per recurrence until the integration is deactivated.

Callback pattern

An integration calls an asynchronous external service, exposes a callback endpoint, and waits in WAITING state until the service posts the result to that URL, then resumes processing.

Scope activity

A container that groups activities, defines local variables, and can carry its own fault handler, isolating error handling to that section of the orchestration.

For-each activity

An activity that iterates over an array, mapping each element in turn. It can run sequentially or in parallel and is the standard way to process repeating payload structures.

Global fault handler

The integration-wide fault handler that catches faults not handled by any inner scope. It is the last resort and cannot itself be fault-handled.

XSLT version in OIC

The visual mapper generates XSLT, and custom XSLT can be imported for complex transformations. The mapper wraps the stylesheet and exposes the resulting target structure.

lookupValue function

A mapper function that takes a lookup name, source column, source value, target column, and default, and returns the matching target value or the default when no match exists.

Conditional mapping

Use the if function or a choose/when construct in the mapper to produce a target value only when a condition holds; otherwise map an alternative or a default.

Namespace mismatch error

A mapping error where the target element's namespace does not match the schema, producing element-not-found faults. Verify the schema namespace on both source and target.

Switch activity

A routing activity that evaluates branches in order and executes the first true branch, with an optional default branch for when no condition matches.

Call activity

An activity that invokes another integration synchronously or asynchronously, letting you modularize reusable logic and isolate fault handling to the called integration.

Rethrow vs suppress fault

Rethrow re-raises a caught fault after logging, marking the instance FAILED. Suppress lets the instance continue and complete successfully despite the error.

Fault categories

Binding faults come from adapters and connections, validation faults from schema or mapping mismatches, and business faults from application errors returned by the target service.

OAuth client credentials flow

OIC sends client ID and secret to the token endpoint, receives an access token, and calls the target with a Bearer token. No user interaction is involved.

OAuth authorization code flow

A user consents once, OIC receives an authorization code, exchanges it for access and refresh tokens, and uses the stored refresh token to obtain new access tokens.

Vault-backed credentials

Connection credentials can reference secrets stored in OCI Vault instead of being entered directly, keeping passwords and client secrets out of the integration artifact.

OIC service roles

ServiceAdministrator manages the instance, ServiceDeveloper designs integrations, ServiceMonitor views instances and logs, and ServiceInvoker calls exposed endpoints. Assign least privilege.

Instance activity stream

The step-by-step view of an instance showing each activity's status and payload. The first red activity marks the failure point for troubleshooting.

Tracking variables

User-defined fields captured during execution and displayed in monitoring, letting operators identify an instance by business key without opening the full payload.

Resubmit vs recover

Resubmit re-runs a failed instance from the beginning with the same payload. Recover replays scheduled instances that were missed while the integration was inactive.

Project export archive

An archive containing the project's integrations, connections, lookups, and certificates. On import, connections are mapped to target connections to keep environment-specific settings.

Integration versioning

Each activation creates a new version. Activating a previous version rolls back. Deactivation stops new instances but lets running instances finish.