RMS PTY LTD
Setting Up RMSWeb Web
Server (Win IIS 6)
Using the RMSWeb Deployment Tool
8/17/2010
Table of Contents
Deployment Package .......................................................................................................................... 3
Setting up IIS Web Server Environment.............................................................................................. 4
Web Server Requirements .............................................................................................................. 4
Add MIME Types for Silverlight to IIS ............................................................................................. 4
Publish Deployment Files ................................................................................................................ 5
Setting Up RMSWeb on IIS Web Server .............................................................................................. 6
Setting up RMSWeb with Default Web Site as Root ....................................................................... 6
Setting up RMSWeb under New Virtual Directory in Default Web Site ......................................... 6
Setting up RMSWeb under Web Site other then Default Web Site................................................ 7
Setting up Virtual Directories .......................................................................................................... 7
Setting up ASP.NET Versions ........................................................................................................... 8
Setting up SSL on the Website and Virtual Directories ................................................................... 8
Appendix ............................................................................................................................................. 9
Enable Compression for WCF.......................................................................................................... 9
Deployment Package
A deployment folder contains the following files shown below.
The Installer.exe launches the installer; this must be run from the Web Server on which the
deployment is to take place. All files should remain in the same directory.
Setting up IIS Web Server Environment
This section ensures you understand what software is required on your web server.
Web Server Requirements
- Ensure .NET Framework 4.0 is installed
- In control panel add/remove programs go to ‘Add/Remove Windows Components’ Select
‘Application Server’ and ensure that Asp.Net is ticked.
- To fix mappings for ASP.NET if needed follow the steps:
o Click Start->run->cmd – press Enter
o Type "%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe" –i then
press Enter.
- Copy the crossdomain.xml and clientaccesspolicy.xml to your IIS Root
(C:\inetpub\wwwroot\).
- If you are hosting in a website other then the ‘Default Website’ then copy the
crossdomain.xml and clientaccesspolicy.xml to the Website Root
- You will need to setup your self-signed or real SSL key. (Steps for setting up an SSL Key are
outside the scope of this document).
Add MIME Types for Silverlight to IIS
- .xaml application/xaml+xml
- .xap
application/x-silverlight-app
- .xbap application/x-ms-xbap
Publish Deployment Files
This prepares the deployment files so that they can be manually placed in IIS.
Ensure you do not have the Output Directory open in Windows Explorer.
1. Run Installer.exe
2. Fill out your desired Server Url and Output Directory.
a. Don’t include http:// or https:// in Server Url
3. Press Publish
4. Once publish completes go to the output directory. It should be laid out as below.
5. Go to section ‘Setting Up RMSWeb on IIS Web Server’ to determine which setup you desire
and follow the steps therein to continue deployment.
Setting Up RMSWeb on IIS Web Server
Setting up RMSWeb with Default Web Site as Root
This allows RMSWeb to be accessed using https://[YourUrl]/Default.apsx or http://[YourUrl]
depending on how you setup your default web site. Example if the header host URL in the Default
Web Site was www.rmsweb.com.au then you could access RMSWeb in your browser using
https://www.rmsweb.com.au/Default.apsx
Setting up RMSWeb under New Virtual Directory in Default Web Site
This allows RMSWeb to be accessed using https://[YourUrl]/[YourVD]/Default.apsx
Example if the header host URL in the Default Web Site was www.rmsweb.com.au and the Virtual
Directory is RMSWebTest then you could access RMSWeb in your browser using
https://www.rmsweb.com.au/RMSWebTest/Default.apsx
Setting up RMSWeb under Web Site other then Default Web Site
This allows RMSWeb to be accessed using https://[YourUrl]/Default.apsx or http://[YourUrl]
depending on how you setup your web site.
Example if the header host URL in the Default Web Site was www.rmsweblive.com.au then you
could access RMSWeb in your browser using https://www.rmsweblive.com.au/Default.apsx
Setting up Virtual Directories
From the previous step the following three folders are required to be converted to Virtual
Directories: MergeFields, FunctionLibrary, ReportLibrary.
Do do this for each folder:
1.
2.
3.
4.
5.
Right click folder and select properties
Select the Directory tab
Click on the Create button
Set Execute Permission to Scripts Only
Select the Application Pool (Ensure the App Pool is for .NET v4.0)
Setting up ASP.NET Versions
You must ensure that each virtual directory and website has an ASP.NET version set to V4.0.
Perform the following steps on each website and virtual directory.
1. Right click on the website or virtual directory and Select Properties
2. Select the ASP.NET tab and verify the version you are using is V4.0, set it if it is not.
Setting up SSL on the Website and Virtual Directories
THIS ASSUMES YOU HAVE SETUP YOUR OWN SELF SIGNED OR REAL SSL KEY (Steps for setting up an
SSL Key are outside the scope of this document).
Perform the following steps on each website and virtual directory.
1.
2.
3.
4.
Right Click on the website or virtual directory and select Properties
Select the tab labelled Directory Security
Press Edit in the secure communications section
Ensure Requires secure channel (SSL) and Requires 128-bit encryption is checked
Appendix
Enable Compression for WCF
In IIS select the properties of Web Site folder (Default Website or other)
1. Go To Services Tab and enable Compression application files
2. Select OK
3. Open command prompt and go to C:\inetput\Adminscripts\ and run the following
commands
CSCRIPT.EXE ADSUTIL.VBS SET W3Svc/Filters/Compression/GZIP/HcScriptFileExtensions "asp" "dll" "exe" "svc"
CSCRIPT.EXE ADSUTIL.VBS SET W3Svc/Filters/Compression/DEFLATE/HcScriptFileExtensions "asp" "dll" "exe" "svc"
CSCRIPT.EXE ADSUTIL.VBS SET W3Svc/Filters/Compression/GZIP/HcDynamicCompressionLevel 9
CSCRIPT.EXE ADSUTIL.VBS SET W3Svc/Filters/Compression/DEFLATE/HcDynamicCompressionLevel 9
5. Restart IIS
See Notes for HTTP Compression, you should ensure that compression is suitable for your web
server hosting environment.
See http://technet.microsoft.com/en-us/library/cc753681(WS.10).aspx. Configure HTTP compression of
dynamic content to use bandwidth more efficiently. Enabling dynamic compression always gives you more
efficient use of bandwidth, but if your server's processor utilization is already very high, the CPU load imposed
by dynamic compression might make your site perform more slowly.
See http://technet.microsoft.com/en-us/library/cc754668(WS.10).aspx. Configure HTTP compression of
static content to use bandwidth more efficiently. Enabling static compression gives you more efficient use of
bandwidth. Unlike dynamic responses, compressed static responses can be cached without degrading CPU
resources.