If you put these directly in your app host config with updated names and
folder paths, you shouldn't need to do any more setup.
C:\Windows\System32\inetsrv\config\applicationHost.config
Trying to open the file from the Open Dialog in an editor may not show
the file appropriately, but navigating to the folder and selecting open
with... should work.
WARNING! BACK UP YOUR CONFIG FIRST
Example App Pools (under the app pools section)
<add name="ClarityDemos.com (local-dm-47.) (DNN)" autoStart="true" managedRuntimeVersion="v4.0" startMode="AlwaysRunning"><processModel identityType="NetworkService" idleTimeout="00:00:00" /><recycling><periodicRestart time="00:00:00" /></recycling></add>
Example of a fully set up site (under the sites section)
<site name="ClarityDemos.com (local-dm-47.)" id="1" serverAutoStart="true">
<application path="/" applicationPool="ClarityDemos.com (local-dm-47.) (DNN)">
<virtualDirectory path="/" physicalPath="C:\Data\Projects\Clients\CEF-4.7-DM" />
<virtualDirectory path="/DesktopModules/ClarityEcommerce/UI" physicalPath="C:\Data\Projects\CEF-4.7-DM\08.Clarity.Ecommerce.UI" />
<virtualDirectory path="/DesktopModules/ClarityEcommerce/UI/documentation" physicalPath="C:\Data\Projects\CEF-4.7-DM\08.Clarity.Ecommerce.APIReference" />
</application>
<application path="/DesktopModules/ClarityEcommerce/API" applicationPool="ClarityDemos.com (local-dm-47.) (API)">
<virtualDirectory path="/" physicalPath="C:\Data\Projects\CEF-4.7-DM\06.Clarity.Ecommerce.Service" />
</application>
<application path="/DesktopModules/ClarityEcommerce/Reporting" applicationPool="ClarityDemos.com (local-dm-47.) (Reporting)">
<virtualDirectory path="/" physicalPath="C:\Data\Projects\CEF-4.7-DM\07.Clarity.Ecommerce.Service.Reporting" />
</application>
<application path="/DesktopModules/ClarityEcommerce/Scheduler" applicationPool="ClarityDemos.com (local-dm-47.) (Scheduler)" serviceAutoStartEnabled="true" serviceAutoStartProvider="SchedulerApplicationPreload" preloadEnabled="true">
<virtualDirectory path="/" physicalPath="C:\Data\Projects\CEF-4.7-DM\08.Clarity.Ecommerce.Scheduler" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:80:local-dm-47.claritydemos.com" />
</bindings>
</site>
After the </sites> tag
<serviceAutoStartProviders>
<clear />
<add name="SchedulerApplicationPreload" type="Clarity.Ecommerce.Scheduler.SchedulerApplicationPreload, Clarity.Ecommerce.Scheduler" />
</serviceAutoStartProviders>
When working with connect, you will perform almost exactly the same
actions, just do it to the connect app pool and site specifically and
use ApplicationPreload instead of SchedulerApplicationPreload and it
would be under the appropriate Connect namespace.