acmeservice+bus... · web viewthere is a document from microsoft which lists the ip addresses for...

Introduction

This deployment guide is a document explaining how each of the various enterprise integration components are deployed and how their appropriate servers are built.

The format of the document is to breakdown by Server Role. Each server role is likely to have different components installed on it and different software prerequisites. Based on this the deployment guide will be broken down by server role and then cover the components that will live together on those servers.

AcmeEnterprise Services Build & Deployment Guide

Connected Systems Consulting Ltd

Azure Service Bus Bridge Server

The Azure Service Bus Gateway Server is intended to host components which will connect to the outside world via the Windows Azure Service Bus. The infrastructure design has identified the requirement to isolate these components onto a separate server role which will be protected from other parts of the network within a secure segment.

This section will explain from a server administrator and software deployment perspective how this server is build and how the various components are deployed.

1Change Analysis & Design Document

Server Build

This will be the standard windows template for Windows 2008 R2 SP1 servers. It is expected that the following components are installed on the box.

Delivered Hardware

The server will be built from a VM template delivered by the infrastructure team. It will be build to include the following software:

· Windows 2008 R2 SP1

· IIS7.5

· Microsoft .net Framework 4.0 (Full)

The hardware is actually a VMWare guest machine hosted on the normal VMWare infrastructure. The specifications of the WMWare guest are:

· Memory = 4GB· Disk

o C = 20GBo E = 20GB

· CPU = 2 Virtual CPU

Windows Azure Configuration

In order to use the components you will need to setup Windows Azure as required for the environment. The following describes this.

No Task More Info1 Setup Windows Live ID Click Here2 Setup Azure Account Click Here3 Setup namespaces This will be described in the individual application

deployment

Additional Software to Install

In addition to the prerequisites please install the following software on this server for use by its components.

No Task More Info1 Install Windows 2008 R2

IIS Security FeaturesClick Here

2 Add .net 3.5.1 Features to Windows Server

Add .net 3.5.1 features

3 Install Windows Server Click Here


AppFabric v1.1

Firewall Configuration

The following ports are expected to be used by the components and applications on this server to talk

Connecting to Windows Azure Service Bus

The below table outlines the ports and firewall configuration requirements for connections from the on-premise bridge server to Windows Azure Service Bus.

Port Source To Connect To Used For80 Bridge Server Windows Azure Service Bus

(outbound)HTTP traffic originating from this server to Windows Azure Service Bus

443 Bridge Server Windows Azure Service Bus (outbound)

SSL HTTP traffic originating from this server to Windows Azure Service Bus

9050-9054 Bridge Server Windows Azure Service Bus (outbound)

To open a listener to the Azure Service Bus

80 Bridge Server Application Proxy Server Used so the solution can be configured to use the proxy server in the future once its upgraded rather than the server having direct access through the firewall

443 Bridge Server Application Proxy Server Used so the solution can be configured to use the proxy server in the future once its upgraded rather than the server having direct access through the firewall

9050-9054 Bridge Server Application Proxy Server Used so the solution can be configured to use the proxy server in the future once its upgraded rather than the server having direct access through the firewall

80 Application Proxy Server

Windows Azure Service Bus (outbound)

HTTP traffic originating from this server to Windows Azure Service Bus

443 Application Proxy Server


SSL HTTP traffic originating from this server to Windows Azure Service Bus

9050-9054 Application Proxy Server


To open a listener to the Azure Service Bus

Note:These ports should be open for outbound connection to the Windows Azure Data Centre IP Address Range. At present we are using the North Europe Azure Data Centre based in Dublin, Ireland.


Note:We expect the specific firewall settings will change once we are able to use the proxy server for Relay Messaging but at present due to limitations of our proxy server we will only go via the proxy server for the ACS calls when connecting to the service bus and other calls will route directly out via the firewall.This is due to the HTTP 1.1 Chunked Encoding issue.

Connecting to Internal Applications

These settings will allow the bridge server to connect

Port Used By To Connect To Used For80 On premise

bridge component

Internal web services via F5 router HTTP traffic from the bridge server to route traffic to internal applications

443 On premise bridge component

Internal web services via F5 router SSL HTTP traffic from the bridge server to route traffic to internal applications

