--- title: Oracle Smart Operations in Fusion Cloud SCM slug: litmusedge/product-features/integration/integration-connectors/oracle/oracle-smart-operations-in-fusion-cloud-scm docTags: createdAt: 2026-10-02T20:54:32.309Z --- ## Overview The Oracle Smart Operations in Fusion Cloud SCM connector enables Litmus Edge (LE) to connect with Oracle Fusion Cloud REST APIs using OAuth2 authentication. ## Supported communication - Outbound (Publish data from Edge to Oracle Fusion Cloud) - Yes - Inbound (Subscribe data from Oracle Fusion Cloud to Edge) - No ## Configurations | **Field** | **Details** | **Required** | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Name | Name of the connector instance. | Yes | | Method | The HTTP method used for requests. Oracle Fusion Cloud supports `POST` only. | Yes | | Endpoint | Full URL of the Oracle Fusion Cloud REST API endpoint to POST data to. | Yes | | OAuth2 - Token Endpoint | URL of the OAuth2 token endpoint used to obtain access tokens before each request. | Yes | | OAuth2 - Client ID | OAuth2 client ID used for authentication. | Yes | | OAuth2 - Client Secret | Client secret credential paired with the Client ID. | Yes | | OAuth2 - Scope | OAuth2 scope, as a comma-separated value. | No | | Headers | Custom HTTP headers sent with each request as key-value pairs. Example: `Authorization: Bearer ` or `Content-Type: application/json`. | No | | Params | URL query parameters appended to the endpoint on each request, as key-value pairs. | No | | Mapping | Maps incoming message field names to Oracle REST API field names. | No | | Request timeout | Request timeout in seconds. | No | | Insecure skip verify | Controls whether a client verifies the server's certificate chain and host name. | No | | Parallel Publish Count | Number of messages published in parallel. Higher values increase throughput and resource usage. | No | | Response Topic | NATS response topic payload for all requests. | No | | Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No | ## Persistent storage configurations | **Field** | **Details** | **Required** | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No | | Persistent storage size limit | Set the size limit for storing persisted data in GB. | No | | Queue mode | Select the sequence of data transfer: `FIFO` or `LIFO`. Selecting `FIFO` (First In First Out) sends the earliest message first. Selecting `LIFO` (Last In First Out) sends the latest message first. | No |