Removing Available Database Servers

The remove operation is used to remove a database from the list of database servers available within the subscription.

In this chapter:

Request Packet Structure

Response Packet Structure

Sample

 
Request Packet Structure

A request XML packet removing a database from the list of databases available within the subscription includes the remove operation node:

<packet>
<webspace>
   <db-servers>
	  <remove>
	   ...
	  </remove>
   </db-servers>
</webspace>
</packet>

 

The remove node is presented by type WebspaceDbServerInput (webspace.xsd). Its graphical representation is as follows:

db-servers-webspace-remove

Note: The interactive schema navigator for all request packets is available here: http://plesk.github.io/api-schemas/1.6.8.0/agent_input.svg.

  • The filter node is required. It serves to specify the criteria by which the necessary service plans will be selected from the database. Data type: domainFilterType (webspace.xsd). See the Available Filters section for details on this node.
  • The db-server node is required. It specifies the database server that will be removed from the list of available database servers. Data type: dbServerInput.
  • The type node is required. It specifies the type of the database server. Data type: string.
  • The id node is optional. It specifies the ID of the database server. Data type: string.
  • The host node is optional. It specifies the host name of the database server. Data type: string.
  • The port node is optional. It specifies the port on which the database server is available. Data type: string.

Important: When creating request packets, put nodes and elements in the order they follow in the packet structure.

 
Response Packet Structure

The remove node of the output XML packet is of complex type (webspace.xsd)which has the following presentation:

db-servers-webspace-remove-resp

Note: The interactive schema navigator for all response packets is available here: http://plesk.github.io/api-schemas/1.6.8.0/agent_output.svg.

  • The result node is required. It wraps the response got from the server. Data type: resultFilterType (common.xsd).
  • The status node is required. Specifies the execution status of the operation. Data type: string. Allowed values: ok | error.
  • The errcode node is optional. Returns the error code when the operation fails. Data type: unsignedInt.
  • The errtext node is optional. Returns the error message if the operation fails. Data type: string.
  • The filter-id node is optional. Returns the parameter by which the service plan was filtered by in the request packet. Data type: anySimple.
  • The id node is optional. Returns the identifier of the service plan to which the application was added. Data type: id_type (common.xsd).
 
Sample

The following request removes the MySQL database server available on the port 3306 of localhost from the list of database servers available with the subscription with id 1:

<packet>
  <webspace>
    <db-servers>
      <remove>
        <filter>
          <id>1</id>
        </filter>
        <db-server>
          <type>mysql</type>
          <host>localhost</host>
          <port>3306</port>
        </db-server>
      </remove>
    </db-servers>
  </webspace>
</packet>

Response:

<packet>
  <webspace>
    <db-servers>
      <remove>
        <result>
          <status>ok</status>
          <filter-id>1</filter-id>
          <id>1</id>
        </result>
      </remove>
    </db-servers>
  </webspace>
</packet>

 

Leave your feedback on this topic here

If you have questions or need support, please visit the Plesk forum or contact your hosting provider.
The comments below are for feedback on the documentation only. No timely answers or help will be provided.