Note::Some specific applications may use other ports and these will be documented in this list as required.

Note::Most internal applications will expose services which sit behind an F5 router for load balancing.

Proxy Configuration

The proxy server is intended to be used for access to the outside world and the bridge server was intended to use this. With issues experienced with HTTP 1.1 Chunked Encoding we are not using the proxy server in the way originally intended. The proxy server is a Squid v2.6 Proxy Server from RedHat.

The proxy server will be used to configure access to the Windows Azure Access Control Service for the specific service bus namespace access control service.

The specific configuration for the proxy server is documented later in the component deployments.

Developer Machine

This page will explain how to apply additional software to change the server into a development server.

At this point you should have completed the instructions on the core server build (Click Here).


Additional Developer Software

Please install the following components.

No Task More Info1 Install Visual Studio 2010 Click Here2 Install Specflow Click Here3 Disable UAC for

AdministratorsClick Here

Service Account

When developing the software we will use a domain service account which will run any IIS Application pools and other key developer widgets.. This account needs to be part of the local admins group.

Build Server

This page will explain how to apply additional software to change the server into a build server for the developer environment.

At this point you should have completed the instructions:

· core server build (Click Here).· The developer machine (Click Here)

Additional Build Software & Installation

Please install the following components.

No Task More Info1 Install Cruise Control

version 1.8.0.0Click Here

2 Configuring CCNet Click Here3 CCOutput folder On the build server there will be a folder at the following

path.

E:\CCOutput

This is where the output from the cruise control build will be placed.

Configuring CCNet

Once cruise control has been installed we need to undertake some configuration tasks to make it run


as required.

Add Service Account to Admin Group

The service account which you will use to run the Cruise Control windows service needs to be in the local Admin Group.

Setting the Cruise Control Service Account

The cruise control windows service needs to be set to run as the normal service account user.

1. On the windows Run menu type Services.msc and hit Enter

2. On the Windows Services management console find the service called "CruiseControl.NET Server" and right click it and click Properties

3. Go to the Logon Tab of the Windows Service

4. Change the selected option to This Account

5. Enter the credentials for the windows account to run Cruise Control as. This should be the main development service account.

6. Click OK

7. Right click on the Cruise Control Service again and click Start to ensure that the Windows Service can start

Change the startup Type of Cruise Control Service

We need to change the start up type of the Cruise control windows service so it auto restarts if the server is restarted.

1. On the windows Run menu type Services.msc and hit Enter

2. On the Windows Services management console find the service called "CruiseControl.NET Server" and right click it and click Properties

3. Change the start up type to Automatic

4. Click OK

5. Right click on the Cruise Control Service again and click Start to ensure that the Windows Service can start

Setting up IIS

The below instructions will describe how to configure IIS.

1. Create an AppPool called ccnet

2. Set its type to Integrated


3. Set its identity to the developer service account

4. Create a virtual directory called ccnet

5. Set its app pool to the new ccnet app pool

6. Set its physical path to C:\Program Files (x86)\CruiseControl.NET\webdashboard

7. In IIS open the Authentication settings for the CCNet application

8. Disable everything except Windows Authentication

9. Recycle the ccnet App Pool


Remove the Sample Project from CCNet

(Note you may need to run notepad as an administrator)

1. Go to the C:\Program Files (x86)\CruiseControl.NET\server folder

2. Open the ccnet.config file in notepad

3. Remove the xml for the project called MyFirstProject

4. Save and close the file

Adding an Admin Password for CCNet

1. Navigate to the cruise control web dashboard folder C:\Program Files (x86)\CruiseControl.NET\webdashboard

2. Using Notepad open the dashboard.config file (note: you may need to open with admin permissions)

3. Edit the <administrationPlugin config item to include a password eg below:

<administrationPlugin password="<add password here>" />

4. Save the file

5. Restart the ccnet app pool in IIS

Add the required Add-in’s

1. Go to the ccnet dashboard add in page http://localhost/ccnet/AdministerDashboard.aspx

2. Enter the admin password

3. Select the following add ins and click install

· Build Packages:o MSTest2010 Resultso MSBuild Results

· Project Packages:o Project Statisticso Modification History

· Server Packageso Queue Status

· Dashboard Packageso Audit History

Test Server


The test server has no additional requirements beyond the base server build documented in the core build section.

