1. Download and Install EktronCloudSetup.exe

Install EktronCloudSetup.exe.

After you download and install EktronCloudSetup.exe, the Cloud Manager is added to the Workarea Settings.

2. Create the Initial Deployment on Amazon

IMPORTANT: You must first install EktronCloudSetup.exe. See 1. Download and Install EktronCloudSetup.exe.

1. In the Workarea, choose Settings > Configuration > Cloud Manager.
2. Choose Create Hosted Service and select Amazon Web Services.
   —Image—

   

3. Click Next. A wizard appears (Step 1 of 5: Amazon Hosted Service). Fields with a red asterisk (*) are required.
   —Image—

   

   1. Cloud Site Name *—Specify a name for the site to deploy to the Cloud. (The name also is used to pre-fill Bucket Name and Database Name fields on other screens.)
   2. AWS Access Key *—Specify your Amazon Web Services (AWSAmazon Web Services) Access Key, which identifies you as the responsible party for service requests.
   3. AWS Secret Key *—Specify your Amazon Web Services (AWSAmazon Web Services) key.
   4. Hosted Service Location—Select the location that is nearest to your hosted service.
   5. Use Auto-scaling—Check this box to automatically use the number of servers you need, up to the maximum number of instances you specify. For example, if you chose 1 Web Instance, and 5 Maximum instances, the number of servers (up to 5) you use adjusts to the load.

      Auto-scaling is set on the On-Premises server and started at deployment time.

      You can set the rules for scaling in C:\Program Files (x86)\Ektron\EktronWindowsService40\Ektron.ASM.EktronServices40.exe.config in the following section:

      <!-- Auto Scaling Parameters used by Amazon CloudWatch-->
      <add key="CloudWatchMetricName" value="NetworkOut" />
      <add key="CloudWatchStatistic" value="Average" />
      <add key="MonitoringInterval" value="1" />
      <add key="BreachDuration" value="300" />
      <add key="Period" value="300" />
      <add key="UpperBreachScaleIncrement" value="1" />
      <add key="LowerBreachScaleIncrement" value="-1" />
      <add key="UpperThreshold" value="6000000" />
      <add key="LowerThreshold" value="2000000" />
      <add key="HealthyThreshold" value="3" />
      <add key="UnhealthyThreshold" value="5" />
      <add key="HealthCheckInterval" value="30" />
      <add key="HealthCheckTimeout" value="5" />
      <add key="CoolDown" value="300" />

      For information about these settings, see Amazon Auto Scaling.

   6. Web Instances—Choose the minimum number of servers on which the load will be balanced. Choosing 1 instance means there is no load balancing.
   7. Maximum instances—Choose the maximum number of servers on which the load will be balanced.
   8. Web Instances Type—Choose 1 of the following types for your Web virtual machine. This is your website, and you can have as many instances as you want. Each option is described at Amazon EC2 Instance Types.
      • c1.medium (default)—High-CPU instances—5 ECUs—2 Cores—613 MB
      • c1.xlarge—High-CPU instances—20 ECUs—8 Cores—7 GB
      • m1.small—Standard instances—1 ECU—1 Core—1.7 GB
      • m1.medium—Standard instances—2 ECUs—1 Core—3.7 GB
      • m1.large—Standard instances—4 ECUs—2 Cores—7.5 GB
      • m1.xlarge—Standard instances—8 ECUs—4 Cores—15 GB
      • m2.xlarge—High-Memory instances—6.5 ECUs—2 Cores—17.1 GB
      • m2.2xlarge—High-Memory instances—13 ECUs—4 Cores—34.2 GB
      • m2.4xlarge—High-Memory instances —26 ECUs—8 Cores—68.4 GB
   9. Support OS Instance—Windows 2008 R2 is the only option at this time.
