Product Documentation

Plan for deploying services

Jun 05, 2015
Updated: 2013-02-27
Before you begin the process of deploying services for Services Manager, create a deployment plan that includes the following information:
  • The types of services you will offer through Services Manager. For example, hosted email, virtual machines, web hosting, and so on.
  • The number of customers and users that each service will need to support. For some services, this has a significant impact on the size of the resource deployment required.
  • The network and server resources that are required to support your service offerings. For example, if you offer Citrix services, you will need to deploy a XenApp farm.
  • The location where each service will be deployed.
  • The topology of the deployment including firewalls, required ports and protocols, and the servers hosting each service offering.
  • Test plans for verifying the integrity and performance of resource deployments before and after deploying services.

Planning guidelines

  • Review the installation and configuration topics for each service carefully and make note of the information you will need to supply for each task.

Service deployment summary

In general, deploying a service includes the following tasks:

Step 1: Deploy the network and application resources that are required to support your service offerings.

All services are based on the network and server resources in your environment. Therefore, these resources need to be fully configured and operational prior to integration with Services Manager. For example, if you intend to offer the Hosted Exchange service, you must first deploy Exchange with multi-tenant support in your environment. Likewise, if you intend to offer Virtual Machines or Windows Web Hosting services, you must first deploy the network resources -- for example, virtual networks, DNS, and web servers -- that are required for customers to use these services.

Step 2: Install the web service.

Some services require the installation of a web service for integration with the Services Manager platform. Web services are installed on the server that will be hosting the service, using the Services Manager Setup Tool or the command line. For example, the Citrix web service is installed on a XenApp server in your environment. Web services are executed with specific parameters which are explained in the installation topic for each service. After the web service is installed, you can configure the service. For services that do not require a web service, you can skip the installation step and configure the service right away. For more information about which services require web service installation, see Deploy services.

Step 3: Configure the service using the control panel.

All services require configuration through the Services Manager control panel. Configuration includes enabling the service, specifying server resources, adding credentials, and configuring service settings. During the configuration process, you create the customer and user plans you want to offer, assign cost values, and specify resource limits for customers and users. After you configure the service, you can provision the service to customers.

Step 4: Provision the service to customers.

In general, provisioning a service enables specific customers (including resellers) to access the service and provision it, in turn, to their users or sub-customers. This occurs through the Services Manager control panel. During the provisioning process, some services might require additional configuration. For example, when provisioning the BlackBerry service to a reseller, you configure a user limit that restricts the number of users the reseller can provision. Additionally, the customer's primary administrator user (the customer administrator) is created. After the customer is provisioned with the service, the customer can provision the service to its users or sub-customers.

Step 5: Provision the service to users.

As with provisioning services to customers, services are provisioned to users through the Services Manager control panel. Typically, this task is handled by the customer administrator or another customer user with the appropriate security role. During the provisioning process, some services might require additional configuration. For example, when provisioning the Lync 2010 for Hosting service to a user, the customer can specify the user's telephone extension. After users are provisioned, the customer provides any additional information or assistance needed for using the service, such as configuring Microsoft Outlook or Office Communicator to access hosted Exchange or Office Communication Server services.