Production Server

The production server has no additional requirements beyond the base server build documented in the core build section.

Note:In production you are likely to have a server farm. Unlike traditional IIS solutions where you have a load balancer, the Windows Azure Service Bus connectivity operates a competing consumer pattern with outbound connections which means the traffic is load balanced for you.

There is no need to have seperate load balancing software or hardware.


Components

This section will outline the components expected to live on this server role

Acme.Azure.ServiceBus.Connect

The Acme.Azure.ServiceBus.Connect widget is the custom web service implementing which uses the WCF routing service to connect to the Windows Azure Service Bus and then when a message is accepted via the Azure Service Bus Relay it will route it to an internal application web service.

The Acme.Azure.ServiceBus.Connect widget will be deployed as an IIS application.

This guide will explain how to deploy the component onto a Test or Production Server.

Assumptions

It is assumed that the following is in place before attempting this deployment:

· The person doing this deployment is an local Administrator on the Windows platform.· The person doing the deployment is familiar with deploying web services in IIS· The deployment person is familiar with standard .net configuration files and WCF

configuration· The deployment person is familiar with the Windows Azure Management Portal· The deployment person is familiar with the Windows Azure Access Control Service· The deployment person is familiar with the Windows Azure Service Bus relay· You have a clean green build from the build server· The windows azure account has already been setup which you will use

Prerequisites

The following prerequisites exist for this application.

· The servers onto which the service will be deployed are setup correctly in accordance with the Server Build Guide

·

What do I need

In order to undertake this deployment you will need the following:

What do I need Where do I get it from

Azure Service Bus Namespace Azure management portalAzure Connect Azure Shared Secret Issuer This will be available from the Azure

Management portal and should be in the form servicebusconnect-<environmentname>

We will cover this later in the guideAzure Connect Azure Shared Secret Key This will be available from the Azure

Management portal


We will cover this later in the guideConfiguration settings to connect to the brokered message service in other applications

Refer to configuration setting reports with the code

Deliverables

The deliverables of the integration team for this deployment are as follows:

Deliverable DescriptionWeb Service Folder containing web service files to be

deployedWeb Service Configuration Folder containing web service config filesDocumentation Contains all of the reports and config setting

descriptionsSpecflow Documentation Provides feature level documentation for this

component

Deployment Instructions

The following steps describe how to deploy the Acme.Azure.ServiceBus.Connect component.

No Task More Info1 Infrastructure Tasks Click Here2 Setup Azure Service Bus Click Here3 Setup IIS Click Here4 Deploy the Code to IIS 7.5 Click Here

Infrastructure TasksThis page will outline the infrastructure tasks which need to be performed for the component deployment the first time that environment is used.

Firewall Configuration

Messaging communications will have direct access from the servers via the firewall to the Azure data centres. We will be using the North Europe Azure Data Centre and the firewall will need to be configured to allow the servers in your IIS farm to talk to the Azure Data Centres.

Please coordinate with the infrastructure team to arrange the following:

Servers All servers which will host the Acme.Azure.ServiceBus.Connect component

Ports Required 8011

Change Analysis & Design Document

4439350-9354

Destination IP Range

The network security team have a firewall rule group which already contains all of the relevant ip addresses for the required azure data centres. Please refer to the network team for more info.

There is a document from Microsoft which lists the ip addresses for each data centre.

http://www.microsoft.com/en-gb/download/details.aspx?id=29840

Note these are the destination ip address range for the northern europe azure data centres.

Firewall Rule The network team have a firewall rule called:

<Rule Name>

Adding servers into this group will allow them to connect to the Azure north europe data centre.

Proxy Server Configuration

In addition to the firewall configuration any comms for the access control service goes via the proxy server. This means that the proxy server will need to be configured to allow the servers hosting the azure connect component to access the proxy server to make calls to the ACS service url. Note that the acs url is different for each environment and will correspond to the messaging namespace.

An example would be

In environment UAT

Servers <Server Name>

Needs access to ACS urlhttps://acme-azureconnect-uat-sb.accesscontrol.windows.net

Please communicate with the infrastructure team to configure the proxy server requirements before deployment.

Setting up Windows Azure Service Bus

This section will describe how to configure Windows Azure Service Bus with the correct requirements for this solution.

