1 out of 1 rated this helpful - Rate this topic

Post-Installation Tasks for Service Provider Foundation

Updated: January 15, 2013

Applies To: System Center 2012 SP1 - Orchestrator

As a hoster administrator, there are a few key tasks that you need to perform after you install Service Provider Foundation. You need to populate the Service Provider Foundation database sufficiently to start managing tenants. There are three ways to get started:

  • Portal applications

    If you installed Service Provider Foundation to use with the Service Management Portal and API, you can register the Service Provider Foundation web service endpoint and start provisioning virtual machine clouds and create plans for tenants. For more information, see the "Provision Virtual Machine Clouds" section of Provision Services in the Installation Guide for Service Management Portal and API.

    If you installed Service Provider Foundation to use with App Controller, you can connect to hosting provider. For more information, see How to Connect to a Hosting Provider in System Center 2012 SP1.

    For detailed information about using portals, see Portals in Service Provider Foundation.

  • Service Provider Foundation Cmdlets

    These Windows PowerShell cmdlets are suited for performing administrative tasks efficiently. For more information see Cmdlets in System Center 2012 - Service Provider Foundation.

  • Administration and VMM Services through OData-based protocols

    You can also use the Service Provider Foundation SDK to the Administration and VMM Services to perform these tasks.

Considerations before creating tenants

Before creating a tenant, consider the following:

  • If a portal application is involved, the tenant can be provided a variety of plans that are defined by specific resource options and user roles. These plans correspond to offers in Service Provider Foundation.

  • The tenant must be able to provide the public key to a self-generated or issued certificate.

  • The tenant can be associated with a trusted issuer, the certification authority who issued the certificate, and with other metadata.

For more information see Managing Certificates and User Roles in Service Provider Foundation.

Creating tenants

A basic, general procedure for populating the database using cmdlets is as follows:

  1. Create a server.

    PS C:\> $server = New-SCSPFServer -Name "server23G.contoso.com" -ServerType 0

  2. Create a stamp.

    A stamp is a logical container for a tenant's association with a server.

    PS C:\> $stamp = New-SCSPFStamp –Name "StampA" –Servers $server

  3. Create a tenant.

    If you are a service provider, a tenant is your paying customer or business unit.

    PS C:\> $tenant = New-SCSPFTenant -Name "Contoso"

  4. Associate the stamp to the tenant.

    You can set the stamp to the tenant and also to a different server if needed.

    PS C:\> Set-SCSPFStamp -Stamp $stamp -Tenants $tenant

  5. Create a Tenant Administrator Role in VMM with the same ID that was generated for the tenant.

    First, enter the following commands to elevate execution policy and to import the Virtual Machine Manager module:

    PS C:\> Set-Executionpolicy remotesigned

    PS C:\> Import-Module virtualmachinemanager

    Enter the following command to create the user role.

    PS C:\> $TARole = New-SCUserRole -Name contoso.cloudspace.com -ID $tenant.Id -UserRoleProfile TenantAdmin

    For more information about defining user roles, see Walkthrough: Creating a Certificate and User Roles for Service Provider Foundation.

Manage Database Connections

Use the Get-SCSPFConnectionString and Set-SCSPFConnectionString cmdlets to manage the connections to the Service Provider Foundation database.

See Also

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft. All rights reserved.