After working through a few issues with the App Management Service Application I figured I should blog my findings. The App Management service actually needs another service application created before it’ll work properly: The Subscription Settings Service Application (See here for instructions on setting it up – It can only be configured with PowerShell: http://technet.microsoft.com/en-us/library/fp161236.aspx)
After setting up this Service Application the “Microsoft SharePoint Foundation Subscription Settings Service” needs to be started in order for Apps to work. In 2010 this was only for multi-tenant installations, but there is now a dependency for apps.
After setting up the appropriate services you need to configure a generic web application that has a blank host header and listens on port 80. Because of how the redirect for the app domain works IIS will try to resolve the app URL by using the default IIS web site, which of course doesn’t work. This appears to be fixed in the March 2013 Public Update (http://technet.microsoft.com/en-us/library/dn144963.aspx).
One gotcha here is that if the NETBIOS name of the server is longer than 15 characters make sure that the generic web application is equivalent to this. Do not go in and change the URL to the full server name as this causes issues!
Here’s a quick checklist to go through when setting up the App Environment:
- Create a fwd lookup zone for apps (ContosoApps.com)
- Create a CNAME alias from app domain to SharePoint Domain
- OPTIONAL: Wildcard SSL Cert for app domain
- Note: If you have a wildcard certificate for *.ContosoApps.com, you would need to purchase another wildcard certificate for *.apps.contoso.com if you are using a subdomain as your app domain. Microsoft highly recommends that you create a new domain name for apps.
- Create the Subscription Settings Service Application using PowerShell ONLY
- Start the Microsoft SharePoint Foundation Subscription Settings Service
- Configure the App Management Service Application (Central Admin or PowerShell)
- Configure App URLs in Central Admin (App Domain and App Prefix)
- Note: Anytime you make a change to this you need to do an IISReset
- OPTIONAL: If using Host Headers you will need to create a generic web app that has a blank host header and listens on port 80 (Or 443 if you are using HTTPS). (Unless March 2013 Public Update is applied)
Edit 8/7/13: For a full setup with screenshots check out http://www.andrewjbillings.com/appsyammer2013/