Accessing the Azure Management Portal & Service Bus Administration

1. In order to configure and manage your windows azure setup you need to go to the following URL.

http://www.windowsazure.com/en-us/12

Change Analysis & Design Document

2. Once there you need to sign in and go to the management portal link.

3. When the management portal opens select the Service Bus, Access Control & Caching tab at the bottom left of the page.

4. The Services node will appear in the tree view at the top left of the screen, select the Service Bus Node which will then display a list of service bus services within your subscription

Setting up the Namespace & Endpoint

To setup your first service bus relay instance you need to follow the below instructions when you are on the service bus management page.

1. Click New{} at the top left of the screen, this will open a new window.

2. Choose the services you require. You just need to senect Service Bus (Note the service bus namespace will automatically get its own ACS management endpoint)

3. In the namespace box choose a namespace for your service endpoints and click the button to check the namespace is available

To give an example of the namespace to be used for some of the key environments refer to the below table:

Environment Namespace Example UrlProduction acme-azureconnect-

production.servicebus.windows.net

http://acme-azureconnect-production.servicebus.windows.net

UAT acme-azureconnect-uat.servicebus.windows.net

http://acme-azureconnect-uat.servicebus.windows.net

4. Select the data centre region for your service bus instance

Notes:

As context it is expected that all instances of the namespaces will be setup in the Europe North Azure Data Centre.

To save confusion Europe North is the Azure Data Centre based in Dublin, Ireland where as Europe West is the Azure Data Centre based in Amsterdam, Netherlands

5. Leave all other settings as their default

6. Click create namespace

7. Please wait while the namespace is created which will take a few seconds

When your namespace is created your url will be https://<Namsepace>.servicebus.windows.net/. This makes it easy to access any services on the listener side. In addition to the service gateway endpoint, there is also the managemenet endpoint which is the namespaces ACS instance. For example https://<Namespace>-sb.accesscontrol.windows.net/


At this stage we are not using the queues and topics for this component.

Configuring the Server Side Security

By the server side security we mean securing the way that the ACME on-premise Acme.Azure.ServiceBus.Connect component accesses the Azure Service Bus to listen for messages. The Acme.Azure.ServiceBus.Connect component will be given its own key which will allow it to have the listen permission. Client applications will not be given the listen permission otherwise they would be able to listen for messages which would be a security vulnerability.

Out of the box ACS only includes an owner identity which has all permissions this would not be appropriate to use especially from an external application. The owner identity should not be used and ideally deleted. We will setup an identity for each application which may send or receive messages from the service bus.

To set this up please go to the ACS site for the service bus endpoint for example: https://<namespace>-sb.accesscontrol.windows.net (eg: https://acme-azureconnect-uat-sb.accesscontrol.windows.net)

Setting up the ACS Identity

To setup the identity for the listening AzureConnect component follow the instructions below:

1. Under the Service Settings on the left hand menu click "Service Identities"

2. Click the Add link

3. Add the name "azureconnect-<environmentname>"For example "azureconnect-uat"

4. Add a description which says "Enables Acme.Azure.ServiceBus.Connect component to access relayed messages"

5. The credential type should be "Symmetric Key"

6. For the key please generate a new key with the generate button

7. Set the effective date to be from today date

8. Set the expiration date to an appropriate date inline with the key expiration policy.

9. Click Save

10. These settings need to be kept safe and need to be added to the configuration team spreadsheet for use with other environments

Setting up the ACS Identity Claims

To configure this follow the instructions below:

1. Click the Rule Groups link under the Trust Relationships section on the left hand menu

2. Click the link for the "Default Rule Group for ServiceBus"


The existing claims you will see listed are for the "owner" permissions

3. Add the following claims mappings to the default rule group

Input Claim Issuer

Input Claim Type

Input Claim Value

Output Claim Type

Output Claim Value

Description

Access Control Service

nameidentifier(its the one from the identity/claims items in the drop down list)

azureconnect-<EnvironmentName>

eg: azureconnect-uat

net.windows.servicebus.action

Listen Enables Acme.Azure.ServiceBus.Connect component to access relayed messages

4. Click Save

When your Azure Connect component comes online, it will now have the appropriate permissions so that using the identity you created earlier it will be able to access and listen for messages.

