PUT Update Perimeter Server

Changes a Perimeter Server object on the server.

With the updatePerimeterServer/{Perimeter Server Name} method, you can update the existing Perimeter Server defined on the Secure Proxy Configuration Manager.

This API method requires authentication, and therefore the authentication token generated at login must be passed in through the "X-Authentication" header.

Table 1. Update Perimeter Server request details
Update Perimeter Server request details.
Method	Resource	URI	Description
`PUT`	`Perimeter Server`	/sspcmrest/sspcm/rest/perimeterServer/updatePerimeterServer/{Perimeter Server Name}	Updates the existing Perimeter Server with the XML provided.

Table 2. Update Perimeter Server URI input parameters
Update Perimeter Server URI input parameters
Parameter	Required or Optional	Description	Validation	Valid values
Perimeter Server Name	Required	Updates the existing Perimeter Server with the new XML.	Must be a non-empty string	A-Z a-z 0-9 ._-

HTTP Perimeter Server request

The following example shows the HTTP request:

PUT https://localhost:8443/sspcmrest/sspcm/rest/
perimeterServer/updatePerimeterServer/LessSecureZone2
“X-Authentication”: “61504f4a524b48532b776a3467643733374b526368513d3d”
“Content-Type”: “application/xml”
XML corresponding to defining a Perimeter Server

HTTP Perimeter Server response

The following example shows the JSON response.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <XmlResponse>
    <httpCode>200</httpCode>
    <httpStatus>OK</httpStatus>
    <action>None</action>
    <message>perimeterServerDef MyLessPerimeterServer2 updated.
</message>
    <messageLevel>INFO</messageLevel>
    <results/>
    </XmlResponse>