4. Click Next. Step 2 of 5: the Hosted Service Storage and Security dialog box appears. Fields with a red asterisk (*) are required.
   —Image—

   

   IMPORTANT: Make sure that you first import the certificate (.cer) into the Management Certificate and then add the .pfx file to the cloud service.

   1. Bucket Name *—This field is already filled with the Cloud Site Name you specified but you can change it. It must be a unique name. The bucket is a container for your files.
   2. Enable CloudFront CDN—Check this box to add the CloudFront CDNcontent delivery network; multiple computers that store copies of data on the nodes of a network. to your S3 service. (CloudFront is a paid service from Amazon.) Items are cached by the CDN and requests to the CDN endpoint result in a lookup to the S3 bucket. You can reference your assets directly through your custom CloudFront endpoint; for example, http://cloudfront.example.url.com/uploadedimages/image.jpg.
   3. Ektron License Key—This field is already filled with your Ektron license. You can specify a different valid license key for the cloud site.
   4. Key Pair *—Choose from a list of existing key pairs, or specify a new one.

      IMPORTANT: For Amazon deployments only: To be able to connect to the EC2Elastic Compute Cloud; by Amazon cloud (VMvirtual machine; simulation of a machine (abstract or real) that is usually different from the target machine (where it is being simulated on). Virtual machines may be based on specifications of a hypothetical computer or emulate the computer architecture and functions of a real world computer. -- Source: wikipedia) instance, you need a private key file (.pem) for the key pair that is used during the cloud deployment. If you create a new key pair when you run the deployment wizard, the CloudPemFile folder is created in the Ektron on-premises Windows Service install directory (C:\Program Files (x86)\Ektron\EktronWindowsService40) and the .pem file is located there. If you enter an existing key pair, you must have an existing .pem file or you cannot connect to the EC2 VM; you cannot update the key pair on EC2 instance later.
      

   5. Security Group Settings *—Choose from a list of existing security group names, or specify a new one.
      Finding information about security groups

      1. In the AWS console, choose Services > EC2.
         —Image—

         

      2. On the left Navigation panel, choose Network and Security > Security Groups.
         —Image—

         

      3. Select the name of the security group you want to see. The Inbound tab displays information about the selected security group.
         —Image—

         

5. Click Next. Step 3 of 5: Amazon Database Connection dialog box appears. Fields with a red asterisk (*) are required.

   IMPORTANT: You should have completed the steps in Setting Up the Amazon EC2 Security Groups and Amazon RDS DB Security Groups to complete this wizard step.

   • If you choose an existing database, fill in the following fields and click Next.
     —Image—

     

     1. Database Name *—This field is already filled with the Cloud Site Name you specified but you can change it.
     2. Database Server *—Choose from a list of existing database servers, or specify a new one.
     3. SQL Server Username *—Specify up to 128 alpha-numeric characters (no spaces) for the database administrator account name. The first character must be a letter, and you cannot use reserved words.
     4. SQL Server Password *—Specify at least 8 and up to 128 alpha-numeric characters (no spaces) for the password for the account.
   • If you choose to create a new database, the screen expands for additional data.
     —Image—

     

     1. Database Name *—This field is already filled with the Cloud Site Name you specified but you can change it.
     2. Database Server *—Choose from a list of existing database servers, or specify a new one.
     3. Database Instance Type *—Choose Web Edition, Express Edition, or Standard Edition. For information about instance types classes, see SQL Server Editions and DB Instance Classes at Amazon Web Services.

        NOTE: The Standard edition supports notification service capabilities; Web and Express editions do not support notifications service capabilities.

     4. SQL Server Username *—Specify up to 128 alpha-numeric characters (no spaces) for the database administrator account name. The first character must be a letter, and you cannot use reserved words.
     5. SQL Server Password *—Appears if you create a new database: Specify at least 8 and up to 128 alpha-numeric characters (no spaces) for the password for the account.
     6. Re-enter SQL Server Password *—Type the password for the account again.
     7. Database Instance Class *—This value is automatically filled in based on the instance type you chose, but you can specify another value. Options are:
        • Small
        • Large
        • Extra Large
        • 2Xtra Large
        • 4Xtra Large.
     8. Server Name Prefix *—Specify up to 63 alpha-numeric characters (no spaces; up to 15 for an SQL server) for the prefix that will help you uniquely identify your server. The prefix name must begin with a letter and cannot have consecutive dashes or end in a dash .
     9. Storage Size *—The range you can specify (in gigabytes) is determined by the instance type you chose.
        • Web Edition—30 to 1024
        • Express Edition—30 to 1024
        • Standard Edition—200 to 1024