Configuring the Client Side Security

The client side security in this context refers to providing security options for applications which want to send messages to the service bus. This section will describe how to configure the client security for all applications which will send messages to the service bus messaging component.

To configure the security please go to the access control instance for your Azure Service Bus namespace https://<namespace>-sb.accesscontrol.windows.net (eg: https://acme-azureconnect-uat-sb.accesscontrol.windows.net).

To configure the sender to have permission to send messages to the relay we will have a unique identity for each sending application. The applications we currently expect to support include:

· Dynamics CRM

The following instructions below will setup a generic permission for each identity. The current list of sender identities is:

Identity Identity Name (for the claim)

Identity Provider Description

Dynamics CRM Online

dynamicscrm-<EnvironmentName>

eg: dynamicscrm-smoked

Azure ACS with Shared Secret

This is the online instance of dynamics crm which will be integrating into SWIFT

Config Team Notes:

In the future other applications may not use shared secret and ACS for authentication. They will still however use ACS for claims mapping to provide access to the service bus. The documentation in this section is currently focused around the Dynamics CRM online access to service bus. the


documentation will be likely to change significantly when there is another client who does not use ACS Shared Secret.

Please take the following tasks to configure client security:

1. Configure security for Dynamics CRM

Setting up Client Security for Dynamics CRM

This section will describe how to configure the client side access to the Service Bus namespace required for Dynamics CRM to be able to access the service bus.

Setting up the ACS IdentityTo setup the identity for the sender use the instructions below

1. Under the Service Settings on the left hand menu click "Service Identities"

2. Click the Add link

3. Add the name <IdentityName>

For example: dynamicscrm-<EnvironmentName> (dynamicscrm-uat)

4. Add a description which is from the table above relating to this identity

5. The credential type should be "Symmetric Key"

6. For the key please generate a new key with the generate button

7. Set the effective date to be today

8. Set the expiration date to be a date inline with the key expiration policy

9. Click Save

10. These settings need to be kept safe and used in the deployment of dynamics CRM and its associated web role.

Setting up the ACS Identity ClaimsTo configure this follow the instructions below:

1. Click the Rule Groups link under the Trust Relationships section on the left hand menu

2. Click the link for the "Default Rule Group for ServiceBus"

3. Add the following claims mappings to the default rule group

Input Claim Issuer

Input Claim Type

Input Claim Value

Output Claim Type

Output Claim Value

Description

Access Control Service

nameidentifier(its the one from

dynamicscrm-<environmentna

net.windows.servicebus.action

Send Claim Rule for the CRM


the identity/claims items in the drop down list)

me> consumer application

(Note: External Clients only need to have the send permisison to be able send messages to the relay and to get a reply)

Setting up IIS

This section will describe how to setup IIS for the Azure Connect Component.

Create Application Pool

The component will run in IIS so we will need an IIS application pool which will be the w3wp host process for this component. The application pool will run as a service account like all other servers.

The following steps will help you to create the application pool.

1. Open the Server Manager

2. Open the left hand tree node to Roles --> Web Serrver -->Internet Information Services IIS Manager and click on this node

3. In the right hand window open the tree node for the server name and click the child node Application Pools

4. Right click on the Application Pools node and seleft the menu item "Add New Application Pool"

5. In the window add the following settings then click ok:Name = Acme.Azure.ServiceBus.Connect.net Framework = .net Framework v4.0.30319Pipeline = IntegratedStart App Pool Imediately = true

6. The list of app pools will now show your new application pool. Right click on it and choose Advanced Settings

7. In the process model/Identity settings click the ellipsis button next to the identity and this will open the new window

8. Change the radio button to choose a custom identity and click the set button

9. Provide the credentials for your application pool and click ok

10. Add the App Pool identity to the IIS_Usr security group

11. Restart IIS

You have now created your application pool.


Create IIS Application

In IIS we will ned to create an IIS application which will be used to host the WCF component. Please follow the instructions below.

1. Create physical directoryCreate the following directory e:\WebSites\Acme.Azure.ServiceBus.Connect

This will be where the code will be deployed to

2. Open the Server Manager

3. Open the left hand tree node to Roles --> Web Serrver -->Internet Information Services IIS Manager and click on this node

