Web Hosting Resource Manager::AllocateDedicatedWebServer

  • Article

This procedure allocates a dedicated Web server to a specified organization.

Arguments

Input argument Required Description

<org>

Yes

The LDAP path of the owning organization.

<serverClassName>

Yes

The server class group to select the server candidate from.

<algorithm>

Yes

Defines the server candidate selection behavior. The allowed values are (note these are case sensitive):

  1. tightPack: From the set of servers that can satisfy the capacity of an allocation, the servers are ranked favoring those with the least amount of free space.

  2. evel: From the set of servers that can satisfy the capacity of an allocation, the servers are ranked favoring those with the most amount of free space.

<preferredDomainController>

Yes

<serverName>

No

The name of the IIS Web Server. Overrides automatic selection behavior. However the specified server is still evaluated to see if it has been added to Resource Manager, has the necessary resources to satisfy the request, is a member of the specified server class, and is set with a shared flag = 0.

Dd279058.note(en-us,TechNet.10).gifNote
Despite the override of automatic selection behavior, you are still required to provide the <algorithm> parameter in the request.

<container>

No

A starting LDAP container to look for the server in. The procedure performs an LDAP search to resolve the <server>/<serverName> to the Active Directory computer object. You can improve the performance of this search by specifying a default container (e.g. LDAP://CN=Computers,DC=fabrikam,DC=Com).

Output Argument

The server selected for the allocation. For example:

    <server> 
      <GUID>AFF7B1E1DF90A042BABA475A5D5E155D</GUID> 
 
      <serverName>WEB01</serverName> 
 
    </server>

Remarks

Access Level

Private.

Provisioning Steps

  1. Find resources to satisfy request

  2. Allocate the specified Web site from Resource Manager

Server Selection Behavior

  1. All IIS Web Server resources are retrieved (if serverName is specified, only this resource is retrieved) if shared = 0 and they are not already allocated to another owner

  2. Discard any that are not members of the specified serverClassName

  3. Rank the server candidates by algorithm (level or tightpack) based on number of free Web sites.

  4. Rank the server candidates by algorithm (level or tightpack) based on the amount of free megabytes

  5. Select the top candidate and allocate the Web site.

Security

  1. Impersonate Caller.

Note

The access level of this procedure is private. It is intended to be called from other namespaces that perform their own security checks.

Sample Code

Example XML Request

<request> 
  <procedure> 
 
    <execute namespace="Web Hosting Resource Manager" procedure="AllocateDedicatedWebServer" impersonate="1"> 
 
      <executeData> 
 
        <org>LDAP://OU=alpineskihouse,OU=consolidatedmessenger,OU=Hosting,DC=fabrikam,DC=Com</org> 
 
        <preferredDomainController>AD01-wh.fabrikam.com</preferredDomainController> 
 
        <algorithm>level</algorithm> 
 
        <serverClassName>IISWebServerBasic</serverClassName> 
 
      </executeData> 
 
      <after source="executeData" destination="data" mode="merge" /> 
 
    </execute> 
 
  </procedure> 
 
</request>

Example XML Response

No example XML response.

Applies To

Web Hosting Resource Manager Namespace for:

  • Hosted Messaging and Collaboration version 4.5

  • Hosted Messaging and Collaboration version 4.0

  • Hosted Messaging and Collaboration version 3.5

  • Hosted Messaging and Collaboration version 3.0

  • Windows-based Hosting version 4.5

  • Windows-based Hosting version 4.0

  • Windows-based Hosting version 3.5

  • Windows-based Hosting for Applications version 1.0

See also

Tasks

Web Hosting Resource Manager::DeallocateDedicatedWebServer