Oracle and Customer Responsibilities
This table summarizes the division of responsibilities between Oracle and customers in Oracle Integration 3.
R=Responsible, A=Accountable, C=Consulted, I=Informed
| Task | Oracle's Role | Customer's Role | Comments |
|---|---|---|---|
| Patching and upgrade | R, A | I | Oracle completes functional and security patching updates work on your behalf, with no work required by you. See Patching Updates to Your Oracle Integration 3 Instance.
Do not stop or start instances on a nightly basis. During routine maintenance patching, lifecycle operations are disabled. This may lead to a situation where the service instance cannot be started or stopped for several hours while the patching cycle completes. See Stop or Start an Instance. |
| High availability | R, A | I | - - |
| Disaster recovery | C | R, A | For information on disaster recovery options, see Enable Disaster Recovery. |
| Security and compliance | R, A | I | - - |
| Data retention | R, A | I | By default, Standard and Enterprise edition instances retain data for 32 days, and Healthcare edition instances retain data for 184 days. If you have an Enterprise edition instance, you can change the data retention period if you want. See Edit the Data Retention Period. |
| Maintenance notifications | R, A | I | See Update Notifications. |
| Service provisioning | C, A | R, I | See Create an Oracle Integration Instance. |
| User setup, roles, and permissions | C | R, A | See Manage Oracle Cloud Console Access and Manage User Access. |
| Overage tracking and management | C | R, A | See Monitor Billing. |
| Test-to-production promotion | C | R, A | Export and import design-time metadata to move an existing configuration to a new instance. See Clone the Design-Time Metadata of an Entire Service Instance in Using Integrations in Oracle Integration 3. |
| On-premises connectivity agent installation | C | R, A | You are responsible for the health and monitoring of your on-premises connectivity agents. Oracle doesn't have access to the servers that host your on-premises connectivity agent or the agent logs. See Install the Connectivity Agent in Using Integrations in Oracle Integration 3. |
| On-premises connectivity agent upgrade/patching | R, A | I | Note: When a new version of the on-premises connectivity agent becomes available, your host is automatically upgraded with the latest version.
There is no downtime or interruption of service for in-progress integrations that use the connectivity agent. You are notified of upgrade success. |
| Source control and continuous integration | C | R, A | You can implement continuous integration/continuous delivery in Oracle Integration. See Integrate Projects and Project Deployments with a GitHub Repository.
You should also consider keeping a backup of your data. See Preserve Your Instance Data. |
| Integration monitoring and management | C | R, A | Make sure that you have enough disc space on your file servers for any integration activity. If you're using Oracle Integration's embedded SFTP server, you can view your available space in the File Server settings. See Configure File Server Settings in Using File Server in
Oracle Integration 3.
Oracle Integration provides tools to help you monitor your integrations. See Monitor Integrations During Runtime in Using Integrations in Oracle Integration 3. Make sure you're also monitoring events generated outside of Oracle Integration. |