4. Open the Site tree node and then the Default Website Tree Node

5. Right click on the Default Website Tree node and choose Add Application, this will open a new window

6. Set the alias for your application to be Acme.Azure.ServiceBus.Connect

7. Click the select button next to App Pool and change the app pool to the one you created in the previous section

8. Set the physical path to be the path you used in step 1

You have now created the IIS Application.

Deploy Cloud Connect to IIS 7.5

This section will describe the steps to deploy the Acme.Azure.ServiceBus.Connect component.

Create Event Log Source

To create the event log source used by this component please execute the following command:

eventcreate /ID 1 /L APPLICATION /T INFORMATION /SO Acme.Azure.ServiceBus.Connect /D "Create Event Log Source"

Notes:

Note these need to be ran as an administrator

Copy the Code

Copy the files inside the Package/WebService directory to the physical directory for the iis application you have created.


Reconfigure the WCF Service

When the WCF service is deployed it will need to be reconfigured to have the appropriate settings for your environment. There are two ways to do this depending upon which team your in.

Development Team

If you are in the dev team deploying to the test server then in the Package/WebServiceConfiguration folder you will find a web.config file already tagged up with the right settings. Use this file to replace the web.config file in the iis application physical directory

Configure IIS Autostart

IIS autostart using Windows Server AppFabric extensions to IIS needs to be configured to allow the services to auto-start and connect to the Azure Service Bus to start listening for messages.

To configure this please refer to the following section Configure IIS AppFabric Autostart

Ensuring the Proxy and Certificate Cache are Configured

Sometimes we get issues when the certificate trust chain is not validated correctly and this seems to be avoided when the below settings are in place.

Open the command prompt running as administrator.

1. Run the following command:certutil -urlcache * delete

This will clear the certificate cache

2. Run the following command:netsh winhttp set proxy proxy-server="http://<proxy server>"

This setting configures the WinHTTP proxy setting

Configure IIS AppFabric Autostart

This page will describe how to configure the services to autostart for hosting of WCF services in IIS 7.5 which will listen to the Windows Azure Service Bus Relay.

1. In IIS Manager select the Acme.Azure.ServiceBus.Connect web application and from the right hand pane under the "Manage WCF and WF Services" heading click Configure.


2. When the window opens select the Auto-Start tab on the left.

3. Choose the Enabled (all services will auto-start) option

4. Click OK and you will get a warning about the app pool restarting

Smoke Test

The following smoke tests can be ran to ensure the component is working correctly.

1. Test Application

There is a test application included with the Acme.Azure.ServiceBus.Connect component deployment package which will allow you to test the stack from the level of calling the service bus simulating what the Dynamics application will do.

The deployment team can configure this test application and ensure the services exposed by Azure Service Bus are functioning correctly.


Software Installs

This section will outline some standard instructions for installing particular components which may be reused elsewhere in this guide.


Install.net 4.0

These instructions will help you to install net 4.0.

Install .net 4.0

Note.net 4.0 should be installed on all BizTalk and SQL Server machines.

1. Download the redistributable from the following location:http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0A391ABD-25C1-4FC0-919F-B21F31AB88B7

2. Run the msi

3. Accept the terns and conditions and click Install4. Click Finish5. You will now need to restart the computer

.net 4.0 is now installed on this server.


Add .net 3.5.1 Features to Windows 2008R2

These instructions will help you to add the .net 3.5 features to Windows 2008 R2.

1. Open Server Manager

2. Select Features on the tree view

3. Click Add Features

4. Check .net Framework 3.5.1 Features

5. Click Add Required Features when the prompt window comes up


6. Click Next

7. Click Install

8. When the final screen confirms installation click Close


Install Windows Server AppFabric v1.1 x64 for Cloud Connect

This section will describe how to install Windows Server AppFabric v1.1 64 bit on Windows 2008 R2.

The installation can be obtained from the following page:http://www.microsoft.com/en-gb/download/details.aspx?id=27115

1. Double Click WindowsServerAppFabricSetup_x64.exe which will extract and start the installation

2. Select Yes to accept the license agreement and then click next

3. Choose not to participate in the customer experience programme and click next


4. Choose No so windows updates are not automatically applied


5. Choose just the AppFabric Hosting Services and click Next

