Update a Service

put

/apiplatform/management/v1/services/{serviceId}

Updates the {serviceId} service.

Users requesting this resource must be assigned the Service Manager role and must be issued the Manage Service grant for the specified service.

Request

Supported Media Types
Path Parameters
Body ()
Root Schema : UpdateServiceRequest
Match All
Show Source
Nested Schema : ServiceDef
Type: object
Show Source
Nested Schema : implementation
Type: object
The service's configuration.
Show Source
Nested Schema : specification
Type: object
The service's configuration.
Show Source
Nested Schema : wsdl
Type: object
The WSDL specification configuration
Show Source
Back to Top

Response

Supported Media Types

200 Response

The service was updated.

400 Response

Bad request, indicates a problem with the input parameters.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : errorDetails
Type: array
additional errors
Show Source

403 Response

Forbidden.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : errorDetails
Type: array
additional errors
Show Source

500 Response

Unexpected error.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : errorDetails
Type: array
additional errors
Show Source
Back to Top

Examples

The following example shows how to update a service by submitting a PUT request on the REST resource using cURL. For more information about cURL, see Use cURL

curl -i -X PUT 
-u apicsadmin:password
-H "Content-Type:application/json"
-d @service-update.json
https://example.com/apiplatform/management/v1/services/{serviceId}

where {serviceId} is a unique Id of a specific service. See Get Services.

Example of Request Body

The following shows an example of the request body, included with the request above in a file named service-update.json.

{
    "name": "traffic",
    "description": "canned service",
    "implementation": {
        "executions": {
            "request":  [ "1"  ],
            "response": [ "2" ]
        },
        "policies": [
            {
                "id": "1",
                "type": "o:BackendRequest",
                "version": "1.0",
                "config": {
                    "endpoints": [
                        {
                            "url":  "http://host:80/endpoint"
                        }
                    ]
                }
            },
            {
                "id": "2",
                "type": "o:BackendResponse",
                "version": "1.0",
                "config": {}
            }
        ]
    }
}

Example of Response Headers

The following shows an example of the response headers.

HTTP/1.1 204 No Content
Server: Oracle-Traffic-Director/12.2.1.0.0
Date:  Sun, 22 Oct 2017 08:34:10 GMT
X-oracle-dms-ecid:  49d14691-2176-4c99-aed3-38438604f528-00001e4e
X-oracle-dms-rid: 0:1
Via: 1.1 otd_opc
Proxy-agent: Oracle-Traffic-Director/12.2.1.0.0
Back to Top