Oracle and Customer Responsibilities for Web Application Acceleration
Understand the responsibilities for both Oracle and yourself when using Web Application Acceleration.
Oracle accepts responsibility for managing tasks related to the administration and monitoring of the Web Application Acceleration service. You, as the customer, are responsible for the certain aspects of the service as well. The following table lists areas of responsibility for using and maintaining the Web Application Acceleration service.
| Responsible Party | Task | Details |
|---|---|---|
| Oracle | Provisioning Web Application Acceleration configuration | Oracle is responsible for provisioning and ensuring that a load balancer is running with the Web Application Acceleration service that is configured by the customer. |
| Oracle | Monitoring service health | Oracle is responsible for monitoring the health of Web Application Acceleration service resources and for ensuring their availability. |
| Oracle | Auditing | Oracle is responsible for logging API calls made to the Web Application Acceleration service and for making these logs available to the customer for auditing purposes. |
| Oracle | Providing alerts and notifications | Oracle is responsible for providing an alert and notification feature for service events. Customer is responsible for monitoring any Web Application Acceleration service alerts that may be of interest. |
| Oracle | Purging cache | Oracle is responsible for purging the cache when requested by the customer. |
| Customer | Configuring and tuning of the Web Application Acceleration service | Customer is responsible for configuration and tuning of the Web Application Acceleration service to accelerate their web application. |
| Customer | Restricting access to the backend servers | Customer is responsible for restricting backend server access to load balancers only. This restriction ensures that the Web Application Acceleration service cannot be bypassed. |
| Customer | Configuring HTTPS | Customer is responsible for configuring the load balancer to use HTTPS. Using HTTPS ensures that traffic between the web application client and the load balancer is encrypted. |
| Customer | Setting up caching headers for responses that need to be cached. | Customer is responsible for setting up cache headers for responses the Web Application Acceleration service will cache. |
| Customer | Requesting a cache purge | Customer is responsible for requesting Oracle to purge the cache. |