The primary integration methods supported with cloud services are (a) inbound and outbound files, and (b) inbound and outbound web services. Other protocols and methods (JMS, SQL Net, etc.) are not currently supported.

Besides standard Oracle Utilities Application Framework integration modules, no additional extract, transform, and load (ETL) capabilities or middleware are provided with cloud service offerings. Oracle Cloud middleware solutions—such as SOA Cloud Service (available via Platform-as-a-Service) or Integration Cloud Service —need to be licensed to address advanced integration requirements such as complex ETL, orchestration, etc. Alternatively an on-premise middleware solution could be used.

Inbound File Processing: Files are uploaded to Object Storage and processed via scheduled batch jobs. Implementation-specific file parsing and processing logic can be introduced using browser-based Oracle Utilities Application Framework tools. Refer to Uploading Records in the Plug-in Driven Background Processes section in the Administrative User Guide or the online help for more information. Please also review the File Access - Cloud Object Storage section in Chapter 6: Data Access and Analytics.

Outbound File Processing: File-based extracts can be generated and made available for download and further processing. Implementation-specific file processing and generation logic can be introduced using browser-based Oracle Utilities Application Framework tools. Refer to Processing System Records in the Plug-in Driven Background Processes section in the Administrative User Guide or the online help for more information.

Large-volume data conversion and loading is supported. See Chapter 11: Data Conversion Guidelines for more information.

Web services are supported through Inbound Web Services (IWS) and Outbound Messages. All inbound and outbound web services communication must be HTTPS. Refer to Inbound Web Services and Outbound Messages in the Administrative User Guide or the online help for more information.

Note that in order to call Inbound Web Services, you must provide a user/password for authentication and authorization (the user must be defined in Identity and Access Management Identity Domains with the 'AppWebServices' Application Role and as an application User). Inbound Web Services support both SOAP and REST. Outbound Messages may only reference public IP addresses, and those addresses must be on an 'allowlist' (which can be provided to Cloud Operations via a service request ticket).

For integrations that involve outbound synchronization to other systems driven by online activity, real-time synchronous outbound messages are not recommended. Rather use the business object batch monitor processing on a frequent basis to process queued messages. This involves using the deferred monitor batch set on the PENDING state of the Sync Request so that message processing occurs asynchronously.

SSL certificates must be created using certification authority. Self-signed SSL certificates are not supported. Also reference the How to access SOAP and REST Services in Oracle Utilities Enterprise Cloud Services document on My Oracle Support (Document ID 2564697.1).

Upload and attachment of implementation-specific xsl files to process xml payloads is supported through the Managed Content portal for relevant product or cloud service. Refer to Maintaining Managed Content in the Administrative User Guide or the online help for more information.