The name of the backend server to update.
If the backend was created with an explicitly specified name, that name should be used here.
If the backend was created without explicitly specifying the name, but was created using ipAddress, this is specified as
Example: {@code 10.0.0.3:8080} or {@code ocid1.privateip..oc1.<unique_ID>:8080}
The name of the backend set associated with the backend server.
Example: {@code example_backend_set}
For optimistic concurrency control. In the PUT or DELETE call for a resource, set the {@code if-match} parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the current etag value of the resource.
The OCID of the network load balancer to update.
The unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.
A token that uniquely identifies a request so that it can be retried in case of a timeout or server error without risk of rerunning that same action. Retry tokens expire after 24 hours but they can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made
Details for updating a backend server.
Click here to see how to use UpdateBackendRequest.