Product Documentation

Plan

Jun 05, 2015
Updated: 2013-04-18
When deploying Services Manager, you have many choices of deployment designs and features which you can tailor to the needs of the services you want to offer and the customers you serve. A typical process of planning a Services Manager deployment includes:
  • Becoming familiar with Services Manager setup by creating a one-server or two-server test deployment.
  • Determining the number of servers you need for your deployment, deciding which roles each server will perform, and evaluating hardware requirements.
  • Deciding which services you want to offer customers and resellers, and determining the deployment requirements for each service.
  • Creating the network infrastructure design.
  • Defining the installation processes.
  • Creating and testing a pre-production pilot deployment based on your design.
  • Releasing the deployment into production.

Deployment Overview

A typical Services Manager deployment process includes:
  • Phase 1: Services Manager platform
  • Phase 2: Services deployment
  • Phase 3: Customer and user provisioning

Phase 1: Services Manager platform

The Services Manager platform represents a series of servers that perform provisioning tasks, authenticate and manage users, host the control panel interface and API services, store and process data from the main database, and manage billing and usage. These servers must be fully configured before services are deployed. A Services Manager deployment includes the following core components (or server roles) that you install and configure:
Web server
The web server hosts the control panel’s web interface and API services. The control panel is the primary user interface for service providers, resellers and end-customer users. The customer administrator can manage the organization’s users and associated services within the same system. Users can perform administrative and self-service tasks that have been delegated to them. Provisioning requests are sent from the web server to the Provisioning Engine through a Microsoft Message Queue.
Databases
The main system databases are the Microsoft SQL Server repositories for user, customer, and configuration information. Several system databases are automatically created when you install and configure the server roles. The Services Manager Reporting Service uses Microsoft SQL Server Reporting Services.
Provisioning Engine
The Provisioning Engine performs all provisioning tasks. It expedites requests from the web server and automates managed services and resources.
Directory web service
The Directory web service provides the web server with function calls related to Active Directory, such as user authentication, user account status inquiries, user enabling and disabling, and security group management.
Data warehouse
The data warehouse performs scheduled storage of historical data from the main system database, and manages the creation and sending of usage and billing reports.
Report Mailer
The Report Mailer gathers anonymous usage data and emails usage reports to the Citrix license monitor. Customer and user information is not transferred, only the number of customers and users-per-service.
To prepare your environment for these components, you perform the following tasks:
  • Review the system requirements for each server role and perform any initial server configuration required.
  • Determine whether you will install and configure these server roles using the graphical user interface or the command line.
  • Determine which server will host each server role. For example, the Directory web service is typically installed on the same server as the Provisioning Engine. However, for a large deployment, you might consider using separate SQL servers for hosting the reporting and billing databases.

Deploying the Services Manager platform also includes creating the first administrator user for the deployment. This user represents the top-level administrator account and has permission to perform all control panel tasks.

Phase 2: Services deployment

Deploying services includes installing and configuring services for resources such as Microsoft Exchange, Citrix Apps and Desktops, and Microsoft SharePoint. Before deploying any service, you must ensure the resources supporting the service are fully deployed in your network environment. For example, to deploy the Hosted Exchange service, Services Manager requires you have a working Exchange deployment in your environment. The Deploy services section of the Services Manager documentation describes the configurations required to enable these resources to function successfully with the Services Manager control panel. However, for details about deploying specific resources, you will need to refer to the product documentation for these resources.

Phase 3: Customer and user provisioning

Provisioning customers and users represents a series of tasks for enabling resellers to sell specific services, making services available to end-customers, enabling customers' users to access services, and assigning security roles. To provision customers and users, you perform the following tasks:
  1. Create the customer profile.
  2. Create the customer administrator user. Some customers might require additional administrator users to manage specific services. When you create these additional users, you can assign appropriate security roles.
  3. Enable and configure the services that you are providing to the customer.
  4. Create users for the customer and assign appropriate security roles.
  5. Provision services to users.