6. Click Next. Step 4 of 5: Deploy Site to Amazon Hosted Service appears.

7. Click Save. A profile is created on the View All Hosted Services screen where you can deploy the site at a later time.

   —Image—

   

8. Then, Step 5 of 5: Deploy Site to Amazon Hosted Service appears. Click Deploy Site.
   —Image—

   

   Ektron creates or uploads a new min database, provisions a storage container, creates the deployment package, and deploys them into a hosted cloud service. A confirmation message appears.

   If you choose to deploy the site at another time, click Close; the View All Hosted Services screen appears with the new profile. To deploy the site, click the Deploy Site icon ().

   —Image—

   

   To view or edit the profile, click on the Template & Database - Upload link. The View Profile "Template & Database - Upload" screen appears. For more information, see 3. Synchronize the Database and Templates.

3. Synchronize the Database and Templates

In this step, you use eSync to copy a site from a local server to the cloud. For more information on this screen, see Setting Up eSync Profiles.

1. Choose Workarea > Settings > Configuration > Cloud Manager. The view panel displays the instances of databases.
2. Run the default profile that was created by the deployment.

   IMPORTANT: Without running this profile your data and resource is not transferred to cloud. You can create additional profiles to perform a similar operation.

3. Click Add Profile () to create a profile for the template. The Add Azure Synchronization Profile screen appears. You can create additional profiles for the database.
   —Image—

   

   • Profile Name—Give a unique name to this synchronization profile. You can have several profiles to synchronize different elements at different times and frequencies.
   • Local Site Name—Specify the site that you want to synchronize.
   • Cloud Database Name—Specify the database that you want to synchronize.
   • Items to Synchronize—You can synchronize everything, or select the portions you want to synchronize on schedule, managing the synchronization activity.
   • Include/Exclude Files—Not supported.
   • Synchronization Direction—Choose which way you want to synchronize the sites.

     NOTE: Templates can only be uploaded.

   • Conflict Resolution Policy—When there is a conflict between the local and cloud sites, choose which site resolves the conflict.
   • Schedule—Choose the frequency of the automatic synchronization.
4. Specify a name, uncheck Database/Resources and CMS Core, and check the items you want to synchronize.
5. Click Save Synchronization Profile. The profile is saved and the View Azure Hosted Services screen appears.
6. In the Action section of the profile you just saved, click Sync () to synchronize the database and templates.
   

4. Manage the Cloud Instances

In the View Azure Hosted Services screen (Workarea > Settings > Configuration > Cloud Manager), you can modify cloud instances in the following ways:

• Start the instance—If the icon is green, the instance is stopped; click to start it.
• Stop the instance—If the icon is red, the instance is running; click to stop it.
• Configure Load Balancing—Modify the number of instances. One (1) instance means no load balancing; more than 1 instance balances the load equally among instances.

  NOTE: The DNS mapping needs to be changed when moving from 1-to-many or many-to-1. There also will be disruption to a live site when making changes.

• Schedule Cloud Event—Display or set cloud event schedules.
• Get Status (Hosted Service)—Display the status of all profiles.
• Delete Hosted Service—Removes the instance from the list.
• Add Profile—Add a new profile.
• Sync—Synchronize the database and templates.
• Get Status (Profile)—Display the status of the selected profile.
• Delete Profile—Removes a selected profile.

