I'm trying to configure an App Server based on the Provider-Hosted (on-premise) App model. In my environment, I've got a separate non-SharePoint IIS server that I wish to publish apps to that will then expose the apps to a SharePoint 2013 farm. I believe I've got all the pieces in place:
- New DNS domain has been created with wildcard alias.
- Self-signed certificate has been created and a trusted environment established between servers.
- The App Management and Subscription Settings Service Applications have been configured (and corresponding services are running)
- The App Host web application has been created (in SharePoint) along with a root site collection.
- The App Domain and App Prefix have been configured.
I am able to publish an App to the IIS server, then upload the AppManifest.xml file to SharePoint so that it is aware of the app. I can see the App in the App Store and select it from a site collection. The app informs me as to the permissions it will be needing and asks me to trust the app. When I try to run the app, however, it can't find the page (404 Page Not Found). The App is a simple "Hello World" type app that has no SharePoint components in it.
I suspect that my app routing is not configured correctly, but am unsure how to set that up. Here are my questions:
- Since the App is being published to IIS, should the DNS wildcard alias refer to the SharePoint environment or to the IIS server? If the DNS wildcard alias refers to the IIS server, then how does traffic get routed to the app url site collection that SharePoint creates for the app?
- My background is not in development, but I did notice a "redirect URI" field when setting up the sample high trust application. Does that come into play here?
- Do I need to create any entries in my local HOSTS file either on the IIS server or on the SharePoint servers?
Thank you in advance for any help and feedback that can be provided.