Note:On developer servers install this to the C drive and on Test servers install this to the E drive


6. Click Install to confirm the setup and install AppFabric


7. Click Finish to complete the Install and open the configuration tool


8. This will close the installation and open the AppFabric Configuration Wizard

9. Select No to not send info to Microsoft and click Next


10. Do not choose any monitoring or persistence providers then click Next


11. Check the box to start IIS and then click Finish


Install Visual Studio 2010

This section will explain how to install Visual Studio 2010.

1. Mount the Visual Studio en_visual_studio_2010_ultimate_x86_dvd_509116.iso file

2. In the iso run the setup.exe file

3. On the setup screen click Install Microsoft Visual Studio 2010

4. In the installation start screen uncheck the Send Information to Microsoft check box and then click Next


5. On the license agreement screen select I have read and accept the license terms and click next


6. On the install features screen select Custom and click Next


7. On the options page choose the options shown below and click Install


8. Wait while the installation progresses


9. Once the installation is complete click Finish


10. In the installation complete screen click Exit


Install Specflow 1.8.1

This page will describe how to install Specflow 1.8.1 onto a developer machine.

The installation can be obtained from the following location:http://www.specflow.org/downloads/installer.aspx

1. Double Click SpecFlowSetup_v1.8.1.msi

2. On the introduction screen click Next

3. On the license screen click to accept the license and click next


4. On the components screen click Next

5. On the ready to install screen click Install


6. On the install complete screen click finish


Install Cruise Control.net 1.8.0.0

This page will describe how to install Cruise Control.net

The installation can be obtained from the following location:

http://sourceforge.net/projects/ccnet/

1. Double click the CruiseControl.NET-1.8.0.0-Setup.exe file

2. On the introduction screen click Next

3. On the License Agreement screen click I Agree


4. On the choose components screen uncheck Examples and then click Next

5. On the additional configuration screen click Next


6. On the Installation Location Screen click Next

7. On the start menu folder screen click Install


8. On the install completed screen click Next

9. On the Install Completed screen click Finish


Add Windows 2008 R2 IIS Security Services

This section will explain how to add the appropriate security features for IIS.

1. Open Server Manager

2. Navigate the tree structure to Roles\Web Server and click the web server role

3. On the details page Go to the Role Services section

4. Click Add Role Services

5. Select all options under Security and click next


6. Click Install


7. On the completed screen click close


Disable UAC in Windows 2008 R2

In the developer and build machines we need to disable Admin Approval Mode to allow automated scripts to run without problems around UAC.

1. Click Start, click All Programs, click Accessories, click Run, type secpol.msc in the Open box, and then click OK.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

3. From the Local Security Settings console tree, double-click Local Policies, and then double-click Security Options.

4. Scroll down and double-click User Account Control: Run all administrators in Admin Approval Mode.

5. Select the Disabled option, and then click OK.


6. Close the Local Security Settings window.

7. Restart the machine


Create Windows Live ID for Azure

This page will describe how to create a Windows Live ID for use with Windows Azure

1. Browse to http://www.windowsazure.com/en-us/

2. Click on the Portal Link

3. This will take you to the Windows Azure login page

4. On the login page click "Sign up now"

5. Enter some details for signing up(The below are the developer details)


6. Once you have added all details click OK

7. You will receive an email with a link to click to verify your email address. Please click this and then log into windows live


8. You will be prompted that your account has been created


Create Windows Azure Account

This page will describe how to create a WindowsAzure account

1. Browse to http://www.windowsazure.com/en-us/

2. Click on the Portal Link

3. You will be directed to a page asking you to sign up. Click the signup link

4. On the select your plan screen select the Pay-As-You-Go option and click purchase


5. On the confirmation of what you need click the next arrow


6. On the verify your account screen enter your mobile number and select to text yourself a verification code and click "Send Text Message"


7. Using the verification code from your SMS message enter the code into verify code text box and click next arrow and click verify account button

8. You will be shown a tick confirming the account then click the Next Button


9. Enter the details on the account information form


10. Once the details have been completed and accepted you will be prompted that you have sccessfully created your account

11. You will recieve some emails confirming that you have created a windows azure account


acmeservice+bus... · web viewthere is a document from microsoft which lists the ip addresses for...

Documents