5. Schedule Cloud Events

1. Go to Settings > Cloud Manager. The Cloud Manager screen appears.
   —Image—

   

2. Click Schedule Cloud Events (). The View Schedule Cloud Events screen appears.
3. Click Schedule Cloud Event. The Schedule Cloud Event screen appears for you to fill in the fields.
   —Image—

   

   • Description—Describe what the event does.
   • Event Type—
     • Edit Instances—Change the number of instances.
     • Deploy Site—Deploy the site.
     • Delete Deployment—Opens a selector to choose sites that you want to delete.
   • Number of Web Instances—The number that you specify will overwrite the number of instances that were set up with the initial deployment.
   • Scheduled Date and Time—Specify when the event will occur.
   • Email Notifications—Send an email to the address list. Use commas to separate the addresses.
4. Click Save. The event appears on the View Scheduled Cloud Events screen.
   —Image—

   

1. Sign Up

Windows Azure hosting requires a Microsoft account (also known as a Windows Live-ID). When you have the subscription, go to https://manage.windowsazure.com and log in using your Live-ID and password.

2. Install a Cloud Server Certificate

1. From the home page of https://manage.windowsazure.com, click Settings in the left menu. The Settings screen appears.
2. Click the Management Certificates at the top of the Settings screen.
3. Click Upload at the bottom of the Setting screen. The Upload screen appears.
   —Image—

   

4. Click Browse For File and choose EktronCloud.cer from the following path:
   • 64-bit system:

     ~\Program Files (x86)\Ektron\EktronCloud\mgtcert

   • 32-bit system:

     ~\Program Files\Ektron\EktronCloud\mgtcert

5. Click OK (check mark).

3. Create a Cloud Service

NOTE: This is an optional step. If you do not create the hosted service, Ektron creates it for you.

1. From the home page of https://manage.windowsazure.com, click Cloud Services. The Cloud Services screen appears.
2. At the bottom of the screen, click New. The New panel opens.
3. Choose Compute > Cloud Service > Quick Create.
   1. Specify a URLUniversal Resource Locator name for your cloud service (for example, cloudservicename). The .cloudapp.net will be appended to your name to complete the URL.
   2. Choose the Region or Affinity Group from the drop-down list. For example, East US.
   —Image—

   

4. Click Create Cloud Service at the bottom of the panel.

4. Create a Storage Account

You need a storage account to store site resources in the cloud storage service, and to store and synchronize assetan external file, such as a Microsoft Word document or image, stored in Ektron. It can be managed like native Ektron content.s, private assets, uploaded files, uploaded images and asset library. To create a storage account:

1. From the home page of https://manage.windowsazure.com, click Storage. The Storage screen appears.
2. At the bottom of the screen, click New. The New panel opens.
3. Choose Data Service > Storage > Quick Create.
   1. Specify a URLUniversal Resource Locator name for your cloud service (for example, cloudservicename). The .core.windows.net will be appended to your name to complete the URL.
   2. Choose the Location or Affinity Group from the drop-down list. For example, East US.
   3. Leave Enable Geo-replication checked if you have multiple servers.
   —Image—

   

4. Click Create Storage Account at the bottom of the panel.

5. Create a CDN Endpoint

Content Delivery Network (CDN) serves files faster from distributed servers. For better performance, Ektron recommends that you define the endpoint for your storage accounts. To create a CDN endpoint:

1. From the home page of https://manage.windowsazure.com, click CDN. The CDN screen appears.
2. Click New. The New panel appears.
3. Choose App Services > CDN > Quick Create and select an Origin DomainURL from the drop down list.
   —Image—

   

4. Click Create at the bottom of the panel.

6. Create a Database Server

