Retrieving Descriptor of Hosting Settings

Use the get-physical-hosting-descriptor operation to retrieve descriptors of hosting settings set for service plans. For details on descriptors, refer to the Representation of Object Descriptor section. For details on hosting settings, refer to the Hosting Settings section.

In this chapter:

Request Packet Structure

Response Packet Structure

Samples

 

Request Packet Structure

A request XML packet retrieving descriptor of service plan hosting settings includes the get-physical-hosting-descriptor operation node:

<packet>
<service-plan>
   <get-physical-hosting-descriptor>
   ...
   </get-physical-hosting-descriptor>
</service-plan>
</packet>

 

The get-physical-hosting-descriptor node is presented by type DomainTemplateGetInputType (domain_template.xsd). Its graphical representation is as follows:

get-physical-hosting-descriptor-input

  • The filter node is required. It specifies a criteria by which service plans will be selected. Data type: DomainTemplateFilterType (domain_template.xsd). See the Available Filters section for details on this node.
  • The owner-id node is optional. It specifies the ID of the service plan owner. Data type: integer.
  • The owner-login node is optional. It specifies the username of the service plan owner. 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 get-physical-hosting-descriptor node of the output XML packet is of type DomainTemplateDescriptorOutput (domain_template.xsd) which is structured as follows:

get-physical-hosting-descriptor-output

  • The result node is required. It wraps the result of the requested get-physical-hosting-descriptor operation. Data type: ResultFilterType (common.xsd).
  • The status node is required. It returns the execution status of the get-physical-hosting-descriptor operation. Data type: result_status (common.xsd). Allowed values: ok|error.
  • The errcode node is optional. Is used to return the error code when the get-physical-hosting-descriptor operation fails. Data type: unsignedInt.
  • The errtext node is optional. Can be used to return an error message if the get-physical-hosting-descriptor operation fails. Data type: string.
  • The id node is optional. It is required if the operation succeeds and the results are filtered by ID. It returns an ID of the service plan which hosting settings descriptor was displayed. Data type: id_type (common.xsd).
  • The name node is optional. It is required if the operation succeeds and the results are filtered by name. It returns a name of the service plan which hosting settings descriptor was displayed. Data type: string (common.xsd).
  • The guid node is optional. It is required if the operation succeeds and the results are filtered by GUID. It returns a GUID of the service plan which hosting settings descriptor was displayed. Data type: string (common.xsd).
  • The external-id node is optional. It is required if the operation succeeds and the results are filtered by external ID. It returns the external ID of the service plan which hosting settings descriptor was displayed. Data type: string (common.xsd).
  • The descriptor node is required if the get-physical-hosting-descriptor operation succeeds. It specifies object descriptor. For details, refer to the Representation of Object Descriptors section. Data type: string.

    Note: This descriptor contains hosting settings extensions. For details, refer to the Representation of Object Descriptors: Property Descriptor > Extension of Limits Descriptor section.

 

Samples

The following packet retrieves hosting settings descriptor for a service plan:

<packet>
<service-plan>
<get-physical-hosting-descriptor>
   <filter>
      <name>base_plan</name>
   </filter>
<get-physical-hosting-descriptor>
</service-plan>
</packet>

A positive response received from the server looks as follows:

<packet>
  <service-plan>
    <get-physical-hosting-descriptor>
      <result>
        <status>ok</status>
        <name>base_plan</name>
        <descriptor>
                  ...
          <property>
            <name>miva</name>
            <type>boolean</type>
            <writable-by>none</writable-by>
            <label>__miva_unix_support</label>
            <extension>
              <service>
                <domain>1</domain>
                <subdomain>1</subdomain>
              </service>
            </extension>
          </property>
                  ...
          <bind>
            <ref>webstat_protected</ref>
            <relevant>
              <name>webstat</name>
              <value>none</value>
            </relevant>
            <read-only>1</read-only>
          </bind>
               ...
        </descriptor>
      </result>
    </get-physical-hosting-descriptor>
  </service-plan>
</packet>

 Note: Data structures that describe a number of properties are omitted to improve the readability of the sample.

A single filter can specify multiple plans, all specified either by ID or by name.

<packet>
<service-plan>
<get-physical-hosting-descriptor>
   <filter>
      <name>base_plan</name>
      <name>quick_plan</name>
   </filter>
</get-physical-hosting-descriptor>
</service-plan>
</packet>
 

Leave your comments on this page

Leave your feedback or question on this documentation topic below. For technical assistance, contact your hosting service provider or submit a request to Plesk support. Suggest new features for Plesk here. Discuss general questions on the Plesk forum. All offtopic comments will be removed.