Академический Документы
Профессиональный Документы
Культура Документы
Summary: Configure domain names, service applications, and URLs for apps for SharePoint 2013.
To enable users to install and use apps for SharePoint in their sites, you must configure your environment to support them. This article describes how to configure your
environment to support apps. Use the Plan for apps for SharePoint 2013 article to review options and determine the values to use for configuration settings in this article.
Important:
The steps in this article apply to both SharePoint Foundation 2013 and SharePoint Server 2013.
One of the feature updates of the March 2013 Public Update for SharePoint 2013 enables you to use multiple app domains in SharePoint 2013 environments with
alternate access mapping or host-header web application configurations. For more information, see Enable apps in AAM or host-header environments for SharePoint
2013.
The following illustration summarizes the steps to take to configure an environment for apps for SharePoint.
These configuration steps result in example app URLs such as the following:
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
http://Apps-12345678ABCDEF.ContosoApps.com/sites/SiteName/App1Name/Pages/Home.aspx
https://Apps-3456789BCDEFG.ContosoApps.com/sites/SiteName/WebName/App2Name/Default.aspx
You must be a member of the Farm Administrators group to perform the steps in this article. For some steps, you must also be a domain administrator on the
domain controller.
Confirm that the SharePoint Administration (spadmin) and SharePoint Timer (sptimer) services are running.
To verify this, click Start, point to Administrative Tools, and then click Services. In the Services list, verify that the SharePoint Administration and SharePoint
Timer services are running.
Note:
Because SharePoint 2013 runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide.
SharePoint 2013 supports the accessibility features of supported browsers. For more information, see the following resources:
Depending on your configuration (for example, if you are using WINS forward lookup), you might have to create a new forward lookup zone first, or you can start with a
wildcard CNAME entry in the same zone as the SharePoint site domain. In the following procedures, you create a forward lookup zone, and then create a wildcard alias
record for the DNS domain name that allows for individual apps to create unique domain names within your app domain. In these procedures, we use DNS Manager for
Windows Server 2008 R2. For more information about DNS server in Windows Server 2008 R2, see DNS Server. If you have a different type of DNS server, follow the
procedures in the documentation for that server type.
To create a forward lookup zone for the app domain name
1. Verify that the user account that performs this procedure is a domain.administrator on the domain controller.
3. In DNS Manager, right-click Forward Lookup Zones, and then click New Zone….
5. In the Zone Type page, accept the default of Primary zone, and then click Next.
6. In the Active Directory Zone Replication Scope page, select the appropriate replication method for your environment (the default is To all DNS servers in this
domain), and then click Next.
7. In the Zone Name page, in the Zone name box type the name for your new app domain name (for example, ContosoApps.com), and then click Next.
The New Zone Wizard shows the new domain name for apps.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
8. On the Dynamic Update page, select the appropriate type of dynamic updates for your environment (the default is Do not allow dynamic updates), and then
click Next.
9. On the Completing the New Zone Wizard page, review the settings, and then click Finish.
For more information about how to create a forward lookup zone, see Add a Forward Lookup Zone.
You have now created a forward lookup zone (and a domain name) to use for apps in your environment.
To create a wildcard Alias (CNAME) record for the new domain name
1. Verify that the user account that performs this procedure is a domain administrator on the domain controller.
2. In DNS Manager, under Forward Lookup Zones, right-click the new app domain name, and then click New Alias (CNAME).
3. In the New Resource Record dialog box, in the Alias name (uses parent domain if left blank) box, type *.
The Fully qualified domain name (FQDN) box displays *. followed by the domain name that you created for apps. For example, *.ContosoApps.com or *.Contoso-
Apps.com.
4. Next to the Fully qualified domain name (FQDN) for target host box, type the FQDN of the server that hosts the SharePoint sites.
Or:
a. Next to the Fully qualified domain name (FQDN) for target host box, click Browse and navigate to the Forward Lookup Zone for the domain that hosts
the SharePoint sites.
b. And then navigate to the record that points to the server that hosts the SharePoint site.
New Resource Record dialog box shows the wildcard alias for the app domain and the FQDN of the server that hosts the SharePoint sites.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
5. Click OK.
For more information about how to create a wildcard alias record in DNS Manager, see Add an Alias (CNAME) Resource Record to a Zone.
You can verify the new domain name and alias by pinging them.
To verify the new domain name
1. Verify that the user account that is performing this procedure is a domain administrator on the domain controller.
3. At the command prompt, type ping followed by a subdomain of the domain that you created, and then press ENTER.
If the ping command returns the correct IP address, then your wildcard for the domain name was configured successfully.
The domain should be added in the form of a wildcard (for example, *.ContosoApps.com). You need a wildcard certificate instead of individual certificates because each
installed app has its own subdomain.
Note:
You can make a certificate request from your SharePoint server through Internet Information Services (IIS). Take a look at the steps for generating the request here
Request an Internet Server Certificate (IIS 7) , and for installing an internet server certificate , here Install an Internet Server Certificate (IIS 7). Consult the documentation
at your Certificate Authority on how to get and download your certificate.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
Apps rely on the App Management and Microsoft SharePoint Foundation Subscription Settings service applications. These service applications use the multi-tenancy
features to provide app permissions and create the subdomains for apps. Therefore, even if you are not hosting multiple tenants, you must still establish a name for the
default tenant for your environment (any SharePoint site that is not associated with a tenant will be in the default tenant).
Note:
You can use the SharePoint Central Administration website to set the default tenant name (also know as the app prefix) for non-hosting environments. You must use
Windows PowerShell to configure tenant names for hosting environments. You perform the steps to set the app prefix in the next section, Configure the app URLs to
use.
To configure these services, you first start the services in Central Administration. After the services are started, you use Windows PowerShell to create the Subscription
Settings service application, and then use either Windows PowerShell or Central Administration to create the App Management service application.
To start the Subscription Settings and App Management services in Central Administration
1. Verify that you are a member of the farm administrators group in Central Administration.
3. On the System Settings page, under Servers, click Manage services on server.
4. On the Services on Server page, next to App Management Service, click Start.
5. On the Services on Server page, next to Microsoft SharePoint Foundation Subscription Settings Service, click Start.
6. Verify that the App Management and Microsoft SharePoint Foundation Subscription Settings services are running. The following illustration shows the Services on
Server page where you can verify that the App Management and Subscription Settings services are running.
Services on Server showing the App Management and Subscription Settings services running.
To configure the Subscription Settings service application by using Windows PowerShell
Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 15 Products cmdlets.
Note:
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about
Windows PowerShell permissions, see Add-SPShellAdmin.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
5. First you must establish the application pool, run as account, and database settings for the services. Use a managed account for the SPManagedAccount (which will
be used for the application pool runas account).
At the Windows PowerShell command prompt, type the following commands, and press ENTER after each one to create the application pool:
Where:
6. At the Windows PowerShell command prompt, type the following commands, and press ENTER after each one to create the new service application and proxy:
Where:
You can use either Windows PowerShell or Central Administration to create and configure the App Management service application. The following procedures provide the
steps for each method.
To configure the App Management service application by using Windows PowerShell
Administrators group on the server on which you are running the Windows PowerShell cmdlets.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 15 Products cmdlets.
Note:
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about
Windows PowerShell permissions, see Add-SPShellAdmin.
5. First you must establish the application pool, run as account, and database settings for the services. Use a managed account for the SPManagedAccount (which will
be used for the application pool runas account).
At the Windows PowerShell command prompt, type the following commands, and press ENTER after each one to create the application pool:
Where:
6. At the Windows PowerShell command prompt, type the following commands, and press ENTER after each one to create the new service application and proxy:
Where:
To create the App Management service application in Central Administration
1. In SharePoint 2013 Central Administration, on the Application Management page, click Manage service applications.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
2. On the ribbon, click New, and then click App Management Service.
3. In the New App Management Service Application page, in the Service Application Name box, type the name for the service application.
4. In the Database section, in the Database Server box, type the instance of SQL Server where you want to store the database, or use the default server.
5. In the Database Name box, type a database name, or use the default name.
6. Under Database authentication, select the authentication that you want to use by doing one of the following:
If you want to use Windows authentication, leave this option selected. We recommend this option because Windows authentication automatically encrypts
the password when it connects to SQL Server.
If you want to use SQL authentication, click SQL authentication. In the Account box, type the name of the account that you want the service application to
use to authenticate to the SQL Server database, and then type the password in the Password box.
Note:
In SQL authentication, an unencrypted password is sent to SQL Server. We recommend that you use SQL authentication only if you force protocol
encryption to SQL Server or encrypt network traffic by using IPsec.
7. In the Failover Database Server section, if you want to use a failover database server, specify the server name.
Click Use existing application pool, and then select the application pool that you want to use from the drop-down list.
Click Create a new application pool, type the name of the new application pool, and then under Select a security account for this application pool do
one of the following:
Click Predefined to use a predefined security account, and then select the security account from the drop-down list.
Click Configurable to specify a new security account to be used for an existing application pool. You can create a new account by clicking the
Register new managed account link.
9. In the Create App Management Service Application Proxy section, leave the Create App Management Service Application Proxy and add it to the default
proxy group check box selected.
The following illustration shows the App Management service application and proxy that were created.
Manage Service Applications page showing the App Management service application and proxy.
12. On the System Settings page, under Servers, click Manage services on server.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
13. On the Services on Server page, next to App Management Service, click Start.
Use the following procedure to configure app URLs for non-hosting (single tenant) environments by using Central Administration.
To configure app URLs
3. In the App domain box, type the isolated domain that you created for hosting apps.
4. In the App prefix box, type a name to use for the URL prefix for apps.
For example, you could use “apps” as the prefix so that you would see a URL for each app such as “apps-12345678ABCDEF.ContosoApps.com”. The following
illustration shows the Configure App URLs page after you have filled in the App domain and prefix.
The Configure App URLs page in Central Administration shows the App domain and App prefix.
5. Click OK.
6. If you will install apps and you have changed the App prefix (also known as the site subscription name), you must perform additional steps that involve restarting
the World Wide Web Publishing Service (WWW Service) that hosts the apps.
Important:
Restarting the WWW Service will also restart the IIS Admin Service and the Windows Process Activation Service. This will also shut down all Web sites and
applications that depend on these services and they may lose existing state and will be unavailable until the services successfully restart. You should plan to
perform these steps during a planned maintenance time.
To complete the App prefix rename tasks, perform these steps:
a. Stop the SharePoint Timer service.
b. Restart the World Wide Web Publishing Service that hosts the apps.
c. Start the SharePoint Timer service.
Use the following procedure to configure app URLs for multi-tenant hosting environments.
To configure app URLs by using Windows PowerShell
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
Administrators group on the server on which you are running the Windows PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 15 Products cmdlets.
Note:
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about
Windows PowerShell permissions, see Add-SPShellAdmin.
5. At the Windows PowerShell command prompt, type the following commands and press ENTER after each one:
Set-SPAppDomain <appDomain>
Where:
6. If you will install apps and you have changed the App prefix (also known as the site subscription name), you must perform additional steps that involve restarting
the World Wide Web Publishing Service (WWW Service) that hosts the apps.
Important:
Restarting the WWW Service will also restart the IIS Admin Service and the Windows Process Activation Service. This will also shut down all Web sites and
applications that depend on these services and they may lose existing state and will be unavailable until the services successfully restart. You should plan to
perform these steps during a planned maintenance time.
To complete the App prefix rename tasks, perform these steps:
a. Stop the SharePoint Timer service.
b. Restart the World Wide Web Publishing Service that hosts the apps.
c. Start the SharePoint Timer service.
To configure Internet-facing endpoints for apps
3. On the Manage Web Applications page, select the web application that you want to change.
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]
Configure an environment for apps for SharePoint (SharePoint 2013)
5. In the feature list, next to Apps that require accessible internet facing endpoints, click Activate.
6. Click OK.
In some cases, for example, when you have an on-premises SharePoint 2013 farm where updates are installed infrequently, you will need to run a cmdlet to update the
URL used to point to the SharePoint Store:
See also
Plan for apps for SharePoint 2013
Install and manage apps for SharePoint 2013
Plan app permissions management in SharePoint 2013
Plan for app authentication in SharePoint 2013
Configure app authentication in SharePoint Server 2013
Enable apps in AAM or host-header environments for SharePoint 2013
© 2015 Microsoft
https://technet.microsoft.com/en-us/library/fp161236(d=printer).aspx[3/29/2015 13:28:27]