1. From the home page of https://manage.windowsazure.com, click CDN. The CDN screen appears.
2. Click New. The New panel appears.
3. Choose Data Services > SQL Database > Quick Create.
   1. Specify a Database name.
   2. Choose a server from the drop-down list or choose New SQL database server.
   3. If you choose a new server, then also specify a login and password.
   —Image—

   

4. Click Create SQL Database at the bottom of the panel.

7. Create a Firewall Rule in an SQL Database

To set up a firewall rule in an SQL database, including the IP Address from your pre-production and development machines:

1. From the home page of https://manage.windowsazure.com, click SQL Databases. The SQL Databases screen appears.
2. Click on the database name from the list. It appears in its own screen.
3. Click Dashboard at the top of the screen. The dashboard appears.
4. Click Manage allowed IP Addresses at the bottom right. The Add Firewall Rule dialog box appears. (See 7. Create a Firewall Rule in an SQL Database.)
5. Specify the Client IP addresses, and enable Yes.
   —Image—

   

6. Click Save at the bottom of the screen.

1. Download and Install EktronCloudSetup.exe

Install EktronCloudSetup.exe.

After you download and install EktronCloudSetup.exe, the Cloud Manager is added to the Workarea Settings.

2. Create the Initial Deployment on Windows Azure

IMPORTANT: You must first install EktronCloudSetup.exe. See 1. Download and Install EktronCloudSetup.exe. You must also upload the certificate to the portal and configure it to the cloud service before following this procedure.

1. In the Workarea, choose Settings > Configuration > Cloud Manager.
2. Choose Create Hosted Service. A wizard appears (Step 1 of 4: Hosted Service and Storage). Fields with a red asterisk (*) are required.
   —Image—

   

   1. Subscription ID—You can get this from https://manage.windowsazure.com.
      1. Click on Hosted Services, Storage Accounts & CDN.
      2. Click the Storage Account folder.
      3. Copy and paste the Subscription ID from the Properties panel.
   2. Hosted Service Name—Specify the name of the server.
   3. Hosted Service Location—Select the location that is nearest to your hosted service.
   4. Deployment Environment—Choose either Production (Friendly URL) or Staging (GUID-based URL).
   5. Web Virtual Machine Size—Choose Small, Medium (default), Large, or Extra Large for your Web virtual machine. This is your website, and you can have as many instances as you want. Each option is described at Amazon EC2 Instance Types.
   6. Web Instances—Choose the number of servers on which the load will be balanced.
      • 1—no load balancing.
      • more than 1—load balance equally among the number of servers you choose.
   7. Worker Virtual Machine Size—Choose Small (default), Medium, Large, or Extra Large for your windows service virtual machine. You can have only 1 instance of this virtual machine.
3. Click Next. Step 2 of 4: the Hosted Service Storage and Security dialog box appears. Fields with a red asterisk (*) are required.
   —Image—

   

   IMPORTANT: Make sure that you first install the certificate (.cer) into the Management Certificate and then add the .pfx file to the cloud service. See Also: 2. Install a Cloud Server Certificate.

   1. Storage Account—Specify the name of the storage account that you created in 4. Create a Storage Account.
   2. CDN—Specify the URL with the Content Delivery Network (CDNcontent delivery network; multiple computers that store copies of data on the nodes of a network.). You can get this from https://manage.windowsazure.com.
      1. Click Hosted Services, Storage Accounts and CDN.
      2. Click the CDN folder.
      3. Click the server name with a CDN endpoint type.
      4. Copy and paste the Default HTTP Endpoint from the Properties panel. Be sure to start the URL with http:// and place a trailing slash (/) on the end.
   3. License Key—Optionally, specify the license key.
   4. Security Protocol Setting—Choose HTTP or HTTPSHypertext Transfer Protocol Secure; a combination of HTTP and SSL/TLS protocols providing encrypted communication..
   5. Security Certificate Thumbprint—If you select HTTPS, you must also specify the hexadecimal string that contains the SHASecure Hash Algorithm-1 hash of the certificate.
   6. Caching—By default, Ektron uses the inmemory caching. However, Ektron uses the AppFabric provider to set up the session state to use inproc.
      1. Go to the portal.
      2. Click Service Bus, Access Control & Caching.
      3. Go to Services > Caching.
      4. Click an active namespace.
      5. Click View Client Configuration.
      6. Copy the XML and paste it in the Caching box.
         —Image—

         

