Kentico CMS 7.0 RC Windows Azure Deployment Guide - DevNet

44
Kentico CMS 7.0 RC Windows Azure Deployment Guide
2. Set the physicalDirectory parameter to the path to the directory where you have your second
website project installed. You don't need to provide this parameter to the first site, because its default
name "Web" instructs Visual Studio that the site definition is referring to the Web role project.
3. Specify a hostHeader for the second site. Similarly to IIS, two sites cannot listen on the same port
without having a host header specified.
Running on an emulator
If you want the two sites to run on your local machine using the emulator, you will need to take the
following additional steps:
1. Edit the hosts file from the following directory: \System32\drivers\etc\.
2. Add mappings of your local IP address to host names, which you specified for sites in the service
definition file. In the case of the provided example code, you would add the following line at the end of the
file:
127.0.0.1 www.example.com
Deploying to the cloud
There's no difference between deploying a standard application and deploying an application that runs
more Kentico CMS instances in a Web role. To deploy your application, follow the steps described in
the Deployment to the cloud topic.
2.12 Configuring external services
By default, external Windows services that come with Kentico CMS do not run in the Azure environment.
However, you can make a few adjustments to the Visual Studio project to make the services work. After
performing the steps described in this topic, the services - Scheduler and Health monitor - will run as
part of the Smart search worker role.
To enable external services on your Azure application, follow these steps:
1. Open the ServiceDefinition.csdef file and uncomment the following code:
2. Open the InstallService.cmd file from the SmartSearchWorker project and on the following line
© 2012 Kentico Software