4. Click Next. Step 3 of 4: Azure SQL Database Connection dialog box appears. Fields with a red asterisk (*) are required.
   —Image—

   

   • Database Option—Create SQL Database is the default database option. If your database is already set up, choose Do not create SQL Database.
   • Database Size—Select the size of your database.
   • SQL Database Server—You can get the server name from the https://manage.windowsazure.com portal: click Database and look under the Subscriptions folder for the server name.
   • Database Name—Specify the name of the database.
   • Administrator Login Name—Create the database administrator account name.
   • Password—Specify the password for the account.
5. Choose to create a new package or upload an existing package to deploy to the cloud. The newly created deployment package is stored at:

   ~\sync\azuredeploy\{subscription-id}\{servicename}\package\{servicename}.cspkg

   • If you choose to create a new package, you get the following dialog box..
     —Image—

     

   • If you choose to upload your files, click the Browse buttons to select the files.
     —Image—

     

   An advanced user can copy the Web.Cloud.config file from Ektron Windows service (~\Program Files (x86)\Ektron\CMS400vxx\AzureConfig).

6. Click Save. A profile is created on the View All Hosted Services screen.
7. The Create Azure Hosted Service screen appears. Click Deploy Site. Ektron creates or uploads a new min database, provisions a storage container, creates the deployment package, and deploys them to a hosted cloud service. A confirmation message appears.
   —Image—

   

3. Synchronize the Database and Templates

In this step, you use eSync to copy a site from a local server to the cloud. For more information on this screen, see Setting Up eSync Profiles.

1. Choose Workarea > Settings > Configuration > Cloud Manager. The view panel displays the instances of databases.
2. Run the default profile that was created by the deployment.

   IMPORTANT: Without running this profile your data and resource is not transferred to cloud. You can create additional profiles to perform a similar operation.

3. Click Add Profile () to create a profile for the template. The Add Azure Synchronization Profile screen appears. You can create additional profiles for the database.
   —Image—

   

   • Profile Name—Give a unique name to this synchronization profile. You can have several profiles to synchronize different elements at different times and frequencies.
   • Local Site Name—Specify the site that you want to synchronize.
   • Cloud Database Name—Specify the database that you want to synchronize.
   • Items to Synchronize—You can synchronize everything, or select the portions you want to synchronize on schedule, managing the synchronization activity.
   • Include/Exclude Files—Not supported.
   • Synchronization Direction—Choose which way you want to synchronize the sites.

     NOTE: Templates can only be uploaded.

   • Conflict Resolution Policy—When there is a conflict between the local and cloud sites, choose which site resolves the conflict.
   • Schedule—Choose the frequency of the automatic synchronization.
4. Specify a name, uncheck Database/Resources and CMS Core, and the items you want to synchronize.
5. Click Save Synchronization Profile. The profile is saved and the View Azure Hosted Services screen appears.
6. In the Action section of the profile you just saved, click Sync () to synchronize the database and templates.
   

4. Manage the Cloud Instances

In the View Azure Hosted Services screen (Workarea > Settings > Configuration > Cloud Manager), you can modify cloud instances in the following ways:

• Start the instance—If the icon is green, the instance is stopped; click to start it.
• Stop the instance—If the icon is red, the instance is running; click to stop it.
• Configure Load Balancing—Modify the number of instances. One (1) instance means no load balancing; more than 1 instance balances the load equally among instances.
• Swap Instance—If you have a production and staging server, click to swap the instance (to staging and production).
• Schedule Cloud Event—Display cloud event schedules.
• Get Status (Hosted Service)—Display the status of all profiles.
• Delete Hosted Service—Removes the instance from the list.
• Add Profile—Add a new profile.
• Sync—Synchronize the database and templates.
• Get Status (Profile)—Display the status of the selected profile.
• Delete Profile—Removes a selected profile.

5. Schedule Cloud Events

1. Go to Settings > Cloud Manager. The Cloud Manager screen appears.
   —Image—

   

2. Click Schedule Cloud Events (). The View Schedule Cloud Events screen appears.
   —Image—

   

3. Click Schedule Cloud Event. The Schedule Cloud Event screen appears for you to fill in the fields.
   —Image—

   

   • Description—Describe what the event does.
   • Event Type—
     • Edit Instances—Change the number of instances.
     • Deploy Site—Deploy the site.
     • Delete Deployment—Opens a selector to choose sites that you want to delete.
   • Number of Web Instances—The number that you specify will overwrite the number of instances that were set up with the initial deployment.
   • Scheduled Date and Time—Specify when the event will occur.
   • Email Notifications—Send an email to the address list. Use commas to separate the addresses.
4. Click Save.

6. Set up Ektron Storage

Ektron uses the unity section of your cloud web.config file to set up a storage destination.

1. Add the following to the configSections section:

   <section name="unity.storage" 
     type="Ektron.Unity.Configuration.UnityConfigurationSection,
      Ektron.Unity.Configuration, Version=2.0.414.0, Culture=neutral,
      PublicKeyToken=1e97f90fc2b998db"/>

2. Define unity.storage as follows:

   <unity.storage>
     <assembly name="Ektron.Storage"/> 
     <assembly name="Ektron.Cloud"/> 
     <namespace name="Ektron.Cloud.Azure.Storage"/> 
     <namespace name="Ektron.Storage"/> 
     <container name="storageContainer"> 
       <register type="IFileService" mapTo="CloudFileService"/> 
       <register type="IDirectoryService" mapTo="CloudDirectoryService"/>
     </container>
   </unity.storage>                                   
   

7. Set Up Ektron Caching

NOTE: Caching configuration is required only if you run more than 1 instance (load balancing). You can get the section values from the portal.

In your cloud web.config file (add location), do the following:

1. Add the following to the configSections section:

   
   <section name="dataCacheClients"
     type="Microsoft.ApplicationServer.Caching.DataCacheClientsSection, 
     Microsoft.ApplicationServer.Caching.Core" allowLocation="true" 
     allowDefinition="Everywhere"/>

2. Define dataCacheClients as follows:

   <dataCacheClients> 
     <dataCacheClient name="default"> 
       <host>
        <host name="[yournamespace].cache.windows.net" cacheport="22233" />
       </hosts> 
       <securityProperties mode="Message"> 
         <messageSecurity authorizationInfo="[yoursecretkeyinfo]"/> 
       </securityProperties> 
     </dataCacheClient> 
     <dataCacheClient name="SslEndpoint">
       <host>
         <host name="ektron.cache.windows.net" cacheport="22243"/> 
       </hosts> 
       <securityProperties mode="Message" sslEnbaled="true">
         <messageSecurity authorizationInfo="[yoursecretkeyinfo]"/> 
       </securityProperties> 
     </dataCacheClient>
   </dataCacheClients>
   

3. Set up the sessions to use Appfabric server:

   <sessionState mode="Custom" 
     customProvider="AppFabricCacheSessionStoreProvider"> 
     <providers> 
       <add name="AppFabricCacheSessionStoreProvider"
         type="Microsoft.Web.DistributedCache
           .DistributedCacheSessionStateStoreProvider,
         Microsoft.Web.DistributedCache" 
         cacheName="default" 
         useBlobMode="true" 
         dataCacheClientName="default" /> 
     </providers>
   </sessionState>

8. Set the SQL Database Connection String

In your cloud web.config file, modify the Ektron.DbConnection section to have an SQL database connection string. You can get this value from the portal.

9. Set the Blob Redirect Handler

In your cloud web.config file, insert the Blob redirect handler into the module section:

<add name="EkBlobModule"
  type="[assemblyname].BlobRedirect.Module,[assemblyname]"
  precondition="integratorMode"/>

10. Create a Cloud Package

1. Open the cloud solution from Ektron Developer's SDK.
2. Set up the storage account details in the service configuration file. Use Visual Studio 2010 (or edit the XML-based configuration file) to have the following details:

   Name: BlobOrCdnUrl
   Type: String
   Value: http://abcdefgh.vo.msecnd.net/

   Name: DataConnectionString
   Type: Connection String
   Value: DefaultEndPointProtocol=https;AccountName=mysite;AccountKey=+Uv/eXOUoYkT1...

   —Image—

   

3. Compile the project with Visual Studio 2010, or use the msbuild command as follows:

   msbuild yourcloudproject.ccproj /p:Configuration=Release /t:Build;Publish

4. Log into the portal and upload yourprojectname.cspkg and ServiceConfiguration.Cloud.cscfg into your newly created hosted service.

   NOTE: After you create the deployment, the set up on the cloud takes some time before the files are ready to be accessed.

Setting up the Cloud Service and DxH

1. Create an affinity group using any Azure data center location.
2. Create a Virtual network and a subnet of A, B, or C class IPs.
3. Create a virtual machine (VMvirtual machine; simulation of a machine (abstract or real) that is usually different from the target machine (where it is being simulated on). Virtual machines may be based on specifications of a hypothetical computer or emulate the computer architecture and functions of a real world computer. -- Source: wikipedia) using the gallery option while creating the VM. See Creating a New Azure Virtual Machine.
4. If you have not already done so, you need to install .NET 4.0 and Port sharing service before you install DxH. Note this step can be performed independently later in the process.
5. Install DxH in the VM.
6. You also need to open the firewall rule and add DxH port (default port is 808) to allow an incoming connection.
7. Create the Cloud service using the affinity group as the location.
8. Create a storage account using the affinity group as the location.
9. Create a package manually, or use the deployment wizard to build and deploy the Cloud Service Package.

If you had completed the DxH installation, you should be able to communicate between your DxH and CMS. You may need to open additional ports (for example, 808 for DxH) using the VM endpoints through the portal. If you do not want to open public end points, use the following procedure.

Securing DxH Communication

To communicate to the DxH VM through the Pass Service only, perform the following redeployment steps after deleting the current deployment.

1. Delete your current deployment from the cloud service so that you can make the change to the serviceconfiguration.cscfg file.
2. From your On-Premise system go to:

   ~/Sync/azure/{guid}/{your service name}/package/
     serviceconfiguration.cloud.cscfg

3. Add the following element before the </serviceconfiguration> tag. Make sure to replace all the values to match your cloud service, virtual network and subnet.

   <NetworkConfiguration>
     <VirtualNetworkSitename="YourVirtualNetworkName" />
     <AddressAssignments>
       <InstanceAddressroleName="YourWebRoleName">
         <Subnets>
           <Subnetname="YourVirtualNetworkSubnetName" />
         </Subnets>
       </InstanceAddress>
       <InstanceAddressroleName="YourWorkerRoleName">
         <Subnets>
           <Subnetname="YourVirtualNetworkSubnetName" />
         </Subnets>
       </InstanceAddress>
     </AddressAssignments>
   </NetworkConfiguration>

4. Create a production deployment using the new updated ServiceConfiguration.cloud.cscfg for configuration. Use from Storage option for Package. After you click on the storage option, go to your storage account and then the ektrondeployment container then select the package (.pkg) file.
   —Image—

   

Your CMS cloud service can now communicate to DxH service securely.